MongoDB empty key inserts

Empty keys can be created in traces ( "data":{"":"0.0150 EOS"} ), which causes those inserts into mongo to be dropped.
Full error message in comment.

Full error message:
warn  2019-01-02T16:16:52.440 thread-1  mongo_db_plugin.cpp:540       handle_mongo_excepti ] mongo logic error, add action traces, line 875, code 22, invalid document for insert: empty key: generic server error
warn  2019-01-02T16:16:52.442 thread-1  mongo_db_plugin.cpp:540       handle_mongo_excepti ] mongo logic error, trans_traces insert: {"id":"8b7787c5c9ed22a893f6331a50f2ed04047943a82bf1caadd4d32a0cd65a655e","block_num":35347843,"block_time":"2019-01-02T16:16:52.000","producer_block_id":"021b5d8387f9c5c0d96111ff1960cf00f3b48e361f76f8c6d3991f5db4051305","receipt":{"status":"executed","cpu_usage_us":1015,"net_usage_words":22},"elapsed":2634,"net_usage":176,"scheduled":false,"action_traces":[{"receipt":{"receiver":"eoszealbank1","act_digest":"7330e3e881851cb40fa1a5ed59d6eb3ca18b84a3f1a4139402e216b8bbc60ca3","global_sequence":3595349030,"recv_sequence":39519,"auth_sequence":[["eoszealbank1",75372]],"code_sequence":3,"abi_sequence":3},"act":{"account":"eoszealbank1","name":"resolvebet","authorization":[{"actor":"eoszealbank1","permission":"active"}],"data":{"bet_id":"7423538076392533341","seed":"f56ce4793a1eae8bd54008bf8543fa7613b0ceefb8eded2ab28878b3d3474fdf"},"hex_data":"5dadf6838cb40567f56ce4793a1eae8bd54008bf8543fa7613b0ceefb8eded2ab28878b3d3474fdf"},"context_free":false,"elapsed":904,"console":"","trx_id":"8b7787c5c9ed22a893f6331a50f2ed04047943a82bf1caadd4d32a0cd65a655e","block_num":35347843,"block_time":"2019-01-02T16:16:52.000","producer_block_id":"021b5d8387f9c5c0d96111ff1960cf00f3b48e361f76f8c6d3991f5db4051305","account_ram_deltas":[{"account":"eoszealbank1","delta":241}],"except":null,"inline_traces":[{"receipt":{"receiver":"zealbounce11","act_digest":"7e781f19737b9b063e33b46f8e548200843126a7a61aeb3e9286737210cce3c1","global_sequence":3595349031,"recv_sequence":12174,"auth_sequence":[["zealbounce11",6190]],"code_sequence":3,"abi_sequence":2},"act":{"account":"zealbounce11","name":"addbonus","authorization":[{"actor":"zealbounce11","permission":"active"}],"data":{"":"0.0150 EOS"},"hex_data":"960000000000000004454f5300000000"},"context_free":false,"elapsed":75,"console":"","trx_id":"8b7787c5c9ed22a893f6331a50f2ed04047943a82bf1caadd4d32a0cd65a655e","block_num":35347843,"block_time":"2019-01-02T16:16:52.000","producer_block_id":"021b5d8387f9c5c0d96111ff1960cf00f3b48e361f76f8c6d3991f5db4051305","account_ram_deltas":[],"except":null,"inline_traces":[]},{"receipt":{"receiver":"zealbancor11","act_digest":"f6e8673a62f027dcacd0d520e59b4c9d4f3ee802b9f425f72331fb5ffe329f7b","global_sequence":3595349032,"recv_sequence":12558,"auth_sequence":[["zealbancor11",6578]],"code_sequence":6,"abi_sequence":3},"act":{"account":"zealbancor11","name":"grant","authorization":[{"actor":"zealbancor11","permission":"active"}],"data":{"player":"tothemoon111","quantity_eos":"0.0150 EOS"},"hex_data":"104298944ad532cd960000000000000004454f5300000000"},"context_free":false,"elapsed":310,"console":"","trx_id":"8b7787c5c9ed22a893f6331a50f2ed04047943a82bf1caadd4d32a0cd65a655e","block_num":35347843,"block_time":"2019-01-02T16:16:52.000","producer_block_id":"021b5d8387f9c5c0d96111ff1960cf00f3b48e361f76f8c6d3991f5db4051305","account_ram_deltas":[],"except":null,"inline_traces":[]},{"receipt":{"receiver":"eosio.token","act_digest":"d890f70e639eeaf68c6d2e118bdd941657f50382fcb89e178161098687b98bb5","global_sequence":3595349033,"recv_sequence":593458914,"auth_sequence":[["eoszealbank1",75373]],"code_sequence":2,"abi_sequence":2},"act":{"account":"eosio.token","name":"transfer","authorization":[{"actor":"eoszealbank1","permission":"active"}],"data":{"from":"eoszealbank1","to":"zealbounce11","quantity":"0.0150 EOS","memo":"for bonus and team cost"},"hex_data":"10e034271af5315510824253d3138dfa960000000000000004454f530000000017666f7220626f6e757320616e64207465616d20636f7374"},"context_free":false,"elapsed":151,"console":"","trx_id":"8b7787c5c9ed22a893f6331a50f2ed04047943a82bf1caadd4d32a0cd65a655e","block_num":35347843,"block_time":"2019-01-02T16:16:52.000","producer_block_id":"021b5d8387f9c5c0d96111ff1960cf00f3b48e361f76f8c6d3991f5db4051305","account_ram_deltas":[],"except":null,"inline_traces":[{"receipt":{"receiver":"eoszealbank1","act_digest":"d890f70e639eeaf68c6d2e118bdd941657f50382fcb89e178161098687b98bb5","global_sequence":3595349034,"recv_sequence":39520,"auth_sequence":[["eoszealbank1",75374]],"code_sequence":2,"abi_sequence":2},"act":{"account":"eosio.token","name":"transfer","authorization":[{"actor":"eoszealbank1","permission":"active"}],"data":{"from":"eoszealbank1","to":"zealbounce11","quantity":"0.0150 EOS","memo":"for bonus and team cost"},"hex_data":"10e034271af5315510824253d3138dfa960000000000000004454f530000000017666f7220626f6e757320616e64207465616d20636f7374"},"context_free":false,"elapsed":253,"console":"","trx_id":"8b7787c5c9ed22a893f6331a50f2ed04047943a82bf1caadd4d32a0cd65a655e","block_num":35347843,"block_time":"2019-01-02T16:16:52.000","producer_block_id":"021b5d8387f9c5c0d96111ff1960cf00f3b48e361f76f8c6d3991f5db4051305","account_ram_deltas":[],"except":null,"inline_traces":[]},{"receipt":{"receiver":"zealbounce11","act_digest":"d890f70e639eeaf68c6d2e118bdd941657f50382fcb89e178161098687b98bb5","global_sequence":3595349035,"recv_sequence":12175,"auth_sequence":[["eoszealbank1",75375]],"code_sequence":2,"abi_sequence":2},"act":{"account":"eosio.token","name":"transfer","authorization":[{"actor":"eoszealbank1","permission":"active"}],"data":{"from":"eoszealbank1","to":"zealbounce11","quantity":"0.0150 EOS","memo":"for bonus and team cost"},"hex_data":"10e034271af5315510824253d3138dfa960000000000000004454f530000000017666f7220626f6e757320616e64207465616d20636f7374"},"context_free":false,"elapsed":31,"console":"","trx_id":"8b7787c5c9ed22a893f6331a50f2ed04047943a82bf1caadd4d32a0cd65a655e","block_num":35347843,"block_time":"2019-01-02T16:16:52.000","producer_block_id":"021b5d8387f9c5c0d96111ff1960cf00f3b48e361f76f8c6d3991f5db4051305","account_ram_deltas":[],"except":null,"inline_traces":[]}]},{"receipt":{"receiver":"eosio.token","act_digest":"7fbd64c13d17e2f8e83ed80eac86e7ca512ecf87f173f7f5ea1e6e111e2d1eb4","global_sequence":3595349036,"recv_sequence":593458915,"auth_sequence":[["eoszealbank1",75376]],"code_sequence":2,"abi_sequence":2},"act":{"account":"eosio.token","name":"transfer","authorization":[{"actor":"eoszealbank1","permission":"active"}],"data":{"from":"eoszealbank1","to":"zealbancor11","quantity":"0.0150 EOS","memo":"for bancor"},"hex_data":"10e034271af5315510c2a5689a138dfa960000000000000004454f53000000000a666f722062616e636f72"},"context_free":false,"elapsed":118,"console":"","trx_id":"8b7787c5c9ed22a893f6331a50f2ed04047943a82bf1caadd4d32a0cd65a655e","block_num":35347843,"block_time":"2019-01-02T16:16:52.000","producer_block_id":"021b5d8387f9c5c0d96111ff1960cf00f3b48e361f76f8c6d3991f5db4051305","account_ram_deltas":[],"except":null,"inline_traces":[{"receipt":{"receiver":"eoszealbank1","act_digest":"7fbd64c13d17e2f8e83ed80eac86e7ca512ecf87f173f7f5ea1e6e111e2d1eb4","global_sequence":3595349037,"recv_sequence":39521,"auth_sequence":[["eoszealbank1",75377]],"code_sequence":2,"abi_sequence":2},"act":{"account":"eosio.token","name":"transfer","authorization":[{"actor":"eoszealbank1","permission":"active"}],"data":{"from":"eoszealbank1","to":"zealbancor11","quantity":"0.0150 EOS","memo":"for bancor"},"hex_data":"10e034271af5315510c2a5689a138dfa960000000000000004454f53000000000a666f722062616e636f72"},"context_free":false,"elapsed":205,"console":"","trx_id":"8b7787c5c9ed22a893f6331a50f2ed04047943a82bf1caadd4d32a0cd65a655e","block_num":35347843,"block_time":"2019-01-02T16:16:52.000","producer_block_id":"021b5d8387f9c5c0d96111ff1960cf00f3b48e361f76f8c6d3991f5db4051305","account_ram_deltas":[],"except":null,"inline_traces":[]},{"receipt":{"receiver":"zealbancor11","act_digest":"7fbd64c13d17e2f8e83ed80eac86e7ca512ecf87f173f7f5ea1e6e111e2d1eb4","global_sequence":3595349038,"recv_sequence":12559,"auth_sequence":[["eoszealbank1",75378]],"code_sequence":2,"abi_sequence":2},"act":{"account":"eosio.token","name":"transfer","authorization":[{"actor":"eoszealbank1","permission":"active"}],"data":{"from":"eoszealbank1","to":"zealbancor11","quantity":"0.0150 EOS","memo":"for bancor"},"hex_data":"10e034271af5315510c2a5689a138dfa960000000000000004454f53000000000a666f722062616e636f72"},"context_free":false,"elapsed":28,"console":"","trx_id":"8b7787c5c9ed22a893f6331a50f2ed04047943a82bf1caadd4d32a0cd65a655e","block_num":35347843,"block_time":"2019-01-02T16:16:52.000","producer_block_id":"021b5d8387f9c5c0d96111ff1960cf00f3b48e361f76f8c6d3991f5db4051305","account_ram_deltas":[],"except":null,"inline_traces":[]}]},{"receipt":{"receiver":"eosio.token","act_digest":"f82924ba08f1fd1f8b07ee323473debd50bf5c2df2adc28f652a778d094a2f7a","global_sequence":3595349039,"recv_sequence":593458916,"auth_sequence":[["eoszealbank1",75379]],"code_sequence":2,"abi_sequence":2},"act":{"account":"eosio.token","name":"transfer","authorization":[{"actor":"eoszealbank1","permission":"active"}],"data":{"from":"eoszealbank1","to":"tothemoon111","quantity":"1.0039 EOS","memo":"Bet id:<PHONE_NUMBER>392533341 -- You win! Congratulations! https://eoszeal.io"},"hex_data":"10e034271af53155104298944ad532cd372700000000000004454f53000000004b4265742069643a2037343233353338303736333932353333333431202d2d20596f752077696e2120436f6e67726174756c6174696f6e73212068747470733a2f2f656f737a65616c2e696f"},"context_free":false,"elapsed":128,"console":"","trx_id":"8b7787c5c9ed22a893f6331a50f2ed04047943a82bf1caadd4d32a0cd65a655e","block_num":35347843,"block_time":"2019-01-02T16:16:52.000","producer_block_id":"021b5d8387f9c5c0d96111ff1960cf00f3b48e361f76f8c6d3991f5db4051305","account_ram_deltas":[],"except":null,"inline_traces":[{"receipt":{"receiver":"eoszealbank1","act_digest":"f82924ba08f1fd1f8b07ee323473debd50bf5c2df2adc28f652a778d094a2f7a","global_sequence":3595349040,"recv_sequence":39522,"auth_sequence":[["eoszealbank1",75380]],"code_sequence":2,"abi_sequence":2},"act":{"account":"eosio.token","name":"transfer","authorization":[{"actor":"eoszealbank1","permission":"active"}],"data":{"from":"eoszealbank1","to":"tothemoon111","quantity":"1.0039 EOS","memo":"Bet id:<PHONE_NUMBER>392533341 -- You win! Congratulations! https://eoszeal.io"},"hex_data":"10e034271af53155104298944ad532cd372700000000000004454f53000000004b4265742069643a2037343233353338303736333932353333333431202d2d20596f752077696e2120436f6e67726174756c6174696f6e73212068747470733a2f2f656f737a65616c2e696f"},"context_free":false,"elapsed":229,"console":"","trx_id":"8b7787c5c9ed22a893f6331a50f2ed04047943a82bf1caadd4d32a0cd65a655e","block_num":35347843,"block_time":"2019-01-02T16:16:52.000","producer_block_id":"021b5d8387f9c5c0d96111ff1960cf00f3b48e361f76f8c6d3991f5db4051305","account_ram_deltas":[],"except":null,"inline_traces":[]},{"receipt":{"receiver":"tothemoon111","act_digest":"f82924ba08f1fd1f8b07ee323473debd50bf5c2df2adc28f652a778d094a2f7a","global_sequence":3595349041,"recv_sequence":437379,"auth_sequence":[["eoszealbank1",75381]],"code_sequence":2,"abi_sequence":2},"act":{"account":"eosio.token","name":"transfer","authorization":[{"actor":"eoszealbank1","permission":"active"}],"data":{"from":"eoszealbank1","to":"tothemoon111","quantity":"1.0039 EOS","memo":"Bet id:<PHONE_NUMBER>392533341 -- You win! Congratulations! https://eoszeal.io"},"hex_data":"10e034271af53155104298944ad532cd372700000000000004454f53000000004b4265742069643a2037343233353338303736333932353333333431202d2d20596f752077696e2120436f6e67726174756c6174696f6e73212068747470733a2f2f656f737a65616c2e696f"},"context_free":false,"elapsed":7,"console":"","trx_id":"8b7787c5c9ed22a893f6331a50f2ed04047943a82bf1caadd4d32a0cd65a655e","block_num":35347843,"block_time":"2019-01-02T16:16:52.000","producer_block_id":"021b5d8387f9c5c0d96111ff1960cf00f3b48e361f76f8c6d3991f5db4051305","account_ram_deltas":[],"except":null,"inline_traces":[]}]}]}],"except":null}, line 908, code 22, invalid document for insert: empty key: generic server error

