[BUG] ParseDateTimeSuite UT failed

Describe the bug
mvn  -Dbuildver=302 clean package -DwildcardSuites=com.nvidia.spark.rapids.ParseDateTimeSuite
mvn  -Dbuildver=312 clean package -DwildcardSuites=com.nvidia.spark.rapids.ParseDateTimeSuite
ParseDateTimeSuite:
- to_date dd/MM/yy (fall back)
- to_date yyyy-MM-dd *** FAILED ***
  Mismatch between CPU and GPU for the following rows:

  [#40] CPU: [1999-12-29
  ,null]
  [#40] GPU: [1999-12-29
  ,1999-12-29] (ParseDateTimeSuite.scala:302)
- to_date yyyy-MM-dd LEGACY
- to_date yyyy/MM/dd LEGACY
- to_date dd/MM/yyyy
- to_date dd/MM/yyyy LEGACY
- to_date parse date
- to_date parse timestamp
- to_timestamp yyyy-MM-dd *** FAILED ***
  Mismatch between CPU and GPU for the following rows:

  [#35] CPU: [1999-12-29
  ,null]
  [#35] GPU: [1999-12-29
  ,1999-12-29 00:00:00.0] (ParseDateTimeSuite.scala:302)
- to_timestamp dd/MM/yyyy
- to_date default pattern
- unix_timestamp parse date *** FAILED ***
  Mismatch between CPU and GPU for the following rows:

  [#35] CPU: [1999-12-29
  ,null]
  [#35] GPU: [1999-12-29
  ,946425600] (ParseDateTimeSuite.scala:302)

This appears to be for 22.02.0-SNAPSHOT and is not failing on 21.12

the failure here is caused when there is a newline in the string:
val ts = Seq("1999-12-29\n")

I am not positive on this but this commit is dealing with newline and is about the time our test started to fail:
https://github.com/rapidsai/cudf/commit/c1bfb26715e0234f6d90aceac7a52caded2e9f9e
https://github.com/rapidsai/cudf/issues/9620
I will verify

so I confirmed that reverting 6dc7b1d16f0eecdc2f932a6f9b94af630db534c5  - Fix regex non-multiline EOL/$ matching strings ending with a new-line (#9715)
make the behavior go back and the test passes

cudf issue: https://github.com/rapidsai/cudf/issues/9764

PR up to temporarily disable the tests, they need to be re-enabled when cudf is fixed

We should be able to re-enable these tests now.


Added back hack from our vendored version of js-debug under goval/nix…

…/dapNode
Why?
After some investigation, I found that this workaround for calling the onInitialize method of the debugAdapter exists in our vendored version of js-debug in https://github.com/replit/goval/tree/main/nix/dapNode but it does not exist in upstream.
Change
Add this change to our fork, after syncing the code to upstream.
Testing

npm i
npx gulp
npx gulp debugServerMain:webpack-bundle
It should start up and print a message

Yeah, I'd like to dig deeper later.


Support minification

The dependency injection breaks when you minify the file. I believe the minified file included in the build  directory is also broken.

I've a pull request ready that fixes the minification:
https://github.com/AlbertBrand/angular-cancel-on-navigate/pull/7


Pause timer in "Timesheet" hides timer and doesn't pause the count up.

Thanks for letting me know. I'll fix asap

@chrstnsmthng I do not experience this. The "pause" timer is actually a "stop" and when you continue it will resume tracking the current time.
I believe you expected it to track running time instead of start / end time?
This is a feature I am planning to implement.

Yep, running time and thanks for the update!

Cool! It has been put in the backlog, will let you know when it's implemented.


consolidations, withdrawals: output request type

This changes the contracts to add the request type into the output buffer.

Note the type is not added into the log data.

Needs some more updates to the tests. It's going to need a lot of changes to the consolidations tests.

Closing in favor of #25


add calibration

Mostly auto-generated. I just would like to test it against a real system before I merge it (see this issue).


Verify extension

See https://code.visualstudio.com/api/working-with-extensions/publishing-extension#verify-a-publisher
I guess we should do it under the nomic.foundation domain.

We are now showing up as a verified publisher again:


Handle synchronizing empty folders

Tested fix for #1139
Retains the current behaviour for folders with negative message counts.

:+1: for the fix and tests
But the tests are a bit hard to read. Here's what I came up with: https://github.com/k9mail/k-9/compare/empty_folders_fix
A couple of notes about testing in K-9 Mail:

I like to write tests in an 'arrange, act, assert' fashion and use empty lines to separate the different stages.
I'm open to changing the naming scheme of tests, but we should aim for some consistency.
Android Studio names the generated 'before' and 'after' methods "setUp" and "tearDown". Again, for consistency reasons I think we should stick to that.

Notes about these tests in particular:

With unit test we should try to aim for testing only one thing. That's why I called synchronizeMailboxSynchronous() directly. That way we don't also test the threading code.
I changed the assert stage to check if the correct listener methods have been called. Setting the folder status is more or less a hidden side-effect I want to get rid of rather sooner than later. Not checking for that means we don't have to update the tests when we change the error reporting mechanism.

Yeah I was trying to avoid changing the visibility of the methods (even with that annotation, which I haven't really seen before) and altering the threading model. I'm happy to go down that route (though I think putting the annotation on a lot (which is what this class really needs to be well tested) is probably a code smell).
In terms of the folder status, I tested it because I wanted it to work as is rather than as we want it to be. If a test fails because you make a change to behaviour I don't see that as a bad thing - it depends on the timescale as to whether it's more of an annoyance than a gain though.
I also considered a different solution of extracting the executor section entirely, so that you could mock the executor section. Again more work for this one fix, possibly better in terms of health of the code base.

Yeah I was trying to avoid changing the visibility of the methods (even with that annotation, which I haven't really seen before) and altering the threading model. I'm happy to go down that route (though I think putting the annotation on a lot (which is what this class really needs to be well tested) is probably a code smell).

It kind of is a code smell. But that's mostly because MessagingController is a horrible class. It will probably require quite a few visibility changes to make it testable. But once we have decent test coverage we dramatically increase the chance that we don't break the current functionality when transforming MessagingController into something sane. However, that's a job for another day.

If a test fails because you make a change to behaviour I don't see that as a bad thing

True. I guess the idea was more to test important functionality first, minor side effects later.

I actually had a crack at reworking the ridiculously long method into sub-methods as well in a separate commit ( https://github.com/philipwhiuk/k-9/commit/574b8f80c5fe335530338738e58b769b82632219 - my master branch is very experimental). and yes I think I broke something as I've had a few lock-ups while synching messages since. So I need to go back and do it in a TDD-like fashion.
For now I guess we can take the code smell and merge your commit. I'll probably finish off the List-Post stuff and then probably try and get back to it.

Cleaned up history and code. Merged. d93a7de36706dcfa62e45c63f9bd7603c7528fef


fixed segfault on close, request timer on macOS standalone

followed on from this PR with just the relevant commit (sorry!)

There's actually a much cleaner way to do the lifetime stuff I think - trying it now

I know from discord you are still thinking about shutdown path. I’m fine to merge this and it’s great but will hold until tomorrow to confirm - let me know if it’s ready

From what I can gather, the NSWindow will always clean itself up on close - so I think we can totally skip the cleanup in applicationWillTerminate - let me give this a try in a couple of hours, I'll see if anything alarming happens, and if not I'll do another push!

I mentioned in the Discord as well, but seems fine removing the [window release] stuff, and it's not crashing etc - I'm happy to sign off on this one unless there's anything you'd like me to change!

Fantastic! Merged!


[Snyk] Upgrade @aws-sdk/client-cognito-identity from 3.46.0 to 3.470.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @aws-sdk/client-cognito-identity from 3.46.0 to 3.470.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 221 versions ahead of your current version.
The recommended version was released 24 days ago, on 2023-12-08.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Regular Expression Denial of Service (ReDoS) SNYK-JS-FASTXMLPARSER-5668858
124/1000  Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00044, Social Trends: No, Days since published: 208, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.06, Score Version: V5
No Known Exploit

Prototype Pollution SNYK-JS-FASTXMLPARSER-3325616
124/1000  Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00044, Social Trends: No, Days since published: 208, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.06, Score Version: V5
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: @aws-sdk/client-cognito-identity

3.470.0 - 2023-12-083.470.0(2023-12-08)
Chores

codegen:  sync with Smithy update (#5556) (2121fd54)

New Features

client-finspace:  Releasing Scaling Group, Dataview, and Volume APIs (f18d4efb)
client-ec2:  M2 Mac instances are built on Apple M2 Mac mini computers. I4i instances are powered by 3rd generation Intel Xeon Scalable processors. C7i compute optimized, M7i general purpose and R7i memory optimized instances are powered by custom 4th Generation Intel Xeon Scalable processors. (1a9fca9e)
client-cloudwatch:  Adds support for the OpenTelemetry 1.0 output format in CloudWatch Metric Streams. (349863d8)

Bug Fixes

client-workspaces-thin-client:  add compatibility alias (#5555) (b0756b9a)

For list of updated packages, view updated-packages.md in assets-3.470.0.zip

3.468.0 - 2023-12-063.468.0(2023-12-06)
Chores

update smithyVersion and smithy hash (#5543) (6d10bffe)

Documentation Changes

client-comprehend:  Documentation updates for Trust and Safety features. (2a70f0ca)

New Features

client-backup:  AWS Backup - Features: Add VaultType to the output of DescribeRecoveryPoint, ListRecoveryPointByBackupVault API and add ResourceType to the input of ListRestoreJobs API (f1f4163d)
client-ec2:  Releasing the new cpuManufacturer attribute within the DescribeInstanceTypes API response which notifies our customers with information on who the Manufacturer is for the processor attached to the instance, for example: Intel. (35fbeb84)
client-payment-cryptography:  AWS Payment Cryptography IPEK feature release (6e117d11)
client-connect:  Releasing Tagging Support for Instance Management APIS (8c5845d7)

For list of updated packages, view updated-packages.md in assets-3.468.0.zip

3.465.0 - 2023-12-013.465.0(2023-12-01)
Chores

remove typedoc (#5532) (9052f984)
create smithy link/unlink in Makefile (#5535) (668c35bd)

New Features

client-verifiedpermissions:  Adds description field to PolicyStore API's and namespaces field to GetSchema. (87207b4f)
client-qconnect:  This release adds the PutFeedback API and allows providing feedback against the specified assistant for the specified target. (93a1fe5f)
client-rbin:  Added resource identifier in the output and updated error handling. (b960b656)
xhr-http-handler:  add static factory method for XHR handler (#5534) (484d1ecd)

Tests

middleware-sdk-s3:  use consistent timestamp in unit test (#5536) (9e3bde93)

For list of updated packages, view updated-packages.md in assets-3.465.0.zip

3.462.0 - 2023-11-29

3.461.0 - 2023-11-28

3.460.0 - 2023-11-28

3.458.0 - 2023-11-27

3.454.0 - 2023-11-17

3.451.0 - 2023-11-14

3.450.0 - 2023-11-13

3.449.0 - 2023-11-10

3.445.0 - 2023-11-07

3.444.0 - 2023-11-06

3.441.0 - 2023-11-01

3.438.0 - 2023-10-27

3.437.0 - 2023-10-26

3.436.0 - 2023-10-25

3.435.0 - 2023-10-24

3.433.0 - 2023-10-20

3.431.0 - 2023-10-18

3.430.0 - 2023-10-17

3.429.0 - 2023-10-16

3.428.0 - 2023-10-12

3.427.0 - 2023-10-06

3.425.0 - 2023-10-04

3.423.0 - 2023-10-02

3.421.0 - 2023-09-27

3.418.0 - 2023-09-22

3.414.0 - 2023-09-15

3.413.0 - 2023-09-14

3.410.0 - 2023-09-11

3.409.0 - 2023-09-08

3.408.0 - 2023-09-07

3.405.0 - 2023-09-01

3.398.0 - 2023-08-23

3.397.0 - 2023-08-22

3.395.0 - 2023-08-18

3.391.0 - 2023-08-14

3.388.0 - 2023-08-09

3.387.0 - 2023-08-08

3.386.0 - 2023-08-07

3.385.0 - 2023-08-04

3.382.0 - 2023-08-01

3.379.1 - 2023-07-28

3.378.0 - 2023-07-26

3.377.0 - 2023-07-25

3.370.0 - 2023-07-13

3.369.0 - 2023-07-11

3.363.0 - 2023-06-29

3.362.0 - 2023-06-28

3.360.0 - 2023-06-26

3.359.0 - 2023-06-23

3.358.0 - 2023-06-22

3.357.0 - 2023-06-21

3.354.0 - 2023-06-16

3.353.0 - 2023-06-15

3.352.0 - 2023-06-13

3.350.0 - 2023-06-09

3.348.0 - 2023-06-07

3.347.1 - 2023-06-07

3.347.0 - 2023-06-06

3.345.0 - 2023-06-02

3.344.0 - 2023-06-01

3.342.0 - 2023-05-30

3.341.0 - 2023-05-26

3.338.0 - 2023-05-23

3.337.0 - 2023-05-22

3.335.0 - 2023-05-18

3.332.0 - 2023-05-11

3.329.0 - 2023-05-08

3.328.0 - 2023-05-05

3.327.0 - 2023-05-04

3.326.0 - 2023-05-03

3.325.0 - 2023-05-02

3.321.1 - 2023-04-27

3.319.0 - 2023-04-24

3.316.0 - 2023-04-19

3.315.0 - 2023-04-17

3.312.0 - 2023-04-12

3.310.0 - 2023-04-10

3.309.0 - 2023-04-07

3.306.0 - 2023-04-04

3.303.0 - 2023-03-30

3.301.0 - 2023-03-28

3.300.0 - 2023-03-27

3.299.0 - 2023-03-24

3.298.0 - 2023-03-23

3.297.0 - 2023-03-22

3.296.0 - 2023-03-21

3.295.0 - 2023-03-20

3.294.0 - 2023-03-17

3.293.0 - 2023-03-16

3.292.0 - 2023-03-15

3.291.0 - 2023-03-14

3.290.0 - 2023-03-13

3.289.0 - 2023-03-10

3.288.0 - 2023-03-09

3.287.0 - 2023-03-08

3.282.0 - 2023-03-01

3.281.0 - 2023-02-28

3.279.0 - 2023-02-24

3.278.0 - 2023-02-23

3.276.0 - 2023-02-21

3.272.0 - 2023-02-15

3.271.0 - 2023-02-14

3.267.0 - 2023-02-08

3.266.1 - 2023-02-07

3.266.0 - 2023-02-06

3.264.0 - 2023-02-02

3.263.0 - 2023-02-01

3.262.0 - 2023-01-31

3.261.0 - 2023-01-30

3.259.0 - 2023-01-26

3.258.0 - 2023-01-25

3.257.0 - 2023-01-24

3.256.0 - 2023-01-23

3.254.0 - 2023-01-19

3.252.0 - 2023-01-17

3.245.0 - 2023-01-05

3.241.0 - 2022-12-29

3.238.0 - 2022-12-23

3.236.0 - 2022-12-21

3.235.0 - 2022-12-20

3.234.0 - 2022-12-19

3.231.0 - 2022-12-14

3.229.0 - 2022-12-12

3.226.0 - 2022-12-07

3.224.0 - 2022-12-05

3.223.0 - 2022-12-02

3.222.0 - 2022-12-01

3.218.0 - 2022-11-28

3.216.0 - 2022-11-22

3.215.0 - 2022-11-21

3.213.0 - 2022-11-17

3.212.0 - 2022-11-16

3.211.0 - 2022-11-15

3.210.0 - 2022-11-14

3.209.0 - 2022-11-11

3.208.0 - 2022-11-10

3.204.0 - 2022-11-04

3.202.0 - 2022-11-02

3.201.0 - 2022-11-01

3.200.0 - 2022-10-31

3.199.0 - 2022-10-28

3.198.0 - 2022-10-27

3.197.0 - 2022-10-26

3.196.0 - 2022-10-25

3.195.0 - 2022-10-24

3.194.0 - 2022-10-21

3.193.0 - 2022-10-20

3.192.0 - 2022-10-19

3.190.0 - 2022-10-17

3.188.0 - 2022-10-13

3.186.0 - 2022-10-06

3.185.0 - 2022-10-05

3.183.0 - 2022-10-03

3.181.0 - 2022-09-29

3.180.0 - 2022-09-27

3.179.0 - 2022-09-26

3.178.0 - 2022-09-23

3.171.0 - 2022-09-14

3.170.0 - 2022-09-13

3.169.0 - 2022-09-12

3.168.0 - 2022-09-09

3.165.0 - 2022-09-06

3.163.0 - 2022-09-01

3.162.0 - 2022-08-31

3.161.0 - 2022-08-30

3.160.0 - 2022-08-29

3.159.0 - 2022-08-26

3.157.0 - 2022-08-24

3.154.0 - 2022-08-19

3.150.0 - 2022-08-15

3.145.0 - 2022-08-08

3.142.0 - 2022-08-02

3.141.0 - 2022-08-01

3.137.0 - 2022-07-26

3.131.0 - 2022-07-15

3.130.0 - 2022-07-14

3.128.0 - 2022-07-12

3.127.0 - 2022-07-11

3.121.0 - 2022-06-30

3.118.1 - 2022-06-27

3.118.0 - 2022-06-24

3.112.0 - 2022-06-16

3.110.0 - 2022-06-14

3.109.0 - 2022-06-13

3.107.0 - 2022-06-08

3.105.0 - 2022-06-06

3.100.0 - 2022-05-26

3.99.0 - 2022-05-25

3.95.0 - 2022-05-19

3.94.0 - 2022-05-18

3.92.0 - 2022-05-16

3.87.0 - 2022-05-09

3.85.0 - 2022-05-05

3.82.0 - 2022-05-02

3.81.0 - 2022-04-29

3.80.0 - 2022-04-28

3.79.0 - 2022-04-27

3.78.0 - 2022-04-26

3.76.0 - 2022-04-22

3.75.0 - 2022-04-21

3.74.0 - 2022-04-20

3.72.0 - 2022-04-15

3.67.0 - 2022-04-08

3.58.0 - 2022-03-28

3.56.0 - 2022-03-24

3.55.0 - 2022-03-22

3.54.2 - 2023-06-12

3.54.1 - 2022-03-16

3.54.0 - 2022-03-11

3.53.0 - 2022-02-25

3.52.0 - 2022-02-18

3.51.0 - 2022-02-12

3.50.0 - 2022-02-08

3.49.0 - 2022-01-29

3.48.0 - 2022-01-22

3.47.2 - 2022-01-21

3.47.1 - 2022-01-20

3.47.0 - 2022-01-15

3.46.0 - 2022-01-07

    from @aws-sdk/client-cognito-identity GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
xiaohailimao, @dagelf, @chiorji, @enuoCM, @shihabdz, @, @gabisajr, @huangkaiqiao, @Flexdat, @tiagoduarte, @w0x0021, @jeremySvanostrand, @courage-liberty, @Jerryrbrn5, @Dankyybomb1, @Mehdish1, @fengmm521, @tenondecrpc, @atong007, @bishop45690


Add tests for Vector2/Vector2i/Vector3/Vector3i

This PR adds some tests for Vector2, Vector2i, Vector3, and Vector3i.

Since the prerequisite PRs have been merged, these tests are now ready for review.

Thanks!


Make fmt header-only by default

Allows user to define preferred fmt target using UMPIRE_FMT_TARGET variable.

Is there a good way to test the various supported fmt external vs. submodule combinations? @adayton1 will you check your use case?

Is there a good way to test the various supported fmt external vs. submodule combinations? @adayton1 will you check your use case?
Does/should Umpire have a build_with_cmake test for each case, submodule and external fmt?

Umpire has a `

My bad, clicked the wrong button.

I'll update the Dockerfile so we have an Azure build that tests the install against the submodule.

This is ready to go!


Video previews not loading - causes failed login attempt

I have a basic card set up:
- type: custom:frigate-card
  cameras:
    - camera_entity: camera.front
      live_provider: ha
      frigate:
        url: https://<my_domain>/ccab4aaf_frigate-proxy/dashboard
  menu:
    style: outside

Whenever I try to look at clips or snapshots, the icons fail to load, and I get this notification in Home Assistant:

Please hold down your Frigate menu button and paste the resulting diagnostics here.
Does Frigate work otherwise? When you use the HA media browser (not the card), can you see Frigate media?

Please hold down your Frigate menu button in the card and paste the resulting diagnostics here.
Does Frigate work otherwise? When you use the HA media browser (not the card), can you see Frigate media?

I have the same issue.  Frigate media is unavailable and causes hundreds of IP Bans when I try to access.
Holding down the Frigate menu button to get diagnostics does nothing... maybe it's due to my card's button configuration?

@wvdeadhead Is it possible you're using an old card version? The current version is v4.0.0. Current version of the integration is v3.0.0. Make sure both are up to date and in sync. Your lack of diagnostics support, and the actual problem, might be related ;-)

@wvdeadhead Is it possible you're using an old card version? The current version is v4.0.0. Current version of the integration is v3.0.0. Make sure both are up to date and in sync. Your lack of diagnostics support, and the actual problem, might be related ;-)

Thanks for the follow-up.  Both the integration and card are installed via HACS and confirmed to be on the latest versions.

@wvdeadhead Hmm. Then I can't tell why diagnostics don't work. Can you paste your card configuration?

@wvdeadhead Hmm. Then I can't tell why diagnostics don't work. Can you paste your card configuration?

Sure thing.  This is the config I had tried.  Maybe I mis-configured?
       - type: custom:frigate-card          cameras:            - camera_entity: camera.backyard              live_provider: webrtc-card              webrtc_card:                entity: camera.backyard_rtsp          live:            controls:              thumbnails:                mode: below                size: 100px                media: clips            preload: true            webrtc_card:              ui: true

I think I found the issue.

Browser cache
Removing the "px" from the thumbnails size.

All is working as expected now... including diagnostics.

Thanks @wvdeadhead , glad you got it figured out.
@sjoshua270 Any development on your end? If not, would you mind following these instructions to provide more information?

It looks like it may have been cache for me, as well.
I had restarted Home Assistant and was not able to show diagnostic output.
I tried on a new machine, and all my settings were applied with no issues.
Today, my mobile app is updated as well.
Thanks for the prompt help! I honestly got busy and forgot to check on this
issue, since it was minor for me.  Didn't realize I was using a cached
3.0.0 😂
On Mon, Oct 17, 2022, 10:43 AM Dermot Duffy @.***>
wrote:

Thanks @wvdeadhead https://github.com/wvdeadhead , glad you got it
figured out.
@sjoshua270 https://github.com/sjoshua270 Any development on your end?
If not, would you mind following these instructions
https://github.com/dermotduffy/frigate-hass-card/issues/872#issuecomment-1279827353
to provide more information?
—
Reply to this email directly, view it on GitHub
https://github.com/dermotduffy/frigate-hass-card/issues/872#issuecomment-1280976936,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXFJ2GBHQU4O7LCQQ3ABLTWDVQZBANCNFSM6AAAAAARGBHC4A
.
You are receiving this because you were mentioned.Message ID:
@.***>

Great. Thank you both, I'll close this bug then.


Refactor SD3

SD3 Cleanup

Removed duplicate code function in SD3 which can be inherited
Added default scheduler in text-to-image sample (SD3 uses default FlowMatchEulerDiscreteScheduler)

@regisss this is the code cleanup PR as discussed in #1153.  I also forgot to add default option for scheduler selection which is needed for SD3 so I added it in this PR

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Tokens impacted by policy

Quick question, in this doc it's specified that when claimtype  jwt is specified it applies to the jwt token.  Does a claim mapping policy add the mapped claim to the access token, the id token or both as both are jwt's?

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

ID: 195c79a3-ccc5-8c6a-233e-95e344a9b4df
Version Independent ID: 401c7557-5817-bbd3-5bd8-8c97ef5a28cc
Content: Customize claims emitted in tokens for a specific app in an Azure AD tenant (Public Preview)
Content Source: articles/active-directory/develop/active-directory-claims-mapping.md
Service: active-directory
GitHub Login: @CelesteDG
Microsoft Alias: celested

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

"Claim Type: The JwtClaimType and SamlClaimType elements define which claim this claim schema entry refers to."
The JwtClaimType, then, would include both access tokens and id tokens since they are both JWTs like you mentioned.

Hope this helps! If you have further questions or if this isn't the answer you were looking for, feel free to reach out to me on MSDN and I will gladly continue the discussion. https://social.msdn.microsoft.com/Forums/en-US/home?forum=WindowsAzureAD


Problem with version suffixes

Hi,
I have two repositories on github with terraform modules :

technical module (monorepo with all technical terraform modules)

technical-module-a
technical-module-b

terraform-myapp-module which reference severals technical modules.

module "myApp1" {
source = "github.com/bogaertg/terraform-technical-module//technical-module-a?ref=v1.0.0-technical-module-a"
}

module "myApp2" {
source = "github.com/bogaertg/terraform-technical-module//technical-module-b?ref=v1.0.0-technical-module-b"
}

I release technical modules with suffix (each different for module) :
Ex :   X.Y.Z-technical-module-a | X.Y.Z-technical-module-b
I have dependabot enabled on terraform-myapp-module. Dependabot suggest to update :

Bump myApp2 from 1.0.0-technical-module-b to 1.1.0-technical-module-b in /app
Bump myApp1 from 1.0.0-technical-module-a to 1.1.0-technical-module-b in /app

I wouldlike dependabot check new version against a pattern with fixed suffixed.

Bump myApp2 from X.Y.Z-technical-module-b to -technical-module-b in /app
Bump myApp1 from X.Y.Z-technical-module-a to -technical-module-a in /app

Regards,

up ?

up ?

👋 Sorry for the glacially slow response.
This issue is over two years old and there's been a lot of changes/improvements to the Dependabot support for Terraform since then... Are you still able to repro this?
My guess is that it's still an active issue and requires a fix similar to https://github.com/dependabot/dependabot-core/pull/5560


Cannot access memory at address 0x7fc2d4080230

code works well most of time, it appeared several times, so far.
the gdb core stack as below:

os：Red Hat Enterprise Linux Server release 6.4 (Santiago)
gcc version:4.6.3
hiredis version:0.13.3

Please post these things as text. Images are not searchable, copyable or easily read.
Also:

What code did you execute?
What did you expect to happen?
What happened instead?

I use hiredis in my project,It works fine in most of the time，but there are several times ，it hangs。
the gdb core stack as below:：
#0 redisBufferRead (c=0x7f26c4013a10) at hiredis.c:800
#1 0x00007f27479e9cd0 in redisGetReply (c=0x7f26c4013a10, reply=0x7f26ea4e7ea0) at hiredis.c:903
#2 0x00007f27479ea02b in __redisBlockForReply (c=0x7f26c4013a10, argc=, argv=,
argvlen=) at hiredis.c:1010
#3 redisCommandArgv (c=0x7f26c4013a10, argc=, argv=, argvlen=)
at hiredis.c:1035
#4 0x00007f27479d31cc in bfd::codis::CodisClient::RedisCommand (this=0x200ceb0, command=..., tt=0) at src/CodisClient.cpp:995
#5 0x00007f27479d3662 in bfd::codis::CodisClient::RedisCommand (this=0x200ceb0, command=..., tt=0) at src/CodisClient.cpp:1035
#6 0x00007f27479c9f64 in bfd::codis::CodisClient::get (this=0x200ceb0, key=..., tt=0) at src/CodisClient.cpp:152
#7 0x00007f27479e5a18 in bfd::codis::BfdCodis::get (this=0x2130120, key=..., tt=0) at src/BfdCodis.cpp:60
#8 0x000000000050d89e in RedisClientProxy::get (this=0x20e34f0, key=...)
(gdb) p c
$1 = {err = 0, errstr = '\000' , fd = 72, flags = 3, obuf = 0x7f26b40087c8 "", reader = 0x7f26c4013af0,
connection_type = REDIS_CONN_TCP, timeout = 0x0, tcp = {host = 0x7f26c4013d50 "192.168.*", source_addr = 0x0, port = 19000},
unix_sock = {path = 0x0}}
(gdb) p *buf
Cannot access memory at address 0x7f26ea4e3d80
os：Red Hat Enterprise Linux Server release 6.4 (Santiago)
gcc version:4.6.3
hiredis version:0.13.3

thanks or sorry，Maybe i am not express my situation，i use a demo work fine all the time which just use set/get command，but when it run on my application ，it hangs！i can't find there are any different between the demo and my application。maybe it is not the hiredis‘s issue，but i don't know what i can do for resolve it。’

See the first comment. I can't act without more info.
Also are you using the context object from multiple threads? If so, that is likely the fault.

as badboy mentioned, hiredis is not thread safe

Thanks，Maybe my code‘s fault，i will have a ’unit test to find the bug！Any progress，i would tell you here.


Issue with overlapping text in Android client

After updating to v5.3.0, I've noticed an issue where a user's name will overlap with the message they sent. I have reinstalled the client and the issues persists, so I am confident that it isn't a configuration issue. I am using a Samsung Galaxy S7 (SM-G930V) running Android 7.0.

same here #23071

:( trying to get my family over to Keybase from WhatsApp and several are having this same issue so it's a no-go for now


Historical Balance Tracking + Balance Pruning

This PR adds support for reconciling account balances using historical tracking. This significantly reduces the number of "skipped" reconciliations that occur.
To enable this new feature, we had to make a breaking change to how balances are stored. This means you will need to re-sync any data that relies on the modeling of <= v0.5.16.
Changelog

[x] Update to<EMAIL_ADDRESS>[x] Enable balance pruning
[x] Add support for custom backlog size using reconciler_active_backlog
[x] Fix balance exemption support

Pull Request Test Coverage Report for Build 5789

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.408%

Totals

Change from base Build 5744:
0.0%

Covered Lines:
186

Relevant Lines:
223

💛  - Coveralls


libinput-gestures: Add coreutils to $PATH

Motivation for this change
The script can't find stdbuf when run as a systemd service.
Things done
Add coreutils to the $PATH.

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build libinput-gestures


Fix test naming error with half and double (#340)

Fixes bug https://github.com/codeplaysoftware/sycl-blas/issues/340
Implements additional specializations of dump_args for double and cl::sycl::half.

A more general approach does not work well because the standard library does not work with with cl::sycl::half.

Tested on DPC++ / Linux for BLAS_DATA_TYPES=half;float;double.

c2214af changes the PR to use partial specialization of a helper struct. This improves the extensibility of the dump_arg functionality for complex types.


name added

Added my name to the list
Related issue

What changes does this PR do?
Screenshots (If any)
Questions

Given the length of time with no activity I will close. Feel free to raise a new Pull Request.


SpiBusDriver is not Send

Is there a reason why Send is implemented for SpiDeviceDriver and not for a SpiBusDriver? From the documentation there seems to be no difference between a SpiBusDriver without cs and a SpiBusDriver.

This should be fixed. PRs welco.e!
Backgroynd: All drivers should be Send but currently few (if any) are Sync. We can actually also do the latter too for most drivers because it turns out most esp idf APIs are thread safe.
But usually folks reaching out to Sync often means they might be doing something suboptimal, as in - say - trying to use the default tokio work-stealing executor, which is not ideal on embedded.

Still a workaround but should do it for most people is just sending the peripheral or the the wrapped SpiDriver as it is Send


Add protoc-gen-validate 1.0.4.bcr.2

This returns DefaultInfo in rules instead of a plain struct() (backports https://github.com/bufbuild/protoc-gen-validate/pull/1200).

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (protoc-gen-validate) have been updated in this PR. Please review the changes.

@bazel-io skip_check unstable_url


International addresses where the postcode is used as a 'known fact'

International addresses where the postcode is used as a 'known fact'
BSP Parcels
Overview
We have a number of technical requirements for international addresses:

the backend expects addresses in a format that is different from the GOV.UK recommended patterns. The pattern we have to use is:

Address line 1
Address line 2
Address line 3 (optional)
Address line 4 (optional)

we have to also collect a postcode as a 'known fact'. 63 countries don't have them, but we have to at least know which field the postcode should be in. Some other services have managed to not have this used as a known fact, but we can't.

We've found that just showing the fields to international users doesn't work.
This example is a first pass on what could be done to make this work. It's based on the assumption that:

Most international addresses don't need four lines
Users that need these extra fields will be used to this

This therefore hides the optional fields at first and shows a separate page to users that need the extra fields. This allows for more tailored content about what line 2 should be.

Is it useful and unique?
This is an extension of the address pattern.
It is useful for situations were users need to put in an international address and where the postcode is required for security reasons.
This pattern should not be used when it doesn't matter what line a postcode is in. Other services have a simpler pattern of just asking for 5 address lines.
Other components or patterns you've tried
The version that's common to ETMP patterns caused problems in usability testing with international users (see 'research on this pattern')

Research on this pattern
We've done testing on the earlier version of the pattern with:

5 users in the USA
5 French-native language users in France

Some US users expected to put something in line 4, not line 2.
French users only put in an address line and the postcode (not the town), so got an error when they tried to submit. They still didn't put a town in address line 2, but put in a different address or even random characters.
We haven't tested with any people yet whose countries don't have postcodes.

Would it be possible to ask for the country first?
If they are a country with a postal code, make it required. If they are not a country with a postal code, do not show the field.

This has led me to something else: at present there doesn't seem to be a definitive list of which countries don't have postcodes.
References I have found so far by asking around are:

http://www.upu.int/uploads/tx_sbdownloader/manualAddressingKnowledgeCentreGeneralIssuesEn_01.pdf - UPU list of all member countries. They also have ways to see formats for all their member countries at http://www.upu.int/en/activities/addressing/postal-addressing-systems-in-member-countries.html
https://www.loqate.com/en-gb/address-verification/international-address-formats/ has a way to check all formats
an informal list that someone recommended to me http://www.mapanet.eu/en/resources/Postal-Format.asp
another list, but with regexes https://www.grcdi.nl/gsb/world postal code formats.html
a list put on github as json https://gist.github.com/bradydan/e172c3f99e211e6e47ad84f08f83dfe3

There are also quirks such as Eirecodes (house level rather than street level), and Hong Kong having one code since the country is so small.
Universal Postal Union has a list but only for their countries (not every country is in the UPU)
Other references:

Schema.org on postal addresses https://schema.org/PostalAddress
ISO 19160 standard for address information https://www.iso.org/standard/64242.html and https://www.iso.org/obp/ui/#iso:std:iso:19160:-4:ed-1:v1:en

Thanks for this, @vickytnz. I wonder, are you aware of other services that share the same need as regards postcode as a "known fact"?


Convert a full namespace to a subns and to be children of another subns

I noticed that full namespaces can be children of subnamespaces by doing kubectl hns set staging --parent service-4, so if we need a way to convert a full namespace to a subnamespace and to be children of another subnamespace. just like:
team-a
├── [s] service-2
└── [s] service-4
     └── [s] staging

Why we need it?
In some scenarios, our cluster already have a lot of full namespaces, and then we wanna take over them by subnamespaces way.

I read codes and had a try that by two steps, I can take over full namespace as a subnamespace manually.

add annotations to full namespaces ns-1, example: hnc.x-k8s.io/subnamespace-of: team-a
create subnamespaceanchor with same name: kubectl hns create ns-1 -n team-a

Yes, that's the right way to solve this problem. Are you asking for a
change in behaviour? And why are you trying to convert a full namespace
into a subnamespace? Thanks!
On Thu, Apr 7, 2022 at 3:11 AM weilaaa @.***> wrote:

I read codes and had a try that by two steps, I can take over full
namespace as a subnamespace manually.

add annotations to full namespaces ns-1, example:
hnc.x-k8s.io/subnamespace-of: team-a
create subnamespaceanchor with same name: kubectl hns create ns-1
-n team-a

—
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-sigs/hierarchical-namespaces/issues/191#issuecomment-1091159228,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE43PZBG352NUV66XMCWEZDVD2DA7ANCNFSM5SYLHODQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

Yep, I'm asking for a behavior change. As I said in Why we need it, assumed that our k8s cluster already had a lot of full namespaces, and I want to take over them by subnamespaces way, cause I want the features of subnamespaces-deep-dive rather than using simple HierarchyConfiguration.

I'm willing to have a try if you think it alright.

Thanks for u answers. Everything works follow twos steps. By the way, can you easily reveal when the HA will be stable?

I think that in v1.1 (probably out in a month or two) we'll upgrade it to
"beta," which means that we think it should work but there might still be
some bugs or instability.
On Sat, Apr 23, 2022 at 11:14 AM weilaaa @.***> wrote:

Thanks for u answers. Everything works follow twos steps. By the way, can
you easily reveal when the HA will be stable?
—
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-sigs/hierarchical-namespaces/issues/191#issuecomment-1107518945,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE43PZDIPHIS2LR3URLYXWLVGQHU3ANCNFSM5SYLHODQ
.
You are receiving this because you commented.Message ID:
@.***>


BatchSplit hang at joint state when execute BatchSplit and move-hot-read-leader at same time

Bug Report

What version of TiKV are you using?

v6.5.9
What operating system and CPU are you using?

Steps to reproduce

Batchsplit was created when the raft was in a joint state due to TransferLeader.
The split will hang until pd triage the operator of "leave-joint-state".
Here are the tikv logs and pd logs.
[2024/09/24 19:19:45.210 +08:00] [INFO] [operator_controller.go:443] ["add operator"] [region-id=368266575] [operator="\"move-hot-read-leader {mv peer: store [1679158548] to [18]} (kind:hot-region,region,leader, region:368266575(212337, 576903), createAt:2024-09-24 19:19:45.208873645 +0800 CST m=+11111568.506147198, startAt:0001-01-01 00:00:00 +0000 UTC, currentStep:0, size:125, steps:[0:{add learner peer<PHONE_NUMBER> on store 18}, 1:{use joint consensus, promote learner peer<PHONE_NUMBER> on store 18 to voter, demote voter peer<PHONE_NUMBER> on store<PHONE_NUMBER> to learner}, 2:{transfer leader from store<PHONE_NUMBER> to store 18}, 3:{leave joint state, promote learner peer<PHONE_NUMBER> on store 18 to voter, demote voter peer<PHONE_NUMBER> on store<PHONE_NUMBER> to learner}, 4:{remove peer on store<PHONE_NUMBER>}]，timeout:[22m30s])\""] [additional-info=]
...
[2024/09/24 19:19:50.395 +08:00] [INFO] [apply.rs:1621] ["execute admin command"] [command="cmd_type: TransferLeader transfer_leader { peer { id:<PHONE_NUMBER> store_id: 18 role: IncomingVoter } }"] [index=89035270301] [term=64797] [peer_id=1755118766] [region_id=368266575]
[2024/09/24 19:19:50.395 +08:00] [INFO] [apply.rs:1621] ["execute admin command"] [command="cmd_type: BatchSplit splits { requests { split_key:<PHONE_NUMBER>00002AFF095F7289CDEBFD54FF514E200000000000FA new_region_id:<PHONE_NUMBER> new_peer_ids:<PHONE_NUMBER> new_peer_ids:<PHONE_NUMBER> new_peer_ids:<PHONE_NUMBER> new_peer_ids:<PHONE_NUMBER> } right_derive: true share_source_region_size: true }"] [index=89035270302] [term=64797] [peer_id=1755118766] [region_id=368266575]
[2024/09/24 19:19:50.395 +08:00] [INFO] [apply.rs:2482] ["    split region"] [keys="key<PHONE_NUMBER>00002AFF095F7289CDEBFD54FF514E200000000000FA"] [region="id: 368266575 start_key:<PHONE_NUMBER>00002AFF095F7289CDEBA413FF51561D0000000000FA end_key:<PHONE_NUMBER>00002AFF1C00000000000000F8 region_epoch { conf_ver: 576906 version: 212337 } peers { id:<PHONE_NUMBER> store_id: 32 } peers { id:<PHONE_NUMBER> store_id: 10 } peers { id:<PHONE_NUMBER> store_id:<PHONE_NUMBER> role: DemotingVoter } peers { id:<PHONE_NUMBER> store_id: 18 role: IncomingVoter }"] [peer_id=1755118766] [region_id=368266575]
[2024/09/24 19:19:50.396 +08:00] [INFO] [peer.rs:4150] ["insert new region"] [store_id=32] [is_uninitialized_peer_exist=false] [region="id:<PHONE_NUMBER> start_key:<PHONE_NUMBER>00002AFF095F7289CDEBA413FF51561D0000000000FA end_key:<PHONE_NUMBER>00002AFF095F7289CDEBFD54FF514E200000000000FA region_epoch { conf_ver: 576906 version: 212338 } peers { id:<PHONE_NUMBER> store_id: 32 } peers { id:<PHONE_NUMBER> store_id: 10 } peers { id:<PHONE_NUMBER> store_id:<PHONE_NUMBER> role: DemotingVoter } peers { id:<PHONE_NUMBER> store_id: 18 role: IncomingVoter }"] [region_id=1755178101]
[2024/09/24 19:19:50.396 +08:00] [INFO] [peer.rs:267] ["create peer"] [peer_id=1755178102] [region_id=1755178101]
[2024/09/24 19:19:50.396 +08:00] [INFO] [raft.rs:2660] ["switched to configuration"] [config="Configuration { voters: Configuration { incoming: Configuration { voters: {1755178105,<PHONE_NUMBER>,<PHONE_NUMBER>} }, outgoing: Configuration { voters: {1755178104,<PHONE_NUMBER>,<PHONE_NUMBER>} } }, learners: {}, learners_next: {1755178104}, auto_leave: false }"] [raft_id=1755178102] [region_id=1755178101]
[2024/09/24 19:19:50.396 +08:00] [INFO] [raft.rs:1127] ["became follower at term 5"] [term=5] [raft_id=1755178102] [region_id=1755178101]
[2024/09/24 19:19:50.396 +08:00] [INFO] [raft.rs:388] [newRaft] [peers="Configuration { incoming: Configuration { voters: {1755178105,<PHONE_NUMBER>,<PHONE_NUMBER>} }, outgoing: Configuration { voters: {1755178104,<PHONE_NUMBER>,<PHONE_NUMBER>} } }"] ["last term"=5] ["last index"=5] [applied=5] [commit=5] [term=5] [raft_id=1755178102] [region_id=1755178101]
[2024/09/24 19:19:50.396 +08:00] [INFO] [raw_node.rs:315] ["RawNode created with id<PHONE_NUMBER>."] [id=1755178102] [raft_id=1755178102] [region_id=1755178101]
...
[2024/09/24 19:20:01.406 +08:00] [INFO] [raft.rs:1581] ["[logterm: 5, index: 5, vote: 0] cast vote for<PHONE_NUMBER> [logterm: 5, index: 5] at term 5"] ["msg type"=MsgRequestPreVote] [term=5] [msg_index=5] [msg_term=5] [from=1755178105] [vote=0] [log_index=5] [log_term=5] [raft_id=1755178102] [region_id=1755178101]

pd logs:
[2024/09/24 19:19:50.395 +08:00] [INFO] [cluster_worker.go:145] ["alloc ids for region split"] [region-id=1755178101] [peer-ids="[1755178102,1755178103,1755178104,1755178105]"]
[2024/09/24 19:19:50.398 +08:00] [INFO] [operator_controller.go:556] ["operator finish"] [region-id=368266575] [takes=5.187803822s] [operator="\"move-hot-read-leader {mv peer: store [1679158548] to [18]} (kind:hot-region,region,leader, region:368266575(212337, 576903), createAt:2024-09-24 19:19:45.208873645 +0800 CST m=+11111568.506147198, startAt:2024-09-24 19:19:45.210858002 +0800 CST m=+11111568.508131561, currentStep:5, size:125, steps:[0:{add learner peer<PHONE_NUMBER> on store 18}, 1:{use joint consensus, promote learner peer<PHONE_NUMBER> on store 18 to voter, demote voter peer<PHONE_NUMBER> on store<PHONE_NUMBER> to learner}, 2:{transfer leader from store<PHONE_NUMBER> to store 18}, 3:{leave joint state, promote learner peer<PHONE_NUMBER> on store 18 to voter, demote voter peer<PHONE_NUMBER> on store<PHONE_NUMBER> to learner}, 4:{remove peer on store<PHONE_NUMBER>}]，timeout:[22m30s]) finished\""] [additional-info=]
...
[2024/09/24 19:20:01.415 +08:00] [INFO] [operator_controller.go:443] ["add operator"] [region-id=1755178101] [operator="\"leave-joint-state {promote peer: store [18]} (kind:unknown, region:1755178101(212338, 576906), createAt:2024-09-24 19:20:01.415300081 +0800 CST m=+11111584.712573633, startAt:0001-01-01 00:00:00 +0000 UTC, currentStep:0, size:1, steps:[0:{leave joint state, promote learner peer<PHONE_NUMBER> on store 18 to voter, demote voter peer<PHONE_NUMBER> on store<PHONE_NUMBER> to learner}]，timeout:[3m0s])\""] [additional-info=]
[2024/09/24 19:20:01.415 +08:00] [INFO] [operator_controller.go:642] ["send schedule command"] [region-id=1755178101] [step="leave joint state, promote learner peer<PHONE_NUMBER> on store 18 to voter, demote voter peer<PHONE_NUMBER> on store<PHONE_NUMBER> to learner"] [source=create]
[2024/09/24 19:20:01.416 +08:00] [INFO] [region.go:669] ["region ConfVer changed"] [region-id=1755178101] [detail="Remove peer:{id:1755178104 store_id:1679158548 role:DemotingVoter },Remove peer:{id:1755178105 store_id:18 role:IncomingVoter },Add peer:{id:1755178104 store_id:1679158548 role:Learner },Add peer:{id:1755178105 store_id:18 }"] [old-confver=576906] [new-confver=576908]
[2024/09/24 19:20:01.416 +08:00] [INFO] [operator_controller.go:556] ["operator finish"] [region-id=1755178101] [takes=1.136862ms] [operator="\"leave-joint-state {promote peer: store [18]} (kind:unknown, region:1755178101(212338, 576906), createAt:2024-09-24 19:20:01.415300081 +0800 CST m=+11111584.712573633, startAt:2024-09-24 19:20:01.415464006 +0800 CST m=+11111584.712737559, currentStep:1, size:1, steps:[0:{leave joint state, promote learner peer<PHONE_NUMBER> on store 18 to voter, demote voter peer<PHONE_NUMBER> on store<PHONE_NUMBER> to learner}]，timeout:[3m0s]) finished\""] [additional-info=

What did you expect?
Don't split the region if it in joint state or not hang.
What did happened?

/severity major

This is caused by https://github.com/tikv/tikv/issues/12410.

/report customer

@mayjiang0203 Could you please help check if this issue should be closed? https://github.com/tikv/tikv/pull/17846 should have been merged aleady.


Unhandled Runtime Error

I was trying out the nextjs-starter and I have been running into this error when I start the development server with yarn dev. There doesn't seem to be any error in the console.
This is the output:
ready - started server on <IP_ADDRESS>:8000, url: http://localhost:8000
info  - Loaded env from C:\Users\Acer\Desktop\Development\blogs-tut\medusa\my-medusa-storefront\.env.local
next.config.js {
  "reactStrictMode": true,
  "images": {
    "domains": [
      "medusa-public-images.s3.eu-west-1.amazonaws.com",
      "localhost"
    ]
  },
  "env": {}
}
event - compiled client and server successfully in 43.3s (1054 modules)
wait  - compiling...
event - compiled successfully in 442 ms (1011 modules)
wait  - compiling / (client and server)...
event - compiled client and server successfully in 5.9s (1645 modules)

But the problem is when I go to localhost:8000 to check it, this is the error I get:

Hi @AviAvinav, you most likely don't have a Medusa server running, or at least not on the port that the starter expects it to be.
If not then please share the failed request from your network tab, so we can better assist you 😄

Ah, alright it works now!


Bools often corrupt when written using Compact

Looks like if you have a bool in your struct and you're writing using Compact format, it's very likely the resulting message will be corrupt.  See attached testcase.
This occurs due to this piece of code -- the "else" clause does not write out the field ID.
    def write_bool(self, bool):
        if self._bool_fid and self._bool_fid > self._last_fid \
                and self._bool_fid - self._last_fid <= 15:
            if bool:
                ctype = CompactType.TRUE
            else:
                ctype = CompactType.FALSE
            self._write_field_header(ctype, self._bool_fid)
        else:
            if bool:
                self.write_byte(CompactType.TRUE)
            else:
                self.write_byte(CompactType.FALSE)

In a practical sense, this may occur if the last field ID written out is more than 15 IDs away, but consider this:

Fields are not necessarily written out in ID order (maybe that's a separate bug?)
If the previous fields were default values, then they are not written out at all -- thus do not contribute to the ID closeness required to not trigger the else clause.

corrupt_bool_testcase.txt

Modify it to 1: bool some_bool will fix it, I think it's not a bug


Replace setup.py with pyproject.toml

Modern python packages use a pyproject.toml file.
Use flit  as build system, because it is possible to get the version from a dynamic variable (useful when parsing from a tag)
[build-system]
requires = ["flit_core >=3.2"]
build-backend = "flit_core.buildapi"

it has been done in #111 for version 1


[WIP] Improve test cases coverage and stability

:white_check_mark: Build AElf <IP_ADDRESS>77 completed (commit https://github.com/AElfProject/AElf/commit/7587319341 by @EricBlack)

:x: Build AElf <IP_ADDRESS>81 failed (commit https://github.com/AElfProject/AElf/commit/556210d4c6 by @EricBlack)

:white_check_mark: Build AElf <IP_ADDRESS>92 completed (commit https://github.com/AElfProject/AElf/commit/f9405e1226 by @EricBlack)

:x: Build AElf <IP_ADDRESS>94 failed (commit https://github.com/AElfProject/AElf/commit/baaa5086c0 by @jason-hoopox)

:white_check_mark: Build AElf <IP_ADDRESS>39 completed (commit https://github.com/AElfProject/AElf/commit/4b22709a35 by @EricBlack)

:white_check_mark: Build AElf <IP_ADDRESS>45 completed (commit https://github.com/AElfProject/AElf/commit/c15bc25d8e by @EricBlack)

:white_check_mark: Build AElf <IP_ADDRESS>64 completed (commit https://github.com/AElfProject/AElf/commit/05ee38337c by @EricBlack)

:white_check_mark: Build AElf <IP_ADDRESS>72 completed (commit https://github.com/AElfProject/AElf/commit/bb6189afcb by @EricBlack)

:x: Build AElf <IP_ADDRESS>77 failed (commit https://github.com/AElfProject/AElf/commit/f438e88034 by @EricBlack)

:white_check_mark: Build AElf <IP_ADDRESS>00 completed (commit https://github.com/AElfProject/AElf/commit/de3fe16420 by @rosona)


20212501 change some stuff

wanted to fix more, but then I only fixed the dates of the schlachthof workshop...

I am so stupid, sorry guys...

I am so stupid, sorry guys...


Fix dummy app generation with Thor 1.0

Pass abort_on_failure option to explictly ignore failing rake db:drop command when no databases exist. Failures used to be ignored.
REDMINE-17780

Coverage remained the same at 99.208% when pulling 1ee7c0fcdaf3c117f196c46cff8f00c8c11a03f4 on tf:travis-fix into 219f5395e0c1c0c29e34ed39dc8250ee1f9776e7 on codevise:master.


Issue #89: agent for tracking unaligned memory accesses with buffers

as discussed in issue #89, check for unaligned accesses can be useful during development/testing but modifying the code is not an option since it can impact inlining. This agent should allow this check when required.
I modified the build.gradle file to generate a new artifact (with classifier 'agent') that contains only the agent classes. I wanted to use the shadow plugin to include bytebuddy  in the agent jar, however I didn't succeed to include it without including all other agrona classes or creating a multi-projects build
Any help or hint to improve the packaging is welcome

If a new module is created for the agent then the packaging should be cleaner. If you look at Aeron you can see how a module can be used.

I wanted to avoid switching to a multi-module build just for a debug feature, but if there is no other clean way to package it correctly, I will do the change.

@mjpt777 I did some fixes on this PR, can you please have another look at it ? Thanks.

Seems reasonable if you can resolve current conflicts.

@mjpt777 conflicts are now resolved

Thanks

Could you add a Wiki page on how to use it?

I added a wiki page.
Feel free to review/edit it. Since I'm a non-native english speaker, it can certainly be improved.


refactor(rust): explicitly parse log verbosity as a LevelFilter

Commit merged as part of https://github.com/build-trust/ockam/pull/5166


entproto: support json for integer type slices

This implements https://github.com/ent/ent/issues/3559

Thanks for the contribution @jamslinger!
Will review this soon.


3Legs link obsolete

Problem description
In the Documentation section, a link to Identity and Consent Management is not correct anymore: https://github.com/camaraproject//IdentityAndConsentManagement/blob/main/documentation/CAMARA-API-access/-and-user-consent.md
Expected behavior
a link to:
https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-Security-Interoperability.md
is expected as described in the guidelines:(https://github.com/jpengar/Commonalities/blob/d4d44f5b72675d10192bc8fdceb21b299f576ec9/documentation/API-design-guidelines.md)

Actually the link is ok.


player.paused() = true while playing via Airplay

I'm using Brightcove + videojs-airplay. When I send the video to Airplay output, the big play button appears over the "This video is playing on 'X'" message, and the player emits a "paused" event.
While the video is playing on the AppleTV, I can call player.paused() and the result is true.
Is this expected behaviour?
I see that there's no incidence of "pause" in the videojs-airplay code.
Hmm, this sounds similar:

https://forums.developer.apple.com/thread/92375

@yokuze this sounds familiar ... like something we had to work around on our internal media player that wraps VideoJS. You remember anything?


KDE environment file URIs

Bug Report

Information
Description

Package
League\Uri\Uri

Version
7.3

PHP version
8.1.6

OS Platform
Windows

Summary
I was looking at this Wikipedia page https://en.wikipedia.org/wiki/File_URI_scheme and tried all the examples. The package fails to parse the The KDE environment example file:/etc/fstab
Standalone code, or other way to reproduce the problem
<?php

use League\Uri\Uri;

require __DIR__.'/../vendor/autoload.php';

var_dump(Uri::new('file:/etc/fstab')->getPath());

Expected result
/etc/fstab

Actual result
PHP Fatal error:  Uncaught League\Uri\Exceptions\SyntaxError: The uri `file:/etc/fstab` is invalid for the `file` scheme. in C:\Dev\row-bloom\examples\vendor\league\uri\Uri.php:827
Stack trace:
#0 C:\Dev\row-bloom\examples\vendor\league\uri\Uri.php(239): League\Uri\Uri->assertValidState()
#1 C:\Dev\row-bloom\examples\vendor\league\uri\Uri.php(406): League\Uri\Uri->__construct('file', NULL, NULL, NULL, NULL, '/etc/fstab', NULL, NULL)
#2 C:\Dev\row-bloom\examples\uri\index.php(7): League\Uri\Uri::new('file:/etc/fstab')
#3 {main}
  thrown in C:\Dev\row-bloom\examples\vendor\league\uri\Uri.php on line 827

Fatal error: Uncaught League\Uri\Exceptions\SyntaxError: The uri `file:/etc/fstab` is invalid for the `file` scheme. in C:\Dev\row-bloom\examples\vendor\league\uri\Uri.php:827
Stack trace:
#0 C:\Dev\row-bloom\examples\vendor\league\uri\Uri.php(239): League\Uri\Uri->assertValidState()
#1 C:\Dev\row-bloom\examples\vendor\league\uri\Uri.php(406): League\Uri\Uri->__construct('file', NULL, NULL, NULL, NULL, '/etc/fstab', NULL, NULL)
#2 C:\Dev\row-bloom\examples\uri\index.php(7): League\Uri\Uri::new('file:/etc/fstab')
#3 {main}
  thrown in C:\Dev\row-bloom\examples\vendor\league\uri\Uri.php on line 827

@medilies thanks for using the package. What you are describing is not a bug per se but the application of another RFChttps://datatracker.ietf.org/doc/html/rfc8089#appendix-A which is still in proposed state. If you are willing to provide a PR to support your expected behaviour I would be more than glad to review and merge it in the package

@medilies the easiest way to add this feature would be to add two methods:

Uri::fromRfc8089(Stringable|string $uri): UriInterface
BaseUri::toRfc8089(): string

It would enable the feature without adding any BC break.

Thank you so much for showing me how to contribute while handling my issue 🙏🏼
I hope to be able to make use of this help and be a better contributor in the futur.

As of 7.6.0 still not release but present in the master branch the toRfc8089 is now also present in the Uri class


Initial check-in of draft version that contains url param support for…

… projected params
@driskull  can you take a look when you get a chance?

@kellyhutchins - Does this follow the spec on http://doc.arcgis.com/en/arcgis-online/reference/use-url-parameters.htm#ESRI_SECTION1_907DD20534E143DEBF352CDA0F1AB938 ?

Had a few comments, otherwise, looks good.


Unable to add Enduser claims to JWT

Description:
It is not possible to add a claim in addition to the claims currently supported by the JWT in cellery's global API gateway. Since the service I am working on validates the JWT using the email of the enduser, the request fails.
I tried to configure the API gateway to pass the Enduser attributes by writing a CustomTokenGenerator[1], however I believe this overrides the cellery token generator which causes problems. This also involves changing the api-manager.xml asl well which means changing the config-maps deployed by cellery runtime itself.
[1] https://docs.wso2.com/display/AM260/Passing+Enduser+Attributes+to+the+Backend+Using+JWT

Fixed with https://github.com/wso2-cellery/mesh-security/pull/90


The issue of model output

Hi, thank you for your excellent work and shared a pre-trained high-quality model.
I am trying to convert a pre-trained model into a TRT model and perform inference.
But the output of the two models is not the same.
pth model's output -->
[[1,19,32,32]
[1,19,32,32]
[1,19,32,32]
[1,19,32,32]]

trt   model's output -->
[(1108992,)
(2217984,)
(1108992,)
(2217984,)]

Has anyone done the same before, please give me some help

Hi! In #42 there is a link with TensorRT instructions: https://github.com/mathblue/Custom-Pose-Estimation-Yaw-Roll-Pitch-detection-tensorrt-compilation#compile-model-with-tensorrt--much-more-faster.

Hope, it helped.


Vote Crate Key Not Giving Items

I used 5 vote keys, 2 times it didn't give the items. It didn't give me the Moon Stone or Electrizer.

@Zaguroth I need server and when you're next online, as I'm pretty sure your IGN is also Zaguroth?


JSDocs unable to handle ChainExpression even existing in code

Input code
https://github.com/daniel-lewis-ab/litegraph.js/tree/startingAgain
For this repo, I've been trying to use JSDocs to document src as per package.json
JSDoc debug output

npm run docs

><EMAIL_ADDRESS>docs
> jsdoc -c ./docs/.jsdoc.config -d ./docs -r --verbose --debug

DEBUG: JSDoc 4.0.3 (Thu, 02 May 2024 03:14:16 GMT)
DEBUG: Environment info: {"env":{"conf":{"plugins":[],"recurseDepth":10,"source":{"includePattern":".+\\.js(doc|x)?$","excludePattern":"(^|\\/|\\\\)_","include":["src"]},"sourceType":"module","tags":{"allowUnknownTags":true,"dictionaries":["jsdoc","closure"]},"templates":{"monospaceLinks":false,"cleverLinks":false}},"opts":{"_":[],"configure":"./docs/.jsdoc.config","destination":"./docs","recurse":true,"verbose":true,"debug":true,"encoding":"utf8"}}}
DEBUG: Parsing source files: ["/media/dl/Data/Projects/litegraph.js/src/contextmenu.js","/media/dl/Data/Projects/litegraph.js/src/curveeditor.js","/media/dl/Data/Projects/litegraph.js/src/dragandscale.js","/media/dl/Data/Projects/litegraph.js/src/lgraph.js","/media/dl/Data/Projects/litegraph.js/src/lgraphcanvas.js","/media/dl/Data/Projects/litegraph.js/src/lgraphgroup.js","/media/dl/Data/Projects/litegraph.js/src/lgraphnode.js","/media/dl/Data/Projects/litegraph.js/src/litegraph-editor.js","/media/dl/Data/Projects/litegraph.js/src/litegraph.js","/media/dl/Data/Projects/litegraph.js/src/llink.js","/media/dl/Data/Projects/litegraph.js/src/nodes/audio.js","/media/dl/Data/Projects/litegraph.js/src/nodes/base.js","/media/dl/Data/Projects/litegraph.js/src/nodes/events.js","/media/dl/Data/Projects/litegraph.js/src/nodes/geometry.js","/media/dl/Data/Projects/litegraph.js/src/nodes/glfx.js","/media/dl/Data/Projects/litegraph.js/src/nodes/glshaders.js","/media/dl/Data/Projects/litegraph.js/src/nodes/gltextures.js","/media/dl/Data/Projects/litegraph.js/src/nodes/graphics.js","/media/dl/Data/Projects/litegraph.js/src/nodes/input.js","/media/dl/Data/Projects/litegraph.js/src/nodes/interface.js","/media/dl/Data/Projects/litegraph.js/src/nodes/logic.js","/media/dl/Data/Projects/litegraph.js/src/nodes/math.js","/media/dl/Data/Projects/litegraph.js/src/nodes/math3d.js","/media/dl/Data/Projects/litegraph.js/src/nodes/midi.js","/media/dl/Data/Projects/litegraph.js/src/nodes/network.js","/media/dl/Data/Projects/litegraph.js/src/nodes/others.js","/media/dl/Data/Projects/litegraph.js/src/nodes/strings.js"]
Parsing /media/dl/Data/Projects/litegraph.js/src/contextmenu.js ...
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
Parsing /media/dl/Data/Projects/litegraph.js/src/curveeditor.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/dragandscale.js ...
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
Parsing /media/dl/Data/Projects/litegraph.js/src/lgraph.js ...
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
Parsing /media/dl/Data/Projects/litegraph.js/src/lgraphcanvas.js ...
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
Parsing /media/dl/Data/Projects/litegraph.js/src/lgraphgroup.js ...
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
Parsing /media/dl/Data/Projects/litegraph.js/src/lgraphnode.js ...
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
Parsing /media/dl/Data/Projects/litegraph.js/src/litegraph-editor.js ...
DEBUG: Found a node with unrecognized type ChainExpression. Ignoring the node and its descendants.
Parsing /media/dl/Data/Projects/litegraph.js/src/litegraph.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/llink.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/audio.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/base.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/events.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/geometry.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/glfx.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/glshaders.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/gltextures.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/graphics.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/input.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/interface.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/logic.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/math.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/math3d.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/midi.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/network.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/others.js ...
Parsing /media/dl/Data/Projects/litegraph.js/src/nodes/strings.js ...
DEBUG: Finished parsing source files.
DEBUG: Adding inherited symbols, mixins, and interface implementations...
DEBUG: Adding borrowed doclets...
DEBUG: Post-processing complete.
Generating output files...
Finished running in 1.50 seconds.

Expected behavior
Can it at least just ignore the ChainExpressions and continue documenting the rest of the code?
Current behavior
Currently just refuses to document any code that contains these expressions, which have been out for >2 years now.
  The settings do include that it uses modules, rather than CommonJS.


Crashing

Seems to be crashing the game when searching from context menu.
"Yak Milk" for example crashed the game.

Hello,
Thanks for the report!
I'll be looking into that error.
Regards

Hello @Revonlieke,
Does this crash keeps happening?
I've checked the Yak Milk item you mentioned, using the "Loot search" option on the context menu and it worked.
Could you provide the log file where you got that unhandled exception you attached? That way I can check where in the code this error could have happened.
Regards.

Yes it's the same as above^^ sorry for not responding sooner.

Thank you both so much for this report!
I'll look into it right away.

Hello @Revonlieke  and @Scrxtchy ,
Dalamud should deliver a new version of the plugin with a fix I've made. I'd like to ask you to test it when it's available and report if the issue was solved.
I hope that it was.
Regards.

These lines are different for me. Otherwise the same error still happening.

Thank you for reporting.
The strange thing is that I wasn't able to reproduce this error.
I've opened a different plugin window (and even MLH window) and did the loot search.
As this seems to be happening cause of the table freeze, I'll remove it, the header being frozen is not that important.

I've submitted the hotfix removing the column freeze from the UI.
I hope that this resolves the issue and stops making your game from crashing.
Sorry for the inconvenience. I'd like to ask you again to test it when it's available and report if the issue was solved.
Regards.

For me it has not. (removed some of the personal info from the file & modules section.
It COULD be some conflict with another mod maybe.
dalamud_appcrash_20230331_154308_100_8948.log

I'm starting to think that this could be a conflict with another mod, even though it shouldn't, as this is simply ImGui trying to render the table and failing to do so for some reason.
It's even more troublesome that I wasn't able to reproduce this until this very moment. I've received some feedbacks about the plugin making the game crash, but none of the steps that were provided me got me to reproduce it :(
I'm trying to understand what's happening but still am unable to do so. I'll keep trying to solve this issue completely.

After some insight from the guys at Dalamud server, I've did some modifications on the code. I hope that now this issue is gone for good.
If the plugin rendering now fails, as it seems to be the case, then it'll suggest using the legacy rendering strategy which I scrapped in favor of the current one. I hope that this fallback is able to make it render without issues if the default one fails.
As soon as the plugin is updated, @Revonlieke I'll be waiting for feedback if it indeed solved it.
Regards.

Now it works, no issues. Good stuff! Thanks a lot for fixing it. :)


lib3mf: 2.0.0 -> 2.1.1

Motivation for this change
Fixes #116888
openscad's 3MF support has been broken since #101105, since lib3mf 2.0 has a different API.  I believe the easiest way to fix this is to wait for the next openscad release (with the new cmake build system).
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 116952 at 04e1a9d2 run on aarch64-linux 1

2 packages failed to build (new failures):

lib3mf
openscad

Also I noticed while building that we should split out include into a dev output

lib3mf: Ask if output path include (4.0M) could be split with outputs = [ ... "dev" ];

Fixes: CVE-2021-21772

A use-after-free vulnerability exists in the NMR::COpcPackageReader::releaseZIP() functionality of 3MF Consortium lib3mf 2.0.0. A specially crafted 3MF file can lead to code execution. An attacker can provide a malicious file to trigger this vulnerability.


Con't use “crx”

“If you need to use a disabled extension, you can contact the extension’s developer and ask them to upload their extension to the Chrome Web Store. This will allow you, and other people who use Chrome, to install that extension from the Chrome Web Store, or if you already have it installed, to manually re-enable it from your list of extensions.”
The info is provided by Chrome

@Yueshi9 Chrome 目前不支持非谷歌官方商店的扩展程序了。
可行的更新后的方案为加载解压缩的文件夹，具体可查看最新 release。

THX


Feasable to train on fewer/single GPU?

Hi,
in the paper it is stated that you used 8 GPUs for training. Some questions regarding that:

Can you specify what kind of GPUs you used (name, amount of GPU memory)?
How long did the training take with your 8 GPUs?
Is it necessary to train with this many GPUs or would the training time with the same settings be otherwise way to long?

Best Karol

8 Nvidia V100, each with 16 GB;
For 180k, about 1.5 days. For 720k or a longer schedule, a longer time is needed.
The simplest way is to keep the total batch size the same while changing GPU num and the training time will be longer.


guidance for locking themselves out?

Since I have seen this twice on the web now, it might be good to mention that if they accidentally locked out themselves (and/or everybody), they need no create a new user which then will have PS access again. Or alternatively, provide guidance on how to exclude a user. Like get-user | Where-Object {$_.userprincipalname -ne<EMAIL_ADDRESS>| Set-User -RemotePowerShellEnabled $false

@SiegfriedB2, I added the following note to the Enable or disable access to Exchange Online PowerShell (which is what I presume we're talking about here?

[!IMPORTANT]
Don't run commands like Get-User | Set-User -RemotePowerShellEnabled $false to universally remove remote PowerShell access without considering admin accounts. Use the procedures in this article to selectively remove remote PowerShell access, or preserve admin access for at least one account by using the following syntax in your removal command: Get-User | Where-Object {$_.UserPrincipalName -ne<EMAIL_ADDRESS>| Set-User -RemotePowerShellEnabled $false.
If you accidentally lock yourself out of remote PowerShell access, create a new admin user account, and then use that account to give yourself remote PowerShell access.

OK?

@SiegfriedB2 Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Combine Config.h and Json.h into one file

Signed-off-by: yudong.cai<EMAIL_ADDRESS>

/lgtm


WinPTY agent fails to launch on Windows 7

[x] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: Windows 7 SP1 64bit
Hyper.app version: 2.0.0
Link of a Gist with the contents of your .hyper.js: https://gist.github.com/codehearts/401f8857f1f817052b187cb119875e32
Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere): N/A
The issue is reproducible in vanilla Hyper.app: Yes

Issue
Since updating to 2.0.0 Hyper throws an error at startup. When I hit OK on the popup, the window appears but there's no text entry since there's no terminal. I've done this using cygwin bash and powershell as my shell, neither works.
Uncaught exception:
Error: Error launching WinPTY agent: ConnectNamedPipe failed: Windows error 232
    at new WindowsPtyAgent
...

The call stack seems to be WindowsPtyAgent<-WindowsTerminal<-spawn<-Session<-initSession<-Server.Window.rpc.on.options<-emitOne<-Server.emit<-Server.ipcListener<-emitTwo. This was working on earlier canaries, I see something changed with winpty so I suspect that's what did it.

Do you remember the last canary that works?

I think it was canary 8 or 9, sometime way back

I just verified that canary 8 works for me, but canary 9 throws an unrelated error before throwing the one I've reported here

Just ran into this on Win10 using the new v2.

@corydeppen Is it reproducible each time?

Yes, it hasn't launched without error yet. I've included the full error and link to my .hyper.js file. I'm also wondering if it may be related to #2865.
Error: Error launching WinPTY agent: Security check failed: pipe client pid (6944) does not match agent pid (283536)
    at new WindowsPtyAgent (C:\Users\[username]\AppData\Local\hyper\app-2.0.0\resources\app.asar\node_modules\node-pty\lib\windowsPtyAgent.js:25:24)
    at new WindowsTerminal (C:\Users\[username]\AppData\Local\hyper\app-2.0.0\resources\app.asar\node_modules\node-pty\lib\windowsTerminal.js:45:24)
    at spawn (C:\Users\[username]\AppData\Local\hyper\app-2.0.0\resources\app.asar\node_modules\node-pty\lib\index.js:27:12)
    at Session (C:\Users\[username]\AppData\Local\hyper\app-2.0.0\resources\app.asar\session.js:53:18)
    at initSession (C:\Users\[username]\AppData\Local\hyper\app-2.0.0\resources\app.asar\ui\window.js:102:24)
    at Server.Window.rpc.on.options (C:\Users\[username]\AppData\Local\hyper\app-2.0.0\resources\app.asar\ui\window.js:105:7)
    at emitOne (events.js:115:13)
    at Server.emit (events.js:210:7)
    at Server.ipcListener (C:\Users\[username]\AppData\Local\hyper\app-2.0.0\resources\app.asar\rpc.js:33:11)
    at emitTwo (events.js:125:13)

https://gist.github.com/corydeppen/65735150ddc5e869b84555ce4d7548b8

I'm running into the exact same problem as Cory on win10x64 1709.  I can re-install 1.48 and work fine for a day but as soon as it upgrades to 2.0.0 it breaks.  No plugins installed.  Installing clean from 2.0.0 also results in the same error.

I've just experienced this issue on Windows 10 when installing Hyper for the first time.

I have the same issue but on Windows 10

I solved instilling with choco

So this is odd, but I tried 2.0.0 stable yesterday and this error was no longer an issue. Then it came back after rebooting today, and of course I'm clueless as to what I did that could've caused it.

Windows 10 version 1709

Same here on Windows 10,
Normally Hyper terminal works, but it breaks with above error when you run it as Administrator.

Hyper <IP_ADDRESS>8 on Windows 10 Pro.

I'm seeing this error after the upgrade to Hyper 2.1. I did not see the error in version 2.0. I'm in a corporate environment, and think the issue is related to running McAfee Endpoint Security, as described in the reference @octachrome provided above.
If I uninstall Hyper2.1 and reinstall 2.0, then the error goes away, but then Hyper automatically upgrade to 2.1. Is there a way to prevent Hyper from automatically upgrading?

Experiencing the exact same behavior as @boydjeff. Anything we can do? I have tried running as admin with no luck.

I'm seeing this error after the upgrade to Hyper 2.1. I did not see the error in version 2.0. I'm in a corporate environment, and think the issue is related to running McAfee Endpoint Security, as described in the reference @octachrome provided above.
If I uninstall Hyper2.1 and reinstall 2.0, then the error goes away, but then Hyper automatically upgrade to 2.1. Is there a way to prevent Hyper from automatically upgrading?

Yes, I also met this issue.  the issue goes away after I roll back it to 2.1-cannary2. But it always prompt to upgrade. and there is not option that can close auto upgrade!

What about setting releases.hyper.is or releases-canary.hyper.is to <IP_ADDRESS> in your hosts file to work around the updater?

The culprit is in McAfee Real-Time Scanning, I tried turning it off and this error never happens, but when turning back on again the error happens again.

Can confirm @aescasiodev 's find. When turning it off, error no longer happens.

For McAfee issue, I got it working by excluding C:\Users\<User>\AppData\Local\hyper\app-2.1.0\resources\app.asar.unpacked\node_modules\node-pty\build\Release\winpty-agent.exe  from real-time scanning on McAfee

@rnagatama yes, you need to exclude that file from Real-Time Scanning in any Antivirus.
That works.

I've also started running into this in 2.1, I'm unable to change my McAfee's settings in my environment, is there an ETA on the fix?
Could it be perhaps due to the executable not being signed?

The culprit is in McAfee Real-Time Scanning, I tried turning it off and this error never happens, but when turning back on again the error happens again.

Deactivated the McAfee Real-Time Scanning and it worked... Put back the R.T.S. and tried to put some files in the exception list and it didn't work... it just appends to work a bit later... weird!


Prometheus metrics in sc-service should be updated as soon as possible, not every 5 seconds

The metrics here are updated only every 5 seconds, when tick is called.
It shouldn't be so. Whenever we have a new block, the metrics should be updated.
If people worry about performances, a metric is a AtomicU64. It literally takes in the order of a nanosecond to update a metric.

Whenever we have a new block, the metrics should be updated.

Where would that be in terms of the code?


Stream Popup immediately disappears on certain failure

Issue: Stream Popup closes instantly on failure
when attempting to watch a stream with an unsupported quality (dota2ti), the stream popup disappears instantly on failure, taking the CLI output with it
Expected: Stream popup should remain to allow for troubleshooting of the issue
I believe if a stream is not found or another issue is encountered, the stream popup remains
Reproduction steps

Attempt to watch dota2ti on the current release build
Stream popup opens, and then closes immediately

Environment details
Ubuntu 16.04 LTS

Already fixed with a new release... #283


current directory mismatch in Spyder 5.0.0

What steps will reproduce the problem?
Incorrect path with function getcwd()

Actual Result
current directory : C:\Users\osama.spyder-py3
Expect Result
current directory : B:\Scripts
Versions
Spyder version: 5.0.0
Python version: 3.8.6
Qt version: 5.12.10
PyQt5 version: 5.12.3
Operating System: Windows 10

Hi @Smsmadly thanks for the feedback. Seems like your current working directory is at C:\Users\osama\.spyder-py3 (the current working directory that Spyder is using is shown in the Working Directory toolbar at the top right of the window). If you want to use the file directory as working directory when running you need to go to Run > Configuration per file... > Working directory settings and select the option The directory of the file being executed
Let us know if the info above helps :)


Fixed dropdown content bug to not go off the right side of page

This fixes the dropdown bug, so that on an expanded page, the content does not overflow off the page

LGTM, thanks for fixing this!


flow_from_directory throwing OS Error saying " The filename, directory name, or volume label syntax is incorrect "

My code goes this way
`
#IMPORTING LIBRARIES
import tensorflow as tf
from tensorflow.keras.preprocessing.image import ImageDataGenerator
import numpy as np
from tensorflow.keras.preprocessing import  image
#DATA PREPROCESSING
#Preprocessing the Training Set
train_datagen = ImageDataGenerator(rescale = 1./255, shear_range = 0.2, zoom_range = 0.2, horizontal_flip = True)
train_set = train_datagen.flow_from_directory("D:\Code\ML\Datasets\CatsDogs\trainingset", target_size = (64,64), batch_size = 32, class_mode = 'binary')
#Preprocessing the Test Set
test_datagen = ImageDataGenerator(rescale = 1./255)
test_set = test_datagen.flow_from_directory("D:\Code\ML\Datasets\CatsDogs\testset",target_size = (64,64), batch_size = 32, class_mode = 'binary')
#BUILDING THE CNN
#Initialize the CNN
cnn = tf.keras.models.Sequential()
#First Convolution layer
cnn.add(tf.keras.layers.Conv2D(filters = 32, kernel_size = 3, activation = 'relu', input_shape = [64, 64,3]))
#Pooling -->Max Pooling
cnn.add(tf.keras.layers.MaxPool2D(pool_size = 2, strides = 2))
#Second Convolution layer
cnn.add(tf.keras.layers.Conv2D(filters = 32, kernel_size = 3, activation = 'relu'))
#Pooling -->Max Pooling(For the second Convolution layer)
cnn.add(tf.keras.layers.MaxPool2D(pool_size = 2, strides = 2))
#Flattening
cnn.add(tf.keras.layers.Flatten())
#Full Connection
cnn.add(tf.keras.layers.Dense(units = 128, activation = 'relu'))
#output layer
cnn.add(tf.keras.layers.Dense(units = 1, activation = 'sigmoid'))
#TRAINING THE CNN
#Compiling the CNN
cnn.compile(optimizer = 'adam', loss = 'binary_crossentropy', metrics = ['accuracy'])
#Training the CNN on train_set and evaluating the same on the test_set at the same time
cnn.fit(x = train_set, validation_data = test_set, epochs = 25)
#MAKING A SINGLE PREDICTION
test_img = image.load_img('D:\Code\ML\Datasets\Cats & Dogs\cat_or_dog_1.jpg', target_size = (64,64))
test_img = image.img_to_array(test_img)
test_img = np.expand_dims(test_img, axis = 0)
result = cnn.predict(test_img)
train_set.class_indices
if result[0][0] == 1:
prediction = 'dog'
else:
prediction = 'cat'
print(prediction)
`
I looked into Keras's documentation but couldn't find anything of use.
You can see my directories here.

Thanks in advance.

I found the solution for myself  I guess!
I just replaced the file path with forward slashes and it worked out of the box!!
Even though the issue is solved I would like to know why fixing my file path solved the error!!?


Update OnScreenKeyboardLayouts.md

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/develop-your-app/OnScreenKeyboardLayouts.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/TOC.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/OnScreenKeyboardLayouts.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/TOC.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/OnScreenKeyboard.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/OnScreenKeyboardLayouts.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/TOC.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/OnScreenKeyboard.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/OnScreenKeyboardLayouts.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix release day and add system-dependent cooldown

This will ensure that we schedule a precise version instead of a lower bound,
and that upgrades to the next release always happens in CD systems earlier than
public/main.
@jonmv

or @andreer (in case @jonmv is OOO)


Error on image start in next_release

When starting the latest build next_release, the following error message is shown:
ERROR: 'klayout' has version (but version must be > 'KLayout 0.28.8')

Further we try to consistently use [ERROR], [WARN] and [INFO] throughout the image, this should be adapted.

This looks like a follow-up error from the fact that klayout can't be called ( as @MrHighVoltage  mentioned here https://github.com/iic-jku/IIC-OSIC-TOOLS/pull/25#issuecomment-1900292624 ).

Strange, yesterday I built and tested the image using bag2_integration commit b7d394a successfully.
This was based on next_release commit e2b85ea9edefbab2b3db003e7f69350b5d5bd12f.
How and how often are the integration tests performed?
The way I tested it was:
cd IIC-OSIC-TOOLS/_build
docker build . --build-arg http_proxy=$http_proxy --build-arg https_proxy=$https_proxy


Pcx 1086 analytics graphql update getting started

User story
Update Analytics dev docs so that the Getting Started section more clearly communicates how to

authenticate with an API token
introspect the API in GraphiQl
build a query in GraphiQL
execute a query with curl

I meant to approve :)

Thanks, Jon!
We'll make that small change to the header and confirm the images before merging.


import IsomorphicRouter from 'isomorphic-relay-router'; fail

/node_modules/react-relay/node_modules/fbjs/node_modules/whatwg-fetch/fetch.js:4
if (self.fetch) {
^
ReferenceError: self is not defined

Are you trying to run the ToDo example?

Well I never managed to run the todo example (a lot of errors with babel and babel-cli) so I tried to implement it my self line by line but I just can't import IsomorphicRouter without getting that error?

Is your babel globally installed? Is it version 6?

Yes, I followed the steps, but what Im really interested on is not to run the todo example but to understand why import IsomorphicRouter is not working? Is it related to babel? Thanks

I can not tell based on the information you provide, my only clue was that there was an issue with babel-cli when you ran the todo example.

Sorry, so, I just started from zero to retry to run the example.
I first installed babel globally, then npm install and npm start. I don't have the same error now, I have an error:   throw new Error("The (" + alias + ") Babel 5 plugin is being run with Babel.
Then, I tried to import IsomorphicRouter into my own project and doing that I have an error
/node_modules/react-relay/node_modules/fbjs/node_modules/whatwg-fetch/fetch.js:4
if (self.fetch) {
^
ReferenceError: self is not defined

I would suggest to double check at your babel configuration, I think there are big differences between 5 and 6. If it is possible in your case and would not affect the rest of your work, try globally uninstalling babel and then installing 6, and make sure in your package.json you are using babel 6 components, including the right versions for the babel plugins for Relay.

I first installed babel globally, then npm install and npm start. I don't have the same error now, I have an error: Error: The (relay-query) Babel 5 plugin is being run with Babel 6.

That was fixed after I updated babel-relay-plugin in the ToDo example.

/node_modules/react-relay/node_modules/fbjs/node_modules/whatwg-fetch/fetch.js:4
if (self.fetch) {

Probably you have outdated version of react-relay in your project. Update to v0.7.3 if this is the case.