Move to operator sdk version 1.24.0

Including update to gomega for golang.org/x/net
dependency update

Operator SDK related version upgrade change as per documentation here are made in series.
Updated gomega in mod, which indirectly upgrades the dependent x/net to 0.7.0 (and other indirect dependents).
Changes to test are due to better error reporting, which as a result failed the tests that were updated.
There is one pending test failure, where a VRG is left behind and hence the API server does not stop, which will be fixed in a subsequent commit.

This is pretty big single commit pr. Can we split the work to smaller commits or multiple prs
to make this change incrementally?

This is pretty big single commit pr. Can we split the work to smaller commits or multiple prs to make this change incrementally?

Posted multiple commits...

Operator SDK related version upgrade change as per documentation here are made in series.
Updated gomega in mod, which indirectly upgrades the dependent x/net to 0.7.0 (and other indirect dependents).
Changes to test are due to better error reporting, which as a result failed the tests that were updated.
There is one pending test failure, where a VRG is left behind and hence the API server does not stop, which will be fixed in a subsequent commit.

Most of the above are now in commit messages, but note that make test still has the above failure and KUBEBUILDER_ASSETS is not set right from the Makefile on a new environment (i.e when run manually on the shell and then executing make test works, but on a fresh system it is empty)

Much nicer! The first commits updating the version looks trivial and
hopefully can be merge now, unless they are the reason for the test
failure.
Regarding gomega - if I understand this correctly, we update it for
fixing the security issue in /x/net. This looks fragile, for example
if we stop using this package, another package can bring older /x/net.
If we want to ensure that we have safe version of /x/net, why not make
the requirement explicit?

Changes to test are due to better error reporting, which as a result failed the tests that were updated.
There is one pending test failure, where a VRG is left behind and hence the API server does not stop, which will be fixed in a subsequent commit.

I don't understand the problem - the test failure are result of upgaraing
the versions or incomplete change, using new features available in the
new verson?
I think it would be useful to merge what we can merge now from this PR,
deferring the incomplete changes to later PR if possible.

Much nicer! The first commits updating the version looks trivial and hopefully can be merge now, unless they are the reason for the test failure.

I would like to merge this as a batch and not in parts. Having moved the SDK version from somewhere around 1.11 till here and picking changes that are intermediate, even though bisect-able, is preferred that we merge this in one go.

Regarding gomega - if I understand this correctly, we update it for fixing the security issue in /x/net. This looks fragile, for example if we stop using this package, another package can bring older /x/net.

Yes it can, go mod graph helps track down dependencies and address the same. Further security scans help check and report any new regressions.

If we want to ensure that we have safe version of /x/net, why not make the requirement explicit?

We do not use this package directly, it comes in as a dependency as an indirect package, so adding it directly does not serve the purpose, for similar reasons as above (i.e if we stop using say gomega, there would be no reason to add this to the module, although quite a few packages that we depend on also depend on /x/net).

Changes to test are due to better error reporting, which as a result failed the tests that were updated.
There is one pending test failure, where a VRG is left behind and hence the API server does not stop, which will be fixed in a subsequent commit.

I don't understand the problem - the test failure are result of upgaraing the versions or incomplete change, using new features available in the new verson?

Upgrade of gomega now ends up returning status errors and compares them more correctly, causing test failures, requiring changes to this file
If you run the change in the commit without those changes the error reported by the tests are visible.

I think it would be useful to merge what we can merge now from this PR, deferring the incomplete changes to later PR if possible.

The changes are incomplete only from the perspective of why KUBEBUILDER_ASSETS is an empty string when run on a fresh setup, the "other" issue due to an existing issue in the VRG tests that was not considered a failure till now, but is from here on, which hence needs a fix.
I will fix these subsequently and update this PR for a merge, not spending time splitting this up.

Operator SDK related version upgrade change as per documentation here are made in series.
Updated gomega in mod, which indirectly upgrades the dependent x/net to 0.7.0 (and other indirect dependents).
Changes to test are due to better error reporting, which as a result failed the tests that were updated.
There is one pending test failure, where a VRG is left behind and hence the API server does not stop, which will be fixed in a subsequent commit.

Most of the above are now in commit messages, but note that make test still has the above failure and KUBEBUILDER_ASSETS is not set right from the Makefile on a new environment (i.e when run manually on the shell and then executing make test works, but on a fresh system it is empty)

KUBEBUILDER_ASSETS issue in Makefile is fixed by splitting up the Makefile targets to envtest and setup-envtest, unsure why this works though.
envtests failure to shutdown the instance is addressed based on https://github.com/kubernetes-sigs/controller-runtime/issues/1571
All changes are updated and ready for review/merge as appropriate.

@nirs some of the changes are easier to follow if you run through a sample operator build exercise using operator-sdk. What I typically do is have a fresh sample created from the version we are moving to, to look at the changes/auto-generated files etc. and pull back changes to our code as per the upgrade documentation.
For example the envtest KUBEBUILDER_ASSETTS or the CRD annotations are explained away more easily.

Sounds like we need a maintainer.md document explaning this process for the next upgrade.

@nirs Can we merge this now?

Sure, lets merge.


zopen-setup fails (not so gracefully?)

Finally setup z/OS 2.5 on the RD&T / ZPDT
After initial setups, tried to install 'zopen'...

Downloaded from https://github.com/ZOSOpenTools/meta/releases/tag/v1.0.0
Brought (SFTP) to the z/OS
chmod u+x

Running in (default) shell yields:

Running in bash (from the z/OS 2.5) yields:

Versions/Hashes etc:

What did I miss?

Solved :)
It was tagged as ISO8859-1 :)
t ISO8859-1   T=on  -rwxr-xr-x   1 OMVSKERN SYS1      245760 Apr 18 15:50 zopen-setup
chtag -b zopen-setup
Worked like a charm...
Closing :)

Also , don't store the installer in a dir called zopen lol


⚠ Bofrost.de has degraded performance

In f49fb80, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2427 ms

Resolved: Bofrost.de performance has improved in a81d8ff.


Create a presentation

What
Create a presentation deck to present the information back to the team. Some of it will be shared in a research recap, most will in the deck for the team to explore on their own time
Why
Share the insights we find with the Design System team and others
Who needs to work on this
Trang, Katrina
Who needs to review this
Trang, Katrina
Done when

[x] Added information about the survey
[x] Added quant analysis into the deck for every question
[ ] Added information about whether there is / isn't a trend
[ ] Added insight from free text analysis
[ ] Added trends to continue monitoring
[ ] Added recommendations

Link to the presentation. Access restricted https://docs.google.com/presentation/d/1enlxH2QFKxBEBhD3bHf_TLowZjfvTd-6hrJgKxVYPlk/edit?pli=1#slide=id.g10372e0cd7_2_16


Add file tree exclude in core

Right now every time an user has a performance issue one of the first things is to ask to install an extension so to exclude some files from the watchers.
It would be nice to have it in the core, to reduce these issues.
It would be help my PR https://github.com/adobe/brackets/pull/12190 because then I could read to exclude list from the configuration.
Plus all of these extensions seems to mess with a private method _indexFilter which could results in some problems in the future.
There are some extensions but I was mostly think to this one:
https://github.com/zaggino/brackets-file-tree-exclude
/cc @zaggino

Fine with me, but there should be some sort of icon/indicator that there were some entries hidden from the file tree and the user would be taken to the filter settings when he clicks that icon.

Mmm totally my fault to not try the extensions before...
What I'm personally really interested is the configuration for the purpose of the PR #12190.
Now I'm not sure if I really want all the features of those extensions...

Check out my enhancement proposal called black-box in https://github.com/adobe/brackets/issues/11833#issuecomment-149285875 which is basically File Tree Exclude + @zaggino's suggestion for UI interactions.

This would indeed be good to have built in. We have huge performance issues with new environments on our default projects - until we install https://github.com/zaggino/brackets-file-tree-exclude - after which they go away.

I much prefer the approach in #12647, so closing.


fix(material/snack-bar): Ensure snackbar enter/exit works with OnPush ancestor

By updating the "arbitrary-component" to OnPush, the following test fails:
MatSnackBar should set the old snack bar animation state to complete and the new snack bar animation.
The assertion that fails is the afterDismissed spy, which never gets called. Adding markForCheck in the exit ensures the _animationState is applied to the host and completes. If this is not done, the following listener never executes, including the _completeExist: '(@state.done)': 'onAnimationEnd($event)'.

Green TGP


PSA: Update PSA default

Changes required:
The PSP default 'RKE Default' should be labelled 'RKE2 Default'.
The PSA default is currently labelled '(None)' - this is fine for k8s <=1.25. When the version is >= 1.25, this should say "Rancher Default".
IF the user changes the CIS Worker Profile to anything other than "None", then we need to reset the PSA to 'Rancher Default" and disable the control to prevent the user changing it. We should show a banner or somehow indicate that we've done this.
In some cases, the user may create a PSA template that is compatible with the Rancher Default - they may want to use this with CIS Worker Profile set to something other than None - I suggest a checkbox 'Allow PSA Default Template to be overridden when using a CIS Profile". Checking this would enable the PSA template dropdown and allow them to select their own.
We should show a banner if they check this that they understand that they know what they are doing.
Note: The Rancher Default is different to the RKE2 Default, so we can't use their docs - Rancher should provide docs that we can link to when done.

@kwwii FYI - feel free to update the UX of how/where the docs link should appear

To recap these combination of cases:

k8s < 1.25.x + CIS different than (None):
PSA label is Rancher Default
Status disabled
k8s < 1.25.x + CIS (None):
PSA label is(None)
Status enabled
k8s >= 1.25.x + CIS different than (None):
PSA label is Rancher Default
Status disabled
k8s >= 1.25.x + CIS (None) or CIS checkbox enabled:
PSA label isRancher Default
Status enabled

I take the chance to signal that we do not have to display the banner if it's not RKE2, as we do not have PSP for K3.

@nwmac Please correct me if I'm wrong.

In view of the K3S requirement to have PSA, could you please tell me if I've to keep the banner in this case?
@kwwii @nwmac

k8s < 1.25.x + CIS different than (None):

PSA label is Rancher Default
Status disabled

@cnotv , k8s <1.25.x with CIS profile different from none will be using PSP either one specified in Rancher UI or default coming from RKE2. So I don't believe we should automatically set PSA in this case, it should remain "None".
Could you please also clarify what do you mean by "Status disabled"? User can't change the selected PSA value?

Status disabled means that the input cannot be used because is disabled. It does not refer to the model or resource.

@snasovich in the UI we do not set automatically no PSP and no PSA whatsoever. This is a logic implemented server side from the other teams. Regardless that's (None) or Rancher Default, in the UI that's always empty value.

As mentioned in the previous conversation, the order of the inputs will be:

PSA/CIS
CIS override
PSA

Given the latest update, the logic is definitely way simpler.
Label:

k8s < 1.25.x: PSA label is(None)
k8s >= 1.25.x: PSA label isRancher Default

Input status:

CIS not set or set with override: enabled
CIS not set: disabled

Checkbox has to be displayed only if PSA is needed.

@kwwii Is the logic for the PSA label the same also in case of K3S, since now it's enabled?

I assume it is the same but we should confirm this.

Increasing size after changing requirements.

