mgmt | OSv management layer implementation | Runtime Evironment library

To achieve that, first you have to group by department, and only then by gender, not the opposite.

The first collector groupingBy(Employee::getDepartment, _downstream_ ) will split the data set into groups based on department. As it downstream collector partitioningBy(employee -> employee.getGender() == Employee.Gender.MALE, _downstream_ ) will be applied, it'll divide the data mapped to each department into two parts based on the employee gender. And finally, Collectors.counting() applied as a downstream will provide the total number of employees of each gender for every department.

So the intermediate map produced by the collect() operation will be of type Map> - employee count by gender (Boolean) for each department (for simplicity, department is a plain string).

The next step in transform this map into Map> - employee count by department for each gender.

My approach is to create a stream over the entry set and replace each entry with a new one, which will hold a gender as its key and in order to preserve the information about a department its value in turn will be an entry with a department as a key and a with a count by department as its value.

Then collect the stream of entries with groupingBy by the entry key. Apply mapping as a downstream collector to extract the nested entry. And then apply Collectors.toMap() to collect entries of type Map.Entry into map.

all departments are included in a sorted order

To insure the order in the nested map (department by count) a NavigableMap should be used.

In order to do that, a flavor of toMap() that expects a mapFactory needs to be used (it also expects a mergeFunction which isn't really useful for this task since there will be no duplicates, but it has to be provided as well).

You can do this two ways:

• custom types (to hide the MarshalJSON methods); or
• custom marshaler (using reflect to ignore any MarshalJSON methods at runtime)

For example, take these nested types:

Use the filter from_yaml to convert the items to dictionaries. For example

It's unclear what you're trying to do, since the count of NAs are different for each columns, but here's a starting point:

you could write this jinja2 template: you loop only if dict_item['json']['hubs'] is defined

Given the list

heroku-fork still works. But it only works if there is actually any code to fork. The important lines here are:

I think something like the following should do the trick:

The VM list all returns a result of Paged values. So , in order to print all the VM's you will need to use by_page or next.

Another issue is doesn't have get_token , so while retrieving the paged values will error out in authentication failed. To avoid this , you can use which is the same as Service Principal Credentials.

I tested applying the above solutions to your code in my environment as below: