Add PageListingViewSet for custom per-page-type page listings

Introduce a new PageListingViewSet to provide filterable, customisable flat listings of a given page type. These share most of the functionality of the new universal listing implementation for pages, except for the ability to navigate through the tree (which is now shifted into a separate ExplorableIndexView subclass), and can potentially serve as a replacement for ModelAdmin's page model support. (It is currently missing the functionality for adding a new page, possibly choosing a parent page along the way.)
This can be tested against bakerydemo by adding the following to bakerydemo/base/wagtail_hooks.py:
from wagtail.admin.viewsets.pages import PageListingViewSet

class BreadPageFilterSet(PageListingViewSet.filterset_class):
    class Meta:
        model = BreadPage
        fields = ["bread_type"]

class BreadPageListingViewSet(PageListingViewSet):
    icon = "globe"
    menu_label = "Bread Pages"
    add_to_admin_menu = True
    model = BreadPage
    columns = PageListingViewSet.columns + [
        Column("bread_type", label="Bread Type", sort_key="bread_type"),
    ]
    filterset_class = BreadPageFilterSet

bread_page_listing_viewset = BreadPageListingViewSet('bread_pages')
@hooks.register('register_admin_viewset')
def register_bread_page_listing_viewset():
    return bread_page_listing_viewset

Please check the following:

[ ] Do the tests still pass?[^1]
[ ] Does the code comply with the style guide?

[ ] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For new features: Has the documentation been updated accordingly? (Not yet - will try to get this together during the 6.0 feature freeze...)

[^1]: Development Testing

Rebased

Re-rebased following #11483 :-)


The demo page is dead

It returns 404 here

It should be https://domoritz.github.io/vbb-coverage/. Can you send a pull request?

Suree! going to make one


Disable and Enable External Logins

Hi,
How can i disable and enable external logins? to not show and accessible with users temporary and enable every time i want,
Thanks,

You can remove them at https://github.com/simplcommerce/SimplCommerce/blob/master/src/SimplCommerce.WebHost/Extensions/ServiceCollectionExtensions.cs#L181

You can remove them at https://github.com/simplcommerce/SimplCommerce/blob/master/src/SimplCommerce.WebHost/Extensions/ServiceCollectionExtensions.cs#L181

@thiennn
Thanks bro, Done.


Fix parameter subsitution

Which issue(s) this PR fixes
Fix for https://github.com/portworx/pds-api-go-client/pull/21, the default substitution didn't work.

Let's try to merge to see if it unblocks us.


index.html includes itself in the list

https://itwin.github.io/iTwinUI/

I noticed local & live both list index as a demo page & it just refreshes the homepage.  Not sure when this got introduced.

Originally posted by FlyersPh9 in https://github.com/iTwin/iTwinUI/issues/718#issuecomment-1213206314

Reopening since we reverted #853 with #865


Update the demo to use port 5001 instead of 5000 to make it easier on a Mac

Update all port 5000 references to 5001
Updates to readme for demo from running locally

I don't really like how the local docker environment's configuration is affecting the deployment configuration.  It should be possible to separate the two so the deployment configuration can be defined independently of the local docker configuration.  That would allow it to remain the same now, and change independently in the future if needed.

I think I know what you are saying (too much hardcoded?) but either way, it's a different change than this. All I did here was change the port 5000 references to 5001.

Can you tell me the impacted files to undo?  Is it all of the yml files in the Openshift folder?

All of the files in the openshift folder and perhaps oidc-controller/src/VCAuthn/Properties/launchSettings.json and oidc-controller/src/VCAuthn/appsettings.json.  You should be able to override the properties in the json files, if needed, using environment variables set in the docker-compose.yml file.  The syntax for overriding a .Net app setting with an environment variable is to use __ to separate the json tree levels, so UrlShortenerService.BaseUrl becomes and environment variable named UrlShortenerService__BaseUrl.

Can you tell me the impacted files to undo? Is it all of the yml files in the Openshift folder?

The only files being updated should be inside the docker folder. Everything else should not be modified.

Done, but wondering about the two files in oidc-controller/src? I think they are only for the demo, but wanted to confirm.
Thanks

That doesn't work -- checking why.  On running the demo, I got this error from ngrok:
`Failed to complete tunnel connection
The connection to https://8d4e-96-54-62-211.ngrok.io was successfully tunneled to your ngrok client, but the client failed to establish a connection to the local address localhost:5000.
Make sure that a web service is running on localhost:5000 and that it is a valid address.
The error encountered was: dial tcp [::1]:5000: connect: connection refused`

All good, I think -- I had reverted the ngrok config as well. Trying again.

OK - should be good to go.

Done, but wondering about the two files in oidc-controller/src? I think they are only for the demo, but wanted to confirm.
Thanks

Those can actually be updated, as they are settings used by demo/local development and need to be mapped to the port bound on the host 👍🏻
There will also be projects that will require updating as the port used to communicate with vc-authn on localhost will have changed (e.g.: https://github.com/bcgov/vc-visual-verifier/blob/main/docker/manage#L225).

Updates made.  Started on the vc-visual-verifier changes, but the instructions are a bit lacking there.  Will open an issue on that repo.

Updates made. Started on the vc-visual-verifier changes, but the instructions are a bit lacking there. Will open an issue on that repo.

Looks good to me now! I agree the visual verifier docs could be improved, it was put together a bit rushed and we never got a chance to go back and polish things there.

@swcurran, Another PR got merged before this one.  Could you please rebase these changes?

Done


Test roles are leaking

Iam roles created on automated tests for this repo are not getting properly deleted and are accumulating inside our test AWS account.

I would also like to be able to delete IAM roles, groups, and users since terraform can generate these., it would be handy indeed to nuke them.

Closing this issue as these features have been implemented
IAM service linked roles in release v0.26.0 PR #415
IAM roles in release v0.14.0 PR #330
IAM groups in release v0.21.2 PR #364
IAM users PR #131
See also #116


Style pickling is currently broken

The pickling of styles is currently not working, presumably since we updated HoloViews to support multiple backends. Note that using the regular pickle module, you can still unpickle your data even if the styles aren't correctly restored.
I also propose adding a few pickle files in the tests directory so we can add some unit tests in order to make sure it doesn't break again without us noticing it.

Most of the issues have been addressed in PR #307 (now merged) which involved the style system across backends in general (and not just pickles).
I'll add some unit tests specifically for pickling and then if they pass, I can close this issue.

I've added two fairly extensive unit tests (cross backend) in 987f9071 and they are passing.
With that I can finally close this issue! I'm very pleased that not only is the bug fixed, but we now have the ability to style the same object across backends. I think this could prove very useful!


point at our 'rc' branch

point at any branch you want, so long as it works

Let's see what CI says!


raise DeploymentFailed when all retries fail to redeploy 3bot

Description
raise DeploymentFailed when all retries fail instead of return empty
Related Issues
https://github.com/threefoldtech/js-sdk/issues/2319
Checklist

[ ] Pre-commit hook is installed to do formatting checks before committing code...etc
[ ] Tests included
[ ] Build pass
[ ] Documentation
[ ] Code format and docstrings

Codecov Report

Merging #2324 (13906c1) into development (e44e950) will decrease coverage by 0.47%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           development    #2324      +/-   ##
===============================================
- Coverage        32.45%   31.97%   -0.48%
===============================================
  Files              136      136
  Lines            13173    13378     +205
===============================================
+ Hits              4275     4278       +3
- Misses            8898     9100     +202

Impacted Files
Coverage Δ

...mpscale/packages/threebot_deployer/bottle/utils.py
10.28% <0.00%> (+0.02%)
:arrow_up:

jumpscale/clients/stellar/wrapped.py
37.14% <0.00%> (-8.58%)
:arrow_down:

jumpscale/clients/stellar/stellar.py
14.86% <0.00%> (-7.02%)
:arrow_down:

jumpscale/clients/stellar/__init__.py
23.07% <0.00%> (-6.75%)
:arrow_down:

jumpscale/clients/explorer/workloads.py
24.74% <0.00%> (-2.76%)
:arrow_down:

...ckages/threebot_deployer/chats/restart_threebot.py
36.98% <0.00%> (-2.15%)
:arrow_down:

jumpscale/entry_points/threebot.py
33.53% <0.00%> (-2.07%)
:arrow_down:

jumpscale/clients/explorer/pools.py
38.88% <0.00%> (-1.74%)
:arrow_down:

jumpscale/sals/zos/workloads.py
32.50% <0.00%> (-0.84%)
:arrow_down:

jumpscale/servers/threebot/threebot.py
69.85% <0.00%> (-0.71%)
:arrow_down:

... and 17 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e44e950...13906c1. Read the comment docs.

Codecov Report

Merging #2324 (13906c1) into development (e44e950) will decrease coverage by 0.47%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           development    #2324      +/-   ##
===============================================
- Coverage        32.45%   31.97%   -0.48%
===============================================
  Files              136      136
  Lines            13173    13378     +205
===============================================
+ Hits              4275     4278       +3
- Misses            8898     9100     +202

Impacted Files
Coverage Δ

...mpscale/packages/threebot_deployer/bottle/utils.py
10.28% <0.00%> (+0.02%)
:arrow_up:

jumpscale/clients/stellar/wrapped.py
37.14% <0.00%> (-8.58%)
:arrow_down:

jumpscale/clients/stellar/stellar.py
14.86% <0.00%> (-7.02%)
:arrow_down:

jumpscale/clients/stellar/__init__.py
23.07% <0.00%> (-6.75%)
:arrow_down:

jumpscale/clients/explorer/workloads.py
24.74% <0.00%> (-2.76%)
:arrow_down:

...ckages/threebot_deployer/chats/restart_threebot.py
36.98% <0.00%> (-2.15%)
:arrow_down:

jumpscale/entry_points/threebot.py
33.53% <0.00%> (-2.07%)
:arrow_down:

jumpscale/clients/explorer/pools.py
38.88% <0.00%> (-1.74%)
:arrow_down:

jumpscale/sals/zos/workloads.py
32.50% <0.00%> (-0.84%)
:arrow_down:

jumpscale/servers/threebot/threebot.py
69.85% <0.00%> (-0.71%)
:arrow_down:

... and 17 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e44e950...13906c1. Read the comment docs.


Suggestion:Adding stardust and abyssal pearl value to the examine plugin

I would like to request the addition of the value of stardust and abyssal pearl to the examine plugin,similarly to mark of graces and golden nugget and their byproduct(prospector set and graceful set),by displaying profit gained if the equal amount of stardust/pearl was used to buy the highest gp/per option.
Also,I dont know if the following values are in,since I dont have any of those at the moment,and they came after marks of graces and golden nuggets,but if its not already the case, Id like to request the same for mermaid tears and unidentified minerals,and any other untradeable currency that can be used to buy tradeable items that doesnt behave like marks or nuggets at the moment
(Collecting untradeable currencies and it would be nice to keep track of their worth if they were to be used in their respecive shops)

Stardust has the problem of being worth 1/10 of a soft clay, something which the mapping system does not support currently.
Abyssal Pearls do not have a good common trade as far as I can tell, though in any case every one of them is also a relationship of fractions.


"Hold Shift key to activate zone when dragging" not working on version 0.35 / 0.36 / 0.37 (for extended display)

Microsoft PowerToys version
0.35 / 0.36 / 0.37
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
"Hold the Shift key to activate zone when dragging" not working on version 0.35 / 0.36 / 0.37.
The issue applies to the system when there's 2 extended display/screen.
The last working version is 0.33.1 in regards to this issue.
✔ Expected Behavior
when holding the shift key and dragging, the system with an extended display will be shown the zone to activate.
❌ Actual Behavior
Activa Zone never appear when holding the shift key and dragging. nothing has happened.
Other Software
No response

@syteoh88
do you have a layout assigned to the other monitor(s)?

yeap， i have 3 screen with different layout.
On Wed, 12 May 2021, 14:46 Enrico Giordani, @.***>
wrote:

@syteoh88 https://github.com/syteoh88
do you have a layout assigned to the other monitor(s)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/11171#issuecomment-839509297,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUACRTHVWZFWFXMGKUDXOULTNIP4JANCNFSM44OP2JYA
.

@syteoh88
run the Report Bug command and upload the zip file

PowerToysReport_2021-05-16-08-19-48.zip
Report-Bug zip file uploaded

looks like we need to add more logging to FZ @SeraphimaZ?

The issue was reopened as https://github.com/microsoft/PowerToys/issues/13958


🗳 VOTE: Bootstrap Technical Steering Committee

As agreed at the project meeting on April 14 and discussed before on Slack, we want to proceed with the Technical Steering Committee entity and with appointing the bootstrap members.
Proposal for voting:

Approve the Technical Steering Proposal https://github.com/open-feature/community/pull/46. As agreed at the meeting, we can extend the committee later as needed
Appoint the bootstrap technical steering committee

Todd Baert, Dynatrace
Steve Arch, CloudBees
Dan O’Brien, LaunchDarkly

Please vote 👍/👎 in this issue or comment below. Any community member can vote.

all connected issues and PRs are closed


Inplace versions of MPRK43 & Tests

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.96%.
Additional details and impacted files
@@             Coverage Diff             @@
##             main      #79       +/-   ##
===========================================
- Coverage   97.88%   85.96%   -11.92%
===========================================
  Files           4        4
  Lines         567      627       +60
===========================================
- Hits          555      539       -16
- Misses         12       88       +76

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Thanks a lot for this clarification! I'll remove the copy.


Keeping Content from Breaking

Is there an option to prevent page breaking on elements? e.g.
page-break-after: auto;
page-break-inside: avoid;
page-break-before: auto;
Generated output does not take the css into consideration and the page will break.

page-break-*  instructions should work if CSS selector is 'Word-friendly' and CSS styles are either inlined in element tag or specified in <style> tag in document's header'. Pls share you html example together with styles for more info.

It appears as though word will not calculate automatic page breaks. You can use

To force a break and that works but it does not seem allow any element other than the "br" tag to use page breaks.

Damn @jarodknoten's workaround no longer seems to work :(
Anyone know how to do this these days?


Addition of the GPU Activity Agent to steer GPU frequency based upon GPU Compute Activity

Fixes #1906

Fixes #1908

Relies upon changes made in PR #1914 #1917 #1945 and should not be integrated prior to review those PRs

Agent operates best when using Fefficient information obtained from GPU frequency sweeps.  Experiments providing GPU frequency sweeps through the integration infrastructure are introduced in PR #2024, #2031.  These may rely upon PR #2010

This PR introduces an agent that modulates the GPU frequency within a set of user specified bounds based upon the GPU_COMPUTE_ACTIVITY signal.  For NVIDIA systems this is the SM_ACTIVE signal.  The user may also provide an optional input 'phi' which can bias the agents frequency selection towards energy efficiency (phi of 1.0) or performance (phi of 0.0).  The default behavior if phi = 0.5
Primary changes:

addition of GEOPM_CXX_MAN_GPUActivityAgent.3.rst
addition of geopm_agent_gpu_activity.7.rst
src/GPUActivityAgent.cpp
src/GPUActivityAgent.hpp
test/GPUActivityAgentTest.cpp
integration/experiment/energy_efficiency/Makefile.mk
integration/experiment/energy_efficiency/gpu_activity.py
integration/experiment/energy_efficiency/run_gpu_activity_parres_dgemm.py
integration/experiment/energy_efficiency/run_gpu_activity_parres_nstream.py
integration/frequency_sweep/gen_gpu_activity_policy_recommendation.py

Additional tasks to consider:

[x] Integration tests based upon the run_gpu_activity_parress_dgemm/stream.py files
[x] Experiment scripts to find the Fe (freq_efficient) policy input based upon the GPU frequency sweep of parres dgemm
[x] Experiment script updates (energy_efficiency/gpu_activity.py) to automatically provide the 'optimal' config instead of a simple phi sweep with default HPE sx40 values.

Latest updates include a SAMPLE_PERIOD policy value that allows the end user to specify sample period/wait time.  This should help address any control loop timing issues that stem from vastly different GPU counts or GPU signal & control access time varying from system to system.

[ ] Add info on system characterization to docs (what workload, how, etc)
[ ] Add info on generating policy
[ ] JSON policy requires double quotes for gen_pol*


Add support for dataState parameter

Hi,
First of all, thank you for the amazing work with this library. A huge time-saver!
I wondered if support for the new (optional) parameter dataState (see https://developers.google.com/webmaster-tools/search-console-api-original/v3/searchanalytics/query) could be added to the query function.
It has been added in December in Google's documentation and If the value is equal to "all" (case-insensitive), data will include fresh data (vs only finalized data if the parameter is not specified).
Thanks!

Thanks @antoineeripret - I didn't know about this!
Would you like to have a go at implementing it yourself? I'm happy to answer any questions and review your PR.
I think the implementation should be pretty simple. A good reference would be how search_type can be set here.

Great @joshcarty.
I'll create it now. As you mentioned, the implementation should be simple so I may be able to do it :)

Solved in #34


Why all dialogs do not work on tablets? Is this a bug or can you fix it? [VERY IMPORTANT]

Why all dialogs do not work on tablets? Is this a bug or can you fix it? [Displayed on ipad]

It works for me

@volkanceylan  It works, but the components do not fit properly on the page.


Auth/Backend/Apache: We did not receive the $_SERVER[REMOTE_USER] property ...

Hi,
I installed SabreDAV 2.0.5 and setup Basic Auth in my .htaccess and https. Also I put the code for using the Apache auth backend into my server.php (according to the getting started documentation).
Accessing the page via browser I get the error message:
We did not receive the $_SERVER[REMOTE_USER] property. This means that apache might have been misconfigured.
This exception is thrown in Backend/Apache.php if getRawServerValue('REMOTE_USER') gives no results. I checked $_SERVER and there was no REMOTE_USER but there is a REDIRECT_REMOTE_USER. I don't know why there is a redirect.
Using this variable it works.
knut

some more info:
according to the PHP manual
http://php.net/manual/en/reserved.variables.server.php
the proper variable seems to be PHP_AUTH_USER

PHP_AUTH_USER doesn't work for every SAPI. It mainly works with Apache + mod_php. However, if PHP_AUTH_USER is set it will be picked up by the plugins.


Option for adding your own WCL API Key?

I understand the issue regarding the fact that WCL didn't want the parse data exposed for free.
It could be a nice feature to allow for adding your personal API key, so we can retrieve people's parses.

You can, but it's currently not updated for TOGC stuff - Parses are still shown for Ulduar.
https://github.com/ForsakenNGS/LogTrackerApp


Typescript extension

Issue Type: Bug
Keeps saying every 5 times in the last 5 minutes Typescript and Javascript Language Feature died. For no reason. I am using Jest, express, nodemon and yarn with some basic tests on.
VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:27:22.494Z)
OS version: Linux x64 4.9.0-9-amd64

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz (4 x 1999)

GPU Status
2d_canvas: unavailable_softwareflash_3d: disabled_softwareflash_stage3d: disabled_softwareflash_stage3d_baseline: disabled_softwaregpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: disabled_offrasterization: disabled_softwareskia_renderer: disabled_off_okvideo_decode: disabled_softwareviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: unavailable_softwarewebgl2: unavailable_software

Load (avg)
5, 7, 4

Memory (System)
3.85GB (0.35GB free)

Process Argv
desafio-conceitos-node --no-sandbox

Screen Reader
no

VM
0%

DESKTOP_SESSION
lightdm-xsession

XDG_CURRENT_DESKTOP
XFCE

XDG_SESSION_DESKTOP
lightdm-xsession

XDG_SESSION_TYPE
x11

Extensions (10)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.1.5

prettier-vscode
esb
5.1.0

debugger-for-chrome
msj
4.12.8

vscode-jest
Ort
3.2.0

material-icon-theme
PKi
4.2.0

vscode-xml
red
0.12.0

LiveServer
rit
5.6.1

vscode-stylelint
sty
0.84.0

sass-indented
syl
1.8.6

vscode-wakatime
Wak
4.0.0

(1 theme extensions excluded)

/needsMoreInfo are you able to update to the current release, 1.46.1 and retest? If the problem remains please use Command Palette to reload with all extensions disabled and see if the problem still occurs.

/needsMoreInfo are you able to update to the current release, 1.46.1 and retest? If the problem remains please use Command Palette to reload with all extensions disabled and see if the problem still occurs.

Hello, thanks for the reply. Ok. What other info do you need? 2) Seems the issue is gone after I've disable all extensions and enable all after it.


Raise error if backend retrieved not in current instance

Summary
In the following scenario where an instance is passed in at initialization and a backend that is not in that instance is retrieved (but the user has access to in a different instance), we should raise an error instead of silently switching to a different instance.
service = QiskitRuntimeService(channel="ibm_quantum", instance="hgp1")
backend = service.get_backend("ibm_algiers")
# algiers is not in hgp1 but in a different instance the user has access to

