Zuul gateway fails to forward HTTP HEAD requests

Hi there!
I think I've found a bug in Zuul. My setup is the following:

eureka server
a RESTful Web Service
Zuul

When I send a HEAD request to the service through Zuul gateway at the following address: localhost:8090/service/greeting I get the following forwarding exception:
gist
I tried to find the bug by debugging Zuul. Unluckily I could not identify what is causing the problem.
Can you confirm if this is a bug or I am doing something wrong?
The service works as expected if I don't send the request through Zuul.

It appears it is just Hystrix timing out.  You can try disabling Hystrix and everything should work
hystrix.command.default.execution.timeout.enabled: false

I tried your solution, but I does not work. Here is the stack trace: gist

Hi @ryanjbaxter !
I've figured out that HEAD methods were working with spring-cloud-netflix versions up to 1.2.0.RELEASE. The problem was introduced with the 1.2.1.RELEASE.
Can you add a bug label to this issue please?

I still don't see how this is a bug.  The exception is not just a socket timeout exception.  It has nothing to do with Zuul or the version of Spring Cloud.  The service is not responding quick enough to the request.

Hi Ryan!
Please excuse me because I didn't provide you all the information why I think this problem might be a bug.
So first of all the REST service responds to both GET and HEAD requests in a matter of few milliseconds if I am not using Zuul. I tried it lots of times and I never had to wait for the response for long time. By default the value of ribbon.ReadTimeout is 5000 ms and I always get a timeout after 5 s.
Even when I set the ribbon.ReadTimeout property to 180000 ms the service is not responding.
When I call the HEAD method on the service directly only the controller corresponding to HEAD method is invoked. However, when I call the same endpoint through Zuul I see in the logs that both GET and HEAD methods were invoked. This seems to be an anomaly. I tried to debug the Zuul gateway to understand why is it working that way, but I could not find the code which calls both GET and HEAD methods.
The 3rd reason why I think this is a problem of Zuul is that this scenario works with spring-cloud-dependencies versions prior and including Brixton.SR7. Of course this does not imply necessarily that the problem is in the spring-cloud-netflix project, but I am using only spring-boot-starter-web, spring-cloud-starter-zuul and spring-cloud-starter-eureka. My gut feeling is that this problem is not caused by spring-cloud-starter-eureka nor spring-boot-starter-web, because I see exceptions coming from Zuul.
Could you reproduce this behavior on your machine?
Thank you for your patience!

I just ran you samples and was unable to reproduce the problem.  The only thing I changed from the zips is that I changed the Eureka server to use the BOM, but that shouldnt have made a difference.
zuul curl --head "http://localhost:8090/service/greeting" \
     -H "Content-Type: application/x-www-form-urlencoded; charset=utf-8"
HTTP/1.1 200
X-Application-Context: zuul:8090
Date: Tue, 03 Oct 2017 19:21:08 GMT
Content-Type: application/json;charset=UTF-8
Content-Length: 0

I am seeing the same behavior. when running service HEAD method independently I get the response, but if the request goes through ZUUL it fails with 502 bad gateway error. 502 response comes from service. if I invoke the same method for GET(method support GET/HEAD) through ZUUL it works.  Something ZUUL is adding up and causing 502 error.

here is error 👍
[APP:null TRACKING_ID:null ACCOUNT_NUM:null] org.apache.http.wire - http-outgoing-1 << "Content-Type: text/plain; charset=utf-8[\r][\n]"
Tue Oct 03 10:39:21 MDT 2017 DEBUG [APP:null TRACKING_ID:null ACCOUNT_NUM:null] org.apache.http.wire - http-outgoing-1 << "X-Cf-Routererror: endpoint_failure[\r][\n]"
Tue Oct 03 10:39:21 MDT 2017 DEBUG [APP:null TRACKING_ID:null ACCOUNT_NUM:null] org.apache.http.wire - http-outgoing-1 << "X-Content-Type-Options: nosniff[\r][\n]"

@pradeepsingh1234 do you use CloudFoundry?

yes, we are using cloud foundry.

You are getting 502 because the gorouter (load balancer) of cloud foundry kills the request on timeout.
Check line 145 bellow:
https://github.com/cloudfoundry/gorouter/blob/2a81454fdc8170bd70a4977d3a0a255b08fcaa4e/proxy/handler/request_handler.go
If you try to run your services on a local machine you will see that Zuul responds after a while, but with 500 status code.

Yes, I saw same.
Sent from my iPhone
On Oct 4, 2017, at 7:51 AM, Leonard L?szl? <notifications<EMAIL_ADDRESS>wrote:
You are getting 502 because the gorouter (load balancer) of cloud foundry kills the request on timeout.
Check line 145 bellow:
https://github.com/cloudfoundry/gorouter/blob/2a81454fdc8170bd70a4977d3a0a255b08fcaa4e/proxy/handler/request_handler.go
If you try to run your services on a local machine you will see that Zuul responds after a while, but with 500 status code.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/spring-cloud/spring-cloud-netflix/issues/2296#issuecomment-334161837, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOuX0TyiN_30tHK_t-z1pFRCnvtiHXuDks5so41xgaJpZM4Pj10y.

Everything works fine if I use brixton SR7.

Like I said I ran the sample apps you provided above on my local machine and do not see any delay when making a HEAD request through Zuul.  Without a way to reproduce the problem its hard for me to help.

What OS do you use guys?

I tried this setup on OS X and it seems to work properly. I've got the errors on windows 7 and 10..

