Can't change steam anymore

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you're not using someone else's docker image?

Yes

Have you searched for similar issues (both open and closed)?

Yes

Describe the bug
i want to change a stream after saving i get this meesage
"data must NOT have additional properties, data must NOT have additional properties, data must NOT have additional properties, data must NOT have additional properties, data must NOT have additional properties"
Nginx Proxy Manager Version
v2.12.1 © 2024 jc21.com. Theme by Tabler
To Reproduce
Steps to reproduce the behavior:

Go to 'steams
Click on 'on of your streams'
Save it
See error

Wiorkaround -> Downgrade to version 2.11.3

Do you use docker volumes or docker mounting system paths?

i have tested both and both do not work in the new version

I have the same issue. Editing existing streams causes the error. Here's my docker compose (I'm forwarding the 8022 port, the nginx-net network is a bridge, and used for attaching other containers):
networks:
  nginx-net:
    external: true

volumes:
  nginx-proxy_data:
  nginx-proxy_letsencrypt:

services:
  nginx-proxy:
    image: jc21/nginx-proxy-manager:latest
    restart: unless-stopped
    networks:
      - nginx-net
    ports:
      - 80:80
      - 443:443
#      - 81:81      # Use this if something goes wrong
      - 8022:8022
    volumes:
      - nginx-proxy_data:/data
      - nginx-proxy_letsencrypt:/etc/letsencrypt
    environment:
      DISABLE_IPV6: 'true'
    healthcheck:
      ...

There's nothing in docker logs. Rolling back to 2.11.3 resolves the issue

I'm also encountering this issue on 2.12.1 both on docker and Proxmox LXC (installed through this script.
Here's my configuration
`services:
nginxproxymanager:
image: jc21/nginx-proxy-manager:latest
restart: unless-stopped
ports:
# These ports are in format :
- 80:80 # Public HTTP Port
- 443:443 # Public HTTPS Port
- 81:81 # Admin Web Port
# Add any other Stream port you want to expose
# - '21:21' # FTP
  # Uncomment the next line if you uncomment anything in the section
environment:
  # Uncomment this if you want to change the location of
  # the SQLite DB file within the container
  # DB_SQLITE_FILE: "/data/database.sqlite"

  # Uncomment this if IPv6 is not enabled on your host
  DISABLE_IPV6: "true"
volumes:
  - /opt/nginxpm/data:/data
  - /opt/nginxpm/letsencrypt:/etc/letsencrypt`


multigpu training

When I set config as follows to perform multigpu training:
"devices": ['cuda:0', 'cuda:1', 'cuda:2', 'cuda:3']
I got the following error:
Traceback (most recent call last):
File "train.py", line 178, in
main(args)
File "train.py", line 124, in main
train_one_epoch(
File "/home/dengandong/Research/actionformer_release/libs/utils/train_utils.py", line 277, in train_one_epoch
losses = model(video_list)
File "/home/dengandong/anaconda3/envs/gtad_pt110/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
return forward_call(*input, **kwargs)
File "/home/dengandong/anaconda3/envs/gtad_pt110/lib/python3.8/site-packages/torch/nn/parallel/data_parallel.py", line 168, in forward
outputs = self.parallel_apply(replicas, inputs, kwargs)
File "/home/dengandong/anaconda3/envs/gtad_pt110/lib/python3.8/site-packages/torch/nn/parallel/data_parallel.py", line 178, in parallel_apply
return parallel_apply(replicas, inputs, kwargs, self.device_ids[:len(replicas)])
File "/home/dengandong/anaconda3/envs/gtad_pt110/lib/python3.8/site-packages/torch/nn/parallel/parallel_apply.py", line 86, in parallel_apply
output.reraise()
File "/home/dengandong/anaconda3/envs/gtad_pt110/lib/python3.8/site-packages/torch/_utils.py", line 425, in reraise
raise self.exc_type(msg)
RuntimeError: Caught RuntimeError in replica 0 on device 0.
Original Traceback (most recent call last):
File "/home/dengandong/anaconda3/envs/gtad_pt110/lib/python3.8/site-packages/torch/nn/parallel/parallel_apply.py", line 61, in _worker
output = module(*input, **kwargs)
File "/home/dengandong/anaconda3/envs/gtad_pt110/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
return forward_call(*input, **kwargs)
File "/home/dengandong/Research/actionformer_release/libs/modeling/meta_archs.py", line 339, in forward
feats, masks = self.backbone(batched_inputs, batched_masks)
File "/home/dengandong/anaconda3/envs/gtad_pt110/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
return forward_call(*input, **kwargs)
File "/home/dengandong/Research/actionformer_release/libs/modeling/backbones.py", line 130, in forward
x, mask = self.embd[idx](x, mask)
File "/home/dengandong/anaconda3/envs/gtad_pt110/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
return forward_call(*input, **kwargs)
File "/home/dengandong/Research/actionformer_release/libs/modeling/blocks.py", line 46, in forward
out_conv = self.conv(x)
File "/home/dengandong/anaconda3/envs/gtad_pt110/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
return forward_call(*input, **kwargs)
File "/home/dengandong/anaconda3/envs/gtad_pt110/lib/python3.8/site-packages/torch/nn/modules/conv.py", line 298, in forward
return self._conv_forward(input, self.weight, self.bias)
File "/home/dengandong/anaconda3/envs/gtad_pt110/lib/python3.8/site-packages/torch/nn/modules/conv.py", line 294, in _conv_forward
return F.conv1d(input, weight, bias, self.stride,
RuntimeError: Given groups=1, weight of size [512, 2048, 3], expected input[2, 512, 2304] to have 2048 channels, but got 512 channels instead
It is weird since the feature dimension seems to be divided by the GPU number.
Similarly, the dimension changes to 1024 when I use 2 GPUs.

Our current codebase does not support multiple GPU training. Please refer to #38 for more details.

Our current codebase does not support multiple GPU training. Please refer to #38 for more details.

Got it. Thanks.


Implement pickban stream overlay

i think itd be better to calculate the map winner client-side/endpoint-side instead(?) since sending the scores may be relevant based on whatever cavoe is thinking of adding to stream overlays, and especially considering we removed the team1Score and team2Score fields for matchup_map pretty recently with that in mind too @ThePooN thoughts...
otherwise if we are keeping that field, then this pr also needs a migration file made (can do with npm run typeorm -- migration:generate MIGRATIONNAME -d ormconfig and removing any extraneous changes added in the generated file)
fwiw winner calculation client-side is how i've been doing it for the referee/_id.vue page at least

GET API should be centered around data retrieval rather than logic.
As we provide our API to COE and eventually other tournaments, it should be considered a product of its own, and we should keep it as simple as possible to not break 3rd-party functionality, unless it provides added value (such as shared logic in multiple front-end projects or speed on popular pages).
It is probably not worth it modifying the DB/API schema for this feature, I'd rather have multiple API calls to gather and reconcile the data if necessary.
So basically keep it to the front-end unless otherwise necessary, which seems to be the right course of action here.


fmigacz update devsecops GitHub

Issue #2381

Include secret scanning in GitHub Security features
Add a consideration of feature variance based on organizational licensing and repo visibility (public/private) - link to pricing

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions


Update README.md

That option depends on which version you're using. I'm closing this pull request but still editing the README. Thanks !


Add initial .gitignore

Ignore VIM temporary files and OS configuration metadata

@binary-sequence PR is out of date with base branch, could you please update?

@binary-sequence could you explain further why these files are landing in your local repo?

@binary-sequence could you explain further why these files are landing in your local repo?

macOS creates .DS-Store
When vim backup setting is enabled, it creates backup files with filename~

It is not produced by the course code.
It is a good practice to ignore any file or directory created by the OS or tool used.
People using Windows or another editor could also add more ignore rules.

Branch updated


Upgrade to Twilio Voice SDK 6.x

https://www.twilio.com/docs/voice/voip-sdk/ios/changelog#621

Thanks! This is definitely on the list of improvements to make

Fixed in https://github.com/jefflinwood/cordova-plugin-twiliovoicesdk/pull/88


WIP: call testing

Ok, there's still a lot skipped and I think we've decided to change some things, but let's get this into master.
Future changes:

do not renegotiate for toggleLocalAudio()/toggleLocalVide() (unless we need to establish an audio/video stream).
refactor the #remoteMediaStream and #localMediaStream tests to remove the extra tick (using call.when() is introducing an extra tick and therefore allowed one of the more annoying bugs to go undetected)


feat: add remote-entry script resource retry for retry-plugin

Description
feat: add remote-entry script resource retry for retry-plugin

Related Issue

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] I have updated the documentation.

can you add new test cases for the feature?


markdown: only update template when file changed

Signed-off-by: Tw<EMAIL_ADDRESS>
1. What does this change do, exactly?
Only update template when file changed
2. Please link to the relevant issues.
#1908
3. Which documentation changes (if any) need to be made because of this PR?
N/A
4. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I am willing to help maintain this change if there are issues with it later

Would someone else like to review this and merge if it's good? I'm a bit swamped this week.


FR: can we put debug level for catching errors (log) under  "advanced settings"

under "advanced settings" putting  debug level option can help us to catch lot of errors and bugs.
at the moment we are building uproxy from dev to test .

Might be a good place to export logs from too.

@zahoriea FYI

@jpevarnek After https://github.com/uProxy/uproxy/issues/914 this is a good followup that I think will end up helping us all. In particular, if we add a text box where user can specify a debug level string; and also a way to export the logs, e.g. into a an HTML chrome extension controlled page.

After discussion, it seems like it would be better to leave this out of the UI.  Any solution that would give developer's solid enough control over logging seems as if it would interfere too much in the user experience.
I think a better way to deal with this issue would be to allow a console command (in the app window) to change the logging level.

@iislucas Daniel had said a while back that you might have some ideas for how to pass calls (my ideal would be to have a setLogLevel function that would proxy to the freedom call regardless of which context it was called in) to the correct context

@willscott @soycode @ryscheng So the question here is when a new logger is created, what happens in the logging provider, and in particular, is there a way for the logging provider to send messages to each registered logger? (We'd really like this as it would allow us to drop many IPCs which are currently causing delays of up to 2 mins of IPC congestion on heavy network traffic when there are lots of log messages)

And also: to send messages to a particular registered logger. :)

@iislucas sorry, this was a different question than that.  This is just: is it possible to have a function exist in every context that will be able to access the logging provider in some way.

That's what including the logging class does; include it in each module and you have the same interface for logging... but I'm sure you know that so I'm not getting the questions; ask me tomorrow! :)

Re: "is there a way for the logging provider to send messages to each registered logger?"
No, I don't think that is possible right now. My understanding is that uProxy makes heavy use of console.log/warn/error and you'd like the ability to essentially turn some of these into noops in order to reduce the number of messages being sent to the logging provider. Since our cross-module interfaces is basically an RPC system, we haven't added any logic that would allow you to do that.
My recommendation is that uProxy maintains internal state on the desired log level and call/notcall the logger as appropriate.

It seems like we should cut down on some of debug logging, e.g. bytes sent and received. This is extremely useful when debugging at a very low level but I think if you're at that level then you need to add about a million ad-hoc printfs anyway so they may not be buying us that much.

Agreed.
We discussed this yesterday; conclusion was that we can actually solve this in the way I was hoping. We'll create a new logging provider API for events, which will be events to specify which things should be logged vs not. Our logger code will then listen to log-filter events, and update it's local filters appropriately. This will allow the local module's logger to filter messages before sending to the logging provider. I think will be a very nice solution.

(Clarifying description to reflect plan)

Closing, working on under #1005


Update install choice buttons

This PR does the redesign of the picking up provider buttons (install choice buttons). Currently, design is pretty different between 1) docs Overview page 2) Get Started page 3) In app. With this, we unify the design so all the places look pretty the same.