We should also return a more informative error message - for example:
QiskitBackendNotFoundError: "Backend ibm_algiers is not in {hgp}.
Please try a different instance. ibm_algiers is in the following instances you have access to:
['hgp', 'hgp', 'hgp']"

Details and comments
Fixes #1246

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 46.438%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
2327

Relevant Lines:
5011

💛  - Coveralls

Does this really fix #1246? My interpretation of #1246 is that the retrieve backend doesn't have the right h/g/p, when it's accessible via multiple instances.

Does this really fix #1246? My interpretation of #1246 is that the retrieve backend doesn't have the right h/g/p, when it's accessible via multiple instances.

Discussed with @blakejohnson on slack - in his scenario, the backend (ibm_algiers) was not actually in hgp1 so the backend was retrieved from a different instance. This was confusing because the provider just silently chooses the different instance that has access to the backend. When this happens, I think we should raise an error.
If an instance is passed in at initialization, retrieving a backend will always use that instance if the backend is actually in it.
So yes, this doesn't actually fix #1246 because it's not actually a bug - this adds a helpful error message.

I am a bit confused about what this fix will do. If the user has several hgp accounts, then I think that for each of them that does not have the specified backend, an error will be issued. But perhaps I am mistaken. Perhaps a test would be helpful to demonstrate this. Also, the phrasing of the release note is cumbersome.

This behavior already existed - if a user did something like this, we raise an error since even though the user has access to ibm_torino, it is not in ibm-q/open/main.
service.backend('ibm_torino', instance='ibm-q/open/main')

This PR makes it so the same error will be raised if an instance is passed in at initialization:
service = QiskitRuntimeService(channel="ibm_quantum", instance="ibm-q/open/main")
service.backend('ibm_torino')

I'll try to add a test and update the release note to make it more clear


multidim groupby on dask arrays: dask.array.reshape error

If I try to run a groupby operation using a multidimensional group, I get an error from dask about "dask.array.reshape requires that reshaped dimensions after the first contain at most one chunk".
This error is arises with dask 0.11.0 but NOT dask 0.8.0.
Consider the following test example:
import dask.array as da
import xarray as xr

nz, ny, nx = (10,20,30)
data = da.ones((nz,ny,nx), chunks=(5,ny,nx))
coord_2d = da.random.random((ny,nx), chunks=(ny,nx))>0.5
ds = xr.Dataset({'thedata': (('z','y','x'), data)},
                coords={'thegroup': (('y','x'), coord_2d)})
# this works fine
ds.thedata.groupby('thegroup')

Now I rechunk one of the later dimensions and group again:
ds.chunk({'x': 5}).thedata.groupby('thegroup')

This raises the following error and stack trace
ValueError                                Traceback (most recent call last)
<ipython-input-16-1b0095ee24a0> in <module>()
----> 1 ds.chunk({'x': 5}).thedata.groupby('thegroup')

/Users/rpa/RND/open_source/xray/xarray/core/common.pyc in groupby(self, group, squeeze)
    343         if isinstance(group, basestring):
    344             group = self[group]