The abi for zealbounce11 addbonus is:
      "name": "addbonus",
      "base": "",
      "fields": [{
          "name": "",
          "type": "asset"
        }
      ]
    }


Add QR Code for joining lobbies

1.Added library qrcode from npm into the project via command : npm install qrcode
2.Modified lobby html to contain a new dropdown button which generates a QR code (placement to where the other buttons were)
3.Modified lobby.js to contain global import of npm qrcode library which is then used in added asynch method generateQRCode which builds the qr code of current lobby and displays it upon dropdown click in lobby.
Images of generated QRCode :
Image of not clicked dropdown:

Image of clicked dropdown:

Did a brief review, looks pretty good. The code to take it from the existing page looks pretty nice too as we can easily add the button to other pages as well.
I'll ping brice to merge it.
Other stuff:
Depending on how long it takes to calculate it might be nice just show the qr code when the page loads, especially for sharing it to other mobile users, but we can leave that for a future pr.

One thing that i just remembered is that I commited the update package.lock and json but just remembered that your architecture has a requirements.txt in scripts, should i remove the package commit and add the required library into requirements.txt ?

One thing that i just remembered is that I commited the update package.lock and json but just remembered that your architecture has a requirements.txt in scripts, should i remove the package commit and add the required library into requirements.txt ?

That is for the backend python requirements, this should be fine.

Just merged in main for you!

Hi currently I have implemented the saving of the qr code in higher resolution, is the 3rd step still needed or is the 2nd step enough ?

Hi Dan,
I think we should leave those tasks to a separate pr it’ll probably be too much to implement 4 new features. Especially creating a separate page will take some time to setup.

Yeah, just having the higher resolution code and an easy way to save it should be fine! They can always get their own page! Once you have that in I can try it out again and it should be ready to merge.

Hi, Could you please take a look at these screenshots if this matches your requirements of the first 2 points ?

Best Regards,
Roland

Regarding the colapsible permanent image instead of a dropdown, I solved it with an invocation of generateQRCode method in the mounted of lobby.js
This way the QR Code is preloaded on the page when the user opens the lobby.

Looks great I will take care of the merge conflicts and myself and can merge it once done!


Segmentation fault on latest release

use opencv::core::{Point, Vector};
use opencv::imgproc::{bounding_rect, min_area_rect};
use opencv::prelude::*;

fn main() {
    unsafe {
        let mut contour = Vector::<Point>::new();
        let points = vec![
            // Point::new(0, 0),
            // Point::new(0, 10),
            // Point::new(10, 10),
            // Point::new(10, 0),
            // Point::new(0, 0),
            Point::new(5, 5),
            Point::new(5, 15),
            Point::new(15, 15),
            Point::new(15, 5),
            Point::new(5, 5),
            // Point::new(0, 0),
        ];
        for point in points {
            contour.push(point);
        }
        dbg!(bounding_rect(&contour).unwrap());
        let t = min_area_rect(&contour).unwrap();
        dbg!(t));
    }
}

This program segfaults on the last line when using latest release. Works fine on 0.56.

Operating system
popos
The way you installed OpenCV: package, official binary distribution, manual compilation, etc.
apt install libopencv-dev
OpenCV version
4.5.1
rustc version (rustc --version)
1.57.0

I'll attach build logs soon.

I cannot immediately confirm this as it works without a segfault on my dev system (Gentoo, OpenCV 4.5.5, rustc 1.57). I'll try to reproduce under your specific circumstances.

The reason for this issue is the mismatch between how Rust expects C calling convention to return a struct and how the default C++ compiler in Ubuntu 20.04 actually does. I'll rework this internally to work around the issue

This issue should now be fixed in 0.62


BC: Treat undefined and false as NOT equal

⚠ BREAKING CHANGE ⚠
Addresses #3061, #1762, #1774, and #1993.

Codecov Report

Merging #3081 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #3081   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          68      68
  Lines        1451    1477   +26
======================================
+ Hits         1451    1477   +26

Impacted Files
Coverage Δ

src/structure/plain/deepEqual.js
100% <100%> (ø)
:arrow_up:

src/createReducer.js
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

v7.0.0 incoming?? 😀

Not merging yet until I'm ready to pull the trigger, but yes. This lib needs to be more respectful of semver.

@erikras Any idea when this would be released ?

Published in v7.0.0.

@erikras shouldn't this also treat null and false as not equal. upgraded and immediately got bit by that.


General: Allow students to unenroll from courses

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[ ] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[ ] I chose a title conforming to the naming conventions for pull requests.

Server

[ ] Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
[ ] I followed the coding and design guidelines.
[ ] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[ ] I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
[ ] I documented the Java code using JavaDoc style.

Client

[ ] Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
[ ] I followed the coding and design guidelines.
[ ] Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
[ ] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
[ ] I added authorities to all new routes and checked the course groups for displaying navigation elements (links, buttons).
[ ] I documented the TypeScript code using JSDoc style.
[ ] I added multiple screenshots/screencasts of my UI changes.
[ ] I translated all newly inserted strings into English and German.

Changes affecting Programming Exercises

[ ] I tested all changes and their related features with all corresponding user types on Test Server 1 (Atlassian Suite).
[ ] I tested all changes and their related features with all corresponding user types on Test Server 2 (Jenkins and Gitlab).

Motivation and Context
If students decide against participating in a course, there is currently no way to disenroll from a course.
Resolves #334.
Description

Steps for Testing

Prerequisites:

1 Instructor
2 Students
1 Programming Exercise with Complaints enabled

Log in to Artemis
Navigate to Course Administration
...

Exam Mode Testing

Prerequisites:

1 Instructor
2 Students
1 Exam with a Programming Exercise

Log in to Artemis
Participate in the exam as a student
Make sure that the UI of the programming exercise in the exam mode stays unchanged. You can use the exam mode documentation as reference.
...

Review Progress

Performance Review

[ ] I confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[ ] I confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[ ] Code Review 1
[ ] Code Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Test Coverage

Screenshots

Codecov Report

Merging #6577 (17a0b3b) into develop (930b704) will decrease coverage by 0.03%.
The diff coverage is 58.40%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #6577      +/-   ##
=============================================
- Coverage      80.51%   80.48%   -0.03%
- Complexity     13293    13348      +55
=============================================
  Files           2362     2366       +4
  Lines          90526    90831     +305
  Branches       13355    13413      +58
=============================================
+ Hits           72885    73106     +221
- Misses          9710     9764      +54
- Partials        7931     7961      +30

Impacted Files
Coverage Δ

.../java/de/tum/in/www1/artemis/config/Constants.java
100.00% <ø> (ø)

.../de/tum/in/www1/artemis/service/CourseService.java
86.98% <0.00%> (-1.28%)
:arrow_down:

src/main/webapp/app/entities/course.model.ts
84.09% <ø> (ø)

...ebapp/app/course/manage/course-update.component.ts
73.70% <26.66%> (-2.44%)
:arrow_down:

...e/tum/in/www1/artemis/web/rest/CourseResource.java
90.10% <37.50%> (-0.64%)
:arrow_down:

...ain/java/de/tum/in/www1/artemis/domain/Course.java
78.83% <48.97%> (-6.12%)
:arrow_down:

...app/app/course/manage/course-management.service.ts
76.65% <75.00%> (-0.03%)
:arrow_down:

...iew/course-exercises/course-exercises.component.ts
85.16% <80.00%> (-0.39%)
:arrow_down:

...pp/overview/course-unenrollment-modal.component.ts
88.88% <88.88%> (ø)

...ww1/artemis/service/AuthorizationCheckService.java
77.62% <100.00%> (+2.42%)
:arrow_up:

... and 1 more

... and 31 files with indirect coverage changes

Flag
Coverage Δ

client
76.52% <65.95%> (+0.01%)
:arrow_up:

server
84.89% <53.84%> (-0.09%)
:arrow_down:

Continue to review full report in Codecov by Sentry.

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


binaryHeader: Fixed partial write issue for index-header.

Fixes https://github.com/thanos-io/thanos/issues/2213
This cause was indicated as the potential root cause for regression of latency and also causes the potentially critical issue
for store GW, where manual delete of index-header from local storage was required.
This might be considered as a blocker for 0.12, so it would be worth it to port it to 0.12 TBH @squat WDYT?
Signed-off-by: Bartlomiej Plotka<EMAIL_ADDRESS>

cc @mkabischev

if we want this in v0.12.0, should we instead PR into release-0.12?

Yes, will do with @GiedriusS fixes.

Correct me if I'm wrong, but I think we can close this as we're going to be merging this into master when we merge release-0.12 back into master no?

ack we can close this now @brancz :+1:


[UBT 16.04] for xacro builds, add inorder option and remove deps and args arguments

xacro has been updated since ROS Jade, so current xacro build commands are not working with ROS Kinetic on Ubuntu 16.04.
So, I added --inorder option and removed ${_xacro_deps_result} and ${xacro_args} like this:
https://github.com/personalrobotics/herb_description/blob/fa6702c164e9ce5321a06ffcf7d1fe7326d10599/CMakeLists.txt#L23-L24
With these changes, I was able to generate corresponding URDFs, but I am not sure this is a proper way to fix.
What are the ${_xacro_deps_result} and ${xacro_args} for on ROS Indigo?

_xacro_deps_result is the result of this execute_process, and xacro_args stores the third argument of build_xacro, which is defined in this CMakeLists.txt. For example, [build_xacro(${HERB_URDF_XACRO} ${HERB_URDF_OUTPUT} "${HERB_URDF_ARGS}")](build_xacro(${HERB_URDF_XACRO} ${HERB_URDF_OUTPUT} "${HERB_URDF_ARGS}")) passes "${HERB_URDF_ARGS}" to  xacro_args. So I think they are all necessary. Without commenting them out didn't work?

On top of the fix in CMakeLists, I removed redundant definitions of pi, so that we can build without any warnings. I checked the generated urdf and srdf files with that from 14.04, and they were technically identical.


How can I do something after a build

My loader will create some cache files while building, and I want to remove these files at the end of build.
What can I do?

You could write a plugin and then perform the cleanup at emit. See https://webpack.github.io/docs/plugins.html for the basic idea.

Of course one option is to do nothing and write to a dotfile. Or you can let the user to toggle caching behavior through a flag.


adding the optional onDayClick resource ID for resource view

Just adding in the optional resourceId described here
https://fullcalendar.io/docs/dayClick

@StickNitro
That green button just there.. pressss itttttt   :eyes:


Non-Stable Diffusion VAE for commercial usage?

Hi! Your project looks great, well done on the work so far.
Although I do open source work in my spare time, I also do image generation at work too. Lumina's MIT License is useful for commercial development, but I notice that the VAE used by Lumina is always Stable Diffusion (either 1.5, or SDXL).  I think this means that using Lumina in a released commercial product requires obtaining a commercial license from stability.ai.
Are there are plans to train or support an MIT-licensed VAE so that the whole stack can be used without licensing difficulties, even in commercial projects?

Do you have any recommendation?

I heard someone (I think it was maybe comfy) saying that training a VAE is pretty easy. I think the code for the stability.ai VAE itself is totally free to use, it's just the weights that need to be commercially licensed?
If that's true, then it should be possible to take a large number of latent outputs of your model just now, along with the images produced by using the Stable Diffusion VAE to produce the correct output images for these latents, and use these latent/image pairs to train a free-to-use VAE that's a license-free drop-in replacement for the stability.ai VAE.
In other words the procedure would be:

Generate a large number of images with random captions using the stability.ai VAE, keeping the latents too
Discard the weights for the stability.ai VAE, but keep the free-to-use code for their model structure
Retrain new VAE weights using the large number of {latent, image} pairs
Upload that somewhere for people to use, with an MIT License

Or, maybe someone's already made a license-free VAE someplace?

We are using stabilityai/sdxl-vae which has MIT license. Should this be legal?

I didn't know the SDXL VAE was MIT licensed. That's great to know, thanks @PommesPeter.


Text Field Boxes

Is there support for Material Design's Text Field Boxes currently and/or planned?
Does anyone know of any 3rd-party implementation?
One point made in the MD spec: "Text field boxes make dense layouts easier to read."
I have a dense form which looks much better when text fields are encapsulated in boxes. With some CSS tweaks I'm able to get fields in rounded-corner boxes, but the positioning of the elements inside needs more work to match the MD spec.

Have a look at the newer library, it seems to have it:
https://github.com/material-components/material-components-web/tree/master/packages/mdc-textfield


chore(main): release 1.1.0

:robot: I have created a release beep boop
1.1.0 (2024-01-01)
Features

CRUD-23 configure github package. (8472982)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/byesfi/customer-express/releases/tag/v1.1.0 :sunflower:

:robot: Release is at https://github.com/byesfi/customer-express/releases/tag/v1.1.0 :sunflower:


Fix documentation for creating Dynaconf instance

The lazy loader expects the parameters to follow the same syntax as environment variables.

Thanks for your PR, but this change is being introduced in the next release 3.0.0

Ah, well then the published docs need to be versioned somehow. Only the 'latest' is available on readthedocs but that isn't the version published on pypi.

@jhesketh sorry for the inconvenience there were some problem when releasing the docs. Thanks for your issue


Naming of --line-numbers and --no-numbers options

The --line-numbers and --no-numbers options are named inconsistently. Shouldn't they be called --[no]numbers, just like --[no]heading, --[no]break and --[no]group? I suggest keeping the oddly named cousins around.
Maybe we could print a deprecation warning to stderr, then eventually remove them in the future.

This makes sense to me. I'm not sure why I messed up those options.

Thanks for your work, looks great!


New version: Pluto v0.3.1

Registering package: Pluto
Repository: https://github.com/fonsp/Pluto.jl
Created by: @fonsp
Version: v0.3.1
Commit:<PHONE_NUMBER>048a06972f0eb3376f6cbc0317d14f
Reviewed by: @fonsp
Reference: https://github.com/fonsp/Pluto.jl/commit/0149307354048a06972f0eb3376f6cbc0317d14f#commitcomment-37769049

Does not meet sequential version number guideline: version 0.3.1 skips over 0.3.0

@fonsp Did you intend to skip a version?
[noblock]

Sorry! I did not mean to skip version.
You can close this PR, I will make sure that the next one can be auto-merged.
Thanks though!


Where to make data augmentation? the inference?

You can modify img_scales to be a list of tuple for multi-scale inference, and flip_ratio to be positive for horizontal flipping.

#135

only support 2 scale?

@spytensor The inference supports any scales.

@hellock  where to change model type  between "range" and "value"?


[stable/airflow] Support pod annotations per "pod"

Hey,
I would like to suggest a small feature change: I think it would be nice if there is support for having podAnnotations per pod. (E.g web, worker or scheduler).
This might be very useful when we automatically scrape Prometheus metrics. (E.g scheduler and flower are shown as "down" because it does not spawn a /metrics route on it. Therefore i need to exclude it then. I could provide a PR if wanted.

Any thoughts on this one?


How to refetch query from asyncData

So, i have some query fetching from asyncData:
aync asyncData ({ app, route, store }) {
    let id = route.params.id
    let apollo = await app.apolloProvider.defaultClient.query({
        query: directory,
        variables: {
            id: id
        },
        update: data => data.getDirById
    })
    let { data } = apollo
    const directoryObject = data.getDirById
    store.commit('SET_CURRENT_DIRECTORY', directoryObject)
},

after some actions in the other part of application i would like to refresh this directory, refetch() or calling query again from this.$apollo in created hook, doesn't work ... Any one can help?

will close this issue due to inactivity

I have the same issue.
Vue apollo comes with a refetch function but here I can't find a way to refetch a query!
useQuery also throw an error
Failed to resolve import "@vue/apollo-composable" from "components\homepage\Faq.vue". Does the file exist?


Adds CopyLine action, the new default action for CtrlC if cursor has no selection

I'm pretty new to writing Go so let me know if I'm missing simple things like style preferences. I've been digging into Micro and love it so far, but I'm used to CtrlC doing "Copy Line" if there's no selections, and "Copy" if there is. This didn't seem to be available yet so I took a swing at it.

Looks good! In the future I recommend using the gofmt tool to autoformat your code. Thanks for your contribution!

Thanks very much -- And yeah, I tried running gofmt and it froze and locked up my terminal. I'll need to dig into that and figure out why. Cheers!


[WIP] Migrate to External PINOperation

PINOperation now has its own home at https://github.com/pinterest/PINOperation and so PINCache needs to bring it in as a dependency.
This also renames Coallescing to Coalescing, so we can get the name changed before the release.

Last failure:
-> PINCache (3.0.1-beta.2)
- ERROR | [PINCache/Core,PINCache/Arc-exception-safe] file patterns: The source_files pattern did not match any file.

@garrettmoon I think the spec lint is failing because it's using the new spec but the old code – that is, it pulls down the 3.0.1-beta.2 tag and tries to validate this spec against that version of the repo, which won't work.

It looks like the build_tests.sh script no longer works. I'm not sure this is valuable at this point anyway. Mind removing?

Thanks so much for the cleanup @Adlai-Holler !


v2.5.2 regression? scrambled text

Hello. I found a difference in former tview code against new one reported here: tview issue 853
My platform:
go version go1.19.5 linux/386
Linux  4.4.0-210-generic #242-Ubuntu SMP Fri Apr 16 09:57:00 UTC 2021 i686 i686 i686 GNU/Linux

Inspecting more I found the difference is in tcell code by running:
tcell/_demos/mouse.go

Last version working for me is the v2.5.1
require (
	github.com/gdamore/tcell/v2 v2.5.1
	github.com/mattn/go-runewidth v0.0.13
)

require (
	github.com/gdamore/encoding v1.0.0 // indirect
	github.com/lucasb-eyer/go-colorful v1.2.0 // indirect
	github.com/rivo/uniseg v0.2.0 // indirect
	golang.org/x/sys v0.0.0-20220318055525-2edf467146b5 // indirect
	golang.org/x/term v0.0.0-20201210144234-2321bbc49cbf // indirect
	golang.org/x/text v0.3.7 // indirect
)

First version not working is the v2.5.2 (up to the 2.6.0):
require (
	github.com/gdamore/tcell/v2 v2.5.2
	github.com/mattn/go-runewidth v0.0.13
)

require (
	github.com/gdamore/encoding v1.0.0 // indirect
	github.com/lucasb-eyer/go-colorful v1.2.0 // indirect
	github.com/rivo/uniseg v0.2.0 // indirect
	golang.org/x/sys v0.0.0-20220318055525-2edf467146b5 // indirect
	golang.org/x/term v0.0.0-20201210144234-2321bbc49cbf // indirect
	golang.org/x/text v0.3.7 // indirect
)

Thanks.

Can you provide details about what terminal your using?
It looks like perhaps we are issuing some extended commands that your terminal might not understand.

In three systems I have xterm-256color
In two "old" computers I have the problems:

ARM 32 bits
Linux 3.10.0 #1 SMP PREEMPT Thu Feb 25 02:51:25 HKT 2016 armv7l GNU/Linux

Ubuntu 16.04 32 bits
Linux 4.4.0-210-generic #242-Ubuntu SMP Fri Apr 16 09:57:00 UTC 2021 i686 i686 i686 GNU/Linux

In a newer one everything is normal:

Ubuntu 22.04 64 bits
Linux 5.19.0-42-generic #43~22.04.01-Ubuntu SMP PREEMPT_DINAMIC x86_64

Please, tell me how to get more info from the terminals (details), though seems to me, some code was "removed" which worked with old systems. My old versions were cross-compiled from go linux to windows (exe), and windows console works ok.

Is this "real" xterm? Or a clone like gnome-terminal or something?

I don't think anything was removed. Rather I think we started making some assumptions which might not hold true.
You could possibly work around this by putting TERM=xterm in your environment though you would only get 16 colors in that case.

Same thing
I tested mouse.go for version v2.5.2 setting TERM for each of the following list:
ls /lib/terminfo/x/
xterm  xterm-256color  xterm-color  xterm-debian  xterm-mono  xterm-r5  xterm-r6  xterm-vt220  xterm-xfree86

as TERM=XXX go run mouse.go but without success.
Workaround
TERM=vt100 go run mouse.go
and
TERM=vt220 go run mouse.go
both give clean displays though colorless. As for me, is OK such workarounds preferring the fullest features than color since my apps are intented to be used by SSH in small linux boxes. In fact, the goodness of tcell/tview is the ability to configure remote headless linux boxes skipping complicated web server/client pages.
I'll continue testing latest versions and more terminals. Thanks.

Even though VTxxx is to simple to aside mouse, give tabs and reverse colors as reference for a GUI... more to investigate...

TERM=linux
For linux-arm 32 bits, do the trick (color, mouse ok) for latest:
require (
	...
	github.com/gdamore/tcell v1.4.0
	github.com/rivo/tview v0.0.0-20230525073430-4a1f85bb2219
)

require (
	...
	github.com/gdamore/encoding v1.0.0 // indirect
	github.com/gdamore/tcell/v2 v2.6.0 // indirect
	github.com/lucasb-eyer/go-colorful v1.2.0 // indirect
	github.com/mattn/go-colorable v0.1.12 // indirect
	github.com/mattn/go-isatty v0.0.14 // indirect
	github.com/mattn/go-runewidth v0.0.14 // indirect
	github.com/rivo/uniseg v0.4.3 // indirect
	github.com/rs/xid v1.4.0 // indirect
	github.com/rs/zerolog v1.28.0 // indirect
	golang.org/x/net v0.10.0 // indirect
	golang.org/x/sync v0.0.0-20220929204114-8fcdb60fdcc0 // indirect
	golang.org/x/term v0.8.0 // indirect
	golang.org/x/text v0.9.0 // indirect
	gopkg.in/yaml.v3 v3.0.1 // indirect
)

Yep, if you're on the Linux console, then TERM=linux is the way to go.  Everything else is Just Wrong.

I'm closing this as there is nothing else for us to do here.


Enhanced Query Export is no longer including all of the fields from the query - eg. Description

We've been using Enhanced Query Export for months without any issues. It's no longer including all of the fields from the Queries.

I think you are in the wrong place this is for the wiql editor not the Enhanced Export extension.


fix changelog hyperlink

Signed-off-by: jonahjon<EMAIL_ADDRESS>Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherrypick main

/lgtm
/approve

should we change this to main branch too?


Add horisontal scroll bar to model browser

Is your feature request related to a problem? Please describe.
It is not possible to read full values that are larger than the model browser box, at least on Chrome (MacOS)
Describe the solution you'd like
Add horisontal scroll bar

This is strange, because I do have horizontal scrollbar there: https://vimeo.com/367229679
What version of Chrome are you using? I have: Version 77.0.3865.120 (Official Build) (64-bit)

Google Chrome is up to date
Version 77.0.3865.120 (Official Build) (64-bit)

High sierra OS

I get horisontal scroll bars in your example also! But try the original Blueprint_Hub, data->SAMPLE_ONTOLOGY_URI

I have it there as well 🤷♂

Strange. Probably some OS issue. You can close the issue, I think.


Help:  The download of leftImg8bit_ sequence_trainvaltest.zip dataset is interrupted!!

Hello, I use Microsoft edge browser to download leftImg8bit_sequence_trainvaltest.zip on the official website. For some reasons, I click Pause to continue downloading the zip dataset. However, I found that the server network failed and it could not be downloaded. Does anyone know how to handle this and continue downloading?
Or, for the 324GB dataset, whether it can be split into multiple datasets. One time downloading is prone to some problems that lead to download failure, thank you!

Hi @zhe-juanz
if you have got the "leftImg8bit_sequence_trainvaltest" dataset, could you share just the "validation" split of it with me, please?
Let me know if it's possible for you to share a download link with me on my email


your extension doesn't show up in my launcher!!

the only warning that shows in my console when opening my jupyter lab is
[W 01:52:37.919 LabApp] The extension "jupyterlab-sql" is outdated.

I'm running
Jupyter lab version : 2.2.6
Jupyterlab-SQL version: 0.3.3
how can I solve this issue please?

I have same problem, have no idea how to troubleshoot

the same here

same

same issue


2.5 --> 2.6: backwards incompatible change in MalformedCSVError#new

In Ruby 2.5, CSV::MalformedCSVError simply inherited from RuntimeError. In 2.6, it defines its own #new, taking 2 arguments (as opposed to the single argument of RuntimeError).
Code explicitly raising new errors of this class outside of the CSV library implementation itself breaks since it doesn't include the second argument (a line number).
Is making the line number optional something you'd entertain?

Could you show codes that creating CSV::MalformedCSVError?

@kou just this:
    def raise_malformed_csv_error
      raise CSV::MalformedCSVError
    end

with 2.6 ruby it's raised this:
     Failure/Error: raise CSV::MalformedCSVError

     ArgumentError:
       wrong number of arguments (given 0, expected 2)

because of this:
  class MalformedCSVError < RuntimeError
    attr_reader :line_number
    alias_method :lineno, :line_number
    def initialize(message, line_number)
      @line_number = line_number
      super("#{message} in line #{line_number}.")
    end
  end

Thanks.
One more question. Why do you want to raise CSV::MalformedCSVError manually?

Thanks.
It seems that it's an application specific error and it's not a general CSV error. So you should use your own error class instead of reusing CSV::MalformedCSVError.

@kou  okay, thanks, I will take note and we will discuss it with colleagues. We've just got this error while ruby update. Now we'got how to resolve it. Thank you

OK. I close this.


The specified key is not present in this container.

Hello aayushbansal,
Thanks for sharing your code!
I installed the caffe version in tool folder and then try to run demo_code.m.
But I got the following error. Do you have any idea about this?

Image : ./experiments/demo/img_000001.jpg
Error using containers.Map/subsref
The specified key is not present in this container.
Error in caffe.Net/blobs (line 77)
blob = self.blob_vec(self.name2blob_index(blob_name));
Error in demo_code (line 53)
net.blobs('data0').reshape([crop_height+200, crop_width+200, 3, 1]);
Error in run (line 96)
evalin('caller', [script ';']);

Thanks for the pointer! I have made the edit. Now it should work.

Thanks a lot!


Bold resets previous color

Depending on order and type of operations, bold causes a previously set color to be suppressed:

chalk.bold("foo") => '\u001b[1mfoo\u001b[22m'
chalk.blue.bold("foo") => '\u001b[94m\u001b[1mfoo\u001b[22m\u001b[39m'
chalk.bold.blue("foo") => '\u001b[1m\u001b[94mfoo\u001b[39m\u001b[22m'
chalk.bold.hex("#0000ff")("foo") => '\u001b[1m\u001b[38;2;0;0;255mfoo\u001b[39m\u001b[22m'
chalk.hex("#0000ff").bold("foo") => '\u001b[38;2;0;0;255m\u001b[1mfoo\u001b[22m\u001b[39m'

The screenshot above was taken on Windows 10 1709 (Enterprise) using Node v10.13.0 through winpty 0.4.3 in mintty 2.8.1 installed with Git for Windows. Running node via Powershell or cmd yields identical ANSI sequences and similar results, as far as the coloration of the last sample is concerned, e.g.:

Running node via Powershell or cmd yields identical ANSI sequences and similar results, as far as the coloration of the last sample is concerned, e.g.:

I think you answered your own question there - this is a bug with mintty, not Chalk.

Hm, maybe I didn't express myself clear enough. Sorry.
Running the tests in other consoles produces the same ANSI sequences as in mintty; those same ANSI sequences produce the same and incorrect colors; mintty, cmd and PowerShell behave the same. (Or rather, they behave comparably; e.g., bold + hex yields bright yellow text in PowerShell, likely because that's PowerShell's default prompt color; that result is independent of the value passed into hex(), at least.)
Also, note that in the second image the last two test strings are unfortunately flipped, but both images - mintty and cmd - show that

bold + hex → non-bold, correct color
hex + bold → bold, incorrect color

I do agree, however, that this probably isn't a bug in chalk, but an odd quirk in how the Windows terminal chooses to interpret those color changes. Also, I'm assuming that there's a general consensus that preserving the color information is more important than preserving the boldness, so chalk may want* to implement some workaround.

Sorry, should have looked closer. The codes are correct, I believe Microsoft has fixed a lot of these.
See visionmedia/debug#683 for something quite similar, if not the same.

Closing as this is not actionable for us and it's not something we're interested in working around. Instead, open an issue on the relevant terminals.


Fixes foreign characters like 'æ', 'ø' and 'å'.

Hi,
This is a quick fix for foreign characters.
I read that its best to escape non-ansi characters by using createTextNode() to get properly escaped strings in XML. I am not sure if that is neccessary here though.

Thanks


feat: Patch notes

Display Northstar release notes in application.

TODOs

[x] Scrollbar
[x] Keep menu visible when scrolling
[x] Dates style (use dark theme?)
[x] Display a loader while fetching notes
[x] Ensure HTTP call is not done on main thread

Actually it would also be really nice if we could add contributor github profile pic (or replace name with it) but that should be its own PR after this one has been merged so as to not delay this PR too much ^^

Just noticed it also doesn't do some image embeds properly yet. No clue what's going on with this one in particular ^^

Just noticed it also doesn't do some image embeds properly yet. No clue what's going on with this one in particular ^^

Good point, the second regex seems to capture Markdown images while it shouldn't.

Squash merging due to large number of commits.


timm version not compatible with torch version

Describe the bug
A torch version conflict with timm. Timm 0.9.2 use torch.frombuffer() function which is developed after torch version 1.13.
To Reproduce

torch version 1.8.1

from timm import create_mdoel
model = create_model("densenet121", pretrained=True)

Expected behavior
provide a document about timm version and its campatible torch version
Desktop (please complete the following information):

OS: [Ubuntu 18.04]
PyTorch version: 1.8.1+cu10.1

Additional context
AttributeError: module 'torch' has no attribute 'frombuffer'

@perspicacitee there is not an explicit call to frombuffer anywhere in timm, so would need to see a full callstack to see what's going on, but sounds like a module mismatch (torchvision vs torch not aligned?) I don't know how else it could be called.
It's hard to say exactly what the minimum torch version is, there are a lot of models that will work with older version, and some functionality/models need newer, defining a hard cutoff would be challenging, enforccing a version would prevent some people from using subsets of the library that work fine.
In general though, I'm likely gaurantee ~18 months of torch version compat, so around 1.10 at this point.


Questions about writing data to the stream

Should I call the lsquic_stream_write function to write data or cache the data in the buffer, and then write through the on_write callback？

Should I call the lsquic_stream_write function to write data or cache the data in the buffer, and then write through the on_write callback？

on_write is an event which tell you that you can write data to lsquic stack by lsquic_stream_write.

How to ensure that all data has been sent out when the stream is closed？

I want to write 62696 bytes of data to the stream, the on_write event is only called once, and lsquic_stream_write returns 46382. Calling lsquic_stream_wantwrite and lsquic_engine_process_conns again will not work.

It is event driven, call lsquic_engine_process_conns immediately wont make it happen. you have to register the event and wait for the event in a event loop. on_write event will happen once those buffered data has been flushed out,

The return value of lsquic_stream_write represents the actual data sent. Does the remaining data need to be sent in the next on_write callback?

yes.


I can't pull the docker image referred to

I tried to run: $ docker run -d -p 9080:80 -v answer-data:/data --name answer apache/incubator-answer:all-in-one and got the following error:
Unable to find image 'apache/incubator-answer:all-in-one' locally
docker: Error response from daemon: pull access denied for apache/incubator-answer, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
Might be a noob question, but, any help here?

see https://hub.docker.com/r/apache/answer/tags
The image name should be apache/answer, not apache/incubator-answer
The all-in-one tag has not been built yet.
If you're in a hurry, you can use: https://hub.docker.com/r/answerdev/answer/tags?page=1&name=all-in-one

@sy-records @LinkinStars thanks guys. Will try it in the morning.

see https://hub.docker.com/r/apache/answer/tags
The image name should be apache/answer, not apache/incubator-answer The all-in-one tag has not been built yet.
If you're in a hurry, you can use: https://hub.docker.com/r/answerdev/answer/tags?page=1&name=all-in-one

@mrprofessork Just as he(@sy-records ) said. But we'll be building new docker image and pushing it to the apache repository ASAP.

Is there any plan to push v1.2.1 of all-in-one?


ComfyUI -  No module named 'skimage' 'cv2' etc.

Hi i have problem with : No module named 'skimage'
[comfyui_controlnet_aux] | INFO -> Using ckpts path: C:\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_controlnet_aux\ckpts
[comfyui_controlnet_aux] | INFO -> Using symlinks: False
[comfyui_controlnet_aux] | INFO -> Using ort providers: ['CUDAExecutionProvider', 'DirectMLExecutionProvider', 'OpenVINOExecutionProvider', 'ROCMExecutionProvider', 'CPUExecutionProvider']
Full error log from comfyui_controlnet_aux:
Traceback (most recent call last):
File "C:\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_controlnet_aux_init_.py", line 32, in load_nodes
module = importlib.import_module(
^^^^^^^^^^^^^^^^^^^^^^^^
File "importlib_init_.py", line 126, in import_module
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1147, in _find_and_load_unlocked
File "", line 690, in _load_unlocked
File "", line 940, in exec_module
File "", line 241, in call_with_frames_removed
File "C:\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_controlnet_aux\node_wrappers\dwpose.py", line 5, in
from controlnet_aux.dwpose import DwposeDetector, AnimalposeDetector
File "C:\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_controlnet_aux\src\controlnet_aux\dwpose_init.py", line 19, in
from .hand import Hand
File "C:\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_controlnet_aux\src\controlnet_aux\dwpose\hand.py", line 10, in
from skimage.measure import label
ModuleNotFoundError: No module named 'skimage'
[comfyui_controlnet_aux] | INFO -> Some nodes failed to load:
Failed to import module dwpose because ModuleNotFoundError: No module named 'skimage'
Check that you properly installed the dependencies.
If you think this is a bug, please report it on the github page (https://github.com/Fannovel16/comfyui_controlnet_aux/issues)
The way i got rid of it was by forcing ComfyUI using this command : ..\python_embeded\python.exe -s -m pip install --upgrade --pre torch torchvision torchaudio opencv-python matplotlib skimage scikit-image simpleeval --extra-index-url https://download.pytorch.org/whl/nightly/cu121 -r ../ComfyUI/requirements.txt pygit2
I checked your install.bat file and requirements.txt but it looks like some requirements are missing and when i want to install them they do not want to be installed when i edit requirements.txt. So i had to force : update_comfyui_and_python_dependencies.bat to install the, for me.
Hope it will help everyone who have problem with this.

I used your method but it still didn't work out and it seems that something is not installed
code
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [3 lines of output]
  *** Please install the `scikit-image` package (instead of `skimage`) ***

  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Hi,
I faced some pretty similar issues, maybe this will help :  #371


GDScript 2.0: Defining a variable inside a for loop does not reset its value back to null each iteration

Godot version
4.0.beta2.official
System information
Windows 10, Vulkan, RTX 2060
Issue description
This code produces the following result in Godot 4 Beta 2:
func _ready() -> void:
    for i in 10:
        var x
        if i == 5:
            x = 1
        print(x)

<null>
<null>
<null>
<null>
<null>
1
1
1
1
1

As you can see, the value assigned to x is persisting between iterations, even though the variable is being redeclared inside the loop. I was surprised by this, as normally I would declare x outside the loop if I wanted its value to be persistent.
Running the same code on Godot 3 produces the result I was expecting, redefining x brings its value back to null.
Tested on Godot 3.5.1 Stable:
Null
Null
Null
Null
Null
1
Null
Null
Null
Null

Steps to reproduce

Run the code snippet on Godot 4 and Godot 3 and compare the outputs.

Minimal reproduction project
No response

Duplicate of #56223.

Closed as a duplicate of https://github.com/godotengine/godot/issues/56223.


Update README.md

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

/close


Review content to make sure it matches the latest versions

@kysrpex I have done a general read and dealt with most of the warnings being shown in the build process.
The remaining ones come from the api ref, so I do not think they should be tackled here (but in the actual docstrings). I briefly tried to silent them, but did not manage.
I would hand over to you now, ping me if you need anything

Regarding black and isort, I run into some issues with pre-commit in another project, this is the configuration that worked in the end:

    - repo: https://github.com/psf/black
      rev: 22.3.0
      hooks:
          - id: black
            args:
                - --line-length=79

    - repo: https://github.com/pycqa/isort
      rev: 5.10.1
      hooks:
          - id: isort
            args:
                - --profile=black
                - --filter-files
                - --line-length=79

Leaving it here so we can apply it next week :)

@kysrpex this has not been applied, has it?
Maybe we can just push the change to dev

@kysrpex this has not been applied, has it?
Maybe we can just push the change to dev

When you commented I was going to make a new PR, but it seems that it is already on dev.

I seem to remember that syntax did not work as it should for me. That is why I suggested the alternative above.

I seem to remember that syntax did not work as it should for me. That is why I suggested the alternative above.

Then if you remember what was not working we make a PR. I do not remember :sweat_smile: .


refactor: use ternaries rather than && in JSX

To make @kentcdodds happy
https://kentcdodds.com/blog/use-ternaries-rather-than-and-and-in-jsx

Same as #536

Also, docs and examples changes can happen in main unless they depend on unreleased changes.


Extract code snippets from working-with-notes-slides.md

Extract the code snippets from docs/presentation/working-with-notes-slides.md and use docfx snippets to retrieve them from the samples folder and audit the text.

closing as duplicate


Make the ImageCanvas.canvasFunction asynchronous

The ImageCanvas.canvasFunction is synchronous, making it really hard to work with in async environment.
It seems the call, bind, apply functionality being used in the to call the canvasFunction, is not capable of running asynchronously.
It would be great to have the option to run an asynchronous function using promises and async / await.
The feature have already been suggested in #8027 but was marked as stale due to inactivity.
I would like to help out, but would need some help doing so i'm afraid.

Any help ?


File path inconsistency

Hey,
I've just noticed an inconsistency between linux and windows, windows seems to just have the filename in the callback filepath, where linux has the full file path.
What is the desired behaviour?
Thanks,
Wayne

oh no!
expected behavior is to give you relative paths, that's why we have rootdir argument in the callback.
check out the latest commit 48234fc2a42e699b7f210df994ecbdb95bffb846, I fixed it for linux. probably more testing needs to be done.


minor formatting change to test pep8speaks

this should trigger pep8speaks

Hello @sauln! Thanks for submitting the PR.

In the file kmapper/kmapper.py, following are the PEP8 issues :

Line 20:80: E501 line too long (82 > 79 characters)
Line 40:80: E501 line too long (88 > 79 characters)
Line 51:80: E501 line too long (89 > 79 characters)
Line 65:51: E712 comparison to False should be 'if cond is False:' or 'if not cond:'
Line 75:80: E501 line too long (80 > 79 characters)
Line 82:9: E741 ambiguous variable name 'l'
Line 84:13: E741 ambiguous variable name 'l'
Line 93:80: E501 line too long (83 > 79 characters)
Line 99:80: E501 line too long (96 > 79 characters)
Line 100:80: E501 line too long (87 > 79 characters)
Line 107:80: E501 line too long (90 > 79 characters)
Line 119:80: E501 line too long (109 > 79 characters)
Line 123:80: E501 line too long (82 > 79 characters)
Line 130:80: E501 line too long (82 > 79 characters)
Line 138:80: E501 line too long (96 > 79 characters)
Line 163:80: E501 line too long (87 > 79 characters)
Line 173:17: E722 do not use bare except'
Line 177:9: E722 do not use bare except'
Line 207:80: E501 line too long (92 > 79 characters)
Line 208:80: E501 line too long (84 > 79 characters)
Line 214:80: E501 line too long (95 > 79 characters)
Line 231:80: E501 line too long (128 > 79 characters)
Line 232:80: E501 line too long (89 > 79 characters)
Line 235:80: E501 line too long (85 > 79 characters)
Line 239:80: E501 line too long (84 > 79 characters)
Line 240:80: E501 line too long (101 > 79 characters)
Line 241:80: E501 line too long (87 > 79 characters)
Line 243:80: E501 line too long (90 > 79 characters)
Line 253:80: E501 line too long (111 > 79 characters)
Line 267:80: E501 line too long (88 > 79 characters)
Line 279:80: E501 line too long (81 > 79 characters)
Line 300:80: E501 line too long (84 > 79 characters)
Line 301:80: E501 line too long (104 > 79 characters)
Line 307:80: E501 line too long (119 > 79 characters)
Line 314:80: E501 line too long (90 > 79 characters)
Line 316:80: E501 line too long (82 > 79 characters)
Line 334:80: E501 line too long (81 > 79 characters)
Line 368:19: E711 comparison to None should be 'if cond is None:'
Line 371:80: E501 line too long (100 > 79 characters)
Line 375:80: E501 line too long (117 > 79 characters)
Line 380:80: E501 line too long (114 > 79 characters)
Line 381:80: E501 line too long (115 > 79 characters)
Line 382:80: E501 line too long (102 > 79 characters)
Line 390:80: E501 line too long (90 > 79 characters)
Line 396:80: E501 line too long (87 > 79 characters)
Line 414:80: E501 line too long (87 > 79 characters)
Line 415:80: E501 line too long (107 > 79 characters)
Line 417:80: E501 line too long (91 > 79 characters)
Line 418:80: E501 line too long (95 > 79 characters)
Line 419:80: E501 line too long (99 > 79 characters)
Line 420:80: E501 line too long (84 > 79 characters)
Line 422:80: E501 line too long (106 > 79 characters)
Line 423:80: E501 line too long (110 > 79 characters)
Line 427:80: E501 line too long (102 > 79 characters)
Line 428:80: E501 line too long (106 > 79 characters)
Line 450:26: E712 comparison to False should be 'if cond is False:' or 'if not cond:'
Line 455:22: E712 comparison to False should be 'if cond is False:' or 'if not cond:'
Line 460:23: E712 comparison to False should be 'if cond is False:' or 'if not cond:'
Line 469:80: E501 line too long (105 > 79 characters)
Line 477:80: E501 line too long (91 > 79 characters)
Line 478:80: E501 line too long (139 > 79 characters)
Line 479:80: E501 line too long (85 > 79 characters)
Line 480:80: E501 line too long (216 > 79 characters)
Line 481:80: E501 line too long (189 > 79 characters)
Line 496:80: E501 line too long (85 > 79 characters)
Line 501:80: E501 line too long (173 > 79 characters)
Line 516:80: E501 line too long (116 > 79 characters)
Line 553:80: E501 line too long (324 > 79 characters)
Line 556:80: E501 line too long (361 > 79 characters)
Line 571:80: E501 line too long (83 > 79 characters)


fix delete namespace error

What type of PR is this?
/kind bug
What this PR does / why we need it:
delete namespace sometimes fail
Which issue(s) this PR fixes:
Fixes #https://github.com/kubernetes/perf-tests/issues/2081
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/easycla

/easycla


What is the current policy on security updates for past versions

Type of question
Are you asking about community best practices, how to implement a specific feature, or about general context and help around the operator-sdk?
Question
What did you do?
I have read the security policy page, but I am still unsure of what it means currently with the major version being 0 right now. For example, I have been using the v0.17.0 helm-operator base image here, and I am refraining from upgrading to v0.19.0 because there are several breaking changes. I see that there is a newer v0.17.2, but how long will v0.17.x keep being updated? Specifically, how long will the version keep getting updates to fix security vulnerabilities reported in the underlying OS that the image is based on?
What did you expect to see?
A clear and concise description of what you expected to happen (or insert a code snippet).
What did you see instead? Under which circumstances?
A clear and concise description of what you expected to happen (or insert a code snippet).
Environment

operator-sdk version:
insert release or Git SHA here

Kubernetes version information:
insert output of kubectl version here

Kubernetes cluster kind:

Additional context
Add any other context about the question here.

Hi @bitscuit,
The Backport Policy is described here. Usually, only very critical issues are backported. Also, it is just done to the most recent release which means -1.
Note that it, if the fix that you are looking for was solved just for upper versions of Helm I am afraid that would not be possible to provide them for 0.17.x. And then, see that the breaking changes from 0.17 to 0.19 valid for Helm-based Operators are related to the Helm itself.
Could you please let us know more in order to help you with? What is the fix that you are looking for to patch in the 0.17.x? Do you need auto migration of Helm v2 releases because of this you cannot upgrade your project? If yes,
not that it does NOT affect support for v2 Helm charts, which are still supported by Helm v3.

I'm not looking for any specific fixes to 0.17.x. I was just curious about whether the image will be updated to fix package security vulnerabilities reported in the security scan https://quay.io/repository/operator-framework/helm-operator?tag=latest&tab=tags.

Hi @bitscuit,
Ok. It depends on the scenario as described above. Please, feel free to attend the bug triage meeting to discuss your needs. Also, since you are speaking over security vulnerabilities then, I will not ask for you be specific and describe it. However, please feel free to reach out us in the Slack channel to seek further information as well.
I am closing this one as. sorted out. However, please feel free to ping us if you think. that would be required re-open it.


Delete evaluator modal is light in dark mode

Hi @aakrem, I had made changes for this. Can you please assign this to me?
This issue is fixed based on this https://ant.design/docs/blog/why-not-static#hooks.

This is the PR https://github.com/Agenta-AI/agenta/pull/1431
@aakrem

Hey @VenkataRavitejaGullapudi
Thanks for the PR 🙌  we will have a look today!

Okay. Let me know if anything. 🙂

Done thanks to @VenkataRavitejaGullapudi


Review Blocking Code in Plans

As discussed with @DominicOram and @dperl-dls, the Artemis plans currently contain long-running blocking code, such as waiting for results from Zocalo.
This makes offline mocking difficult and potentially doesn't play well with asyncio. Ideally we would like a solution involving Bluesky messages. Something along the lines of:
yield from bps.wait("zocalo")

This issue is for reviewing possible solutions and places where they may be needed in existing code.

See also https://github.com/DiamondLightSource/python-artemis/issues/597

I think we can probably get the callback to return a Future and so use bps.wait_for


Feature/lint

Codecov Report

Merging #81 into develop will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           develop    #81   +/-   ##
======================================
  Coverage      100%   100%
======================================
  Files           20     20
  Lines          389    389
  Branches        33     33
======================================
  Hits           389    389

Impacted Files
Coverage Δ

src/state-machine/linked-state-type.ts
100% <ø> (ø)
:arrow_up:

src/state-machine/active-state.ts
100% <ø> (ø)
:arrow_up:

src/interface.ts
100% <ø> (ø)
:arrow_up:

...rc/state-machine/type-wrapper/string-state-type.ts
100% <ø> (ø)
:arrow_up:

src/state-meta/index.ts
100% <100%> (ø)
:arrow_up:

src/state-machine/map-builder.ts
100% <100%> (ø)
:arrow_up:

src/state-machine/type-getter/named-type-getter.ts
100% <100%> (ø)
:arrow_up:

src/state-machine/type-getter/index.ts
100% <100%> (ø)
:arrow_up:

src/state-machine/index.ts
100% <100%> (ø)
:arrow_up:

src/state-meta/meta-state-action.ts
100% <100%> (ø)
:arrow_up:

... and 6 more

Continue to review full report at Codecov.

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


Update self-service opportunities on service blueprint

User story
As an RS teammate, I want to update the self-service opportunities at each step of the ReportStream Universal Pipeline process, so that I can better reflect where the team could strategize to implement improvements.
Background & context
@jsutantio and @dylansmith-Nava conducted a major overhaul of the initial COVID service blueprint which can be found in this Mural. As the ReportStream team migrates ReportStream to the Universal Pipeline (UP), the blueprint now needs to be updated to show UP processes and reflect the "delta" from COVID processes.
We will need to show 1 initial scenario (as other major scenario [Migrating from COVID to UP] has too many unknowns):

Scenario 1: Onboarding straight to the UP

Working links

COVID Service blueprint This is the service blueprint mural that has been widely distributed and linked to.
Service blueprint Workspace This is the temporary space that contains drafts and in progress work.
Interest & Intake Self-Service Opportunities Mural This is WebEx Mural that focuses on the "Intake" section and opportunities there

Acceptance criteria

[x] Update self-service opportunity content as needed
[x] Add internal self-service improvements where possible
[ ] Share-out to scrum team

Not within scope:

Precise timing/ durations for each step
Documenting "before onboarding" steps (e.g., patient testing/ test submission)
Documenting "post onboarding" step specificities (e.g., specific bugs and errors during maintenance, etc.)
Conceptual features, wireframes, etc. based on opportunity areas

Sharing out with designers for approval. Should be done by EoW.

Moving to done and will make a new ticket if I need to update a new version with feedback! CC @chinelo-ikejimba @brandonnava
Link: https://app.mural.co/t/primedatainput6410/m/nava4113/1681488534126/acccd696c031a19d3335e62204ece296ef483b9e?sender=ufb3824a0e63fafb0304f5774


PHP not supported?

Even PHP comments not supported?

You can add PHP into the settings file and it will spell check.  But it will check the entire doc unless you add a regexp to ignore the non commented text see issue #20


Crash with pointer being freed was not allocated in SNUnit

I didn't try yet to reproduce on a smaller example.
Non-minimal reproduction
// server.sc
//> using platform "scala-native"
//> using lib "com.github.lolgab::snunit::0.2.4"
//> using lib "com.github.lolgab::snunit-async-epollcat::0.2.4"
//> using lib "com.armanbilge::epollcat::0.1.2"

import snunit._

AsyncServerBuilder
  .build(_.send(StatusCode.OK, "Hello!", Seq.empty))

#!/bin/bash

scala-cli package -f server.sc

curl --unix-socket /usr/local/var/run/unit/control.sock -XPUT -d '
{
  "applications": {
    "app": {
      "type": "external",
      "executable": "./server",
      "limits": {
        "requests": 2
      }
    }
  },
  "listeners": {
    "*:8082": {
      "pass": "applications/app"
    }
  }
}
' http://localhost/config

how to run
# in a terminal with pwd on the same dir where server.sc is
unitd --log /dev/stdout --no-daemon

# in another terminal
./deploy.sh

curl localhost:8082/hello
curl localhost:8082/hello
curl localhost:8082/hello

After the third request we receive the quit_t event from NGINX Unit which should make the process end gracefully and make Unit create a new one, but with epollcat I get this log in NGINX Unit:
server(68567,0x113118600) malloc: *** error for object 0x7f94df808200: pointer being freed was not allocated
server(68567,0x113118600) malloc: *** set a breakpoint in malloc_error_break to debug

And then it doesn't respond anymore.
The server behaves normally with scala-native-loop

This is the only call to free in epollcat.
https://github.com/armanbilge/epollcat/blob/911d61eadb8f956b2629d9613400e2c7a2895990/core/src/main/resources/scala-native/socket.c#L63-L64
So it's not really obvious to me what's going on :)


Queue item with state

In the spirit of batching things, this now allow returning cursors as part of the Lock response.

@aviau @mlefebvre


google oauth setup

This is a DRAFT, and not tested
Upgrading from the faked credentials in #4. This switches over to using google oauth over a hardset user/pass.

[x] Add a "sign in through google" page
[x] only allow @bu.edu emails
[ ] Create TSX components to allow sign in functionality

[ ] Add sign in/profile at the top of every user page
[ ] Add a profile page so users can set their preferences, if they are signed in
[ ] Add logout functionality (switch accounts?)

[ ] Fully complete walk through of auth

I have another exam tomorrow, but during class I'll see if I can get auth fully working. Then I can spend some time on making some actual functionality.


Release to Melodic and ROS2?

Hi @fsuarez6, I think this repo is a great work that should be well recognized to wider community. Recently I made an effort to make this repo working as a plugin to MoveIt community. Please see the PR in MoveIt. And I also ported it to ROS2 in my fork. Do you still consider releasing it to Melodic, and welcoming a porting to ROS2 PR? I would be very happy to contribute.

Sounds like a good idea. I'll release this package and it's dependencies into Melody this weekend.
I shall add some comments to the moveit PR afterwards.

@fsuarez6 Thanks!

Created the release PRs:

baldor: https://github.com/ros/rosdistro/pull/23184
criutils: https://github.com/ros/rosdistro/pull/23185
handeye: https://github.com/ros/rosdistro/pull/23186

Created the release PRs:
baldor: ros/rosdistro#23184
criutils: ros/rosdistro#23185
handeye: ros/rosdistro#23186


Refresh button not updating for deleted kernels

Testing #11963
If the kernel picker can update while it's open, is the refresh button still needed?

Yes, e.g if you delete/create a conda or virtual env outside vscode, then it might not necessarily appear here.
after all we rely on file monitoring and thats not guaranteed to work 100% of the time
At that point refresh is the only way to get things updated.

When I delete a venv via the terminal, then click refresh, it's actually still there

I close and reopen the kernel picker, then it appears

@roblourens didn't you mean then it disappears

I guess so, I don't quite remember what I was seeing sorry


 If I'm not wrong, the permission error for the second command (after the '&&') will still persist.
Can i work on this issue?

@makalaaneesh sure!

Can I close this issue?

Yes, I think

Yup!


Fixed typos in Button Coloring section of Foundation Docs

Description

...

Closes

Types of changes

[ ] Documentation
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (anything that would change an existing functionality)
[ ] Maintenance (refactor, code cleaning, development tools...)

Checklist

[ ] I have read and follow the CONTRIBUTING.md document.
[ ] The pull request title and template are correctly filled.
[ ] The pull request targets the right branch (develop or develop-v...).
[ ] My commits are correctly titled and contain all relevant information.
[ ] I have updated the documentation accordingly to my changes (if relevant).
[ ] I have added tests to cover my changes (if relevant).

Hi @cdang3, thanks for your PR. Please amend it and change the title of the commit to describe what it does.

Hi @DanielRuf, I have changed the title of the commit.

What exactly do you mean with typos?
Do you ,ean that the !default is not needed?
Keeo in mind that this is standard Sass.

https://sass-lang.com/documentation/file.SASS_REFERENCE.html#variable_defaults_default
PS: The commit message is still not changed.

Yes, when I had !default in my Sass file, it did not work for me so I thought it was a typo. If not, then please ignore.

See https://foundation.zurb.com/sites/docs/button.html#custom-colors

If you're using the Sass version of Foundation, you can customize the button classes by editing the $button-palette map in your settings file.

https://github.com/zurb/foundation-sites/blob/master-v6.5/scss/settings/_settings.scss#L298
But it seems we do not use !default anymore and just forgot to update this section.

Please run git commit --amend, change the commit message and do git push -f.
Update button.md is not helpful.
Also please fill out the issue template.

You can use following PR title and commit message:
docs: remove unnecessary !default flag in button config examples

Okay all updated :)