docs Overview page (width: more than 980px, 3 columns)

Get Started page (width: between 620px and 980px, 2 columns)

In app (width: more than 980px, 3 columns)

width less than 620px, single column

This PR does the redesign of the picking up provider buttons (install choice buttons). Currently, design is pretty different between 1) docs Overview page 2) Get Started page 3) In app. With this, we unify the design so all the places look pretty the same.

Thanks for updating this!
The one thing that sticks out for me is the extra white space around most of the buttons (i.e. those without two lines of description) - it doesn't feels right visually to me.
I wonder if we should require that the description texts are one line maximum after all?

The one thing that sticks out for me is the extra white space around most of the buttons (i.e. those without two lines of description) - it doesn't feels right visually to me.

That is intentional, to not have to worry about the length of the description text. In my design I vertically centered the description text tho, and I think that helps visually.
Screenshot for reference

If you feel strongly about, I am happy to forfeit this tho, but I am sure this will bite us later, and I rather go for clarity in communication than optimizing for visual things.

It would be nice to have the cards be uniform height, like in the design (whether through setting a min-height or limiting to a single line of text; I don't feel strongly about that).
Also, I'm not sure if we need the "and many other environments" on self-managed if we are explicitly going to add a note like "Don't see your platform listed? Learn how to integrate Postgres on other providers." below.

Re: vertical alignment, I was lazy about it so good job everyone for pointing that out. Here is some single line version (by making it shorter for both Azure and self-managed per Lukas/Maciek's suggestion):

It's simple, but this could still be two lines description when the width got smaller, and the button size can be different depending on two lines v.s. one line:

Here is a min-height version, with min-height being 38px + line-height 19px:

Which one do people prefer? 1) line-height 100% 2) min-height 38px?
Also should we cut the description part to be a single line with the normal screen size?

Nice, this looks awesome. I prefer the min-height version, but +1 to either one (the other cleanup makes the height difference stand out less, I think). It might also be worth testing with different levels of browser zoom to make sure nothing breaks in the desired approach (that should trump any aesthetic concerns).
Not sure what you mean by cutting the description and which is the normal screen size. If it's whether to cut it to what you have in the screenshots, +1: that works great. If it's too cut it further for the second, narrower screen size: I don't think that's necessary.

Nice, this looks awesome. I prefer the min-height version, but +1 to either one

I'm currently adopting the min-height version, I think this works well too 👍

It might also be worth testing with different levels of browser zoom to make sure nothing breaks in the desired approach

I checked with Chrome, Safari, Firefox and all of them act pretty much the same. When to change from buttons count in one row (there are 3, 2, 1 cases) is still a bit questionable, but I don't think it's too off. You can checkout the review app for this too:
https://pganalyze-we-install-ch-eglz0u.herokuapp.com/docs

Not sure what you mean by cutting the description and which is the normal screen size

Sorry, I completely understand your confusion 🤦 (I don't even know what I meant).
I think I was asking if adopting Lukas/Maciek's feedback for the shorter version (e.g. dropping "for PostgreSQL" for Cosmos) look okay to everyone.

Ok updated based on the PR review sessions today. The major thing is to align install and feature choice aligned, in the Overview page. Attached screenshots for both large screen + mobile, but you can also check out the deploy preview in https://pganalyze-we-install-ch-eglz0u.herokuapp.com/docs/

And this is how it looks in-app:

No, no, I kept an eye on it, but did not have any other feedback. Looks great!


[SUPPORT] Support MetaSync Even there is no new data, Just create the table if not exist in DeltaStream

I have wanted to sync the hudi table in HIVE Catalog, but not able to sync, due to no new data in Source while using DeltaStream.
It should create a table if not exist or leave as it. if it is empty otherwise do what it was doing earlier.
Environment Description

Hudi version :0.12.1

Spark version : 3.3.0

Storage (HDFS/S3/GCS..) : s3

Running on Docker? (yes/no) : no

this looks doable but not sure how much benefit this will give. @Amar1404 can you elaborate on the benefit of this feature pls?


Update link for Sync Wizard evaluation

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

#sign-off


Clear handler?

Example
button.onTap(handler:{
    // do stuff
})

How do I clear this handler to avoid a leak when my VC is deallocated?

See here: https://stablekernel.com/how-to-prevent-memory-leaks-in-swift-closures/#toc_2.
button.onTap(handler:{ [weak self] in
    self?.doStuff()
})

So there is no way to clear the handler on the button?

If you can help me understand the problem, I'll be able to help you and also help myself in order to provide the best solution for your (and other's) use case.
It just simply uses target-action, so everything is weakly held. The closure will stay around as long as you have the button strongly held by your VC, just the way that a target-action handler stays around when you use @IBAction or something.
If all you want to do is remove the handler, there are a few ways to do that right now as a work-around:
button.removeTarget(nil, action: nil, for: .touchUpInside) removes all touch up inside events
button.onTap {} sets the handler to do nothing
Let me know if this works or maybe what you're trying to accomplish and I'll try to assist as best I can.

i think he is talking about the .removeTarget.
for example
button.onTap = { [weak self] in  self?.loadData() } button.onTap = { [weak self] in  self?.loadData() }
if we tap the button, we load the data twice, right?

Ah ok. Yes, I just saw this bug yesterday and fixed it. Please upgrade to v0.3, as it is fixed there.
I will leave this issue open, however, because I think it would be beneficial to have an explicit way to remove the handlers.
Good find, and thanks for the feedback!

Actually I was saying if I can do this
button.onTap(handler:{
    // do stuff
})

then I would like to do this
button.removeOnTapHandler()

Hello
Any news on this?
I would like the block to be deleted when the object is deleted without additional code

Objects are removed without additional code. This issue is for an enhancement to have it explicitly removed. If you are having those types of issues you'll have to post a new issue with your code so we can take a look. Likely it may be a retain cycle in your closure handler (retaining self typically).


Refactored the code display the total number of users in the music room for the users counter workflow

Endpoint is: http://<IP_ADDRESS>:8000/music/api/v1/header-user-count/

I meant this "Refactored the code to display the total number of users in the music room for the users counter workflow"


chore(deps): update Release-Notes-Preview action

:tada: This PR is included in version 3.4.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[MS Teams]-Post request to smba.trafficmanager.net/xxx/v3/conversations/xxxx/activities/xxx returns canceled status

bot Builder: 4.5.1 C#
step to reproduce

install bot in teams channel and type a query.it returns response.
deploy code changes and ping bot with sample query.
bot returns error message.

how to handle smba.trafficmanager failure.

@clearab Can you help triage this?

I'm not quite sure what you mean, could you provide a code sample or more detailed information about what you're trying to accomplish? Are you starting from one of our code samples?

@clearab , we used 46.teams-auth bot sample . we have been while in teams channel and after every deployment bot not responding to user query.but if they signout and signin , it starts working . As a bot team, we are facing difficulties to explain this process to each one of the users. Please provide your suggestion to handle better.

@clearab Yes, its from bot( logout and sign-in) .our bot is supporting domain functionalities (more than 21 process areas) adoption of 150k users .we have test and live environment and this issue occurring on both environment and most of the user are facing same error as mentioned here. Also verified in application insight log and it shows only this dependency failure.

It sounds like you're trying to either continue a conversation using a conversationId that no longer exists, or maybe trying to use an expired user token. Can you debug and figure out what specifically is happening in your code when this error is thrown? Since it is happening once for each of your users, I'm guess there is something amiss in like your user or conversation state storage. @Jeffders  or @carlosscastro maybe you have some ideas?

I'm going to close this for now - please feel free to re-open if you have additional information to share.


fix agg dial

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

Comparison is base (46da825) 95.15% compared to head (66399fa) 95.15%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #729   +/-   ##
=======================================
  Coverage   95.15%   95.15%
=======================================
  Files         124      124
  Lines        4854     4855    +1
=======================================
+ Hits         4619     4620    +1
  Misses        235      235

Flag
Coverage Δ

unittests
95.15% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Users wrongly receiving WETH on Ethereum/Rollups

Problem
We've had a couple reports from users, for example one sent from BNB to Ethereum and received WETH https://discord.com/channels/454734546869551114/1071479822414532650/1071481363787698329
Solution
Users should be receiving native ETH where possible otherwise ERC20
ex/ For the mainnet and L2 destination chains, user should receive native ETH by default
X --> Ethereum
X--> Optimism
X --> Arbitrum
We should show this in the UI as well (ETH receive) BUT allow a dropdown on destination to receive WETH instead, to cover all usecases

This was implemented through
https://github.com/connext/monorepo/issues/2946
https://github.com/connext/monorepo/issues/2642

updated spec for optionality


feat(lexical-react): add initialEditorState for LexicalCollaborationPlugin