Validated this against v2.7-head https://github.com/rancher/rancher/commit/ab561bf837ca6051176bf169784edb01d9dee134. See details below:
ENVIRONMENT DETAILS

Rancher install: Helm
Rancher version: v2.7-head https://github.com/rancher/rancher/commit/ab561bf837ca6051176bf169784edb01d9dee134
Browser: Chrome

TEST RESULTS

Scenario
Test Case
Result

1
As a standard user, validate that CIS Profile 1.23 appears only for K8s v1.25 and rancher-restricted is set by default
:white_check_mark:

2
As a standard user, validate that CIS Profiles 1.5 and 1.6 appear for K8s < v1.25
:white_check_mark:

3
As a standard user, provision a downstream RKE2 v1.25 custom cluster with CIS 1.23, validate cluster and nodes are Active
:white_check_mark:

4
As a standard user, provision a downstream RKE2 v1.24 custom cluster with CIS 1.6, validate cluster and nodes are Active, upgrade cluster to v1.25 and CIS to 1.23, validate cluster and nodes upgrade
:white_check_mark:

Scenario 1

Navigated to Cluster Management > Create > Custom.
Using K8s v1.25, clicked the CIS Profile dropdown and validated only cis-1.23 appears:

Clicking cis-1.23, I noted that rancher-restricted is selected by default as expected:

By clicking the Allow PSA Default Template to be overridden when using a CIS Profile, I can successfully modify the PSA template with any built-in and/or created PSA templates I have available:

Scenario 2

Navigated to Cluster Management > Create > Custom.
Using K8s v1.24 and v1.23, the CIS Profile has values 1.5 and 1.6:

Validated that the PSP default is set to Default - RKE2 Embedded and PSA is set to rancher-restricted when CIS Profile is selected or not selected.

Scenario 3

Validated as part of this issue's results.

Scenario 4

Validated as part of this issue's results.


-l flag doesn't work with B2 or S3

What is the problem you are having with rclone?
The flag -l does not seem to work with B2 and S3 (tested on Wasabi) remotes. From #1152, I would expect that this is working now. And from the docs:

 -l, --links  Translate symlinks to/from regular files with a '.rclonelink' extension

What is your rclone version (output from rclone version)
Tested with:
rclone v1.46
- os/arch: darwin/amd64
- go version: go1.11.5

and
rclone v1.47.0-032-gb9e16b36-beta
- os/arch: darwin/amd64
- go version: go1.12.4

Which OS you are using and how many bits (eg Windows 7, 64 bit)
macOS 1.14.4 and 64 bit
Which cloud storage system are you using? (eg Google Drive)
B2 and Wasabi vs S3
The command you were trying to run (eg rclone copy /tmp remote:tmp)
I am trying to copy a symlink.
$ rclone copyto -l alink b2:bucket/newlink

(or something like that)
A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)
When I do it with no -l flag:
2019/05/03 14:45:19 ERROR : : error reading source directory: failed to read directory "": readdirent: invalid argument
2019/05/03 14:45:19 ERROR : Attempt 1/3 failed with 1 errors
2019/05/03 14:45:19 ERROR : : error reading source directory: failed to read directory "": readdirent: invalid argument
2019/05/03 14:45:19 ERROR : Attempt 2/3 failed with 1 errors
2019/05/03 14:45:19 ERROR : : error reading source directory: failed to read directory "": readdirent: invalid argument
2019/05/03 14:45:19 ERROR : Attempt 3/3 failed with 1 errors

When I use -l
2019/05/03 14:45:41 ERROR : Attempt 1/3 failed with 0 errors and: object not found
2019/05/03 14:45:41 ERROR : Attempt 2/3 failed with 0 errors and: object not found
2019/05/03 14:45:41 ERROR : Attempt 3/3 failed with 0 errors and: object not found
2019/05/03 14:45:41 Failed to copy: object not found

And, for the record, -L works but that is not the behavior I am looking for

If you want to copy an individual link, then you will have to name it like this
rclone copyto -l alink.rclonelink b2:bucket/newlink

If you just copy the source directory then it should work.

I am trying to copy a list of specified files so it really looks like
rclone copy --include-from list_of_files rootdir b2:bucket

where list_of_files looks like
/file1
/alink

etc.
But you're saying my list_of_files should look like
/file1
/alink.rclonelink

where I manually add the extension to the file?
Either way, I just tested:
all of the following and it it didn't work:
$ rclone copyto -l alink backblaze:BUCKET/link
$ rclone copyto -l alink.rclonelink backblaze:BUCKET/link
$ rclone copyto -l alink.rclonelink backblaze:BUCKET/link.rclonelink
$ rclone copyto -l alink backblaze:BUCKET/link.rclonelink

I guess I am (a) missing something, (b) the documentation and expected behavior is very unclear, (c) this really is a bug, and/or (d) this just isn't possible.
From the documentation, what I would have expected is that if rclone encounters any symlink with -l, it makes the .rclonelink file when copying it. Is that not the expected behavior?

I do see it works when you copy an entire directory. I think this is a bug then. It seems to me like it should behave the same regardless of copying a single file or a directory.
Furthermore, if I do what I noted with --include-from it still doesn't work:
$ rclone copy -l --files-from list_of_files . backblaze:BUCKET

with the link called alink and list_of_files is:
/alink

Interesting, I ran with -vv and got:
2019/05/07 07:10:48 DEBUG : alink.rclonelink: Excluded

which is odd since I didn't name the file with .rclonelink
So, based on this, I renamed the file alink.rclonelink and changed list_of_files accordingly and now it worked.
Based on this empirical testing, it seems like the behavior is: (all for -l flag)

when copying/syncing a directory and rclone encounters a symlink, automatically rename the file on the remote end, leaving the local copy untouched
When copying a single file, or list of files (copy FILE or copy --include-from list_of_files) the symlink must be already named with  .rclonelink in order to be copied

Personally, I think that is very not-expected behavior. And it is very inconsistent. When rclone encounters a link with -l it shouldn't behave differently (and with a good bit of effort to rename everything)
Please don't get me wrong, I am amazed at the power of rclone and have been really happy using it and incorporating it into my code (still in testing phase so it's not in master yet). I just want to make sure I understand the behavior

If you do rclone ls -l src you'll see that rclone "sees" the symlinks as symlink.rclonelink with the -l flag.  That explains what you are seeing.
It would be relatively easy to put in a workaround if you ask for a file called "symlink" and there isn't one, rclone could look for one called "symlink.rclonelink" if -l is in effect and return that instead.
There is some discussion of this in the original issue.


Fix low contrast in css code blocks

Issue #39967
First noticed on "Divide the Grid Into an Area Template", text is hard to read due to low contrast in the css code block. Problem was discussed in the related issue, and this change was proposed to boost contrast above the minimum acceptable ratio of 4.5:1.
References: https://github.com/freeCodeCamp/freeCodeCamp/issues/39967
Checklist:

[ x ] I have read freeCodeCamp's contribution guidelines.
[ x ] My pull request has a descriptive title (not a vague title like Update index.md)
[ x ] My pull request targets the master branch of freeCodeCamp.
[ x ] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #39967

Credit to @ojeytonwilliams for suggesting the change!

Hi @EliBCC thanks for creating this.  However, that static file is redundant and is going to be removed: https://github.com/freeCodeCamp/freeCodeCamp/pull/39981. I changed how prism gets imported and forgot to clean up the old import.
The best approach is probably to create a new, higher specificity, rule in client/src/components/layouts/prism-night.css.


let author add/edit metadata (title, author)

We can use in place editing for setting .title and .author in dat.json via the desktop app!

@Kriesse assigned this to you as it'd be cool to have designs for this before working on it

Cool! In future releases, we should also have a full edit view, as inline edits come with a few accessibility issues.
Here are mockups for inline-editing, almost the same except how we handle save/cancel:
Version A (implicit Save, explicit Cancel):
Changes are saved when the user clicks out of the editable area.
Changes are dismissed when the "x" is clicked.
Edit and Save:

Edit and Cancel:

Version B (explicit Save, implicit Cancel):
The edits are saved when the button "Save" is clicked.
The edits are dismissed when the user clicks outside of the editable area.
Edit and Save:

Edit and Cancel:

I agree with an eventual full edit screen, and for now I favor version B, as it's more explicit

dependent upon having a dat.json file #255

We decided on the call to go for option B first, and see how well that works

@Kriesse it's been merged now, could you do the styling bits? Thanks!

The behavior needs a but of fine-tuning.

[ ] after click, show the current title in the editable field
[ ] give an indication that it's saving and saved (see mockup)
[ ] when clicking outside of the editable area, editing is canceled (right now only "escape" does that)

since @yoshuawuyts is out for a week I'll help with this :)

@Kriesse how shall we implement the indication for successful save?

@juliangruber " when clicking outside of the editable area, editing is canceled" does not work for me yet

@Kriesse maybe try with a fresh set of node modules? it works for me

Done! https://github.com/datproject/dat-desktop/pull/352


1.3 Update docs to reflect major new features

Remove content about obsolete features and add content about new way things work in 1.3
Go through doc set to pin down:

obsolete content
gaps
alignment to use case of driving from Edge/Stream

Closing, since we've made this a task in the epic https://github.com/criblio/appscope/issues/1352


[v0.3] Support batch json content type

The current architecture of the SDK does not support implementing batch json because of how each request is assumed to have a response.
this is changing in sdk v2. I am going to push this and we can fix it then.

Duplicate of #301


docs: updated openrpc specification

Description:
This PR updates the OpenRPC specification document to include a statement for each listed method, letting users know of the supported protocols.

Related issue(s):
Fixes #2543
Notes for reviewer:

Checklist

[x] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

replaced by https://github.com/hashgraph/hedera-json-rpc-relay/pull/2598


Clean up header includes

Forward declare classes rather than including one header in another. This will help produce better diagrams with doxygen.
This is already WIP here: https://review.gerrithub.io/#/c/376670/.

Fixed by c51ebc83cf7c8becaac08ef2aed9541e628f54c3


Fix some RSA documentation

RSA_private_encrypt(), RSA_public_decrypt(), RSA_public_encrypt() and
RSA_private_decrypt() are declared with a "const" from parameter, but
this is not reflected in the docs.

Checklist

[x] documentation is added or updated
[ ] tests are added or updated

Description of change

Pushed. Thanks.


Improve configuration of make_regular_arrays

Some improvements and changes tomake_regular_arrays:

allow to configure simulation model version on the command line (before: prod5 was hardwired)
do not generate for North and Site sites the arrays, but allow to configure the site on the command line (--site as usual) and generate regular arrays for one site only
- required to introduce a site_model flag in the configurator class
fix a bug introduced when changing the output file writing using writer.ModelDataWriter.dump. This used always args_dict[out_file], meaning that all subarray telescope lists are overwritten during the process of writing

required to add a output_file parameter to  writer.ModelDataWriter.dump to handle this case

@VictorBarbosaMartins - thanks for the quick review. I've improved the docstring in question and answered on the other issue. Let me know how to continue.


Reproducible serialisation, fixes #213

Can you please comment on what you want to achieve with this? I'd like to note that reindexing the same set of files is very likely to lead to a different index, so this is unlikely to help with reproducibility (#213).