I can rerpdoce this error in latest mac book pro2 with Sierra OS.
From: Leonard László<EMAIL_ADDRESS>Reply-To: spring-cloud/spring-cloud-netflix<EMAIL_ADDRESS>Date: Wednesday, October 4, 2017 at 3:39 PM
To: spring-cloud/spring-cloud-netflix<EMAIL_ADDRESS>Cc: Pradeep Singh<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [spring-cloud/spring-cloud-netflix] Zuul gateway fails to forward HTTP HEAD requests (#2296)
I tried this setup on OS X and it seems to work properly. I've got the errors on windows 7 and 10..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/spring-cloud/spring-cloud-netflix/issues/2296#issuecomment-334297400, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOuX0W-Z1XX9eRl2y59ltkqcIH7OPtk_ks5so_r5gaJpZM4Pj10y.

I am using OS X

Closing due to age of the question. If you would like us to look at this issue, please comment and we will look at re-opening the issue.


Implement _codecs (but not encoding/decoding) as a Rust module

Based off #2634

I think the windows failure was a fluke from rustup.


Fix for time selection not allowing other changes

Fixes #1295

Hey @aij, thanks for the feedback. I've updated the PR and I think this solution works nicely.

Reverted the version change as requested by @rafeememon

Thanks @tomtwttr

You're welcome


Remove outdated project from Community Docs

What issue does this PR address?
Razor pages community project has no content and is no longer active.
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

[x] The commit follows our guidelines
[ ] Unit Tests for the changes have been added (for bug fixes / features)

Other information:

thanks


Added possibility to play video in background and when app is inactive.

When streaming live video it's sometimes desirable to let the video continue to play when app is entering background. This PR makes it possible to configure the video component to allow this.
Prior to this PR iOS stops playing video when entering background but Android contiues to play video. This PR unifies the behaviour between iOS and Android so that when playInBackground is set to true both platforms will continue to play video and naturally false will make both platforms stop the video.
Also added a iOS specific prop called playWhenInactive which prevents the video to stop if control center or notification center is shown. Again when streaming live video you don't want to stop the playback when for example using control center to change volume.

Great, thanks!

Thanks for this!! In what version number is this code included? Or is it in master only? @brentvatne It would be nice to create a release 👍

Hey so is there a way to have the video resume when the control panel is closed on IOS?


make a easy to understand Readme.mb file

it will help contributer for better understanding of code flow and also help them setup the project locally via npm or docker

I think it's a big project so we can have a simple readme about the project and demos.
For development specific we can have another readme to tell how to set up with npm or docker.

@kom-senapati Yes we can have seperate markdown files, do you want this issue to be assigned to you?

@cb7chaitanya Assign me this issue

No I dont want the issue @vishalmaurya850  can do it.

Great assigning it to @vishalmaurya850

I am not getting the repository link. Please share @cb7chaitanya


[Resizing Partitions] - cloud-guest-utils

Investigate into transitioning to cloud-guest-utils for auto resizing on first bootup..
Anyway, on the off-chance you're unaware, you can simply add
cloud-guest-utils to the installed package list when building an image,
then automatically resize the partition on the first boot.  A snippit
from a debootstrap second-stage script which sets this up via systemd
follows.

NOTE: The growpart utility is just a shell script, so you could also
potentially use it as a reference to do online resizing w/o requiring a
reboot in your grow_partition.sh script.

# Resize root partition on the first boot
# ==========
# Create a systetmd service file
cat > /etc/systemd/system/resize_rootfs.service << EOF_resize
[Unit]
Description=Resize root file system
After=basic.target

[Service]
Type=oneshot
ExecStartPre=-/usr/bin/growpart /dev/mmcblk0 ${ROOTPARTN}
ExecStart=-/sbin/resize2fs /dev/mmcblk0${ROOTPART}
ExecStartPost=/bin/systemctl disable resize_rootfs

[Install]
WantedBy=multi-user.target

EOF_resize

# Enable the new service
systemctl enable resize_rootfs

On x86: depends list is small.
sudo apt install cloud-guest-utils
[sudo] password for voodoo:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  cloud-init
The following NEW packages will be installed:
  cloud-guest-utils
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 23.3 kB of archives.
After this operation, 61.4 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 cloud-guest-utils all 0.31-1 [23.3 kB]
Fetched 23.3 kB in 0s (59.5 kB/s)
Selecting previously unselected package cloud-guest-utils.
(Reading database ... 361394 files and directories currently installed.)
Preparing to unpack .../cloud-guest-utils_0.31-1_all.deb ...
Unpacking cloud-guest-utils (0.31-1) ...
Setting up cloud-guest-utils (0.31-1) ...
Processing triggers for man-db (2.9.1-1) ...

Available in Stretch/Buster:
https://packages.debian.org/stretch/cloud-guest-utils
Available in Bionic:
https://packages.ubuntu.com/bionic/cloud-guest-utils


Make Plutarch sound

All new way of deriving PlutusType and all other P-classes.
pcon is always strict (plazy hasn't been added yet).
Lots of general clean-ups, removing unsound code, etc.
PForall, PSome, PFix, instead of extra type parameter on PInner.
Fixed upcasting and downcasting by adding magical P{Co{,ntra}v,V}ariant type families.
Added a lot more warnings by default.
Removed AllowAmbiguousTypes in a lot of places.
Made FFI a lot simpler.
Removed a lot of bad uses of overlapping instances.
This is the final pressing stuff for 1.2 AFAICT. The tests don't work yet, and plutarch-extra also needs to be fixed.

@MangoIV why not just do it in a separate PR

I guess that's fair, then we open an issue and add it to plutarch v1.2 todo list maybe?


Merge terraform stacks

What this PR does / why we need it: This PR merges the Terraform stacks which were previously run sequentially by Tarmak. This will allow us to both parallelise Terraform and plan all stacks properly
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #110

I have just pushed my rebased to upstream/master state

The next step would fixing the a cluster apply of the hub.
The terraform code generation fails currently:
go test -v ./pkg/tarmak
--- FAIL: TestTarmak_Terraform_Generate_Hub (0.43s)

/test verify docs

/lgtm

/approve

/lgtm


Switch to sphinx_symbiflow_theme

fixes #209

It doesn't seemed to have worked? https://symbiflow-examples--210.org.readthedocs.build/en/210/ ?

Seems to be working now! - https://symbiflow-examples--210.org.readthedocs.build/en/210/index.html


Dynamic routing accepts only YAML, but not YML

Issue Summary
I tried to upload my routes.yml to a production configured ghost instance and I got Please select a valid YAML file to import..
After some research I figured out that the problem was the file extension, so after I renamed it from routes.yml to routes.yaml it worked.
Why I'm writing this then?
Because the default routes in Ghost is in yml format and the common sense dictates to follow this example. It's just a small thing, but one can lose time with it.
Steps to Reproduce

On a production ghost instance
Go to  hostname/ghost/#/settings/labs
Beta features > Routes > Upload routes file
Select a file with .yml ending

Ghost Version
5.96.1 (ghost:5.96.1-alpine image)
Node.js Version
It's included with the docker image
How did you install Ghost?
On Debian 12 via Docker
Database type
MySQL 5.7
Browser & OS version
Firefox
Relevant log / error output
[2024-11-07 08:39:32] INFO Updating incoming recommendations on boot

[2024-11-07 08:40:11] INFO [Recommendations] Updating recommendations metadata

[2024-11-07 08:40:19] ERROR "POST /ghost/api/admin/settings/routes/yaml/" 415 22ms

Please select a valid YAML file to import.

Error ID:

    eb8c1470-9ce3-11ef-89d3-2d4682878da5

----------------------------------------

UnsupportedMediaTypeError: Please select a valid YAML file to import.

    at uploadValidation (/var/lib/ghost/versions/5.96.1/core/server/web/api/middleware/upload.js:212:25)

    at Layer.handle [as handle_request] (/var/lib/ghost/versions/5.96.1/node_modules/express/lib/router/layer.js:95:5)

    at next (/var/lib/ghost/versions/5.96.1/node_modules/express/lib/router/route.js:149:13)

    at /var/lib/ghost/versions/5.96.1/core/server/web/api/middleware/upload.js:94:9

    at Immediate._onImmediate (/var/lib/ghost/versions/5.96.1/node_modules/multer/lib/make-middleware.js:53:37)

    at process.processImmediate (node:internal/timers:478:21)

Code of Conduct

[X] I agree to be friendly and polite to people in this repository

From your title, this is by design, but from your description, there might be a bug/docs issue 😁

Because the default routes in Ghost is in yml format and the common sense dictates to follow this example. It's just a small thing, but one can lose time with it.

Which default routes are you referring to?

I see now that in the docker image it's indeed yaml. I copied the routes.yml from /content/settings/ of a localy installed ghost instance and it caused the confusion.
Thank you for the feedback. :)


Alignment of schedule grid

The schedule grid got misaligned in spacing:

width of each column (day) should be the same
height of each row (event) should have same min-height (might get larger), a bit larger than currently (one of the rows looks too small)

this may have been fixed? not sure

This has been fixed.


Enable Link-Time Optimization (LTO)

Hi!
I noticed that in the Cargo.toml file Link-Time Optimization (LTO) for the project is not enabled. I suggest switching it on since it will reduce the binary size (always a good thing to have) and will likely improve the application's performance a bit.
I suggest enabling LTO only for the Release builds so as not to sacrifice the developers' experience while working on the project since LTO consumes an additional amount of time to finish the compilation routine. If you think that a regular Release build should not be affected by such a change as well, then I suggest adding an additional dist or release-lto profile where additionally to regular release optimizations LTO will also be added. Such a change simplifies life for maintainers and others interested in the project persons who want to build the most performant version of the application. Using ThinLTO should also help to reduce the build-time overhead with LTO. If we enable it on the Cargo profile level, users, who install the application with cargo install, will get the LTO-optimized version "automatically". E.g., check cargo-outdated Release profile.
Basically, it can be enabled with the following lines:
[profile.release]
lto = true

Thank you.
P.S. It's more like an improvement idea rather than a bug. I created the issue just because the Discussions are disabled for the repo for now.

Hi @zamazan4ik
Thank you for the suggestion, this is not something we will be pursuing any time soon, it will increase compilation time and it's unlikely to be the first optimization on the list.


Spyder crashes when I try to save the file

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[x] Reset preferences with spyder --reset
[x] Reinstalled the latest version of Anaconda
[x] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
What steps reproduce the problem?

What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version:
Python version:
Qt version:
PyQt version:
Operating System name/version:

Dependencies

PASTE DEPENDENCIES HERE

Hey @SadhviV, thanks for reporting. Could you elaborate more and let us now what is the crash you're seen? Otherwise we won't be able to help you.

Hello,
Spyder crashes whenever I try to save a new file in anaconda. The only file
I am able to use and save is the default temp.py file which is there
already when I open spyder.
Anaconda navigator : 2020.07
Spyder : 4.1.4
The error message says:
"Python stopped working"
"A problem caused the program to stop working correctly.Windows will close
the program and notify you if a solution is available"
Can you guide me on this issue. What steps need to be taken to resolve this
issue?
What steps will reproduce the problem?

Open Anaconda
Open Spyder, click on new file
Try saving the new file and this error will pop up.

What is the expected output? What do you see instead?
The expected output is to see the new file getting saved in the location
specified. Instead the spyder application crashes after the following error
message.
"Python stopped working"
"A problem caused the program to stop working correctly.Windows will close
the program and notify you if a solution is available"
On Sun, Oct 25, 2020 at 7:15 PM Carlos Cordoba<EMAIL_ADDRESS>wrote:

Hey @SadhviV https://github.com/SadhviV, thanks for reporting. Could
you elaborate more and let us now what is the crash you're seen? Otherwise
we won't be able to help you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/14066#issuecomment-716228932,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGID5MSIPEGJZEYEPYST7EDSMSWQRANCNFSM4S6THTZQ
.

Please open the Anaconda Prompt and run there
spyder --report-segfault

After it crashes, please run again
spyder --report-segfault

Then a dialog will be shown that will allow you to upload the crash report here to Github.
If no dialog appears, please look for a file called faulthandler.log in Spyder's configuration directory (C:\Users\<your user>\.spyder-py3 on Windows; /Users/<your user>/.spyder-py3 on macOS; or /home/<your user>/.config/spyder-py3 on Linux) and upload it here.

please find the attached file.
Best Regards,
Sadhvi
On Sat, Oct 31, 2020 at 12:03 AM Carlos Cordoba<EMAIL_ADDRESS>wrote:

Please open the Anaconda Prompt and run there
spyder --report-segfault
After it crashes, please run again
spyder --report-segfault
Then a dialog will be shown that will allow you to upload the crash report
here to Github.
If no dialog appears, please look for a file called faulthandler.log in
Spyder's configuration directory (C:\Users<your user>.spyder-py3 on
Windows; /Users//.spyder-py3 on macOS; or /home//.config/spyder-py3 on Linux) and upload it here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/14066#issuecomment-719879664,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGID5MX77MI2T6QBI6CNT6DSNOD7JANCNFSM4S6THTZQ
.

I saw the issue you opened with the crash information for this (#14111). Unfortunately, it couldn't capture any useful information, sorry.

Do you want me to provide you with more details?
please provide me with the workaround for this issue?
On Sat, Oct 31, 2020 at 8:50 PM Carlos Cordoba<EMAIL_ADDRESS>wrote:

I saw the issue you opened with the crash information for this (#14111
https://github.com/spyder-ide/spyder/issues/14111). Unfortunately, it
couldn't capture any useful information, sorry.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/14066#issuecomment-720009123,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGID5MTSHNMCXPRPT6EYHDDSNSWF7ANCNFSM4S6THTZQ
.

Some ideas:

Perhaps you have some firewall or antivirus program that prevents Spyder to work.
Or you're writing to a protected directory, which causes the crash.
Or you're writing to a Dropbox or OneDrive directories.

If none of that helps, I'm sorry but I have no more advice nor workarounds to offer.

Spyder version: 4.1.5
Python version: 3.9.1
Qt version: 4.8.7-57
PyQt version: 5.15.0-4
Operating System name/version: Fedora release 33
I've been able to reproduce this issue consistently. I open the distro install app, then try to save the default file and it just crashes.
I installed spyder using the distro package manager (dnf).
Here is the backtrace: https://gist.github.com/sysadmin75/130aec232c0489908c625023f23e2ff4
I tried reproducing the problem by setting up a dev environment following the instructions here.  I tested against master but was unable to repro the problem.
I also tried against branch 4.1.x and was still unable to repro the problem.

Spyder version: 4.1.5
Python version: 3.9.1
Qt version: 4.8.7-57
PyQt version: 5.15.0-4
Operating System name/version: Fedora release 33
I've been able to reproduce this issue consistently. I open the distro install app, then try to save the default file and it just crashes.
I installed spyder using the distro package manager (dnf).
Here is the backtrace: https://gist.github.com/sysadmin75/130aec232c0489908c625023f23e2ff4
I tried reproducing the problem by setting up a dev environment following the instructions here.  I tested against master but was unable to repro the problem.
I also tried against branch 4.1.x and was still unable to repro the problem.

@sysadmin75, thanks for chiming in but we don't have the resources nor the time to offer support for custom installations (only Anaconda and our installers).
And, as you already verified, everything is working with Anaconda. So please bring your problem to the attention of your distro maintainers.

@sysadmin75, thanks for chiming in but we don't have the resources nor the time to offer support for custom installations (only Anaconda and our installers).
And, as you already verified, everything is working with Anaconda. So please bring your problem to the attention of your distro maintainers.

Also, I'm going to close this one due to lack of response.

Also, I'm going to close this one due to lack of response.


Testing Filter not working

I am trying to test my app but ran into this problem.
mock := r.NewMock()
mock.On(r.Table("test").Filter(r.Row.Field("name").Eq("Kujtim Hoxha"))).Return([]interface{}{
	map[string]interface{}{"id": 4, "name": "Kujtim Hoxha"},
},nil)
cursor,_:=r.Table("test").Filter(r.Row.Field("name").Eq("Kujtim Hoxha")).Run(mock)

I get an error saying that the query was not expected.
It looks like the query when translated into string is turned into
r.Table("test").Filter(func(var_2 r.Term) r.Term { return r.Row.Field("name").Eq("Kujtim Hoxha") })

I suspect that in mock.On the query is translated to
r.Table("test").Filter(func(var_1 r.Term) r.Term { return r.Row.Field("name").Eq("Kujtim Hoxha") })

So mock will not expect this query.
Is there a workaround for this ?

Hi, thanks for reporting this issue. I have been able to replicate the issue locally and have discovered that this is caused by the way the driver builds functions in ReQL, internally the driver contains a counter which is used to chose a unique identifier for all variables used in any functions.
Unfortunately because this counter is global a different ID is used when mocking the query and running the query. I will try to figure a better way of comparing the mocked function variables to the actual function variables and release this as part of v2.2.0 which will hopefully be coming in the next couple of weeks.

The fix has been released to master.


[Identity] Review feedback on DefaultAzureCredential

Is your feature request related to a problem? Please describe.
We recently updated DefaultAzureCredential to make additional credentials public and to expose the credential list used by DAC. We should review feedback from users to see if this addresses previous issues around configuring a mix of production and developer credentials during development.
Describe the solution you'd like
Review comments and reach out to on-going beta testers of the preview releases of Identity. Respond to this feedback where necessary.

Closing as there are no actionable items at the moment.


ea-nightly/libc/master: #29 Failed

Build ea-nightly/libc/master #29 Failed
View full output
Change log:

9a9df64: Relocate Jenkinsfiles from docs -> tools [Phillip Johnston]
28f0fc0: Make docs in libc CI build [Phillip Johnston]
2fc3f35: Register libc tests with meson [Phillip Johnston]
688ad53: Complete conversion to meson for running the test sequence [Phillip Johnston]
de99c55: Update jenkinsfiles with new test location [Phillip Johnston]
0575232: Update tests [Phillip Johnston]

Last 75 of output:
[...truncated 6.88 KB...]
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Setup)
[Pipeline] echo
Creating temporary tag
[Pipeline] sh
[ea-nightly_libc_master-MTVIUQJOZBC7SDBFGUQSYP25Z67VD5GU7NRZ6ZAJCNBHKOTTDYFQ] Running shell script
+ git tag -a 0.1.29 -m 'Creating tag to build 0.1.29'
[Pipeline] echo
Removing existing build results
[Pipeline] sh
[ea-nightly_libc_master-MTVIUQJOZBC7SDBFGUQSYP25Z67VD5GU7NRZ6ZAJCNBHKOTTDYFQ] Running shell script
+ make purify
Removing Build Output
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build)
[Pipeline] sh
[ea-nightly_libc_master-MTVIUQJOZBC7SDBFGUQSYP25Z67VD5GU7NRZ6ZAJCNBHKOTTDYFQ] Running shell script
+ make
make: meson: No such file or directory
make: *** [groundwork] Error 1
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Test)
Stage "Test" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Documentation)
Stage "Documentation" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Archive)
Stage "Archive" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] warnings
[WARNINGS] Skipping publisher since build result is FAILURE
[Pipeline] openTasks
[TASKS] Skipping publisher since build result is FAILURE
[Pipeline] echo
Sending slack message: <http://<IP_ADDRESS>:12345/job/ea-nightly/job/libc/job/master/29/display/redirect|ea-nightly/libc/master #29>: *FAILED*
Changes:
- `9a9df64`: Relocate Jenkinsfiles from docs -> tools [Phillip Johnston]
- `28f0fc0`: Make docs in libc CI build [Phillip Johnston]
- `2fc3f35`: Register libc tests with meson [Phillip Johnston]
- `688ad53`: Complete conversion to meson for running the test sequence [Phillip Johnston]
- `de99c55`: Update jenkinsfiles with new test location [Phillip Johnston]
- `0575232`: Update tests [Phillip Johnston]