This PR is a follow-up of this discord thread.
I tested this feature, by connecting the WebsocketProvider to my custom Websocket server which removes the YDoc from persistence when there were no connections (last user disconnected)
Here is the initialEditorState that I passed to CollaborationPlugin
              <CollaborationPlugin
                id="main"
                providerFactory={createWebsocketProvider}
                shouldBootstrap={!skipCollaborationInit}
                initialEditorState={`{"root":{"children":[{"children":[{"detail":0,"format":0,"mode":"normal","style":"","text":"1","type":"text","version":1}],"direction":null,"format":"","indent":0,"type":"paragraph","version":1},{"children":[{"detail":0,"format":0,"mode":"normal","style":"","text":"22","type":"text","version":1}],"direction":null,"format":"","indent":0,"type":"paragraph","version":1},{"children":[{"detail":0,"format":0,"mode":"normal","style":"","text":"333","type":"text","version":1}],"direction":null,"format":"","indent":0,"type":"paragraph","version":1}],"direction":null,"format":"","indent":0,"type":"root","version":1}}`}
              />

Thanks for working on it!

@zurfyx Just realized that 0.5 has plans to move initialEditorState to composer component. Idea of this PR is to provide default editor state when collab server does not have any data, which means LexicalComposer will still have to have initialEditorState=null, and the CollabPlugin can optionally have initialEditorState (in case users want something more than empty paragraph). Any concerns?

@strdr4605 thanks for this - can you fix the linter error? If so we can merge this for 0.5

Thank you for your contribution @strdr4605! We discussed this as a team, while we think this is correct we want to double down on the initiative to move the initialEditorState to LexicalComposer https://github.com/facebook/lexical/pull/3032.
@fantactuka is working on the Collab equivalent, a LexicalCollaborationComposer, which besides the initialEditorState it will also remove the need to have a separate Collab plugin and have all the collab basics initializing altogether.

Thank you for your contribution @strdr4605! We discussed this as a team, while we think this is correct we want to double down on the initiative to move the initialEditorState to LexicalComposer https://github.com/facebook/lexical/pull/3032.
@fantactuka is working on the Collab equivalent, a LexicalCollaborationComposer, which besides the initialEditorState it will also remove the need to have a separate Collab plugin and have all the collab basics initializing altogether.

Ok. Waiting for the implementation!

Also, while preparing for our release. Testing the collaborative editing with ~4-6 users, we had some should not happen errors from lexical. And we are not sure where the problem is, lexical? Yjs or our websocket implementation.
I would suggest to test collaborative with ~4 users (different browsers), maybe running 2 instances of playground with yjs ws servers connected one persistence DB.

We recently updated errors so it should be easier to spot what has happened: https://github.com/facebook/lexical/pull/2971

Don’t forget to update any documentation if needed.


Add a wiki entry on how to configure Coverity Scan build spy

https://pixhawk.org/dev/configuring_coverity_scan_cross_build


Custom Form Elements

We have to find a good way to handle custom form elements. Of course we can create very fast standard forms based on the 15 generic form elements. But you will always come to the point where you want to have some custom form elements like search or something else.
The question ist, how we can handle that need without "polluting" the generic platform. Here're some possible solutions (there can be more):

Integrate a custom form element as npm package.
Integrate the whole form as npm package.
Define a generic field with http request (does not solve the problem, that you want to show the results in a for the case suitable way.)
Use some kind of microfrontend solution.
...

@dominikhorn93

Here's an other idea (this is an older and more high fliyer one)

@dominikhorn93 Do we not already have that? @martind260 showed us how to integrate custom inputs. That was exactly what the picture ist showing.
Please close the issue if that's correct

We need a way to integrate custom inputs. One way could be to achieve this via WebCompontens and an interface that we specify.


Performance Optimizations for Non-Bulk Indexing

The indexer was designed for bulk-indexing. However, it may become necessary to point the indexer at a single file (or a small batch). Until now, that would require a not insignificant overhead.

Replaced --no-patch with --patch

patching is not common

Check if the file already exists in the FC before collecting its metadata

unless given --patch, skip the file
this will save significant time
also decreases (but does not eliminate) the need for blacklists (--blacklist-file)

Optimize for single-processed indexing (--processes 1 / the default case)

successive child processes are no longer spawned when there's only one process

Added option for not recursively indexing (-n/--non-recursive)

the indexer will only index the filepaths it's directly given, and will ignore any directories
it's a freeby, so might as well add it

closes https://github.com/WIPACrepo/file-catalog-indexer/issues/23
closes https://github.com/WIPACrepo/file-catalog-indexer/issues/24

depends on https://github.com/WIPACrepo/iceprod/pull/294 for git pips