I can understand that quarks has problems with reproducible builds, but in this case, we're using gander outside quarkus.  Topological order is fine and should be stable to lead to a reproducible index.

I'll work on additional commits to keep the index stable.

Fwiw, jandex 1.x was writting reproducible indices.  This PR restores that and avoid rewriting the index file in case it has not changed.

I'll investigate the test which fails on JDK 20, but first, let me know if you would merge this PR, else there's no point in spending time in investigating...

OK so if all the changes needed are the PrimitiveType hash code, then that seems sensible. I wouldn't want to merge such invasive changes as #72.
I would also be fine with the solution for detecting unchanged files using hash trees, as outlined in #213, but that would require bumping the index version -- so if this PR achieves reproducibility, that's even better.

OK so if all the changes needed are the PrimitiveType hash code, then that seems sensible. I wouldn't want to merge such invasive changes as #72.

Sounds good.  I can check with a larger code base if the index serialisation is reproducible if needed.

I would also be fine with the solution for detecting unchanged files using hash trees, as outlined in #213, but that would require bumping the index version -- so if this PR achieves reproducibility, that's even better.

The computation of the index is fast enough, I don't think we really need to detect unchanged files.  Not rewriting the output looks sufficient and will avoid downstream projects in reactor builds to be recompiled (because jars would have changed).

I agree -- the way I would detect unchanged files would still require building the entire index in memory. It would just skip writing it to the file if no input changed. If this PR achieve the same, I'm happy with that.

I'm merging this with an explicit statement that I do not consider index reproducibility an intentional feature that's subject to the compatibility promise. It's a best effort kind of thing that I will not hesitate breaking if required.
That said -- thanks a lot for the PR!


Remove maven dependencies on Hibernate.

Java EE API already contains JPA specification. Hibernate is an one of the implementations of JPA specification. No need to use specific implementation because everything we need is already provided by the JPA specification.

Fixed with #9.


Add grain to _parse_basic_info()

Grain is quite important for many datetime use cases. Could this be added to the DucklingWrapper method _parse_basic_info() if the results return a grain key-value pair.  The abstract DucklingWrapper is nice to use for convenience but limiting the grain makes its somewhat useless, for my use case at least.
I could make pull request to do so if you prefer.

Pull requests are always welcome :)

Pulled down. Running tests.

I integrated grain now into the wrapper as well. It will return something like
    {
        "dim": "time",
        "end": 23,
        "start": 6,
        "text": "for 2 hours today",
        "value": {
            "grain": "minute",
            "others": [
                {
                    "grain": "minute",
                    "value": "2017-05-09T16:56:00.000-07:00"
                }
            ],
            "value": "2017-05-09T16:56:00.000-07:00"
        }
    }

Released with version 1.6.0


resourcepool/namespace force removal

HI
Incase of resourcepool/namespace stuck on a termination state, currently there is no option to delete it forcefully. requesting for force remove feature

This improvement is available in the forthcoming 2.15 release which will be available soon.
For some reason, I can't link the PR and this issue ticket, but the PR is:
https://github.com/portainer/portainer/pull/7081


CVXopt package: slow to install on Azure, failed to run on Windows Machine

@dccowan : Do we still need the CVXopt package?
Here are a few things we notice during DISC Vancouver:

Slow to pip install on Azure (up to several minutes!)
We tried to install the em_examples on Nick's window machine, but the bdist_wheel install of cvxopt failed, thus preventing Nick to use it locally

closed on #98


Error:Cannot import /ComfyUI/custom_nodes/comfyui_jankhidiffusion module for custom nodes: invalid syntax (msw_msa_attention.py, line 92)

os:linux
ComfyUI-Manager: installing dependencies done.
** ComfyUI startup time: 2024-05-10 03:43:36.985964
** Platform: Linux
** Python version: 3.9.19 | packaged by conda-forge | (main, Mar 20 2024, 12:50:21)
[GCC 12.3.0]
** Python executable: /opt/conda/envs/comfyui/bin/python
** Log path: /home/ubuntu/MHF/AIGC/ComfyUI/comfyui.log
Prestartup times for custom nodes:
0.1 seconds: /home/ubuntu/MHF/AIGC/ComfyUI/custom_nodes/ComfyUI-Manager
Total VRAM 22516 MB, total RAM 63609 MB
Set vram state to: NORMAL_VRAM
Device: cuda:0 NVIDIA A10G : cudaMallocAsync
VAE dtype: torch.bfloat16
Using pytorch cross attention
Loading: ComfyUI-Manager (V2.30)
ComfyUI Revision: 2169 [0fecfd2b] | Released on '2024-05-09'
Traceback (most recent call last):
File "/home/ubuntu/MHF/AIGC/ComfyUI/nodes.py", line 1867, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "/home/ubuntu/MHF/AIGC/ComfyUI/custom_nodes/comfyui_jankhidiffusion/init.py", line 1, in
from .py import *
File "/home/ubuntu/MHF/AIGC/ComfyUI/custom_nodes/comfyui_jankhidiffusion/py/init.py", line 1, in
from .msw_msa_attention import *
File "/home/ubuntu/MHF/AIGC/ComfyUI/custom_nodes/comfyui_jankhidiffusion/py/msw_msa_attention.py", line 92
match shift:
^
SyntaxError: invalid syntax
Cannot import /home/ubuntu/MHF/AIGC/ComfyUI/custom_nodes/comfyui_jankhidiffusion module for custom nodes: invalid syntax (msw_msa_attention.py, line 92)
Import times for custom nodes:
0.0 seconds: /home/ubuntu/MHF/AIGC/ComfyUI/custom_nodes/websocket_image_save.py
0.0 seconds (IMPORT FAILED): /home/ubuntu/MHF/AIGC/ComfyUI/custom_nodes/comfyui_jankhidiffusion
0.1 seconds: /home/ubuntu/MHF/AIGC/ComfyUI/custom_nodes/ComfyUI-Manager
Starting server
To see the GUI go to: http://<IP_ADDRESS>:8188
[ComfyUI-Manager] default cache updated: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/model-list.json
[ComfyUI-Manager] default cache updated: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/alter-list.json
[ComfyUI-Manager] default cache updated: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/extension-node-map.json
[ComfyUI-Manager] default cache updated: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/custom-node-list.json
FETCH DATA from: /home/ubuntu/MHF/AIGC/ComfyUI/custom_nodes/ComfyUI-Manager/extension-node-map.json

match/case were added in Python 3.10 while you have 3.9. i refactored some stuff to use plain if statements (hopefully without breaking anything else). try updating. not sure if there are other things that Python 3.9 can't handle but that specific issue should be fixed now at least.

作业已收到。

现在还有问题没有？

现在还有问题没有？

没有问题了，非常感谢！！！！！！！

不客气啊！


cmd/compile go1.19 Fails to build generic program

What version of Go are you using (go version)?
master
$ go version
go version devel go1.19-5c8ec89cb5 Thu Jul 28 21:13:04 2022 +0000 linux/amd64
Does this issue reproduce with the latest release?
Fails on both go1.19rc2 and master. Passes on go1.18.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="off"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/user/.cache/go-build"
GOENV="/home/user/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/user/go-code2/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/user/go-code2"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org/,direct"
GOROOT="/home/user/go/src/github.com/golang/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/user/go/src/github.com/golang/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="devel go1.19-5c8ec89cb5 Thu Jul 28 21:13:04 2022 +0000"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3108614045=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Try compiling this test program
package main

import (
	"fmt"
	"testing"
)

type Bar[T any] interface{
    Blanker()
}

type FooBar[T any] interface{}

type Foo[E comparable] struct {
	me E
}

func (b *Foo[E]) do(h Bar[E], f FooBar[E]) {
	check(h, f)
}

func check[T comparable](p Bar[T], q FooBar[T]) int {
	if _, ok := p.(Checkable); ok {
		fmt.Println(ok)
	}
	if _, ok := q.(Checkable); ok {
		fmt.Println(ok)
	}
	return 1
}

type Checkable interface{}

func TestFunction(m *testing.T) {
	x := Foo[int]{me: 2}
	fmt.Println(x)
}

What did you expect to see?
Test passed.
What did you see instead?
./main_test.go:19:7: internal compiler error: assertion failed

To add a bit of context, we found this issue while testing Go 1.19 on our Go Monorepo at Uber. We noticed both master and 1.19 rc2 is breaking with some of the latest changes in our codebase that made use of generics.
The program above is a small repro we were able to isolate out of the actual code that broke.

May be a dup of #53762.

@ianlancetaylor thanks, i can confirm the failure is coming from the same place as #53762.
The repro program we posted above should help debugging the root cause.

Thanks, closing as a dup.  My understanding is that #53762 has already been fixed on tip.

@ianlancetaylor Sorry, but I don't think it has been. The program above still fails to build on tip. The latest comments in #53762 seems like there are others facing the same issue on tip.
> Will you re-open this issue or should I create a new one?

You're right, it's still crashing.  Sorry about that.
CC @randall77 @mdempsky

Tested the fix above, and it still is failing to build some generics code. I will follow up with a repro.

The repro below still fails to build with the fix above.
import (
        "fmt"
        "testing"
)

type Foo[T comparable] interface {
        FooFoo(tt []T)
}

type Bar interface {
        BarSize() int
}

func Test[T comparable](tt []T, foos []Foo[T]) {
        if len(foos) == 0 {
                return
        }
        p := FooBar[T]{fooCnt: len(foos)}
        p.getT(foos[0])
}

type FooBar[T comparable] struct {
        fooCnt int
}

func (p *FooBar[T]) getT(foo Foo[T]) {
        barSize(foo)
}

func barSize[T comparable](p Foo[T]) {
        s := 1
        if b, ok := p.(Bar); ok {
                s = b.BarSize()
        }
        fmt.Println(s)
}

func TestTest(t *testing.T) {
        tt := []int{1, 2, 3}
        foos := []Foo[int]{}

        Test(tt, foos)
}

On Go 1.18, this passes as expected.
On Go 1.19, both on tip and tip with the patch in https://go-review.googlesource.com/c/go/+/420394/

Can this fix be cherry-picked to Go 1.19 branch before the release tomorrow? Plenty of code out there will be blocked on upgrading to 1.19 until this fix is made available.


last_vrf_output and sub_window_densities missing from Archive Node schema

Description
The fields last_vrf_output and sub_window_densities used to calculate chain strength are missing from the Archive Node schema (the blocks table). Including such fields in the schema would allow for https://github.com/o1-labs/Archive-Node-API to calculate the best block to return at the tip of the network.
Could we add a migration to include this data related to all blocks in the Archive Node?

Before doing a migration, we'd need to get the fields for blocks on the berkeley net.
I've implemented that in a branch feature/vrf-out-win-sub-densities-in-archive-blocks. I'll create a PR once #12741 is merged.

@deepthiskumar can you please take a look.


fix: handle annotations in positional-only args

Annotations in positional-only args were not being handled, which resulted in contained names being interpreted as runtime usages:
from typing import TYPE_CHECKING

if TYPE_CHECKING:
    from typing import List

def func(data: List[int], /) -> None:
    ...

$ flake8 --select TC004 test.py
test.py:4:1: TC004 Move import 'List' out of type-checking block. Import is used for more than type hinting.

