Store Figurant jID as Meta/Add Select in Persona Generator

We need to send meta data after the character is created.

Figurant jID

We also need to display this data in the figurant overview

[x] Josh will send this data from POST/PUT endpoints
[ ] Josh will add a meta field in the POST that allows Silvester to store the Joomla ID of the figurant who is playing the persona so that we can later retrieve PasFotos and OC Naams and such.
[ ] Silvester will add a dropdown in the Persona Generator to allow Figuhuis to choose OC name of the Figurant

Past me was not clear. Why is this needed again?... Think hard future me. Think hard. Did it have something to do with pictures?...

I do not remember why this was required at all. It is labeled should, Why?

https://github.com/eosfrontier/PersonaGenerator/issues/18

This has now been accomplished by adding a column in ecc_characters


Bump packages that will be released in release/0.58.0 again to account for adjusted versioning scheme

See #9428 for matching change.
To address the ambiguity with something like 0.58.1 in the new versioning scheme, we are moving to 1 indexing for minor releases to retain 4 significant digits because padding 0s are invalid.  E.g. 0.58.1000 will be the first minor release instead of 0.58.0.  main needs to be bumped to 0.58.2000 as a result.

Looks like protocol-definitions just needs another install/build to get the type tests working again (already broken in main).

@ChumpChief - One of my goals for my OCE shift is to figure out where in the bump/release process these breaks are introduced, so we can update the instructions to include the install/build loop so we don't get broken commits in main.
Is this the change that should have had a corresponding local install/build in order to get the new type validator goo for (now old) version 0.1027.0?

Looks like protocol-definitions just needs another install/build to get the type tests working again (already broken in main).

@ChumpChief - One of my goals for my OCE shift is to figure out where in the bump/release process these breaks are introduced, so we can update the instructions to include the install/build loop so we don't get broken commits in main.
Is this the change that should have had a corresponding local install/build in order to get the new type validator goo for (now old) version 0.1027.0?

Looking at the history, it broke in main but the "breaking change" was completely unrelated.  I'm guessing what happened was that it broke when we did the release for protocol-definitions yesterday then paused the release process.  Usually the next step would catch that and force the install, so the window during which it's broken is very small.  I think the real issue is probably that there is behavior here that is dependent on available published packages rather than repo state.

I'm guessing what happened was that it broke when we did the release for protocol-definitions yesterday then paused the release process. Usually the next step would catch that and force the install, so the window during which it's broken is very small. I think the real issue is probably that there is behavior here that is dependent on available published packages rather than repo state. Though this wouldn't be a lasting issue so I don't think it's worth the effort to fix.

This is my understanding as well, that main will automatically break (for some duration) every time we release a package which does type tests.  I think this should change (IMO main should never be by-design broken for any duration) though I don't have a concrete proposal of any sort.


[HIGH] VOLUNTEER TIME DISAPPEARS WHEN SAVED

@JasonTheAdams In an event listing, Volunteer Time does not save properly and the time entry disappears from event listing. I was working from this entry:
https://sdrefugeetutoring.com/event/elem-tutoring-2022-10-04/

Oops! Good catch! This has been resolved in f0ce53f


fix default YouCompleteMe path

fix default YouCompleteMe path

 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.

fix outdate link


Must-gather: Add SCC to cluster-scoped must-gather

Signed-off-by: jackyalbo<EMAIL_ADDRESS>

/ok-to-test

/ok-to-test

Thanks for the PR. Code changes looks good.
I have a request in commit msg

Please add Must-gather:  tag in the beginning
Instead of adding ->add (optional)
Thanks for the feedback - fixed

Thanks for the PR. Code changes looks good.
I have a request in commit msg

Please add Must-gather:  tag in the beginning
Instead of adding ->add (optional)
Thanks for the feedback - fixed

/lgtm

/lgtm


Bugfix/ab#10699 fix length mismatch

I had to remove the drop columns that I have in the new pull request on the application form object as they would break the previous implementation of mapping.

will fix with hotfix #236


Icon missing

Hey @grinich, thanks for checking out this plugin. (Also congrats on 30 under 30!) I can't seem to replicate this problem, however if you have the chance, could you check the developer tools to see if an error was thrown? And could you verify that unsubscribe.png is located inside of the assets folder?

It seems like in the latest version of N1, this isn't showing up in the message list anymore

Here's the error being thrown regarding the icon. It isn't in the assets folder.

Thanks for the added info @simgooder. It seems that the issue is that when you download repos, Github will append the branch name onto the folder that the code is downloaded into. When you go to install the package, it will give it the name of the folder which is now something like n1-unsubscribe-<branch_name>. This messes with the assets URL, since the package name is now different. I'll update the installation steps in the README, but you just need to make sure the downloaded folder is named n1-unsubscribe, not something like n1-unsubscribe-master.

@grinich: The quick actions are back! They just required a change to how thread data was pulled (API in place of the MessageStore) so that you could access them by hovering over a thread.


Input.Root does not store/output value when type="datetime-local"