fix: send transaction clobbers fee (fixes #67)

PR-Codex overview
Focus of the PR:
This PR focuses on refactoring the code in the base.ts file for the provider module.
Detailed summary:

Added a new overrides object of type UserOperationOverrides.
If request.maxFeePerGas is provided, it is assigned to overrides.maxFeePerGas.
If request.maxPriorityFeePerGas is provided, it is assigned to overrides.maxPriorityFeePerGas.
The previous code block that assigned maxFeePerGas and maxPriorityFeePerGas directly to the sendUserOperation function has been replaced with the overrides object.
The maxFeePerGas and maxPriorityFeePerGas properties are removed from the sendUserOperation function call.
The overrides object is passed as an argument to the sendUserOperation function.
The waitForUserOperationTransaction function is called with the hash parameter and the result is returned.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Current dependencies on/for this PR:

main

PR #78   👈

This comment was auto-generated by Graphite.


use yaml.safe_load instead of yaml.load

It is not safe to call yaml.load with any data received from an untrusted source. It allows instantiation of arbitrary objects. The function yaml.safe_load limits this ability to simple Python objects like integers or lists. For security reasons, yaml.safe_load is used.

@m4dcoder Can you please add a small test case for it? Here is quick example of similar test case I added recently - https://github.com/StackStorm/st2/pull/4846/files#diff-4d4c6f566c2d72910eff03ac16f442387a53beb0aa7e9b0ad5944ec5ce602ab2R101.
Besides that, LGTM.

We just reformatted the code with black. (Hooray!)  (Arrgh!)
Luckily, merging master into this PR should not have many conflicts. Cheers!
Also, we need to look at performance when we switch out yaml.load for yaml.safe_load. @m4dcoder just added CSafeLoader to orquesta, and ended up needing to pass CSafeLoader into yaml.load to get both the performance boost and the safety. See: https://github.com/StackStorm/orquesta/pull/230/files#diff-c2248ccb7408cc089d472f1dcb72a531c386cac3a9af7ad7de9bebc1d5910f3c (and the discussion on that PR as well).


inconsistency in rounding days with a large increment

I have this code snippet:
import { Temporal } from 'temporal-polyfill';

let d1 = Temporal.Duration.from({days: 65});
let dt1 = Temporal.PlainDateTime.from('2024-06-19 00:00:00');
let d2 = d1.round({
  relativeTo: dt1,
  largestUnit: 'year',
  smallestUnit: 'day',
  roundingIncrement: 35,
});
console.log(d2.toString());

Using this polyfill, the output is 2m. But with @js-temporal/polyfill, I'm getting 2m9d. I think the latter is correct. From what I can tell, the issue is here:
https://github.com/fullcalendar/temporal-polyfill/blob/2d3fd89f21eac311eceee9151640072911fb6467/packages/temporal-polyfill/src/internal/round.ts#L538-L544
Namely, this is rounding the duration based only on the time/day component. But it is neglecting the days contributed by units higher than days. Which in this case is 2 months since the duration, at this point, has been balanced.
(I am working on a datetime library for Rust inspired by Temporal, and I found this case by trying weird values of roundingIncrement.)

Hi @BurntSushi, thanks for using this package and for exploring this edge case. The temporal spec changed a little while ago, but the @js-temporal/polyfill package did NOT yet update to it. However, temporal-polyfill DID. So temporal-polyfill implements the newer spec for diffing/rounding. If you go to https://tc39.es/proposal-temporal/docs/ and open up the console to use the "playground" you'll see the answer is 'P2M'.
The rounding logic in the spec was refactored for a number of reasons (I actually helped out with it) but one of the outcomes is that roundingIncrement only operates "within" the parent unit. So, if the unrounded result is P2M4D, then the only the 4D is being rounded, within 0-35, and of course it rounds down to 0.
But I'm glad you brought this up because rounding UP could yield strange results. I've opened a TC39 ticket here: https://github.com/tc39/proposal-temporal/issues/2902

Oh nice! That's a relief. It is definitely an odd case and I wasn't fully sure what the right answer ought to be, but what y'all settled on seems sensible. And thanks for the tip on using the console on the doc web site.

The rounding logic in the spec was refactored for a number of reasons (I actually helped out with it)

Yeah I've been following this and really appreciated the gist you provided. It was quite timely too, because I was dreading implementing duration rounding before then. But your approach massively simplified it.

No problem at all.

Yeah I've been following this and really appreciated the gist you provided

That makes me very happy, I'm glad others got some good use out of that!


Port to GGEZ 0.5

GGEZ 0.5 release candidate is expected to be released soon, it's a good idea to try porting Zemeroth to it and report/fix the issues.

The master branch now uses a git fork of GGEZ 0.5.0-rc.0 (See https://github.com/ozkriff/zemeroth/pull/426)
Waiting for GGEZ's issues 569 and 570 to be closed now.

0.5.0-rc.1 was released

master now uses ggez 0.5.0-rc.1. Waiting for 0.5 release.

Closed by https://github.com/ozkriff/zemeroth/commit/127d3418f38a5963116679bcc22b7f12cc676e63#diff-80398c5faae3c069e4e6aa2ed11b28c0


chore: add Chengzhong Wu as maintainer

Propose Chengzhong Wu as maintainer of OpenTelemetry Javascript in recognition of his work on the project. Chengzhong has show good judgement in all areas of the project, and has been especially helpful in development the API and the metrics SDK.

Also, remove @legendecas(and me. Amir seems to already be missing anyway) from the approvers list?

Also, remove @legendecas(and me. Amir seems to already be missing anyway) from the approvers list?

I think daniel planned to do it in a different PR

No I did it in this one


python3Packages.python-bip32: init at 3.4

bip32 is a required dependency of ledger-bitcoin 0.2.2, which was updated from 0.2.1 as part of #251878. It's currently failing to build.
This fixes the currently failing build as well pkgs.electrum which depends on it.
There is unfortunately no tag of this release available on github yet, so the commit hash is used directly in the src.
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Is there any reason to not use fetchPypi? 3.4 is released on pypi.

Is there any reason to not use fetchPypi? 3.4 is released on pypi.

setuptools failed to work with the pypi distribution (it looks like setup.py or requires.txt need patching/renaming), so I figured it was easier to use the source tarball that just works as-is. I could hack around that and switch back to pypi as src though if that's preferred.

setuptools failed to work with the pypi distribution (it looks like setup.py or requires.txt need patching/renaming?),

That's fair. But it's better to comment this in the code.

Reviewed points

[x] package path fits guidelines
[ ] package name fits guidelines
[ ] package version fits guidelines
[x] package build on x86-64
[ ] executables tested on ARCHITECTURE
[x] meta.description is set and fits guidelines
[ ] meta.license fits upstream license
[ ] meta.platforms is set
[x] meta.maintainers is set
[x] build time only dependencies are declared in nativeBuildInputs
[ ] source is fetched using the appropriate function
[x] the list of phases is not overridden
[x] when a phase (like installPhase) is overridden it starts with runHook preInstall and ends with runHook postInstall.
[x] patches that are remotely available are fetched with fetchpatch

Possible improvements

Maybe adding the package python-bip32 and adding the missing dependencies to ledger-bitcoin could be two separate commits.
Is the license correct?  https://github.com/darosior/python-bip32/blob/1492d39312f1d9630363c292f6ab8beb8ceb16dd/LICENCE looks like bsd3 (or is this the same as MIT ?).

Comments
I tested the pull request at hand by building electrum with it (via ledger-bitcoin): It starts, and viewing transactions and accounts seems to work flawlessly (I didn't create any transactions though).  Due to this, I recommend this pull request to be merged to unbreak electrum on master.
(Note: This review is based on the branch ba10d73)

Is the license correct?

Good catch! It seems like the license is inaccurately listed in its metadata, but it is indeed bsd3.

Rebased past #264290 to attempt to resolve the eval error.

There is unfortunately no tag of this release available on github yet, so the commit hash is used directly in the src.

This is no longer necessary

@ofborg build python311Packages.bip32

Result of nixpkgs-review pr 263636 at edcac9fa run on x86_64-linux 1

12 packages built successfully:

electrum
electrum-grs
electrum-grs.dist
electrum.dist
python310Packages.bip32
python310Packages.bip32.dist
python310Packages.ledger-bitcoin
python310Packages.ledger-bitcoin.dist
python311Packages.bip32
python311Packages.bip32.dist
python311Packages.ledger-bitcoin
python311Packages.ledger-bitcoin.dist


keytool syntax is wrong

[Enter feedback here]
update the keytool syntax for java it doesn't work , try with this
keytool -import -alias emulator_cert -keystore  -file ~/emulatorcert.crt -storepass changeit -noprompt
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 4b8e447c-2814-df77-a9cb-d631e7f5c491
Version Independent ID: 44ed5bc8-1eb7-c981-96ad-7faa2645a61b
Content: Run the Azure Cosmos DB Emulator on Docker for Linux
Content Source: articles/cosmos-db/docker-emulator-linux.md
Service: cosmos-db
GitHub Login: @StefArroyo
Microsoft Alias: esarroyo

@christianpadovano
Thanks for your feedback! We will investigate and update as appropriate.

Hello, @christianpadovano,
We are updating the keytool sample with the one you provided based on my testing:
keytool -import -alias emulator_cert -keystore -file ~/emulatorcert.crt -storepass changeit -noprompt

The change should be live soon.

:tada:
We recently released a complete revamp of the emulator documentation to cover many of the content gaps, be more succinct, and enable you to use the emulator quickly.
The new emulator documentation shows how to use the containerized (Docker) or local (Windows) variants of the emulators across five different APIs (NoSQL, MongoDB, Apache Cassandra, Apache Gremlin, Table) and three programming languages (Python, .NET, JavaScript).
We have also retired the outdated legacy emulator documentation as many of the code samples and instructions were out of date relative to the latest SDKs/libraries for each API and programming language.
Here's a few helpful links to get you started with the new emulator docs:

Link

Emulator landing page
https://learn.microsoft.com/azure/cosmos-db/emulator

How-to use the emulator guide
https://learn.microsoft.com/azure/cosmos-db/how-to-develop-emulator

Emulator release notes (local Windows only)
https://learn.microsoft.com/azure/cosmos-db/emulator-release-notes

**Emulator command-line arguments (local Windows only)
https://learn.microsoft.com/azure/cosmos-db/emulator-windows-arguments

I hope this helps unblock you. If you need changes to the emulator docs, feel free to open a new GitHub issue.
Thank you for your patience!


Remove unused code in presto-main

REFACTORING
It removes apparently unused codes in presto-main.

Thanks!


Dynamically starting sagas

This might have some overlap with with the runSaga idea mentioned in #13 (comment).
Currently all sagas need to be provided during startup, I am curious if it make sense to have the ability to dynamically start them.
After writing the example below I think the main use case would be larger apps that use code splitting, if you know all your sagas ahead of time its probably simpler to have watchers which fork based on dispatched actions (compatible with time travel).

For example if we only want the onBoarding saga to be running while in a specific section of our app it could be started/stopped with a container component:
componentWillMount() {
  this.onBoardingTask = runSaga(onBoarding, this.props.store);
}

componentWillUnmount() {
  cancelSaga(this.onBoardingTask);
}

While I understand the code splitting requirement. I tend to not agree with starting sagas from inside containers elements. Perhaps, it'd be better to start the dynamic sagas in the same place we update the store. For example, if we load some dynamic module with new reducers and sagas I can imagine
function updateAppWithNewModule(module) {
  updateStoreWithNewReducer( module.reducer )
  runSaga(module.saga)
}

FYI, I've already pushed changes in the master branch which include runSaga support (along with monitoring support).

Yeah a component was probably a bad example (though I have been curious if proc could be used locally within a component to manage complex flows). I mainly wanted to show the cancelling of saga on unmount.
Starting the saga at module load time seems like the correct approach; I could see this working well with dynamic routes in react-router.

though I have been curious if proc could be used locally within a component to manage complex flows

technically yes. actually proc has a signature like (iterator, subscribe, dispatch) -> Promise. So you can hookup take and put to any external input/output (aka csp channels). But I wouldn't recommend using an internal function, as the signature may change in the future.
This is another item on my todo list. Initially, I imagined runSaga(iterator, {subscribe, dispatch}) which would work with Redux Stores out of the box. But the store doesn't actually provide the triggered action to its subscribers, and I read in a related Redux issue that this is intentional (https://github.com/rackt/redux/issues/1057).
Another solution I m considering is keeping the generic runSaga(iterator, {subscribe, dispatch}) and exposing the utility function storeChannel so we'll end up with something like
runSaga( iterator, storeChannel(store) )

With the benefit of being able to connect the Saga to any external channel

I do like the idea of keeping it generic, would remove the need for things like emitterFromStore or store enhancers mentioned in #13.
Is there a common interface that other libraries seem to be using for channel like functionality? closest thing I can think of is Rx.Subject.

Is there a common interface that other libraries seem to be using for channel like functionality? closest thing I can think of is Rx.Subject

Node duplex streams seems to mimics channel's take/put, but uses 2 independent channels reads/writes. It doesn't also use promises for communication

FYI. the new v0.4.0 supports runSaga

:+1:

看看这个： https://github.com/GuillaumeCisco/redux-sagas-injector


Assetto Corsa

I'm done adding the tyres, ive made it so tyrewear is -1 doing outlap, i think that will be good enaugh.
[edit]
Some tyres might need a little tweak. but thos ive tryed so seems to be working as expected.

Wow, this must have taken ages. Nice one fella :). I'll do a release for this tonight if I get time.
Raceroom have just announced a major rework of their shared memory so that'll keep me busy for a while :(


[misc] Undo functionality

Undo/redo (some sort of action history management) would be a great addition to this library. While it shouldn't be too big a job for us to write a custom implementation when we get around to wanting it, I think most people will expect it when trying out this grid.

tracked by AG-169
https://www.ag-grid.com/ag-grid-pipeline/

+1 fwiw :)

Any estimation date on when this might be available ? Thank you.

Could you please tell me if the undo feature is planned for the next or a future version of AG-Grid?
If present in your backlog, could you please tell me when it will be available and if not, could you provide some inputs on how to implement it?

Hi,
Thank you for raising this issue for us, at this moment we are reviewing how we process Feature Requests/questions that come through from GitHub.
As I am sure you are aware, we offer two products:
ag-Grid - this is entirely free to use in line with our MIT license
ag-Grid Enterprise - our commercial version which funds the development of both versions.
We currently have a very full pipeline of work which can be viewed here: https://www.ag-grid.com/ag-grid-pipeline/
This will be our priority for the coming months and as a result, we don’t have capacity to take feature requests/questions from GitHub, but you might find that yours has already been raised in our pipeline.
We will do a periodic review of GitHub issues for any bugs raised and these can also be tracked on our pipeline page.
Thanks for your understanding.
ag-Grid Team.

Has the Undo/Reset changes feature added to this library ??

It seems like undo has been removed, did a search for 'undoCellEditing' with no hits, also see that the docs page has been removed;

@makinggoodsoftware can you maybe confirm any of this? is there any other functionality that replaced this?


Bounds for SvgPath don't take transforms into account

Description
PR  #282 (Issue #281) introduced the logic for applying transforms to SvgPathBasedElements. Since SvgPath overrides the Bounds getter and simply returns this.Path(null).GetBounds() it bypasses possible transforms. Is this intended?
If it is not I would propose simply removing the getter for SvgPath and fall back to the SvgPathBasedElement 's one. I could create a PR accordingly...

Sorry for the long delay...
I don't think this was intended (I made that PR, but I don't actually remember it...), so please go ahead and make a PR if you are still willing!


Improvements to the ARM client factory

Share the *arm.Client across SDK clients instead of always creating a new one (and not throwing away the "test" one).

@tadelesh I'll wait for your ack before merging. Also will clean up CODEOWNERS.


Added a GetLastRequest() method for debugging.

The api referred to by the tests doesn't seem to exist.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8ce25c8). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage          ?   81.69%
=========================================
  Files             ?        3
  Lines             ?      153
  Branches          ?        0
=========================================
  Hits              ?      125
  Misses            ?       25
  Partials          ?        3

Impacted Files
Coverage Δ

soap.go
92% <100%> (ø)

encode.go
74.73% <100%> (ø)

Continue to review full report at Codecov.

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

@earncef can you add more test to the package?
Thank you!