Hope I put the test in the correct place, let me know if it's better suited for another file 😅

This sounds like something a straight forward fix 😊 Thanks for opening the PR!
That being said, I'm on Holiday without a laptop until next Thursday 😊 So will review it as soon as I can, but most likely not until then 👍

Sounds good!
And no worries, first and foremost enjoy your holiday! 😄
I may have found a small issue or two, for which I'll likely open github issues as I'm nowhere near knowledgeable enough about AST traversal to fix them myself, but none of these are urgent in any way :)

Thanks @shiftinv! And thanks for opening the PR/issues 👍


fix(proxy-cache) handle 204/304 responses without Content-Type

Summary
According to the RFC 7231 & 7232, 204 and 304 should not have content type
header:

204 https://datatracker.ietf.org/doc/html/rfc7231#section-6.3.5
304 https://datatracker.ietf.org/doc/html/rfc7232#section-4.1

Initial commit from @adrien-f
see https://github.com/Kong/kong-plugin-proxy-cache/pull/34

@kikito  sorry to ping, Should I improve this PR ? Is something missing ?

@dndx Do you think Kong will be able to merge this fix soon ?
We have proposed this fix in May before the merge of the plugin into the Kong repo.

not interested today on my side


Home page date appears to have static value of 2/28/19

Describe the bug
I haven't checked code but the date should be advancing and appears to be static with an older date that doesn't reflect the latest on master etc.  The "2.0-preview" value may also need to be checked.
To Reproduce
Steps to reproduce the behavior:

Go to GUI home page and see "2/28/19" date and "2.0-preview" values.

Expected behavior
Users should be informed of a later version of the application being available on each home page load if I understand the intent.
Screenshots

System Configuration (please complete the following information):

OS: Windows
OS Version: [e.g. Windows 10 1803]
Application Version: [e.g. 2.0.1-beta+50af283871]
CLI or GUI: GUI

Additional Context
Add any other context about the problem here.

I'll update the static value to our official release date when we have one. I'm not exploring dynamically populating that at this time.


Inconsistent error handling in case of twine upload fails