bug: magnetometer sensor values not updating

I want to use magnetometer in my app. But for some reason in the magnetometer RxJS observable, x, y & z are not updating in my app (see console logs).

What I have tried:

My magnetometer in Android's compass app works fine. So there is no issue with my physical device
If I replace magnetometer with gyro or accelerometer, those sensors work fine in my app (their values update every 500ms as expected). But in case of magnetometer, it's values are not updating.
When I switch over to the Android compass app keeping my app in background, suddenly the magnetometer starts updating its values fine (see console logs)

what am I doing wrong? (I think there might be a issue with magnetometer observable only)
I am using RN v0.68.1 & react-native-sensors v7.3.6

I have found an alternative to react-native-sensors which works great
https://docs.swmansion.com/react-native-reanimated/docs/api/hooks/useAnimatedSensor/


Using /var/flexlm/adsk_server.lic and docs update

Changing the default license path to ‘/var/flexlm/adsk_server.lic’ which aligns with Autodesk Help Desk articles.
Updating documentation which did not call out the expected license paths. Props to @hyperknot
Upgrading example to read-only file to file mapping which additionally calls out the expected license path. Props to @hyperknot

Resolves: #1

Interesting, I didn't know that.  I'm hunting for some docs on the -l flag.  I'm guessing that if not included it will output to stdout/stderr?  Good catch!

