requestAnimationFrame called by Pixi

Hi Mat / Chad / Pixi Team!
Chrome reports that Pixi JS is calling requestAnimationFrame.
I'm using my own requestAnimationFrame(update). Having both seems to interfere slightly with performance. I think it would be great if Pixi would never call rAF unless when it's necessary (eg for MovieClip).
In any case: Is there a way for me to disable it?
Adding this in my JS doesn't help:
PIXI.ticker.autoStart = false;
and this is not available:
PIXI.ticker.stop();

Hello,
You can do that by calling these lines :
var ticker = PIXI.ticker.shared;
ticker.autoStart = false;
ticker.stop();

And then in your own loop, call this :
ticker.update(timestamp);

Regards.

Thanks, but I want to continue using my own requestAnimationFrame(update) .
And I want to be sure that Pixi doesn't call requestAnimationFrame. (if that's not possible/desired, I want to make sure Pixi doesn't call requestAnimationFrame).

Yes? Well I may need to explain it in a better way but what I wrote is what you need to do that.

        var ticker = PIXI.ticker.shared;
	ticker.autoStart = false;
	ticker.stop();
	function run(timestamp){
		requestAnimationFrame(run);
		ticker.update(timestamp);

I want to be sure that Pixi doesn't call requestAnimationFrame.
If Mat/Chad/etc decide to stop Pixi from calling requestAnimationFrame unless required, I'll get the latest version of Pixi and be happy.
Only if they don't want to stop Pixi from calling requestAnimationFrame I'll add the code for stopping the timer (thanks for the code).
My current project doesn't have MovieClips or interactivity, so I guess I don't have to call ticker.update.

Then don't call it and you'll be fine.
autostart is true by default. Changing that (meaning they think that it should be done for whatever reasons) would break every other code running pixi. Not likely to happen.

No, nothing should break :) Like I wrote, Pixi should still call requestAnimationFrame when required.
Avoiding rAF calls when they're not required can only help performance, I think.

It is required, the interaction manager uses it. @JiDW gave you the solution like 3 times, stop the timer and manually update it in your own loop.
The reason we have it running in a separate loop is so that interaction/movieClip checks are not in the main loop (which increases performance). I seriously doubt having two RAFs decreases performance.

It is required, the interaction manager uses it.

My current project doesn't have MovieClips or interactivity.

@JiDW gave you the solution like 3 times

Yes, and I wrote that I'll use it if necessary = if future Pixi will still call rAF.
Here's how I came across it: I hadn't known that Pixi calls rAF, investigated a perf issue, and came across Pixi's rAF calls in exactly the low-FPS regions of the Chrome timeline. I don't know how severe the perf impact is, but it was always listed among the various calls in the problematic timeline regions.
Here's a copy of the unfinished demo:
http://tobireif.com/non_site_stuff/copy_of_unfinished_pixi_demo/1_webgl_2d/
In the above demo, Pixi is calling rAF (reported by Chrome's timeline) although there's no interactivity and no MovieClip.
I think that when there's no interactivity and no movie clips, Pixi shouldn't call rAF - that could help performance. (And when the user creates interactive items or movie clips, Pixi would start the rAF loop).
But the decision absolutely is up to Mat / you / etc.

More importantly, the shared ticker is a public api. People rely on and use it. Changing its behavior is a breaking change."

People could still use it - it would have to start running as soon as the API user calls eg ticker.add(...) (it would be one of currently three reasons for starting the ticker.) (If it gets implemented like that, there also should be an option to set eg .neverStart = true.)
Another aspect to consider is that many users don't know that Pixi is running an rAF loop, and thus can't consider whether they want to turn it off.
That's why I think it should only start running when necessary.
I hope you understand my suggestion, and that it is potentially good for performance in all Pixi apps (not just in mine). It seems possible to implement it without breaking anything - in that case please consider it.
If you decide against it, please close the ticket, then I'll stop the Pixi ticker in my code (and call PIXI.ticker.shared.update(timestamp) from my rAF loop if necessary).

People could still use it - it would have to start running as soon as the API user calls eg ticker.add(...)

That is what it does right now when autoStart is true, which it is by default. If we make autoStart instead false by default, then people's code will break until they realize they have to manually start the ticker now.

That's why I think it should only start running when necessary.

I already does :) The interaction manager is using it so it runs, though the callback it hits does nothing because there are no interactive elements. If you don't use the interaction manager, then get rid of it:
renderer.plugins.interaction.destroy();
renderer.plugins.interaction = null;

The interaction manager will shutdown, remove its events, and the Ticker will go to sleep since it is no longer used. There is no way to know when the interaction manager should run and not. There is no event or notification of something becoming interactive. So the only way to know when something becomes interactive to be checking for it the way it does now.

I don't know how severe the perf impact is, but it was always listed among the various calls in the problematic timeline regions.

I can't find anything the timelines or profiles that would suggest that the RAF used by ticker takes any more time than 1ms. Can you post an example of what you are seeing? According to my timeline the RAF from the ticker takes ~0.06ms, so I'm not sure what the problem is.

It seems possible to implement it without breaking anything - in that case please consider it.

Possibly, but that would involve some serious rewritting of how the interaction manager works, and how making things interactive work. We may do that at some point in the future, but it is very unlikely to happen any time soon.

then I'll stop the Pixi ticker in my code (and call PIXI.ticker.shared.update(timestamp) from my rAF loop if necessary).

If you have no movie clips or interactivity, then no need to call it. All you want to do in your app is just stop the ticker (or stop the interaction manager and the ticker will stop itself).

Closing since this seems answered.


"In Power BI, support for UserType Member is currently in preview" | Mean ?

[Enter feedback here]
Can someone explain what is the meaning of this statement in detail, it creates ambiguity and need clarity what may or may not work or has know issue/restrictions?
"In Power BI, support for UserType Member is currently in preview"

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 725c3bff-b250-c882-6f2b-1f2cb7f00341
Version Independent ID: f48832e7-8fc5-498a-8522-435a8ce42129
Content: Distribute content to external guest users with Azure AD B2B - Power BI
Content Source: powerbi-docs/enterprise/service-admin-azure-ad-b2b.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @ajburnle
Microsoft Alias: ajburnle

Thanks for your comment, @vamdevmishra. This issue has been assigned to the doc author for review.

@vamdevmishra Thank you for taking the time to submit feedback. The referenced article has been updates since your comment was submitted, so I am closing this issue now. If you have additional feedback, please feel free to use the on-page feedback tools for the article. Thanks again for taking the time to help improve our docs!


[Bug]: [Describe the issue]

What happened?
I did step by step what was told you gave me access but still wont work copied link as in video correctly redeemed channel points as in video but still never q's any song.
What part of the service is not working for you?
Other (please describe above)

{"level":"error","ts":"2023-06-27T01:48:14.099Z","caller":"api/callback.go:161","msg":"failed to publish","input":"[https://open.spotify.com/track/2MbdDtCv5LUVjYy9RuGTgC?si=1e6e099ae0404701","error":"song](https://open.spotify.com/track/2MbdDtCv5LUVjYy9RuGTgC?si=1e6e099ae0404701%22,%22error%22:%22song) is too long. 227478 > 8000","

It looks like you set a max song duration and are trying to queue songs that are longer.

i put max song length to 9 mins or 8 I know those songs are not that long maybe 4 min max

nvm got it to work
thanks for this bud great stuff

Thanks! Glad you got it to work. In case it wasn't clear, I think you tried to set the max to 8 minutes, but input 8 seconds.


FINERACT-696 - add spotbug bug-pattern plugin

Description
While code reviewing https://github.com/apache/fineract/pull/464, I came accross a catch & printStackTrace, which is of course wrong (it should instead be, correctly, logged, instead).
In an ideal world, it would not take human code review to catch this, but just an automated build failure. This is possible using SpotBugs (not FindBugs anymore; SpotBugs is the new FindBugs, it's a fully compatible successor)  and https://github.com/KengoTODA/findbugs-slf4j/ (for this particular case https://github.com/KengoTODA/findbugs-slf4j/issues/70, but using findbugs-slf4j for Fineract would have value even before that's implemented).
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Commit message starts with the issue number from https://issues.apache.org/jira/projects/FINERACT/. Ex: FINERACT-646 Pockets API.

[ ] Coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions have been followed.

[ ] API documentation at https://github.com/apache/fineract/blob/develop/api-docs/apiLive.htm has been updated with details of any API changes.

[ ] Integration tests have been created/updated for verifying the changes made.

[ ] All Integrations tests are passing with the new commits.

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the list.)

Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide

Looks like you have a spotbugs violation and possibly a Checkstyle voilation in this PR. Opening and closing n times may not solve this. run ./gradlew clean check to see the problem and fix them on local Dev env before sending PR:
See: https://travis-ci.org/apache/fineract/builds/658740697#L1963
You can also check the logs online via Travis.. Do you understand what I mean?

This still fails due to a hopefully simple to fix SpotBugs violation problem.  This failure has nothing to do with the problems we are chasing in https://issues.apache.org/jira/browse/FINERACT-850 and sub-tasks.

@xurror actually I suspect that this probably now fails SpotBugs because it detects (many?) wrong log statements? We should just fix them all up, as part of this PR... I know it's a bit painful manual work, but "fixing all and immediately enforcing" is the only pattern that I know of to make something like this have any real lasting impact (similar to #715).

@vorburger I already resolved them earlier today, it was actually quite long and boring but I think it's ready for merge

@vorburger,this is ready


chore: bumping cryptography (pip-audit warning)

Currently blocked due to https://github.com/auth0/auth0-python/issues/627.

@neilcampbell we can either:

Move the related abstractions (its just 2 classes that we rely on in this package around JWT validation) - we can remove dependency on auth0 completely (it was known to cause similar issues for at least twice over past year)
Wait for this to be addressed on auth0 package, looks like issue 627 has a lot of folks pushing for resolution
Ignore the warning on pip audit side and apply 2 as soon as the fix is available.

What do you think ?

@aorumbayev If we can remove the dependency easily, then maybe that's a good way forward.

@neilcampbell moved auth0 specific depenendcies to _vendor folder inside core, header include ref to file and ref commit. Let me know what you think

@aorumbayev Nice. Assuming you've checked the testnet dispenser features are all working as expected?


Replaced Bootstrap Tour with IntroJs in Stopwatch activity

I have migrated Stopwatch activity tutorial from bootstrap-tour to IntroJs
Issue: https://github.com/llaske/sugarizer/issues/1090
screen-capture (3).webm

Thanks @saakxshi .
Two things:

Popup title has not the right color: should be white not gray.
Avoid reformatting files (TAB/Space). Your update should be limited to updated lines. Guess it's an option in your IDE.

Okay, I'll take care of auto-formatting for the upcoming activities. I've disabled auto-formatting, which automatically formatted my files on saving.

Please update this PR without auto-formatting else it's difficult to see your changes in updated files.

Please update this PR without auto-formatting else it's difficult to see your changes in updated files.

I've made the changes , lemme know if it's correct.


Implement setting for whether quotes are single or double

By default, htmlhint flags HTML that uses single quotes in attribute values. While the default behaviour is fine, it would be nice with an option to change the quote output to double. :)

Maybe we should just switch to double quotes.

I’d be down with that.

Want to submit a PR?


[EPIC] Support ZK proofs of the EVM + IBC client in Rollkit

Rough steps:

[ ]  PoC with Reth directly working with Rollkit
[ ] Proof generation triggering sidecar process
[ ] Sequencer consensus proof + Send State Proofs + Merkle Inclusion Proofs + Blob Inclusion Proof to the IBC relayer
[ ] EVM verifier
[ ] Celestia ZK Accounts compatibility

The sequencer consensus proof here comprises of the signature(s) of the sequencer (network) of the rollup. In a centralized sequencer case, this is a single signature. Whereas when using a shared sequencer network, that's an aggregated signature of the sequencer network. In the based rollup case, this'd be the signature of the DA layer validators on the DA block

For now, the PoC with Reth directly working with Rollkit can be the same as https://rollkit.dev/tutorials/beaconkit
This is because the proof generation sidecar process just needs an RPC and a block number as an input. These proofs per block are then put in a Range program to get a proof for a range of blocks and then run in an aggregator program that gets a proof for a larger range of blocks that is posted on the destination chain. Reference diagram:

We should able to reuse the Range Program and Aggregation program from the op-succinct docs.
For a withdrawal request from the rollup to a destination chain, we'd construct a separate program that verifies the MPT storage proof of a message in a state root already proven on the destination chain. Proof verification code in Rust h/t Union. We'd then send a proof of this program to a destination chain to process a transfer.
I'm not sure if the Blob inclusion proof is something the rollup needs to provide when bridging to Celestia necessarily since Celestia already has that information but it might be better to do to standardize the IBC client for other chains.

Code pointers
E2E tests
Shows step-by-step with manual relaying of packets.
The main version currently uses a dummy light client on the cosmos side. It will soon be switched out with the union light client shortly (will let you know)
https://github.com/cosmos/solidity-ibc-eureka/blob/main/e2e/interchaintestv8/ibc_eureka_test.go
Union library for Ethereum verification (including membership and non-membership
https://github.com/unionlabs/union/blob/4e987f48d90af728cda09a992b2ea51220a43f33/lib/ethereum-verifier/src/verify.rs#L303
Light client examples for ibc-go
I think an easy example to start with might be the solo machine light client. It has a pretty simple model that just verifies a signature, so the structure can be reused fairly easily and just replaced with your own stuff:
https://github.com/cosmos/ibc-go/tree/main/modules/light-clients/06-solomachine
The dummy client is the bare minimum implementation:
https://github.com/cosmos/ibc-go/tree/poc-solidity-ibc-eureka-wasm/modules/light-clients/00-mock
The interchain attestation light client can also be useful to look at as it is a standalone light client written from scratch:
https://github.com/cosmos/interchain-attestation/tree/main/core/lightclient
Keep in mind that since these are just Cosmos SDK modules, there is some proto files as well that is used to generate the stored values (client state and consensus state)
Operator
The operator is doing proof generation and relaying. It works as a CLI with a few different modes. It can just run in a loop updating headers (i.e. queuing headers, creating proofs and submitting them to the light client Solidity contract) or it can execute specific SP1 programs and generate fixtures (which we use for testing)
https://github.com/cosmos/sp1-ics07-tendermint/tree/main/operator
Take a look at the root README to see how to build and run different parts of this.
Just to give a quick intro to the structure.
The SP1 programs themselves are under the “programs” folder
The operator has different runners which are triggered by the different CLI commands.
The runners take in input, makes any RPC calls it needs (to get headers and so on) and uses the SP1 programs to create proofs (and in some cases fixtures for Solidity, used by tests at the moment)

https://github.com/invocarnau/succint-zk-residency/tree/main/fep-type-1

Example of proving transaction inclusion in a zkvm from Risc-Zero:

https://github.com/risc0/demos/tree/tx_inclusion (ignore the base branch, just needed somewhere to push where you can see)
There are some small hacks with serialization given alloy Headers serde impl is broken for non self describing serialization protocols, but this should roughly show the flow of how this could work.
All this does is pull the latest block from ethereum, prepare the proof, pass in the inclusion proof with the block header, and prove that the inclusion proof is valid all the way to the block header.


Add support of the command READONLY & READWRITE

Search before asking

[X] I had searched in the issues and found no similar issues.

Motivation

redis cluster utilize readonly to support reading from slave node
go-redis will send a 'readonly' command to server when 'ReadOnly' option is true during initialisation which would incur an error response from kvrocks 'ERR unknown command readonly' because kvrocks doesn't support command 'readonly'
this is important because without reading from slave a shard  is not readable during failover which is not acceptable for some businesses

Solution
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@singular-seal Thanks for your feedback.

Hi @git-hulk, I want to help implement this feature, could you give me some suggestions on where to start? thanks a lot!

@LiuYuHui Thank you! Go ahead.

Hi @LiuYuHui.
You can add a flag in redis::Connection to store if this connection enables read queries.
You can add new commands in cmd_server.cc
The following code may be the code you need to modify.

https://github.com/apache/kvrocks/blob/unstable/src/cluster/cluster.cc#L804-L807

If you have any other questions, feel free to ask me.


Base branch for CI/env fixes

Description
Current teachopencadd has a couple of dependency conflicts and deps-unrelated pytest fails.
This base branch shall be used to get a fully passing CI, while fixing all the different bits and pieces in smaller PRs.
Todos

[x] https://github.com/volkamerlab/teachopencadd/pull/294 -- pin numpy<1.24 and unpin tensorflow; do not test T021/22 and deal with it later (see below)

[x] #299

[x] https://github.com/volkamerlab/teachopencadd/pull/297

[x] #152

[x] https://github.com/volkamerlab/teachopencadd/pull/304

[x] #300

[x] https://github.com/volkamerlab/teachopencadd/pull/305

#303 --- do not close before at least Feb

[x] https://github.com/volkamerlab/teachopencadd/pull/306

[x] #298

[x] https://github.com/volkamerlab/teachopencadd/issues/302
[x] https://github.com/volkamerlab/teachopencadd/pull/309

[x] https://github.com/volkamerlab/teachopencadd/issues/289
[x] https://github.com/volkamerlab/teachopencadd/issues/265

[x] #310

Fixed in https://github.com/volkamerlab/teachopencadd/pull/296/commits/eccb30addd07f6a6ec30acf16c25ba108cbc62a1

[x] Unpin fontconfig because https://github.com/conda-forge/fontconfig-feedstock/issues/54 seems fixed?

Seems fine, all tests are passing as before after https://github.com/volkamerlab/teachopencadd/pull/296/commits/6d8e5015fdc5145f52bb1180de27b5f28cf86e2a

[ ] At the end: Remove base-ci-env-fix branch from CI.yml

Notes: After this PR's merge
...continue with TODOs in #312
Status

[x] Ready to go

CI is passing for all notebooks except for T019, which we will tackle in a follow-up PR, see #308.


Update .travis.yml to check multiple python versions

@Clivern Why do you want to test against development versions of Python?

I agree it not widely used & based on personal preferences but it is just to let you know what may go wrong in future or can be fixed beforehand. they all on the allow failure list so result won't affect the build result. But it still a personal preference so it is totally up to you.

I think testing so many versions is unnecessary and wasteful, so I've removed all the -dev versions and kept only nightly.


Warn when browser or dev are used

Describe the problem
People use import { browser, dev } from '$app/environment' and then their packages end up being tied to SvelteKit and Vite when they should work with any Svelte project
Describe the proposed solution
Print a big loud warning when running svelte-package if anyone tries to use import.meta.env.SSR, import { browser, dev } from '$app/environment', etc. and tell them to use import { BROWSER, DEV } from 'esm-env' unless they intend for their package to only be used in SvelteKit
Put a warning in the docs not to use these for libraries
Alternatives considered
Get rid of import { browser, dev } from '$app/environment' and just tell people to use esm-env in the docs. I think I'd prefer that honestly, but it couldn't be done until SvelteKit 2 as it's a breaking change
Importance
nice to have
Additional Information
No response

Please notice @benmccann that there is a problem with the REPL, I filled up an issue: https://github.com/benmccann/esm-env/issues/1

We should move forward with this change regardless. Using $app/environment in components already doesn't work in the REPL, and so pushing people towards esm-env won't make them worse off. The REPL is a lot more likely to support exports maps in the future than it is to ever support a hacky workaround specifically for $app/environment when that's syntac we discourage people from using anywhere else.

Hi, can you have a look at https://github.com/Tal500/esm-env-robust and confirm it's a valid workaround for the expected behavior?
If it is, can we push the code upstream to the svelte kit implementation, so that the environment api behaves as expected?

Would really love to use the alternative — use esm-env directly. I'm running into issues trying to use stuff in my SvelteKit app in utility scripts and in the node REPL.

Should be able to close this now
https://github.com/sveltejs/kit/blob/72436944dff4ebdc47b3ab212169fb7924574714/packages/package/src/validate.js#L46


First-run issues: Does not load some pages on first attempt

There's a weird behavior I've seen a few times in the past and now observed again when testing 0.6.0 (=> not new to 0.6.0):
When starting a fresh setup, sometimes the first time one clicks on certain pages, they don't load (they start loading, then send one back to the page one loaded from). The second time I load that page, everything works as expected.
For example: Create a project, submit a workflow. From the project page, go to the Jobs page. First time I do that, jobs page briefly flashes up, then project page reloads. Every following time, I get to the job page correctly.
Besides observing this in fresh installation, I don't have a way to reproduce it yet and not sure what exactly triggers this.

Same happens the first time I try to open a workflow. Nothing suspicious in the log of server & web that I can see though

To reproduce this it is necessary to generate a new tag and restart the app.
You can notice that when you create a new workflow for the first time (and you are erroneously redirected back to the previous page) the Svelte logs displays the following:
[vite] ✨ new dependencies optimized: slim-select, marked, dompurify, semver, ajv
[vite] ✨ optimized dependencies changed. reloading

A similar thing happens when you try to list the jobs for the first time:
[vite] ✨ new dependencies optimized: @vincjo/datatables
[vite] ✨ optimized dependencies changed. reloading

So, it's vite that, when detects a new dependency inside the page, optimize it and then reload the page, causing the weird behavior.
This should happen only on dev mode, but since it could cause issues with automated tests I fixed it adding the following to the vite.config.js:
optimizeDeps: {
    include: ['slim-select', 'marked', 'dompurify', 'semver', 'ajv', '@vincjo/datatables']
}

More here:

Vite Docs about Dep Optimization Options
Dependency Pre-Bundling

I've tried to disable the feature at all instead of listing all the dependencies but it doesn't seem to work with our configuration:
Incompatible options: `prebundleSvelteLibraries: true` and vite `optimizeDeps.disabled: true`

Thanks Sonia for the explanation, I understand at least a part of it ;)
Two quick comments:

If you think it's useful, feel free to explore (with no special urgency) whether prebundleSvelteLibraries: true is needed/appropriate. I cannot recall any special reason for having it.
The optimizeDeps.disabled option is marked as experimental, and it's not clear whether it will remain. Let's try to avoid it.

Thanks Sonia for the explanation, I understand at least a part of it ;)
1. If you think it's useful, feel free to explore (with no special urgency) whether prebundleSvelteLibraries: true is needed/appropriate. I cannot recall any special reason for having it.

Ok, I can have a look on it.

2. The `optimizeDeps.disabled` option [is marked as experimental](https://vitejs.dev/config/dep-optimization-options.html#optimizedeps-disabled), and [it's not clear whether it will remain](https://github.com/vitejs/vite/discussions/13839#discussioncomment-6719495). Let's try to avoid it.

Docs says: "Dependency optimization is enabled by default in dev only." and "Optimizing dependencies in build mode is experimental.", so I think that disabling it in dev (by setting it to false) is not experimental. Only setting it to build is experimental. Do you agree?

As quickly discussed, optimizeDeps.disabled is marked as "Experimental: Give Feedback", so we can stay on the proposed solution that uses the include option.


Not able to send message after using subject in MessageProperties

First of all I want to state that I am rather new to AMQP, so I may have misunderstood something here and if so, sorry...
I was expecting to be able to set the subject of a message to be sent, however when I try to send it I get a:

DEBUG:uamqp.client:Message error, retrying. Attempts: 1, Error: ClientMessageError('ErrorCodes.ClientError: expected bytes, uamqp.c_uamqp.StringValue found')

I see the same error if it try to use the get_properties_obj() function, which leads me to believe the following is a shortcut to reproduce my problem:

props = uamqp.message.MessageProperties(subject='test')
props.get_properties_obj()
Traceback (most recent call last):
File "", line 1, in
File "X:\env\lib\site-packages\uamqp\message.py", line 753, in get_properties_obj
self._set_attr('subject', properties)
File "X:\env\lib\site-packages\uamqp\message.py", line 742, in _set_attr
setattr(properties, attr, attr_value)
File ".\src/properties.pyx", line 140, in uamqp.c_uamqp.cProperties.subject.set
TypeError: expected bytes, uamqp.c_uamqp.StringValue found

If I instead set the message_id, everything seems to work properly.
I am currently running python 3.7 under windows with uamqp 1.0.0 installed by pip.
Let me end this post with a big thank you for providing this module. I am hoping to access an Azure servicebus using AMQP instead of the somewhat sluggish (in comparison) REST api.

Thanks for the report @mi-dst!
You're right - this does appear to be a bug - as we are converting the subject property into an AMQP encoded object when it should be a string/bytes.
I will get a patch out asap :)
Thanks again!

Ah, yes. I am not using get_properties_obj() normally. I just tried to make the problem as easy to reproduce as possible for you, but thanks for looking out for me :)
I will keep my eyes peeled for the patch.
Thanks for your quick feedback!

Thanks for your patience @mi-dst - v1.0.1 is now released with a fix. :)

Thanks for the quick update. However I am sad to report that I still cannot seem to get the subject-property working. I do get a different error with 1.0.1 though.
When sending a message I now get:

DEBUG:uamqp.client:Message error, retrying. Attempts: 1, Error: ClientMessageError("ErrorCodes.ClientError: 'bytes' object has no attribute '_c_value'")

Again I believe the quickest way to test it is:

props = uamqp.message.MessageProperties(subject='hello')
props.get_properties_obj()
Traceback (most recent call last):
File "", line 1, in
File "C:\uamqp-test.pyenv\lib\site-packages\uamqp\message.py", line 752, in get_properties_obj
self._set_attr('subject', properties)
File "C:\uamqp-test.pyenv\lib\site-packages\uamqp\message.py", line 741, in _set_attr
setattr(properties, attr, attr_value)
File ".\src/properties.pyx", line 142, in uamqp.c_uamqp.cProperties.subject.set
AttributeError: 'bytes' object has no attribute '_c_value'

Sorry for bringing you bad new just before the weekend...

That's strange - I wonder why my test didn't catch that...
Doh... okay - another patch on it's way....

I'm hoping to include this patch with a couple of other small fixes - release should be out sometime this coming week. Thanks again for your patience :)

Sounds great! Thanks for the feedback!

Okay - this should now actually be resolved in 1.0.2 :)
I actually found some issues in setting a couple of the other message properties as well so a good find!
Sorry it took so long - one of the other changes I wanted to add to this release was giving me headaches.

Unfortunately I will have to restrain myself from testing this for a couple of days as I have other pressing matters to handle. I will get there soon though! :)
Thanks again for your help!


Cylinder resource and collision shape (bullet only)

looks like it works...
some notes and potential issues:

bullet only, it crashes with SW, maybe I should at least add a warning message
doesnt expose bullet cylinder's half extent constructor, but only the radius and height
can the PhysicsServer::ShapeType values change or must the existing order be preserved?
symmetry axis is up, in sync with the mesh cylinder, not with the current capsule shape (99% of use cases imho)
no docs
icon most likely must be fixed

Related to #17252

Hmm, in this case I think it's fine like this.. I will check it better and
I will let you know
On Sun, Jun 17, 2018, 20:07 muiroc<EMAIL_ADDRESS>wrote:

@muiroc commented on this pull request.
In modules/bullet/shape_bullet.cpp
https://github.com/godotengine/godot/pull/19540#discussion_r195936898:

@@ -113,6 +113,10 @@ btCapsuleShapeZ *ShapeBullet::create_shape_capsule(btScalar radius, btScalar hei
return bulletnew(btCapsuleShapeZ(radius, height));
}