I wanted to upload our artifacts from https://github.com/fairy-stockfish/Fairy-Stockfish/actions/runs/12547320652#artifacts
I uploaded several releases before without any problem, but today I get this:
tamas@tami:~/Fairy-Stockfish$ twine check dist/*
Checking dist/pyffish-0.0.85-cp310-cp310-macosx_10_14_x86_64.whl: PASSED
Checking dist/pyffish-0.0.85-cp310-cp310-macosx_11_0_arm64.whl: PASSED
Checking dist/pyffish-0.0.85-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl: PASSED
Checking dist/pyffish-0.0.85-cp310-cp310-win_amd64.whl: PASSED
Checking dist/pyffish-0.0.85-cp311-cp311-macosx_10_14_x86_64.whl: PASSED
Checking dist/pyffish-0.0.85-cp311-cp311-macosx_11_0_arm64.whl: PASSED
Checking dist/pyffish-0.0.85-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl: PASSED
Checking dist/pyffish-0.0.85-cp311-cp311-win_amd64.whl: PASSED
Checking dist/pyffish-0.0.85-cp312-cp312-macosx_10_14_x86_64.whl: PASSED
Checking dist/pyffish-0.0.85-cp312-cp312-macosx_11_0_arm64.whl: PASSED
Checking dist/pyffish-0.0.85-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl: PASSED
Checking dist/pyffish-0.0.85-cp312-cp312-win_amd64.whl: PASSED
Checking dist/pyffish-0.0.85-cp38-cp38-macosx_10_14_x86_64.whl: PASSED
Checking dist/pyffish-0.0.85-cp38-cp38-macosx_11_0_arm64.whl: PASSED
Checking dist/pyffish-0.0.85-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl: PASSED
Checking dist/pyffish-0.0.85-cp38-cp38-win_amd64.whl: PASSED
Checking dist/pyffish-0.0.85-cp39-cp39-macosx_10_14_x86_64.whl: PASSED
Checking dist/pyffish-0.0.85-cp39-cp39-macosx_11_0_arm64.whl: PASSED
Checking dist/pyffish-0.0.85-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl: PASSED
Checking dist/pyffish-0.0.85-cp39-cp39-win_amd64.whl: PASSED
Checking dist/pyffish-0.0.85.tar.gz: PASSED
tamas@tami:~/Fairy-Stockfish$ twine upload dist/* --verbose --repository pyffish
INFO     Using configuration from /home/tamas/.pypirc
Uploading distributions to https://upload.pypi.org/legacy/
INFO     dist/pyffish-0.0.85-cp310-cp310-macosx_10_14_x86_64.whl (531.9 KB)
INFO     dist/pyffish-0.0.85-cp310-cp310-macosx_11_0_arm64.whl (517.8 KB)
INFO     dist/pyffish-0.0.85-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (5.7 MB)
INFO     dist/pyffish-0.0.85-cp310-cp310-win_amd64.whl (363.4 KB)
INFO     dist/pyffish-0.0.85-cp311-cp311-macosx_10_14_x86_64.whl (531.9 KB)
INFO     dist/pyffish-0.0.85-cp311-cp311-macosx_11_0_arm64.whl (517.9 KB)
INFO     dist/pyffish-0.0.85-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (5.7 MB)
INFO     dist/pyffish-0.0.85-cp311-cp311-win_amd64.whl (363.4 KB)
INFO     dist/pyffish-0.0.85-cp312-cp312-macosx_10_14_x86_64.whl (531.9 KB)
INFO     dist/pyffish-0.0.85-cp312-cp312-macosx_11_0_arm64.whl (517.9 KB)
INFO     dist/pyffish-0.0.85-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (5.7 MB)
INFO     dist/pyffish-0.0.85-cp312-cp312-win_amd64.whl (363.4 KB)
INFO     dist/pyffish-0.0.85-cp38-cp38-macosx_10_14_x86_64.whl (531.9 KB)
INFO     dist/pyffish-0.0.85-cp38-cp38-macosx_11_0_arm64.whl (517.8 KB)
INFO     dist/pyffish-0.0.85-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (5.7 MB)
INFO     dist/pyffish-0.0.85-cp38-cp38-win_amd64.whl (363.4 KB)
INFO     dist/pyffish-0.0.85-cp39-cp39-macosx_10_14_x86_64.whl (531.9 KB)
INFO     dist/pyffish-0.0.85-cp39-cp39-macosx_11_0_arm64.whl (517.8 KB)
INFO     dist/pyffish-0.0.85-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (5.7 MB)
INFO     dist/pyffish-0.0.85-cp39-cp39-win_amd64.whl (363.4 KB)
INFO     dist/pyffish-0.0.85.tar.gz (317.5 KB)
INFO     username set by command options
INFO     password set from config file
INFO     username: __token__
INFO     password: <hidden>
Uploading pyffish-0.0.85-cp310-cp310-macosx_10_14_x86_64.whl
100% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 576.5/576.5 kB • 00:00 • 1.0 MB/s
INFO     Response from https://upload.pypi.org/legacy/:
         400 'License :: OSI Approved :: GNU General Public License v3 or later (GPL-3.0-or-later)' is not a valid classifier. See
         https://packaging.python.org/specifications/core-metadata for more information.
INFO

           <title>400 'License :: OSI Approved :: GNU General Public License v3 or later (GPL-3.0-or-later)' is not a valid classifier. See
         https://packaging.python.org/specifications/core-metadata for more information.</title>

400 'License :: OSI Approved :: GNU General Public License v3 or later (GPL-3.0-or-later)' is not a valid classifier. See
         https://packaging.python.org/specifications/core-metadata for more information.

           The server could not comply with the request since it is either malformed or otherwise incorrect.

         'License :: OSI Approved :: GNU General Public License v3 or later (GPL-3.0-or-later)' is not a valid classifier. See
         https://packaging.python.org/specifications/core-metadata for more information.

ERROR    HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/
         'License :: OSI Approved :: GNU General Public License v3 or later (GPL-3.0-or-later)' is not a valid classifier. See
         https://packaging.python.org/specifications/core-metadata for more information.
tamas@tami:~/Fairy-Stockfish$ twine --version
twine version 6.0.1 (keyring: 24.3.1, pkginfo: 1.10.0, requests: 2.31.0, requests-toolbelt: 1.0.0, urllib3: 2.0.7)
tamas@tami:~/Fairy-Stockfish$

The error message is clear with the problem - the classifier updated 2 days ago is non conformant with the allowed classifiers.
See https://pypi.org/classifiers/

You are absolutely right. I completely forgot about that change, sorry for the noise.
I have to note that twine error handling could be better and cleaner.

twine check passed. I expect it to tell me about this error early, not in twine upload phase.
The response formatting could be better somehow.
First it about the license in a paragraph started with "INFO", then comes another "INFO" paragraph and finally an "ERROR"
As a Python programmer I find this a bit confusing.

Those issues probably belong in the twine issue tracker here instead: https://github.com/pypa/twine


USB passthrough

Description
Is there a way to make RT1176 passthrough usb directly to coral accelerator, since usb acceleration is out of stock.
Click to expand!
Issue Type
Others
Operating System
Linux
Coral Device
Dev Board
Other Devices
No response
Programming Language
C++
Relevant Log Output
No response

I think, you are referring to i.MX RT1176 uCOM module. We don't have any devices other than the Coral USB accelrator module to directly connected to host machines via USB. If possible, feel free to prototype and integrate the Coral Accelerator Module into your custom PCB hardware design.

I mean this https://coral.ai/products/dev-board-micro, is there possibility to turn this into usb accelerator without buying one specially made for it.

No, its not possible.


Error: 'module' object has no attribute 'module', Why?

As described by the title:
>>> import mxnet as mx
>>> mx.mod
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'mod'
>>> mx.mod.Module
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'mod'
>>> mx.module
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'module'
>>>

try update your mxnet to latest version
On Thu, Jun 30, 2016 at 6:55 AM dengdan<EMAIL_ADDRESS>wrote:

As described by the title:

import mxnet as mx
mx.mod
Traceback (most recent call last):
File "", line 1, in
AttributeError: 'module' object has no attribute 'mod'
mx.mod.Module
Traceback (most recent call last):
File "", line 1, in
AttributeError: 'module' object has no attribute 'mod'
mx.module
Traceback (most recent call last):
File "", line 1, in
AttributeError: 'module' object has no attribute 'module'

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dmlc/mxnet/issues/2582, or mute the thread
https://github.com/notifications/unsubscribe/ACdUIMkHWMX0KE1fmwfJKwavm2o7ZRKAks5qQ8rkgaJpZM4JCL1X
.

Oh, I see. My mxnet was installed months ago. The 'module' was added long after my installation. Thank you.

fixed #2582


Show amount of storage used by Object Storage on Object Storage page

It would be handy to have the amount of storage currently used by the account's object storage showing on the object storage page.

Hey @Oloryn, I agree this would be handy. We've been discussing ways we could expose this info in our API, and thus display it in Cloud Manager. I don't have specifics to share on a timeline, but I've noted your request and will update this issue as details become available.
In the meantime, you can use a tool like the Linode CLI to view the size of each bucket:
$ linode-cli obj du <bucket_name>

For more info on using Object Storage with the Linode CLI, see https://www.linode.com/docs/platform/object-storage/how-to-use-object-storage/#linode-cli.

+1 for this

I am considering using the object storage product, but I find it concerning that there doesn't appear to be a way for me to see the total amount stored. Especially considering this is a billable metric.

Thanks @andysh-uk and @kanongil; I've noted your interest in this feature in our internal tracker.
I do want to underscore that it's possible to see your total Object Storage usage with other tools like the Linode CLI (example above) or s3cmd:
$ s3cmd du

You can find more info on Object Storage tooling at https://www.linode.com/docs/platform/object-storage/how-to-use-object-storage/

Thanks @johnwcallahan, I do hope you get this in the UI soon though; it’s a pain having to drop into the CLI when most other operations can be done in Manager.
If linode-cli can surface this information, does this mean it’s available in the Linode API?

I just tested your linode-cli workaround, however it is not a viable solution. I timed a run, and it took 3m 44s to complete, and used heaps of cpu and bandwidth in the process.
FYI, I'm still only using 1/8'th of what I plan to use, so it will likely take take ~30 mins to complete by then!
Again, this is a billable metric, which should be readily available in your system.

@kanongil What have you got stored in S3 storage  that it's taking that long?  Using either the s3cmd or the linode-cli workaround, etiher from home or from one of my linodes, it takes me no more than 3 seconds of run time,  and I've got about 72GB of storage in use (in about 1100 files).  Only thing I can think of is perhaps you have a huge number of small files?

Huge number of files, yes.
FYI, I found that ceph seems to be able to expose the storage size through the swift API: https://docs.ceph.com/docs/mimic/radosgw/swift/serviceops/#list-containers

It's true that if you have a huge number of files the calculation that tools like s3cmd does is going to take a while.
Fortunately it looks like we're going to be able to add this to the API/Cloud very shortly; I'll keep you posted.

Amazing, thank you @johnwcallahan and @adammohammed  😊

This make me very happy, look forward to it hitting live.  Thanks @johnwcallahan @adammohammed 😄

These changes were just released. There is now a "Size" column on the Buckets table:

You can see the full release notes of v1.13.0 here.

Brilliant, looking good 😄 👍
Thanks again guys


Datastream infinitely recurses on some fundamental types in eosiolib

These specializations catch too much, as they will take any type that is not specialized above and expect that it is a magic-reflectable type.  In the case of a type (exactly) like int this will mis-detect int as a struct with a single member of type int and recurse into itself:
https://github.com/EOSIO/eos/blob/24cfeca84800d7ac17ef99f0de45e1a1cbb80a8d/contracts/eosiolib/datastream.hpp#L619-L632
ATC: contracts using the EOSIO_API and EOSIO_SERIALIZE macros can operate on types like int without causing stack or memory exceptions

Pull request https://github.com/EOSIO/eos/pull/2264 created to fix the pointer type cases (try to serialize pointer type using datastream will result in compile error). Add unit test cases.


Missing JavaScript.tmLanguage in Sublime 3

When installing the plugin in Sublime 3 (on OSX) I received the following message on opening Sublime:
Error loading syntax file "Packages/Better JavaScript.sublime-package/JavaScript.tmLanguage": Unable to open Packages/Better JavaScript.sublime-package/JavaScript.tmLanguage

Since there is no dir Better JavaScript.sublime-package creating a symlink to Better JavaScript fixes this issue. ( ln -s 'Better JavaScript'/ 'Better JavaScript.sublime-package'  )

@isliliye Thanks!

+1

thanks @isliliye  !!!!

Thanks a lot @isliliye ! Pretty sure you saved me a ton of time here :-)

+1

Thanks isliliye!

@isliliye Awesome. Thanks.


Add exclude_columns to ToDatetimeTransformer

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

Project coverage is 100.00%. Comparing base (7d300bd) to head (bcb00d6).
Report is 21 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #298   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           41        41
  Lines         1071      1071
  Branches        41        41
=========================================
  Hits          1071      1071

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


support for auto heirarchy

Old Definition
The old way of auto works the same way. i.e. by defining auto in features
example:
# initial definition
ipv4:
# other parameters
 dst:
  x-field-pattern:
    format: ipv4
    default: <IP_ADDRESS>
    features: [auto, count]
  x-field-uid: 1

# after expansion by openapiart
Pattern.Ipv4Pattern.Ipv4.Dst:
  type: object
  properties:
    choice:
      type: string
      x-enum:
        value:
          x-field-uid: 2
        values:
          x-field-uid: 3
        auto:
          x-field-uid: 1
        increment:
          x-field-uid: 4
        decrement:
          x-field-uid: 5
      default: auto
      x-field-uid: 1
      enum:
      - value
      - values
      - auto
      - increment
      - decrement
    value:
      type: string
      x-field-uid: 2
      default: <IP_ADDRESS>
      format: ipv4
    values:
      type: array
      items:
        type: string
        format: ipv4
      x-field-uid: 3
      default:
      - <IP_ADDRESS>
    auto:
      description: |-
        The OTG implementation can provide a system generated
        value for this property. If the OTG is unable to generate a value
        the default value must be used.
      type: string
      x-field-uid: 4
      default: <IP_ADDRESS>
      format: ipv4
    increment:
      $ref: '#/components/schemas/Pattern.Ipv4Pattern.Ipv4.Dst.Counter'
      x-field-uid: 5
    decrement:
      $ref: '#/components/schemas/Pattern.Ipv4Pattern.Ipv4.Dst.Counter'
      x-field-uid: 6

New Definition
The new definition allows auto to be hierarchical.
only valid property inside auto allowed till now is ref , which points to a object in the yaml
# initial definition
ipv4:
# other properties
 dst:
  x-field-pattern:
    format: ipv4
    default: <IP_ADDRESS>
    features: [auto, count]
    auto:
      $ref: "#/components/schemas/AutoIpOptions"
  x-field-uid: 1

AutoIpOptions:
description: |-
  The OTG implementation can provide a system generated, value for this property. If the OTG is unable to generate a value,
  the default value must be used.
type: object
  required: [choice]
  properties:
    choice:
      type: string
      x-field-uid: 1
      x-enum:
        static:
          x-field-uid: 1
        dhcp:
          x-field-uid: 2

# after expansion by openapiart
Pattern.Ipv4Pattern.Ipv4.Dst:
  type: object
  properties:
    choice:
      type: string
      x-enum:
        value:
          x-field-uid: 2
        values:
          x-field-uid: 3
        auto:
          x-field-uid: 1
        increment:
          x-field-uid: 4
        decrement:
          x-field-uid: 5
      default: auto
      x-field-uid: 1
      enum:
      - value
      - values
      - auto
      - increment
      - decrement
    value:
      type: string
      x-field-uid: 2
      default: <IP_ADDRESS>
      format: ipv4
    values:
      type: array
      items:
        type: string
        format: ipv4
      x-field-uid: 3
      default:
      - <IP_ADDRESS>
    auto:
      $ref: '#/components/schemas/AutoIpOptions'
      x-field-uid: 4
    increment:
      $ref: '#/components/schemas/Pattern.Ipv4Pattern.Ipv4.Dst.Counter'
      x-field-uid: 5
    decrement:
      $ref: '#/components/schemas/Pattern.Ipv4Pattern.Ipv4.Dst.Counter'
      x-field-uid: 6

Go snippet to set hierarchical auto
Config.Ipv4().Dst().SetValue("<IP_ADDRESS>")
Config.Ipv4().Dst().Auto().Static()
Config.Ipv4().Dst().Auto().Dhcp()

Python snippet to set hierarchical auto
Note: python SDK exposes choice as of now unlike go SDK and also choices with no properties does not have a getter yet
config.ipv4.dst.value = "<IP_ADDRESS>"
config.ipv4.dst.auto.choice = "static"
config.ipv4.dst.auto.choice = "dhcp"

@Vibaswan : Please change the examples to point to a single field such ipv4.src instead of ipv4.

@Vibaswan : Please change the examples to point to a single field such ipv4.src instead of ipv4.
Another query : How will the description be generated ... will it use the description if supplied by the model author ?

@apratimmukherjee corrected the examples
Yes the description in auto hierarchy will be provided by the user , it should be mention in the object auto is referring to , updated the example as well

models link where auto hierarchy is been used
https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/open-traffic-generator/models/traffic_over_dhcp_interface/artifacts/openapi.yaml&nocors#tag/Configuration/operation/set_config
ipv4_yaml changes
https://github.com/open-traffic-generator/models/pull/372/files#diff-b4e391ad7a6920f2c2eb0175634e1655ee8d42bdd7db74e833b99448f8de2116R115


Correct drivers position in uefi (surya) and add initial support for r5q

Description
Surya:
The state is the same but now everything is more orderly
R5Q:
Now has initial support and is able to boot uefi correctly
Checklist

[ y] Have you tested the change you are submitting?
[ y] Is the commits history nice and clean?

Please split r5q and surya into their on separate commits.


Multiple Slack Channels

Is your feature request related to a problem? Please describe.
I'm running botkube as a PoC for my company, we have one cluster per team for non-prod environments & one cluster per team for prod environments, each team wants to be able to manage only their clusters.
This poses a problem because @BotKube doesn't have awareness of the channel and allows running kubectl commands for all clusters it knows about and running ping will give the user the list of all clusters configured.
Describe the solution you'd like
I'd love for botkube to be able to work on multiple slack channels while keeping context of each of them, specifically, I would like to have separate botkubes that have access to only one cluster in a single Slack workspace
Describe alternatives you've considered
I tried to find a way to add multiple botkube instances to slack but adding to a Slack workspace will always render the same token.
I have added botkube to a few channels but all channels have  access to all clusters
Additional context
Having this would allow me to manage all my clusters and allow my teams to manage their clusters separately without them needing either kubectl or having access to clusters not their own
I found this ticket that seemed to describe something similar, however, it's not the same request

The token for botkube slack app will always be the same, its not related to the channel value. Both of those are stored in botkube-communication-secret. For now the workaround would be to create another deployment for botkube, that for communication uses diffrent secret, with the same token, and diffrent channel.

I'd like to send errors to a specific channel, and the chaff to another, so I am in the same boat.

Well, I would like to have a same feature.
We use BotKube in our Slack to notify about Deployment tool status directly to responsible person<EMAIL_ADDRESS>instead of channel.
It would be great, if BotKube could mention status to more persons and also public channel.
For example like this:
slack:
    enabled: true
    channel<EMAIL_ADDRESS><EMAIL_ADDRESS>"devel-status"]

Use case for sending event one channel vs kubectl access to another.

Well, I would like to have a similar feature.
We use BotKube in our Slack to notify about Deployment tool status directly to responsible person<EMAIL_ADDRESS>instead of channel.
It would be great, if BotKube could mention status to more persons and also public channel.
For example like this:
slack:
    enabled: true
    channels<EMAIL_ADDRESS><EMAIL_ADDRESS>"devel-status"]

Since you already have it going to a dedicate person did you try using @slack_group?

I would love to be able to route functionality to different channels instead of all in one without needing to run multiple deployments.
Events could go to a certain channel, k8s commands another. etc

related https://github.com/infracloudio/botkube/issues/508 ?

This issue is not related strictly to the multichannel support as defined in https://github.com/infracloudio/botkube/issues/596.
Here is the main difference:

I'd love for botkube to be able to work on multiple slack channels while keeping context of each of them, specifically, I would like to have separate botkubes that have access to only one cluster in a single Slack workspace

Currently, you are able to do that:

to limit the kubectl executor access, add --set config.settings.kubectl.restrictAccess=true during Helm chart installation (or put this in values.yaml).
to send the notification, just specify a proper communication.slack.channel per deployment.

Findings
However, this solution has a few problems:

It works only if you will deploy one BotKube per cluster/channel. But it's what you asked for.

The @BotKube ping command returns information about all registered cluster, even if a given channel is not authorized with a given channel. IMO, it's a bug.

If you send the @BotKube get po --cluster-name prod from a channel that is not authorized, you will not get any response. IMO, it makes pure UX experience. It should print sth like:
Cluster "prod" is not registered or channel is not authorized to access it.

Related issue: https://github.com/infracloudio/botkube/issues/402

If you use the botkube.io/channel: <channel_name>, notifications are sent to a given channel even if not authorized. IMO, it's a bug.
However, fixing this is problematic as we will need to do that base on config.settings.kubectl.restrictAccess and if it is set to true, allow only communications.<name>.channel. It will be better to postpone that until BotKube will support multiple channels per single configuration. For example:
slack:
  enabled: true
  channels: ["@foo", "@bar", "devel-status"]

Action Items

Fix bugs:

The @BotKube ping should return only clusters that are authorized clusters with a given channel.
If the botkube.io/channel: <channel_name> annotation is used, send notification only if a given channel is authorized. Do that after https://github.com/infracloudio/botkube/issues/596.

Improve UX:

If cluster is not authorized, instead of ignoring, send info:Cluster "prod" is not registered or channel is not authorized to access it.

Hi all,
Closing as the requested features along with the UX improvements were implemented in https://github.com/kubeshop/botkube/issues/596.
When it comes to resource annotations, I put the requirements in an aggregated task for reworking the feature: https://github.com/kubeshop/botkube/issues/690
Feel free to reopen the issue or create another ones with a description of what's missing in the new configuration features, after trying out BotKube 0.13. It's just around the corner, so stay tuned!


Error ignoring mesage seven with "true" in the .env file

@solution01 You gotta leave it at false to disable this messages


Failed to parse the package from xxxx

Brief description of your issue
I try to follow the document to use the wingetcreate new.
However, I got the error as follows
Downloading and parsing: https://github.com/jayhuang75/rust-cli-med/releases/download/0.6.2/med-0.6.2-x86_64-windows-msvc.tar.gz... Failed to parse the package from [https://github.com/jayhuang75/rust-cli-med/releases/download/0.6.2/med-0.6.2-x86_64-windows-msvc.tar.gz]
And the version I have
 wingetcreate -h Windows Package Manager Manifest Creator v<IP_ADDRESS>
Can I get some guidance on what format the URL should be? Currently, the tar.gz file contains only the exe file.
URL: https://github.com/jayhuang75/rust-cli-med/releases/download/0.6.2/med-0.6.2-x86_64-windows-msvc.tar.gz
Thank you again.
Steps to reproduce
wingetcreate new
Expected behavior
process continuous
Actual behavior
However, I got the error as follows
Downloading and parsing: https://github.com/jayhuang75/rust-cli-med/releases/download/0.6.2/med-0.6.2-x86_64-windows-msvc.tar.gz... Failed to parse the package from [https://github.com/jayhuang75/rust-cli-med/releases/download/0.6.2/med-0.6.2-x86_64-windows-msvc.tar.gz]
Environment
winget --info
Windows Package Manager v1.4.11071

wingetcreate -h
Windows Package Manager Manifest Creator v<IP_ADDRESS>

Turn out the URL package needs to be in the zip format. Thank you.


Different geometry got using deepcopy

Expected behavior and actual behavior.
I got a GeometryCollection containing a LineString when I tried to deepcopy a GeometryCollection containing a LinearRing.
Steps to reproduce the problem.
import shapely
import copy

lring = shapely.LinearRing([[0,0],[0,1],[1,1],[1,0]])
geomcollection = shapely.GeometryCollection([lring])

print(geomcollection)
print(copy.deepcopy(geomcollection))

Output:
GEOMETRYCOLLECTION (LINEARRING (0 0, 0 1, 1 1, 1 0, 0 0))
GEOMETRYCOLLECTION (LINESTRING (0 0, 0 1, 1 1, 1 0, 0 0))

Operating system
Windows 11
Shapely version and provenance
2.0.1 installed from PyPI using pip

Yes, deepcopy essentially pickles/unpickles the object (if the object does not define __copy__ and __deepcopy__), and so what you see is a limitation of (or I would actually call it a bug in) the way we pickle geometries.
Pickling shapely objects generally relies on WKB (de)serialization, and this has some limitations, as you list. We actually work-around the specific limitation for LinearRings by having a custom reduce method there:
https://github.com/shapely/shapely/blob/5c4670bbbac54fffddbabac202efdecdc445317d/shapely/geometry/polygon.py#L113-L116
But this only works for LinearRings itself, and not for LinearRings that are contained within a GeometryCollection.
Relying on WKT has its own set of limitations (eg loss of precision of coordinates), and is slower. So I think we certainly want to stick to WKB.
One possible fix for GeometryCollection would be to pickle its list of children geometries, although not sure if that would not cause other corner cases.

Side question: what is your use case of wanting to deep copy the geometry objects? Starting with shapely 2.0, geometries are now immutable, so there generally shouldn't be a need to copy them.

Thanks. Deep copying that Feature object will then recursively copy each of its members, and thus also the geometry; that makes sense.
In any case, also for pickling GeometryCollections in itself, I would consider this a bug, since ideally pickling always gives a faithful roundtrip (although having GeometryCollections with LinearRings is probably a rather corner case)


Rename 'closed' parameter of 'latLngsToCoords' to 'close' to avoid confusion

I noticed the use of the parameter name closed in latLngsToCoords when looking at the changes or PR #7344.
But I got confused on what the usage is regarding this parameter as it suggests (because on the fact it's a noun) it states something about the current 'status' of the coords (latlngs parameter) being passed to the function.
Therefore I think it's better to change the name to close...

It is named closed because the argument needs to be true if the shape is closed.

But when I look at the function, with shape you mean the latlngs parameter?
If so, when I look at the closed is interpreted, it actually closes (an action) the newly (based on the latlngs) created shape, so that the created shape is actually 'closed'.
So basically inside the function, a close action is performed on the shapedata to close it, creating a closed shape...
Therefore I suggest renaming the parameter from a 'noun' to a 'verb' as it gives a more clear understanding...

Please revert the changes of replacing tabs with spaces.

Sorry about the spaces, used the wrong editor.

Thanks!


[RFC] show the issue when it is created

After an issue is opened there is no feedback from the command line
that the issue is created correctly, so this is calling show_issue to
print the issue result on the command line.
Also, I'm proposing a new show issue format on the terminal
because the previous one looks a little bit odd to me in
comparison with the other rad commands.

Mh the CI error looks like a little bit odd to me
thread 'rad_issue' panicked at '
--- Expected
++++ actual:   stdout
   1    1 | ╭─ flux capacitor underpowered ───────
   2    2 |
   3    3 | Flux capacitor power requirements exceed current supply
        4 +
   4    5 | ╰─────────────────────────────────────
   5    6 | state: open
   6    7 | tags:
   7    8 | assignees:

Exit status: 0
', radicle-cli-test/src/lib.rs:210:40
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

but on my system, this is building correctly, looks like the description is parsed in a different way?

You added a call to trim, perhaps that's the issue?

You added a call to trim, perhaps that's the issue?

Not sure the I should not call the trim because it is called already down into the call stack, so I do not have idea why this is happening


azuresu

replace azure_superuser which was in single server with azuresu which is now in Flexible server.

@kabharati
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Implement QuadraticBezierCurve and MANNAutoregressiveInputBuilder

This PR implements the MANNAutoregressiveInputBuilder that is required to easily generate input for MANN from a joypad. The class does not depend on the joypad since it requires only two vectors. The desired motion direction and the facing direction.

I applied the modification you suggested, @S-Dafarra you can check again it 😄


##[error]The requested REST API version of 6.1 is out of range for this server. The latest REST API version this server supports is 6.0.

I am getting this error while using rigger Azure DevOps Pipeline extension

Could you share the complete log file? After a run with the system.debug variable set to true

Hi @maikvandergaag
I added this task in my release pipeline. Can you help me where to set system.debug in release pipeline

Just at it as a variable to the pipeline with the value true

extension_debug.txt

@maikvandergaag
Any idea why it is throwing the error?

@Yaseen17: Yes you are using a internal hosted Azure DevOps instance. It looks like the api version 6.1 is not installed there.

is updated


FileNotFoundError: [Errno 2] No such file or directory: '/data/kitti/Kitti/sequences/00/calib/000000.txt'

Where can I download Kitti/sequences/00/calib/000000.txt?

https://s3.eu-central-1.amazonaws.com/avg-kitti/data_odometry_poses.zip

@fzhiheng  Thanks for your amazing work!
The above link is not a download link for Kitti/sequences/00/calib/000000.txt. I find the calib file in /KITTI/training/calib/000000.txt， but when use the calib file，I can not get right results for "camera2world_all", and the python train.py running error.
I can run success for nuscene dataset.
can you give some advice about kitti odometry calib file?  @wadefrank @fzhiheng  Thanks


Create initial extension project

empty project based on autorest-extension-base
make sure the project compiles

this seems to be done


Handle float counts + warn users

Fixes #782.
This primarily handles getting counts like {"01": 500.0, "10": 500.0}, where they're already whole numbers. For float results more generally, I claim it's enough to warn users since we also offer service.get_counts as a public method, but I'm open to ideas about how else to address this.
(Seems like we can't get around cirq.ResultDict needing a list/array of results for the measurements param, and we can't append half or a quarter of an array element...)

one more weird case we might need to consider (thanks to convo w/ @paaige) - i think qiskit's quasi-probabilities can sometimes be negative?

one more weird case we might need to consider (thanks to convo w/ @paaige) - i think qiskit's quasi-probabilities can sometimes be negative?

Yeah, I've been doing experiments using the runtime sampler (which returns quasi probability distributions) and have had to filter out negative results.

one more weird case we might need to consider (thanks to convo w/ @paaige) - i think qiskit's quasi-probabilities can sometimes be negative?

Yeah, I've been doing experiments using the runtime sampler (which returns quasi probability distributions) and have had to filter out negative results.

Right good points -- I added another warnings case for negative counts.


Add keyboard selection for key remapping

Is it possible to specify the keyboard where the key remapping will happen?
This is quite useful for notebook users who also have a full keyboard in office, the keyboard mapping is only needed for the build-in keyboard of his/her notebook computer, not the normal full keyboard.
Thank you!

Unfortunately it's not currently possible to do with public APIs, and is at the driver level. we're hoping that changes but in the meantime this isn't in the plans for v1. We understand the use case and hope we can push this feature sometime soon!
closing as duplicate as well: #1460


Handle "Back" button after "Already configured" error

When eduroam was already configured, the user correctly gets an error message about this. However, pressing "Back" after this error causes the app to soft-lock on an empty screen. When #71 is fixed, this should be easier to remedy, because the user should go back to the institution screen, so they can try again.

This bug is particularly bad on the OAuth flow, where pressing Back will take you to the "We are configuring your device" page, which gives the user the impression that something is happening, while nothing is happening.

Fixed in commit 5e703027537ea871bcc4de328a61a3a85b394021


sc_client::Client (now sc_service::Client) no longer publicly accessible?

I updated which commit I was pointing at recently, to find that places where I was using the client are now broken since it's hidden behind a "test-helpers" flag. What's the intention behind that change?
Even enabling the flag, using it is still fairly challenging. This is what I ended up having to do (working from the node template):
type ConcreteBlock = opaque::Block;
type ConcreteClient<E> = Client<sc_client_db::Backend<ConcreteBlock>, E, ConcreteBlock, RuntimeApi>;

pub struct ClientUser<E> {
    client: Arc<ConcreteClient<E>>,
}

and in my service definition:
/// Builds a new service for a full client.
pub fn new_full(
    config: Configuration,
) -> Result<
    impl AbstractService<
        Block = ConcreteBlock,
        Client = ConcreteClient<impl CallExecutor<ConcreteBlock>>,
        Backend = impl sc_client_api::Backend<ConcreteBlock>,
        CallExecutor = impl CallExecutor<ConcreteBlock> + Clone + Send + Sync + 'static,
        SelectChain = impl SelectChain<ConcreteBlock>,
    >,
    ServiceError,
> {
    new_full!(config).map(|(service, _)| service)
}

That type declaration is... rough.
This is also dramatically simpler than it was from when I tried avoiding using Client directly because of the new flag. I eventually had to give up, seemingly what I needed to do was just not possible any longer, which is use https://substrate.dev/rustdocs/master/sc_client_api/backend/trait.StorageProvider.html#tymethod.storage
But since AbstractService does not have StorageProvider as a bound on it's associated Client type, you simply cannot get a client out of it that implements StorageProvider unless you actually say (as I did above) that the associated Client is an instance of sc_service::Client -- because StorageProvider is only implemented on the actual Client struct.
Seemingly the Client should be public, I'm not sure why it's behind this flag now - alternatively Client could be a pub trait, and there can be a private Client struct, and things like StorageProvider should be blanked implemented on the trait Client rather than struct Client.
Please let me know if this isn't how the client is intended to be used, but this seemed fine before and was pretty tough to work through the changes.

You could do what we are doing in Polkadot.

@bkchr Thanks for pointing that out - at least demonstrates how to not need to pull in the Client struct specifically (at least, I think, I'm still not sure that approach is going to work since I need something that impls StorageProvider).
Overall though, the fact that you need about ~30ish lines to even define what a usable client type looks like is probably less than ideal. The goal of having different bits of functionality be mix-and-match-able is a good goal, but I've got to wonder if there's some overall simplification that could be done here. If not, having some good docs around how this is supposed to work would go a long way.

CC @seunlanlege


[Addition]: 35 PantherX Hotspot cluster asserted in Civitavecchia, Italy

Hotspot b58 Addresses
11heGQJzqV698x3kz11eS7JNey7kv494WjzJyzv4JjajTQ4Vhkp
1124DotsvZt6KRzseXNV2aRhbC1aVkDmYJYHSLJtt6XaFdoQBMNH
11uxXXKDX4AZa5DQGqCvkpwbBAgDQxZUzYT3KBJ2cqQjpYhTNZb
1126ATg6qvsagiz21USpu6QG6fdKxUaBBvitRsmT1WDVtAvFdyRo
112s3yCtu3RouuKceH2q9BaZEa73ztLr9tYcGXvRq4t6SLoVGZCd
112Bj2wo48ruij8WyJF2sQBVUcF3jp6cZxEycaYZbWTG2a7VMfnh
112NnQ8B3Z5Uq6gpFNCeSSx9qzisqRYwbDbCgmUC33Aznqj26bSY
112UxX9EmCcXRLB2kNVbxAvvQjHfposKVzgG7Yk6g7QZdMuZGbQv
112wZXS1Bvp21a3YnCiooiHndv2hzMyMbrYTYRVBy5K56LYXWhvF
1125aesre5F3U98iSvPWYzHhLwKg1q1TGRcSNP77fHEG37rfBGTt
112ht57FfFaUkg6wga1yocktomtPTv4ikqMA7kLLUDjR3ZfQx7mA
112QrBgRFU1q7EnWNseFJRVPskCYbUE52p6Ew2AsS2AxWj7Qrag2
112774kwUmTU4XT3ekvPu2kSzjMz939BV3Tkm8DHMjSXi7EWuSnp
11VAEyBLbb3x55Wh23aX7DKqzDvgrh2ufW5FEbAQGK2fifhuFUe
11isPeRvgUPro3mGc2HekKTnUj68DpUaaog55E9J3N7KE7W7DJg
11aFf1sGF16wzdmJjd6GwfVJGXZsMBGyDkST7utAcAGkLBQyoW9
112RaSX1CXMCAgLYrrqEq4zqB2A7oznkUDdeT6nx9ZXLRmwJ9rW8
11jLjkLW91WApG5dizQFisBKVAn4deF78n6EVPh85VQPftYxJwT
1125qv9UkJ2NoQBcUGpFVEsaGQivVz4r3Q9veGK1P1ap6iyzp2nJ
11phL6SL6Tk9jVzDZQ1GV4umhYyJgBeEgJCyQtB64V5HBvtjvA3
119ANcg7a7Rvtw2GkpwPmyGz9twDGu5THKdMSrBiN5Z983kvWxQ
11pJEeQT4SBN3j6D8wY1Xtx8q5xBaRnfCecE6qJVJ6xRncjWaM8
11XEL9eP9RheRebMD3pShL8zmWxCoeDHFdn2ev1i2YFvtoUx4x2
112REvuQ1BLb7Lpt8sYVG3eq5fyykKhKoNqUABWr78BBED1CXKH2
112rwhJH1XQL9zQm5YL8BbKqPCrk6jbJePc9FkdYY3UrxtANjgi1
11UNn2niw8JK93WCpxjNYJePAjBvkPgymXxHkwQsHncSeHXWZXA
11BYWb53ZBzjQKVfoQ3iXS7X2enuj3PWzqdtF5KfSL1ptgc5zr3
1165BRKB98Vg9ENhkMwogheu5SRcD3fpSCZ16AqPxHtfWYwB1X5
112AQitoxzsC84Jr7khYaCFANzZ4nckdgysFNc3J6FgBnvH1cQcW
11RWiSKSfs1D39t23XuTD2ZLQPV59ts8a4SnmnPDSuRkQACHryK
11dU3m96fJgkrbvg5ZvvJQ3hWEcVNYt2zdL19aH6evPDNuBsGAm
112cMGqSbykHgiTuxPG8bjQBB696hSW6hbjgZofEi9nFy6aSRYhd
11qMHUrF3F4eoDf4HDurS8pAkvwSUfvZHzbJWj3pnWcjmpqecKR
112gFLHkFtVYoeJbQHRY7J4QPLdnbYiWa1L1T15x3T3iRStpiHy
1123oXw9viSsssdy48s9uovspv2TJGvV59BUB3MeJCNaf7gxP6UQ
Discord Handle
radical#5327
Reason(s)
Until recently, this area only had two hotspots.  As of a couple of weeks, these 35 hotspots were asserted nearby, but have only witnessed each other, never witnessing or being witnessed by the local hotspots.

All hotspots are distributed amongst these wallets:
13GQ71LVZkZzwZBP8YogTAeLUP9Hty5mxph2vcZv8PMMMg8H9BY
13gUz8gtAQ4gSDcXs6VKNosuQ9tog17VAHXcsPSQhSooU2PwG7A
13jSnKGRivVRNmbi4VAAkbia1mUz6kyxcj9M5XR2nXRWj5SahUD
13VNacsQ7RuCZs8BsQvTX8jfWcgdErBqm7a5QEmiMh6tsqcyyzG
13Z3CbPAcqg8LjiYdN6k8ohpQo7E91FMz2ShvJY7guQhhQPDQ3L
13zMViySuEkTmtU8KVEjyy2itQhnWhPQd7ST9iUf2ue9RXY7iC9
14cv6punzFWy87Mtc7sK9E3WY7Mak5hiaM3hDaP3wRkkv7PPh14
14H9DheRQWUm1JXKccXmkdBBGgzcAqYXY7Ad5gHwEcPTzxZs225
14iCTU3eCrusypuJMpjxn76p4ZgpWkCHjkVZJ4F1hy1kShUS53P
14nfM8RGurDccuwiMNudf3zNhwFTGh8s1ZmKqiB6RyadWwTXBPc

I queried the ETL database to find unique witnesses within the group with the following parameters:

22 days back from today
Following 6 hops
Starting hotspot address 112774kwUmTU4XT3ekvPu2kSzjMz939BV3Tkm8DHMjSXi7EWuSnp

The results remain limited to the 35 hotspot set listed above.  This would be highly unlikely unless these are hotspots are truly geographically isolated.  I've identified at least two SenseCAP hotspots that seem to realistically be located in the area, witness each other, and have participated in packet transfers:

11NCY1VH9oveQhwWHSW6ohbvZKPESmPw12UTt7XGgCgDfYQZAjj
112WNzwGkAHwSuKrkaXANz4UCDJ72wFJeuxkpwjVoucKDtGukA7G

A similar ETL query of these yield totally different results.  The query will not complete with 6 hops, and only 2 hops already leads to several hundreds of hits across Italy (presumably due to some relocations within the 22 day time frame), and from all hotspot vendors.

Finally, this may just be the tip of the iceberg for a much larger operation.  If the ETL query is extended further into the past, the cluster extends to hundreds of unique PantherX addresses.  This may be an indication of a recent segmentation of a much larger gaming cluster to optimize rewards and evade detection.

Great stuff


PyPI version needs to be installable for Python3

Gftools now works with python3, even though some scripts still need work. The version of gftools that is hosted on PyPI can't be installed with a python3 venv and needs to be updated.
This was an issue for @eightmoe durring the Atypi fontbakery workshop while trying to fix a FAIL.

This works fine now, at least with version 0.9.21.


I can't add Codebase as a chat context

Copilot Chat Extension Version: v0.20.0
VS Code Version: 1.93.0 (Universal)
OS Version: macOS 12.5.1

I can repro in stable but not in insiders. Not sure what changed here, cc @roblourens

still having same issues??? while cursor AI can do this with no issues? Please see why cant this extension behave as intended and marketed

I am already Using vscode insiders and prerelease copilot!!  Context is the biggest issue also why there is no limit shown??


[Monitoring v2] Wrong permissions in the PSP for Grafana

Rancher Server Setup

Rancher version: 2.6.x
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1

Proxy/Cert Details:

Describe the bug

rancher-monitoring 100.0.0+up16.6.0 fails to install when passing the value grafana.persistence.enabled=true since its PSP set runAsUser=MustRunAsNonRoot but the grafana deployment wants to run the init pod as root.
To Reproduce

install rancher-monitoring 100.0.0+up16.6.0 with the value grafana.persistence.enabled=true
Result
grafana pod will fail to run up with the error
pods "rancher-monitoring-grafana-7f54b7d8bc-" is forbidden: PodSecurityPolicy: unable to admit pod: [spec.initContainers[0].securityContext.runAsNonRoot: Invalid value: false: must be true]:Deployment does not have minimum availability.

Expected Result

the installation should succeed
Screenshots

With initChownData: false this should not be a problem I believe… so maybe the helm chart needs to create the PSP different based on this setting?

Could this be a result of https://github.com/grafana/helm-charts/issues/752?

@Tejeev Yep, it is the same bug. The fix is in the next release of rancher monitoring.

Can be tested in the rancher-monitoring  100.1.0+up19.0.3
Root cause
rancher-monitoring 100.0.0+up16.6.0 fails to install when passing the value grafana.persistence.enabled=true since its PSP set runAsUser=MustRunAsNonRoot but the grafana deployment wants to run the init pod as root.
What was fixed, or what changes have occurred
correct the permission in the PSP file
Areas or cases that should be tested? What areas could experience regressions? Are the repro steps accurate/minimal?
Please check this commit for the scope of tests.

Image Name
Image Tag
Image Digest

rancher/rancher
v2.6.2
51658639bf2b28f4796e7daa04b0434e29fcf69ce062bf649462be77ae76cd2c

rancher/rancher
v2.6-head
49e9e6f39477971969399ea925951536986d7d09699d70d9a127db16eec33712

Issue was verfied to exist in 2.6.2 (rancher version) / v100.0.0+up16.6.0 (chart version) through the following steps:

Deploy hardened cluster
Run rancher:v2.6.2 through docker (on separate host)
Import hardened cluster into rancher
Deploy CIS benchmark on the hardened-cluster through Cluster Tools
Validate the cluster is hardened (i.e no fails) using CIS benchmark scan profile rke-profile-hardened-1.6 (warnings should not fail the scan)
Deploy Monitoring v100.0.0+up16.6.0 through Cluster Tools. Grafana storage should be enabled through Edit Options -> Grafana -> Grafana Storage -> Enable with PVC template
Validate that the rancher-monitoring-grafana deployment failed (in cattle-monitoring-system namespace) due to the PodSecurityPolicy

Issue was verfied to be fixed (i.e. test passed) in 2.6-head (rancher version) / v100.1.0+up19.0.3 through the following steps:

Deploy hardened cluster
Run rancher:v2.6-head through docker (on separate host)
Import hardened cluster into rancher
Deploy CIS benchmark on the hardened-cluster through Cluster Tools
Validate the cluster is hardened (i.e. no fails) using CIS benchmark scan profile rke-profile-hardened-1.6 (warnings should not fail the scan)
Enable the local storage class for the cluster
Deploy a PV of size 20Gi to the cluster
Deploy Monitoring v100.1.0+up19.0.3 through Cluster Tools. Grafana storage should be enabled through Edit Options -> Grafana -> Grafana Storage -> Enable with PVC template. PVC size should be 15Gi and use the storage class created a few steps earlier. In addition, grafana.initChownData.enabled should be set to false
Validate that the rancher-monitoring-grafana deployment succeeded (in the cattle-monitoring-system namespace)
Validate that the Grafana UI can be access through hardened-cluster -> monitoring.

Some notes:

I had to disable the init container for Grafana to get this to work on the upgraded version grafana.initChownData.enabled=false
No PV was provisioned when validating that the issue occured on 2.6.2/v100.0.0+up16.6.0
The end deployment (which worked) was a bit unstable, and had to be deployed a couple of times before it took hold (I don't believe this to be related to the changes - moreso to how the PV was created/used).

Post fix Dev-Validate

Image Name
Image Tag
Image Digest

rancher/rancher
v2.6.3-rc5
a8ebbe326619f99644d3784311b431b74feefbd0a769e61bdff9c889b29988e0

Validation Steps:

Deploy hardened cluster
Run rancher/rancher:v2.6.3-rc5 (on a separate machine)
Import hardened cluster into ranchar
Install CIS benchmark v2.0.2 from Cluster Tools (in the downstream cluster)
Install longhorn v100.1.0+up1.2.2 from Cluster Tools (in the downstream cluster)
Run a scan (in the downstream cluster) using the profile rke-profile-hardened-1.6. Warnings should not cause a failure. Validate that the scan passed.
Install Monitoring v100.1.0+up19.0.3 from Cluster Tools (in the downstream cluster). Enable Grafana Persistence using Edit Options -> Grafana -> Grafana Storage -> Enabled with PVC Template. Set size to 15Gi, Storage Class Name to longhorn, and Access Mode to ReadWriteOnce.
Using kubectl, validate that the pod prefixed by rancher-monitoring-grafana is running using kubectl get pods --all-namespaces | grep "rancher-monitoring-grafana"
Validate that the grafana UI can be reached and is functioning by going to Monitoring -> Grafana in the rancher UI.
Validate that the newest version of the chart was published by running kubectl describe psp rancher-monitoring-grafana -n cattle-monitoring-system and reviewing the output to ensure that it includes specifically enumerated Required Drop Capabilities (including DAC_OVERRIDE).

Validation Status: Pass
@sowmyav27 This now passes after the fix (without grafana.initChownData.enabled=false)


Cannot install because installer looks for non-existent previous install...

I'm trying to install the latest version of the community tasks but when installing it asks to uninstall v<IP_ADDRESS> of the community tasks, except

I don't have it installed
The msi doesn't exist in your releases for me to try target the msi during the uninstall request.

How can I get around this?

It seems to be caused by v 1.3

I tried to uninstall 1.3 and it asks for the msi for 1.4? I don't have an installer for this...


Trade Id not collected

Describe the bug
When creating a script that is using real-time trades, I found that the trade id was always null.
After checking this, I realized that the connectors are not parsing it properly and that's why is always null.

Fixed with #6440, merged to latest development, will be available in 1.18.0 Release


[Feature Request]: stamp mirroring option

Is your feature request related to a problem? Please describe.

Describe the solution you'd like
Hello,
would it be possible to add a mirror command when using the stamp feature?

Proposed workflow

Describe alternatives you've considered
Have to use Photoshop. But that's an extra step i would like to avoid if possible.
Additional context
No response

On branch seijihariki/issue193.

On main now

Closing as completed for now. There is both a button for mirroring, but the '=' key also should work for inverting. If there are any issues with the current implementation, please send a message here.


added solution to max consecutive ones

added this as a part of practice

Merged Arrays 101 intro to main


[BEAM-7923] Streaming support and pipeline pruning when instrumenting a pipeline with interactivity

Updated pipeline_fragment to not prune newly added TestStream
transforms.
Updated pipeline_instrument to support streaming pipeline and prune
transforms that don't contribute to the desired outputs.
Updated ipython version upperbound to <8. We are targeting ipython >
7.3 for the introduction of cell magic %pip. Note %pip has different
behavior than !pip because the previous one guaranteees the
installation in the kernel not arbitrary environment the notebook is
running in.
Updated the README for Interactive Beam. The main change is
recommending using Jupyterlab over old Jupyter notebook and setup
instructions such as setting virtual env through Python3 venv module, installing
new labextensions over nbextensions and install extra dependencies.

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

This PR depends on some other pending PRs, there is no need to run any test for it temporarily.

I think this change is fine. But it was really difficult to review.
For this PR - Please add a more descriptive PR title.
For future PRs - Please separate unrelated changes from each other have logical commit sets.
LGTM once the PR title and description is updated to be more specific.

Thanks, Ahmet!
Updated the title to Streaming support and pipeline pruning when instrumenting a pipeline with interactivity.
I'll do several rebases when dependency PRs are merged and IM you for tests.
For future PRs, we'll separate changes into more fine grained commit sets, thanks for the review!

Resolved some merge conflicts, will need another rebase once PR https://github.com/apache/beam/pull/11050 is merged.

retest this please

retest this please

Run Python PreCommit


Documentation of functions and the Codebase for new Contributers.

There is little to no documentation, so i will most likely myself write the docs for the codebase.

The docs is focused on plastic_core for now, since that what others will interact with most if they are using it as a library.
But you are right on the UI crates, those don't have docs


Code refactoring, register all commands to the global variable and add the Name function to display the command name

Codecov Report

Merging #74 (81562d3) into main (a5796f7) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #74   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           59        60    +1
  Lines         1632      1697   +65
=========================================
+ Hits          1632      1697   +65

Impacted Files
Coverage Δ

command/command.go
100.00% <100.00%> (ø)

command/commands.go
100.00% <100.00%> (ø)

command/cp.go
100.00% <100.00%> (ø)

command/echo.go
100.00% <100.00%> (ø)

command/hash.go
100.00% <100.00%> (ø)

command/is_dir.go
100.00% <100.00%> (ø)

command/is_empty.go
100.00% <100.00%> (ø)

command/is_equal.go
100.00% <100.00%> (ø)

command/is_equal_text.go
100.00% <100.00%> (ø)

command/is_exist.go
100.00% <100.00%> (ø)

... and 7 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[BULK UPDATE] DocuTune - Rebranding links

Global effort for the Microsoft Learn platform rebrand
The Microsoft team is applying changes to content for the Microsoft Learn platform rebrand. Changes include modifications to current Microsoft Learn and Microsoft Docs terminology as well as associated domain name and content URL path changes.
Please review this draft PR and provide any necessary comments as soon as possible. Because these fixes are tightly scoped, we have approval to automatically merge these changes to the default branch for publication.
This PR was generated via DocuTune. It includes only targeted fixes and minor formatting adjustments.
CorrelationId: d8c4c3ac-d49a-4c95-9ddc-9822ca297907
InitiativeId: docutune-rebranding-2022-09
PointOfContact: Alex Buck

#docutune-draft

Docs Build status updates of commit 9c45ebc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

README.md
:white_check_mark:Succeeded

TerminalDocs/command-line-arguments.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

#docutune-ready


fix extra newlines in raw strings

fixes #941
I wonder how it decides to call pos.advance() and pos.newline()

It looks like it's fine calling pos.advance() and still calling pos.new_line(). It corrects from being one past the last character of the line to being the first character of the new line - it doesn't really advance twice, though it wouldn't make a difference if it didn't advance when the character is a newline. AFAIK this PR is ready.


[SUGGESTION] a web-app or browser extension that runs this code regardless of OS or device

ive seen this method used more and more, where basically everything required for a specific program is able to be run from a web-app skipping the need to install and configure the program manually. i imagine this could be streamlined with a browser plugin and/or implemented as a mobile application much easier.

An app is possible but a web browser can't access ports...

Hey @imnotjack91, unfortunately phantom requires fairly low-level networking access that I don't believe is possible in a browser extension. I'm actively looking into and prototyping a mobile app for iOS and Android, but no ETA on that just yet.
I've also considered adding a UI to phantom that you just use from your browser on your computer, so that you don't have to configure it manually from the command line. So that's definitely possible as well.

Hey @imnotjack91, unfortunately phantom requires fairly low-level networking access that I don't believe is possible in a browser extension. I'm actively looking into and prototyping a mobile app for iOS and Android, but no ETA on that just yet.
I've also considered adding a UI to phantom that you just use from your browser on your computer, so that you don't have to configure it manually from the command line. So that's definitely possible as well.