[Pipeline] slackSend
run slackstepsend, step null:false, desc :true
Slack Send Pipeline step configured values from global config - baseUrl: true, teamDomain: true, token: true, channel: true, color: false
[Pipeline] echo
Deleting temporary tag
[Pipeline] sh
[ea-nightly_libc_master-MTVIUQJOZBC7SDBFGUQSYP25Z67VD5GU7NRZ6ZAJCNBHKOTTDYFQ] Running shell script
+ git tag -d 0.1.29
Deleted tag '0.1.29' (was ba8817a)
[Pipeline] sh
[ea-nightly_libc_master-MTVIUQJOZBC7SDBFGUQSYP25Z67VD5GU7NRZ6ZAJCNBHKOTTDYFQ] Running shell script
+ git config --get remote.origin.url
[Pipeline] readFile
[Pipeline] echo
Creating a GitHubPluginConfig for credential 4c01f168-ca25-483e-bc6d-8d105fc5fb70
[Pipeline] echo
Registering GithubProjectProperty for repo URL https://github.com/embeddedartistry/libc
[Pipeline] properties

Fixed the meson build


[$250] [Search v2.2] Hide mobile Search nav button + status tabs on scrollDown, but reveal on scrollUp

Problem
On mobile, the Search page occupies a lot of fixed space between the top workspace switcher, the page navigation button, the status tabs, and the bottom fixed tabs. This doesn't lave a whole lot of vertical space remaining to view the expenses page.
Solution:
Let's make it so that the nav button and status tabs scroll the page with the content, but are revealed as soon as the user scrolls back up. Here is a rough prototype of the action:
https://github.com/user-attachments/assets/1e7f7599-6990-454c-9846-f95c98c42a2f
Note that in the prototype, we're scrolling the button + tabs back into view at the same speed as the content, but I could see where it might even make sense to just animate that area back in as soon as we detect "one scroll" going back up.
cc @Expensify/design @luacmartins for visibility. I think this is good #wave-control polish.
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ee6fbdd84bda73a1
Upwork Job ID:<PHONE_NUMBER>737004666
Last Price Increase: 2024-08-27
Automatic offers:

rayane-djouah | Contributor | 103694364

Issue OwnerCurrent Issue Owner: @rayane-djouah

@luacmartins Can you share the video in OP again, I can't see it in the OP.

I am unable to see provided video or screenshot.Please provide a video or screenshot of issue.

Hey! I’m Jakub Szymczak from Software Mansion, an expert agency, and I’d like to work on this issue!

When working on this issue I got one thought concerning StatusBar during selection mode. I think we shouldn't show it during selection mode:

When clicking on anything on status bar Selection mode is cancelled

https://github.com/user-attachments/assets/e0d1c53a-1a56-440c-99a4-57774180e709

We have already hidden filters button and Type selector, so it doesn't make sense to give user option to choose Status
It's cluttering the screen
I could remove StatusBar from selection mode and put this change in PR that would be linked to this task
WDYT @luacmartins

Yeah, I think I agree with that. cc @Expensify/design for thoughts there too, but what you laid out above makes sense to me.

How do you guys like it? @dannymcclain @shawnborton @luacmartins
https://github.com/user-attachments/assets/09e7ae47-6b65-4f6c-abca-40eae1addf26

Once again, totally agree with all of Shawn's comments.
I think it should scroll away at the same pace as the content when you're at the top, but when you're scrolled down and scroll back up, I do think it should come in with a snappier animation than the regular scroll since we're showing it "in the middle" of a list of item. And then if you scroll down again (without going all the way to the top) I think it would be okay for it to go away with a bit more juice than the normal scroll (since again, it's not really in its home/resting place). Does that make any sense at all?? 😅 😵💫

Right now it seems like we are just hiding that area as soon as we detect a single scroll, is that correct?

Yeah, that's how it's currently implemented, as it's the easier solution and I wanted to know your opinion. I'll try to adjust to your comments, but doing so is pretty hard, because of the limitations of SelectionList, which we are forced to use(the outcome may be laggy or not so smooth).
Anyway I'll ping you when I have some new!

https://github.com/user-attachments/assets/280f89c7-dad9-4d4a-b788-25b1c63d2cb2
This is what I managed to come up with:

When user scrolls down the tab is hiding with the same speed as the user scrolls.
When user scrolls up the drawer is put up to full height at a constant speed
WDYT @dannymcclain @shawnborton

Feels solid to me! I would get rid of the gap below the status tabs though, and have that be part of the gap on top of the rows, if that makes sense.

Yup! Perhaps we could keep the padding but reduce it to 8px or something - mostly just thinking that we had too much padding below it previously and it felt a bit clunky?

mostly just thinking that we had too much padding below it previously and it felt a bit clunky?

Yeah I agree. I like your suggestion of trying 8px to see what that's like. We just need a little bit of separation.

Reduced padding to 8 and I think it looks neat 😃

Can you share a video of that?

https://github.com/user-attachments/assets/fed4b798-52af-4574-a204-f4c07764f4a9
Here you go

Cool, I think we just need to add some padding back to the top of the rows so that we get a larger gap between the status tabs and the rows:

Let me know if that makes sense. We probably need to add like 12px there to make up for the 12px we shaved off from the tabs area.

Are talking about something like this?
https://github.com/user-attachments/assets/e1b7cd59-5e12-45b3-b805-bfdf9875fdc3

Yup, that spacing looks correct.

There was a need for small refactor, but this should be ready for C+ review tomorrow!

PR was merged

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@rayane-djouah] The PR that introduced the bug has been identified. Link to the PR:
[ ] [@rayane-djouah] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] [@rayane-djouah] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ] [@rayane-djouah] Determine if we should create a regression test for this bug.
[ ] [@rayane-djouah] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ] [@kadiealexander] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Payouts due:

[ ] Contributor+: $250 @rayane-djouah (Offer link)

Upwork job is here.


Add Travis badge

What's up with this?
https://travis-ci.org/fisherman/awesome-fish

@bucaran I fixed invalid issues


Lack of direction compatibility in Grid2

Summary
Since V6 Grid became deprecated and Grid2 recommended.
Unfortunately it's not possible to convert from Grid to Grid2 since Grid2 doesn't support the direction property. So no column direction is allowed.
Goal:
Grid2 items can be also arranged in column direction.
Examples
`

`
Motivation
Refactor Code from Grid to Grid2
Search keywords: Grid2 Grid direction column

Thanks for the report, @RunRanger. The direction prop is available in Grid2, although I see that it behaves differently than Grid. Is this what you're referring to, or is it something else?

Thank you for your response!
Example with deprecated Grid and new Grid2:
https://stackblitz.com/edit/stackblitz-starters-6zeyer?file=src%2FApp.tsx
Direction prop doesn't work properly for "column". It's also mentioned in the doku. But since the normal Grid becoming deprecated there's no alternative to replace since Grid2 doesn't support column-direction.

@RunRanger Can you explain the need for using Grid with direction column? In my opinion, the Grid should always be row (with its limitation). If you want to fill the items by row, please consider using CSS Grid with grid-auto-flow: column

@siriwatknp It doesn't happen often, but as soon as I don't want a page to be scrollable (fixed height) or elements such as full-screen dialogues or similar, vertical grids are very useful.
Since you can normally also set columns in CSS for grids, my expectation as a user would be that this is also available for the MUI component.
Of course, you could also recreate this yourself with your own CSS. But for me the question arises as to why basic functionalities are restricted with a version upgrade. Also it would be better from a coding point of view if you didn't have to differentiate between row grids and vertical grids.