+btCylinderShape *ShapeBullet::create_shape_cylinder(btScalar radius, btScalar height) {

return bulletnew(btCylinderShape(btVector3(radius, height / btScalar(2), radius)));

Sorry, to be clear, this is what the user sees when he creates a cylinder
collision shape in GodotPhysics:
[image: cyli_err]
https://user-images.githubusercontent.com/10036337/41510575-73cd2260-7267-11e8-8da7-502e3ad8bf37.png
As you can see the console outputs the main error message, but also some
failed assertions.
Same happens when loading a scene that contains cylinder collision shapes
(slightly more asserts tbh)
Is it ok that way?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/19540#discussion_r195936898,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH9MR8Ih2HdXTmOfGU8GBblsbd9Nx6Reks5t9prwgaJpZM4UmaSV
.

There are some small style issues as shown by this diff: https://travis-ci.org/godotengine/godot/jobs/393317423
See http://docs.godotengine.org/en/latest/community/contributing/code_style_guidelines.html for how to setup style checks locally.
The commits would need to be squashed into one too before merging, see http://docs.godotengine.org/en/latest/community/contributing/pr_workflow.html

@akien-mga when the last change is done can be merged

Cool! Just wanted to say that I'm using this for KinematicBody characters and I really like the resulting  behavior and feeling especially when getting close to ledges, stepping stairs and the resulting normal when snapping to the ground.
Asap when the controller script is cleaned up I will share it (ofc don't expect something perfect!).

Thanks for this contribution!


Allow to set resources limits/requests for pt-heartbeat container

For now, under "podSpec" - there is no way to set resources limits and requests for pt-heartbeat container from mysqlcluster's statefulset.
Please add option for pt-heartbeat like mysqlOperatorSidecarResources and metricsExporterResources.

Yes, this is a very important feature as for now the resources for the heartbeat container can be set to default values only. Allowing to configure these values, will make the operator more flexible.


Does gradio-webrtc support stream IP camera via a RTSP url?

I'm integrating an IP camera feed into my Gradio application using WebRTC. The camera provides an RTSP stream URL. I'd like to know if gradio-webrtc currently supports directly connecting to and streaming from RTSP sources. Thank you so much!

Yes I think so because you can connect to your source using something like open-cv and then yield out the frames
import gradio as gr
from gradio_webrtc import WebRTC
import cv2

def generation():
    url = "https://download.tsi.telecom-paristech.fr/gpac/dataset/dash/uhd/mux_sources/hevcds_720p30_2M.mp4"
    cap = cv2.VideoCapture(url)
    iterating = True
    while iterating:
        iterating, frame = cap.read()
        yield frame

with gr.Blocks() as demo:
    gr.HTML(
        """
    <h1 style='text-align: center'>
    Video Streaming (Powered by WebRTC ⚡)
    </h1>
    """
    )
    output_video = WebRTC(label="Video Stream", rtc_configuration=rtc_configuration,
                    mode="receive", modality="video")
    button = gr.Button("Start", variant="primary")
    output_video.stream(
        fn=generation, inputs=None, outputs=[output_video],
        trigger=button.click
    )

if __name__ == "__main__":
    demo.launch()

Update to the latest version please!


Enhancement: Transform to add (or remove) container (e.g. library name or resource name) prefix on the front of keyword calls

We feel it is a best practice to always include the library name or resource name on the front of every keyword call. For example, instead of just saying Click Element (from the SeleniumLibrary). We say SeleniumLibrary.Click Element. Or, even better, we create a resource file called Selenium.resource which has a keyword called Click that is a wrapper for the Click Element keyword from the SeleniumLibrary. So, to call that Click keyword, our convention is to always write Selenium.Click. It would be great if a transform could be created for robotidy that would check for this convention and ensure that all keyword calls are prefixed with the library name or resource name that they are being called from. Alternatively, there could be a transform to ensure that library or resource prefixes are NOT included on keyword calls (for people who like the inverse).

I apologise for leaving this issue without the answer for so long - somewhow it escaped me.
It's more difficult to implement because we need to know the source of given keyword - although we could at least load libraries defined in particular *** Settings *** section and try to match it from there. And it's hard to also find keywords from dynamically loaded libraries (with Import Library keyword for example). But it's definitetly possible - I could try to implement MVP for it and see how it works.


CFD - Not fully working

Realise the CFD chart is showing a total WIP in the duration, not at a point in time - need to update measures

Now fixed in new version


Issue74: Fix invalid gzip files uploaded to analytics

Fix invalid gzip files getting uploaded to analytics by the analytics adapter.
Problem
There are two root causes for this problem.

The gzip writer stream should be closed after a flush so that it writes
the metadata to the zip. This was not happening in certain cases.
In crashRecovery method in the analytics adapter, there is no validation
in place to check if the gzip is a valid gzip or not.

Fix

Close() the writer stream after the Flush().
Fix the crashRecovery logic to skip the invalid gzip files.
Add test cases which handles two good zips; fix the existing crashRecovery
test case.

@robbrit : ^^


Use haproxy to load balance Kube API requests

Now that we can have multiple masters, we need a way for the various
services and end-users to be load balanced over the set of kube-api
servers.
We install haproxy on each node, inside a docker container, configured
to load balance requests over all the cluster masters. This haproxy
is configured to listen on <IP_ADDRESS> on the masters, and <IP_ADDRESS> on
the workers.
This is to allow the minions to simply "talk" to <IP_ADDRESS>, and be
routed to an active kube-api server.

Most of this code was grabbed from an older change in the "ha" branch, and reworked as the diff was too large to just cherry-pick or rebase.
https://github.com/kubic-project/salt/commit/35da1bedf1116a6544693bdd5a24ce4a5eceb7ee

Approving as the issue is with the devenv tooling (using an IP in place of a FQDN)


feat: track remote pins in progress

Closes #1752
Closes #1991

[x] Persistance via persistActions
[x] Breathing cloud when pending
[x] Red cloud when failed
[x] Periodic checks per storage with back-off
[x] Dismiss failed pin when clicking red cloud (failed)
[x] Replace /pins by a list of pending and done pin jobs that can be cleared (similar to the upload drawer)

There are some things you can test via the Storybook. However, there are some aspects, such as dismissing a failed pin on the Files page that I wasn't able to test.

@hacdias mind resolving conflicst?  I think we should review and ship this, so this work is not lost.

@juliaxbow another one for you

I tried running this locally and got the following error:

@SgtPooki I think I fixed the issue you were having with the checkbox.

Regarding the UI element to navigate to the Pins page: I would like to add something that would fit in. However, I'm not having great ideas.

Problem: the remanning information blocks on this style are not clickable.

Problem: better, as the button indicates an action. However, we do not usually use buttons for navigation, so it also does not feel natural.

I pushed your suggestion, but it doesn't make me necessarily happy.

We could also keep it minimal without the button surrounding it. I just feel like it's still a bit out of place too.
What do you think?

Tweaked the interface to include an 'x' for all types of pins:

Thanks @hacdias!
@juliaxbow any suggestions on what could be the best way to indicate "there are remote pins in progress"?
Design requirement: we want it to be visually noticeable, so the user won't miss the fact there are pinning jobs in progress.
See initial mockups in https://github.com/ipfs/ipfs-webui/pull/1919#issuecomment-1202685324

I like the idea of a breathing cloud! Something like below. Tested this on two people who both were inclined to click the cloud

Separately I would also suggest an additional visual clue (aside from color) for failed pin to make it more accessible for users.
Like this

or the more straightforward version (which I prefer):

I updated the breathing cloud to match your idea:
https://user-images.githubusercontent.com/5447088/183380046-1a2b69e6-5e6a-4d29-8ffe-6dd5c00c3635.mov
Regarding the icon for the failed pins: I think it'd be a great addition, but maybe we should add it to https://github.com/ipfs-shipyard/ipfs-css first. /cc @lidel

@juliaxbow could you please send the bottom icon (cloud with the slash) as an SVG so I can add it to the ipfs-css repository? You can see how the other icons are formatted and sizes, here: https://github.com/ipfs-shipyard/ipfs-css/tree/main/icons

@hacdias added here

I added the new icon in #2008 @lidel @SgtPooki. Please review and merge that PR into this one.

@lidel @SgtPooki this PR is ready for review. It already includes the new icon.

@SgtPooki I created some follow up issues (#2043 #2042) according to your comments. Once CI is green, I will be merging this.

@SgtPooki it seems I need a new approval for this to go through 😄

I do not understand. There are no pending changes requested, but I still can't merge.

Ah, @lidel requested changes at some point so we also need @lidel's review.


Replace std::fs with fs-err crate for much better error messages sake

bors d=anelson

bors d=anelson

bors d=@anelson

bors r+


Catch CM_Class_Exception_TypeNotConfiguredException and re-throw as CM_Exception_Nonexistent

In CM_Http_Request_Abstract::popPathSite() catch  CM_Class_Exception_TypeNotConfiguredException and re-throw as CM_Exception_Nonexistent because passing a wrong language or site-id in the URL should lead to 404.

@njam unfortunately it's not as easy as it seems because CM_Exception_Nonexistent it treated as a 404 at the page level and in this specific case we're not there. Checked this with @tomaszdurka and the refactoring looks quite big if we think to move CM_Exception_Nonexistent and CM_Exception_InvalidParam to higher level.

Hm I see. I got alerted tonight 5:30 so I'm still in favor of making this a non-error ;)
Example problematic URLs:

/ajax/de-de/100
/layout/de-de/100/1423665456/manifest.json
The language is not detected, so de-de is treated as the site-id.

Looking a bit at the whole Request/Response classes, I think the following should be done:

Request should not change, especially not by other classes -> #1636
The popSomething() functions should be changed to getPathPart($index), so they only return a value, and don't have side-effects on the Request.
Then the Response would get the relevant parts from the Request in its _process() method.

@dlondero @tomaszdurka wdyt?

Maybe that is not bad solution. As I understand you would non-obtrusively check if request matches any response and if not proceed to other response. Still it throw some kind of bad url exception if none response matched - which would be presented as Not Found. I definitely agree it would be good to not alter Request in the whole process.
It will still require some app logic to verify request is correct - like check if site with given id really exists.

Closing in favor of https://github.com/cargomedia/CM/pull/1638


fix build on SunOS

Fix build on SunOS (Solaris and illumos distributions like SmartOS, OpenIndiana, ...) by not using the reserved sun word.


Create challoners.txt

Email address would be<EMAIL_ADDRESS>

@cameron-robey Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!


Corrected PHP Syntax

Checklist

[x] I have made a material change to the repo (functionality, testing, spelling, grammar)
[x] I updated my branch with the master branch.

Short description of what this PR does:

Corrects a syntax error in documentation example

If you have questions, please send an email to Sendgrid, or file a Github Issue in this repository.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks @davcpas1234!

Hello @davcpas1234,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Put close() at beginning of autoClose

Fixes this issue: https://github.com/dancormier/react-native-swipeout/issues/101

Thanks!


Feature Request - Customize characters shown around song name

Saw your extension on Reddit, thanks!
I don't know how much of a hassle this may be to implement, but could you add a setting to replace the vertical pipes shown around the song title to a character of choice (such as parenthesis or even a space to 'disable')? I know that I could change it myself and install from source, but I think this may be a nice addition.
This is where I found the vertical pipes being outputted:
https://github.com/cliffniff/media-controls/blob/a0855ede73ce98b02f40b842a2bd73bb43a0acbe/extension.js#L328
Will be working on a pull request to implement this, feel free to reject.
Thanks again!

That would be a nice feature. If you are working on it, I'll be looking forward to it or else I'll try and implement it. Thanks for replying!

Also please update your fork with my recent commit, I changed the implementation of the pipes in that because of a feature I am gonna add in the future.
https://github.com/cliffniff/media-controls/blob/a55d05a12b58400de6f8e0ea2ad58444ed646207/extension.js#L80-L81
https://github.com/cliffniff/media-controls/blob/a55d05a12b58400de6f8e0ea2ad58444ed646207/extension.js#L484-L494
Hope this helps and thank you!

I added the feature in the latest update. So I guess I will close this issue. Anyways thanks for replying. If there are anymore features you need, don't hesitate to request!

Thanks!


Obtaining response.json

I'm wondering if we could include some information on how to obtain response.json for each student in the readme file. Thanks!

Instructions have been added to readme file


Documentation updates

Update the document about the right python version and current ansible version used in ansible driver

PR is merged. Closing the issue


Is there a USBX HOST PIMA reference code ?

Hi ,
I need to use STM32H573 as a USB host to read and write Android phone files.
I registered the pima class, connected to the mobile phone to set the MTP function, enumeration failed, but the PTP function can be successfully enumerated.
I have not used PIMA function. What function code should I use to read and write files on my phone?
Do you have the usbx host pima reference code?
Thanks!

Define UX_PIMA_WITH_MTP_SUPPORT and compile again to enable MTP support.
PIMA manages files as objects, you can use object functions to access your files. Usually you should open a session, get object information, open it, read/write it then close it.

Hi

MTP mode still fails enumeration, PTP enumerates successfully.
I opened the macro definition UX_PIMA_WITH_MTP_SUPPORT ,But this macro definition only seems to work on the USB DEVICE side?

Hi CQ，
I would like to confirm whether these are the only file formats supported by MTP?
/* Define PIMA Object Format Codes.  */

#define UX_HOST_CLASS_PIMA_OFC_UNDEFINED                        0x3000
#define UX_HOST_CLASS_PIMA_OFC_ASSOCIATION                      0x3001
#define UX_HOST_CLASS_PIMA_OFC_SCRIPT                           0x3002
#define UX_HOST_CLASS_PIMA_OFC_EXECUTABLE                       0x3003
#define UX_HOST_CLASS_PIMA_OFC_TEXT                             0x3004
#define UX_HOST_CLASS_PIMA_OFC_HTML                             0x3005
#define UX_HOST_CLASS_PIMA_OFC_DPOF                             0x3006
#define UX_HOST_CLASS_PIMA_OFC_AIFF                             0x3007
#define UX_HOST_CLASS_PIMA_OFC_WAV                              0x3008
#define UX_HOST_CLASS_PIMA_OFC_MP3                              0x3009
#define UX_HOST_CLASS_PIMA_OFC_AVI                              0x300A
#define UX_HOST_CLASS_PIMA_OFC_MPEG                             0x300B
#define UX_HOST_CLASS_PIMA_OFC_ASF                              0x300C
#define UX_HOST_CLASS_PIMA_OFC_QT                               0x300D
#define UX_HOST_CLASS_PIMA_OFC_EXIF_JPEG                        0x3801
#define UX_HOST_CLASS_PIMA_OFC_TIFF_EP                          0x3802
#define UX_HOST_CLASS_PIMA_OFC_FLASHPIX                         0x3803
#define UX_HOST_CLASS_PIMA_OFC_BMP                              0x3804
#define UX_HOST_CLASS_PIMA_OFC_CIFF                             0x3805
#define UX_HOST_CLASS_PIMA_OFC_GIF                              0x3807
#define UX_HOST_CLASS_PIMA_OFC_JFIF                             0x3808
#define UX_HOST_CLASS_PIMA_OFC_PCD                              0x3809
#define UX_HOST_CLASS_PIMA_OFC_PICT                             0x380A
#define UX_HOST_CLASS_PIMA_OFC_PNG                              0x380B
#define UX_HOST_CLASS_PIMA_OFC_TIFF                             0x380D
#define UX_HOST_CLASS_PIMA_OFC_TIFF_IT                          0x380E
#define UX_HOST_CLASS_PIMA_OFC_JP2                              0x380F
#define UX_HOST_CLASS_PIMA_OFC_JPX                              0x3810

If I want to transfer zip files or bin files, is it not supported?
Thanks！

The upper code is actually defined by PIMA 15740:2000.
I'm not sure if how your device reports zip or bin files, if they can be referenced in undefined code or some other codes you can use them.

Hi CQ，
Can you help us see why the MTP enumeration fails, but the PTP enumeration succeeds?

Do you have traces for the enumerations to analyze?


add hard_constraint support for the preemptible VMs in KFP

This change is

/assign @sarahmaddox

/lgtm
/approve


Fix environment owner during re-render

Addressing #85 to the best of my ability.
Root Issue: During re-render, the env.owner was not correct within an outlet. This was because outlet.render was not called, meaning that the check for ensuring the proper owner never occurred.
Solution: Move the check for owner into outlet.childEnv, which is called on initial and subsequent render.
I'm not 100% certain this is the best solution as I still don't fully understand the rendering flows and hooks, but it works. I've included a previously failing test as well.
cc @krisselden

Just to leave a comment on why, childEnv is always called, but the render hook is only called if the outlet is dirty.


Navigate subtasks in Open Task View

It would be nice if one could navigate the subtasks using the 'J' and 'K' keys to move up or down over the subtasks when in the Open Task View, 'i'.  As is I can almost keep my hands on the keyboard except when I need to do something with an existing subtask.

Good idea!  My work on todoist-shortcuts is mostly in maintenance mode, though (maintaining existing features).  Would merge a PR adding this, though.
In the meantime there are some alternative ways of doing this:

If the task is collapsed, l re-expands it, can use j to select the subtasks
If in a label / some other view that doesn't show subtasks, can use shift+g to view the task in the project, so that the subtask are visible

Thanks for the alternatives!  Those actually work really well.
-Kevin
On Tue, Dec 7, 2021 at 10:40 PM Michael Sloan @.***>
wrote:

Good idea! My work on todoist-shortcuts is mostly in maintenance mode,
though (maintaining existing features). Would merge a PR adding this,
though.
In the meantime there are some alternative ways of doing this:

If the task is collapsed, l re-expands it, can use j to select the
subtasks
If in a label / some other view that doesn't show subtasks, can use
shift+g to view the task in the project, so that the subtask are
visible

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mgsloan/todoist-shortcuts/issues/188#issuecomment-988541867,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANDHR2ONF6E56YWSW6XKEQ3UP34VLANCNFSM5JHSZV3Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Added BL position ID getter

Pull Request Test Coverage Report for Build 2325

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

Totals

Change from base Build 2314:
0.06%

Covered Lines:
784

Relevant Lines:
924

💛  - Coveralls


Incorrect handling of non-latin characters

https://sorbet.run/#Ó %3D Integer
class A<Ó
end
should be permitted

Closing in favor of #2234


Enable Security Analysis (CodeQL) for Policy Compliance

As CodeQL is a GitHub Action, I went looking for the documentation on running it locally and all I found was that they removed the documentation on how to do this (in a PR) -- so it looks like its not supported..
When you publish a PR it does run it and you can see the "Code scanning results / CodeQL" task is automatically added once the "CodeQL / Analyze" action completes.


Define a guideline/policy for handling accounts of deceased or incapacitated user

Currently, nuget.org does not have a documented policy to handle e.g. the following situation:
Imagine a popular product with packages on nuget.org managed and owned by account A. The community around this product contributes additional packages to nuget.org that enrich this product's ecosystem. These packages are not owned by account A.
When one of the owners of these contribution packages, e.g. .account B, passes away or is incapable for whatever reason to continue this package, but the community at large, including account A, wants to continue supporting and maintaining them, they are blocked as they can't do that without transferring package ownership. However, the original package owner, account B, is incapable of responding to these ownership transfer requests.
There are other, similar scenarios that may lead to the above problem, and I feel we should provide some guidance or have a policy in place to help resolve this issue.

As a maintainer of a project that is currently in this situation, I wanted to add some notes on this from our point of view...
The Cake project hosts 6 packages on NuGet.  These are the core components of the Cake Build project.  In addition to the core functionality of Cake, we have an addin architecture that means that the Cake Community can easily extend the functionality.  We have been truly delighted with the response from the Cake Community, and I am aware of over 130 addins that have been created for Cake.  You can find these by searching for Cake on NuGet.org.
Back in August last year, after a discussion with our community on Gitter, we identified that there was a potential issue with our addin eco-system (which we documented here).  The problem at the time was that if a Community Member walked away from a project, then other community members who relied on a particular addin would not be in a position to get any further updates to the package hosted on NuGet.org.  We decided that this was less than desirable, and we set about doing something about this (you can see this being tracked here.  This took the form of the cake-contrib user on NuGet.org.  This user has now been made the co-owner of 117 of the cake addin's on NuGet.org.  For most packages, this has no impact on the original owner of the package.  They continue in exactly the same way as before.  The addition of the cake-contrib user is simply a fail safe.  In the event of an owner no longer being interested in maintaining a project (or in the more serious situation of a death), members of the Cake Team can step in, and continue to push new versions of the package to the same package id.  This means that the package itself can continue.  If we didn't have the cake-contrib user in place, it would mean that we would have to push new package versions to an alternative package id, which dilutes the eco-system, and doesn't make it clear which package is the correct one to use.
We were in the process of trying to get the cake-contrib user added to another package when we learned that the package owner had sadly passed away.  This leaves the package in question in limbo.  We are obviously hopeful that the decision that is made here will allow us to continue the excellent work that the original owner made, without having to create another package id.
We were in a similar situation with regard to the GitHub Repository which held the source code for the package.  We got a response from GitHub stating that nothing could be done without involvement from the next of kin, or business partner.  We decided to fork the repository and move it under the cake-contrib GitHub Organisation.  This decision was made because we didn't want to/or have no real way, to contact the next of kin (which would potentially cause additional sadness), and also due to the fact that the forked repository is still "linked" to the original, so credit to the original source code is still in tact.  NuGet.org has no real concept of "linking" to an original package.  Over on chocolatey.org when we have a need to what we call "deprecate" a package, we follow this process so that people consuming the original package automatically get the new one.  However, this process would still require access rights to the original package,

@anangaur @karann-msft @xavierdecoster just wanted to follow up to see if there had been any further discussions about this. Thanks.

@anangaur @karann-msft @xavierdecoster just checking in again... Any updates?

This sounds like a completely legit situation.  I am not sure of any legal situations this may cover or if said "property" would need to be assigned in a will or something similar to be legal (at least in the US).  However, this is a real life thing that happens and should be covered by law or at least GitHub policy to make sure something some one or many people have spent a lot of time to develop does not disappear because someone has passed away.  Maybe in the report and confirmation of death the ownership gets passed to the person with the most commits and latest active time (if they accept) would keep the project in the hands of someone that has a vested interest.

I'll check on this. I agree it's important, and it would be good to get a policy in place.
This is similar to the goals of .NET Foundation stewardship for member projects, but we need to solve this problem for NuGet packages at large, the huge majority of which won't be members of a software foundation.

First off, thank you all so much for the feedback. We absolutely are committed to maintaining the continuity of the ecosystem when an unfortunate situation like this happens.
We have been working with our legal team on this issue, and have now posted a policy update at the location below. This policy has been written to ensure confidence in the claim of ownership, before the NuGet.org administrators intervene to manually add any additional owners to a package.
Package succession under special circumstances
While we were working on defining the policy we also worked with the the Cake project to resolve their immediate concern, but going forward we will be following the policy above.
Thanks again on behalf of the NuGet team.


bug:

Version
latest
Describe the bug
Cody claims it is unable to read project files and cannot generate test files.
Expected behavior
As above, it should behave as advertised.
Additional context
No response

This should be fixed, please create a new ticket if the problem persists


Adding algorithms for arrays and bitwise operations.

Added algorithms in Bit Algorithms and Array with updated readme file in ALGORTIHMS. Please merge this pull request under the tag 'hacktoberfest2021'. #265

Sir please put the label hacktoberfest-accepted.


No entites due to setTemperature = None

Logger: homeassistant.components.climate
Source: custom_components/tech/climate.py:54
Integration: Klimat (documentation, issues)
First occurred: 21:16:09 (1 occurrences)
Last logged: 21:16:09
Error while setting up tech platform for climate
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 197, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/tech/climate.py", line 32, in async_setup_entry
[
File "/config/custom_components/tech/climate.py", line 33, in
TechThermostat(
File "/config/custom_components/tech/climate.py", line 54, in init
self._target_temperature = device["zone"]["setTemperature"] / 10
TypeError: unsupported operand type(s) for /: 'NoneType' and 'int'

I has been preported that fix works, but still there is error log during entity update:
homeassistant.components.climate
Source: custom_components/tech/climate.py:116
Integration: Klimat (documentation, issues)
First occurred: 7:25:51 (3 occurrences)
Last logged: 7:25:51
tech: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 357, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 466, in async_device_update
await task
File "/config/custom_components/tech/climate.py", line 116, in async_update
self._target_temperature = device["zone"]["setTemperature"] / 10
TypeError: unsupported operand type(s) for /: 'NoneType' and 'int'

It has been reported that now it gives following error:
2020-11-21 13:40:25 ERROR (MainThread) [homeassistant.components.climate] Error adding entities for domain climate with platform tech
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 314, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 505, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 531, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 296, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 322, in _async_write_ha_state
attr.update(self.state_attributes or {})
File "/usr/src/homeassistant/homeassistant/components/climate/init.py", line 221, in state_attributes
self.current_temperature,
File "/config/custom_components/tech/climate.py", line 129, in current_temperature
return self._temperature
AttributeError: 'TechThermostat' object has no attribute '_temperature'

It has been reported by users on FB page "Home Assistant Polska" that now the issue is fixed and there is no errors in the logs.


Backend refactor

Backend files (application/server files) have been re-organized for modularity and to enable reusability.

Corresponding front-end enhancements are being tracked on https://github.com/IBM/fabric-contract-attribute-based-access-control/pull/9


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1327 ms

Resolved: Bofrost.de performance has improved in 472c4ce after 19 minutes.


npx api install <openapi.json url> does not install package to local package.json

Hi!
I'm trying to generate an SDK and use it in a library I'm building but when I follow the installation instructions using npx api install and a URL to my openapi.json, the generated package is not added as a dependency to my local package.json
Steps to reproduce:

mkdir api-test && cd api-test
npm init
npx api install https://api.bit.io/openapi.json -l ts

select bitdotio as name for generated SDK
confirm package installs

installation completes without error and the files are generated in .api, but package.json, package-lock.json and node_modules are unaltered. I am unable to import @api/bitdotio.

I'm using npm 8.5.5 and node 16.14.2
Hopefully I'm missing something obvious here 😅

Works now! Thanks for the quick fix :~)


Add option to fail the task whilst generating a report file

I'm using Grunt with TeamCity to build our JS sources. I'd like jshint failures to fail the grunt build, whilst outputting the jslint style xml report for TeamCity.
As the plugin stands, the task will always succeed when the results are written to a report file. I've added an option to control this behaviour.

if I use force the jshint errors won't go to reporter, that way can not generate reports like I've said here #235


Issue when downloading large files from web browser

Let's try to squeeze this in 1.7.0, otherwise 1.7.1.
Describe the bug
as reported by @pgetta while developing scientific portals, the downloading of large files is problematic. Feedback of progress to the user isn't working in Fusion or his portal. Pavlo has attempted several workarounds without success.
We should have a meeting with @pgetta to review the issue and consider how we could address it.
What part of Nexus is affected

[x] Fusion
[x] Delta (to be confirmed)

To Reproduce
Steps to reproduce the behavior, e.g. for Fusion:

Go to Fusion and open an entity that has a large data file attachment
Click on Download, nothing appears to happen and after a while, the file appears downloaded, no intermediate feedback ti the user in between. It has been tested with files as big at 13GB in the ngv project and it took about 20' for the file to show up.

Expected behavior
The browser should be able to provide a view of the progress of the download while it is happening.

Hi @samuel-kerrien, I've noticed that this issue is closed now.
Is there a feature/api we can use as a solution?

I believe this has been closed in favour of: #2215, but wasn't linked.

Understood, thank you, @bogdanromanx


Misc updates for canal

Adds calicoctl wrapper when network type is canal ( #856 )
Adds network policy directory when network type is canal ( #857 )
Edit: Tested successfully locally

ci check this

please rebase, the coreos fixes allows CI pipeline to proceed over the faily step 1


Please update Changelog documentation

What happened?
Request: Please update Changelog documentation with latest releases info.
On the home page, there is a link to the Changelog: https://github.com/samemory/homebridge-eufy-security/blob/master/CHANGELOG.md
The info in this file has not been updated since 1.0.4 (27/10/2021). Current release appears to be 1.0.8.
(specifically, I'm looking to confirm whether bropat's latest library is included in 1.0.8)
Thanks!
Device Type
other (UnSupported)
Plugin Version
v1.0.x (Supported)
HomeBridge Version
v1.4.x (Supported)
NodeJS Version
v16 (Supported)
Operating System
Mac OS X 11+ (Supported)
Relevant log output
No response

Yeah lol i check Issues tab to see what changes have been made skjdaksldjs

Sure, but that doesn't easily summarize which changes were included in which release (unless you know what revisions are associated with each "release version").

Oh man ...

I will keep version track within the commit but can't keep it for the beta on change log. But for main release we will :)

Thanks @lenoxys, main version only is fine. I was confused when I last installed the mainline version in Homebridge UI because it posted the older release notes (for 1.0.4 I think) when I had just finished installing 1.0.8, which is where this request came from. Much appreciated!


udp_proxy: support proxy access logging

Signed-off-by: giantcroc<EMAIL_ADDRESS>Commit Message:
Some stats like no_route and idle_timeout can't be printed by session access log,
so we need proxy-level access logging to log global stats.
Additional Description:
Risk Level: Low
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue] #23241
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/retest

/retest

/retest

@phlax Hi, it seems wierd that the old code is still used to do test
test/extensions/filters/udp/udp_proxy/udp_proxy_filter_test.cc:639:42: error: too few arguments to function call, expected 3, have 2
                        access_log_format));

Can you help with it? Thanks!

@giantcroc CI runs on merge commit and you can see that part code here: https://github.com/envoyproxy/envoy/blob/e143e084f5/test/extensions/filters/udp/udp_proxy/udp_proxy_filter_test.cc#L629-L639
It's a merge race with #23121, you just need to merge main branch and fix that test as well.

@giantcroc CI runs on merge commit and you can see that part code here: https://github.com/envoyproxy/envoy/blob/e143e084f5/test/extensions/filters/udp/udp_proxy/udp_proxy_filter_test.cc#L629-L639
It's a merge race with #23121, you just need to merge main branch and fix that test as well.

OK, fixed, thanks a lot!

/retest

/retest

The coverage failure is a real one so you either need increase coverage or change threshold.

The coverage failure is a real one so you either need increase coverage or change threshold.

Hi, lizan!  Sorry for late respond. The coverage has been fixed after rebase. Thanks!

/retest

Should remove this line in this pr?
https://github.com/envoyproxy/envoy/blob/82667905a934826576e817a8222b0e1117b79b15/source/extensions/filters/udp/udp_proxy/udp_proxy_filter.h#L28

OK, thanks!

@lizan Hi, I have recovered the field name to address compatibility issue. Please help review, thanks!


 I'm not seeing the OOM problem that I was seeing when I run rank/gpu with shardrefine, so I did some scaling runs.
I am seeing a slow startup as we've seen in the past: http://sapling2.stanford.edu/~seshu/s3d_subrank/shardrefine/startup_legion_prof.html
Some profiles are available here: http://sapling2.stanford.edu/~seshu/s3d_subrank/shardrefine/

I also got some stacktraces from a 128 node run at two points in time if those are useful: http://sapling2.stanford.edu/~seshu/s3d_subrank/shardrefine/stacktraces/

You're sure you've enabled functional projection functors?
There are two options for debugging this:

Either you make a small example for me to play with on sapling
I'm going to give you some changes that are going to dump a metric ton of logging to help us understand what is going on.

Also, the line numbers are out-of-date with respect to the current shardrefine branch which makes it hard to understand what is going wrong. What hash was this built with?

From what I remember @elliottslaughter merged the changes for function projection functors. He will have to confirm that though.
For debugging this why dont we do both options? Given the issues we have with sapling I may not be able to reproduce this there, so you should try to add extra logging as well in the meantime while I see what I can do on sapling. Alex pinged action@cs for an update and they did not have any news other than they will continue looking at sapling.
From what I see the branch that @elliottslaughter made was rebased on to this commit of shardrefine:
commit e264eb0bd5fe7f66c596796a251dd925beec022b (origin/shardrefine)
Merge: 0ba740529 e881d2dda
Author: Mike<EMAIL_ADDRESS>Date:   Tue Oct 31 00:58:17 2023 -0700

    Merge branch 'control_replication' into shardrefine

It is the regent-fix-hip-multigpu-shardrefine branch.

From what I remember @elliottslaughter merged the changes for functional projection functors. He will have to confirm that though.

Yes, it merged into shardrefine a long time ago.

From what I see the branch that @elliottslaughter made was rebased on to this commit of shardrefine: ... the regent-fix-hip-multigpu-shardrefine branch.

regent-fix-hip-multigpu (without -shardrefine) has merged to master, so once we merge master -> control_replication -> shardrefine this will be available as well and we can prune the extra branches.

I am not able to run S3D on sapling right now it keeps hanging at startup with processes in D state.

Can you try with the most recent shardrefine branch at scale. I checked in a slightly more optimized data structure for the projection tree exchange. I want to see if it is blowing up just because STL is bad or because there is an asymptotic overhead.

Its looking much better: http://sapling2.stanford.edu/~seshu/s3d_subrank/shardrefine/startup_legion_prof.html
Down to 15 seconds from 500 seconds at 64 nodes. I submitted up to 2048 nodes so we'll see what happens with the rest.

Please get some profiles for these runs as well so we can see how things are changing.

Here is the startup time up to 2048 nodes: http://sapling.stanford.edu/~seshu/s3d_subrank/startup_legion_prof.html
Iteration time: http://sapling.stanford.edu/~seshu/s3d_subrank/average_21to30_iteration.html
legion_prof --archive profiles are here: http://sapling.stanford.edu/~seshu/s3d_subrank/
View them like this: https://legion.stanford.edu/prof-viewer/?url=https://sapling2.stanford.edu/~seshu/s3d_subrank/pwave_x_1024_hept/legion_prof/
Still waiting on 4096 and 8192 node runs.

Did you get backtrace samples from the slow start-up at 8K nodes?

The 8192 run actually worked and completed. We have scaled to the full machine on Frontier.
The 4096 run did not finish starting up. I tried to get some stack traces from that. They are here: http://sapling2.stanford.edu/~seshu/s3d_subrank/startup/

The backtraces from 4K are not interesting. Many of the files are actually empty suggesting that those processes never even started.
Did you get backtraces for 8K nodes?

The 4096 node run completed when I resubmitted. Here are the final results:
Startup: http://sapling2.stanford.edu/~seshu/s3d_subrank/startup_legion_prof.html
Iteration: http://sapling2.stanford.edu/~seshu/s3d_subrank/average_21to30_iteration.html

I'm not satisfied. I would still like to understand why the start-up is not scalable. Please get some backtraces in the middle of the startup for either the 2K, 4K, or 8K runs. There are enough nodes there that just sampling each node should give us enough of a clue as to what is going on.

Here is a test run I did at 128 nodes. I set it up to dump stack traces with gdb every 15 seconds.
http://sapling2.stanford.edu/~seshu/s3d_subrank/startup/
2048 is in the queue.

Im not sure if my script is working reliably. A lot of the stack trace files seem to be empty and I see gdb ending up in a D state. Will have to try something different.

He haven't been able to get stack trace dumping to work reliably. I might try to profile with HPCToolkit or gprof.

This worked on Perlmutter as well. Scaled to 1536 nodes full machine. Have one more machine I am planning on scaling on. Hopefully I will finish that in the next day or two.

I commented out what I think is the slow part of the remaining start-up. Can we generate results with the latest shardrefine branch on one of the machines?

I did a few smaller test runs first to make sure the build works and I'm seeing a lot of these messages: [22 - 7fffcbc0df80]    0.005833 {5}{mailbox}: Failed to send message: 111 it still seems to run to completion though.

The 2048 and 4096 node runs did not startup. The 1024 did but I did not see much improvement in startup time. It was about 55 seconds the old build was 59 seconds.

The 2048 and 4096 node runs did not startup.

At what point did they stop running? There are some known issues in Realm bootstrapping right now.

The 1024 did but I did not see much improvement in startup time. It was about 55 seconds the old build was 59 seconds.

I'd still like to see some backtrace samples to see where the time is going.

I am actually able to get profiles with hpctoolkit at small scales. Im going to go back to the commit of shardrefine that worked and try profiling with hpctoolkit at larger scales.

Its been a little hit or miss. Im still waiting for the larger runs, but I got a profile from 512 nodes and 4 nodes. Any hints for what I'm looking for?

I'm just looking for backtraces that suggest where the time is being spent in the start-up. If it was like before it is somewhere in the logical analysis, but hard to say where that is without backtraces. A few hundred different backtraces during start-up should give us a pretty good sampling of where the time is being spent.

Here is the stuff Im seeing in legion_analysis.cc:

That doesn't really make sense. If I'm interpreting the percentages on the right hand side correctly, 60% of the time is being spent somewhere else, and that is the 60% we're interested in. This is all just trace capture stuff and we know that is scalable.
I think just sampling backtraces uniformly across all the shards will be more valuable. Pick a stopping time. Capture backtraces from all shards. Resume for a few seconds and then do it again. Do that three or four times. That should give us some representative data.

Also check to make sure your profiler here understands Realm's user-level threading. If it doesn't a lot of these results are going to be quite confusing. That's why backtraces with -ll:force_kthreads are probably going to be more meaningful.

I will try dumping stacktraces again. The script I made before wasnt working reliably at larger scales, but I'll try simplifying it a bit.

Does the debugger that you're using not having something equivalent to thread apply all bt?

I am using gdb, but on some nodes its getting stuck in a D state when it attaches.

I would rate limit my script to only attach on a few nodes at a time. You might be overwhelming (a poorly implemented) filesystem.

I tried using the nvme drives on the compute nodes so each node is just writing 1 file to a local disk. Here is the launch.sh script:
#!/bin/bash
sleep_time=( [1]=3 [2]=3 [4]=3 [8]=3 [16]=6 [32]=6 [64]=6 [128]=10 [256]=10 [512]=20 [1024]=30 [2048]=50 [4096]=110 [8192]=300 )
$@ &
S3D_PID=$!
sleep ${sleep_time[$SLURM_JOB_NUM_NODES]}
outdir=/mnt/bb/seshuy
gdb -p $S3D_PID -batch -quiet -ex "thread apply all bt" 2>&1 > "$outdir/bt_$(hostname)_$S3D_PID.log"
wait $S3D_PID

It should be srun -n 1024 --ntasks-per-node 1 ... launch.sh s3d.x so you start s3d, sleep for however many seconds and then start gdb, and there should only be 1 gdb process/node writing a single file to its local nvme drive that will get copied over to the network drive after the s3d job step has completed, but when I looked at some of the nodes in the 1024 node job, gdb is still in a D state and the log on /mnt/bb/seshuy/ is empty.

I suspect the problem is with gdb probing at the whole binary to load all the symbols when it starts up and the file system becoming unhappy...

I made a version that uses sbcast to copy the shared libraries and executable to the nvme drives on the compute nodes: https://docs.olcf.ornl.gov/systems/frontier_user_guide.html#sbcast-your-executable-and-libraries
I was seeing a crash when attaching gdb at startup in Realm when it tries to create shmem, it would work when I didnt attach gdb though, but there were messages about failing to resize a shmem region. I know a bunch of stuff has been changing in Realm, so I upgraded to the latest shardrefine and it works up to 8 nodes, but at 16 nodes I'm seeing this now:
[0 - 7ffe43ffeb40]    7.041922 {5}{runtime}: [error 93] LEGION ERROR: Unable to find entry for color 9 in index space 20. (from file /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/legion/region_tree.cc:8102)
For more information see:
http://legion.stanford.edu/messages/error_code.html#error_code_93

Here is a stack trace:
[15] Thread 6 (Thread 0x7ffe41ff4b40 (LWP 33715) "s3d.x"):
[15] #0  0x00007fffe4af274f in wait4 () from /lib64/libc.so.6
[15] #1  0x00007fffe4a69ba7 in do_system () from /lib64/libc.so.6
[15] #2  0x00007fffdedf7776 in gasneti_system_redirected () from /mnt/bb/seshuy/librealm.so.1
[15] #3  0x00007fffdedf711b in gasneti_bt_gdb () from /mnt/bb/seshuy/librealm.so.1
[15] #4  0x00007fffdeded94f in gasneti_print_backtrace () from /mnt/bb/seshuy/librealm.so.1
[15] #5  0x00007fffdef0adaa in gasneti_defaultSignalHandler () from /mnt/bb/seshuy/librealm.so.1
[15] #6  <signal handler called>
[15] #7  0x00007fffe4a5bcbb in raise () from /lib64/libc.so.6
[15] #8  0x00007fffe4a5d355 in abort () from /lib64/libc.so.6
[15] #9  0x00007fffe1beccdf in Legion::Internal::Runtime::report_error_message (id=93, file_name=0x7fffe0bbb2cf "/lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/legion/region_tree.cc", line=8129, message=0x7ffe41f9973
0 "Unable to find entry for color 9 in index space 20.") at /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/legion/runtime.cc:32159
[15] #10 0x00007fffe1b39c23 in Legion::Internal::IndexSpaceNode::get_child (this=0x7ff944159a00, c=9, defer=0x0, can_fail=false) at /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/legion/region_tree.cc:8127
[15] #11 0x00007fffe1b3aa5c in Legion::Internal::RegionTreeForest::get_index_partition (this=0x688d780, parent=..., color=9) at /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/legion/region_tree.cc:922
[15] #12 0x00007fffe1c54a4a in Legion::Internal::Runtime::get_index_partition (this=0x7600ea0, parent=..., color=9) at /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/legion/runtime.cc:18315
[15] #13 0x00007fffe1734489 in Legion::Runtime::get_index_partition (this=0x688d740, parent=..., color=9) at /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/legion/legion.cc:5255
[15] #14 0x00007fffe2c7bda4 in legion_terra_index_cross_product_get_subpartition_by_color_domain_point (runtime_=..., prod=..., color_=...) at /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/bindings/regent/regent_partitions.
cc:645
[15] #15 0x00007fffe49c5531 in $<main> () from /mnt/bb/seshuy/libregent_tasks.so
[15] #16 0x00007fffe4910bcd in $__regent_task_main_primary () from /mnt/bb/seshuy/libregent_tasks.so
[15] #17 0x00007fffde1a9c3b in Realm::LocalTaskProcessor::execute_task (this=0x67ef980, func_id=2839, task_args=...) at /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/realm/proc_impl.cc:1175
[15] #18 0x00007fffde231fc0 in Realm::Task::execute_on_processor (this=0x7ff8000ca040, p=...) at /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/realm/tasks.cc:326
[15] #19 0x00007fffde23640c in Realm::KernelThreadTaskScheduler::execute_task (this=0x6694c60, task=0x7ff8000ca040) at /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/realm/tasks.cc:1421
[15] #20 0x00007fffde2351a0 in Realm::ThreadedTaskScheduler::scheduler_loop (this=0x6694c60) at /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/realm/tasks.cc:1160
[15] #21 0x00007fffde23577a in Realm::ThreadedTaskScheduler::scheduler_loop_wlock (this=0x6694c60) at /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/realm/tasks.cc:1272
[15] #22 0x00007fffde24723c in Realm::Thread::thread_entry_wrapper<Realm::ThreadedTaskScheduler, &Realm::ThreadedTaskScheduler::scheduler_loop_wlock> (obj=0x6694c60) at /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/
realm/threads.inl:97
[15] #23 0x00007fffde24a47a in Realm::KernelThread::pthread_entry (data=0x688c570) at /lustre/orion/cmb138/scratch/seshuy/legion_s3d_subrank/legion/runtime/realm/threads.cc:781
[15] #24 0x00007fffe88936ea in start_thread () from /lib64/libpthread.so.0
[15] #25 0x00007fffe4b28a6f in clone () from /lib64/libc.so.6

I am on this commit of shardrefine:
commit cd49b6b5a153d02de2244fc4666e4da587ed98bc (HEAD -> shardrefine, origin/shardrefine)
Author: Mike<EMAIL_ADDRESS>Date:   Wed Nov 15 02:04:58 2023 -0800

    legion: adding an optimization for using congruent equivalence sets across fields when making new equivalence sets

I found that shmem crash with the old build depends very heavily on when we attach with gdb, just changing the sleep time seems to make it go away. Another thing I found is that gdb does eventually get out of the D state but by the time it does s3d will have already exited. Maybe I might try not sleeping at all at larger scales and see what happens.

I guess its possible to write the symbol table to a file and have gdb reuse that file when it runs a program. I'm not sure if that will work with attach, but I'll give it a try and see. Or maybe we can use LAUNCHER='gdb --args'

I am on this commit of shardrefine:

You should check the CI before switching to new commits of a development branch:
https://gitlab.com/StanfordLegion/legion/-/pipelines/1073205477

Closing this now that shardrefine is merged.


Set default values for variables in run-squeezelite

That would give more flexibility especially with the upcoming feature allowing to combine presets.
This feature will allow to set more configuration parameters in presets.
So for example if DELAY is never set, I would like the default to be applied. So it needs to be blank in the Dockerfile.

Implemented


Use ITensorNetworks.heisenberg in PEPS example

Use ITensorNetworks.heisenberg in PEPS example.

Hopefully helps a test issue that popped up in #116.


Please share Write benchmark as well

Hi, Can you also share write performance benchmark against badger, bolt and other as provided for read?

You can find the benchmarking tool at https://github.com/akrylysov/pogreb-bench it measure the write and read performance for pogreb, goleveldb, bbolt and badger.

Choosing the right data structure and optimizing the store for the specific use case (random lookups) allowed to make Pogreb significantly faster than similar solutions.


Resolve imports

What are all those changes to .gitignore? Which lines of those are really needed for IntelliJ? They seem to be copy-pasted from elsewhere and I'm not sure if you are able to contribute it directly.

Sorry, my mistake. It's fixed now.


When using vim extension, cursor navigation with keyboard doesn't trigger matching symbol highlights

Install Vim extension (I don't think an extension should be able to break this, so filing it here)
Enter insert mode (or not)
Move the cursor over a symbol in a TS file
Matching symbols should be highlighted, but they are not
If I click somewhere on the same symbol, then matches are highlighted

+1

+1

I found a workaround! If you just want to highlight the current word, you can use # or * command to navigate previous or next matched word.

Would nice to at least get typical mouse cursor functionality with a keypress, so i hover over a word or linter error or whatever and hit a key and I get the same effect as if I had hovered in that location.

@rebornix Not sure 100% what you mean, but I think the problem here is that we lose the information that the cursor was moved due to a direct interpretation of a keypress (i.e. not like jump to definition or undo, etc)... Would be good if we would have a way to distinguish the vim case from the rest of the users of TextEditor.selections

This issue was moved to VSCodeVim/Vim#3044

I added a command for triggering the word highlight if there is no word highlighting available in the document (meaning the word highlighting feature is enabled but there are no decorations for current word). The Vim extension can decide when to call this command to run the word highlighting.

@rebornix Anything to verify on this or is it an upstream issue now?

@mjbvz it's an upstream now, we added a command editor.action.wordHighlight.trigger now to trigger the highlight programatically so if that command works for you always, then it's valid.


Remove aws provider block from the module

replace the hardcoded provider block
changeset

Confirmed working by running a plan against an internal deployment (see internal Linear ticket for details)


NEI CRASH

Still a recipe crash after suggested AE2 rv2 build 18 update
I even disabled AE2 integration with Mekanism
Still no go.
http://pastebin.com/D31HZ4yW

I can assure you this is not a Mekanism issue - if you install Mekanism without any other mods, you won't get the crash.  The only thing I can suggest is to find the offending mod by means of removing each one individually, and then report the integration issue to their bug tracker.

it was minetweaker 3.09c or modtweaker 2 -0.7.5
thanks for the fast response and help..truly appreciate it! :)
#wouldn't want you're job

No worries! :)


Please Support laravel 8.

Here is the composer log:
Problem 1
    - Root composer.json requires code-lts/laravel-fcm ^1.5 -> satisfiable by code-lts/laravel-fcm[1.5.0].
    - Conclusion: don't install laravel/framework v8.15.0 (conflict analysis result)
    - code-lts/laravel-fcm 1.5.0 requires illuminate/support 5.* || ^6 || ^7 -> satisfiable by illuminate/support[v5.0.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev].
    - Only one of these can be installed: illuminate/support[dev-master, v4.0.0-BETA2, ..., 4.2.x-dev, v5.0.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev], laravel/framework[v8.15.0, 8.x-dev]. laravel/framework replaces illuminate/support and thus cannot coexist with it.
    - Root composer.json requires laravel/framework ^8.15 -> satisfiable by laravel/framework[v8.15.0, 8.x-dev].

Duplicate of #8

Hi !
Please have a look to https://github.com/code-lts/Laravel-FCM/issues/8#issuecomment-703908098
And let me know as soon as possible so I can release the next version


feature is not passed to style function when set via .setStyle()

I'm using style functions. They work well when set on a layer level.
However, when I'm trying to set styles to individual features using feature.setStyle(stylefunction), it doesn't work. The problem is that the feature is not passed on to the style function, only the resolution.
So normally it's calling a styleFunc(feature, resolution) but when set via .setStyle() it's calling styleFunc(resolution).
version: 3.20.1

This is intentional and documented. See http://openlayers.org/en/latest/apidoc/ol.html#.FeatureStyleFunction. The feature will be this.
If you think the documentation could be improved here, please submit a pull request.

But this way how can I use the same function for both cases?
I cannot image but a very ugly hack using generic variable names (a, b, c)
and somehow rewriting them to feature, resolution based on if "this" is
present.
On 2017. Jan 28., Sat at 7:26, Andreas Hocevar<EMAIL_ADDRESS>wrote:

This is intentional and documented. See
http://openlayers.org/en/latest/apidoc/ol.html#.FeatureStyleFunction. The
feature will be this.
If you think the documentation could be improved here, please submit a
pull request.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openlayers/openlayers/issues/6411#issuecomment-275830739,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAeKj4YEX6YhkmfyOG2wbNEPCdB6bg9pks5rWt-FgaJpZM4LwZcb
.

You are right. We should discuss whether we want a breaking change that ol.Feature uses the same style function signature as ol.layer.Vector.
In the meantime, you can do something like this:
function featureStyleFunction(resolution) {
  return layerStyleFunction(this, resolution);
}

I agree this is a bit odd API-wise. but a change here would affect nearly all users,  I guess.

Actually we can make this change without breaking existing applications. Pull request to come.

Wow it looks great. I didn't know about function.length, especially that
it's been there since JavaScript 1.1!
On 2017. Jan 28., Sat at 14:37, Andreas Hocevar<EMAIL_ADDRESS>wrote:

Actually we can make this change without breaking existing applications.
Pull request to come.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openlayers/openlayers/issues/6411#issuecomment-275848606,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAeKj881PaXT9tTsWwi6kf-TD8Phz_UQks5rW0SwgaJpZM4LwZcb
.


Fix examples in README.md

Coverage remained the same at 100.0% when pulling ed637edea8a91ae9b430d62d720c239a8853a3fb on SaadeMotion:patch-1 into 3ac51f4cf1ae7b74fef5cabb4a1e42012d6ccb60 on rickydunlop:master.


Bring documentation into master from gh-pages?

GitHub pages have now changed so you can nominate a directory in the master branch as the location of the pages to render. This makes the gh-pages branch redundant. I believe the new way much better for projects and for actually getting website changes done.

I am just wondering if the gh-pages branch is currently used, dlanguage.github.io is a 404.

I don't think the gh-pages is used but I think it would be worth giving it a massive overhaul.
http://intellij-dlanguage.github.io/intellij-dlanguage/
It's very out of date
Is this something you want to pickup?

I can certainly do something with this. Step 1 for me is to ditch the gh-pages branch and put the stuff into master/develop in the /docs directory or have a separate repository. It may be just me but I don't find the separate branch approach at all workable.

I've created https://github.com/intellij-dlanguage/intellij-dlanguage.github.io and moved the old gh-pages stuff into there. From now on we can maintain it there. I'll delete the gh-pages branch.
new site url is simply https://intellij-dlanguage.github.io/ as it for the organisation as a whole it can include documentation for any other related projects we have


Concurrent auth failure due to duplicate DB write conflict

With RBAC enabled, when there are multiple concurrent auth operations, the auth fails because RBACRemoteGroupToRoleSyncer sync operation error on duplicate DB write conflict.
ERROR base [-] Conflict while trying to save in DB.Traceback (most recent call last):File "/opt/stackstorm/st2/lib/python2.7/site-packages/st2common/persistence/base.py", line 173, in add_or_updatemodel_object = cls._get_impl().add_or_update(model_object)
File "/opt/stackstorm/st2/lib/python2.7/site-packages/st2common/models/db/__init__.py", line 314, in add_or_updateinstance.save()
File "/opt/stackstorm/st2/lib/python2.7/site-packages/mongoengine/document.py", line 408,
NotUniqueError(message % six.text_type(err))NotUniqueError: Tried to save duplicate unique keys (E11000 duplicate key error collection: st2.user_role_assignment_d_b index: role_1_user_1 dup key: { : "base_permissions", : "foobar" })
ERROR handlers [-] Failed to synchronize remote groups for user "foobar"
Traceback (most recent call last):File "/opt/stackstorm/st2/lib/python2.7/site-packages/st2auth/handlers.py", line 202, in handle_auth syncer.sync(user_db=user_db, groups=user_groups) File "/opt/stackstorm/st2/lib/python2.7/site-packages/st2common/rbac/syncer.py", line 423, in sync is_remote=True)
File "/opt/stackstorm/st2/lib/python2.7/site-packages/st2common/services/rbac.py", line 207, in assign_role_to_userrole_assignment_db = UserRoleAssignment.add_or_update(role_assignment_db)
File "/opt/stackstorm/st2/lib/python2.7/site-packages/st2common/persistence/base.py", line 185, in add_or_updatemodel_object=model_object)
StackStormDBObjectConflictError: Tried to save duplicate unique keys (E11000 duplicate key error collection: st2.user_role_assignment_d_b index: role_1_user_1 dup key

This DB conflict occurs at https://github.com/StackStorm/st2/blob/v2.3/st2common/st2common/rbac/syncer.py#L421.

With multiple concurrent auth operations I assume you mean multiple invocations of st2-apply-rbac-definitions run in parallel.
In any case, thanks for reporting and digging in, I will have a look.


Set assumedWaitForSync when creating replicated log

Scope & Purpose
Set assumedWaitForSync on log creation

Will add test as well.

The failure might be related to this: https://arangodb.atlassian.net/browse/CINFRA-312


Support Retrograde Seconds

Retrograde Hours
“Retrograde” hands sweep a segment of a circle before springing back to their initial position to begin their movement again. Their endless choreography is an inspiration for innovative and highly spectacular dials.
Learn more here
Watch it live here
Specs

The functionality should exist within the existing Dials.js module
Discussion: How best to include the property in the existing Dials object?

dials: [{
        hands: {
          hour: 'retrograde-sec-hour-hand',
          minute: 'retrograde-sec-minute-hand',
        },
        retrograde: {
          second: {
            id: 'retrograde-second-hand-one',
            max: 180,
            duration: 10
          }
        }
      },
    ]

Functionality
TickTock will assume the retrograde hand will be designed in its beginning position, 0 degrees. Be defining a max value, the seconds will be evenly divided amongst that range. Upon reaching the end of the range, the hand will reset back to its original position.
Considerations

Watches contain retrograde hours, minutes, and seconds. Building a solution that can be leveraged for all three is the goal

Does this possibly warrant a separate Module?

Settled on this format:
dials: [{
        hands: {
          hour: 'retrograde-sec-hour-hand',
          minute: 'retrograde-sec-minute-hand',
        },
        retrograde: {
          second: {
            id: 'retrograde-second-hand-one',
            max: 180,
            duration: 10
          }
        }
      },
    ]

Implemented and tested but will review further before merging and releasing 2.11.

Included in v2.11.

Reopening after Seconds hand updates. Will fine tune this along with the hours and minutes at the same time to roll out al Retrograde functionality at once.

This will be released with V4, or Horologist V1.