--> 345         return self.groupby_cls(self, group, squeeze=squeeze)
    346
    347     def groupby_bins(self, group, bins, right=True, labels=None, precision=3,

/Users/rpa/RND/open_source/xray/xarray/core/groupby.pyc in __init__(self, obj, group, squeeze, grouper, bins, cut_kwargs)
    170             # the copy is necessary here, otherwise read only array raises error
    171             # in pandas: https://github.com/pydata/pandas/issues/12813>
--> 172             group = group.stack(**{stacked_dim_name: orig_dims}).copy()
    173             obj = obj.stack(**{stacked_dim_name: orig_dims})
    174             self._stacked_dim = stacked_dim_name

/Users/rpa/RND/open_source/xray/xarray/core/dataarray.pyc in stack(self, **dimensions)
    857         DataArray.unstack
    858         """
--> 859         ds = self._to_temp_dataset().stack(**dimensions)
    860         return self._from_temp_dataset(ds)
    861

/Users/rpa/RND/open_source/xray/xarray/core/dataset.pyc in stack(self, **dimensions)
   1359         result = self
   1360         for new_dim, dims in dimensions.items():
-> 1361             result = result._stack_once(dims, new_dim)
   1362         return result
   1363

/Users/rpa/RND/open_source/xray/xarray/core/dataset.pyc in _stack_once(self, dims, new_dim)
   1322                     shape = [self.dims[d] for d in vdims]
   1323                     exp_var = var.expand_dims(vdims, shape)
-> 1324                     stacked_var = exp_var.stack(**{new_dim: dims})
   1325                     variables[name] = stacked_var
   1326                 else:

/Users/rpa/RND/open_source/xray/xarray/core/variable.pyc in stack(self, **dimensions)
    801         result = self
    802         for new_dim, dims in dimensions.items():
--> 803             result = result._stack_once(dims, new_dim)
    804         return result
    805

/Users/rpa/RND/open_source/xray/xarray/core/variable.pyc in _stack_once(self, dims, new_dim)
    771
    772         new_shape = reordered.shape[:len(other_dims)] + (-1,)
--> 773         new_data = reordered.data.reshape(new_shape)
    774         new_dims = reordered.dims[:len(other_dims)] + (new_dim,)
    775

/Users/rpa/anaconda/lib/python2.7/site-packages/dask/array/core.pyc in reshape(self, *shape)
   1101         if len(shape) == 1 and not isinstance(shape[0], Number):
   1102             shape = shape[0]
-> 1103         return reshape(self, shape)
   1104
   1105     @wraps(topk)

/Users/rpa/anaconda/lib/python2.7/site-packages/dask/array/core.pyc in reshape(array, shape)
   2585
   2586     if any(len(c) != 1 for c in array.chunks[ndim_same+1:]):
-> 2587         raise ValueError('dask.array.reshape requires that reshaped '
   2588                          'dimensions after the first contain at most one chunk')
   2589

ValueError: dask.array.reshape requires that reshaped dimensions after the first contain at most one chunk

I am using the latest xarray master and dask version 0.11.0. Note that the example works fine if I use an earlier version of dask (e.g. 0.8.0, the only other one I tested.) This suggests an upstream issue with dask, but I wanted to bring it up here first.

This was an intentional change -- see https://github.com/dask/dask/pull/1469
Previously, we created lots of teeny tasks, which tended to negate any out of core benefits. The problem is that reshape promises an order to the elements it reshape which tends to split across existing chunks of dask arrays.
We could work around this in xarray by adding custom logic to stack for keeping chunks together when reshaping, but we can't do this upstream in dask because we need to make sure we keep all the arrays aligned.

We could work around this in xarray by adding custom logic to stack for keeping chunks together when reshaping

If you give me a few hints about how to approach this, I can try a PR. I need this rather urgently for an ongoing project.

It would look something like this:

Verify that chunks are the same on all dask arrays to be stacked.
Use np.ravel with map_blocks to flatten each block independently.
Construct the appropriate (non-sorted) MultiIndex to label the flattened elements.

Hi @rabernat and @shoyer
I have come across same issue while re-running some old code now uxing xarray 0.9.1 / dask 0.11.0. Was there any workaround or solution?
Issue occurs for me when trying to unstack 'allpoints', e.g.
mle = stacked.dis.groupby('allpoints').apply(combogev)
dsmle = mle.unstack('allpoints')

Thanks

@byersiiasa can you share what stacked.dis looks like?

<xarray.DataArray 'dis' (time: 30, allpoints: 259200)>
array([[  9.969210e+36,   9.969210e+36,   9.969210e+36, ...,   9.969210e+36,
          9.969210e+36,   9.969210e+36],
       [  9.969210e+36,   9.969210e+36,   9.969210e+36, ...,   9.969210e+36,
          9.969210e+36,   9.969210e+36],
       [  9.969210e+36,   9.969210e+36,   9.969210e+36, ...,   9.969210e+36,
          9.969210e+36,   9.969210e+36],
       ...,
       [  9.969210e+36,   9.969210e+36,   9.969210e+36, ...,   9.969210e+36,
          9.969210e+36,   9.969210e+36],
       [  9.969210e+36,   9.969210e+36,   9.969210e+36, ...,   9.969210e+36,
          9.969210e+36,   9.969210e+36],
       [  9.969210e+36,   9.969210e+36,   9.969210e+36, ...,   9.969210e+36,
          9.969210e+36,   9.969210e+36]])
Coordinates:
  * time       (time) datetime64[ns] 1971-01-01 1972-01-01 1973-01-01 ...
  * allpoints  (allpoints) MultiIndex
  - lon        (allpoints) float64 -179.8 -179.8 -179.8 -179.8 -179.8 -179.8 ...
  - lat        (allpoints) float64 89.75 89.25 88.75 88.25 87.75 87.25 86.75 ...

That array is loaded in numpy already - can you share the dask version?
On Mon, Mar 13, 2017 at 2:57 AM byersiiasa<EMAIL_ADDRESS>wrote:

<xarray.DataArray 'dis' (time: 30, allpoints: 259200)>
array([[  9.969210e+36,   9.969210e+36,   9.969210e+36, ...,   9.969210e+36,
9.969210e+36,   9.969210e+36],
[  9.969210e+36,   9.969210e+36,   9.969210e+36, ...,   9.969210e+36,
9.969210e+36,   9.969210e+36],
[  9.969210e+36,   9.969210e+36,   9.969210e+36, ...,   9.969210e+36,
9.969210e+36,   9.969210e+36],
...,
[  9.969210e+36,   9.969210e+36,   9.969210e+36, ...,   9.969210e+36,
9.969210e+36,   9.969210e+36],
[  9.969210e+36,   9.969210e+36,   9.969210e+36, ...,   9.969210e+36,
9.969210e+36,   9.969210e+36],
[  9.969210e+36,   9.969210e+36,   9.969210e+36, ...,   9.969210e+36,
9.969210e+36,   9.969210e+36]])
Coordinates:

time       (time) datetime64[ns] 1971-01-01 1972-01-01 1973-01-01 ...
allpoints  (allpoints) MultiIndex

lon        (allpoints) float64 -179.8 -179.8 -179.8 -179.8 -179.8 -179.8 ...
lat        (allpoints) float64 89.75 89.25 88.75 88.25 87.75 87.25 86.75 ...

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pydata/xarray/issues/1026#issuecomment-286062113, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABKS1pd_uTiUQLRXjBhR7D06uvkkKJBDks5rlRLxgaJpZM4KMB0C
.

I have been re-running that script  you helped me with in Google groups:
https://groups.google.com/forum/#!searchin/xarray/combogev|sort:relevance/xarray/nfNh40Zt3sU/WfhavtXgCAAJ
do you mean the delayed object from within the function?
perhaps <bound method Array.visualize of dask.array<from-va..., shape=(11L,), dtype=float64, chunksize=(11L,)>>
or perhaps
Delayed('fit-3767d9ad6cfa517555b5800b3b5f4e41')
I am going to keep trying with different versions of dask since this 0.9.0 doesn't seem to behave it did previously.

@byersiiasa What matters for dask's reshape is the array shape and chunk shape, all of which you should see when you print a dask.array (or xarray.DataArray containing one). What is the size of the chunking along time and allpoints?

So, not sure if this is helpful but I'll leave these notes here just in case.

0.11.0 - similar problem to @rabernat above
- 0.10.1 - seems to work fine for what I wanted  (delayed)
0.9.0 - appeared to work ok, but actually I'm not convinced it was parallelising the tasks. And also resulted in massive memory issues
0.14.0 - another problem, can't remember what but issue to do with delayed I think.

@shoyer No chunking as the dataset was quite small (360x720x30).  Also, the calculation is along the time dimension so this effectively disappears for each lat/lon. Hence initial surprise why it was coming up with this chunk/reshape issue since I thought all it has to do is unstack 'allpoints'
If I print one of the dask arrays from within the function
print sT
dask.array<from-va..., shape=(11L,), dtype=float64, chunksize=(11L,)>

This is 11L because the calculation returns 11 values per point to an xr.Dataset.
Others have no chunks because they are single values (for each point)
print p_value
dask.array<from-va..., shape=(), dtype=float64, chunksize=()>

Only returns one value per point
The object returned (xr.Dataset) from the .apply function comes out with chunks:
mle.chunks  Frozen(SortedKeysDict({'allpoints': (1, 1, 1, 1, 1......(allpoints)....., 1, 1), 'T': (11L,)}))
and looks like:
<xarray.Dataset>
Dimensions:            (T: 11, allpoints: 259200)
Coordinates:
  * T                  (T) int32 1 5 10 15 20 25 30 40 50 75 100
  * allpoints          (allpoints) MultiIndex
  - allpoints_level_0  (allpoints) float64 40.25 40.25 40.25 40.25 40.25 ...
  - allpoints_level_1  (allpoints) float64 22.75 23.25 23.75 24.25 24.75 ...
Data variables:
    xi                 (allpoints) float64 -0.6906 -0.6906 -0.6906 -0.6906 ...
    mu                 (allpoints) float64 9.969e+36 9.969e+36 9.969e+36 ...
    sT            (allpoints, T) float64 9.969e+36 9.969e+36 9.969e+36 ...
    KS_p_value         (allpoints) float64 3.8e-12 3.8e-12 3.8e-12 3.8e-12 ...
    sigma              (allpoints) float64 5.297e-24 5.297e-24 5.297e-24 ...
    KS_statistic       (allpoints) float64 0.6321 0.6321 0.6321 0.6321 ...

This is what I was looking for:

Frozen(SortedKeysDict({'allpoints': (1, 1, 1, 1, 1......(allpoints)....., 1, 1), 'T': (11L,)}))

So in this case (where the chunk size is already 1), dask.array.reshape could actually work fine and the error is unnecessary (we don't have the exploding task issue). So this could potentially be fixed upstream in dask.
For now, the best work-around (because you don't have any memory concerns) is to "rechunk" into a single block along the last axis before reshaping, e.g., .chunk(allpoints=259200) or .chunk(allpoints=1e9) (or something arbitrarily large).

Thanks - this is working well.
Reverting back to xarray 0.8.2 and dask 0.10.1 seems to be a combination that worked well for this particular task using delayed.

Fixed upstream, I think, in https://github.com/dask/dask/pull/2089

(along with now supporting many other reshape options)

We should check if this issue is resolved.

Indeed, it looks like this works now. Extending the example from the first post:
In [3]: ds.chunk({'x': 5}).thedata.groupby('thegroup').mean()
Out[3]:
<xarray.DataArray 'thedata' (thegroup: 2)>
dask.array<shape=(2,), dtype=float64, chunksize=(1,)>
Coordinates:
  * thegroup  (thegroup) object False True


Password-protect the app

*If your proposal is more a rough idea than a precise description of a feature, please consider starting a discussion instead: https://github.com/ransome1/sleek/discussions
Please only continue the feature request if you have a precise idea of what you're asking for and if you can provide specific details, use cases or examples.
Did you check if a similar feature request has already been reported?
Yes. I did.
Is your feature request related to a problem? Please describe.
Currently, sleek can be opened by anyone.
Describe the solution you'd like
I use sleek at work. I don't like people checking my tasks. So I think sleek should be password protected. That's my suggestion.
Describe alternatives you've considered
I'm running sleek from an usb drive using BitLocker.

Should the text be scrambled too?
just a thought

Hi @g3434343,
a password protection of sleek would only protect the GUI of the app but your todo.txt on your USB drive would still be unprotected (unless the content of the file would be encrypted). Encrypting the todo.txt would not be a solution for me as I use a different app than sleek on my Smartphone. This app would need to support the same encryption method.

I agree with @befedi  -- encrypting the todo.txt file itself is against all the principles of the format,
and encrypting the app only is pointless.
If people want encrypted data then they encrypt the file storage device itself (with Veracrypt or similar).

I agree with the above said, if the file is located locally. And if sleek would encrypt the file as well, it would be useless to other apps. Though an interesting use case could be if sleek had an API integration to a cloud service where the todo.txt file would be hosted and never duplicated to the local file system. I am not sure though if many todo.txt users would be interested in pushing their todo data into a popular cloud that is no self hosted.

RClone would provide a good free mechanism for synching a file (via an encrypted cloud mechanism). Cryptomator is another possibility. Sleek needs to do what it does best and leave other things to the systems that do that best.
I think we have to assume that Sleek is for people who are at least slight geeks and at least slightly sophisticated as a basis for good development.


deno: 1.13.1 -> 1.13.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for deno is: "A secure runtime for JavaScript and TypeScript"
meta.homepage for deno is: "https://deno.land/"
meta.changelog for deno is: "https://github.com/denoland/deno/releases/tag/v1.13.2"
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/0b0xmz6lvfky96alzg96zqds4d4yr82b-deno-1.13.2/bin/deno passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 1.13.2 with grep in /nix/store/0b0xmz6lvfky96alzg96zqds4d4yr82b-deno-1.13.2

found 1.13.2 in filename of file in /nix/store/0b0xmz6lvfky96alzg96zqds4d4yr82b-deno-1.13.2

directory tree listing: https://gist.github.com/adae26aa545be31f8b6e9225092d07b8

du listing: https://gist.github.com/10eaeba03971ba585ab5b20427403332

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
deno

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0b0xmz6lvfky96alzg96zqds4d4yr82b-deno-1.13.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A deno https://github.com/r-ryantm/nixpkgs/archive/bd51f857d8450becb1e69a38764bd6ff28f29da9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0b0xmz6lvfky96alzg96zqds4d4yr82b-deno-1.13.2
ls -la /nix/store/0b0xmz6lvfky96alzg96zqds4d4yr82b-deno-1.13.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

deno

Maintainer pings
cc @06kellyjac for testing.

Result of nixpkgs-review pr 135498 run on x86_64-linux 1

1 package built:

deno


Remove deprecated code and deprecate int compression

Describe your changes
Remove previously deprecated code, listed in #1236
Deprecate  https://github.com/TomographicImaging/CIL/issues/1408
Describe any testing you have performed
Please add any demo scripts to CIL-Demos/misc/
Link relevant issues
Closes #1236
Closes https://github.com/TomographicImaging/CIL/issues/1408
Checklist when you are ready to request a review

[ ] I have performed a self-review of my code
[ ] I have added docstrings in line with the guidance in the developer guide
[ ] I have implemented unit tests that cover any new or modified functionality
[ ] CHANGELOG.md has been updated with any functionality change
[ ] Request review from all relevant developers
[ ] Change pull request label to 'Waiting for review'

Contribution Notes
Please read and adhere to the developer guide and local patterns and conventions.

[x] The content of this Pull Request (the Contribution) is intentionally submitted for inclusion in CIL (the Work) under the terms and conditions of the Apache-2.0 License.
[x] I confirm that the contribution does not violate any intellectual property rights of third parties

After https://github.com/TomographicImaging/CIL/pull/1431 is merged I will need to update this PR


[We See a Way] - Home Page Design -CTA Action - component

bkground color and text color configurable(2/3 - 1/3)

Figma desing link :

this has been implemented on home page.
https://main--danaher-ls-aem--hlxsites.hlx.page/us/en/we-see-a-way


about queue len

file:go/discovery/queue.go
code:
// QueueLen returns the length of the queue (channel size + queued size)
func (q *Queue) QueueLen() int {
  q.Lock()
  defer q.Unlock()

  return len(q.queue) + len(q.queuedKeys)
}

I am confused about the calculation of the queue length.
q.queue and q.queuedKeys are the same.
Is there double counting here?
Thank you!
@MOON-CLJ

cc @sjmudd who authored this code.

@shlomi-noach @sjmudd any update? It obviously feels like a bug.

This is code that's been around for a long time but after looking again I think I would agree.  I will modify this however to reflect the complete length of the discovery queue. That is both the pending (queued) plus being processed (consumed) entries as that is the total size.
However, this does lead me to realise that in many cases it's interesting to see these 2 values separately as what's being processed has a hard limit config.Config.DiscoveryQueueCapacity and it's not currently possible to see the split here.
So prior to making any changes I wonder what you were looking for and whether you might be interested in monitoring these to map lengths separately or not?

@sjmudd separation's good.

@MOON-CLJ: thanks for catching this. I've made a PR which I think should address the issue.


Update PaymentProperties.cs

Removed dependency to ucommerce, moved methods into class, should fix this issue: http://eureka.ucommerce.net/#!/question/2314/QuickpayV10-issues-on-uCommerce-77017130

Håber det går godt Bjørn :)

It was more places than one, I'll move them all


train problem

when i run ex_audioset.py, there is a problem:
in line 111 :   x,f,y,i=batch
problem:  not enough values to unpack(expected4, got3)
I think the value i dose not have a value and I want to know how to use the teacher preds.
Thanks!

Hi! batch should be a tuple of 4 elements: the waveform (x), the filename (f), the label (y), and the index (i). The index is added as long as you don't call the function get_full_training_set with add_index=False.
However, I have recently added a file fname_to_index.pkl that contains a python dict for converting the filename to the respective index position in the numpy array that stores the predictions. As long as you have the latest version of the code in this repo, this new version should be used automatically.

OK, Thanks! I will update the code.


Query caching and prepared statements for SPARQL

This change lets you put a parameter map into the executeSparql() call, which binds variables to values. This is akin to prepared statements in SQL.
Query parsing is expensive. On our workload, this yields a 44% speedup.

Argh, this is now pulling in other stuff. I'll close this and recreate it separately.


Generalize macro expansion for macros written as attributes

Add 'attributed' trait for nodes that can have attributes, and use it to generalize macro expansion for macros written as attributes.

@swift-ci please test

@swift-ci please test


AutoFixture.NUnit2 broken: missing reference to nunit.core.interfaces

The AutoFixture.NUnit2 NuGet package does not work out of the box - it does not ship the nunit.core.interfaces assembly required for the provided LocalAddIn class to compile, nor add it as a reference to the test project to which the package is added.
Furthermore, having added this reference manually to my test project, I find that the tests still fail to run in the ReSharper test runner and in NCrunch, albeit with (seemingly) different reasons. In ReSharper, the tests decorated with the AutoDataAttribute are automatically ignored with the message "No arguments were provided", and in NCrunch the project fails to compile with the following error:
An error occurred while analysing this project after it was built: System.InvalidCastException: Unable to cast object of type 'MyTestProject.LocalAddin' to type 'NUnit.Core.Extensibility.IAddin'.
   at NUnit.Core.CoreExtensions.InstallAddin(Type type)
   at NUnit.Core.CoreExtensions.InstallAdhocExtensions(Assembly assembly)
   at NUnit.Core.Builders.TestAssemblyBuilder.Load(String path)
   at NUnit.Core.Builders.TestAssemblyBuilder.Build(String assemblyName, Boolean autoSuites)
   at NUnit.Core.Builders.TestAssemblyBuilder.Build(String assemblyName, String testName, Boolean autoSuites)
   at NUnit.Core.TestSuiteBuilder.Build(TestPackage package)
   at nCrunch.TestExecution.Frameworks.NUnit.NUnitDynamicTestFinder.FindFrameworkTestsUsingRuntimeInvoke(TestPackage package, ILogger logger, List`1 tests)
   at nCrunch.TestExecution.Frameworks.NUnit.NUnitTestFramework.FindFrameworkTestsInAssembly(ReflectedAssembly assembly, FilePath assemblyFilePath, IList`1 referencedAssemblyFilePaths)
   at nCrunch.TestExecution.TestFinder.FindTestsForFrameworks(ReflectedAssembly assembly, FilePath assemblyFilePath, IList`1 referencedAssemblyFilePaths, TestFrameworkDescription[] frameworks)
   at nCrunch.TestExecution.RemoteTaskRunner.AnalyseAssembly(TestFrameworkDescription[] applicableFrameworks)

This compilation error is in spite of the fact that the LocalAddIn class derives from Ploeh.AutoFixture.NUnit2.Addins.Addin, which does implement NUnit.Core.Extensibility.IAddin, and the containing assembly is shipped with the NuGet package and referenced from my test project.

Just ran into this issue myself. To summarize, in order for AutoFixture to work with R# 8.2.3 you must:

Reference NUnit 2.6.3 in the test assembly (or R# won't find the Addin)
Add binding redirects (or AutoFixture will be unhappy). Not sure if both core and core.interfaces are needed?

      <dependentAssembly>
        <assemblyIdentity name="nunit.core.interfaces" publicKeyToken="96d09a1eb7f44a77" culture="neutral" />
        <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>83" newVersion="<IP_ADDRESS>83" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="nunit.core" publicKeyToken="96d09a1eb7f44a77" culture="neutral" />
        <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>83" newVersion="<IP_ADDRESS>83" />
      </dependentAssembly>

I've filed https://youtrack.jetbrains.com/issue/RSRP-432554 to see what they have to say about this.


Allow log level to be set and filtering logs accordingly

Checklist

[x] make test-all (UNIX) passes. CI will also test this
[ ] unit and/or integration tests are included (if applicable)
[x] documentation is changed or added (if applicable)

Description of change
Some of the goss default logging messages might be seen as not very useful. This fix allow easy log level customisation and filtering

I haven't had a chance to go through this PR in depth, but this was a much needed feature. Many thanks for taking the time to add this!
The main thing I'll be reviewing is making sure this PR and #576 don't have major conflicts.

@aelsabbahy no pb, many thanks to you for the great work

One of these days I need to fork the go-lang code and run code climate on it. Very curious what the results would be.

Which function was failing?

Which function was failing?

strangely the error was triggered by my changes in Validate but seems like other functions also had this issue without failing see this link

Took this for a spin, it's a very nice change that greatly improves debugging and can be built upon. The only thing that needs to change is that INFO is too noisy/chatty as a default.

Oh, and I think a small writeup on the log-levels and when they should be used would be nice, but that can be a separate PR/improvement.

Took this for a spin, it's a very nice change that greatly improves debugging and can be built upon. The only thing that needs to change is that INFO is too noisy/chatty as a default.

Understood and agreed will do the change soon (after rebased on v0.3.14)

Oh, and I think a small writeup on the log-levels and when they should be used would be nice, but that can be a separate PR/improvement.

Will do too

Done with additional documentation. @aelsabbahy however, after doing so, I do not understand why you find INFO too verbose, may be just changing the default logging level to WARN instead of INFO would better match your thoughts

@aelsabbahy done rebasing on latest master
Do you think you'll merge this in some future version please ?

$ goss v
2020/11/25 11:04:33 Setting log level to WARN
........

Total Duration: 0.002s
Count: 8, Failed: 0, Skipped: 0

@aelsabbahy got it, will have a look at this later this week. Many thanks for making this way clearer

https://dave.cheney.net/2015/11/05/lets-talk-about-logging
This might not be a bad approach. Split logging into just two levels that are both disabled by default.. INFO and DEBUG.
Can use INFO to help users get more info regarding goss and DEBUG for more developer level debugging. But I'm open to suggestions.

@aelsabbahy finally got some time to rework on this. Could you please check that the new code fullfill your requirements
I also tried to understand why the CI is failing on OSX but I do not see why brew install bash is failing. Many thanks in advance

@aelsabbahy finally got some time to rework on this. Could you please check that the new code fullfill your requirements
I also tried to understand why the CI is failing on OSX but I do not see why brew install bash is failing. Many thanks in advance

@aelsabbahy finally found a way to fix OSX CI by building bash homebrew formula from source. Currently trying another option

@aelsabbahy finally found a way to fix OSX CI by building bash homebrew formula from source. Currently trying another option

@aelsabbahy both solutions work, only keeping the binary HomeBrew formula version

@aelsabbahy both solutions work, only keeping the binary HomeBrew formula version

@aelsabbahy any chance you could review and possibly integrate this soon please ?

@aelsabbahy any chance you could review and possibly integrate this soon please ?

Is there a plan to revive this PR. I'm interested in this feature.

@sebinjohn unfortunately looking at #699 and #713 the only possibility for you is to fork this PR to use it (BTW this is already what we are doing on our side for quite some time)
We were considering maintaining our own supported fork but this is completely non possible for our team at this point in time

It's unfortunate, because now there is also a sever security vulnerablity in runc that this package depends on, it's likely we will have no choice but to maintain a fork :( @obourdon @sebinjohn

@obourdon  thanks for the info.  I will look into forking further.

@sebinjohn see PR https://github.com/goss-org/goss/pull/802


[Bug]: Documentation - Web service doc - 1st parameter - execute or service?

Apache Hop version?
2.6
Java version?
N/A
Operating system
Other
What happened?
In the documentation for both Web Service (https://hop.apache.org/manual/latest/hop-server/web-service.html) and Hop REST Web Application - Execute a pipeline synchronously (https://hop.apache.org/manual/latest/hop-rest/index.html#_execute_a_pipeline_synchronously) the table of parameters lists the first parameter as 'execute' but the examples list the first parameter as 'service'
Issue Priority
Priority: 3
Issue Component
Component: Documentation

https://hop.apache.org/manual/latest/hop-server/web-service.html

https://hop.apache.org/manual/latest/hop-rest/index.html#_execute_a_pipeline_synchronously

In addition, some consistency in style in the documentation wouldn't go astray

Thanks Phil, you're a time-saver.  Suggestions on how to achieve this consistency are always welcome as well.

re consistency - for this particular example, copy the 'Request Parameters' table from the first one to the second one, so it doesn't look like an afterthought


bun: 1.1.34 -> 1.1.37

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for bun is: Incredibly fast JavaScript runtime, bundler, transpiler and package manager – all in one
meta.homepage for bun is: https://bun.sh
meta.changelog for bun is: https://bun.sh/blog/bun-v1.1.37
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.37 with grep in /nix/store/qj3p1wks7zkc3knlxqg1ihbp1jq9ry62-bun-1.1.37
found 1.1.37 in filename of file in /nix/store/qj3p1wks7zkc3knlxqg1ihbp1jq9ry62-bun-1.1.37

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
bun

Instructions to test this update (click to expand)

Build yourself:
nix-build -A bun https://github.com/r-ryantm/nixpkgs/archive/7a250cad348bedea0bbae5a619c229a53d589412.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7a250cad348bedea0bbae5a619c229a53d589412#bun

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qj3p1wks7zkc3knlxqg1ihbp1jq9ry62-bun-1.1.37
ls -la /nix/store/qj3p1wks7zkc3knlxqg1ihbp1jq9ry62-bun-1.1.37/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @DAlperin @06kellyjac @thilobillerbeck @cdmistman @coffeeispower @diogomdp for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Still needs to be fixed with musl as bun has fixed their issues with musl.

superseded by https://github.com/NixOS/nixpkgs/pull/360759


Provide a procedure that updates K8s-based NE from one version to another.

Some thoughts... reading the update code. OK, it's docker oriented.
For the kubernetes-installed NE can we safely assume that helm is installed?
If so, then [https://pypi.org/project/pyhelm/] may be the way to go...
We can use the k8s connector as other actions then use helm to update as usual?

[] check the version

A rather large note while found in testing...
A user wants to upgrade the NE and is presented with the update panel...
there is the current version, possible versions to update to and the peripherals (all not checked).
The user must know which peripherals were checked in the original deployment...
Why?
Because if they are all left unchecked when helm is run the payload does not contain these peripherals.
The behaviour of helm upgrade will be to upgrade to exactly as described.
So some peripherals may be removed unintentionally if the user assumes that the original set may be preserved.

Looking through the API, I cannot find where the current state of the deployed NE is held... i.e what peripherals are activated and VPN client etc.
So I'm not sure where the initial deployments are stored and what happens subsequently when helm runs an upgrade and "overwrites" the peripherals deployment.

Demoed on 2023/10/03


My application for all the world to see

The GSoC page suggested putting my application as an issue. I think this is what's expected. So, tada!
..
..
..
Connor-McPherson
<EMAIL_ADDRESS>sites.google.com/mocs.utc.edu/mcpherson-portfolio
Improve Mio Support on Windows
When I first started high school, I was handed an old C++ project my older brother made as a windows multiplayer game made to span a LAN network. Back then we weren’t involved in the open-source community, so we just pulled down the closest socket library we could find.
We used the winsock library, and yes, it’s disgusting.
Here’s a snippet:
 // Create the socket
 SocketFD = socket(PF_INET, SOCK_DGRAM, 0);
 // Fill in my address data
 MyAddr.sin_family = AF_INET;
 MyAddr.sin_port = htons(27000);
 MyAddr.sin_addr.s_addr = INADDR_ANY;
 memset(MyAddr.sin_zero, '\0',sizeof(MyAddr.sin_zero));
 setsockopt(SocketFD, SOL_SOCKET, SO_REUSEADDR, &optionValue, sizeof(optionValue));
 // Bind the socket to the host at the proper port
 bind(SocketFD,(struct sockaddr*)&MyAddr,sizeof(MyAddr));
 // Fill in the peer's address data
 //MyAddr.sin_addr.s_addr = inet_addr("<IP_ADDRESS>"); // Broadcasting (Upstairs Network)
 MyAddr.sin_addr.s_addr = inet_addr(FinIP); // Broadcasting (Upstairs Network)
 memset(MyAddr.sin_zero, '\0',sizeof(MyAddr.sin_zero));
 socklen_t StAddrSize = sizeof(struct sockaddr_storage);
 // Make socket nonblocking
 u_long One=1;
 ioctlsocket(SocketFD,FIONBIO,&One);
 // Make the socket capable of broadcasting
 char Broadcast = 1;
 int RV = 0;
 RV = setsockopt(SocketFD, SOL_SOCKET, SO_BROADCAST, &Broadcast, sizeof(Broadcast));
 if( RV < 0)
   printf("Error with Broadcasting Setting.\n");

Ever since last year, I’ve been rethinking how the game communicates and I’ve been looking for a robust communication package. This requires a complete refactoring of the I/O and how the network inputs are set up.
Mio is undergoing a similar change: refactoring its I/O Windows implementation. It will be an involved project to rebuild the wepoll interface in rust. I have first-hand experience with the worst a windows socket system can look like, and I have been introduced to other libraries such as MPI through research at the University of Tennessee at Chattanooga. Although I am still a greenhorn when it comes to rust, I believe my experience with the Windows operating system and networking can help in refactoring the Mio implementation of its I/O.
Schedule of Deliverables
The first milestone will be to set up the environment first. This is because, as shown in test-first development, you can improve your overall efficiency if you verify that tests fail first to prove that it works when it passes. This first milestone would be to add unit tests for I/O. These will initially work because of Mio’s already existing (but not ideal) I/O implementation. Mio already has a testing framework set up using Cirrus CI, making this first deliverable extremely easy. Many of the unit tests may already exist.
The second deliverable will be the rust parallel to wepoll’s epoll_create, epoll_ctl and epoll_close. Functionality of these epoll instances will then be added throughout the first month. Ideally, epoll would be able to receive information from sockets and ports by the end of the first month, even if the order of receiving is not managed concurrently.
The second month would deal with using Rust and Tokio’s concurrency software to optimize the epoll system, as well as adding additional I/O functionality, such as the variety of uses associated with epoll_wait.
Open Source Development Experience
Though I am ashamed to say, I have not yet taken part in the open-source community, as much as I wish I had. Most of my work has been to add to the MocsArcade code base, a project based at my university to make a library of student-made games. This repository can be found on github (github.com/mocsarcade). Beyond that, the rest of my free time is invested in the private repo my older brother left me, the one written in C++ using winsock.
Academic Experience
I am majoring in Computer Science and currently studying COBOL, Perl, software engineering practices and Numerical Analysis. I am double-minoring in writing and math. I believe the duality of science and humanities helps me gain a more well-rounded education and gives me a more diverse set of skills. In my freshman year, one of my professors taught me that the purpose of the computer science degree is to teach students how to learn, not how to do everything in computer science. He encouraged me to teach myself beyond what I’m told in class. Even when I graduate in a year and a half, I plan to continue learning throughout my entire life, and through that gain a fuller understanding of the field of computer science as a whole. I desperately wish to learn rust and I am well versed in DevOps. Even if I’m not accepted into a GSoC internship, I plan to take part in the open-source community with what free time I carve out for myself. My goal is to learn through making.
Why Me
I believe my experience with networking, although still small, can add to the project by helping to build the system with concurrency in mind. My experience with sockets and MPI together can help me better understand Tokio and Mio as the project advances.
Still, I would recommend at least one other student that is more familiar with Rust. I know I’m not making a great case for myself, but I am neither familiar nor confident when it comes to Rust. I have experience in Python, Java, C++, COBOL and PhP, and I believe I will be able to pick up Rust quickly, but the hands-on activities needed for this project will require a deeper understanding of Rust than I currently have. I’m afraid the unique aspects of concurrency in Rust are still new to me… for now!
In Conclusion
I am not a professional at Rust, nor do I pretend to be. I plan to become one over the space of this summer, while being able to improve Mio as I improve. I believe my interest and experiences in I/O networking will be able add to Mio and improve its current implementation.

Great start!
To make the application more complete, I think the following two sections could help a lot:

A high level analysis of how wepoll is implemented. Imagine you are writing "overview" documentation and are trying to give the reader enough context to be able to dive into the wepoll source.
A description of how the ideas implemented in wepoll would apply to mio. Mio is trying to do something (similar but) different than wepoll. wepoll aims to provide API compatibility with epoll. Mio, on the other hand, provides its own set of APIs that work in isolation (Poll, TcpStream). This will make implementing the wepoll strategy in mio easier.
As a follow up point, wepoll is not able to support edge-triggered notifications. Mio will be able to. Could you describe how that might work? Hint: it will require hooking into TcpStream::ready and TcpStream::write, which mio can do because it provides its own types and read / write function implementations.

After adding these sections, I would suggest submitting the proposal via the google summer of code UI.
Cheers!


MLHR-1956 Added POJO Kafka Output operator with auto-metrics and batchprocessing

@siyuanh : Please review.

Incorporated the review comments.


DO NOT MERGE: commit to remove unit checking (branch renamed)

new reporting requires better unit support, which will require model cleanups and pint unit registry, for now this commit changes all units to '-' (for reporting testing). FYI @khaeru

now built on #149 @khaeru this is the branch I'm using to do the profiling work + the upstream message_ix branch

I'm now confused what the status of this is. The drop kwargs to the computations seem like they are in #150? Which leaves only the single-line deletion of all units?
If units in message_ix or specific global model scenarios are causing problems, then let's:

add real features to ixmp or message_ix that do things like pre-substitute units in a generalized way, e.g.: https://github.com/iiasa/ixmp/blob/62d9f1ae4095355e2b1bcf31cdf59d7b999e7ac3/ixmp/reporting/utils.py#L17-L20

…and then (2) use those features to handle the brokenness of units in those models and/or scenarios, e.g.:

https://github.com/iiasa/message_ix/blob/e2b85e90b72e6c46d7fd1e3d64e4a09eaf8abd00/message_ix/reporting/__init__.py#L17-L22
https://github.com/iiasa/message_data/blob/126591fe26356ee6d5fe1049dc5a4df543069864/reporting/data/global.yaml

I would strongly prefer this to ‘temporary’ changes in ixmp that might ossify and cause trouble when we later try to remove them.

For sure this is not meant at all to make it into any non-testing branch. It was only so I could actually run the reporting on the global model.

this is no longer needed to run reporting via our testing script, though not entirely sure why =)


[ble-mesh] possibly bug in publish with period/interval (IDFGH-5915)

Hi,
i am not sure if this is a bug or just log message that should not be BT_ERR just BT_WARN or even lower level.
I tested with simple battery server in root element and after provisioning, bound app key etc i wanted to setup from nrf mesh provisioning app publish on battery server which should publish data with interval i wanted. I dont know if data is really published, because i dont have prepared client node yet and android app is not receiving any data (tried with sendors too, same result).
Here are logs as much as i could grab:
I (64531) BLE_MESH: Publish period 4500 ms
I (64531) BLE_MESH: Publish Retransmit Count 1 Interval 100ms
I (64531) BLE_MESH: send, app_idx 0x0000 src 0x002d dst 0xffff
I (64541) BLE_MESH: send, len 0:
I (64541) BLE_MESH: Publishing next time in 100ms
I (64551) BLE_MESH: src 0x002d dst 0xffff seq 0x00000013 friend_match 0
I (64561) BLE_MESH: Payload<PHONE_NUMBER>
I (64561) BLE_MESH: AFK 1 AID 0x08
I (64561) BLE_MESH: ASZMIC 0 AKF 1 AID 0x08
I (64571) BLE_MESH: len 4: 00000000
E (64571) BLE_MESH: Too short SDU + MIC (buf len 4, expected len[5])

It looks like published data is patched from network layer back to transport layer when it should be discarded as it is from that node. If this is not the problem and packet should be discarded in transport layer, then Too short SDU + MIC  is most likely bug.
esp-idf commit 220590d599e134d7a5e7f1e683cc4550349ffbf8
esp32 C3 devkit rev2
ble-mesh with bluedroid stack
Thanks for any help

Its not a bug. I just didnt have implemented esp_ble_mesh_register_custom_model_callback with ESP_BLE_MESH_MODEL_PUBLISH_UPDATE_EVT and esp_ble_mesh_model_publish in it.
Sorry


Add Aiven as an OSPO Adopter

Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Have you picked the single best (existing) category for your project?
[ ] If submitting a tool, is your project closed source or, if it is open source, does your project have at least 100 GitHub stars?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~10 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Build failed because of:
Aiven (Adopter): Only svg logos are supported
Empty twitter for Apple (Adopter): https://twitter.com/apple
No cached entry, and Banco Itaú (Adopter) has issues with twitter: https://twitter.com/itauunibanco_ri, Request failed with status code 404
No cached entry, and Banco Itaú (Member) has issues with twitter: https://twitter.com/itauunibanco_ri, Request failed with status code 404
Item Aiven (Adopter) has no image_data

Build failed because of:
Aiven (Adopter): Only svg logos are supported
No cached entry, and Banco Itaú (Adopter) has issues with twitter: https://twitter.com/itauunibanco_ri, Request failed with status code 404
No cached entry, and Banco Itaú (Member) has issues with twitter: https://twitter.com/itauunibanco_ri, Request failed with status code 404
Empty twitter for Apple (Adopter): https://twitter.com/apple
Item Aiven (Adopter) has no image_data

Build failed because of:
No cached entry, and Aiven (Adopter) has issues with logo: aiven.svg, SVG file embeds a png. Please use a pure svg file
Empty twitter for Apple (Adopter): https://twitter.com/apple
No cached entry, and Banco Itaú (Adopter) has issues with twitter: https://twitter.com/itauunibanco_ri, Request failed with status code 404
No cached entry, and Banco Itaú (Member) has issues with twitter: https://twitter.com/itauunibanco_ri, Request failed with status code 404
Item Aiven (Adopter) has no image_data

Hi @anajsana is there something I can do to help you in this PR?

Hi @anajsana is there something I can do to help you in this PR?

hi @jlprat ! I've just made a new commit adding the SVG logo you provided and deleting the broken one. The deployment preview should be ready in a few minutes and hopefully, we will be able to merge it :)

LGTM!


feat: Simple close button for the filter panel

What feature?
In the /projects directory, there is a filter button that opens up a dialog panel/pop-up to allow the user to select the desired filter. However, some users may be confused about how to close the filter panel because, currently, the only way to do so is by clicking anywhere outside of the filter panel. In my own experience, I was confused about how to close it since I intuitively looked for a close button.
Benefits:

Reduce confusion regarding how to close the filter panel.
Increase intuitiveness in the process of selecting filters.

Solution:
We can a simple close button on the top right of the filter panel.
Add screenshots
Demo screenshot of the new close button:

View for desktop users:

View for mobile users:

Record

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I agree to follow this project's Code of Conduct
[ ] I'm a GSSoC'23 contributor
[X] I want to work on this issue

yeah we need to add. just remove the text close & use only icon

Will do @priyankarpal, I have made the PR.


bookstack: 24.05.4 -> 24.10.3

Diff<EMAIL_ADDRESS>Changelog: https://github.com/BookStackApp/BookStack/releases

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I'm not quite sure why nixfmt is failing here, if I run nixfmt on my machine, nothing changes and nixfmt --check exits 0.


AIX playbook requires an update

[x] Failing Yum task

The task Install yum package support fails with the error coreutils-8.29-4.ppc conflicts mktemp. A temporary solution is to skip the coreutils package.

[ ] Outdated installation links

The task Install yum package support contains 3 links to rpm packages which no longer exist:
http://www.bullfreeware.com/download/bin/2328/libiconv-1.14-22.aix6.1.ppc.rpm
http://www.bullfreeware.com/download/bin/2591/libunistring-0.9.6-2.aix6.1.ppc.rpm
http://www.bullfreeware.com/download/bin/3944/perl-5.24.0-3.aix6.1.ppc.rpm

Causing the error Failed to get nevra information from RPM package

[ ] Installation packages/archives need to be in /Vendor_Files/aix on the ansible controller

This isn't really an error, but what I feel to be an inconvenient method of installing packages. Many of the installation packages are required to be in /Vendor_Files/aix on the machine which run the ansible playbook, which I didnt have, causing the playbook to fail many times. So my question is, is there a more efficient way of doing this?
Examples include

/Vendor_Files/aix/XLC/XL_C_Cpp_FOR_AIX_V16.1_EMG.tar.Z

/Vendor_Files/aix/OpenGL_X11.tar

/Vendor_Files/aix/openssl/openssl-<IP_ADDRESS>1.tar.Z

[ ] Transfer and extracting /Vendor_Files/aix/openjdk-7u-aix.tar results in the following error

    "msg": "Failed to find handler for \"/.ansible/tmp/ansible-tmp-1594290693.3986292-109761101654969/source\". Make sure the required command to extract the file is installed. Command \"/opt/freeware/bin/unzip\" could not handle archive. Command \"/usr/bin/gtar\" detected as tar type None. GNU tar required."
}

After trying to transfer and extract /Vendor_Files/aix/openjdk-7u-aix.tar manually, i get the error:
x j2sdk-image/jre/lib/rt.jar, 60290313 bytes, 117755 tape blocks
tar: tape read error: unexpected EOF

I suspect that this is the error that causes ansible to stumble, since the same ansible error does not occur when transfering and extracting /Vendor_Files/aix/OpenGL_X11.tar. Hence, I can only conclude that there maybe something wrong with the openjdk-7u-aix.tar file

[x] {{ bootjdk }} variable will not load for AdoptOpenJDK 9 through 12 tasks.
Despite there being a

name: Load AdoptOpenJDKs variable file
include_vars: ../adoptopenjdk_variables.yml

tasks at the beginning of the playbook, in which the variable bootjdk: openj9 is supposed to load, it doesnt. To temporarily overcome I replace instances of {{ bootjdk }} with openj9

I agree that this is very out of date.  The reason behind the file being "hidden", is because some might have a license that not all users might have access too.  Others are not available for direct download (or weren't at the time of writing).
openssl-<IP_ADDRESS>1.tar.Z for instance there was no direct download url as there was an agreement acceptance required by IBM.  For XC_C, whether its 13 or 16, there are license implications, so there couldn't be a posting of the binary free for all to obtain. :)
For some sections there are comments detailing reasons.

Moving the - name: Load AdoptOpenJDKs variable file task, which is run in its own task block, to its own role seems to have fixed the issue of the bootjdk variable not loading. Changes are being made in https://github.com/AdoptOpenJDK/openjdk-infrastructure/pull/1434

The Failing Yum task may have been intermittent, as it did not occur on 2 'out of the box' aix machines

How can I help?
I'll help patch this one up - but if you (openjdk) are game, I'd like to attempt an alternative - with fewer dependencies re: the Opensource tooling.
FYI: IBM is very committed to using yum - which requires their packaging of python2, which has it's dependencies, etc. etc. Personally, I liked the idea - very much - back in 2001 - but by 2004 I was against because mixing package managers just leads, sooner or later - to conflicts.
I see that IBM is working hard to correct the issues of the past, but I know I'll never really embrace using two package managers - e.g., Debian base, and all additonal OSS installed using RPM rather than 'native' aptitude.
Back on point: how I can I help with the current situation!

The Failing Yum task may have been intermittent, as it did not occur on 2 'out of the box' aix machines

If those are the two new systems I prepped at OSU - then that is probably because I spent some time getting yum fixed and installed by default. So, the stray dependencies coreutils needed before were already resolved.
If it is not those systems - then I am would have to guess differently.

As I mention in #1581 - in part by your concerns above (I did not have this ...), this should be part of a verification check. IMHO it is wrong to assume that the playbook installs software requiring a license.
My opinion is that whoever is supplying the LPAR (or WPAR) is responsible for supplying licensed software. So, maybe IBM provides the software - but not via a (relatively) uncontrolled licensed version stored as a file in an OSS supported site.
I do not care who put it there, it does not make it suddenly available as licensed software. IBM support would not agree - at least I would not expect them to agree formally.

This can be closed. The issues have since been resolved


Update README.md

Updated readme according to the team name, members and github id's

Please add github ids also

Added github ids also. Please review.


Byzantine fork attack fails with fast hotstuff

I am running an experiment with 4 replicas on my local machine. When I attempt to run the byzantine fork module and the fasthotstuff consensus module, I run into a few issues.
When running with a fixed leader, the program returns an RPC error. Below is a screenshot of this scenario.

When running with a rotating leader, the experiment runs to completion, only a small number of commands are actually executed and the vast majority time out.

I have also encountered a similar issue when using silence module, where only a single digit number of transactions are completed, and the vast majority are left to time out. I am not sure if I am incorrectly using this feature or if it is an underlying issue. Any clarity would be greatly appreciated.
Thanks,
Birju

Just wanted to reach out and say that @hanish520 is looking into this.


Streams order, use format: "set" for streams

Fixes #83

We tested this diff on our setup (following the Testing the provider locally instructions on the README) and it fixes the noisy plan diffs we get on connections with a lot of streams. Thanks so much for the patch.
What else do we need to get this merged and released?

@JonsSpaghetti @bgroff could you guys have a look when you get a chance?

@lucasmazza @dholleran-volt I'm in touch with Airbyte team. I got info from @marcosmarxm that @perangel will be back on July 15th from his PTO and he'll take care of it.

I have PR up https://github.com/airbytehq/terraform-provider-airbyte/pull/128 with the proposed changes. There is a link to the branch that has the fully generated provider source that you can use to run it locally to verify if it fixes your use case

#128 fixed https://github.com/airbytehq/terraform-provider-airbyte/issues/83. I'm closing this pull request.


Remove whitespace and newlines before closing parentheses

Fixes #47.

Still testing. Meant to create pull request on my forked version. Sorry.


NPM warns of a moderate vulnerability

$ npm audit

                       === npm audit security report ===

                                 Manual Review
             Some vulnerabilities require your attention to resolve

          Visit https://go.npm.me/audit-guide for additional guidance

  Moderate        Regular Expression Denial of Service

  Package         mime

  Patched in      >= 1.4.1 < 2.0.0 || >= 2.0.3

  Dependency of   s3 [dev]

  Path            s3 > mime

  More info       https://nodesecurity.io/advisories/535

found 1 moderate severity vulnerability in 3942 scanned packages
  1 vulnerability requires manual review. See the full report for details.

um, wrong repo.


Update the state archival JavaScript tutorial

This updates the state archival tutorial (from here):

use the latest stellar-sdk (both the package name and the correct modules)
fetch the WASM entry correctly alongside getFootprint()

(Better late than never :sweat_smile:)

Preview is available here:http://soroban-docs-pr698.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr698.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr698.previews.kube001.services.stellar-ops.com/


T29013 LabelSetImage unnecessarily have a color property.

Since we are maintaining a single propertyList for all kind of images(regular medical image, LabelSetimage), we are not able to delete it. So as part of fix to this issue I have disable color property for lablesetImage. so it will not be selectable in this case. If you still want to remove this property completely please put your suggesion.

Hi, thanks for your contribution. We would prefer to remove the property completely from LabelSetImages instead of blocking editing. However, keep in mind that it is a low priority task and a clean solution is probably heavier than you may anticipate as we also do not want to introduce reverse soft dependencies between modules, which would be necessary at the moment to exclude LabelSetImage from the list of data nodes that will get a color property by default.


add imagemagick package

This needs to be tested on bsd and macosx before merging.
It should apparently work the exact same way as installing on Linux according to the docs, but I wanna be sure.
Edit: lol I forgot there are CIs for that.

note: the following packages are unsupported for bsd/x86_64!
-> pkg-config

Maybe need add @bsd to pkg-config package

/usr/bin/ld: miff.c:(.text+0x8cbe): undefined reference to BZ2_bzCompress' /usr/bin/ld: miff.c:(.text+0x8d3e): undefined reference to BZ2_bzCompressEnd'
/usr/bin/ld: miff.c:(.text+0x8da9): undefined reference to lzma_code' /usr/bin/ld: miff.c:(.text+0x8e29): undefined reference to lzma_end'
/usr/bin/ld: /home/runner/.config/.xmake/packages/i/imagemagick/7.0.11-13/68813100e8ca4f02803ff9fa5f5d9714/lib/libMagickCore-7.Q16HDRI.a(MagickCore_libMagickCore_7_Q16HDRI_la-msl.o): in function MSLInternalSubset': msl.c:(.text+0x5a1): undefined reference to xmlCreateIntSubset'
/usr/bin/ld: /home/runner/.config/.xmake/packages/i/imagemagick/7.0.11-13/68813100e8ca4f02803ff9fa5f5d9714/lib/libMagickCore-7.Q16HDRI.a(MagickCore_libMagickCore_7_Q16HDRI_la-msl.o): in function MSLResolveEntity': msl.c:(.text+0x63c): undefined reference to xmlLoadExternalEntity'
/usr/bin/ld: /home/runner/.config/.xmake/packages/i/imagemagick/7.0.11-13/68813100e8ca4f02803ff9fa5f5d9714/lib/libMagickCore-7.Q16HDRI.a(MagickCore_libMagickCore_7_Q16HDRI_la-msl.o): in function MSLGetEntity': msl.c:(.text+0x6a9): undefined reference to xmlGetDocEntity'
/usr/bin/ld: /home/runner/.config/.xmake/packages/i/imagemagick/7.0.11-13/68813100e8ca4f02803ff9fa5f5d9714/lib/libMagickCore-7.Q16HDRI.a(MagickCore_libMagickCore_7_Q16HDRI_la-msl.o): in function MSLGetParameterEntity': msl.c:(.text+0x70e): undefined reference to xmlGetParameterEntity'
/usr/bin/ld: /home/runner/.config/.xmake/packages/i/imagemagick/7.0.11-13/68813100e8ca4f02803ff9fa5f5d9714/lib/libMagickCore-7.Q16HDRI.a(MagickCore_libMagickCore_7_Q16HDRI_la-msl.o): in function MSLEntityDeclaration': msl.c:(.text+0x7dc): undefined reference to xmlAddDocEntity'
/usr/bin/ld: msl.c:(.text+0x81a): undefined reference to xmlAddDtdEntity' /usr/bin/ld: /home/runner/.config/.xmake/packages/i/imagemagick/7.0.11-13/68813100e8ca4f02803ff9fa5f5d9714/lib/libMagickCore-7.Q16HDRI.a(MagickCore_libMagickCore_7_Q16HDRI_la-msl.o): in function MSLAttributeDeclaration':
msl.c:(.text+0x8d4): undefined reference to xmlSplitQName' /usr/bin/ld: msl.c:(.text+0x923): undefined reference to xmlAddAttributeDecl'
/usr/bin/ld: msl.c:(.text+0x974): undefined reference to xmlAddAttributeDecl' /usr/bin/ld: msl.c:(.text+0x988): undefined reference to xmlFree'

Maybe we need add some deps or disable them in cmake.install/configs

Tracking them down now. At first glance I see bzip2 and some xml-related one.

Hmm. It seems like the some of the Linux CIs are still failing due to openexr.
As for MacOS, this line in particular stands out:

checkinfo: ...gramdir/core/sandbox/modules/import/core/tool/linker.lua:75: @programdir/core/sandbox/modules/os.lua:262: Undefined symbols for architecture x86_64:

https://github.com/xmake-io/xmake-repo/pull/424/checks?check_run_id=2616618403#step:4:571

missing freetype, fontconfig, webp , you can add these deps and disable them.

Huh, libwebp is already a dependency though.
I'll add freetype and fontconfig.

Hmm, I can see a threading issue with the Arch CI.
The solution according to the internet should be simple. Adding -pthread to the CFLAGS.

if is_plat("linux") then
add_syslinks("pthread")
end

Need to disable lcms it looks like from the Ubuntu log.

Oh oof, I think libjpeg-turbo needs to libjpeg.

I'm not sure what's causing Arch/Fedora/Ubuntu to fail.
It fails while checking the header MagickWand/MagickWand.h for the function MagickWandGenesis.
It appears to have a lot of undefined references to... it's own functions that it supplies?
Yet the same thing succeeds in other Linux CIs.

checking for c links(MagickCore-7.Q16, MagickWand-7.Q16, Magick++-7.Q16, png, z, jpeg, m)

By default, xmake will automatically scan all library files in the installdir/lib directory, and then automatically add links, but their link order may be unreliable.
If there are multiple library files in a package, and there are link order dependencies between them, we can manually call add_links("xxx", "yyy") ot package:add("links", ... to rewrite them and adjust the link order.

Ah that would explain it!
MagickWand depends on MagickCore, and Magick++ is separate. So it should be:
MagickCore -> MagickWand
Magick++

I'll need to wait a bit before I can test though.
Compiling GCC right now.
Shouldn't be too long, I've been compiling for about 4-5 hours now.

OH I need to update the include dirs like I did with the lib dirs.

It still seems to fail on the same few CIs.

(ubuntu-latest, shared) completed properly, but (ubuntu-latest, static) failed.
Huh. I assume those are the same just with shared vs static libs right?

(ubuntu-latest, shared) completed properly, but (ubuntu-latest, static) failed.
Huh. I assume those are the same just with shared vs static libs right?

missing liblqr? maybe we disable it first?

gemagick/7.0.11-13/fe10404f83fd46caad7cebdf03666a5d/lib/libMagickCore-7.Q16.a(libMagickCore_7_Q16_la-resize.o): in function LiquidRescaleImage': resize.c:(.text+0x31d2): undefined reference to lqr_carver_new_ext'
/usr/bin/ld: resize.c:(.text+0x3252): undefined reference to lqr_carver_set_preserve_input_image' /usr/bin/ld: resize.c:(.text+0x3274): undefined reference to lqr_carver_init'
/usr/bin/ld: resize.c:(.text+0x329a): undefined reference to lqr_carver_resize' /usr/bin/ld: resize.c:(.text+0x32ac): undefined reference to lqr_carver_get_height'
/usr/bin/ld: resize.c:(.text+0x32bb): undefined reference to lqr_carver_get_width' /usr/bin/ld: resize.c:(.text+0x336f): undefined reference to lqr_carver_scan_reset'
/usr/bin/ld: resize.c:(.text+0x34c9): undefined reference to `lqr_carver_scan_ext'

Thanks! :+1:

I'll make sure to update the package once pkg-config has bsd support.
Next on my list was fixing the drogon package, then I'll update the pkg-config package.

I'll make sure to update the package once pkg-config has bsd support.
Next on my list was fixing the drogon package, then I'll update the pkg-config package.

it's great, thanks!


Admins can manage async run state

admins should be able to do things like mark a player as forfeited, or update their time/vod URL if necessary

/cancel_race is like, 15% of this

given that we now have the whole bracket race infrastructure to report results into, and asyncs are more ad-hoc, i think we don't need any more features here.


Adding InferencePool, Group and Endpoint

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[x] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearningServices/workspaces/{workspaceName}/inferencePools/{name}/status": {

Post action name should have a verb in it to define an action. Avoid using works get/list though in this case. You could say /fetchStatus

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:8803 in af94a88. [](commit_id = af94a88c21d1bffad796a4a445adee592aab5abc, deletion_comment = False)

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearningServices/workspaces/{workspaceName}/inferencePools/{poolName}/groups/{name}/status": {

same comment as above for action name

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:9813 in af94a88. [](commit_id = af94a88c21d1bffad796a4a445adee592aab5abc, deletion_comment = False)

      "description": "The resource URL of the entity (not URL encoded).",

is there any reason why you are not using the common type anymore?

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:20397 in af94a88. [](commit_id = af94a88c21d1bffad796a4a445adee592aab5abc, deletion_comment = False)

This PR got rebased which resulted in unrequired changes and gates/approvers added. Updated PR is https://github.com/Azure/azure-rest-api-specs/pull/25819


Accept HTML in placeholder

:+1:

+1

+1

Closing it down as it is a old issue. Please create new issue if this is still a bug/ problem.
Also i'm trying to get a good overview of recent bugs.
Thanks for understanding.


CSV-formatted 3rd-party dependency report

I finally got around to whipping this up.  Everything I needed was in place, so there is not much to review.  Let me know what you think about it.
Thanks!
(Addresses #69)

Johannes Rudolph » sbt-dependency-graph #26 FAILURE
Looks like there's a problem with this pull request
(what's this?)

I am looking for this feature. Any news on this?

@jrudolph Let me know if there is anything I can do to help you integrate and publish this enhancement.  We've been using it for a while now without any problems.
@rintcius you can grab my branch and publish locally.  It is set to version 0.7.6-SNAPSHOT.

Thanks for the PR, @joescii, and sorry for not yet commenting on this. I'm currently restructuring the code a bit to make it more straight-forward to make changes. I will hopefully get to this PR afterwards.
I like the idea of providing CSV output. I guess it would make sense to make it configurable what fields you would like see.


Bugfix/attri2vec demo

I fixed the following bugs for attri2vec demos:

Specify the edge type as cites for attri2vec node classification and embedding learning demo.

Change the use_multiprocessing option of keras.model.fit_generator to False for attri2vec link prediction demo.

@adocherty, Andrew, could you please help me review it?
Best regards!
Daokun

Thanks @adocherty !

@adocherty, Andrew, should I do something to merge the pull request? like signing commits?


Multiple videos in a queue

This is cool! Could it be updated to support looping a queue of different videos? Give it an array of videoURLs and it'll play them all with transitions between each, looping back to the first when completed to play indefinitely?

@hipwelljo That was my intention when I first started. Will see if I can update it for supporting this.


Add hrishikeshnikam2000

resolve #612

Sorry missed this one

Thanks for contributing and nice profile btw 🚀

Thank you so much! @schmelto


Add draft feature

Create the draft feature for each of the notes so that even if the user has not saved the data the data will still be there on the notes but is not updated in the database, just like Whatsapp.

Done