I've added a few more tests.


The Examples- some links under Maths are not working in hindi

Actual Behaviour
some links like नक्शा  , पैरामीट्रिक समीकरण are not loading under Maths section in Example page
Expected Behaviour
they should open page with actual code example of topic we selected
Steps to reproduce it

Screenshots of the issue

The examples numbering in the translated examples folders are out of sync with the English version so many of them are not building and linking to the right examples.

Also duplicate of #1167, tagging @Divyansh013

so do i need to work on it or close it? @limzykenneth

The examples numbering in the translated examples folders are out of sync with the English version so many of them are not building and linking to the right examples.

Gotcha! Thanks for the input, will be ready with my PR soon

so do i need to work on it or close it? @limzykenneth

I will attach my PR with the original issue

Thanks @rinkydevi, I'll be letting @Divyansh013 work on this because of the existing open issue. Feel free to look at some of the other open issues we have. Closing in favour of #1167.


List of OS images includes version 6.0 which looks not documented

October 2018 list of patches here https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/cloud-services/cloud-services-guestos-msrc-releases.md includes version 6.0 which looks not documented anywhere and also not available for selection.

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

ID: 3a8cc2c5-eb5f-edaf-f155-98e5ff1b252c
Version Independent ID: 8e1a1933-e037-d682-5ba0-50d0f85f12e8
Content: List of updates applied to the Azure Guest OS
Content Source: articles/cloud-services/cloud-services-guestos-msrc-releases.md
Service: cloud-services
GitHub Login: @raiye
Microsoft Alias: raiye

Thanks for the feedback! We are currently investigating and will update you shortly.

@raiye Can you please share your insights on this customer's question. Thanks.

This pull request has been merged and is ready to publish at 3pm.
Remove fix for and reference to 6.0 family #57761

Thanks @RichardScheel and @v-piwijs
@Dmitry-Me Thanks for bringing this to our attention. The changes will be live shortly.

#please-close
the page has now been updated with #57761


Depth buffer precision issues

The way the depth buffer precision was divided up in OpenGL doesn't map well to Metal.
The problem shows up best when tilting and presumably with buildings.

#1753
#1847


Add Helidon as MP 2.2 implementation. Fixes #192

Just for our information, is there an ETA on when this PR might be merged? Thanks.

@tjquinno Merged. You may watch https://gitter.im/eclipse/microprofile-starter for messages from bot about when the build is ready on https://test-start.microprofile.io/
It will appear on https://start.microprofile.io/ when we release 0.9.4


[schema-registry-avro] deserialize to support streams

Adding support for both WHATWG's and NodeJS's readable streams in deserialize.
Tests are added in another branch for now. I opened https://github.com/Azure/azure-sdk-for-js/pull/17463 to clean things up first.

/cc @jeremymeng @ramya-rao-a - should we look into doing something similar for Form Recognizer and Storage?

For Form Recognizer this would be nice to add browser stream support. @willmtemple
For Storage, it would be upload (uploadStream) only unless core response adds support to browser stream. @EmmaZhu

@jeremymeng thanks! I was talking to @xirzec about doing browser streams support in core responses as well but he suggested to do so after migrating off XmlHttpRequest first. Will no longer uses this github account for work, /cc @witemple-msft

Adding support for both WHATWG's and NodeJS's readable streams in deserialize.

Is there an issue or prior discussion that lead us to add this feature?

@ramya-rao-a https://github.com/Azure/azure-sdk-for-js/issues/10950 and there was a prior discussion with the crew

Do we also plan to add support to serialize TO a stream?

@nguerrera Good question. I made serialize return a Uint8Array in https://github.com/Azure/azure-sdk-for-js/pull/17549 which is a standard ECMAScript type. I am holding off on adding more serialize methods with other return types for now until we learn more about concrete customer scenarios. If we decide to add one, we can follow the pattern storage follows, e.g. async serializeToStream(value: unknown, schema: string): Promise<ReadableStream>.


reload kamelets on file editor route #1134

fix for #1134
Kamelets were loaded only in the application load time. hence, the application does not render custom kamelets while running until we refresh or reload the web app in the browser.
Fixed by adding ProjectService.reloadKamelets() in the FileEditor useEffects.

In this case it will download 2MB file of Kamelets every time user open any file.
I would prefer to have a different solution:

If I created/updated Kamelet that it should be added/updated in the Kamelets in KameletsApi.txt
User should be able to reload Kamelets manually
User should filter Custom only Kamelets

Noted @mgubaidullin, update you with a better solution.


Remove trailing slash for backend defined in query

If you define a backend in query instead of datasource, the trailing slash isn't removed before building the url. This MR fix the issue.

Merci @vaxvms !


Fixed a bug where some components are disabled by default

Surprising that it took so long to discover this bug.
GearVRf-DCO-1.0-Signed-off-by: Rahul Rudradevan
<EMAIL_ADDRESS>

How did you find out?

Incorrect IPickEvents were being generated for colliders that were disabled. The sample app that I wrote for daydream enables and disables colliders inside IPickEvents.
Just to be sure I ran eye picker and the picking tests against this pull request and they ran fine.


Error while uploading file

Internal Server Error: /upload/
Traceback (most recent call last):
File "C:\Users\Admin\AppData\Local\Programs\Python\Python38-32\lib\site-packages\django\core\handlers\exception.py", line 34, in inner
response = get_response(request)
File "C:\Users\Admin\AppData\Local\Programs\Python\Python38-32\lib\site-packages\django\core\handlers\base.py", line 115, in _get_response
response = self.process_exception_by_middleware(e, request)
File "C:\Users\Admin\AppData\Local\Programs\Python\Python38-32\lib\site-packages\django\core\handlers\base.py", line 113, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "C:\Users\Admin\AppData\Local\Programs\Python\Python38-32\lib\site-packages\django\contrib\auth\decorators.py", line 21, in _wrapped_view
return view_func(request, *args, **kwargs)
File "C:\Users\Admin\AppData\Local\Programs\Python\Python38-32\lib\site-packages\django\views\generic\base.py", line 71, in view
return self.dispatch(request, *args, **kwargs)
File "C:\Users\Admin\AppData\Local\Programs\Python\Python38-32\lib\site-packages\django\views\generic\base.py", line 97, in dispatch
return handler(request, *args, **kwargs)
File "C:\Users\Admin\papermerge-proj\papermerge\core\views\documents.py", line 282, in post
page_count = get_pagecount(f.temporary_file_path())
File "C:\Users\Admin\AppData\Local\Programs\Python\Python38-32\lib\site-packages\mglib\pdfinfo.py", line 83, in get_pagecount
compl = subprocess.run(
File "C:\Users\Admin\AppData\Local\Programs\Python\Python38-32\lib\subprocess.py", line 489, in run
with Popen(*popenargs, **kwargs) as process:
File "C:\Users\Admin\AppData\Local\Programs\Python\Python38-32\lib\subprocess.py", line 854, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\Admin\AppData\Local\Programs\Python\Python38-32\lib\subprocess.py", line 1307, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
[21/Jul/2020 17:46:30] "POST /upload/ HTTP/1.1" 500 128740

I think you did not install poppler utils.
Can you double check that please ?
If you type in command line:
$ pdfinfo -v

You should see something like:
pdfinfo version 0.62.0
Copyright 2005-2017 The Poppler Developers - http://poppler.freedesktop.org
Copyright 1996-2011 Glyph & Cog, LLC

@ciur i have install package still same error.

ah, man, wait a second. You are using Windows machine, right?
I never tested on Windows!
Here in requiremens I mentioned that you need a Unix-flavoured machine (some linux distro or mac os).
Sorry, man, it is not designed to work on Windows :)
Maybe you can try via Docker image ? I never tried to run docker+windows but in theory should work.


400 error?

Hi - done some work adapting this project for Azure blob storage (still in dev). Works great with included JS client but I am now trying with the Android Client and get a 400 error. I have the android client working with the official test instance at https://master.tus.io/files - so that's known working too. Any idea what's going wrong? Using the Owin netcore app btw.
Thanks for your work on this project!

OK done a bit more investigating, looks like it fails on metadata checks:
`
if (!ctx.Metadata.ContainsKey("name"))
{
ctx.FailRequest("name metadata must be specified. ");
}
                        if (!ctx.Metadata.ContainsKey("contentType"))
                        {
                            ctx.FailRequest("contentType metadata must be specified. ");
                        }

The android client sends a key as _filename_ not _name_, and also does not send acontentType` key at all. If I make these changes all works as expected. I'm not a tus expert - don't know if those things are part of the standard?

Hi @drphilgarner
The protocol does not specify any metadata what so ever. This is entirely up to the server and client to decide on.
The code you have provided above is for the OnBeforeCreateAsync event. This event can be used by the server to validate a file before creating it so that all required metadata is present. The code in the test site just sets up some metadata as an example. There is no requirement to have these properties or any properties for that matter.
You could just remove the OnBeforeCreateAsync event handler, change the code to validate filename instead or add name as a property in the Android client. All of these are valid according to the protocol.

Ok great, thanks for the clarification.

No worries, feel free to open new issues if you have any more questions :)

Btw if you decide to make your blob storage store public please let me know and I'll add a link to your github.

Well it's in a workable state now @smatsson https://github.com/drphilgarner/tusdotnet very basic implementation using Azure blob stores, tested on the Owin site.

Cool! Thanks for sharing. I started working on a store using append blobs but found append blobs to be really, really slow. Haven't done any work on it since August (and it's not made public). What's your experience with the performance of append blobs?
If you decide to extract the actual store into its own project/nuget, please let me know and I'll gladly add a link to the readme or wiki.

Not really tested it well enough yet. You could be right on the speed. I
was wondering about abstracting all the small files tus uses to maintain
state to a database and just using the blob to store the actual files. What
do you think?
On 14 March 2018 at 09:00, Stefan Matsson<EMAIL_ADDRESS>wrote:

Cool! Thanks for sharing. I started working on a store using append blobs
but found append blobs to be really, really slow. Haven't done any work on
it since August (and it's not made public). What's your experience with the
performance of append blobs?
If you decide to extract the actual store into its own project/nuget,
please let me know and I'll gladly add a link to the readme or wiki.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/tusdotnet/tusdotnet/issues/43#issuecomment-372949129,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6983Wtt-w74MYG_4xdAc3mQpCHw6uOks5teNwygaJpZM4SbSfN
.

In the version I made I used the blob's metadata to store all the small files. It worked fairly well as that part felt much faster than actually writing data to the blob. I would probably not want to use different tech to store actual files and the rest of the data (e.g using SQL for metadata and blob storage for files).

Found the code on my computer and uploaded it here: https://github.com/smatsson/TusAzureStore
Feel free to use any bits and pieces that you find useful.

Great, thanks Stefan, will take a look.
On 16 March 2018 at 08:47, Stefan Matsson<EMAIL_ADDRESS>wrote:

Found the code on my computer and uploaded it here:
https://github.com/smatsson/TusAzureStore
Feel free to use any bits and pieces that you find useful.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/tusdotnet/tusdotnet/issues/43#issuecomment-373643853,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6980GiNYUn-Yz7wogxRFzhMPw2NFJ2ks5te3w1gaJpZM4SbSfN
.


Replace deprecated error with BadZipFile

zipfile's error have been deprecated since Python 3.2, use BadZipFile instead, added in 3.2.

https://docs.python.org/3/library/zipfile.html#zipfile.BadZipfile
https://github.com/python/cpython/blob/6829b1256a596301f82e3573214230186a4babfd/Lib/zipfile.py#L53
https://github.com/python/cpython/issues/86437

Looks good! Thank you for providing those links alongside this PR, and thank you for finding this issue.


[Bug]:  GeneratedPluginRegistrant.java:64: error: cannot find symbol

Platform
android 13
Plugin
9.0
Version
9.0
Flutter SDK
3.22
Steps to reproduce
Launching lib/main.dart on Pixel 4 XL in debug mode...
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
/Users/4edoc/Documents/beboro/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java:64: error: cannot find symbol
flutterEngine.getPlugins().add(new dev.fluttercommunity.plus.share.SharePlusPlugin());
^
symbol:   class SharePlusPlugin
location: package dev.fluttercommunity.plus.share
1 error
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:

Run with --info option to get more log output.
Run with --scan to get full insights.

Code Sample
No response
Logs
GeneratedPluginRegistrant.java:64: error: cannot find symbol

Flutter Doctor
not applicable

Checklist before submitting a bug

[X] I searched issues in this repository and couldn't find such bug/problem
[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I'm using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[X] I did a flutter clean
[X] I tried running the example project

No, the plugin was working just fine before FLutter 3.22 upgrade, kindly do some checking.

Again, GeneratedPluginRegistrant.java is a file from your project, not a plugin file.
I checked the project compilation with our CI and locally, and it works as expected.
Please do some research, likely a flutter clean would be enough to fix the issue.

Sure let me check, Also, I am using latest Gradle version 8.x and latest kotlin version 1.9, can you test with that as well.

Any ideas?


fix(deps): upgrade react-native-reanimated to 3.0.0-rc.3

Description
This PR aims to resolve an identified vulnerability by upgrading react-native-reanimated to latest pre-release (3.0.0-rc.3). (Latest release 2.10.0 is still affected by the vulnerability.)

The package react-native-reanimated before 3.0.0-rc.1 is vulnerable to Regular Expression Denial of Service (ReDoS) due to improper usage of regular expression in the parser of Colors.js.

Other changes
Describe any minor or "drive-by" changes here.
Tested
Local unit tests pass.
How others should test
N/A
Related issues
N/A
Backwards compatibility
Compatible, because no Valora application logic has been changed.

Closed in favor of ignoring the vulnerability.


Are vulnerability scan results for Official Images still shown on Docker Hub?

File: docker-hub/official_images.md
I do not see any vulnerability scan results from any of the Official Images I looked at after signing in with my Docker account.

Wondering the same.  I see in docker-hub/release-notes.md that missing scan results is a known-issue, but it's been listed as such for almost 6 months now.  Any plan to fix?

@pkennedyr @ddebroy ptal

Any progress on this issue?  Should the scan results be available for all official images ?  Not seeing any result on the amazon linux official images.


How to unifiedly detect sprites in the observation overall substrates?

Hi, I am planning to generate a text-based description for RGB-based observation. To do this, I need to know the type of all sprites. For example, given a [88, 88, 3] observation, which contains 11x11=121 sprites, I wanna know what type it is for each sprite, i.e. classify it as "agent", "wall", "water", "apple", "sand", etc.  Can you give me some advice for achieving my goal?  Thanks a lot!

Yeah, don't use the LAYERS observation, we have not documented its dynamics (and they could be extremely confusing).\
As Edgar said, the best way to do this is by adding custom observations.  You'll have to read through the tutorial docs on substrate creation to see how to do this. If you still have questions after that then let us know, we would be happy to help.

Hi @jzleibo @duenez , recently I tried to read the source code for the Melting Pot. I am curious about the spacial relation of prefabs, i.e. the definition of "upperPhysical", "overlay" and "supperOverlay" and their mechanism for aggregating RGBA pixels. I wanna calculate the combined pixel results for the given two prefabs. For example, in Clean Up substrate, I can directly calculate "AVATAR_W + SAND" since the RGB color of AVATAR_W will entirely overwrite the background prefab's color so that one can get the sprite if one knows their ASCII map and corresponding color Platte. However, I cannot calculate the correct result for "SAND + SHADOW_N + SHADOW_E" since some prefabs' layer combination rule is "upperPysical" which seems like I need to know the fusion mechanism with some RGBA pixels. In addition, I don't find the relative code about this. Can you tell me how to obtain the combined image given two or more prefabs' ASCII maps with color platte( which is defined in shape.py and xxx_substrate.py) and layer relation?

The question of how precisely to fuse the RGBA values for sprites on different layers at the same x,y position is really a question about the underlying engine: dmlab2d. Maybe try asking it there https://github.com/google-deepmind/lab2d


Simple Update

can we update this project for default message ?
simple : 'https://api.whatsapp.com/send?phone=attendants.number&text=attendants.message',
idk which platform can support message but i need this update for whatsapp ^_^

I also need this


Upgrade grpcio and remove future compat

What problem does this PR solve?
Issue Number: #8095
Problem Summary:
This is the last of the steps to upgrade future. It will update grpc-rs to 0.6 and remove compat code added before.
What is changed and how it works?
What's Changed:

cargo update: kvproto futures grpcio protobuf-build grpcio-compiler
remove futures 0.1 and compat code, then make build pass.

Release note

Upgrade grpcio and remove future compat

For now,

kvproto uses my branch temporarily, when this PR is ready to merge, I will change the patch path
The work to update raft_client/fresh.rs is a lot. In order to decouple, the file is temporarily deleted. After other parts is ready, I'll commit to update that file.

/rebuild

/rebuid

/run-integration-common-test

/run-test

/run-all-tests


Script to list TODOs

@tisnik Your image is available in the registry: docker pull registry.devshift.net/MISSING_IMAGE_NAME:SNAPSHOT-PR-9


fix(metrics): updates unit option behavior to be spec-compliant

Fixes #2910
Short description of the changes
Changes the behavior of the unit option for an instrument descriptor to be compliant with the specification. See additional discussion on issue.
How Has This Been Tested?
Unit tests were added to confirm behavior.
Checklist:

[x] Followed the style guidelines of this project
[x] Unit tests have been added
[ ] Documentation has been updated

There is a downstream behavior here that will need resolved before merging. The MetricOptions interface expects any string, including a default of '', but the additional tests expect an integer value. I could use some guidance as what the behavior/update should be. I see a few paths.

Instruments accept a non-integer value
Instruments default to 1 for a blank string
Instruments throw an error if a blank string is passed.

  1) Instruments
       Counter
         should add valid INT values:

      AssertionError [ERR_ASSERTION]: unit not equals: <no-message>
      + expected - actual

      +1

      at assertPartialDeepStrictEqual (test/util.ts:134:12)
      at assertMetricData (test/util.ts:79:5)
      at validateExport (test/Instruments.test.ts:560:19)
      at Context.<anonymous> (test/Instruments.test.ts:63:7)

  2) Instruments
       UpDownCounter
         should add INT values:

      AssertionError [ERR_ASSERTION]: unit not equals: <no-message>
      + expected - actual

      +1

      at assertPartialDeepStrictEqual (test/util.ts:134:12)
      at assertMetricData (test/util.ts:79:5)
      at validateExport (test/Instruments.test.ts:560:19)
      at Context.<anonymous> (test/Instruments.test.ts:179:7)

  3) Instruments
       Histogram
         should record INT values:

      AssertionError [ERR_ASSERTION]: unit not equals: <no-message>
      + expected - actual

      +1

      at assertPartialDeepStrictEqual (test/util.ts:134:12)
      at assertMetricData (test/util.ts:79:5)
      at validateExport (test/Instruments.test.ts:560:19)
      at Context.<anonymous> (test/Instruments.test.ts:264:7)

Can you mark this as a draft until it is complete and has passing tests?

I don't think there's an option to switch a PR back to draft without closing and reopening a new one.
I've pushed an update that changes the expectation for unit values. (Tests should pass, but waiting for CI to run).

You might still have to replace the expected unit: '1' with unit: '' in these files of the exporter tests:

experimental/packages/opentelemetry-exporter-metrics-otlp-grpc/test/metricsHelper.ts
experimental/packages/opentelemetry-exporter-metrics-otlp-http/test/metricsHelper.ts
experimental/packages/opentelemetry-exporter-metrics-otlp-proto/test/metricsHelper.ts

Then this PR should be ready to go :slightly_smiling_face:
Thanks for taking the time to work on this! :slightly_smiling_face:

Please add a changelog entry in experimental/CHANGELOG.md


SD card initialization is wrong