I'd expect the size prop in Grid2 items to be respected when using column direction, only that the size is calculated vertically instead of horizontally, because the axis has changed. I'd assume this is the mental model for most people. Is there a technical limitation for this? I did a quick test in https://stackblitz.com/edit/stackblitz-starters-hwnzzp?file=src/App.tsx switching width for height in the devtools and it seems to work properly. I'm sure I'm missing more details but I'm curious to know if we could achieve this.

@aarongarciah it could work, the height of the container would have to be set. Adding the new feature and waiting for upvotes labels.

How does a "Grid" component fail at providing a simple grid?
https://codesandbox.io/p/sandbox/4ftdsc

Hey @ZacharyACoon, what are you trying to achieve? If you provide an explanation, we might be able to help you.


boards: bbc_microbit_v2: Add buzzer

Tie pwm1 to buzzer pin and adjust sample.

Hi @kartben - I see you were auto-assigned.  Would there be more potential reviewers than those in the list?

@anangl could you help review?

can you also update the sample.yaml?

@larsgk 👆 :)

can you also update the sample.yaml?

@larsgk 👆 :)

Sorry...missed that. Will do 🙂

can you also update the sample.yaml?

@larsgk 👆 :)

Sorry...missed that. Will do 🙂

@kartben - just added bbc_microbit_v2 to sample.yml - how do I verify it will be picked up?

looks good, but you have compliance issues that'll need fixing :)

I've been struggling with LE Audio all day - so I probably missed it, but what compliance issues?


Request for license clarification

Hey rules_itest maintainers!
We're evaluating pulling this in for assisting our more complicated unit tests. There's no official license listed in the repo root, so we are hoping to get clarification on allowed usage here. Would that be possible to get updated?

Hi, I've added an MIT license. I'm guessing that works for you, but please let me know if it doesn't and we can figure something out.

Yes, that's perfect. Thanks for handling that so quickly! Looking forward to trying it out.


Defensive spore crawlers

Create one or more spore crawlers on each base to defend against:

Oracle;
Banshee;
Battle-cruiser;
Mutalisk;

There is a rudimentary version already: emergency() in making.py


Changes to run v1.5 directly from Maven Central

Dear @bwaldvogel , DKPro (https://github.com/dkpro/dkpro-core) has a dependency on liblinear 1.5, and we would like to have that dependency downloaded directly from Maven Central (currently, only versions >=1.8 of liblinear are kept there). We need to keep the old group id/artifact id though (liblinear.liblinear).
I provided the changes needed for packaging a 1.51 version without the need of other dependencies apart from the ones already in Maven Central.
Please, would it be possible for you to incorporate those changes to your repository and uploading the new jar to Maven Central?
Thank you,
Beto

These changes are needed to upload v.1.5 to Maven Central:

Use netlib-java 0.9.3 dependency from Maven Central, instead of using BLAS 0.8 with manual dependency resolution.
Updates to Tron.java due to newer BLAS version in netlib-java 0.9.3
Updates in the pom.xml (maybe some extra configuration is needed)

Why is upgrading to latest liblinear-java not an option?

Actually, we have a transitive dependency, DKPro uses a third-party module that, by it's turn, depends on liblinear 1.5. Thus, to upgrade to the the latest liblinear, we would have to fork that third-party module, something that we'd prefer not to do.

Hi, @bwaldvogel , do you think you will be able to integrate the changes and upload the updated version to maven central?

Couldn’t you overwrite the version of liblinear that gets pulled in? With your proposed patch you would need to force version 1.51 over 1.5 anyway.

Yes, that would be fine for us. I've updated the pom.xlm to 1.5.

With that change would it be ok for you uploading 1.5 to Maven Central then?

Actually I meant the latest version: 1.95.

The problem is, we intend to bundle and upload to Maven Central the third party module that uses liblinear. And, since liblinear group id changed between 1.5 and 1.95, we'd have to change the source code from that third party module in order to support that, something we want to avoid (that third party project is frozen in Google Code). At the other hand, if liblinear 1.5 is present in Maven Central with the original group id, we'll only have to update the third party module pom (to use liblinear 1.5 instead of 1.51 - no source code changes) when we bundle it.

I’ve started branch 1.7 that could be released as version 1.7.1. Please note that I cannot release to Maven central with groupId liblinear. However, version 1.7.1 would live in the (old) Java package liblinear and has no dependencies to other libraries such as BLAS.
Could you test the temporary snapshot liblinear-1.7.1-SNAPSHOT.jar if it would be working for you?

I tested the 1.7.1 snapshot that you provided, it seems to work fine. Please, go ahead with the release.  :)

Released version 1.7.1.

Thank you, @bwaldvogel !


[SMALLFIX]fix a typo

https://alluxio.atlassian.net/browse/ALLUXIO-2523

Can one of the admins verify this patch?

Jenkins, add to whitelist

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13137/
Test PASSed.

Merged build finished. Test PASSed.

LGTM. thanks for the typo fix!


fix: Update travis-ci to use uptrend-scripts

What: Fix travis-ci config to use uptrend-scripts in the after_success step

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix(nix): Fix install script for version > 2.23

Starting with nix 2.24, the binary is located under buildStatic.nix.x86_64-linux instead of buildStatic.x86_64-linux.
Without this commit:
ubuntu@125e8aa7e907:/$ install-tool nix 2.24
installing v2 tool nix v2.24
[13:40:49.461] INFO (87): Installing tool<EMAIL_ADDRESS>Download failed: https://hydra.nixos.org/job/nix/maintenance-2.24/buildStatic.x86_64-linux/latest/download-by-type/file/binary-dist
Download failed, retrying
Download failed: https://hydra.nixos.org/job/nix/maintenance-2.24/buildStatic.x86_64-linux/latest/download-by-type/file/binary-dist
Download failed, retrying
Download failed: https://hydra.nixos.org/job/nix/maintenance-2.24/buildStatic.x86_64-linux/latest/download-by-type/file/binary-dist
Download failed: https://hydra.nixos.org/job/nix/maintenance-2.24/buildStatic.x86_64-linux/latest/download-by-type/file/binary-dist
[13:40:52.311] INFO (137): Downloading file ...
    url: "https://hydra.nixos.org/job/nix/maintenance-2.24/buildStatic.x86_64-linux/latest/download-by-type/file/binary-dist"
    output: "/tmp/50789f3416da6a7a362045e5add6d2ba81fef302b1678eae91ab63978e430317/binary-dist"
[13:40:52.589] ERROR (137):
[13:40:52.590] FATAL (137): Download failed in 278ms.
[13:40:52.653] ERROR (87): Command failed with exit code 1: /usr/local/containerbase/bin/install-tool.sh nix 2.24
[13:40:52.653] FATAL (87): Install tool nix failed in 3.1s.

With this commit:
ubuntu@51abd3626c1e:/$ install-tool nix 2.24
installing v2 tool nix v2.24
[13:47:18.920] INFO (5): Installing tool<EMAIL_ADDRESS>linking tool nix v2.24
nix (Nix) 2.24.1
[13:47:26.446] INFO (5): Install tool nix succeeded in 7.5s.

Closing as duplicate of #3066.


Please add description to CHEBI:142575 and 142576

Please add the following Description to
ChEBI:142575 A cholesterol derivative in which one of the hydrogen attached to the C25 has been replaced by another atom or group.
ChEBI:142576 A cholesteryl beta-D-glucoside derivative in which one of the hydrogen attached to the C25 of the cholesterol has been replaced by another atom or group.
Thanks

I have now checked both entries and have added a definition to the entries.
Best Regards,
Adnan


Fix for issue with creating new signalR.HubConnection()

Great guide to get started with SignalR, thanks. Just a minor issue as the SignalR Connection was throwing an error stating that 'protocol' is required. I fixed this by replacing the new signalR Hub Connection line in chat.js with the following:
const connection = new signalR.HubConnectionBuilder()
.withUrl("/chathub")
.build();
Source: https://www.npmjs.com/package/@aspnet/signalr
This also worked with the latest version of @aspnet/signalr (1.0.0-rc1-update1 currently) as I initially thought the issue was with NuGet and Npm version mismatches but it didn't work with the same versions anyway (1.0.0-preview2-final) before I replaced how the hub connection is initialised.

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

ID: 778aaeae-2fa8-fb73-b644-8e99ee06398e
Version Independent ID: 159a95c8-7afd-bb03-fdfc-2323559ef50a
Content: Get started with SignalR on ASP.NET Core
Content Source: aspnetcore/signalr/get-started.md
Service: unspecified
GitHub Login: @rachelappel
Microsoft Alias: rachelap

@natsch93  Thanks for the feedback.
@rachelappel  can you get this fixed this week?

@natsch93 Thanks for the comment, however, you must use the full path in the .NET client when you use withUrl.  The shorter “/chathub” form only works because it’s on a web page that itself has a URL, so there’s something to resolve relative to. Otherwise, it will error,

Hey folks,
Is there a best practice solution for this issue yet?
Thanks

@hellopop Hello there! See the above comment. Use the full path, that's the proper way to do it.

Hi.
@rachelappel  If I understand you correctly you want to write out the entire url in the .ts file.
This is bad practice. How does this work with multiple environments. The URL will be different from Dev, Test, QA, and Production. The code should be URL agnostic. Even hard coding all the different urls and switching between them is bad practice. The code then needs to be recompiled for a url change.


Font size in password list not adjustable and too large on Windows

The list should use the configurable font size on separately adjustable, i.e.  FontChooser would be desirable

Hopefully fixed now ...

Hopefully fixed now ...


create _tryEnsureMessageMember in listener.ts

#178

Agree. If we have to do something like this a second time, we will introduce a new abstraction. Perhaps called MessageTransform or something.


Rework stage retry

After revisiting the stage retry feature, I found some obvious bugs that were not ready for production use. This issue is to track the design,existing problems and solutions.
Background and design
Some background and design are included in the previous design doc and github issues.
You can search the github to retrieve them to know more about this feature.

https://github.com/apache/incubator-uniffle/issues/477
https://docs.google.com/document/d/1OGswqDDQ52rpw5Lat-FpEGDfX1T6EFXYLC7L0G5O4WE/edit?usp=sharing
https://github.com/apache/incubator-uniffle/issues/825