Yes, that's how stdout behaves with Docker! If either -l "" or -l - or something similar would work then I guess we could use ARGS to enable/disable logging.
Actually, with this changelog, your filesystem based log file is not going to be visible to the host.

@hyperknot I totally see your point. Logging to /var/log/flexlm/lmgrd.log is lame compared to just logging it to Docker and utilizing docker log.  I'll update this default behavior and post the fix in a bit.

@hyperknot Less is more, no default arguments. 😄  Hopefully, this will result is less confusion, better logging, etc.  The logging change will also be helpful when utilizing other utilities packaged with the FlexLM.
Sorry about the confusion about logging, I read what you mentioned in your Issue #1.  However, I did not make the connection that lmgrd output everything to stdout if the -l flag is not provided.

Thanks a lot for all these changes. These were minor things for me, but I believe for the future users they might save quite a lot of time of figuring everything out!


localtunnel gives error of bad gateway - 502

Issue: 502 Bad Gateway Error with LocalTunnel on React.js Project
Description: I'm encountering a 502 Bad Gateway error when using LocalTunnel with my React.jsproject. The error occurs intermittently and affects my ability to test my application locally. Below are the details of my setup and the steps I've taken to troubleshoot this issue.
Project Setup:
React Version: 19
Node.jsVersion: 22.3.0
LocalTunnel Version: 2.0.0
Operating System: Windows 11
Steps to Reproduce:
Start the development server using npm start.
Open a tunnel using LocalTunnel with the command lt --port 3000.
Access the provided URL in a browser.
Observe the 502 Bad Gateway error intermittently.
Troubleshooting Steps Taken:
Verified that the LocalTunnel service is up and running.
Updated all dependencies to their latest versions.
Restarted the development server and LocalTunnel service multiple times.
Checked for any known issues on LocalTunnel's GitHub repository.
Expected Behavior: The application should be accessible through the LocalTunnel URL without encountering the 502 Bad Gateway error.
Actual Behavior: The 502 Bad Gateway error occurs intermittently, preventing access to the application.