Describe the bug
When Input.Root component is type="datetime-local", bind:value={someVariable} returns undefined. It also returns undefined when using on:input callback and on:mouseleave callback. Seems this other repository had a same issue (https://github.com/bestguy/sveltestrap/issues/314), and fixed it in commit (https://github.com/bestguy/sveltestrap/commit/f14512636aa5f91b20cb763057f1f1ce484381e7).
Reproduction
<Input.Root
type="datetime-local"
on:input={(e) => {
console.log(e.target.value);
}}

Logs
N/A
System Info
System:
    OS: macOS 14.2.1
    CPU: (8) arm64 Apple M1
    Memory: 120.08 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.10.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.14.1 - ~/Library/pnpm/pnpm
    bun: 1.0.3 - ~/.bun/bin/bun
  Browsers:
    Chrome: 122.0.6261.112
    Safari: 17.2.1
  npmPackages:
    @sveltejs/kit: ^1.27.4 => 1.30.1
    bits-ui: ^0.11.7 => 0.11.7
    cmdk-sv: ^0.0.12 => 0.0.12
    formsnap: ^0.4.1 => 0.4.1
    svelte: ^4.2.7 => 4.2.8
    sveltekit-superforms: ^1.11.0 => 1.11.0

Severity
annoyance

Sorry I just want to ensure the issue was worded correctly, the component does not return any output or raise warnings. It's not an incorrect type as per the duplicate mentioned - there is no output at all on input and the bind:value is also blank.
I understand the intended behaviour in https://github.com/huntabyte/shadcn-svelte/issues/687 is to return all values as a string, but with the "datetime-local" type nothing is returned at all which seems unintended?
I have modified the component code to fix my specific issue, as per below and this seems to be working, but would need to be accommodated for each individual type it seems as type={type} cannot be passed in if it is a two way binding.


Update doctr deploy API usage

The --gh-pages-docs flag is deprecated and the deploy directory is now a required argument.

Sorry, found a bug in this release, going to close this.


add device_cert option + better match observed request

Hi, I have a few comments.

The Accept-Language header depends on the system language of your Wii U. My Wii U is set to German for example, so it sends "de" in the Accept-Language header instead of "en".
Accept: */* is added automatically by the requests module as far as I can tell.
Adding an option to send the X-Nintendo-Device-Cert header is a good, but it only seems to be sent in a small number of requests by a real Wii U (oauth20/access_token/generate for example). Your patch includes the header in every single request.
If you really want to replicate the behavior of a real Wii U you probably want to change fields like the user agent as well.
The FLAG_HAS_SIZE flag is indeed set in all Wii U games I analyzed, but when I captured packets that were sent to the friend server I noticed that it was not set. I think it depends on the PRUDP version that's used, so unless I'm mistaken your patch is just another (maybe better) way of doing it 'wrong'.

I would be willing to add your changes to the master branch but I want to make sure that they don't break any of the example scripts first (it's easy to mess things up with prudp). I'm on vacation right now however, so I can't exactly tell you how soon that will be.

Thanks for the comments!

With regards to Accept-Language, I guess in set_device it can be set based on the country to lowercase?
I will specify the X-Nintendo-Device-Cert as an optional parameter to login instead then!
Right now I'm going off what CEMU is doing, to keep my WiiU completely unmodded but I will check if the User-Agent is set and add it to the wiki
My captures are all for Super Mario Maker and whatever friends server that uses, the size is still somewhat inconsistent so I will try to replicate exactly what I see on the wire and just make it possible to specify in the .cfg

Actually, the language is independent from the country. In my case, the country code is "NL" because I live in the Netherlands, but the Accept-Language header is still "de" because I set the system language to German. I'd probably keep English the default (like you did), and let the user change it with a generic set_header method if he wants to send a different language code to the server.
I think the device certificate should stay in set_device, because there are some other requests where it's sent to the server as well (although login and refresh_login are the only ones I've implemented so far). I'd probably store it in a separate variable in AccountAPI and add it to the Request object in each method that 'needs' it.
If there is a consistent way to replicate the real behavior I wouldn't add another config setting. I think it depends on the prudp version and whether FLAG_RELIABLE is set, so if you can figure out exactly when and why these flags are set that would be very helpful.

I touched up my commits. Now Accept-Language is set to en per default and introduced the set_header method as you suggested.
I also added a device_cert member and set it for the login and refresh_login headers only if present.

Looks good.
I just tested it myself, and the FLAG_HAS_SIZE change didn't break the friends client or another example script. I'm adding it to master.


chore: release 2.12.0

:robot: I have created a release *beep* *boop*
2.12.0 (2024-06-26)
Features

add cheque withdraw-all command (#519) (764f958)
disambiguate xdai and xbzz values (#511) (c0a5337)
improve stamp capacity listing (#514) (cf776ab)
print helpful message after topup and dilute (#516) (391ca6f)
remove upload size warning (#515) (fb11c19)

Bug Fixes

do not error out on dev mode ttl (#517) (6de29f9)
set immutable stamps as default (#513) (55eacab)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ethersphere/swarm-cli/releases/tag/v2.12.0 :sunflower:


question about the srnn_loss

In the translate.py, when you test with srnn seeds, it looks like the srnn_loss you print out is only for the last action instead of an average loss of all actions.

Hi,
Sorry this is pretty hard for me to follow. Could you point to me to specific lines in the code, and what you think they should be instead? Better yet, you could open a pull request with the fix and then we can discuss it.
Cheers,

Sure, in translate.py line 193, you have the srnn_loss for one action. However, after the for loop of all actions, in line 472, you print out the srnn_loss, which is only the srnn_loss for the last action. If i am correct, you should sum up srnn_losses for all actions and print out the average.

I think I see it. It works fine when there is only one action, but not when we train on all actions.
Would you be up for submitting a PR?


Image description: Pteropus poliocephalus 2.jpg

Which image is this for?
Pteropus poliocephalus 2.jpg
What is your suggested image description?
A bat hangs from the branches of a tree.  It is facing the camera with its wings partially extended allowing the sunlight to cast through one side.  It has prominent elblows and a highly furred body, mostly grey but with a red ruff collar.  It has small pointed ears raised upward, large front facing brown eyes and a long snout with split nostrils on its grey head.

I've accepted a slightly modified version of this suggestion.

A bat hangs from the branches of a tree. It is facing the camera with its wings partially extended, allowing the sunlight to cast through on one side. It has prominent elbows and a highly furred body, mostly grey but with a red ruff collar. It has small pointed ears raised upward, large front-facing brown eyes, and a long snout with split nostrils on its grey head.


Good Job!

This is a really elegant and thorough micro web framework. The API is pretty intuitive and the documentation is pretty easy to follow. This is a great addition to Server-Side Swift.
Good job to the authors and contributors of Alchemy. Keep it up 👍

Thank you @danielinoa ! Appreciate the feedback 😄
Let us know if there's anything you'd like to see us add as we are continue development.

Thank you @danielinoa ! Appreciate the feedback 😄
Let us know if there's anything you'd like to see us add as we are continue development.


Fix dock visibility issues

Fix dock visibility for Editor Features and distraction free mode.

fixes https://github.com/godotengine/godot/issues/66834
fixes #84125 crash when changing Editor Features with floating docks (import, filesystem, node, or history)
fixes error when closing floating dock if there are less tabs than before
fixes loading layouts in distraction free mode being very buggy (bottom dock disappears, side docks might open and be empty)
fixes floating dock still opened even if it was disabled in Editor Features when loading layout

Updated TabContainer's move_tab_from_tab_container to preserve all tab data.
The crash fix is a workaround, ideally it wouldn't have to close all floating docks. I am working on a different pr that should fix this in the future.
There were 4 separate implementations to update the dock slots visibility:
update_dock_slots_visibility(),  _update_dock_containers(), in _load_docks_from_config(), and _dock_tab_changed() (removed the lines affecting bottom docks for this one, see #39177).
I have consolidated them all in update_dock_slots_visibility().

Since this fixes a crash, should it be for 4.2?

Can you please open an issue for the crash part, I don't see it reported in the linked issue, a crash is serious enough to track actively

But note also that we're in the late stage of the 4.2 cycle and focus right now is on bugs introduced in 4.2 and fixing them so 4.2 introduces as few new bugs as possible, and as some of this behaviour goes back to 4.0 it's lower priority right now, marked for cherry picking for 4.2 so it can be added to it for 4.2.1 if it doesn't meet the deadline

Made an issue for the crash: https://github.com/godotengine/godot/issues/84125
If this isn't cherrypick-able I can create a smaller pr that is just the crash fix if needed.

I'm curious if @kitbdev could reproduce https://github.com/godotengine/godot/issues/66834, or if this is an assumed fix based on code changes.

I added some reproduction steps on https://github.com/godotengine/godot/issues/66834
I only found the crash since I was extracting all dock logic from EditorNode and found some issues and thought they should be applicable to 4.2, so I fixed them without the extraction.
I'm working on a different pr (open and close docks) that already has a proper fix for the crash.
So we can wait for that if we want to.

Since this PR is pretty much ready (just too late for 4.2), I think that we should merge it first, and then discuss your other PR built on top of this.

Cherry-picked for 4.2.2.

Cherry-picked for 4.1.4.


enableVersioning

Is there an existing issue for this?

[x] I have searched the existing issues

Current behavior
How can use cahce with enableVersioning?
When I have a version that I know the value of the controller version with the header, it doesn't work properly because of the cache
Minimum reproduction code

Steps to reproduce
No response
Expected behavior
work with enable versioning
Package version
2.2.2
NestJS version
No response
Node.js version
No response
In which operating systems have you tested?

[ ] macOS
[ ] Windows
[ ] Linux

Other
No response

Thank you for taking the time to submit your report! From the looks of it, this could be better discussed on our Discord. If you haven't already, please join here and send a new post in the # 🐈 nestjs-help forum. Make sure to include a link to this issue, so you don't need to write it all again. We have a large community of helpful members, who will assist you in getting this to work.


Hey. How to use your mod?

I Can't find any tutorial and I need your mod. how can I do this?

This is a library used by tetra, it's nothing you can use ingame. Closing, use discord for questions.

This is a library used by tetra, it's nothing you can use ingame. Closing, use discord for questions.

What is the discord? (I asking to make a mod based on your lib, not ingame....)

What is the discord? (I asking to make a mod based on your lib, not ingame....)


Modifying state during view update, this will cause undefined behavior when I add .autofillPrefix(true)

When I add .autofillPrefix(true)
I got this error

Modifying state during view update, this will cause undefined behavior

Yup, same here

Same behavior

Same behavior

Ever since iOS 16, I've had the same issue and my keyboard jumps up and down between each input

Any solutions friends?

I still don't know why anyone will create library but didn't suppourt it !

I think you missed the open-source part of the open-source library my friend

You can use the direct change method to work around the issue:
            iPhoneNumberField(
                "Title",
                text: $text,
                isEditing: $isEditing,
                formatted: true
            ) {
                $0.withExamplePlaceholder = true // <- works as `autofillPrefix`
                $0.withPrefix = true // <- works as `!prefixHidden`
            }

Feel free to reopen this issue if it persists or mention this thread if you came with a PR ;)

Please provide the minimum complete setup code and your desired behavior. So that I can tell you wich settings you need to change directly. @X901

You should no longer see this warning on version 0.10.1


Headers from multiple objects

Background Information

Module Version: 4.2.1
Node/Browser Version:

The issue I'm reporting is with:

[x] json2csv
[ ] csv2json

I have...

[x] searched to see if an issue has already been reported.
[x] verified that my JSON/CSV data is valid (using something like http://jsonlint.com or https://csvlint.io/).
[x] tried upgrading to the latest version of json-2-csv (since the issue may already be fixed).

Expected Behavior
when i provide an array like
[{"a":{"b":2,"c":"3"}},
{"a":{"c":3,"d":4}}]

output should be
a.b, a.c, a.d
2,3,
,3,4

Actual Behavior
a.b, a.c
2 ,3
,3

few headers are missing (un even json)
Data Sample
JSON:
[{"a":{"b":2,"c":"3"}},
{"a":{"c":3,"d":4}}]

Code Example
using the node version
json2csv -F -i input.json -o out.csv

This is a duplicate of #335
This is not a bug.
Please read my comment: https://github.com/zemirco/json2csv/issues/335#issuecomment-439191379
Closing. Feel free to reopen if you think that I missed something.


Add cross-account access pattern to the S3 provider

Thank you very much @Pilskalns for the feature!


Integrate cancer hallmarks from new API into widget

Apologies - all those commits were intended for issue #927 .

Ticket closed as work merged into alpha


Fix on OS where root group != 'root'

There are plenty of OS out there, where group root doesn't exist,
so use 0 instead to refer to the root users group, i.e. might
be group wheel
This is the case for me on OpenBSD, and my usual fix when I
encounter a group named 'root'

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

Yes, thank you.


CV2-5247-support-yake-keyword-extraction-for-chinese

Description
using jieba to segment mandarin text
Reference: CV2-5247 and CV2-4909
How has this been tested?
Has it been tested locally? Are there automated tests?
locally. will add automated tests as well.
Are there any external dependencies?
Are there changes required in sysops terraform for this feature or fix?
Have you considered secure coding practices when writing this code?
Please list any security concerns that may be relevant.

One extremely minor note otherwise good to go!


Allow non-standard CA for validating ACME server HTTPS in development

Hi folks :wave:,
It would be wonderful if Lego was able to easily interact with a Pebble instance. This is my own preferred way to debug issues with an ACME client and it may prove useful for integration testing now that Lego has the required ACME v2 support.
The only stumbling block that I'm aware of is that Lego doesn't facilitate interacting with an ACME server that has a HTTPS certificate from a CA that isn't part of the system trust store. This can be worked around by adding the Pebble CA certificate to the system's CA trust store but we specifically recommend against this because it can easily compromise the security of a developer's system if done carelessly or forgotten about.
Would you be interested in a feature to specify a non-standard CA certificate via command line flag or an environment variable? For instance, Certbot can be made to trust the Pebble CA by using the REQUESTS_CA_BUNDLE env var.
It seems like the challenge is primarily in piping a *x509.CertPool populated with the provided non-standard CA to the *http.Transport instance that is used by the Lego *http.Client here:
https://github.com/xenolf/lego/blob/7fedfd1388f016c7ca7ed92a7f2024d06a7e20d8/acme/http.go#L18-L30
I'd be willing to submit a PR to do the work required but wanted to touch base first to see if the feature was interesting to you and whether there were recommendations on how you would like to see the *x509.CertPool propagated forward.
Thanks!

I would welcome this.
I've been using pebble for testing the V2 implementation and always just changed the code you outlined to use a TLS config with cert validation disabled while debugging :)
I think the option with using an environment variable to override this would make sense as its only used for debugging and not for normal operation.

I think the option with using an environment variable to override this would make sense as its only used for debugging and not for normal operation.

Great. I'll see about submitting a PR in the coming days.

@xenolf I submitted https://github.com/xenolf/lego/pull/571 to allow customization of the HTTP Client CertPool based on a CA_CERTIFICATE env var. Thanks!


NumberFormatException when message is sent from

I am trying the ChatLauncher demo of netty-socketio. But, I am using SocketIOClientDotNet as the client. Please see https://github.com/Quobject/SocketIoClientDotNet
I am able to connect to the server. But when I send a json object from SocketIOClientDotNet , I get a NumberFormatException on the server side (ChatLauncher). It looks something like this:
....java.lang.NumberFormatException: Invalid int: "���42["chatevent",{"userName"" at java.lang.Integer.invalidInt(Integer.java:138).....
The same code from SocketIOClientDotNet is working fine with socket-io running on a node.js server.
While I can assume that the client is sending data in wrong format, but the fact that it works with node.js makes me think that the issue may be handled on the server side too.
I can send the test code if needed.

is working fine with socket-io running on a node.js server

which version is it?

Here are the version details:
SocketIoClientDotNet: Latest version (I did not find any version number there)
Node.js : 0.12.0 running on Windows 8 64 bit.
socket.io: 1.3.5
netty-socketio: latest (1.7.7 )

I don't understand the .NET :) Could you provide me a test with easy way to run using SocketIoClientDotNet?

I uploaded a zip file at the following location: https://www.dropbox.com/s/pv4mcxqy8dcsnqj/Release.zip?dl=0
It requires .net 4.5.
Among other things, there are files named test_data.txt and dotnettest.exe
put your URL and test object in test_data.txt and then execute dotnettest.exe from command prompt.
I noticed that the error is coming intermittently.
Let me know if I can help in any other way. Thanks.

Fixed!

This issue still exists


Add MAC Logo?

Diana wants the MAC Logo added to a few different pages

Logo added, but needs resizing


'$geoWithin' is a valid operation but it is not supported by Mongomock yet

ERROR - application.main | Server Error: code=500, message='$geoWithin' is a valid operation but it is not supported by Mongomock yet.
This seems to be happening when I try doing something like:
SomeLocationModel.objects(coordinates__geo_within_center=[(latitude, longitude), radius])

Yes we do not support geo operations yet, dupe of #315


Out of date information

You may want to consider updating this cheat sheet for latest features. For example, "Until auto-statistics are generally available" but this is generally available as of 7/21/2020.

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

ID: 61988aaf-ef0d-999f-536b-47af6b6b1258
Version Independent ID: bf939211-a490-f304-16cf-db870d3fae54
Content: Cheat sheet for Azure Synapse Analytics (formerly SQL DW) - Azure Synapse Analytics
Content Source: articles/synapse-analytics/sql-data-warehouse/cheat-sheet.md
Service: synapse-analytics
Sub-service: sql-dw
GitHub Login: @mlee3gsd
Microsoft Alias: martinle

Additionally "Next, use PolyBase to load your data into staging tables.", but my understanding is use COPY INTO which is even faster.

@jeffmoltenberry
Thanks for the feedback and bringing this to our notice. At this time we are reviewing the feedback and will update the document as appropriate.

@jeffmoltenberry  : When i look at the release notes here : https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/release-notes-10-0-10106-0#july-2020
I don't see anything mentioned about auto-statistics , but I will bank on content author @mlee3gsd  to update the document if its appropiate .

#assign:julieMSFT

@jeffmoltenberry Hi Jeff, Thank you bringing this to our attention. I am updating the article and you will see the changes in the next day or so. I will proceed with closing this issue. The @notification mechanism continues to work even after an item is closed, in case further communication is needed. We hope to hear from you again.

#https://github.com/MicrosoftDocs/azure-docs-pr/pull/125783

#please-close


Sessions are scrolled down when visited

[Uploading Screen Shot 2018-05-24 at 11.48.48.png...]

@orballo it's also happening in other screens, like announcements


Prevent removing the last 2FA method associated with an account

With this change, a user will only be allowed to remove a 2FA method if there are 2 or more 2FA methods on the account. When there is only 1, the "Remove" button will be disabled. The backend also checks if there are 2 or more 2FA methods when trying to remove.
I noticed that when the "Remove" button is disabled, the cursor doesn't change to "not-allowed" when hovering, nor does the title appear in a tooltip. That's because https://github.com/pypi/warehouse/pull/13110, added pointer-events: none to disabled buttons. On the "Your Projects" page, disabled buttons show the title and the "not-allowed" cursor because _snippet.scss sets pointer-events: auto. I wasn't sure the reason behind setting pointer-events: none in _button.scss, but if this behavior change is unintended, we could address this in another PR.
Closes https://github.com/pypi/warehouse/issues/13771

I noticed that when the "Remove" button is disabled, the cursor doesn't change to "not-allowed" when hovering, nor does the title appear in a tooltip. That's because https://github.com/pypi/warehouse/pull/13110, added pointer-events: none to disabled buttons. On the "Your Projects" page, disabled buttons show the title and the "not-allowed" cursor because _snippet.scss sets pointer-events: auto. I wasn't sure the reason behind setting pointer-events: none in _button.scss, but if this behavior change is unintended, we could address this in another PR.

I think I just did this in an effort to not have it change to the more active pointer for the button, without realizing that there was a better option. I think that that setting pointer-events: auto across all buttons probably makes more sense!

I think it's a little cleaner if we invert the logic here. (I'll let you update the tests accordingly!)

Agreed :+1:

I think that that setting pointer-events: auto across all buttons probably makes more sense!

I'll open a separate PR for this.


[Feature][SolidUI-Web] Design the page, hide the static legends and the legends data tab.

Search before asking

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

Problem Description
Design the page, hide the static legends and the legends data tab.

Description
No response
Use case
No response
Solutions
No response
Anything else
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

1


Missing Origin Validation in Webpack-dev-server for react-script-ts

Is this a bug report?
Yes

Did you try recovering your dependencies?

6.7.0
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment

(paste the output of the command here)
Steps to Reproduce

(Write your steps here:)

npm audit
=== npm audit security report ===
                          Manual Review
      Some vulnerabilities require your attention to resolve

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

High            Missing Origin Validation
Package         webpack-dev-server
Patched in      >=3.1.11
Dependency of   react-scripts-ts
Path            react-scripts-ts > webpack-dev-server
I ran npm audit fix, but its not fixing the issue.
2.
3.
Expected Behavior

(Write what you thought would happen.)
npm audit fix is throwing error "unable to fix the issue"
Actual Behavior
npm audit fix resolve the issue.

(Write what happened. Please add screenshots!)
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Hi, this should have been fixed with https://github.com/facebook/create-react-app/releases/tag/v2.1.3,  can you confirm if this still happens with new versions of CRA?

@petetnt - https://github.com/facebook/create-react-app/releases/tag/v2.1.3 is about react-script fix. but I am using react-script-ts and its not fixed. I upgraded all the packages but its throwing the Missing Origin validation error.

I tried to latest version of CRA for typescript and its still happening.

Ah, my bad.
We now natively support typescript natively and the third party project (react-scripts-ts) is now deprecated. See the repo (https://github.com/wmonk/create-react-app-typescript#-deprecated-) for more information.


Change position of testimonial-wall button

Feature request-
Remove testimonial wall button from the navbar and place it somewhere on the home page.

Note:

Do mention if your are working under GSSoC'21.
If you want to work on an issue, you should check if it has already been assigned to anyone. If the issue is free you can comment /assign to get the issue assigned to you.
If you are raising a new issue and want to work on it then also you should comment /assign under the issue to get it auto assigned.
Please refrain from adding labels to your issue/pull-request on your own. It is the job of the Project Admin and the Mentors to review your issue/pull-request and add labels accordingly.
According to the level of the issue, respective time will be allotted under which the task needs to be completed/resolved by the assigned person. If the issue is not resolved within the given time, it will be assigned to the next person. In case of any discrepancies, the decision of the maintainer will be final.

level - 0: 2 days
level - 1: 3 days
level - 2: 4 days
level - 3: 5 days

/assign

Hey @Pranav016 have you made some changes to the husky ? I am getting this error while adding a commit:

Hey @Pranav016 have you made some changes to the husky ? I am getting this error while adding a commit:

Pull the changes and try again


Clarify github.sha context description

Why:
Closes: https://github.com/github/docs/issues/17767
Uses the more accurate description from the equivalent GITHUB_SHA environment variable for the github.sha context. This explains that the SHA used is dependent on the event that triggered the workflow.
Check off the following:

[ ] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

This is still unclear IMO. The events that trigger workflows docs refer to "context of the base of the pull request" and "context of the merge commit", but those terms are not defined anywhere.
Questions:

This context includes the workflows as they are in the base branch. How about the code itself?
What is the value of github.sha for a pull_request_target event?


Ambiguity of scaledEffect in SwiftUI

Hi @zmian
I've noticed an ambiguity when using SwiftUI scaledEffect with Xcore.
Because of CGSize conformance to ExpressibleByIntegerLiteral and ExpressibleByFloatLiteral as in here:
// MARK: - CGSize - ExpressibleByFloatLiteral
extension CGSize: ExpressibleByFloatLiteral {
    public init(floatLiteral value: FloatLiteralType) {
        let value = CGFloat(value)
        self = CGSize(width: value, height: value)
    }
}

// MARK: - CGSize - ExpressibleByIntegerLiteral
extension CGSize: ExpressibleByIntegerLiteral {
    public init(integerLiteral value: IntegerLiteralType) {
        let value = CGFloat(value)
        self = CGSize(width: value, height: value)
    }
}

there's an ambiguity between these SwiftUI modifiers:
@inlinable public func scaleEffect(_ s: CGFloat, anchor: UnitPoint = .center) -> some View

@inlinable public func scaleEffect(_ scale: CGSize, anchor: UnitPoint = .center) -> some View

Particularly when we try to apply scaledEffect to a SwiftUI View:
Text("Xcore")
    .scaleEffect(1.5)    // Ambiguous use of 'scaleEffect(_:anchor:)'

Do you think you can solve this issue? My current solution simply removes both conformances but I'm sure this can be solved in a better way. Please let me know what you think.

@pawello2222 I've noticed this as well. Let me spend sometime to think about this.

@pawello2222 there are 2 ways to solve this:

Remove the conformance - like you mentioned
Or, be explicit for the API usage: .scaleEffect(CGFloat(1.5))

It seems Apple's approach is to overload these api with CGFloat and CGSize, I think it's better to remove the conformances all together. I've put up a patch to fix this here: https://github.com/zmian/xcore/commit/506e1188745131b59efe5b71e657e08c68bbf3e1

Thank you @zmian for a quick fix. This solves all issues 🎉


examples/whisper.py doesn't work

I have first tried:
PYTHONPATH=. CPU=1 DEBUG=1 python3 examples/whisper.py  ../T-22050.wav
ram used:  0.08 GB, decoder.ln.bias                                   : 100%|██████████████████████████████████████████| 167/167 [00:00<00:00, 4705.07it/s]
loaded weights in 37.21 ms, 0.08 GB loaded at 2.03 GB/s
Traceback (most recent call last):
  File "examples/whisper.py", line 198, in <module>
    waveform, sample_rate = librosa.load(sys.argv[1], normalize=True)
TypeError: load() got an unexpected keyword argument 'normalize'

Then without normalize:
PYTHONPATH=. python3 examples/whisper.py  ../T-22050.wav
ram used:  0.11 GB, decoder.ln.bias                                   : 100%|██████████████████████████████████████████| 167/167 [00:00<00:00, 1818.19it/s]
loaded weights in 93.72 ms, 0.11 GB loaded at 1.16 GB/s
/home/rocm-user/.local/lib/python3.8/site-packages/librosa/core/spectrum.py:362: ComplexWarning: Casting complex values to real discards the imaginary part
  stft_matrix[..., :off_start] = fft.rfft(fft_window * y_frames_pre, axis=-2)
/home/rocm-user/.local/lib/python3.8/site-packages/librosa/core/spectrum.py:366: ComplexWarning: Casting complex values to real discards the imaginary part
  stft_matrix[..., -off_end:] = fft.rfft(fft_window * y_frames_post, axis=-2)
/home/rocm-user/.local/lib/python3.8/site-packages/librosa/core/spectrum.py:378: ComplexWarning: Casting complex values to real discards the imaginary part
  stft_matrix[..., bl_s + off_start : bl_t + off_start] = fft.rfft(
Traceback (most recent call last):
  File "examples/whisper.py", line 201, in <module>
    dat = model.encoder(Tensor(log_spec)).realize()
  File "examples/whisper.py", line 71, in __call__
    x = self.conv1(x).gelu()
  File "/app/tinygrad/tinygrad/nn/__init__.py", line 52, in __call__
    return x.conv2d(self.weight, self.bias, padding=self.padding, stride=self.stride, dilation=self.dilation, groups=self.groups)
  File "/app/tinygrad/tinygrad/tensor.py", line 517, in conv2d
    assert groups*cin == cin_ and len(self.shape) == len(weight.shape), f"Input Tensor shape {self.shape} does not match the shape of the weights {weight.shape}. ({groups*cin} vs. {cin_})"
AssertionError: Input Tensor shape (80, 124) does not match the shape of the weights (384, 80, 3). (80 vs. 124)

librosa doesn't expect normalize; Can you fix it please?

@lusk4r Thank you for looking into this.
I have now retried with current master and the above patch and I get:
$PYTHONPATH=. python3 examples/whisper.py /app/test.wav
ram used:  0.11 GB, decoder.ln.bias                                   : 100%|███████████████████| 167/167 [00:00<00:00, 2051.79it/s]
loaded weights in 83.21 ms, 0.11 GB loaded at 1.30 GB/s
/home/rocm-user/.local/lib/python3.8/site-packages/librosa/core/spectrum.py:362: ComplexWarning: Casting complex values to real discards the imaginary part
  stft_matrix[..., :off_start] = fft.rfft(fft_window * y_frames_pre, axis=-2)
/home/rocm-user/.local/lib/python3.8/site-packages/librosa/core/spectrum.py:366: ComplexWarning: Casting complex values to real discards the imaginary part
  stft_matrix[..., -off_end:] = fft.rfft(fft_window * y_frames_post, axis=-2)
/home/rocm-user/.local/lib/python3.8/site-packages/librosa/core/spectrum.py:378: ComplexWarning: Casting complex values to real discards the imaginary part
  stft_matrix[..., bl_s + off_start : bl_t + off_start] = fft.rfft(
(1, 80, 53641)
Traceback (most recent call last):
  File "examples/whisper.py", line 202, in <module>
    dat = model.encoder(Tensor(log_spec)).realize()
  File "examples/whisper.py", line 74, in __call__
    x = x + self.positional_embedding[:x.shape[1]]
  File "/app/tinygrad/tinygrad/tensor.py", line 679, in __add__
    def __add__(self, x) -> Tensor: return self.add(x)
  File "/app/tinygrad/tinygrad/tensor.py", line 639, in add
    def add(self, x:Union[Tensor, float], reverse=False) -> Tensor: return mlops.Add.apply(*self._broadcasted(x, reverse)) if x.__class__ is Tensor or x else self
  File "/app/tinygrad/tinygrad/tensor.py", line 636, in _broadcasted
    if yshape != shape_ret: y = y.expand(shape_ret)
  File "/app/tinygrad/tinygrad/tensor.py", line 252, in expand
    def expand(self, shape, *args) -> Tensor: return mlops.Expand.apply(self, shape=tuple([x if x != -1 else s for s,x in zip(self.shape, argfix(shape, *args))]))
  File "/app/tinygrad/tinygrad/tensor.py", line 30, in apply
    ret = Tensor(ctx.forward(*[t.lazydata for t in x], **kwargs), device=ctx.device, requires_grad=ctx.requires_grad)
  File "/app/tinygrad/tinygrad/mlops.py", line 166, in forward
    return x.expand(shape)
  File "/app/tinygrad/tinygrad/lazy.py", line 275, in expand
    return self._movement_op(self.st.expand(arg), MovementOps.EXPAND, arg)
  File "/app/tinygrad/tinygrad/shape/shapetracker.py", line 183, in expand
    return ShapeTracker(self.views[0:-1] + (self.views[-1].expand(new_shape), ))
  File "/app/tinygrad/tinygrad/shape/view.py", line 77, in expand
    assert all(is_sym_int(x) and (s == x or (s == 1 and st == 0)) for s,x,st in zip(self.shape, new_shape, self.strides)), f"can't expand {self.shape} into {new_shape}"
AssertionError: can't expand (1, 1500, 384) into (1, 26821, 384)

My test file:
$file ../test.wav
../test.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, mono 16000 Hz

Try https://github.com/tinygrad/tinygrad/pull/2042

Hmm, running 6e4a12a I still get the same error.
I think it's the length of the wav file that is problematic: two different files of the same type/encoding with different lengths:
PYTHONPATH=. DEBUG=1 python3 examples/whisper.py ../test.wav
using devices: [('v1', 'Advanced Micro Devices, Inc.', 4098, 'gfx1100', 'OpenCL 2.0 ')]
ram used:  0.11 GB, decoder.ln.bias                                   : 100%|████████████████████████████| 167/167 [00:00<00:00, 1973.87it/s]
loaded weights in 86.55 ms, 0.11 GB loaded at 1.25 GB/s
/home/rocm-user/.local/lib/python3.8/site-packages/librosa/core/spectrum.py:362: ComplexWarning: Casting complex values to real discards the imaginary part
  stft_matrix[..., :off_start] = fft.rfft(fft_window * y_frames_pre, axis=-2)
/home/rocm-user/.local/lib/python3.8/site-packages/librosa/core/spectrum.py:366: ComplexWarning: Casting complex values to real discards the imaginary part
  stft_matrix[..., -off_end:] = fft.rfft(fft_window * y_frames_post, axis=-2)
/home/rocm-user/.local/lib/python3.8/site-packages/librosa/core/spectrum.py:378: ComplexWarning: Casting complex values to real discards the imaginary part
  stft_matrix[..., bl_s + off_start : bl_t + off_start] = fft.rfft(
Traceback (most recent call last):
  File "examples/whisper.py", line 237, in <module>
    transcribe_file(model, enc, sys.argv[1])
  File "examples/whisper.py", line 221, in transcribe_file
    dat = model.encoder(Tensor(log_spec)).realize()
  File "examples/whisper.py", line 74, in __call__
    x = x + self.positional_embedding[:x.shape[1]]
  File "/app/tinygrad/tinygrad/tensor.py", line 679, in __add__
    def __add__(self, x) -> Tensor: return self.add(x)
  File "/app/tinygrad/tinygrad/tensor.py", line 639, in add
    def add(self, x:Union[Tensor, float], reverse=False) -> Tensor: return mlops.Add.apply(*self._broadcasted(x, reverse)) if x.__class__ is Tensor or x else self
  File "/app/tinygrad/tinygrad/tensor.py", line 636, in _broadcasted
    if yshape != shape_ret: y = y.expand(shape_ret)
  File "/app/tinygrad/tinygrad/tensor.py", line 252, in expand
    def expand(self, shape, *args) -> Tensor: return mlops.Expand.apply(self, shape=tuple([x if x != -1 else s for s,x in zip(self.shape, argfix(shape, *args))]))
  File "/app/tinygrad/tinygrad/tensor.py", line 30, in apply
    ret = Tensor(ctx.forward(*[t.lazydata for t in x], **kwargs), device=ctx.device, requires_grad=ctx.requires_grad)
  File "/app/tinygrad/tinygrad/mlops.py", line 166, in forward
    return x.expand(shape)
  File "/app/tinygrad/tinygrad/lazy.py", line 275, in expand
    return self._movement_op(self.st.expand(arg), MovementOps.EXPAND, arg)
  File "/app/tinygrad/tinygrad/shape/shapetracker.py", line 183, in expand
    return ShapeTracker(self.views[0:-1] + (self.views[-1].expand(new_shape), ))
  File "/app/tinygrad/tinygrad/shape/view.py", line 77, in expand
    assert all(is_sym_int(x) and (s == x or (s == 1 and st == 0)) for s,x,st in zip(self.shape, new_shape, self.strides)), f"can't expand {self.shape} into {new_shape}"
AssertionError: can't expand (1, 1500, 384) into (1, 19462, 384)

PYTHONPATH=. DEBUG=1 python3 examples/whisper.py ../test2.wav
using devices: [('v1', 'Advanced Micro Devices, Inc.', 4098, 'gfx1100', 'OpenCL 2.0 ')]
ram used:  0.11 GB, decoder.ln.bias                                   : 100%|████████████████████████████| 167/167 [00:00<00:00, 1847.22it/s]
loaded weights in 92.35 ms, 0.11 GB loaded at 1.18 GB/s
/home/rocm-user/.local/lib/python3.8/site-packages/librosa/core/spectrum.py:362: ComplexWarning: Casting complex values to real discards the imaginary part
  stft_matrix[..., :off_start] = fft.rfft(fft_window * y_frames_pre, axis=-2)
/home/rocm-user/.local/lib/python3.8/site-packages/librosa/core/spectrum.py:366: ComplexWarning: Casting complex values to real discards the imaginary part
  stft_matrix[..., -off_end:] = fft.rfft(fft_window * y_frames_post, axis=-2)
/home/rocm-user/.local/lib/python3.8/site-packages/librosa/core/spectrum.py:378: ComplexWarning: Casting complex values to real discards the imaginary part
  stft_matrix[..., bl_s + off_start : bl_t + off_start] = fft.rfft(
Traceback (most recent call last):
  File "examples/whisper.py", line 237, in <module>
    transcribe_file(model, enc, sys.argv[1])
  File "examples/whisper.py", line 221, in transcribe_file
    dat = model.encoder(Tensor(log_spec)).realize()
  File "examples/whisper.py", line 74, in __call__
    x = x + self.positional_embedding[:x.shape[1]]
  File "/app/tinygrad/tinygrad/tensor.py", line 679, in __add__
    def __add__(self, x) -> Tensor: return self.add(x)
  File "/app/tinygrad/tinygrad/tensor.py", line 639, in add
    def add(self, x:Union[Tensor, float], reverse=False) -> Tensor: return mlops.Add.apply(*self._broadcasted(x, reverse)) if x.__class__ is Tensor or x else self
  File "/app/tinygrad/tinygrad/tensor.py", line 636, in _broadcasted
    if yshape != shape_ret: y = y.expand(shape_ret)
  File "/app/tinygrad/tinygrad/tensor.py", line 252, in expand
    def expand(self, shape, *args) -> Tensor: return mlops.Expand.apply(self, shape=tuple([x if x != -1 else s for s,x in zip(self.shape, argfix(shape, *args))]))
  File "/app/tinygrad/tinygrad/tensor.py", line 30, in apply
    ret = Tensor(ctx.forward(*[t.lazydata for t in x], **kwargs), device=ctx.device, requires_grad=ctx.requires_grad)
  File "/app/tinygrad/tinygrad/mlops.py", line 166, in forward
    return x.expand(shape)
  File "/app/tinygrad/tinygrad/lazy.py", line 275, in expand
    return self._movement_op(self.st.expand(arg), MovementOps.EXPAND, arg)
  File "/app/tinygrad/tinygrad/shape/shapetracker.py", line 183, in expand
    return ShapeTracker(self.views[0:-1] + (self.views[-1].expand(new_shape), ))
  File "/app/tinygrad/tinygrad/shape/view.py", line 77, in expand
    assert all(is_sym_int(x) and (s == x or (s == 1 and st == 0)) for s,x,st in zip(self.shape, new_shape, self.strides)), f"can't expand {self.shape} into {new_shape}"
AssertionError: can't expand (1, 1500, 384) into (1, 5559, 384)

@nextgens, in  #2068 I tried to split the waveform in chunks in order to fit the required dimensions

Thank you.
That works when applied on top of master!
It seems real slow compared to the original but it does output something :tada:

Looks like there was #1410 too that was WIP on this

#2378 adds support for >30s audio transcription

Great, thank you.
This is solved


Adsk Contrib - Fix some issues reported by SonarCloud

Signed-off-by: Patrick Hodoul<EMAIL_ADDRESS>Done by @BernardLefebvre.
The pull request fixes several issues reported by Sonar Cloud.

Friendly reminder that the pull request can now be merged next week.


Update to Rails 5

Make changes to generate rails5 app

Remove puma generation
Remove quite assets
minor improvements

Coverage increased (+0.7%) to 51.152% when pulling b452264333d18c44b216d9d5dd7c5b02dcdb2e06 on rails5 into 0a4d35eb01d796c0f6bfdb76a0e095b2cca170d4 on master.

http://gph.is/NY2QTR


Bypass blocks causing accessibility issue certain browsers

An issue encountered with CDTS the same is encountered on the canada.ca site as well.
Bypass blocks are invisible causing an accessibility issue for certain OS/Browser combinations.
•	Behaviour in Mac: Firefox - The tab focus does not go to the blocks.
•	Behaviour in iPad: Voiceover + Chrome -  The bypass blocks read but not highlighted in a contrastic color.
Example of the bypass block being referred (highlighted in red border) -

@Kamla55 Could you confirm this issue still exists in version 4.0.39 ? Thanks.

Hold on checking with the client - they will test and let us know

hey @Kamla55, would you know if the clients got back to you regarding this issue? Thanks.

Closing. If this issue occurs, we can reopen.


Some multimedia keys on the keyboard are not sent to the RDP server

Describe the bug
FreeRDP tries to map X11 keycodes to RDP scancodes, but fails with certain media keys.
For example, when I press the VK_BROWSER_REFRESH (XF86Refresh) key, the following log appears in the console:
[ERROR][com.freerdp.client.x11] - [xf_keyboard_send_key]: Unknown key with X keycode 0x08
Note: The VK_BROWSER_REFRESH key exists in the RDP scancode list
https://github.com/FreeRDP/FreeRDP/blob/d864393a8a7ec1b54b0c89c8141b2b563e8249ec/include/freerdp/scancode.h#L222
A list of keys that don't work:

rdp code
scancode
keysym

103
181
XF86Refresh

104
136
XF86Stop

109
234
XF86AudioMedia

110
156
XF86Launch0

111
157
XF86Launch1

(from https://github.com/neutrinolabs/xrdp/pull/3022)
To Reproduce
Try pressing certain media keys (or, in my case, send the key programmatically with xdotool key "XF86Refresh")
Expected behavior
FreeRDP sends a valid RDP scancode to the RDP server.
Screenshots
Not applicable.
Application details

FreeRDP version (xfreerdp /version)
This is FreeRDP version 3.4.0-3 (2-3.4.0-3)
Command line used
xfreerdp3 /v:omitted /u:omitted /p:omitted
Output of xfreerdp /buildconfig
Unnecessary
OS version connecting to (server side)
ArchLinux, pinned to 2024-03-06 + xrdp (PR https://github.com/neutrinolabs/xrdp/pull/3022) + Xvnc session
If available the log output from a run with /log-level:trace 2>&1 | tee log.txt
Unnecessary
If you built it yourself add some notes which tag/commit/branch you have used, also your cmake parameters and
compiler can help
Tag 3.4.0, CMake parameters, Compiler: gcc (GCC) 13.2.1 20230801

Environment (please complete the following information):

OS: [e.g. Linux/Windows/Android/..]
Linux
Version/Distribution: [e.g. Debian 10, Windows 2008, Android 10]
ArchLinux, pinned to 2024-03-06. FreeRDP is from ArchLinux GitLab.
Architecture: [amd64, arm]:
amd64

Additional context
Related: https://github.com/neutrinolabs/xrdp/pull/3022

@sasha0552 check freerdp_keyboard_get_rdp_scancode_from_x11_keycode there is a map X11_KEYCODE_TO_VIRTUAL_SCANCODE that should contain this mapping.
it is populated in freerdp_keyboard_init so check which keys are mapped and which are not.


Show child device's interfaces in parent device

We have a lot of network appliances that have a bay to add additional interfaces (like http://www.lannerinc.com/products/x86-network-appliances/rackmount/fw-8758).
We currently define the parent device type (fw-8758) with its GB-interfaces and a bay for the interface card.
We then define a child device type for the interface card which is then added to parent device's bay.
The problem is: after instantiating parent- and child-device and "inserting" the child device into the parent, I can not connect an interface or assign an IP to an interface of the interface card when looking at the parent device's page.
IMHO, by inserting the interface card into the parent device, the interfaces become interfaces of the parent device and hence should be configurable from the parent device's page.

Device bays are only meant to house discrete, autonomous devices (for example, a chassis of blade servers). Components which do not provide their own control plane (for example, a line card in a chassis switch) should be installed as modules.
Incidentally, #824 was just opened to foster detailed discussion around this concept, so I'm going to mark this as a duplicate of that issue. Please feel free to share any additional thoughts there.


Unhandled libobsensor::memory_exception in C++ Wrapper Causes Application Crash

Description:
I am encountering an issue with the Orbbec SDK C++ wrapper, which is based on a C API. The wrapper’s API contract specifies that exceptions should be propagated as k4a::error when interfacing with the C++ code. However, the underlying Orbbec SDK throws exceptions like libobsensor::memory_exception, which are not propagated as k4a::error.
In my case, I am seeing the following log, likely caused by a camera cable issue:
[09/05 17:10:40.622595][warning][4680][ObException.hpp:40] Update data size(13331533) > data buffer size! (6666240)
terminate called after throwing an instance of 'libobsensor::memory_exception'
what():  Update data size(13331533) > data buffer size! (6666240)

Question:
Is there something I am missing about how this wrapper is supposed to handle exceptions from the underlying Orbbec SDK, or is there currently no mechanism to catch and handle these exceptions (libobsensor::memory_exception) through the C++ interface?
Any guidance on how to properly handle such exceptions would be greatly appreciated.

Description: I am encountering an issue with the Orbbec SDK C++ wrapper, which is based on a C API. The wrapper’s API contract specifies that exceptions should be propagated as k4a::error when interfacing with the C++ code. However, the underlying Orbbec SDK throws exceptions like libobsensor::memory_exception, which are not propagated as k4a::error.
In my case, I am seeing the following log, likely caused by a camera cable issue:
[09/05 17:10:40.622595][warning][4680][ObException.hpp:40] Update data size(13331533) > data buffer size! (6666240)
terminate called after throwing an instance of 'libobsensor::memory_exception'
what():  Update data size(13331533) > data buffer size! (6666240)

Question: Is there something I am missing about how this wrapper is supposed to handle exceptions from the underlying Orbbec SDK, or is there currently no mechanism to catch and handle these exceptions (libobsensor::memory_exception) through the C++ interface?
Any guidance on how to properly handle such exceptions would be greatly appreciated.

Okay, we have received your question and will provide you with a response after analyzing it.

Description: I am encountering an issue with the Orbbec SDK C++ wrapper, which is based on a C API. The wrapper’s API contract specifies that exceptions should be propagated as k4a::error when interfacing with the C++ code. However, the underlying Orbbec SDK throws exceptions like libobsensor::memory_exception, which are not propagated as k4a::error.
In my case, I am seeing the following log, likely caused by a camera cable issue:
[09/05 17:10:40.622595][warning][4680][ObException.hpp:40] Update data size(13331533) > data buffer size! (6666240)
terminate called after throwing an instance of 'libobsensor::memory_exception'
what():  Update data size(13331533) > data buffer size! (6666240)

Question: Is there something I am missing about how this wrapper is supposed to handle exceptions from the underlying Orbbec SDK, or is there currently no mechanism to catch and handle these exceptions (libobsensor::memory_exception) through the C++ interface?
Any guidance on how to properly handle such exceptions would be greatly appreciated.

Hello, we have identified the cause of the issue and will fix it in future versions.


Is it possible to terminate a cell?

Description:
[Description of the issue]
Steps to Reproduce:

[First Step]
[Second Step]

Versions:
Which OS and which version of Hydrogen and Atom are you running?
You can get this information from copy and pasting the output of atom --version  from the command line.
Plugins:
Do you have any Hydrogen plugins installed and active?

[ ] hydrogen-python
[ ] Hydrogen Launcher
[ ] Data Explorer

Logs:
Please post any error logs and the output of the developer tools as described in our Debugging Guide.

You can interrupt the kernel. Check the Hydrogen commands in the command palette


Enhance mock daemon client

Mock daemon should handle
request in given order and
be able to return response
whatever the request body.

self-ACK a38ac7c93137576f97d7ba0c30c849a0388a2bf0


[SPARK-41098][SQL] Rename GROUP_BY_POS_REFERS_AGG_EXPR to GROUP_BY_POS_AGGREGATE

What changes were proposed in this pull request?
This PR proposes to rename GROUP_BY_POS_REFERS_AGG_EXPR to GROUP_BY_POS_AGGREGATE
Why are the changes needed?

The error class name should be simplificated as much as possible.
Does this PR introduce any user-facing change?
No
How was this patch tested?
./build/sbt “sql/testOnly org.apache.spark.sql.SQLQueryTestSuite*”

ping @itholic

+1, LGTM. Merging to master.
Thank you, @itholic.


feat: Collaboration

I can't seem to see this branch locally for some reason. Is it a private branch?

        <div
            style={{
              marginTop: topBarHeight,
              paddingLeft: 0,
            }}
          >
            <EditorWrapper
              defaultContext={siteConfig.content[contentKey]}
              context={contentConfig}
              branches={branches}
            />
          </div>

this is the component that seems to be causing the cursor to appear at the wrong height. Somehow the Editor will need to compensate for the marginTop applied to the div that wraps around the editorWrapper

nice!


is there anyway to auto refresh cache after online

the item stats changed to what it was before upgrade after character offline and online again, it seems right after refresh cache with that NPC, is there any way to finish this in player login events?

Can you provide exact steps on how to reproduce this issue? How were the item stats changed? When player logs in, item packets are sent after 3 seconds, so everything should be visually OK. Manual cache refresh using the NPC calls the exact same code as log in event, so I can't see  any differences.


lazy resonite port

bare minimum edits to make the mod work. unlike #6 I kept the csproj file intact.

:)


Store databases in the config

Machine configs should keep track of databases:
databases:
  - engine: mysql
  - version: "5.7"
  - dbs:
    - mydb1
    - mydb2

Then the apply / init commands (and any other commands that apply config changes internally) should start ensuring that each of the configured databases exist.
(apply should not remove databases that have been removed from the config, though, since that could end up removing databases people created manually within the VM.)

We discussed not adding this to the config and instead added the db command namespace to handle the easy creation of databases.
Are we good to close this out?

Based on our last conversation, yeah.


src/GlassCat/generate.jl tests

The existing GlassCat test sets are a little jumbled.
@testset "Parsing Tests" parses an AGF file TEST_CAT.agf into a Julia Dict cat, but then only checks the first glass' values.
@testset "Module Gen Tests" then checks the generated AGF_TEST_CAT.jl against cat, which creates a dependency on the previous test set.
@testset "Glass Tests" then uses a glass from the TEST_CAT module, which also creates a dependency on the previous test set.
Reorganising these and extending the range of checked values to all 4 glasses catches a couple of odd behaviours that have snuck into GlassCat (mostly due to changes that I've made). I'll fix these before opening the PR for review.
Changes

"AGF to dict", "dict to JL" and pure "glass tests" properly organised within their test sets
TEST_CAT.agf tests expanded to check all values instead of just the first glass
Fix #133, which was caught by the expanded tests
Add a TEST GlassType to avoid redefinition of const AGF_GLASSES etc.

Codecov Report

Merging #143 (6cb6329) into main (352ea4b) will decrease coverage by 0.82%.
The diff coverage is 68.75%.

@@            Coverage Diff             @@
##             main     #143      +/-   ##
==========================================
- Coverage   48.37%   47.54%   -0.83%
==========================================
  Files          65       64       -1
  Lines        6659     6613      -46
==========================================
- Hits         3221     3144      -77
- Misses       3438     3469      +31

Impacted Files
Coverage Δ

src/GlassCat/GlassTypes.jl
8.86% <61.53%> (+0.45%)
:arrow_up:

src/GlassCat/generate.jl
88.54% <100.00%> (+0.12%)
:arrow_up:

src/Optical/Emitters/Emitters.jl
0.00% <0.00%> (-20.00%)
:arrow_down:

src/Geometry/Primitives/Qtype.jl
75.00% <0.00%> (-8.34%)
:arrow_down:

src/Optical/LensAssembly.jl
48.22% <0.00%> (-7.33%)
:arrow_down:

src/Optical/OpticalInterface.jl
63.23% <0.00%> (-4.30%)
:arrow_down:

src/Geometry/CSG/Intersection.jl
48.57% <0.00%> (-2.14%)
:arrow_down:

src/Geometry/Geometry.jl
0.00% <0.00%> (-1.86%)
:arrow_down:

src/Geometry/Primitives/Curves/BSpline.jl
66.15% <0.00%> (-0.52%)
:arrow_down:

src/Geometry/CSG/Interval.jl
83.20% <0.00%> (-0.37%)
:arrow_down:

... and 4 more

Continue to review full report at Codecov.

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

@friggog and @alfredclwong is this PR ready to merge? A conversation doesn't seem resolved.

@BrianGun I haven't yet resolved Charlie's comment on the new glasstype arg. In general I think it's important to have longer, in-depth code review periods and I don't see a need to rush PR merges (unless we're building merge conflicts elsewhere).

didn't mean to rush anybody. Just wanted to make sure this wasn't forgotten.


Datakurre acceptance tests setup

@tisto I only now noticed that Start Webpack -keyword accepts custom check parameter. So everything is great and I can finish this on Tuesday morning.

Coverage remained the same at 58.086% when pulling e0061fca83682e4a8be9ec48d33fb0473a59dd11 on datakurre-acceptance-tests-setup into 23d4245787e0fa7b141915d3455edd6548a2aa21 on master.

@tisto This seems to pass now. Review would be appropriate. This includes

pybot and robot-server for api
Robot test setup with examples
Docker for API
Jupyter notebook setup

This still needs

confirmation that Jupyter works for you and possible fixes (I have a little different setup due to NixOS)
figure out the best practices to use these tools and document
integrating tests to yarn run in package.json

@tisto Please, read README changes https://github.com/plone/plone-react/pull/102/files#diff-04c6e90faac2675aa89e2176d2eec7d8 for a summary
It's good to know that both docker image and Travis-CI setup are based on the requirements.txt generated by api/buildout.cfg
For Jenkins you could choose to use either buildout created pybot or pip installed pybot (as created in travis.yml).
For local test development it's easiest to use docker, because it has the test fixture set up. If you want to use buildout-created robot-server you need to check the environment variables for the environment from Dockerfile.
Running all tests with ... pybot ... tests/ will always manage both backend and frontend.
Running individual test case files ... pybot ... tests/test_login.robot assumes that backend and frontend are already running and backend is manually cleaned up after tests.


[sai-gen] Update Sai attribute doc to include the latest support values, also split it into SaiVal and SaiTable for better clarity.

No changes to generated contents as below, using the latest main as baseline:
r12f@r12f-dl380:~/data/code/sonic/DASH/dash-pipeline
$ diff SAI/SAI/inc ~/data/code/sonic/DASH-exp/dash-pipeline/SAI/SAI/inc

r12f@r12f-dl380:~/data/code/sonic/DASH/dash-pipeline
$ diff SAI/SAI/experimental/ ~/data/code/sonic/DASH-exp/dash-pipeline/SAI/SAI/experimental/

r12f@r12f-dl380:~/data/code/sonic/DASH/dash-pipeline
$ diff SAI/lib ~/data/code/sonic/DASH-exp/dash-pipeline/SAI/lib

ok, as promised in #473 . getting the doc and existing code up to date first.

PR is ready to review.

Woot! Thanks!


fix "failed to read lastArgFile"

if the palera1n directory's path had spaces in it, img4tool would not be able to read the blob. adding quotes around the $(pwd) call fixes this.

still though
why use palera1n in a folder with spaces

if you're reading this in the discord server
please react fr
thank you bye


UtilityIcon prototype error

Hello, I get this error on the developper console :
Warning: The <UtilityIcon /> component appears to be a function component that returns a class instance. Change UtilityIcon to a class that extends React.Component instead. If you can't use a class try assigning the prototype on the function as a workaround. `UtilityIcon.prototype = React.Component.prototype`. Don't use an arrow function since it cannot be called with `new` by React.

What component are you rendering? Can it be with website examples?


"Go To Definition" is limited compared to PyCharm

In PyCharm, it seems that "Go To Definition" is searching for any function/method/class candidate with the same name, even if the imports are missing, even if the types are not correct or undefined/unknown. In the screenshot below, imports are missing, and code analysis should not be able to find the definition of myMethod. Still PyCharm finds two myMethod methods in the root directory, and proposes them as candidate.
It would be helpful if pylance could also propose candidates based only on name matching, rather than code analysis/inspection.
PyCharm

VS Code

Where are Cat and Dog defined? If they don't exist, we will infer the return type of that createAnimal function as Unknown and then not know anything. PyCharm's analysis method is quite different than a typical type checker, and it's somehow deciding (without evidence) that Cat and Dog are classes, and that myMethod exists on them.
Actually make the code valid, and we have the same behavior:

The main value of "Go to Definition" is to show the precise definition used for the selected symbol. Showing all definitions in the project that happen to share the same name would greatly reduce the value of this feature. The behavior you describe would also be inconsistent with the intended use of "Go To Definition" in the language server protocol.

Yeah, I don't think this is a good idea... This is a constrained case where there really is only one option. what if there are many? Should it search all libraries for potential candidates too? And so on...

Incidentally, there's already a way to search for a symbol by name within the project. Choose "Go To Symbol in Workspace" (command-T on Mac OS), then start typing the first few characters of the symbol you want to look up.

I don't see us doing this. Note that we already provide diagnostics with quick fixes that would automatically fix this code (hover on the squiggles for Cat and Dog with indexing enabled and you'll get auto-imports).

This is a constrained case where there really is only one option. what if there are many?

I totally agree with you two @erictraut and @jakebailey : the behaviour proposed by PyCharm is not relevant when the exact/precise definition is already found. But it is relevant when nothing is found : user can still find something, and in many cases the candidates make sense, because there are not so much foo name in a real project, thus not so much false candidates.

Choose "Go To Symbol in Workspace"

I did not know this feature, and it does the job well, thank you :+1:

quick fixes that would automatically fix this code

The point is not to fix the code. Python allows duck typing, and thus you can write valid code where it is not possible to predict the type of objects. You might guess the type, but without certainty. In such cases, name based candidates are relevant for the developer.


added openapi

OMG, I am not reviewing this thing :rofl:

closing this one, since we banked on keeping this out of repo!


Issues with rm -rf command on windows powershell

It appears that windows powershell doesn't support the rm -rf command that is used in the main scripts.
This can be fixed in 2 ways that I'm aware of:

Change the command to make it agnostic using something like rimraf or writing something in Node
Update the README to make sure users use the Bash terminal on windows, as it does support the rm -rf command.

@larshp let me know if you have a preference and I can work on this

feel free to change it to use rimraf

Closing since PR https://github.com/abap-openapi/abap-openapi/pull/91 was merged


Make Material AppBar search aware

Make this https://github.com/flutter/flutter/blob/b586a97ad25cd5d33b98573ef207578707a09f46/examples/stocks/lib/stock_home.dart#L286
Should probably handle auto suggests too
See also:
https://material.io/guidelines/patterns/search.html#search-in-app-search

For the people who have marked this thumbs-up, what exactly do you want this to entail beyond what the stocks app does?
cc @willlarche

For me, the main thing is Expandable search in https://material.io/guidelines/patterns/search.html#search-in-app-search (which seems more or less what the stock app does)

I believe that's implemented now with https://github.com/flutter/flutter/pull/17629?

yay, awesome


Feat: ECS container status updating

Features:

Added initial method to set container instance states to DRAINING or ACTIVE
Updated boto3 dependency to the corresponding version introducing the new method

Fixes:

PEP8 fixes - minor issues as well as a couple of duplicate methods - have kept the newer version where appropriate

References:

https://aws.amazon.com/about-aws/whats-new/2017/01/amazon-ecs-supports-container-instance-draining/
https://boto3.readthedocs.io/en/latest/reference/services/ecs.html#ECS.Client.update_container_instances_state

I've updated the run_task method to only place tasks on active instances for now but the chunk of work to fully implement container draining as well as resource checking when placing tasks/services will be made in a different merge request as it's a fairly substantial piece.

I realise the test for instance state setting is a bit unwieldy, but I wanted to cover testing idempotency as well as switching between the two states to cover the real world behaviour as closely as possible.

Coverage increased (+0.08%) to 93.505% when pulling 2ab752fd54c23b2299a22c751e71b35f4a33a856 on gjtempleton:ECS-Container-Draining into d3df810065c9c453d40fcc971f9be6b7b2846061 on spulec:master.

This is great, thanks!


PDF print is not rendering the document second time on safari browsers

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: Safari / 14.0.3
Operating system and its version: BigSur
PDF.js version: Latest
Is a browser extension: No

Steps to reproduce the problem:

Navigate to the demo link - https://mozilla.github.io/pdf.js/web/viewer.html
Click on print
The print renders the exact 14 pages
Cancel the operation and click on print for the second time
A pop-up comes up asking your permission to print/ cancel
Click on print, rather than showing the 14 pages it shows 3 blank pages.

I am trying to skin on top of the default viewer and our team supports safari browser while implementation we came across this issue. I observed that during the second time when the pop-up is displayed the "data-pdfjsprinting" attribute is getting destroyed and it is unable to render the pages as expected.
What is the expected behavior? (add screenshot)
It should show the exact 14 pages as it did for the first time

What went wrong? (add screenshot)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension): NA

Duplicate of #7597

Looks similar enough to issue #7597, hence closing as such.
Please note that the web platform unfortunately has quite limited support for controlling printing, and that Safari isn't the main focus of development in the PDF.js library.
Duplicate of #7597

Duplicate of #7597, since this issue looks similar enough.
Please note that the web platform unfortunately has quite limited support for controlling printing, and that Safari isn't the main focus of development in the PDF.js library.

@Snuffleupagus, I think the issue I raised looks similar to #9578.


remove a static keyword in fast_ftoi

this ensures that fast_ftoi is thread-safe and faster ( I think) because of cache locality.

I don't know if this really makes things faster, but I think this whole method looks quite outdated by now and should like be replaced by a simple return lrintf(a); on all platforms.


Collapsible SidenavBoxes

Enables 'Collapse' functionality for sidenav boxes on desktop.
Makes it possible to display group Sidenav all the time, without it taking to much space.
Group sidenav is folded in on storePages automatically now.
On group pages, the StoreSidenav is hidden.

I like this change - makes the sidebar more consistent across group and store.
Maybe it would be clearer to use the same collapse/uncollapse icon also in the wall notifications (availablePickups, joinendPickups)?
If you could run yarn test -u to generate updated snapshots and commit them, that would be great! It makes it possible to see if something unexpected changed.

Thanks! Do you think the now sidenavBoxes store endpoint makes sense? And closing / opening the group box in the store endpoint?
And I actually wondered how to update those! Will do that.

Do you think the now sidenavBoxes store endpoint makes sense? And closing / opening the group box in the store endpoint?

You mean the vuex module? Yes, I think it's nice to have these in state management, gives us a clear place where to control them.


[CI] Use for loop insetad of find -exec to catch tests errors

Fixes #224

Great, it actually caught the failing tests it missed the last time!
I'll update the tests, merged them into dev-v0.4.0 and then we can merge dev-v0.4.0 into this branch so the CI passes and we can merge this branch into dev-v0.4.0

@ohadmo @tijyojwad PR #226 fixes the failing tests in cudamapper. After merging those changes tests for this PR also pass


Replace glsl-to-spirv and spirv-reflect with Naga

Replace both bevy-glsl-to-spirv (a fork of glsl-to-spirv) and spirv-reflect with naga
This should reduce compile times a lot, as well make it easier to cross-compile for platforms like android, ios, and webassembly.
The glsl frontends and spirv backend for naga are not very mature yet. They're progressing pretty quickly, but they're still not usable for real applications yet. Hopefully this will change in the upcoming weeks.

I love this. Naga is a big step forward in terms of build complexity and compile times. I'll try to review as soon as I can.

I also just added a preprocessor in the naga-glsl path (since the glsl-new glsl naga front-end doesn't have one yet) and it adds support for shader includes! Not exposed yet, of course though.

FYI I just tried rebasing this onto the current master commit, applied the fixes I've been experimenting with for wasm for the non-rendering-related stuff, and managed to compile all crates to wasm! No idea yet if rendering will actually work on the web, but the tests still pass and examples still run on Linux, and without this PR I couldn't get anything depending on the renderer to compile at all.

I tried updating this PR to current bevy main and released naga, it is failing on https://github.com/gfx-rs/naga/issues/321

Dang. Thanks for checking. Hopefully we'll be able to use it Soon™ :smile:

Closing this issue as discussed here.
This appears to be a goal of the new rendering rework planned for 0.6.
As well have #2130 which appears to be a alternative to this PR.
Please feel free to reopen if I'm incorrect or future development spawns from this PR :)


[Bug]: Could not find a declaration file for module '@rnmapbox/maps'.

Mapbox Implementation
Mapbox
Mapbox Version
default
Platform
iOS, Android
@rnmapbox/maps version
10.0.0-rc.13
Standalone component to reproduce
import React from 'react';
import {StyleSheet, View} from 'react-native';
import Mapbox from '@rnmapbox/maps';

function App(): JSX.Element {

  return (
    <View style={styles.page}>
      <View style={styles.container}>
        <Mapbox.MapView style={styles.map} />
      </View>
    </View>
  );
}

const styles = StyleSheet.create({
  page: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
  },
  container: {
    height: 300,
    width: 300,
  },
  map: {
    flex: 1,
  },
});

export default App;

Observed behavior and steps to reproduce

Create a new react-native application with npx react-native init MyApp --template react-native-template-typescript
Install this library

Expected behavior
No response
Notes / preliminary analysis
No response
Additional links and references
No response

@johhansantana Sorry but without steps to reproduce the issue there is not much I can do.
Do you have a<EMAIL_ADDRESS>file?

@mfazekas I'm assuming the steps under Observed behavior and steps to reproduce aren't enough?
Though it seems I don't have that file you're mentioning:

It appeared I had installed the package without @ and that caused this issue for me.
yarn add @rnmapbox/maps

As a heads-up, this issue seems to be caused by the suggested way to install the library in the installation steps.
yarn add rnmapbox/maps#main seems to not install the declaration file, whereas yarn add @rnmapbox/maps solved the issue, as mentioned above.


Fix calculation of crowdsale participation on Windows

Note: this PR is currently used to pin down the issue, and to leverage the cache of Travis CI.

The issue I'm currently facing: for the MetaDEx we use the boost::rational wrapper. There are a few options now:

we extend uint256 and make it "compatible" with boost::rational (meh.. has the risk of more issues with boost)
we reimplement boost::rational (meh.. that's complicated, because  boost::rational is actually pretty smart in term of normalizing and reducing the numbers internally (e.g. 3/6 + 4/8 -> 1/2 + 1/2 and not 24/48 + 24/48)
we get rid of boost::rational and untangle the calculations to use plain numbers (meh.. a lot of work)
we do nothing, and just hope we never see numbers, which break consensus ;)

I'm in favor of (3), which provides full control, and seems to be the cleanest solution.

Alright..
The MetaDEx core logic, traditional DEx, STO and crowdsale participations are updated.
The boost::multiprecision library is still in use for:

order matching, comparing prices (consensus relevant)
creating string representations of the prices (not consensus relevant)

I'm not entirely sure how the comparison works, but the worst implementation is probably something like:
2 / 3 < 1 / 8?

->  2 * 8 < 1 * 3
 = 16     < 3
 = false

... because then the intermediate results may be out of int64 range:
INT64 / INT64 < INT64 / INT64 ?

-> INT64 * INT64 < INT64 * INT64
 = INT128-ish    < INT128-ish

This should be fine, given that we use int128_t, and there is still a bit of space, but I'd really like to get rid of the whole multiprecision library as soon as possible, which is sad, but probably the better choice.
I tested an approach without int128_t and without rational_t, where I implemented a rational class with uint256 (see: 0fcbb9ad30d87bbff4a995dc02ffb42b06f8c3b3). This worked fine, but requires a non-trivial overhaul of the "price to string" methods.
This is not part of this PR, and may be added later. I'm a bit drained at the moment, and I'd like to finish this first..
@zathras-crypto: for an easier review I converted the MetaDEx logic in very small steps, and it's probably best to look at each commit one by one. If this submission is accepted, I'm going to squash all "temp" commits.

@dexX7 this is just phenomenal work mate, absolutely fantastic, thanks!!!!!

The boost::multiprecision library is still in use for:
order matching, comparing prices (consensus relevant)

In a 'busy' market where users may be listing trades 1 willet off the previous "best" trade to make themselves the most attractive offer (eg listing a 0.0000514 MSC price when the current best price is 0.0000515 MSC) do we run the risk of the engine matching different trades together if we continue use of int128_t where the results may be different on Windows?

@zathras-crypto: for an easier review I converted the MetaDEx logic in very small steps, and it's probably best to look at each commit one by one. If this submission is accepted, I'm going to squash all "temp" commits.

I've reviewed the changes (to the best of my ability, I'm not that great with the math hehe) - looks great!
I've also run some local testing on Ubuntu building the current Omni tip and building this branch, then comparing the consensus hashes for them from fresh parsing on both testnet and mainnet.  The hashes match so the results from the changes are identical between the two builds for both networks on Linux for previous transactions :)
Testnet block 552887:
omnicore-0.0.10
03d165f88ba25a4525c509950cbba3a00a7ebdc2c456d7be4304307c3650bf6e
0.0.10-Z-Testoc-0.10-crowdsale-participation-win
03d165f88ba25a4525c509950cbba3a00a7ebdc2c456d7be4304307c3650bf6e

Mainnet block 372496:
omnicore-0.0.10
1ac2da8f151ee650d79dc75a7a5eb841c60168969ed09f98788c9f816f72e496
0.0.10-Z-Testoc-0.10-crowdsale-participation-win
1ac2da8f151ee650d79dc75a7a5eb841c60168969ed09f98788c9f816f72e496

This is not part of this PR, and may be added later, because I'm a bit drained at the moment, and I'd like to finish this first..

I'm happy for you to merge dude, and want to say a huge thank you, we'd be lost without your skills and strong work ethic bud so thank you so much :)

Nice, thanks a lot, @zathras-crypto!

do we run the risk of the engine matching different trades together if we continue use of int128_t where the results may be different on Windows?

To be honest, I have no idea. I've never seen an issue here, but I also have not a good idea how to test this (ideas welcome!). We have the following precedence in this context:
1)<PHONE_NUMBER>854775807000000000000 /<PHONE_NUMBER>00000000000 =<PHONE_NUMBER>8         FAIL
2)<PHONE_NUMBER>8547758070000000000000 /<PHONE_NUMBER>00000000000 =<PHONE_NUMBER>97        FAIL
3)<PHONE_NUMBER>85477580700000000000000 /<PHONE_NUMBER>00000000000 =<PHONE_NUMBER>987       FAIL
4)<PHONE_NUMBER>854775807000000000000000 /<PHONE_NUMBER>00000000000 =<PHONE_NUMBER>9886      FAIL
5)<PHONE_NUMBER>8547758070000000000000000 /<PHONE_NUMBER>00000000000 =<PHONE_NUMBER>98876     FAIL
6)<PHONE_NUMBER>85477580700000000000000000 /<PHONE_NUMBER>00000000000 =<PHONE_NUMBER>988770    FAIL
7)<PHONE_NUMBER>854775807000000000000000000 /<PHONE_NUMBER>00000000000 =<PHONE_NUMBER>9887715   FAIL
8)<PHONE_NUMBER>8547758070000000000000000000 /<PHONE_NUMBER>00000000000 =<PHONE_NUMBER>98877165  FAIL
9)<PHONE_NUMBER>88072266900000000000000000000 /<PHONE_NUMBER>78212887156 =<PHONE_NUMBER>00808077  FAIL

These are the wrong results observed in #124 and the new one, reported recently.
It's not clear to me why they fail on Win64 (but not Win32), and it's interesting that, when using checked_int128_t for (9), an overflow exception is thrown on Win64. However, even when using int1024_t on Win64 for (9), it was still incorrect.
I also can't tell how we could check, if we ever may see such large numbers during the comparison of prices, because it's not clear to me how boost works. The implementation is on GitHub, but it's hard for me to gain an understanding here: boost/multiprecision/cpp_int
It might be worth to file an issue though.

FYI I built 25c85ce277dd580702f9e9ce4c26dd65a798a53e for Win64 and ran it through a fresh parse, it passed block 320000 with no checkpoint failure with your new code :)
It's syncing the rest of the chain now, I'll let you know if it fails further on but so far looking good :)

Yay, thanks for the test! I'm currently away from my desktop (until tomorrow), so the test is very appreciated!


Network Trace - Config/Widget Area Name = Summary panel

The label you use for Area output becomes the summary panel title.  Can we set the summary panel settings somewhere else?  Maybe have a section for the summary panel where the user can chose the name?

@MikeMillerGIS We can place the display text for Summary panel at either of the following two places:

In Others panel of configuration UI
In NLS file of widget

Please confirm

NLS file is fine.

@MikeMillerGIS We have implemented this in V0.3

verified


Minimap (in SoD)

Hi, this happens all the time.

disabling -> reload -> fixed -> a few reloads later -> broken again
Scale 1.1
X -25
Y -205

I think you are using LeatrixPlus.
Just deactivate 'Enhance Minimap'.

Bistn Gott ;D
Gutes Addon ;)

Bistn Gott ;D
Gutes Addon ;)


harfbuzz: 3.3.2 -> 4.0.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/harfbuzz/harfbuzz/releases.
meta.description for harfbuzz is: "An OpenType text shaping engine"
meta.homepage for harfbuzz is: "https://harfbuzz.github.io/"
meta.changelog for harfbuzz is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

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

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

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

found 4.0.1 with grep in /nix/store/6sajnfam02974lg742i06889y0rvbr99-harfbuzz-4.0.1

found 4.0.1 in filename of file in /nix/store/6sajnfam02974lg742i06889y0rvbr99-harfbuzz-4.0.1

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

11631 total rebuild path(s)

8958 package rebuild(s)

8939 x86_64-linux rebuild(s)
2692 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
AusweisApp2
CHOWTapeModel
ChowCentaur
ChowKick
CuboCore.coreaction
CuboCore.corearchiver
CuboCore.corefm
CuboCore.coregarage
CuboCore.corehunt
CuboCore.coreimage
CuboCore.coreinfo
CuboCore.corekeyboard
CuboCore.corepad
CuboCore.corepaint
CuboCore.corepdf
CuboCore.corepins
CuboCore.corerenamer
CuboCore.coreshot
CuboCore.corestats
CuboCore.corestuff
CuboCore.coreterminal
CuboCore.coretime
CuboCore.coretoppings
CuboCore.coreuniverse
CuboCore.libcprime
CuboCore.libcsys
DisnixWebService
HentaiAtHome
MIDIVisualizer
OSCAR
PageEdit
R
SDL2
SDL2_gfx
SDL2_image
SDL2_mixer
SDL2_net
SDL2_ttf
SDL2_ttf_2_0_15
SDL_Pango
SDL_gpu
SDL_mixer
Sylk
_1oom
_1password-gui
_20kly
_7kaa
_90secondportraits
abbaye-des-morts
abcl

Instructions to test this update (click to expand)

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

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

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

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @edolstra for testing.

4.0.1, 4.1.0 and 4.2.0 were released in the meantime

Opened https://github.com/NixOS/nixpkgs/pull/182616


Telemetry and Insight ignore telemetry options (spyworks)

VS Code Version: 1.53.2
OS Version: Win10x64

Steps to Reproduce:

Set up any proxy monitor/intercepter
Launch VSCode with proxy settings
Observe Telemetry/Insights/Recommendations (whatever buzzword MS calls it now just to diminish the issue) related connections that should NOT be there

Does this issue occur when all extensions are disabled?: Yes/No
YES.
Settings
"workbench.settings.enableNaturalLanguageSearch": false,
"update.showReleaseNotes": false,
"json.schemaDownload.enable": false,
"extensions.autoCheckUpdates": false,
"extensions.showRecommendationsOnlyOnDemand": true,
"telemetry.enableCrashReporter": false,
"telemetry.enableTelemetry": false,
"code-runner.enableAppInsights": false,
"update.channel": "none",
"update.mode":"none",
"extensions.autoUpdate": false,
"extensions.ignoreRecommendations": true,
"settingsSync.ignoredExtensions": [
    "*.*",
],
"workbench.enableExperiments": false,

chrmarti removed their assignment 2 hours ago
I see nobody wants to hold an answer for hideous direction from the MS top office about how we can insert more telemetry user data fathering that is not governed by "telemetry" options because we call it something else. I mean, A/B testing with unique user id is not telemetry, right? So we can easily send whatever, why bother trying to explain ourselves to a user?

@Kein Your screenshot is quite useful here actually in diagnosing this issue. Last month, I explicitly addressed this issue for VS Code core, no telemetry means disabling everything about experiments. Unfortunately, the extensions use a slightly different module that needs to be updated to reflect this change. Note that we are still not sending any telemetry back, we are just requesting the list of experiments. However, that said, I will get this change in ASAP.

@bamurtaugh @aeschli when the experiments module is updated, please update the extensions consuming it

@sbatten
Hopefully this fix wont end up as empty as
#104293
#103159
#115818

Note that we are still not sending any telemetry back

When normal users people say telemetry, they dont actually mean THE classic definition of telemetry, because both Google, MS and other big corpos diluted the meaning of this definition over the years with their corporate bullspeak.  So whey they say "telemetry" they talk about all user data that can be used to identify and/or track a user. Unique ID, taking place in that screenshot of a log - is part of said data.

@Kein I am not sure what you mean by "empty" regarding the linked issues. Those issues resulted in actual code change to prevent the ping you talk about from core vs code. This issue will be tracked to resolve the same issue for extensions.

@sbatten I updated remote-wsl-recommender & remote-wsl to use<EMAIL_ADDRESS>and added code to observe workbench.enableExperiments.

@aeschli very cool, thanks, this will resolve the issue from OP, but I will leave this issue as a reminder to ping when vscode-tas-client is updated to do telemetry disablement detection automatically

looks like we can close this issue now as the clients are up to date


Infinite loop getting request.user

Django DataDog Logger version: 0.3.3
Python version: 3.8
Operating System: Ubuntu

Description
DataDogJSONFormatter accesses wsgi_request.user which can result in a SuspiciousOperation (checking hash from session data). Django tries to log this, which results in DataDogJSONFormatter being called and the loop begins again.
I believe this happened because the SECRET_KEY for my project changed - definitely an edge case and something that can be handled by removing sessions from DB. However, I think it's worthwhile looking into a way to prevent things which are logged during DataDogJSONFormatter.json_record calls from causing an infinite loop.
What I Did
Log in to a Django app in the browser, change settings.SECRET_KEY attempt to access via the browser again.

@jake-nz Thanks for the bug report including the mechanism to reproduce it. I will find a workaround for this situation, I've just been overwhelmed with higher priority tasks in the past few days.

Fixed in 0.3.5


[BUG] Star wars connector Page is wrong case for all "Get all" requests

Type of Connector
Independent Publisher Connector
Name of Connector
Star Wars
Describe the bug
It looks like the star wars flow connector uses Page(uppercase P) as a query parameter but, API expects it to be lowercase page and urls are case sensitive
For Example:
https://github.com/microsoft/PowerPlatformConnectors/blob/1add4c2e55b3f09acac51ba53d0c948baa91d9ab/independent-publisher-connectors/Star Wars/apiDefinition.swagger.json#L272
This would be for all the parameters that accept page, People, Species, Planets, and Films
Is this a security bug?
No, this is not a security bug
What is the severity of this bug?
Severity 3 - Minor issue
To Reproduce
Create flow that grabs page 1 and page 2 of the any of the "Get All" endpoints(People, Species, Planets, or Films)
Both results are identical, it is not changing the page
You can see it in the "next page" url, it has both cases in the url(the Uppercase
https://swapi.dev/api/people/?Page=5&page=1
Expected behavior
Use lowercase page, this is the only one supported by the endpoint
Environment summary
Production Power Automate workspace
Additional context
None

@Intellemerc Thanks for your contibution in this repository. I have replaced uppercase with lower case P. I haven't tested swagger file but you can see change I made here #1628

Thank you @Intellemerc for reporting this issue and @last72 for quickly taking a look and submitting a fix! :)