The stage retry whole design is based on the Spark's fetchFailedException , once spark scheduler accepts this exception thrown from task, it will not schedule the next tasks in this stage and trigger the stage resubmit to run. That means uniffle will use this exception as the way to trigger whatever encountering fetch/write failure.
Leveraging from this mechanism, Uniffle wants to hack this to acheive the stage retry ability to improve the spark jobs stability, especially on the case of shuffle-server shutdown unnormally.
The shuffle task failure could be split into 2 parts: write failure and read(fetch) failure, that should be digged separately and together. Below description will be shown by my understanding correct solution.
All the below design architecture is based on the consensus that we want to keep the spark's original semantic of shuffleId.
Write failure
Once the task failed on the write failure that may be shuffle-server hang or shutdown or network lost..., task will ask shuffle manager whether throwing spark's fetchFailedException.
At this time, shuffle manager will check whether the task failure reaches the spark max failure threshold. Once this condition is satisfied, this will make task throw and fail.
To avoid the data duplication, the unregister map output tracker related with the shuffleId is necessary.
Fetch failure
Fetch failure shows the similar logic with the above write failure.
The special point of fetch failure is that will rerun all the map tasks from the upstream stage, which is different with the spark vanilla shuffle service that only will trigger the maps executed on the broken servers.
Write + fetch failure together
Write and fetch failures won't happen at the same time, that's ensured by the spark, that's not pipelined data flow.
For uniffle shuffle manager, the write and fetch failure problem is on the retry condition. But I think the shuffle manager only needs to worry about the reported index of task attempts, whatever the failure type.
QA
How to clear previous stage attempt data and reassign
Before answering this question, another question is that do you really need to clear previous stage data. I think this is necessary

Current blockId layout's taskAttemptId is not real unique taskId, that means we can't depend this to filter the retry tasks outdate data. (Although in the following QA, I will re-introduce this real task attempt id into blockId layout)
Too much data will make client read unnecessary memory data, although the localfile data could be filtered out by the index file. This will bring too much cost
Outdate data remains on the shuffle-server that will waste disk/memory space, this is unnessary

Based on the above thought, let's answer the initial question.
The unregister and reassign will occur on the first request that reaches the retry condition with the lock to make other tasks' ask requests to hang.
Once the reassign is finished, shuffle manager will register the next stage attempt shuffle to the reassignment shuffle-servers. At this time, server will accept this request and then to clear out the previous data, including in the memory/disk/hdfs.
We hope this deletion is quick, but properly not. From my survey, the 200g disk file with 3000 partition costs 40s. this is not accpetable for a grpc request.
So the two phase deletion should be introduced to solve the problem of data visibility and delete speed, that splits the deletion into rename sync and delete async 2 phases.
This is based on the rename quick speed of disk and hdfs. If having object store, the first phase will not use the rename mechansim, or store some metadata into memory and then to rename. However, there are always ways to solve the OSS storage type.
And in now codebase, the report failure and reassignOnStageRetry is splitted into 2 rpcs, it's necessary to unify them into one.
How to ensure shuffle data consistency in different stage attempt
Everything looks fine now, but some corner cases are ignored especially on the high-concurrent jobs.
When deleting previous shuffle data, the another writer or reader may read the same partition data.
For the writer, it's hard to use lock to ensure consistency as it need to ensure write throughput. So in this case, we hope that the partial leak data could be filtered out from the client side by the task attempt id. Based on this, the real unique task attemptId will be introduced here to solve this problem, which may bring some limitation for the huge jobs, but I think this is necessary and worthwhile.
For the reader, the premise of accuracy is to obtain the real blockId bitmap, so locking is required here by stage attempt number check.
Next step
The current code has some bugs described on the above Q&A, so this is time to create some issues to solve them.

Unify the fetch failure + write failure retry checking into the RssStageResubmitManager, the checking logic may be different but we could distingush them and use different strategies.
RPC merge from 2 rpcs of reportXXFailure and reassignOnStageRetry into reportXXFailure, that include the reassign into one request.
Introduce the real unique taskAttemptId into uniffle by the indiviual config option to make client filter out previous stage data correctly
Ensure the getting shuffle result safe
Some bugs

once spark scheduler accepts this exception thrown from task, it will kill all the running tasks in this stage
AFAIK,  it will not kill any running tasks if FetchFailed occured.

The stage retry whole design is based on the Spark's fetchFailedException , once spark scheduler accepts this exception thrown from task, it will kill all the running tasks in this stage and trigger the stage resubmit to run.

AFAIK, vanillia spark will not kill any task if FetchFailed occured, new stage attempt will submit missing tasks which have no registered mapstatus. Does it have same behavior with rss enabled?

The stage retry whole design is based on the Spark's fetchFailedException , once spark scheduler accepts this exception thrown from task, it will kill all the running tasks in this stage and trigger the stage resubmit to run.

AFAIK, vanillia spark will not kill any task if FetchFailed occured, new stage attempt will submit missing tasks which are not finished. Does it have same behavior with rss enabled?

Good to know this, and I have checked this part that spark will not kill all running tasks. Let me fix this description

Exchange reuse.
Map stiil runs after stage finished
Limit
Stage fail, shuffle will consists of multple attempts.

I don't find out any concept that the limit operator will get the stage attempt 0 + stage attempt 1 data to be as the normal data pipeline. Could you give me some background or spark issues? @jerqi

Could you help review this? @advancedxy I want to go on to finish this feature.

Can you elaborate on why the current block id scheme does not work for stage retry given all data of previous stage gets erased?