Request for Help: I would appreciate any guidance or suggestions on how to resolve this issue. If there are any additional logs or configurations needed, please let me know.

same

same did anyone manage to find a solution to this?

same here

Same

Same Here


This is something that has to be done and I can't accomplish it so I figured I should make an issue.

thanks


lxc/list: Better handle --all-projects

This fixes --all-projects with non-clustered setups.
It also makes it work properly with --fast.
Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

@tomponline good to go


added Hulu clone

Added Hulu clone
I wish to add a Hulu clone to projects under Hacktoberfest 2021
This PR is an issue related to https://github.com/ZeroOctave/ZeroOctave-Javascript-Projects/issues/118

@Astrodevil @NOiR-07


Fix sentence with module naming

1. Why is this change necessary?
Languages are casing nouns differently.
2. What does this change do, exactly?
Enable to change casing of a text in the admin by add two cased variants of a replaced input.
Adjustment of an English snippet to use that new casing as assumed, that there are less languages that use small casing for nouns than unchanged casing.
3. Describe each step to reproduce the issue or behaviour.

Use the global admin search and type in SW
A lot of products get listed:

> duden_are_thrown_through_the_rooms.png
Client calls and asks why it says "Alle 16 Suchtreffer in produkte anzeigen... " and why it writes "produkte" lower cased and everywhere else like it should be
Me seeing the .toLowerCase()
Me here doing the pull request

4. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Thank you for your contribution. These changes are now merged 🎉

whooohoooo :) thank you for merging


SPARK-4550. In sort-based shuffle, store map outputs in serialized form

Refer to the JIRA for the design doc and some perf results.
I wanted to call out some of the more possibly controversial changes up front:

Map outputs are only stored in serialized form when Kryo is in use.  I'm still unsure whether Java-serialized objects can be relocated.  At the very least, Java serialization writes out a stream header which causes problems with the current approach, so I decided to leave investigating this to future work.
The shuffle now explicitly operates on key-value pairs instead of any object.  Data is written to shuffle files in alternating keys and values instead of key-value tuples.  BlockObjectWriter.write now accepts a key argument and a value argument instead of any object.
The map output buffer can hold a max of Integer.MAX_VALUE bytes.  Though this wouldn't be terribly difficult to change.
When spilling occurs, the objects that still in memory at merge time end up serialized and deserialized an extra time.

Test build #26998 has started for   PR 4450 at commit 3a248df.

This patch merges cleanly.

Test build #26998 has finished for   PR 4450 at commit 3a248df.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26998/
Test FAILed.

Test build #26999 has started for   PR 4450 at commit 6d50599.

This patch does not merge cleanly.

Test build #26999 has finished for   PR 4450 at commit 6d50599.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26999/
Test FAILed.

Test build #27006 has started for   PR 4450 at commit c88830b.

This patch merges cleanly.

Test build #27006 has finished for   PR 4450 at commit c88830b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27006/
Test FAILed.

Test build #27050 has started for   PR 4450 at commit 171014e.

This patch merges cleanly.

Test build #27051 has started for   PR 4450 at commit 503136a.

This patch merges cleanly.

Test build #27051 has finished for   PR 4450 at commit 503136a.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27051/
Test FAILed.

Test build #27052 has started for   PR 4450 at commit 6acfb4e.

This patch merges cleanly.

Test build #27050 has finished for   PR 4450 at commit 171014e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27050/
Test FAILed.

Test build #27054 has started for   PR 4450 at commit 6c9c16d.

This patch merges cleanly.

Test build #27052 has finished for   PR 4450 at commit 6acfb4e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27052/
Test FAILed.

Test build #27054 has finished for   PR 4450 at commit 6c9c16d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27054/
Test FAILed.

Test build #27152 has started for   PR 4450 at commit 675e767.

This patch merges cleanly.

Thanks - I'm pretty swamped right now. Will take a look once I free up more (maybe next week)

Test build #27152 has finished for   PR 4450 at commit 675e767.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27152/
Test PASSed.

@sryza don't bother with my comments yet, still just taking a tour through this part of the code.

Hey @sryza - two higher level questions as I'm doing a deeper review of this.

This seems predicated on the idea that serialization streams can safely be sliced with respect to individual objects. In general that's a bit of a gamble, given that both of our serializers only officially support use through a stream interface. I was actually surprised this works given that Kryo does object reference tracking, however, I looked and it turns out that Kryo will reset its internal tracking maps after every outer call to writeObject(): https://github.com/EsotericSoftware/kryo/blob/kryo-2.21/src/com/esotericsoftware/kryo/Kryo.java#L488. Is the idea that we just assume Kryo will continue to have this property, or at least some configuration where this will work?
The second broad question is whether the chained buffer is necessary, since it constitutes a lot of the complexity in this patch. Is the chain buffer just an additional optimization or is it in some way required for using serailized outputs? The way it is now, you are going to allocate a large number of 8KB buffers, at random memory locations.... overall the fragmentation this creates could make GC slower for the JVM. The "win" is that you don't need to use a buffer that does copying to double growth, but given that the copying is amortized over a relatively small number of doublings, I'm not sure I see why that's a big deal. When GC tries to move your little buffers around, it will likely have to copy them anyways. I guess I'd like to better understand the evidence that this chaining is clearly better than the simpler alternative of using a managed, growing buffer.

Thanks for the review Patrick.
Regarding Kryo:  I would be really really surprised if Kryo were to change its serialization format in such a drastic way without adding a backwards compatibility option.  Of course, not impossible. So yeah, the assumption here is that they won't do that.  If they did, and we upgraded our dependency, we'd need to remove or rethink this feature.
The main reason for the ChainedBuffer is a performance optimization.  However, it's not to minimize copies, it's to use memory efficiently and minimize spills.  If we use an array that grows by doubling, we can end up momentarily using 3x the memory that we actually need to store the bytes.  I.e. if we have 512 MB of data and write another MB, we then allocate a 1 GB array.  If that byte was our last byte, we've ended up with a momentary allocation of 1.5 GB to hold 513 MB of data.  Its other advantage is that we can support a buffer greater than 2GB in size.  BTW, the current default value of 8 KB is probably way too low.

Hey Sandy,
I've now taken a pretty thorough look at this patch. There are a lot of low level comments and it would be nice if you could do a pass to bring this up to date and address them. The two major new classes seem good ChainedBuffer and PartitionedSerializedPairBuffer at a high level.
The only issue on which I have some remaining concern is just the overall complexity this adds to the already fairly convoluted ExternalSorter and that the new WritablePartitionedPairCollection is a little clunky. However, I don't have concrete suggestions to improve that issue at present. Curious if you have any ideas.