Trying to initialize a Samsung Evo Plus SD card (MB-MC32GA/EU) it failed. Other SD cards worked just fine.
Looking at a LA the problem seems to be the selection of the SPI mode:
After insertion, 74 clock pulses needs to be applied to SCLK, with holding CS and DI high (http://elm-chan.org/docs/mmc/mmc_e.html#spiinit).
According to what I see on the LA, this is not the case since CS is low:

The error should be reprod. when using the fat_fs sample on a nRF52-DK

IMO the error happens, because the initialization is done in disk_access_spi_sdhc.c in the function static int sdhc_spi_go_idle(struct sdhc_spi_data *data):
sdhc_spi_tx(data, sdhc_ones, 10);
spi_release(data->spi, &data->cfg);
return sdhc_spi_cmd_r1_idle(data, SDHC_GO_IDLE_STATE, 0);

It writes 10bytes of ones using SPI onto the line, which is equivalent to MOSI being High and the clock toggling 80 times. However this also implies that CS is low.

@trembel thanks for the analysis. Have you tested your proposed solution? If so, and if it works, could you propose a PR, even if it's a Draft or RFC?

I've for now switched to the nRF5 SDK, since I had not enough time to fix this. One possibility would be to use an "invalid" pin as CS for the first toggles, however I could not find out if something like this exists in Zephyr.

Looking at a LA the problem seems to be the selection of the SPI mode:
After insertion, 74 clock pulses needs to be applied to SCLK, with holding CS and DI high (http://elm-chan.org/docs/mmc/mmc_e.html#spiinit).
According to what I see on the LA, this is not the case since CS is low:

From Physical Layer Simplified Specification, 6.4.1 Power Up Sequence for SD Bus Interface:
"A device shall be ready to accept the first command within 1ms from detecting VDD min.
Device may use up to 74 clocks for preparation before receiving the first command."

Switching to SPI Mode is done by CMD0 reception over SPI, 7.2.1 Mode Selection and Initialization:
"The SD Card is powered up in the SD mode. It will enter SPI mode if the CS signal is asserted (negative)
during the reception of the reset command (CMD0)."

@trembel @richardbarlow as per @jfischer-no's analysis, for now we will close this issue since work done since this issue was posted can potentially fix the problem. If this is not the case we can reopen it.


updated reveal (1.6.3)

Thank you for the contribution. It was merged directly as ab880de7b5765ef73789e8db2ab39cd6bcb2f9a3 to keep commit history cleaner. Your contribution is still credited to you.


Foreign field operations

companion to https://github.com/o1-labs/snarkyjs/pull/985

no longer needed


Fix String#rindex with invalid UTF-8 string

Previously String#rindex returned the wrong index when given an invalid UTF-8 string.

This patch was incomplete. Do not merge.
% ./build/host-utf8/bin/mruby -e 'p "★".rindex("\x98")'
1  # <= NG! Should be nil

Solved the problem mentioned above (https://github.com/mruby/mruby/pull/4625#issuecomment-520153135).
% ./build/host-utf8/bin/mruby -e 'p "★".rindex("\x98")'
nil

The new behavior is different from CRuby's. What's your opinion?

Ah, I does not confirmed the behavior of CRuby.
% ${RUBY} -e 'str = "\xf0☀\xf1☁\xf2☂\xf3☃\xf0☀\xf1☁\xf2☂\xf3☃"; p str.rindex("☁")'
ruby26                11
./mruby-head          nil
./mruby-patched       11

% ${RUBY} -e 'str = "\xf0☀\xf1☁\xf2☂\xf3☃\xf0☀\xf1☁\xf2☂\xf3☃"; p str.rindex("\xf1")'
ruby26                nil
./mruby-head          5
./mruby-patched       10

% ruby26 -e 'p "☁".unpack1("H*")'
"e29881"
% ${RUBY} -e 'str = "\xf0☀\xf1☁\xf2☂\xf3☃\xf0☀\xf1☁\xf2☂\xf3☃"; p str.rindex("\x98")'
ruby26                nil
./mruby-head          nil
./mruby-patched       nil

However, the current behavior is not all the same as CRuby.
Delete all the added tests except str.rindex("☁").
As for str.rindex (" \ xf1 "), it is a side effect result. Should it be nil as well?
Is there anything else I have missed?

I removed the behavior test that doesn't match CRuby.


Area2D body_entered signal is emitted too late

Tested versions
Reproducible in: v4.2.1.stable.official [b09f793f5]
System information
Windows 10 - v4.2.1.stable.official [b09f793f5]
Issue description
Area2D body_entered signal seem to execute the callback 1 physics tick too late. Here is a visual representation, where the player is a CharacterBody2D, and the coin is an Area2D. The Area2D callback is set to increase the score by 1 and make the coin invisible and queue_free()

This visual overlap is undesired, the Area2D (coin) is set to become invisible (visible = false) in the body_entered callback, however it is still visible for the first frame where it overlaps with the player.
This also happens in the official pong demo, where the ball can be seen overlap the paddles if the speed of the ball increases.
If maybe this is not considered a bug and it's just the way the engine was designed, there should be an easy alternative to make an Area2D with immediate body_entered callbacks. There's a running thread on the forums on this issue: https://forum.godotengine.org/t/why-are-area2d-collisions-triggered-1-frame-late/37354
Steps to reproduce
Create a CharacterBody2D and another Area2D. Make the Area2D emit the body_entered signal, and on the callback set it so the Area2D becomes invisible or whatever. You'll see that the CharacterBody2D actually overlaps the Area2D for 1 frame.
Minimal reproduction project (MRP)
MRCollisionExample.zip
In this MRP just press right arrow key to move the CharacterBody2D to the right. When it reaches the Area2D, the callback is set to teleport the CharacterBody2D back to the start, however, they can be seen overlapping for a frame, like this:

This also happens in the Godot pong official demo: https://godotengine.org/asset-library/asset/121
If you increase the ball speed, it will be seen overlaping the paddles, which is a highly undesired visual glitch.

I think overlapping one frame is acceptable, but it may overlap two frames.
In the _on_body_entered function of area.gd, print the non-reset position of the body:

In most cases it is (133.3333, 0);
In rare cases, it is (120, 0).
Note: In order to test faster, I set the initial position of the body to (0,0), and left nothing else modified.

(106.6667, 0)
(120, 0)
(133.3333)

I noticed that if you raise "physics/common/physics_ticks_per_second" or set "application/run/max_fps" to a low value so there are multiple consecutive _physics_process calls with no _process call in between, the overlap is not visible. The visual overlap only happens if there are _process calls between the _physics_process calls. I guess that's because the engine drawing happens somewhere during _process calls, as it's tied to FPS.

Adjusting the fps will make it look like there is no overlap.
But it will still overlap two physics frames (you will get two different positions where x exceeds 111, one can be output in _physics_process() of player.gd, and the other can be output in _on_body_entered() of area.gd) .
Update position (first overlap) --> _physics_process() --> Update position (second overlap) --> _on_body_entered().
Ideally it might be:
Update position (first overlap) --> _physics_process() --> _on_body_entered().

The reason for the two-frame overlap seems to be that move_and_slide() immediately updates the CharacterBody2D's transform, but does not immediately update the corresponding GodotBody2D's transform in the physics server.
GodotBody2D in PhysicsServer2D::BODY_MODE_KINEMATIC mode can only update its transform through integrate_velocities(), but not through set_state().
The following is an approximate process.
...
PhysicsServer2D::flush_queries()
    ...
        GodotSpace2D::call_queries()                                        // Query from `monitor_query_list`.
            GodotArea2D::call_queries()
                Area2D::_body_inout()
                    signal body_entered/body_exited                         // May emit.
...
OS::get_singleton()->get_main_loop()->physics_process()
    SceneTree::physics_process()
        ...
        SceneTree::flush_transform_notifications()
        ...
        SceneTree::_process
            Node::_notification(NOTIFICATION_PHYSICS_PROCESS)
                _physics_process()                                          // Script method.
                    CharacterBody2D::move_and_slide()                       // Update `CharacterBody2D`'s transform.
                        Node2D::set_global_transform()
                            Node2D::set_transform()                         // Add the `CharacterBody2D` to `xform_change_list`.
        ...
        SceneTree::flush_transform_notifications()                          // Flush transform notifications from `xform_change_list`.
            CollisionObject3D::_notification(NOTIFICATION_TRANSFORM_CHANGED)
                GodotPhysicsServer2D::body_set_state()
                    GodotBody2D::set_state()                                // May update `GodotBody2D`'s transform.
                        // Fails due to its mode (`PhysicsServer2D::BODY_MODE_KINEMATIC`).
                        // GodotCollisionObject2D::_set_transform()
        ...
...
PhysicsServer2D::step()
    ...
        GodotStep2D::step()
            GodotStep2D::_pre_solve_island()
                GodotAreaPair2D::pre_solve()
                    GodotArea2D::add_body_to_query()                        // Add the area to `monitor_query_list`.
            GodotBody2D::integrate_velocities()                             // Update `GodotBody2D`'s transform.
                // Success. But it may be too late to add the area to `monitor_query_list` in time.
                GodotCollisionObject2D::_set_transform()

Although GodotBody2D's transform is also updated in the same frame, it is updated too late, resulting in missing the opportunity to add area to monitor_query_list in the same frame. This ultimately results in emit body_entered/body_exited signals possibly being 2 frames late.

@Rindbee Got any news on this?
Just for the record, recently tried to replicate this on Unity with Unity's Area2D body_entered equivalent, OnTriggerEnter2D (which calls Destroy() to remove the Coin). On Unity it works as expected, without overlapping frames, with any framerate and timestep settings. As soon as the Player touches the Coin, OnTriggerEnter2D event is called immediately. You will never see the Player overlapping the Coin.
But it seems impossible to replicate that behaviour in Godot. In Godot, the _body_entered signal may be called up to 2 visible frames late (depending on if you used move_and_slide(), 2 frames late, or updated position manually, 1 frame late), causing visible overlaps. I wish it worked the same way as in Unity. It seems there's no simple solution to this problem in Godot, at least not without relying on a custom coded solution or RayCasts that would add unnecesary performance overhead.
Sadly nobody seems to care about this.  But then we have threads like these, all originated by the same issue:
https://github.com/godotengine/godot/issues/53099
https://www.reddit.com/r/godot/comments/vqgq1j/area2d_body_entered_delayed/
https://forum.godotengine.org/t/collision-between-two-areas-2d-happens-too-late/2158
I only wish that someday this issue will be addressed and we can have events that fire on the same visible frame

I am facing similar issues in my project too, and sadly in my case the problem is not limited to a single frame.
I too am unable to access the correct position of a RigidBody2D right after entering an Area2D. I want to use this position (and a stored previous position) to draw a line showing where the body has crossed the boundary of the area. Since the signal is fired late, both the current and the previous positions are already inside the Area2D, causing the line to be drawn in the wrong location. The line remains visible for way more than one frame, and it is clearly noticeable that it does not cross the boundary.
At the moment, the only clean solution I found is to avoid using signals altogether and test for collisions manually in _physics_process, which does not seem ideal.


Added cololab instructions

Description
Because people need to know hot to add to this code
Status

[x] Ready to go

So quick question: WHO ARE YOU!?


Which pins used for SPI on Galileo Gen1?

Which pins are (CLOCK, MOSI, MISO, CS) when
x = m.Spi(0)

or
x = m.SPI(1)

runs?

In file intel_galilieo_rev_d.c:
mraa_intel_galileo_rev_d()

...

    b->spi_bus_count = 1;
    b->def_spi_bus = 0;
    b->spi_bus[0].bus_id = 1;
    b->spi_bus[0].slave_s = 0;
    b->spi_bus[0].cs = 10;
    b->spi_bus[0].mosi = 11;
    b->spi_bus[0].miso = 12;
    b->spi_bus[0].sclk = 13;

```

So yes, that's it, use the pins you've found. There's only one spi bus and one chip select.


Incompatible with dotenv

I've noticed a funny issue, which is that the way env vars are used to set constants is incompatible with using dotenv for setting environmental paths.
My hunch is that this has something to do with the way bundler follows requires.
I think the fastest fix would be to eliminate these lines:
      ORG           = ENV['OKTA_ORG']    || 'your-org'
      DOMAIN        = ENV['OKTA_DOMAIN'] || 'okta'
      BASE_URL      = "https://#{ORG}.#{DOMAIN}.com"
      DEFAULT_SCOPE = %[openid profile email].freeze

And instead reference ENV wherever the constants were called.
Thoughts?

It is incompatible with config files too, there is a PR out: https://github.com/dandrews/omniauth-okta/pull/1. It does not seem like there is any movement on this gem, so maybe add it to your boot.rb file if you are using rails:
# config/boot.rb

ENV['OKTA_ORG'] ||= 'exampleorg'

hey guys, any progress on that one?

I merged in #1 but if anyone wants to submit a pull request here it'd be greatly appreciated.

@dandrews works perfect, thank you!!


[Traefik Plugin Catalog] Plugin Analyzer has detected a problem.

The plugin was not imported into Traefik Plugin Catalog.
Cause:
failed to run the plugin with Yaegi: the load of the plugin takes too much time(10s), or an error, inside the plugin, occurs during the load: 1:21: import "github.com/morzan1001/forward_auth_grpc_plugin" error: /tmp/traefik-plugin-gop3774387656/src/github.com/morzan1001/forward_auth_grpc_plugin/forward_auth_grpc.go:10:2: import "github.com/morzan1001/forward_auth_grpc_plugin/proto" error: /tmp/traefik-plugin-gop3774387656/src/github.com/morzan1001/forward_auth_grpc_plugin/proto/auth.pb.go:10:2: import "google.golang.org/protobuf/reflect/protoreflect" error: /tmp/traefik-plugin-gop3774387656/src/github.com/morzan1001/forward_auth_grpc_plugin/vendor/google.golang.org/protobuf/reflect/protoreflect/value_unsafe_go120.go:10:2: import "unsafe" error: unable to find source related to: "unsafe"

Traefik Plugin Analyzer will restart when you will close this issue.
If you believe there is a problem with the Analyzer or this issue is the result of a false positive, please fill an issue on piceus repository.

https://github.com/traefik/traefik/issues/7459 😞


config eventsource handler image & trigger handler image(#353)

 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.shenyong seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@wrongerror would you help to review this?

@shyupc Are you in our wechat group? You can scan below barcode to get in if you're not in

Also it'll be great if you can let us know how you use OpenFunction in more details


⚠ AGEG website (redirect) has degraded performance

In 177fb27, AGEG website (redirect) (https://ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 2500 ms

Resolved: AGEG website (redirect) performance has improved in ee3007b.


Adds back SSR

Still have to step through all the new SSR steps but my first impressions are:

ScopeDepth can go, with Ancestry we should have enough information to skip destruction. Maybe move the destruction skip into the implementation of DOMInterpret
I have a hunch that we can still reduce the surface area of DOMInterpret

Still have to step through all the new SSR steps but my first impressions are:

ScopeDepth can go, with Ancestry we should have enough information to skip destruction. Maybe move the destruction skip into the implementation of DOMInterpret
I have a hunch that we can still reduce the surface area of DOMInterpret

Cool, I'll try my best to sub in Ancestry for ScopeDepth. As for moving the destruction skip, it's a bit above my pay grade currently as I don't quite understand that part of the code yet, but I can study it!
Re DOMInterpret, absolutely, I think we can squeeze it down more. Basically, anything that's not directly touching the DOM , that's not different between the DOMInterpret, and that's not strictly necessary for SSR/hydration can go.
Another thing the PR needs is an algo to slim down the size of the generated HTML. It's currently bloated with too many deku-related attributes, and it's possible to traverse the DOM & eliminate all of the atts that won't be used during hydration. That'll also make hydration much faster, as we'll be able to use the isBoring field to skip hydrating some chunks entirely.

Now that you mention them, could you add an explanation of isBoring and isLucky? I'm assuming that "isBoring"~ pure and "isLucky" ~ unnested dyn element?

Now that you mention them, could you add an explanation of isBoring and isLucky? I'm assuming that "isBoring"~ pure and "isLucky" ~ unnested dyn element?

So isLucky I'm not sure (I couldn't find it in this PR), but isBoring = pure, meaning that we can skip hydration. All the info to determine that is baked into the DOM & the cache, so it can be done after the html is extracted and fed to hydration. In the tests I don't do that yet, but I'll write an algo that does. Also, anything that's boring or a descendent thereof will have its data-deku-ssr attributes and text markers removed.
Lastly, SSR needs jsdom to work, but if you're running it from the deku repo this gets installed when you do pnpm i.

I'm going over ScopeDepth and, just to make sure I understand, could you point me to where it's reset to 0? I see where 1 is added, and I also see where it's 0'd out at the toplevel, but I'm not sure where it's set to 0 again. I see a ScopeDepth 0 in remove for useDynWith, but I'm not sure if/how that turns into a lifecycle. Could you give me a bit more info? Thanks!

Nvm, I understand now. The ScopeDepth for lifecycle is monotonically increasing, which means it'll be 0 up until we hit our first element. By mergeing it with ScopeDepth 0 in dyns, we guarantee that remove fires if a dyn fires.
I can definitely recreate this logic using ancestry. dispose can likely be Effect Unit and lifecycle can likely be Poll Unit as I'll be able to embed ancestry in the dispose effect 👍

@jterbraak ScopeDepth is now removed and Ancestry is used.

The optimizer is now added.
The best way to see the result is the tests. Now, every test in index.test.js runs in its SSR+hydration and "normal" variants. Furthermore, there's a new test suite in Main.purs that makes assertions about the SSR output. You can see that the DOM is quite lean in terms of extra identifiers, and the isBoring cache assertions show how hydration is aggressively optimized.

https://github.com/mikesol/vite-deku-minimal/ 🚀

Added a client routing example as well: https://github.com/mikesol/vike-deku-client-routing.

Migrated the docs to ssr to test it out (will migrate back if this isn't merged). They deploy fine on vercel. https://deku-documentation.vercel.app . The generated html via view-source is pretty complete, it picks up on almost 100% of the pages & healthy chunks are ignorable, so the rendering is faster than the previous docs 🚀

Merging so this doesn't go stale as I won't have time in the next few days. Thoroughly tested & deku docs are deployed with it 🚀


complex: Fix hash function to work correctly

Currently, hash(3.1-4.2j) or hash(3.1+4.2j) is crashed due to
overflow error on RustPython.
This patch will fix this issue.

@silmeth I've updated the PR. PTAL


actions/checkout v2 is not supporting submodule anymore.

actions/checkout v2 is not supporting submodule anymore.

The current action supports submodule like this:
    - uses: actions/checkout@v1
      with:
        submodules: true

In v2 / master this is not working anymore. Fix it (and in all other docker- projects)


fix(fromOpenApi): remove extra whitespace from content type

Fixes #61

@Kiskae Thanks for taking care of this. Never thought of the whitespaces 🤗
Personally, barely ever pass multiple content-types to Accept

Thank you for jumping on this so fast, @Kiskae! The changes look great. The only thing that's missing is an automated test for this.
Feel free to explore and add one, otherwise I will try to add it later next week. Thank you!

Added some tests. After looking at the RFC I realized that there are more complex accept headers that aren't being handled, but solving that probably involves adding dependencies. So I've just added some skipped tests as a reminder that they exist.
Also made it so the automated tests in src actually get executed :P

This looks fantastic! Thank you for adding the tests, @Kiskae!
I've polished the things a bit, mostly around test names and changing the getAcceptedContentTypes to accept just the Headers instance (it never needed anything else from the request). Made it easier to test too.

Released: v0.3.1 🎉
This has been released in v0.3.1!

📄 Release notes
📦 npm package

Make sure to always update to the latest version (npm i @mswjs/source@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.


Clarify if we still need requeue setting in the dispatcher

Do we need to explicitly give the user the option to configure requeue if we retry by default in the CE client.
Related: #540
https://github.com/knative-sandbox/eventing-rabbitmq/blob/519852a36f044dec7d79421320b6d56d26d03400/cmd/dispatcher/main.go#L45

Expectation for end users;

Broker(dispatcher) will retry for # of retries configured in delivery spec
After retries, will route message to DLX Or drop it if no DLX is configured

/assign

Had a team discussion about whether we could ensure message ordering with the current implementation. In short, there is no way we can guarantee msg process ordering when 1) use process msgs in prefetch buffer in parallel 2) we requeue unack msgs instead of using DLE.
All messages in a prefetch (prefetch count is currently configurable) are ordered, and messages in prefetch will arrive in the same ordered as they were published. However, when we process them in parallel we lose guarantee of ordering. When we re queue msgs, the requeued msgs will go to the end of the buffer and order won’t be preserved.
To guarantee message ordering, the recommendation is 1) use 1 consumer with or without prefetch (better to use to ensure better performance compare to prefetch=1) and process incoming msgs in a single thread instead of parallel 2) always use DLE for any nack msgs instead of requeuing.
Another pattern that could work is the single active consumer pattern and set prefetch to 1. Single active consumer is a property you can set in your queues and queues ensure that there is one consumer actively consuming messages at a time. People use SAC pattern for having HA consuming apps, not for parallel msgs process.


[serve] Add gRPC support by extending the existing HTTP proxy

Detail
Proposal to offer GA support on Serve's gRPC feature
Prototype PR
https://github.com/ray-project/ray/pull/37310

Really exciting feature. Thanks @GeneDer and @edoakes !