Sorry for the late reply (Pity. I'm busy for my daily work). If the stage retry, the taskAttemptId in the blockId is not unique for the multiple stage retry. Right?

I strongly object to moving back to the original unique task attempt id which limits the number of tasks or partitions, which renders Uniffle unusable in our production environment.我强烈反对回到原来的唯一任务尝试 ID，这会限制任务或分区的数量，从而导致 Uniffle 在我们的生产环境中无法使用。
I am happy to discuss alternative approaches like adding the stage attempt no, similar to us adding the task attempt no (#1529), to the block id.我很高兴讨论替代方法，例如添加阶段尝试编号，类似于我们将任务尝试编号 ( #1529 ) 添加到块 ID。

Yes. This is the important concern for this feature. So I want to try whether to add the retry attempt number into memory/file prefix or memory data structure indicator

Before retrying a stage, isn't all data deleted of the earlier attempt?


Zigbee2mqtt don't start with no error in the log

Description of the issue
Zigbee2mqtt don't start but it recognise devices and connect to mosquitto
Addon version
1.30.2-1
Platform
Home Assistant 2023.2.5
Supervisor 2023.03.1
Interface utilisateur : 20230202.0 - latest
Logs of the issue (if applicable)
[19:07:21] INFO: Preparing to start...
[19:07:23] INFO: Socat not enabled
[19:07:31] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-03-21 19:07:40: Logging to console and directory: '/config/zigbee2mqtt/log/2023-03-21.19-07-40' filename: log.txt
Zigbee2MQTT:info  2023-03-21 19:07:40: Starting Zigbee2MQTT version 1.30.2 (commit #unknown)
Zigbee2MQTT:info  2023-03-21 19:07:40: Starting zigbee-herdsman (0.14.96)
Zigbee2MQTT:info  2023-03-21 19:07:44: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2023-03-21 19:07:44: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2023-03-21 19:07:44: Currently 4 devices are joined:
Zigbee2MQTT:info  2023-03-21 19:07:44: cagibi (0xa4c138d3764c3937): TS0011 - TuYa Smart light switch - 1 gang (EndDevice)
Zigbee2MQTT:info  2023-03-21 19:07:44: inter hall (0xa4c13845d1b4b4b0): TS0012 - TuYa Smart light switch - 2 gang (EndDevice)
Zigbee2MQTT:info  2023-03-21 19:07:44: prise (0x00124b0022d4d013): SA-003-Zigbee - eWeLink Zigbee smart plug (Router)
Zigbee2MQTT:info  2023-03-21 19:07:44: 0xa4c138f223f4bb2c (0xa4c138f223f4bb2c): TS0041 - TuYa Wireless switch with 1 button (EndDevice)
Zigbee2MQTT:info  2023-03-21 19:07:44: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2023-03-21 19:07:44: Connecting to MQTT server at mqtt://core-mosquitto:1883
Zigbee2MQTT:info  2023-03-21 19:07:45: Connected to MQTT server
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
Zigbee2MQTT:info  2023-03-21 19:07:45: Started frontend on port <IP_ADDRESS>:8099
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"unknown","coordinator":{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"},"log_level":"info","network":{"channel":11,"extendedPanID":"0x00124b0024c31a38","panID":6754},"permit_join":false,"version":"1.30.2"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/switch/0xa4c138d3764c3937/switch/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"command_topic":"zigbee2mqtt/cagibi/set","device":{"identifiers":["zigbee2mqtt_0xa4c138d3764c3937"],"manufacturer":"TuYa","model":"Smart light switch - 1 gang (TS0011)","name":"cagibi"},"json_attributes_topic":"zigbee2mqtt/cagibi","name":"cagibi","payload_off":"OFF","payload_on":"ON","state_topic":"zigbee2mqtt/cagibi","unique_id":"0xa4c138d3764c3937_switch_zigbee2mqtt","value_template":"{{ value_json.state }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/sensor/0xa4c138d3764c3937/power_on_behavior/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0xa4c138d3764c3937"],"manufacturer":"TuYa","model":"Smart light switch - 1 gang (TS0011)","name":"cagibi"},"enabled_by_default":false,"entity_category":"config","icon":"mdi:power-settings","json_attributes_topic":"zigbee2mqtt/cagibi","name":"cagibi power on behavior","state_topic":"zigbee2mqtt/cagibi","unique_id":"0xa4c138d3764c3937_power_on_behavior_zigbee2mqtt","value_template":"{{ value_json.power_on_behavior }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/select/0xa4c138d3764c3937/power_on_behavior/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"command_topic":"zigbee2mqtt/cagibi/set/power_on_behavior","device":{"identifiers":["zigbee2mqtt_0xa4c138d3764c3937"],"manufacturer":"TuYa","model":"Smart light switch - 1 gang (TS0011)","name":"cagibi"},"entity_category":"config","icon":"mdi:power-settings","json_attributes_topic":"zigbee2mqtt/cagibi","name":"cagibi power on behavior","options":["off","previous","on"],"state_topic":"zigbee2mqtt/cagibi","unique_id":"0xa4c138d3764c3937_power_on_behavior_zigbee2mqtt","value_template":"{{ value_json.power_on_behavior }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/sensor/0xa4c138d3764c3937/backlight_mode/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0xa4c138d3764c3937"],"manufacturer":"TuYa","model":"Smart light switch - 1 gang (TS0011)","name":"cagibi"},"enabled_by_default":false,"entity_category":"config","icon":"mdi:lightbulb","json_attributes_topic":"zigbee2mqtt/cagibi","name":"cagibi backlight mode","state_topic":"zigbee2mqtt/cagibi","unique_id":"0xa4c138d3764c3937_backlight_mode_zigbee2mqtt","value_template":"{{ value_json.backlight_mode }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/select/0xa4c138d3764c3937/backlight_mode/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"command_topic":"zigbee2mqtt/cagibi/set/backlight_mode","device":{"identifiers":["zigbee2mqtt_0xa4c138d3764c3937"],"manufacturer":"TuYa","model":"Smart light switch - 1 gang (TS0011)","name":"cagibi"},"entity_category":"config","icon":"mdi:lightbulb","json_attributes_topic":"zigbee2mqtt/cagibi","name":"cagibi backlight mode","options":["off","normal","inverted"],"state_topic":"zigbee2mqtt/cagibi","unique_id":"0xa4c138d3764c3937_backlight_mode_zigbee2mqtt","value_template":"{{ value_json.backlight_mode }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/sensor/0xa4c138d3764c3937/linkquality/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0xa4c138d3764c3937"],"manufacturer":"TuYa","model":"Smart light switch - 1 gang (TS0011)","name":"cagibi"},"enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:signal","json_attributes_topic":"zigbee2mqtt/cagibi","name":"cagibi linkquality","state_class":"measurement","state_topic":"zigbee2mqtt/cagibi","unique_id":"0xa4c138d3764c3937_linkquality_zigbee2mqtt","unit_of_measurement":"lqi","value_template":"{{ value_json.linkquality }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/switch/0xa4c13845d1b4b4b0/switch_left/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"command_topic":"zigbee2mqtt/inter hall/left/set","device":{"identifiers":["zigbee2mqtt_0xa4c13845d1b4b4b0"],"manufacturer":"TuYa","model":"Smart light switch - 2 gang (TS0012)","name":"inter hall"},"json_attributes_topic":"zigbee2mqtt/inter hall","name":"inter hall left","payload_off":"OFF","payload_on":"ON","state_topic":"zigbee2mqtt/inter hall","unique_id":"0xa4c13845d1b4b4b0_switch_left_zigbee2mqtt","value_template":"{{ value_json.state_left }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/switch/0xa4c13845d1b4b4b0/switch_right/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"command_topic":"zigbee2mqtt/inter hall/right/set","device":{"identifiers":["zigbee2mqtt_0xa4c13845d1b4b4b0"],"manufacturer":"TuYa","model":"Smart light switch - 2 gang (TS0012)","name":"inter hall"},"json_attributes_topic":"zigbee2mqtt/inter hall","name":"inter hall right","payload_off":"OFF","payload_on":"ON","state_topic":"zigbee2mqtt/inter hall","unique_id":"0xa4c13845d1b4b4b0_switch_right_zigbee2mqtt","value_template":"{{ value_json.state_right }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/sensor/0xa4c13845d1b4b4b0/power_on_behavior/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0xa4c13845d1b4b4b0"],"manufacturer":"TuYa","model":"Smart light switch - 2 gang (TS0012)","name":"inter hall"},"enabled_by_default":false,"entity_category":"config","icon":"mdi:power-settings","json_attributes_topic":"zigbee2mqtt/inter hall","name":"inter hall power on behavior","state_topic":"zigbee2mqtt/inter hall","unique_id":"0xa4c13845d1b4b4b0_power_on_behavior_zigbee2mqtt","value_template":"{{ value_json.power_on_behavior }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/select/0xa4c13845d1b4b4b0/power_on_behavior/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"command_topic":"zigbee2mqtt/inter hall/set/power_on_behavior","device":{"identifiers":["zigbee2mqtt_0xa4c13845d1b4b4b0"],"manufacturer":"TuYa","model":"Smart light switch - 2 gang (TS0012)","name":"inter hall"},"entity_category":"config","icon":"mdi:power-settings","json_attributes_topic":"zigbee2mqtt/inter hall","name":"inter hall power on behavior","options":["off","previous","on"],"state_topic":"zigbee2mqtt/inter hall","unique_id":"0xa4c13845d1b4b4b0_power_on_behavior_zigbee2mqtt","value_template":"{{ value_json.power_on_behavior }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/sensor/0xa4c13845d1b4b4b0/backlight_mode/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0xa4c13845d1b4b4b0"],"manufacturer":"TuYa","model":"Smart light switch - 2 gang (TS0012)","name":"inter hall"},"enabled_by_default":false,"entity_category":"config","icon":"mdi:lightbulb","json_attributes_topic":"zigbee2mqtt/inter hall","name":"inter hall backlight mode","state_topic":"zigbee2mqtt/inter hall","unique_id":"0xa4c13845d1b4b4b0_backlight_mode_zigbee2mqtt","value_template":"{{ value_json.backlight_mode }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/select/0xa4c13845d1b4b4b0/backlight_mode/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"command_topic":"zigbee2mqtt/inter hall/set/backlight_mode","device":{"identifiers":["zigbee2mqtt_0xa4c13845d1b4b4b0"],"manufacturer":"TuYa","model":"Smart light switch - 2 gang (TS0012)","name":"inter hall"},"entity_category":"config","icon":"mdi:lightbulb","json_attributes_topic":"zigbee2mqtt/inter hall","name":"inter hall backlight mode","options":["off","normal","inverted"],"state_topic":"zigbee2mqtt/inter hall","unique_id":"0xa4c13845d1b4b4b0_backlight_mode_zigbee2mqtt","value_template":"{{ value_json.backlight_mode }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/sensor/0xa4c13845d1b4b4b0/linkquality/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0xa4c13845d1b4b4b0"],"manufacturer":"TuYa","model":"Smart light switch - 2 gang (TS0012)","name":"inter hall"},"enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:signal","json_attributes_topic":"zigbee2mqtt/inter hall","name":"inter hall linkquality","state_class":"measurement","state_topic":"zigbee2mqtt/inter hall","unique_id":"0xa4c13845d1b4b4b0_linkquality_zigbee2mqtt","unit_of_measurement":"lqi","value_template":"{{ value_json.linkquality }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/switch/0x00124b0022d4d013/switch/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"command_topic":"zigbee2mqtt/prise/set","device":{"identifiers":["zigbee2mqtt_0x00124b0022d4d013"],"manufacturer":"eWeLink","model":"Zigbee smart plug (SA-003-Zigbee)","name":"prise","sw_version":"1.0.5"},"json_attributes_topic":"zigbee2mqtt/prise","name":"prise","payload_off":"OFF","payload_on":"ON","state_topic":"zigbee2mqtt/prise","unique_id":"0x00124b0022d4d013_switch_zigbee2mqtt","value_template":"{{ value_json.state }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/sensor/0x00124b0022d4d013/linkquality/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0x00124b0022d4d013"],"manufacturer":"eWeLink","model":"Zigbee smart plug (SA-003-Zigbee)","name":"prise","sw_version":"1.0.5"},"enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:signal","json_attributes_topic":"zigbee2mqtt/prise","name":"prise linkquality","state_class":"measurement","state_topic":"zigbee2mqtt/prise","unique_id":"0x00124b0022d4d013_linkquality_zigbee2mqtt","unit_of_measurement":"lqi","value_template":"{{ value_json.linkquality }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/sensor/0xa4c138f223f4bb2c/battery/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0xa4c138f223f4bb2c"],"manufacturer":"TuYa","model":"Wireless switch with 1 button (TS0041)","name":"0xa4c138f223f4bb2c"},"device_class":"battery","enabled_by_default":true,"entity_category":"diagnostic","json_attributes_topic":"zigbee2mqtt/0xa4c138f223f4bb2c","name":"0xa4c138f223f4bb2c battery","state_class":"measurement","state_topic":"zigbee2mqtt/0xa4c138f223f4bb2c","unique_id":"0xa4c138f223f4bb2c_battery_zigbee2mqtt","unit_of_measurement":"%","value_template":"{{ value_json.battery }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/sensor/0xa4c138f223f4bb2c/action/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0xa4c138f223f4bb2c"],"manufacturer":"TuYa","model":"Wireless switch with 1 button (TS0041)","name":"0xa4c138f223f4bb2c"},"enabled_by_default":true,"icon":"mdi:gesture-double-tap","json_attributes_topic":"zigbee2mqtt/0xa4c138f223f4bb2c","name":"0xa4c138f223f4bb2c action","state_topic":"zigbee2mqtt/0xa4c138f223f4bb2c","unique_id":"0xa4c138f223f4bb2c_action_zigbee2mqtt","value_template":"{{ value_json.action }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/sensor/0xa4c138f223f4bb2c/linkquality/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0xa4c138f223f4bb2c"],"manufacturer":"TuYa","model":"Wireless switch with 1 button (TS0041)","name":"0xa4c138f223f4bb2c"},"enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:signal","json_attributes_topic":"zigbee2mqtt/0xa4c138f223f4bb2c","name":"0xa4c138f223f4bb2c linkquality","state_class":"measurement","state_topic":"zigbee2mqtt/0xa4c138f223f4bb2c","unique_id":"0xa4c138f223f4bb2c_linkquality_zigbee2mqtt","unit_of_measurement":"lqi","value_template":"{{ value_json.linkquality }}"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'zigbee2mqtt/cagibi', payload '{"backlight_mode":null,"linkquality":120,"power_on_behavior":null,"state":"OFF"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'zigbee2mqtt/inter hall', payload '{"backlight_mode":null,"linkquality":105,"power_on_behavior":null,"power_on_behavior_left":"previous","state_left":"OFF","state_right":"OFF"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'zigbee2mqtt/prise', payload '{"linkquality":30,"state":"ON"}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'zigbee2mqtt/0xa4c138f223f4bb2c', payload '{"action":null,"battery":90,"linkquality":null}'
Zigbee2MQTT:info  2023-03-21 19:07:45: Zigbee2MQTT started!
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'zigbee2mqtt/cagibi/mode', payload '{"backlight":null}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'zigbee2mqtt/inter hall/mode', payload '{"backlight":null}'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/sensor/0x00124b0022d4d013/power_on_behavior/config', payload 'null'
Zigbee2MQTT:info  2023-03-21 19:07:45: MQTT publish: topic 'homeassistant/select/0x00124b0022d4d013/power_on_behavior/config', payload 'null'
Zigbee2MQTT:info  2023-03-21 19:07:47: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"inter hall","ieee_address":"0xa4c13845d1b4b4b0"},"type":"device_announce"}'
Zigbee2MQTT:info  2023-03-21 19:07:47: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"inter hall"},"type":"device_announced"}'
Zigbee2MQTT:info  2023-03-21 19:07:49: MQTT publish: topic 'zigbee2mqtt/inter hall', payload '{"backlight_mode":null,"linkquality":90,"power_on_behavior":null,"power_on_behavior_left":"previous","state_left":"ON","state_right":"OFF"}'
Zigbee2MQTT:info  2023-03-21 19:07:49: MQTT publish: topic 'zigbee2mqtt/inter hall/mode', payload '{"backlight":null}'
Zigbee2MQTT:info  2023-03-21 19:13:52: MQTT publish: topic 'zigbee2mqtt/cagibi', payload '{"backlight_mode":null,"linkquality":120,"power_on_behavior":null,"state":"OFF"}'
Zigbee2MQTT:info  2023-03-21 19:13:52: MQTT publish: topic 'zigbee2mqtt/inter hall', payload '{"backlight_mode":null,"linkquality":90,"power_on_behavior":null,"power_on_behavior_left":"previous","state_left":"ON","state_right":"OFF"}'
Zigbee2MQTT:info  2023-03-21 19:13:52: MQTT publish: topic 'zigbee2mqtt/prise', payload '{"linkquality":30,"state":"ON"}'
Zigbee2MQTT:info  2023-03-21 19:13:52: MQTT publish: topic 'zigbee2mqtt/0xa4c138f223f4bb2c', payload '{"action":null,"battery":90,"linkquality":null}'
Zigbee2MQTT:info  2023-03-21 19:13:52: MQTT publish: topic 'zigbee2mqtt/cagibi/mode', payload '{"backlight":null}'
Zigbee2MQTT:info  2023-03-21 19:13:52: MQTT publish: topic 'zigbee2mqtt/inter hall/mode', payload '{"backlight":null}'
Zigbee2MQTT:info  2023-03-21 19:21:55: MQTT publish: topic 'zigbee2mqtt/prise', payload '{"linkquality":21,"state":"ON"}'
Zigbee2MQTT:info  2023-03-21 19:26:55: MQTT publish: topic 'zigbee2mqtt/prise', payload '{"linkquality":18,"state":"ON"}'