Test build #31074 has started for   PR 4450 at commit d8462d8.

Updated patch rebases on master and incorporates @pwendell 's review comments.

Test build #31074 has finished for   PR 4450 at commit d8462d8.

This patch fails Scala style tests.

This patch merges cleanly.

This patch adds no public classes.

This patch adds the following new dependencies:

tachyon-0.6.4.jar
tachyon-client-0.6.4.jar

This patch removes the following dependencies:

tachyon-0.5.0.jar
tachyon-client-0.5.0.jar

Test build #31080 has started for   PR 4450 at commit 6c54e06.

Test build #31080 has finished for   PR 4450 at commit 6c54e06.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.
This patch adds the following new dependencies:

RoaringBitmap-0.4.5.jar
activation-1.1.jar
akka-actor_2.10-2.3.4-spark.jar
akka-remote_2.10-2.3.4-spark.jar
akka-slf4j_2.10-2.3.4-spark.jar
aopalliance-1.0.jar
arpack_combined_all-0.1.jar
avro-1.7.7.jar
breeze-macros_2.10-0.11.2.jar
breeze_2.10-0.11.2.jar
chill-java-0.5.0.jar
chill_2.10-0.5.0.jar
commons-beanutils-1.7.0.jar
commons-beanutils-core-1.8.0.jar
commons-cli-1.2.jar
commons-codec-1.10.jar
commons-collections-3.2.1.jar
commons-compress-1.4.1.jar
commons-configuration-1.6.jar
commons-digester-1.8.jar
commons-httpclient-3.1.jar
commons-io-2.1.jar
commons-lang-2.5.jar
commons-lang3-3.3.2.jar
commons-math-2.1.jar
commons-math3-3.4.1.jar
commons-net-2.2.jar
compress-lzf-1.0.0.jar
config-1.2.1.jar
core-1.1.2.jar
curator-client-2.4.0.jar
curator-framework-2.4.0.jar
curator-recipes-2.4.0.jar
gmbal-api-only-3.0.0-b023.jar
grizzly-framework-2.1.2.jar
grizzly-http-2.1.2.jar
grizzly-http-server-2.1.2.jar
grizzly-http-servlet-2.1.2.jar
grizzly-rcm-2.1.2.jar
groovy-all-2.3.7.jar
guava-14.0.1.jar
guice-3.0.jar
hadoop-annotations-2.2.0.jar
hadoop-auth-2.2.0.jar
hadoop-client-2.2.0.jar
hadoop-common-2.2.0.jar
hadoop-hdfs-2.2.0.jar
hadoop-mapreduce-client-app-2.2.0.jar
hadoop-mapreduce-client-common-2.2.0.jar
hadoop-mapreduce-client-core-2.2.0.jar
hadoop-mapreduce-client-jobclient-2.2.0.jar
hadoop-mapreduce-client-shuffle-2.2.0.jar
hadoop-yarn-api-2.2.0.jar
hadoop-yarn-client-2.2.0.jar
hadoop-yarn-common-2.2.0.jar
hadoop-yarn-server-common-2.2.0.jar
ivy-2.4.0.jar
jackson-annotations-2.4.0.jar
jackson-core-2.4.4.jar
jackson-core-asl-1.8.8.jar
jackson-databind-2.4.4.jar
jackson-jaxrs-1.8.8.jar
jackson-mapper-asl-1.8.8.jar
jackson-module-scala_2.10-2.4.4.jar
jackson-xc-1.8.8.jar
jansi-1.4.jar
javax.inject-1.jar
javax.servlet-3.0.0.v201112011016.jar
javax.servlet-3.1.jar
javax.servlet-api-3.0.1.jar
jaxb-api-2.2.2.jar
jaxb-impl-2.2.3-1.jar
jcl-over-slf4j-1.7.10.jar
jersey-client-1.9.jar
jersey-core-1.9.jar
jersey-grizzly2-1.9.jar
jersey-guice-1.9.jar
jersey-json-1.9.jar
jersey-server-1.9.jar
jersey-test-framework-core-1.9.jar
jersey-test-framework-grizzly2-1.9.jar
jets3t-0.7.1.jar
jettison-1.1.jar
jetty-util-6.1.26.jar
jline-0.9.94.jar
jline-2.10.4.jar
jodd-core-3.6.3.jar
json4s-ast_2.10-3.2.10.jar
json4s-core_2.10-3.2.10.jar
json4s-jackson_2.10-3.2.10.jar
jsr305-1.3.9.jar
jtransforms-2.4.0.jar
jul-to-slf4j-1.7.10.jar
kryo-2.21.jar
log4j-1.2.17.jar
lz4-1.2.0.jar
management-api-3.0.0-b012.jar
mesos-0.21.0-shaded-protobuf.jar
metrics-core-3.1.0.jar
metrics-graphite-3.1.0.jar
metrics-json-3.1.0.jar
metrics-jvm-3.1.0.jar
minlog-1.2.jar
netty-3.8.0.Final.jar
netty-all-4.0.23.Final.jar
objenesis-1.2.jar
opencsv-2.3.jar
oro-2.0.8.jar
paranamer-2.6.jar
parquet-column-1.6.0rc3.jar
parquet-common-1.6.0rc3.jar
parquet-encoding-1.6.0rc3.jar
parquet-format-2.2.0-rc1.jar
parquet-generator-1.6.0rc3.jar
parquet-hadoop-1.6.0rc3.jar
parquet-jackson-1.6.0rc3.jar
protobuf-java-2.4.1.jar
protobuf-java-2.5.0-spark.jar
py4j-<IP_ADDRESS>.jar
pyrolite-2.0.1.jar
quasiquotes_2.10-2.0.1.jar
reflectasm-1.07-shaded.jar
scala-compiler-2.10.4.jar
scala-library-2.10.4.jar
scala-reflect-2.10.4.jar
scalap-2.10.4.jar
scalatest_2.10-2.2.1.jar
slf4j-api-1.7.10.jar
slf4j-log4j12-1.7.10.jar
snappy-java-<IP_ADDRESS>.jar
spark-bagel_2.10-1.4.0-SNAPSHOT.jar
spark-catalyst_2.10-1.4.0-SNAPSHOT.jar
spark-core_2.10-1.4.0-SNAPSHOT.jar
spark-graphx_2.10-1.4.0-SNAPSHOT.jar
spark-launcher_2.10-1.4.0-SNAPSHOT.jar
spark-mllib_2.10-1.4.0-SNAPSHOT.jar
spark-network-common_2.10-1.4.0-SNAPSHOT.jar
spark-network-shuffle_2.10-1.4.0-SNAPSHOT.jar
spark-repl_2.10-1.4.0-SNAPSHOT.jar
spark-sql_2.10-1.4.0-SNAPSHOT.jar
spark-streaming_2.10-1.4.0-SNAPSHOT.jar
spire-macros_2.10-0.7.4.jar
spire_2.10-0.7.4.jar
stax-api-1.0.1.jar
stream-2.7.0.jar
tachyon-0.6.4.jar
tachyon-client-0.6.4.jar
uncommons-maths-1.2.2a.jar
unused-1.0.0.jar
xmlenc-0.52.jar
xz-1.0.jar
zookeeper-3.4.5.jar

Test build #31136 has started for   PR 4450 at commit 9c16fe6.

Test build #31136 has finished for   PR 4450 at commit 9c16fe6.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Merged build triggered.

Merged build started.

Test build #31160 has started for   PR 4450 at commit 8c70dd9.

Test build #31160 has finished for   PR 4450 at commit 8c70dd9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31160/
Test PASSed.

Merged build finished. Test PASSed.

Jenkins, test this please.

LGTM pending a final test run. I want to get this in since there may be some other changes to shuffle interfaces due to some of the binary management stuff.

Merged build triggered.

Merged build started.

Test build #31512 has started for   PR 4450 at commit 8c70dd9.

Test build #31512 has finished for   PR 4450 at commit 8c70dd9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31512/
Test PASSed.

Alright let's do it. Thanks for the work Sandy. Let's leave this on for now and we can decide to de-flag it later in the QA cycle if we want.

Thanks for reviewing and merging @pwendell !


Reevaluate file loading code.

The Python code that walks the filesystem is somewhat robust, but it's a little backwards in the sense of OOP practices.
The primary flow of all operations are:

Identify all files in a directory structure, matching a suitable filename pattern.
Iterate through all filenames, load each file with the XML parser, and then return a Media object for everything matching the XML criteria.
Iterate through the list of Media objects.

For situations where we want to extend the POC tools so they can be easily usable within the Python shell, I want to consider this logical flow.

A pool list object containing nothing but Media objects in memory.
Repository objects which point to paths where XML files reside.
Implementor scans the repository using a suitable filename match.
The repository object returns the list of files.
The loader object (or maybe the repository object?) reads the files, creates the Media objects, and puts them in the pool object.

Anyone should be able to perform this functionality from the Python shell where they have a persistent pool object that can be populated by reading one or more directory paths.
Something along the lines of...
>>> x = Repo(pathA)
>>> p = []
>>> fileset = x.identify(movie_files_regex_pattern)
>>> p.extend(loader_object.scan_files(fileset))
>>> p[0]
<media.data.media.contents.movie.internal.Movie object at 0xfffffc7fedb6fbe0>

Additional notes (based on the example above):

The p object could be either a regular Python list, or even a custom object that's iterable.  It shouldn't matter.
The p object in this case, would store all of the Media device objects.
The current code that walks the directory tree is pretty good, with a decent feature set, but not too complex.  Consider a model where the Repo object doesn't do the scanning directly, but passes the job onto a delegate object.
Filename components don't matter to the internal data, so the current method of assuming anything with '-dvd' in the filename being a DVD is kind of sloppy.  However, there should be future tools that can scan the pool, and legitimacy filter out objects by things like device type, or other characteristics.

Commit.
https://github.com/cjcodeproj/medialibrary/commit/01739ba48c93f7d87cebc91668a634b0c55f44ae


How does Craig dig up those functions and their usage?

I tried typing Display GD_Shields.A_Item.Shield_Roid_05_ThresherRaid and GetAll GD_Shields.A_Item.Shield_Roid_05_ThresherRaid in the console, just got nothing.
Where and how did you awesome guys do that?
Thanks.

obj dump GD_Shields.A_Item.Shield_Roid_05_ThresherRaid. You can join his discord server and ask him or other guys that made custom patches https://discord.gg/0YjZxbVBS9b3bXUS

wow, thanks a lot


Input shadows are offset incorrectly in Firefox

First of all, thank you for releasing v2! I had been looking forward to it for some time now, and it looks great :)
Issue Description
In Firefox, the box shadow of a focused input element is offset slightly incorrectly, resulting in a sort of "double vision" effect.
This issue occurs in Firefox, but not in Chromium. See the comparison below. I focused especially on the corners where the issue is most apparent. Both screenshots were made by going to pico's own Forms overview documentation page. Both screenshots were made in a fresh browser profile without add-ons.

Firefox 122.0.1
Chromium 121.0.6167.160

Expected Behavior
I expect both browsers to behave as in Chromium.
Reproduction URL
https://picocss.com/docs/forms
Environment

OS
Linux 6.6.13, Debian Testing, KDE, X

Browser
See above

picocss
2.0.3

I agree. Not pretty.
I don't see this problem with Firefox 122 on macOS.
I don't have much idea how to fix it.

I was able to reproduce the bug Firefox on Linux (Arch Linux with GNOME 45) and Windows 11.
Tested on Chromium browsers as well with no problems.

Windows 11

Linux