I tried to reconfigure mosquitto whitout succes
In device mosquitto shows

my only problem is that Z2m is shown as stopped; the first time I start it, it show the log but z2m remains stopped
if i press start again, nothing happens

I have exactly the same issue. Z2M log shows it as started, but on the addon page I have "red" dot and when I click Start nothing happens.
Zigbee2MQTT:info  2023-03-29 16:13:22: Zigbee2MQTT started!
Supervisor log shows:
23-03-29 16:13:38 WARNING (MainThread) [supervisor.addons.addon] 9336c2b0_zigbee2mqtt is already running!
23-03-29 16:19:18 WARNING (MainThread) [supervisor.addons.addon] core_mosquitto is already running!
When I try to open addon's WebUI the following message pops up:
Addon is not running. Please start it first.
Home Assistant 2023.3.6
Supervisor 2023.03.2
Operating System 9.5
Frontend 20230309.1 - latest
MQTT Broker version: 6.2.0
Zigbee2MQTT version: 1.30.2-1
Zigbee dongle: Sonoff ZBDongle-E ZigBee Dongle Plus-E EFR32MG21
Coordinator firmware version: '{"meta":{"maintrel":"3 ","majorrel":"6","minorrel":"10","product":8,"revision":"<IP_ADDRESS> build 297"},"type":"EZSP v8"}'
Please help! :(


Validate RHEL/CentOS 8.3

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.3_release_notes/index
https://lists.centos.org/pipermail/centos-announce/2020-December/035874.html
gz#14177

Please validate RHEL/CentOS8 with Docker CE 19.03.x as well as 20.10.x, see available releases here: https://download.docker.com/linux/centos/8/x86_64/stable/Packages/

Please validate RHEL/CentOS8 with Docker CE 19.03.x as well as 20.10.x, see available releases here: https://download.docker.com/linux/centos/8/x86_64/stable/Packages/

Docker 20.10.x is covered in https://github.com/rancher/rancher/issues/30406

Docker 20.10.x is covered in https://github.com/rancher/rancher/issues/30406

Duplicate of https://github.com/rancher/rancher/issues/31093


Crash upon saving or opening file under certain conditions

When, in a git initialized folder, I save a certain file multiple times, then it crashes on opening until I commit it. Then this reoccurs doing the same steps.
Reproduction Steps:

Open a git project
Open a file with a non default extension (ex template.theme)
Set it to php
Save the file
Edit the file
Save the file again

Expected behavior:
File get saved.
Observed behavior:
Atom crashes. And keeps crashing on open.
Screenshots and GIFs

Atom version: 1.2.0
OS and version: OS X 10.11.1
Installed packages:
None, created a clean install
Additional information:

Problem can be reproduced in safe mode: Yes
Problem started happening recently, didn't happen in an older version of Atom: Yes
Problem can be reliably reproduced, doesn't happen randomly: No
Problem happens with all files and projects, not only some files or projects: No

If someone can tell me how I can see the debug logs, I could try and debug it myself.

Thanks for the report, @haringsrob! It seems that you used the template from the contributing guide -- that's great! :zap: If you scroll a bit up from that template, you should see a section which has a line that tells you how to get the crash report on OSX:
"If you're reporting that Atom crashed, include a crash report with a stack trace from the operating system. On OSX, the crash report will be available in Console.app under "Diagnostic and usage information" > "User diagnostic reports". Include the crash report in the issue in a code block, a file attachment, or put it in a gist and provide link to that gist."

Hi,
Here it is:
https://gist.github.com/haringsrob/cc2626d965242385e34b
Regards,

Thanks, @haringsrob!
@zcbenz -- any ideas on this crash?


Namespaced controllers only show the top level name

For instance, MyNamespace::MyController will only appear as MyNamespace.
I've checked https://github.com/lessonly/slimy/blob/main/lib/slimy/rails/sli_concern.rb#L40 to ensure that self.class.name returns the fully qualified constant and it appears to do so. At some point between the class introspection and sending sli controller to datadog it is stripping the classname.
Checked https://github.com/lessonly/slimy/blob/main/lib/slimy/reporters/datadog.rb#L22-L26 and inspecting current_span as well as context.tags returns data as expected
current_span
=>
Name: rack.request
Span ID: XXXXX
Parent ID: 0
Trace ID: XXXXX
Type: web
Service: my_service
Resource: MyNamespace::MyController#new
Error: 0
Start:<PHONE_NUMBER>768532992
End: 0
Duration:
Allocations: 0
Tags: [
  runtime-id => XXXXXXXX,
  sli_status => failure,
  controller => MyNamespace::MyController,
  action => new,
  functional_area => my_area]

This seems to be more likely tied to a limitation of a Datadog graph


Show suggestion images and viewfield icons

When an ai-suggested sidewalk is selected, show images in Rapid left hand panel and viewfield icons on the map.
You can also accept the suggestion or ignore it. This PR is supposed to merged with streetview_workflow branch. Later PRs will add more functionality.
https://user-images.githubusercontent.com/65986784/112027289-463d2e00-8af4-11eb-8b32-73f9514e9814.mov

added some minor comments inline besides the question to @bhousel .
There were some additional UI ideas we've discussed - @amolkhad is the plan to add them in later PRs?

Yes, these will be done in subsequent PRs. Although need to figure few things for (2).

Planning to make a few more changes

Planning to make a few more changes

Cool, looks good so far 👍


App Release - patch 1.0.1

This app release introduces app doc from the developers site to this repo.

Assigning this PR to @nCastle1 to strategize for and release the patch.


added collapsible widget

Describe your changes
Added a collapsible widget with functionality of accordion.
Screenshots [Optional]
Issue ticket number and link
Closes #
closes #297
Checklist before requesting a review

[x] I have performed a self-review of my code
[ ] I have added tests
[x] I have added a changeset pnpm changeset add
[x] I have added example usage in the kitchen sink app

@anserwaseem can you please review and see if it meets the requirements you need?

@sagardspeed2 would need few more things:

item-template
ability to give my own icon
styles for collapsible head (I need to change its background colour) - low priority

@sagardspeed2 something like this?
Collapsibe:
  item-template:
     data
     name: item
     template:
         CollapsibleItem:
             label ${item.title}
             key: ${item.id}
             item:
                Text:
                    text: ${item.value}

@anserwaseem can you please review and see if it meets the requirements you need?

@sagardspeed2 would need few more things:

item-template
ability to give my own icon
styles for collapsible head (I need to change its background colour) - low priority

Added item-template, ability to give custom icon, also added ability to change the collapsible header and content background color


Add dockerfile

@afwillia Thanks for adding the Dockerfile.
It looks like the Dockerfile is using the schematic-rest-api branch and this PR is going to merge into the develop. I think there are more features could be added before we implement the Dockerfile. For example, add backing renv and implementing schematic API to develop branch first.
I just quickly tested the dockerfile and it failed to run due to miss data.table library. You might need to re-run the snapshot to ensure the required libraries are not missing in renv.lock.
I see you requested me for reviewing. Just to clarify, is this PR just for testing or we plan to add Dockerfile now?

@rrchai those are good points - I think I will keep this Dockerfile in the schem-api-feat-ui branch where I'm updating all the DCA + dashboard reticulate calls. We can keep this file out of develop for now. I tagged your review just to test this. Currently I'm the only one using the Dockerfile.


Request to Add a Splash Screen Feature

I would like to propose adding a splash screen feature to the app. Implementing a splash screen will enhance the user experience by providing a professional look and feel.

I want to add the splash screen to the app. Can you please assign it to me?

Sir, please add gssoc-extd and other labels to it


web actions should not project return when using extension .http

When using content extension .http with a path like demo/hello.http/pets/123 it will automatically try to project the field pets.123 from the return object.
This is not the use case I want, I want to be able to return a body and be able to access the path pets/123 (__ow_meta_path) to parse it and use it a path parameter in my web action.

Fixed by linked PR.

I wonder if we should remove all projections. I'm finding them increasingly frustrating to use.

Ha ! Finally you came around
I never love them and found them very confusing.


Suspected HMR issue in array-style webpack configs

I see that array-style webpack config support was added in this commit: https://github.com/aspnet/JavaScriptServices/commit/2241c55a9000c83592ea02dab54c6bc4359caacf
I'm trying to leverage this functionality with both configs requiring HMR support (herein lies the issue). Whichever config is listed first in the array supports HMR and the other results in failed requests <blah>.hot-update.json 404 (Not Found). Similarly if I comment out any one config the remaining functions with HMR as expected.
Having had a scan of the code, I suspect there's something around the fact the two configs share the same public path. @SteveSandersonMS does it seem likely/possible?
I'd like to provide a PR if you can help with the diagnosis. I may need some help getting the code to build on my machine for testing purposes.

Although I can't help you with the diagnosis, if you track this down and believe there's an issue in some code in this repo or the standard templates, please let us know the details!
I expect that you are right that the two configs would need to have different publicPath values for them to be used simultaneously (otherwise the HMR service for one would capture all the requests).

Sure thing


Add ValueHintType.Email for new Email column type

And I think if you just run make build after you're done with your final changes, the CI should be happy.

And I think if you just run make build after you're done with your final changes, the CI should be happy.

My make build is failing at the end, possibly related to my git origin, which may explain the CI failures.  Will look into it more tomorrow.
Writing /Users/coda/code/packs-sdk/index.ts -> /Users/coda/code/packs-sdk/dist/bundle.d.ts
Checking generated files...
Compiler option "skipLibCheck" is disabled to properly check generated output
Done in 7.11s
isolated-vm version matches, skipping.
Please config your git origin to git@github.com:coda/packs-sdk.git
make: *** [typedoc] Error 1

Oh and last tiny thing, let's bump the version in package.json to 0.9.0 and add an entry to CHANGELOG.md that briefly mentions the existence of ValueHintType.Email and that ValueHintType.Url will now create Link columns, a minor but technically breaking change.


Remove comment-based syntax for generic methods

This code is just copy/pasted from package:http.  We're going to remove it soon (once package:http publishes their current master on pub).  Rather than edit this code, I'm inclined to leave it until we can remove it.

ok


Common name

Set common name field to only accept one entry

Estimate is to add a validation function to ensure only one common name is added.


zoomEnabled not working

zoomEnabled not working

+1 Not working for me as well.

+1  kind of a deal breaker :(

same here

Will be fixed in https://github.com/openspacelabs/react-native-zoomable-view/pull/34/files


How to customize the record information before inserting into elastalert_status_silence index?

Hi,
We are releartning events/records based on querykey : [“hostname” , “message”] . its working properly. We want to create kibana dashboard to visualize, how many events/records are inserted into main index and how many events/records are triggered (here I am using email) and how many events are silenced/suppressed in given time range?
I know we can get the total events from main index(here it is test_elastalert) and triggered events count from elastalert_status and silenced events from elastalert_status_silence index. But I want to apply filters on hostname. Means I have to add hostname field from the main event into record before inserting  into elastalert_status and elastalert_status_silence. Can anyone please let  me know how to add “hostname” filed in each record before inserting into elastalert_status and elastalert_status_silence indexes?
Thanks,
Sudhakar

Hi,
Any comments on this please?
Thanks,
Sudhakar

I dont believe this can be done without making changes to the code

@Qmando / @thommor , Can you please let me know which file/method needs to be used for customizing the code to insert fields in elastalert_status_silence and elastalert_status index after parsing rules?


Multiple agents

Is it possible to have multiple agents in the environment and control them independently?

Thanks for the interest. For now this is not supported. But you can start multiple instances of environment on the same house, and control these environments separately.

But those multiple instances will be independent of each other. In other words, agent in one instance will be completely unaware of the second agent in a separate instance. Is that correct?

Yes.


IDE shows unresolved references for MPP Compose in androidMain source sets

This happens for me for a couple of months already. All MPP Compose references are red (unresolved) in all androidMain source sets in all IDEs. Other KMP libraries work fine. Everything compiles just fine.
Kotlin 1.7.0, 1.7.10
Compose 1.2.0-alpha01-dev753, 1.2.0-beta01
Gradle 7.4.2, 7.5.1
AGP 7.2.2.
I have tried different IDEs:

AS Chipmunk 2021.2.1 Patch 2
AS Dolphin 2021.3.1 RC 1
AS Flamingo 2022.2.1 Canary 1
IDEA Ultimate 2022.2.1

I have also tried different OSs - Ubuntu and macOS.
I have attached a reproducer project - Reproducer.zip.

Just wanted to add the link to the related discussions on Slack: https://kotlinlang.slack.com/archives/C3PQML5NU/p1652224566469179

If you apply the original androidx compose libraries to the Android source set (androidMain), the IDE issue is gone.

try specifying these two properties in gradle properties of the project & subprojects
kotlin.mpp.enableGranularSourceSetsMetadata=true
kotlin.mpp.hierarchicalStructureSupport=true

@wakaztahir Isn't HMPP is enabled by default since 1.6.20? https://kotlinlang.org/docs/multiplatform-hierarchy.html

yeah , I thought you might have them false , since I was having issues and found it was false

It seems reproducible with AGP 7.2.2, but isn't reproducible with AGP 7.3.0 or AGP 7.1.3.
AGP 7.3.0 is supported by IDEA 2022.3 EAP (223.4884.69) and Android Studio Dolphin 2021.3.1

I couldn't use AGP 7.1.3 with Kotlin 1.7.10. For example Android lint fails with error messages like:
> Task :common:database:lintAnalyzeDebug
e: /Users/arkivanov/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-jdk8/1.7.10/d70d7d2c56371f7aa18f32e984e3e2e998fe9081/kotlin-stdlib-jdk8-1.7.10.jar!/META-INF/kotlin-stdlib-jdk8.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
e: /Users/arkivanov/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-jdk7/1.7.10/1ef73fee66f45d52c67e2aca12fd945dbe0659bf/kotlin-stdlib-jdk7-1.7.10.jar!/META-INF/kotlin-stdlib-jdk7.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
e: /Users/arkivanov/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.7.10/d2abf9e77736acc4450dc4a3f707fa2c10f5099d/kotlin-stdlib-1.7.10.jar!/META-INF/kotlin-stdlib.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
e: /Users/arkivanov/dev/workspace/compose-jb/examples/todoapp/common/database/build/.transforms/1c2bbefbddd565671d87bbbe54277e4b/transformed/out/jars/classes.jar!/META-INF/database_debug.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
e: /Users/arkivanov/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-test-junit/1.7.10/27228b08adb999a47ae98ac03e98e1f3132f83ca/kotlin-test-junit-1.7.10.jar!/META-INF/kotlin-test-junit.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
e: /Users/arkivanov/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-test/1.7.10/4d644a88cc0a386712d4b1c1b4ca748203421e07/kotlin-test-1.7.10.jar!/META-INF/kotlin-test.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
e: /Users/arkivanov/dev/workspace/compose-jb/examples/todoapp/common/database/build/tmp/kotlin-classes/debug/META-INF/database_debug.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.

Meantime, there seems to be a workaround with AGP 7.2.2. Just add Jetpack Compose original dependencies in pure Android modules and androidMain KMP source sets.
implementation("androidx.compose.foundation:foundation:1.2.1")
implementation("androidx.compose.material:material:1.2.1")

Update : I have started experiencing this bug

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


v2.2.0 is not available on Maven Central

https://mvnrepository.com/artifact/com.apple.itunes.storekit/app-store-server-library
The latest version is 2.1.0

@ndson040496 Sorry I didn't notice the job for publishing failed, it should be available in a few minutes on Maven Central

Thank you, v2.2.0 is working now.

A little odd though, the mvn website still doesn't show 2.2.0, but I can import this version


Save Sessions: fail to check suffix/extension.

To reproduce:

Open VAPOR, load Katrina.
Create a renderer, enable it.
Click FIle->Save Session. Type "mysess" in the saved filename.
"mysess" is accepted, and a session file named "mysess" is saved to disk.

Platform: cisl-vapor.

Note: it seems this is a linux specific issue...


Unstable saving of DIBS-reference in comment-field of osCommerce-order

Exactly what reference to the DIBS-transaction is stored in osCommerce will vary.
When "Set order status" is set to "standard", it will only append " transaction=" to the end of the comment-string.
If "Set order status" is set to a specific Order status in osCommerce, it will store "[DIBS Order ID: ]", and the transaction number is not added.
Since the transcation number is unique, while order number can refer to multiple (attempted) transactions, I'd prefer that both are stored in osCommerce.

done in latest release <IP_ADDRESS>


torch2pytorch_data.py problem

When use torchfile to load the panoContext_img_train.t7, the result is empty。

th_path = "D:\program\pytorch-layoutnet\data\origin\data\panoContext_img_train.t7"
imgs = torchfile.load(th_path)
print(imgs.shape)
(0,)

Windows 7 environment

It seems that there is an portability issue for python-torchfile.
The newest commit #272a5a uses pytorch's load_lua instead.
Hope it help you.


When I run LoadTest，the error showed"Dimention 0 in both shapes must be equal,but are 10560 and 89280.shapes are [10560,256] and [89280,256], is there anyone else that have ever met and solved this problem? Really needs help here.

I have also encountered this problem. How can I solve it? Thanks.


fix: create OS agnostic build command/s for rm and mkdir (#395)

Closes #395

Thanks @develper!

Many Thanks to you @mhagmajer and xFAANG for giving me a chance, towards my first contribution :).


[bug]: Critical Mobile Bug

Describe the bug
https://github.com/user-attachments/assets/026e8e19-6e20-42cc-9fda-b991ea536a24
Affected component/components
MultiSelect
How to reproduce

Mobile when scrolling down then typing...

Codesandbox/StackBlitz link
No response
Logs
No response
System Info
Mobile

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

fixed.


[API] I2C repeated start

I was trying to implement a I2C Repeated start for a sensor, is there a way around it or is it a feature.
http://www.i2c-bus.org/repeated-start-condition/

I looked at the i2c-dev that is being used, I don't think i2c-dev supports mixed transactions. We will have to use an i2c_msg struct to support repeated start, does it make sense? or is there a software I2C (bit banging) that would be easier to implement/ port.

Hi, I have a temporary fix here https://github.com/sajingeo/i2crw and I have verified it works :) we still need to integrate it to MRAA.

Thanks that's really helpful, question is do we want to support just a simple Rx/Tx buf combination or do we want to be more flexible and let users construct their own i2c_msg? The first should be fairly easy, the second is much more complicated (especially when it comes to exposing this via SWIG).

Hi @sajingeo @arfoll ,
Thanks for your efforts !
Unfortunately I cannot understand  most of  the technical part of your discussion but if I may express the opinion of an end user, It is really needed to be able to use I2c sensors that require repeated start on an Edison breakout.
It is very frustrating  to be unable to plug more than one sensor on the I2c bus ! From my experience only one sensor out of 3 standard ones (listed in upm lib) that I bought did not request repeated start which means that I cannot get the advantages of having an I2c bus. Of course I should have read more and  I may change the sensors but that increases the cost and does not eliminate frustration... ;-(
I can help testing solutions but I do not know how to implement @sajingeo  temporary fix. I am using the up-to-date git source of mraa and upm, I can make amendments in the code,compile and test it.
Let me know if I can do anything to help.
I am using python

Hi @arfoll and maybe @jontrulson
It seems that this "repeated start condition" is causing more and more trouble #547 #530(?). I am not able to propose a PR on this topic, I have found a workaround proposed by @tdicola for raspberries that works in some cases for me :
echo -n 1 > /sys/module/i2c_bcm2708/parameters/combined
Is there such a workaround for Edisons ?
This condition is not needed for all sensors  and i have understood that it was complicated to implement it as a generic feature, Would-it be possible to get a function that could be called before the creation of the sensor with the upm init function. I am a python user and I would love to be able to write something like  :
mraa.request_repeated_start(bus)
from upm import pyupm_tsl2561 as tsl2561
mytsl = tsl2561.TSL2561(bus1,addrtsl)
Is it possible ? Is it huge work ? Can anybody with skills please contribute ?
Thanks

Hi @g-vidal, just for objectivity's sake - neither of the two issues you've mentioned has to do with repeated start. The "combined" thing doesn't exist on Edison, I think. So all this would need to be implemented from scratch. Can't comment on the amount of work, that would require some further analysis of specific use cases and API we want to expose.

Hi @alext-mkrs From what I have read  here

In Linux kernel I2C read operations with repeated start condition are performed by default for combined (write/read) messages.

Which means that using combined  is a trick to get repeated start by default. It is unfortunate that it does not exist in Edisons ;-(.
We have thrown away (not too far) all our repeated start  devices  but the question remains, are there any plans to add this option in mraa lib.