swarm mode Worker failed do connect on manager

Output of docker version:
Client:
 Version:      1.12.0-rc4
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   e4a0dbc
 Built:
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.0-rc4
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   e4a0dbc
 Built:
 OS/Arch:      linux/amd64

Output of docker info:
manager docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 1.12.0-rc4
Storage Driver: devicemapper
 Pool Name: docker-253:0-394249-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 11.8 MB
 Data Space Total: 107.4 GB
 Data Space Available: 38.62 GB
 Metadata Space Used: 581.6 kB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.147 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2016-06-09)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host null overlay
Swarm: active
 NodeID: 2jsjqw173j8l17ohxjc7p6h4n
 IsManager: Yes
 Managers: 1
 Nodes: 1
 CACertHash: sha256:fb20c03df56aa58f778833d83b40b8b948c60149b75ea6264c177cece047ee54
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-327.22.2.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.797 GiB
Name: manager1
ID: MEJZ:ZHB4:ABD2:DEUI:SCHB:CR6N:IQLK:HUIG:P3LX:LHDY:ASMK:7FYL
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-ip6tables is disabled
Insecure Registries:
 <IP_ADDRESS>/8

worker docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 1.12.0-rc4
Storage Driver: devicemapper
 Pool Name: docker-253:0-394249-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 11.8 MB
 Data Space Total: 107.4 GB
 Data Space Available: 38.52 GB
 Metadata Space Used: 581.6 kB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.147 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2016-06-09)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-327.22.2.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.797 GiB
Name: centos7-docker-1.12rc4
ID: MEJZ:ZHB4:ABD2:DEUI:SCHB:CR6N:IQLK:HUIG:P3LX:LHDY:ASMK:7FYL
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 16
 Goroutines: 32
 System Time: 2016-07-17T12:24:20.315385507-04:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):

Virtualbox-5.0
CEntos-7

Steps to reproduce the issue:

docker swarm init --listen-addr <IP_ADDRESS>:2377 on manager
docker swarm join <IP_ADDRESS>:2377 (or docker swarm join --secret '$2a$10$ObapK4Oz1bUDl83ESn5iIuvP6IdnlJ4VuZix53/Q7VX695WXiy8HK' <IP_ADDRESS>:2377) on worker

Describe the results you received:
Error response from daemon: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: invalid policy or secret

Describe the results you expected:
WORKER join to swarm cluster
Additional information you deem important (e.g. issue happens only occasionally):

Same steps was done with docker-1.12.0~rc3 and everything works ok on manager and workers.

systemctl status docker on worker

  docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
   Active: active (running) since Dom 2016-07-17 11:55:11 EDT; 33min ago
     Docs: https://docs.docker.com
 Main PID: 11590 (dockerd)
   Memory: 36.5M
   CGroup: /system.slice/docker.service
           ├─11590 /usr/bin/dockerd -D -H fd://
           └─11593 docker-containerd -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --shim docker-containerd-shim --metrics-interval=0 --start-timeout 2m --state-...

Jul 17 12:26:38 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:26:38.490613315-04:00" level=debug msg="successfully loaded the Root CA: /var/lib/docker/swar...ot-ca.crt"
Jul 17 12:26:38 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:26:38.490697742-04:00" level=debug msg="loaded local CA certificate: /var/lib/docker/swarm/ce...t-ca.crt."
Jul 17 12:26:38 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:26:38.490757933-04:00" level=debug msg="no valid local TLS credentials found: open /var/lib/d...directory"
Jul 17 12:26:38 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:26:38.683023387-04:00" level=warning msg="error fetching signed node certificate: rpc error: ...or secret"
Jul 17 12:26:38 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:26:38.860911939-04:00" level=warning msg="error fetching signed node certificate: rpc error: ...or secret"
Jul 17 12:26:39 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:26:39.035433694-04:00" level=warning msg="error fetching signed node certificate: rpc error: ...or secret"
Jul 17 12:26:39 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:26:39.218425708-04:00" level=warning msg="error fetching signed node certificate: rpc error: ...or secret"
Jul 17 12:26:39 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:26:39.401706574-04:00" level=warning msg="error fetching signed node certificate: rpc error: ...or secret"
Jul 17 12:26:39 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:26:39.401816678-04:00" level=error msg="cluster exited with error: rpc error: code = 3 desc =...or secret"
Jul 17 12:26:39 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:26:39.401856423-04:00" level=error msg="Handler for POST /v1.24/swarm/join returned error: rp...or secret"
Hint: Some lines were ellipsized, use -l to show in full.

journalctl -f -u docker on worker after trying join

Jul 17 12:29:25 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:29:25.127277688-04:00" level=debug msg="Calling POST /v1.24/swarm/join"
Jul 17 12:29:25 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:29:25.127566159-04:00" level=debug msg="form data: {\"CACertHash\":\"\",\"ListenAddr\":\"<IP_ADDRESS>:2377\",\"Manager\":false,\"RemoteAddrs\":[\"<IP_ADDRESS>:2377\"],\"Secret\":\"*****\"}"
Jul 17 12:29:25 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:29:25.164139797-04:00" level=debug msg="successfully loaded the Root CA: /var/lib/docker/swarm/certificates/swarm-root-ca.crt"
Jul 17 12:29:25 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:29:25.253142182-04:00" level=debug msg="successfully loaded the Root CA: /var/lib/docker/swarm/certificates/swarm-root-ca.crt"
Jul 17 12:29:25 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:29:25.253240690-04:00" level=debug msg="loaded local CA certificate: /var/lib/docker/swarm/certificates/swarm-root-ca.crt."
Jul 17 12:29:25 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:29:25.253321859-04:00" level=debug msg="no valid local TLS credentials found: open /var/lib/docker/swarm/certificates/swarm-node.crt: no such file or directory"
Jul 17 12:29:25 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:29:25.446092986-04:00" level=warning msg="error fetching signed node certificate: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: invalid policy or secret"
Jul 17 12:29:25 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:29:25.620537233-04:00" level=warning msg="error fetching signed node certificate: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: invalid policy or secret"
Jul 17 12:29:25 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:29:25.796807603-04:00" level=warning msg="error fetching signed node certificate: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: invalid policy or secret"
Jul 17 12:29:26 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:29:25.975056928-04:00" level=warning msg="error fetching signed node certificate: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: invalid policy or secret"
Jul 17 12:29:26 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:29:26.152853207-04:00" level=warning msg="error fetching signed node certificate: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: invalid policy or secret"
Jul 17 12:29:26 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:29:26.153206928-04:00" level=error msg="cluster exited with error: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: invalid policy or secret"
Jul 17 12:29:26 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T12:29:26.153337799-04:00" level=error msg="Handler for POST /v1.24/swarm/join returned error: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: invalid policy or secret"

As the error mentions, you must provide a secret token. docker swarm init will output a token for joining as either a manager or as a worker.
If you didn't notice the token, you can retrieve it (for now) via docker swarm inspect.

Do this behavior changed from 1.12.0rc3 to 1.12.0rc4?

on RC3 it isn't necessary to mention.

Is it necessary even with AcceptancePolicy/Policies/Role/worker: "Autoaccept": true?
Although, I also try this:

`docker swarm join --secret '$2a$10$ObapK4Oz1bUDl83ESn5iIuvP6IdnlJ4VuZix53/Q7VX695WXiy8HK'  <IP_ADDRESS>:2377``

Error response from daemon: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: crypto/bcrypt: hashedPassword is not the hash of the given password

journalctl -f -u docker

Jul 17 13:00:34 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T13:00:34.657088670-04:00" level=debug msg="Calling POST /v1.24/swarm/join"
Jul 17 13:00:34 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T13:00:34.657231237-04:00" level=debug msg="form data: {\"CACertHash\":\"\",\"ListenAddr\":\"<IP_ADDRESS>:2377\",\"Manager\":false,\"RemoteAddrs\":[\"<IP_ADDRESS>:2377\"],\"Secret\":\"*****\"}"
Jul 17 13:00:34 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T13:00:34.686065259-04:00" level=debug msg="successfully loaded the Root CA: /var/lib/docker/swarm/certificates/swarm-root-ca.crt"
Jul 17 13:00:34 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T13:00:34.753260992-04:00" level=debug msg="successfully loaded the Root CA: /var/lib/docker/swarm/certificates/swarm-root-ca.crt"
Jul 17 13:00:34 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T13:00:34.753373995-04:00" level=debug msg="loaded local CA certificate: /var/lib/docker/swarm/certificates/swarm-root-ca.crt."
Jul 17 13:00:34 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T13:00:34.753430102-04:00" level=debug msg="no valid local TLS credentials found: open /var/lib/docker/swarm/certificates/swarm-node.crt: no such file or directory"
Jul 17 13:00:35 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T13:00:35.092216033-04:00" level=warning msg="error fetching signed node certificate: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: crypto/bcrypt: hashedPassword is not the hash of the given password"
Jul 17 13:00:35 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T13:00:35.422275183-04:00" level=warning msg="error fetching signed node certificate: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: crypto/bcrypt: hashedPassword is not the hash of the given password"
Jul 17 13:00:35 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T13:00:35.779491252-04:00" level=warning msg="error fetching signed node certificate: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: crypto/bcrypt: hashedPassword is not the hash of the given password"
Jul 17 13:00:36 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T13:00:36.110573017-04:00" level=warning msg="error fetching signed node certificate: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: crypto/bcrypt: hashedPassword is not the hash of the given password"
Jul 17 13:00:36 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T13:00:36.438059213-04:00" level=warning msg="error fetching signed node certificate: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: crypto/bcrypt: hashedPassword is not the hash of the given password"
Jul 17 13:00:36 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T13:00:36.438175234-04:00" level=error msg="cluster exited with error: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: crypto/bcrypt: hashedPassword is not the hash of the given password"
Jul 17 13:00:36 centos7-docker-1.12rc4 dockerd[11590]: time="2016-07-17T13:00:36.438213892-04:00" level=error msg="Handler for POST /v1.24/swarm/join returned error: rpc error: code = 3 desc = A valid secret token is necessary to join this cluster: crypto/bcrypt: hashedPassword is not the hash of the given password"

@adrianovieira Yes, this was added in RC4, still some more work being done on it.

As I mention above, the issue happens even when I provided the -- secret parameter.
Then may be the issue needs to be reopened, isn't it?

The error is different and would seem to indicate that you put in the wrong secret.

I opened a related issue #24737

Please explain. The error says the secret that's stored does not match the secret you provided. Did you try creating a new cluster?

Yes!
I created a new cluster with --secret <key> and everything goes ok.
Thanks for all.

Note that if you don't provide a secret, it will generate 2 for you, one for workers and one for managers.

Forgive the intrusion! Is it possible that the secret join token is not yet accommodated by swarmkit? It seems if I follow the swarmkit quickstart instructions, swarmd fails with "A valid join token is necessary" error, while creating a second node with:
bin/swarmd -d /tmp/node-2 --hostname node-2 --join-addr <IP_ADDRESS>:4242 --join-token=6j3cxnz6n3pvlsbm2z5pfb00t
The value I passed in for the join-token was the ID field returned from running:
bin/swarmctl node inspect node-1 -s /tmp/manager1/swarm.sock
...on the master node. Perhaps I'm using the wrong field?

The node ID is the not the same as the join token. If you use swarmctl cluster inspect default, you will find the join tokens.
Please discuss swarmd/swarmctl issues and questions in the swarmkit repository.

Thanks Aaron. That got me to the next step.


QRNG docs assume an EOA sponsor, while qrng-example has the requester sponsor itself

See https://discord.com/channels/758003776174030948/765618225144266793/994593770509189131
In the context of qrng-example, sponsor and requester addresses are the same for simplicity. The docs have the user generate a sponsor mnemonic, which is not needed. This may be why QRNG users have been confused about the sponsorship scheme. The docs need to be updated to match qrng-example. Alternatively, strip the docs down and rely on qrng-example more heavily.

This has resulted in major changes to the QRNG docs. See the preview site.

New sub-sections added to the sidebar.
The QRNG sample project is now a first-class-citizen in the sidebar under "Guides".
A new "Remix Example" page added to the guides section.
Added the Youtube video to the guides section.
Added a new sidebar section "Reference".
Added both the QrngExample.sol and RemixQrngExample.sol contracts to the reference section.

@bbenligiray @Ashar2shahid @dcroote @kolenic-martin
Some comments on the Remix Example would be useful. Do we keep it, change anything in it? I was thinking of doing another Remix example for dAPIs as I had heard in a meeting it might be nice to have an integration example for dAPI calls.

@kolenic-martin This PR introduces a restructuring of the QRNG docs. The only new "thing" is the Remix Example. I have tested it and think it works well but a second set of eyes is always useful. Let me know if you need and guidance. It uses a combinations of the Remix IDE and CLI.


fix: west-bengal-district-name

Description of PR
Type of PR

[x] Bugfix

Relevant Issues
Fixes #452
Checklist

[x] Compiles and passes lint tests
[x] Properly formatted
[x] Tested on desktop
[x] Tested on phone

Screenshots

This can be merged to fix this district's name issue, but the West Bengal json is old. #413 will resolve this automatically

Resolved with #521


Add standardjs to dev deps

I understand an app's dependencies being anything the app needs to actually run. Anything in devDependencies is needed only to develop the app. The advantages of having this distinction vary according to what your build process looks like (if you use webpack, for instance). An advantage is that anyone not interested in developing the app could run it with npm install --production, which omits all the modules in devDependencies.
People have different opinions about this. A couple of links:
https://stackoverflow.com/questions/18875674/whats-the-difference-between-dependencies-devdependencies-and-peerdependencies
https://github.com/webpack/webpack/issues/520

@simoneduca thanks for this! For clarity, would you mind updating the PR description for why this is a good thing to do?

@edwardhorsford Done, hope it helps. Also, sorry about the tests failing. Having a look.

That's odd. It looks like Travis is failing because standardjs is picking up some errors which were there before my PR 🤔

it's probably because you've updated the version of Standard at the same time :)

@joelanman ah, that's it. Didn't notice that, thanks.

It might be worth pinning dependencies to specific versions, rather than ranges. That should help avoid this sort of scenario, plus you know exactly what versions you're working with

@simoneduca really sorry for the long delay on this, would it be possible to rebase this? Let me know if you need help doing this. We may also need to look again if any other dependencies should also move to devDependencies

@joelanman no worries. Let me know if I missed anything 😃

@simoneduca hey, it looks like there's a few files that are changed that maybe was not intentional: https://github.com/alphagov/govuk-prototype-kit/pull/503/files
We'd also want to squash the commits so we don't have 'rebase branch'.
I can do both of these things on your behalf if you wish, since they're just cleanup.
Let me know

@nickcolley ah sorry about that. Yes please!

Can you please enable 'Allow edits from maintainers' to allow us to push changes to your fork?
Thanks!

@36degrees it's already enabled 🤔

Apologies Simon – I assumed it wouldn't be by default, but hadn't actually tried it. I've updated this PR with a single commit, which simply moves the standard dependency from dependencies to devDependencies.

wondering if supertest would also be a devDependency

@joelanman closing this in favour of #619 where i have also moved supertest to dev depencies
ready for second approval


[$500] Web - Empty spaces before line break are not removed

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open any report
Type some text in composer, add empty spaces& create a line break
Type some text on new line
Send the message
Observe the empty spaces in the first line by copying the text by selection or editing the message and removing the line break

Expected Result:
Empty spaces before line break should be removed
Actual Result:
Empty spaces before line break are not removed
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/4532c171-012c-4fad-b859-aea5485bc86b
https://github.com/Expensify/App/assets/93399543/a187de6e-95f1-4945-9301-8d6bf2253448
Expensify/Expensify Issue URL:
Issue reported by: @Krishna2323
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694220412655639
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0165a04bcce244ada9
Upwork Job ID:<PHONE_NUMBER>673042432
Last Price Increase: 2023-09-12

@flaviadefaria Looks like I was incorrectly double assigned here by the external label. We are discussing fixing this here. In the meantime, going to un-assign as this doesn't need two BZ assignees.

PROPOSAL
Please re-state the problem that we are trying to solve in this issue.
Web - Empty spaces before line break are not removed
What is the root cause of that problem?
src/pages/home/report/ReportActionCompose/ComposerWithSuggestions.js
Line 237 in 2163c54

trim() method in JavaScript is designed to remove leading and trailing whitespace characters, such as spaces and tabs, but it does not remove whitespace characters within the middle of a string or before line breaks (newlines).

https://github.com/Expensify/App/blob/2163c549de291cfdf305ade59015fda1dd34fc3f/src/pages/home/report/ReportActionCompose/ComposerWithSuggestions.js#L237

And this issue I have already implemented in my chat app

socket.emit("sendMessage", {
    content: message?.replace(/\s+\n/g, "\n").trim(),
    chatID: selectedChat?._id,
});

What changes do you think we should make in order to solve the problem?

Replace line 237 with following line:

const trimmedComment = commentRef.current.replace(/\s+\n/g, '\n').trim();

PROPOSAL
Please re-state the problem that we are trying to solve in this issue.
Web - Empty spaces before line break are not removed
What is the root cause of that problem?
src/pages/home/report/ReportActionCompose/ComposerWithSuggestions.js Line 237 in 2163c54

trim() method in JavaScript is designed to remove leading and trailing whitespace characters, such as spaces and tabs, but it does not remove whitespace characters within the middle of a string or before line breaks (newlines).

https://github.com/Expensify/App/blob/2163c549de291cfdf305ade59015fda1dd34fc3f/src/pages/home/report/ReportActionCompose/ComposerWithSuggestions.js#L237

And this issue I have already implemented in my chat app

socket.emit("sendMessage", {
    content: message?.replace(/\s+\n/g, "\n").trim(),
    chatID: selectedChat?._id,
});

What changes do you think we should make in order to solve the problem?

Replace line 237 with following line:

const trimmedComment = commentRef.current.replace(/\s+\n/g, '\n').trim();

Contributer Details
Expensify account email:-<EMAIL_ADDRESS>Upword Profile Link:- https://www.upwork.com/freelancers/~01e92101ac60dd2cf0

Proposal
Please re-state the problem that we are tryng to solve in this issue.
Spaces before line break are not removed
What is the root cause of that problem?
Markdown parser's newline rule is not covering the case.
What changes do you think we should make in order to solve the problem?
We need to add a tweak([ ]*) on newline rule's regex https://github.com/Expensify/expensify-common/blob/main/lib/ExpensiMark.js#L218
after fix, will be as following:
            {
                name: 'newline',
                regex: /[ ]*\r?\n/g,
                replacement: '
',
            },

Along with the amendment on newline rule, we need to fix some original auto test cases to remove spaces before linebreak(
)

@stephanieelliott  I'm going OoO for a week so assigning this to you so that you can move it forward in the meantime. I'll take it back from you once I'm online again.


Add sql tag clickable

Yeah, I agree with you, it would be super convenient.

I found this issue when I was searching for the SQL tag... (which is clickable now, BTW). Can you advise about the intended behavior though?

Is this SQL tag only supposed to appear for map layers with Analysis applied?
(I know that the SQL tag also appears when importing .carto files from other accounts, but that is another issue).
I was expecting that if I apply a SQL query from the DATA tab of a selected layer, this SQL tag would appear in the LAYERS pane.

If you run an UPDATE or INSERT statement in the SQL view, the SQL code disappears after being applied, and no SQL tag is displayed from the LAYERS pane.  (Note: Clicking the undo button from the SQL view displays the applied statement though)
If you run a SELECT query, the statement remains in the the SQL view and the SQL tag appears in the LAYERS pane.

tagging @noguerol for transparency (since I was bugging him about this ;-)

SQL tag appears on SELECT because is a non destructive query, while UPDATE and INSERT are directly applied to the table.

Okay, thanks for confirming the expected behavior.
@xavijam , did you want to close this issue? (Since the SQL tag is clickable)

Yep, lets close it.


MC Genealogy Information

At the moment we store information on:

the particle that creates the tracker (demc branch);
the PrimaryParticle that was created in this event, which can be the same particle as the above (demcpri branch); and,
the GenParticle that was generated in this event, which can be the same as th above (demcgen branch).

In issue #9, the demcgen branch will be deleted since the GenParticle is now always a proton-on-target and not of particular use. We should also revisit what other information we want to store. We could, for example, store information on the parent and grandparent of the particle that creates the track.
Another thing we might want to revisit is what inforamtion we store. At the moment, the demcpri branch only stores the initial information but maybe we also want to store the end information of the particle too? We might also want to store the beginning / end of the parents and grandparents too (although then we would be duplicating information).

I've been thinking about this and here is a proposed new branch structure:

demc will stay as it is
demcparent will contain the information of the parent SimParticle
demcgparent will contain the information of the grandparent SimParticles

In mixing for MDC2020, we are only guaranteed to have information up to the grandparent level. I will try to write the oode so that it is easier to extend to higher generations, just incase that is a use case we want to support in the future.
I think the new branches will use the GenInfo struct. However, I will rename this to SimInfo since we no longer want the demcgen branch (issue #9) and renaming to SimInfo makes it more obvious we are storing information about SimParticles.
One thing I'm unsure of is whether we also want to keep the demcpri branch. @brownd1978 do you know what the PrimaryParticle will contain in MDC2020?

Hi Andy,
PrimaryParticle is already updated for MDC2020, it is just Ptr(s) to the
primary SimParticle(s).  Your plan sounds good.
Note that we may decide to truncate background frame genealogy above
grandparent, so TrkAna should handle that gracefully (if the creation is
'truncated').  This will be discussed in the comp-soft
meeting tomorrow in case you want to weigh in.
On Tue, Aug 10, 2021 at 4:25 PM Andrew Edmonds @.***>
wrote:

I've been thinking about this and here is a proposed new branch structure:

demc will stay as it is
demcparent will contain the information of the parent SimParticle
demcgparent will contain the information of the grandparent
SimParticles

In mixing for MDC2020, we are only guaranteed to have information up to
the grandparent level. I will try to write the oode so that it is easier to
extend to higher generations, just incase that is a use case we want to
support in the future.
I think the new branches will use the GenInfo struct. However, I will
rename this to SimInfo since we no longer want the demcgen branch (issue
#9 https://github.com/Mu2e/TrkAna/issues/9) and renaming to SimInfo
makes it more obvious we are storing information about SimParticles.
One thing I'm unsure of is whether we also want to keep the demcpri
branch. @brownd1978 https://github.com/brownd1978 do you know what the
PrimaryParticle will contain in MDC2020?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Mu2e/TrkAna/issues/25#issuecomment-896377206, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAH57YTUOW3WKDXGVZ27V3T4GYN3ANCNFSM5BFH6XKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

--
David Nathan Brown            @.***
Office Phone<PHONE_NUMBER>  Fax  495-2957
Lawrence Berkeley National Lab
MS 50R5008 (50-6026C)  Berkeley, CA 94720

This has been done in PR #28


HHH-17300 detect and throw exception for @Table annotation on @MappedSuperclass

https://hibernate.atlassian.net/browse/HHH-17300

The failures don't appear to be related to my change.


why do you use Cassandra

Hi, I am reading your project and I love this project
I have a question, why do you choose Cassandra in your project instead of other NoSQL like Redis, MongoDB , are there any special features that others dont have it. Can you share me it. I am wondering when I should choose Cassandra instead of your project instead of other NoSQL like Redis, MongoDB

Cassandra is a highly scalable, NoSQL database that is widely used for storing and managing large amounts of data. It is known for its ability to handle high write and read loads, making it well-suited for chat applications. For example, Discord uses Cassandra to store 100+ billion messages a day: https://discord.com/blog/how-discord-stores-billions-of-messages.


Misleading document for os::file_exists/1

The document of os::file_exists/1 says that:

True if the specified file exists (irrespective of type and file permissions).

The word "type" is not quite clear, for first impression, I thought it means "file or directory", which is not true.

Fixed in dd1bf8e13d1c090608467b44032c4f96eb793f43. Thanks for reporting.


Thx for your job. I wonder what's suitable to train model, specially in what type of gpu and how big of gpu memory. I trained a few times in quadro 6000 but the log said sigkill problem in second epoch.

My GPU quadro 6000 24g main cpu memory 64g

I mean, the first epoch seems work well, but in the second epoch and during the mid time of the seonc batch like 4660/5033, my thread will be killed and the pycharm tips are like:"interrupted by signal 9: sigkill" I check my log in linux and it said cpu out of memory, But my main memory of linux is 64g, I think it might be enough. I don't know what causes this kind of error.

I think that the CPU memory is too small because we have to load many reports.
Have you tried loading a small portation of reports for each claim?

Thanks a lot for your generous help. I will star this project.
But I mean it's not the storage capacity 199g, it's main memory capacity 64g. So I revised the eval_exp_fc5 from report each claim=12->report_each_claim=6, and change the report _each_claim from 30 to 15 in  train_exp_fc5_liar_raw2. But it seems still throw kill sig problem. But the difference is before I change the parameter, it would crash during training time but after I revised it, it would crash during evaluation time. But I just had changed the parameter of report_each_claim in evaluate_model func from eval_exp_fc5. So could you help me to figure it out?

Or in other words， how big of the required memory is?

Hi, @nievuelo . I can not figure it out with limited information, but you can try this code on the other machine with GPU 3090 because we have successfully tested it.


Ensure the package contains the right information in it

[ ] Release notes: we need to update the PackageReleaseNotes node in the Azure.Core package to contain the release notes.
[ ] Link to the readme file
[ ] Icon as needed

This didn't happen for Preview2. I am going to move it to Vnext so we don't forget to do it for future releases


Add 2024-03-01 API to storageCache

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.StorageCache

@archerzz @tg-msft @KrzysztofCwalina Could someone approve this PR? All checks are successful.


ssr-manifest generated for solid-start-static

I am using solid-start-static as such to build a SSG:
export default defineConfig({
  plugins: [solid({
    solid: { hydratable: true },
    adapter: 'solid-start-static',
  })],
  build: {
    ssrManifest: false,
  }
});

However, solid-start seems to be hard-coding the ssrManifest resulting in ssr-manifest.json being generated when it's not needed.
Code Reference: solid-start-static

Isn't it used internally to grab the list of items that need to be server-generated? Even so, it should be removed afterwards, if that is the case.

In setting up for SolidStarts next Beta Phase built on Nitro and Vinxi we are closing all PRs/Issues that will not be merged due to the system changing. If you feel your issue was closed by mistake. Feel free to re-open it after updating/testing against 0.4.x release. Thank you for your patience.

See https://github.com/solidjs/solid-start/pull/1139 for more details.


Hello World example leverages secret APIs

http://expressjs.com/en/starter/hello-world.html
var server = app.listen(3000, function () {
  var host = server.address().address;
  var port = server.address().port;

  console.log('Example app listening at http://%s:%s', host, port);
});

docs say nothing about a return value for app.listen, although the code docs do.
In any event that usage is definitely not good for a hello-world example.

tried to fork & run site but it's jekyll which I've never been able to run successfully.

Hi @Sequoia , that's a good point on our documentation. We do write that

This method is identical to Node’s http.Server.listen().

and so the return value from our method is whatever Node.js returns. It looks like they don't document the return value, either. Besides it getting fixed here, getting their documentation to also mention the return value would also be valuable to the entire Node.js community :)

I agree that we should be more explicit, and I'll pursue clarifying the Node docs as well.
To be fair, the last sentence in the doc does show (in code) the value that it returns:

The app.listen() method is a convenience method for the following (for HTTP only):

app.listen = function() {
  var server = http.createServer(this);
  return server.listen.apply(server, arguments);
};

But I think we should clarify.  So, should we just state that app.listen returns an http.Server object?

So, should we just state that app.listen returns an http.Server object?

SGTM

Do you agree? Should we change our Hello World example?

Perhaps. So I think the idea was to get the print statement to show the address and port being listened to. We could eliminate server variable and change the references inside the function to this, but that may also be confusing.
The other option is to just change it to the following:
var express = require('express');
var app = express();

app.get('/', function (req, res) {
  res.send('Hello World!');
});

app.listen(3000, function () {
  console.log('Example app listening on port 3000!');
});

:+1: @dougwilson's revised version. IMO "hello world" should show the absolute minimum to get an app running, in order to avoid confusion. If server = is there, there's a strong chance readers will assume this is "necessary code" to start an express instance. In the case of server = app.listen(..., in my limited experience this is not "idiomatic" express code-- I don't tend to see this direct reference the HTTP.Server object.
@crandmck That code only shows that app.listen returns whatever server.listen returns, which is likewise not documented! :smile_cat: But I see what you mean.

OK I updated the API doc as noted above: caf6ada728cf9813969a6fff4f817fd4ec88311f
+1 on @dougwilson's suggestion above.  I believe @hacksparrow said he'll change Getting Started.
I also opened an issue to update the Node docs accordingly as well.

Updated the example for all languages, according to Doug's suggestion.

Thanks @hacksparrow !

Epilogue: @crandmck submitted issue against nodejs/node, patch should land soon. Thanks for the speedy response yall! 👽


Q: why it is callled riot

Just out of sheer curiosity, why the search engine is called "riot"?

Just a joke. And there is a lack of contributors and maintainers. But there are a lot of Internet troll, keyboard warrior and free rider.

Interesting, :)


Add option to specify for roslyn server the razor output directory path

Adds devKitRazorOutputPath option
Allows RazorSourceGenerator to be picked up by tooling rather than SDK
Fixes WorkItem 1926900 (https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1926900)

/cc @CyrusNajmabadi @davidwengier @dibarbet
Related to https://github.com/dotnet/roslyn/pull/72482

Applied PR feedback. Tested changes again for VS code and confirmed the problem goes away when project is targeting 6.0 and using 6.0 SDK.
Before change:

After change:

The roslyn server version in vscode-csharp is not updated to a version that contains the server side change yet causing the failure on the CI.
[stderr] Unrecognized command or argument '--razorSourceGenerator'.
Unrecognized command or argument '/mnt/vss/_work/1/s/.razor/Microsoft.CodeAnalysis.Razor.Compiler.dll'.

Thanks @dibarbet for clarifying this

/azp run


URGENT add Ohni back

URGENT add Ohni back

Merged in main list
This will be merged in the local list today. #1673


Fix ECS Fargate processes not being associated with containers

What does this PR do?
Fixes a bug where sometimes the process data generated for an ECS Fargate container is missing the container tags
Motivation
https://datadoghq.atlassian.net/browse/CONS-6242
Additional Notes
It appears that the problem was due to regex parsing, while debugging I found instances where the fargate container ID was {32}-{9}, but we were explicitly only looking at {32}-{10}. I cannot find any information on the definition of the fargate container ID format, so while this addresses the situation we came across in the support ticket, I do not know if there are other cases we have not run into yet.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
I was able to reliably replicate this issue using the python container using the following task container definition:
        {
            "name": "api",
            "image": "public.ecr.aws/docker/library/python",
            "essential": false,
            "command": [
                "python",
                "-m",
                "http.server",
                "8080"
            ]
        }

Add this container definition as another container here, after the redis container definition, and deploy to an ECS fargate cluster
Verify that the container shows up on the live containers page, and that the process data shows up attached to this container, like so:

Also, to make sure the original bug that we ran into was being hit, log into the AWS console and navigate to the tasks page for you cluster, find the task that contains the python container, and validate that the container runtime ID matches the format that caused the issue in the first place:

The above container reliably triggered the issue, across multiple clusters. However, if it does not result in a container ID that is one character short, then it is worth noting that the QA for this has already been done in a cluster where we were able to reproduce the issue, and has been validated

/merge


topology validator not splitting classpath

I have been experiencing severe errors during the classpath checking step of the topology validation:
WLSDPLY-05024: Attribute ClassPath in model location topology:/Server/myserver_batch1/ServerStart/SERVER_START-0 references entry wlsdeploy/classpathLibraries/javax.persistence_<IP_ADDRESS>_2-0(1).jar:wlsdeploy/classpathLibraries/com.oracle.jpa2support_<IP_ADDRESS>_21(1).jar:wlsdeploy/classpathLibraries/weblogic_patch(1).jar:wlsdeploy/classpathLibraries/weblogic(2).jar that is not found in the archive file /home/bea/bacstelip_discovered.zip
It seems that the classpath is not being split (on colons in our case), so the full string, separators included, is being searched for as a path in the archive.
We're currently using a workaround by changing the ifs in the original source to the elifs and adding a conditional to check for colons. This works for us, but is obviously specific to our case and wouldn't work as a general fix.
    # lib/python/wlsdeploy/tool/validate/validator.py
    881         valid_valus_data_types = ['list', 'string']
    882         if value_data_type not in valid_valus_data_types:
    883             validation_result.add_error('WLSDPLY-05023', attribute_name, model_folder_path, value_data_type)
    884         else:
    885             attr_values = []
    886
    887             if value_data_type == 'string' and ":" in attribute_value:
    888                 attr_values = attribute_value.split(":")
    889
    890             elif value_data_type == 'string' and model_constants.MODEL_LIST_DELIMITER in attribute_value:
    891                 attr_values = attribute_value.split(model_constants.MODEL_LIST_DELIMITER)
    892
    893             elif value_data_type == 'string':
    894                 attr_values.append(attribute_value)
    895
    896             for item_path in attr_values:
    897                 validation_result = self.__validate_single_path_in_archive(item_path.strip(), attribute_name,
    898                                                                            model_folder_path, validation_result)```

The Server/ServerStart/Classpath attribute is a list type, so it can be represented in the model in two ways, as a comma-delimited string, or as a list. Your entry in the model should look like:
ServerStart: 'wlsdeploy/classpathLibraries/javax.persistence_<IP_ADDRESS>_2-0(1).jar, wlsdeploy/classpathLibraries/com.oracle.jpa2support_<IP_ADDRESS>_21(1).jar, wlsdeploy/classpathLibraries/weblogic_patch(1).jar, wlsdeploy/classpathLibraries/weblogic(2).jar'
or:
ServerStart: [
'wlsdeploy/classpathLibraries/javax.persistence_<IP_ADDRESS>_2-0(1).jar',
'wlsdeploy/classpathLibraries/com.oracle.jpa2support_<IP_ADDRESS>_21(1).jar',
'wlsdeploy/classpathLibraries/weblogic_patch(1).jar',
'wlsdeploy/classpathLibraries/weblogic(2).jar'
]
The tools will use the correct delimiter when setting the value in WLST.  If any list member contains a comma, a list must be used in the model.
There is a more detailed discussion of list values here.
Hope this helps.

Thanks Richard, but our problem is during domain discovery, we are not creating our own model file at this point.

OK, I'm able to reproduce it in discover.


Protect main and 4.1 branches

Expected behavior
Fools like myself shouldn't be able to commit directly on the main and 4.1 branches by mistake, or worse push force. They should be required to open a PR with at least one reviewer to get it merged.
If necessary, core maintainers could be exempted from these rules.
All these protection rules are available in GitHub.
Actual behavior
I inadvertently push into 4.1 and was able to remove my commit. Sorry about this.
I definitely shouldn't be able to do that.

cc @normanmaurer

Good point... let me do this :)


Debugging of tests  is not working when ANDROID_TEST_ORCHESTRATOR is enabled.

When ANDROID_TEST_ORCHESTRATOR is enabled . debugging of tests is not working .
apart from that whenever failed tests leads to process crash an error message is shown saying that
"Test instrumentation process crashed. Check test.txt for details" but i had never seen that txt file is  generated.

According to the documentation, if you are using ANDROID_TEST_ORCHESTRATOR then you cannot debug your tests, you need to disable the orchestrator (by commenting the code) in your app's build.gradle
Otherwise, if you want to see the generated file, from the emulator you can go to /data/user_de/0/android.support.test.orchestrator/files/ and then look for the particular file


Trying to build MNIST model and batch jobs without train job in SageMaker via Kubeflow Pipeline

@dalbhanj @brentley
I am trying to create MNIST model , Prediction and Batch Transform in SageMaker without training jobs in SageMaker.
I have removed the HPO and training part from the script and run only the MNIST model , Prediction and Batch Transform part but Code automatically re redeploying HPO and training part also which I dont want in SageMaker.
Thanks in advance 👍

Hi @swarnaditya, let me see if I understand your use case. Are you trying to run all steps of Mnist pipeline in Kubernetes? Can you review the sample provided here: https://github.com/aws-samples/eks-kubeflow-workshop/blob/master/notebooks/05_Kubeflow_Pipeline/05_03_Pipeline_mnist.ipynb
This notebook will run all the steps of pipeline on EKS and Not on Sagemaker. If you need to offload some of the steps to Sagemaker, you can review 05_04_Pipeline_SageMaker.ipynb example and replicate that in your use case. For ex, run training and model creation job on EKS and expose inference endpoint on Sagemaker

@dalbhanj
We are trying to create a MNIST model on AWS Sagemaker (SM) using kubeflow component
The main goal is like building a hybrid pipeline kind of workflow (some part like inference on Kubeflow and creation of the model and do the batch Transfromation jobs on AWS Sagemaker.
Anyway I will try your steps as you mentioned.


[HUDI-8275] DO NOT MERGE 2

Change Logs
asfdsafs
Impact
sdafdsfs
Risk level (write none, low medium or high below)
none
Documentation Update
N/A
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Closing this testing-only PR.


Add intermix to bower repo

Intermix should be available from bower as well. Milestone 0.1 should be added first.

Done. All git tags available


Screen slides up to focused input when the input is out of the window

Steps to Reproduce

Open the snack on your iPhone
Input some texts to the first textinput
Do NOT dismiss the keyboard and scroll down to bottom
Tap "Tap me"

Actual: Screen slides up to the first input
Expected: The button is pressed and onPress is triggered
Snack
https://snack.expo.dev/@zhen-zhu/keyboard-and-input

Same issue here  🙃

It is RN ScrollView issue itself:
https://github.com/facebook/react-native/issues/30736


Apply prettier to all directories

I would like to propose adding other folders (such as samples and test folders) to format script
Something like this
{
  "format:code": "prettier --write \"**/*.{js,ts}\""
}

It is great idea, however we have to be sure do not format node_modules and dist.
I've also created issue #64, where prettier will be replaced by eslint.


Getting title text from CodeMirror.title

It's kind of difficult to take the value. Remove from the 1.2 milestone.

Remove from Issues. After CodeMirror supporting feature to get title from Doc object, this issue can be reopened.


Added Kurtcopter section

i forgot to add a line between ## Kurtcopter and the text after it i am shaking and crying right now

you should add that line and commit it, then i'll merge it :)

The line has been added.

LGTM


Add state alicloud.tablestore

Description
A state component which implemented by Alibaba Cloud TableStore.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: https://github.com/dapr/components-contrib/issues/914
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: https://github.com/dapr/docs/issues/1535

@theonefx Can you fix the linter issues in this PR? See inline in the "Files changed" tab.
@artursouza & @daixiang0 FYI, since you reviewed a previous version of this PR before.

@CodeMonkeyLeet no problem

@CodeMonkeyLeet Done

lgtm
/cc @artursouza  @pkedy


[FEATURE REQUEST] add google translator in home page

Description
Is your feature request related to a problem? Please describe.
I want to add google translator in home page
Describe the solution you'd like
A google translate element will be added in navbar.
Additional Information
Priority (optional)
Please indicate the priority level of this feature request (e.g., High, Medium, Low).
High
Additional Notes (optional)
Add any other notes or comments about the feature request here.
PLease assign this issue to me

it distorts the other elemnts so its not needed currently


Question about the order of the code here

https://github.com/mittalgovind/fifty/blob/9aaf00a38ae9b98be8b89ccff8a87082e04054cc/fifty/commands/whatis.py#L181
Is the remapping of the distribution of probabilities to the top 4 types here a bug?
            top_labels = df['Class Label'].value_counts()[:4]
            top_labels *= 100 / top_labels.sum()

That is to say, is this code supposed to be like this:
            top_labels = df['Class Label'].value_counts()
            top_labels *= 100 / top_labels.sum()
            top_labels = top_labels[:4]

Or is this intentional?

@ahmed-masud Thank you for noticing it. I have fixed it.


update(cassandra): add ZDM_ORIGIN_ENABLE_HOST_ASSIGNMENT=false

https://aiven.atlassian.net/browse/DOC-915
Checklist

[x] The first paragraph of the page is on one line.
[x] The other lines have a line break at 90 characters.
[x] I checked the output.
[x] I applied the style guide.
[x] My links start with /docs/.

This doc needs to be updated, it is still using ZDM_SOURCE_* for all the env variables, I assume naming has changed in newer versions, see:
https://github.com/datastax/zdm-proxy?tab=readme-ov-file#quick-start
the ZDM_ORIGIN_ENABLE_HOST_ASSIGNMENT=false. is already mentioned on this doc but it is under the old naming: ZDM_SOURCE_ENABLE_HOST_ASSIGNMENT=false
let me know if you need help to make the other changes or if you want me to take this PR from here.

@wojcik-dorota please review the changes I have pushed.


More Info URL for unneeded configuration options is out of date

Library Affected:
workbox-webpack-plugin
Browser & Platform:
N/A
Issue or Feature Request Description:
This URL does not resolve:
https://github.com/GoogleChrome/workbox/blob/master/packages/workbox-webpack-plugin/src/lib/warn-about-config.js#L18
And the commit / PR that added it has no indication of where it should link. When a user gets this warning they have no way to know where to get more info.

Never mind, strange network issue on our end.


Transport to close channel if read detects closure

Motivation:
Protocols powered by the ByteStream transport classes (TCP, UDS) do not have independent state for input/output shutdown. If we read the transport is shut down then future writes are not expected to succeed, but today we leave the channel in an unusable state and expect the next write to detect the failure and trigger a close.
Modifications:

Instead of waiting for the write to detect the channel is closed the transport should just close the channel when it detects it is closed.

build failure attributed to https://github.com/netty/netty/issues/11542

discussed with @chrisvest offline and agreed that sending FIN can be interpreted as "I'm done writing, but will still read" and if we pull in this PR Netty won't be able to do this.


[WIP] compose: Render stream icons according to stream type(public/private).

Probably unsafe due to use of .html method(I'm not sure).
My question is, is this the right(and safe) way to proceed? Is there some other method which I can use to display the html for icon?

issue #19058
I am able to achieve this:

BTW I'm aware of the fact that tests are failing, I haven't made any changes to the tests, as for now.

@aryanshridhar is there any other security issue? or can I proceed with this?

@raghupalash did you intend to close this?
In any case, you indeed need to escape the HTML.  Usually the way to do this is to create two spams; one that is has the user input and is set via .text, and other is set via .html.  The other good option is to make an HTML template and pass multiple parameters into it.

I closed this because It wasn't going anywhere as I was busy with my exams and I was not really sure if I did it right, but since now I'm free, I think I'm gonna look at this again.

I'm trying to work on updating the rendered_markdown.js tests. There I can see a stream that is used to do the stream mention test-
const stream = {
    subscribed: true,
    color: "yellow",
    name: "test",
    stream_id: 3,
    is_muted: true,
    invite_only: false,
};

This only tests public streams, but for our purposes, we need to test for private stream too. Now I was thinking of making another stream with invite_only set to true. So instead of just stream and stream-topic, test will now check for both stream_public and stream_private(same for stream_topic). But now  problem arises, turns out, I'm not allowed to create two a.stream. I think I should first test for public then somehow delete a.stream(no idea how to do that or something else, any help?)


Closes issue #93, deletes legacy folder.

Legacy configs will forever be available in the git repo history.  In the (unlikely) event anyone ever wants them, they will be available.

The Dota 2 Reborn Keyboard Setups should get a new name too then.

that name seems fine to me
but feel free to suggest alternatives

I think he's trying to say the naming is redundant...  I tend to agree, but I would also like to see the rest of the folders renamed to be more streamlined.  I.e. "!! THE CORE..."

Yes, I'm implying the name is redundant. There is nothing else than Reborn anymore. It's should be just called Dota 2.


[PROMOCODE] CHORE: update the Promo code script to run one script and provision all codes on all chains at once.

CHORE: update the Promo code script to run one script and provision all codes on all chains at once

Delievered.


Add ebfe to uutils members

because he is top 1 commiter in this moment and actively support the project :heart_decoration:

Oh I thought I did this already.. Will do yes, welcome @ebfe

Actually an invitation has been sent already, it just needs to be accepted at https://github.com/uutils

Actually an invitation has been sent already, it just needs to be accepted at https://github.com/uutils

Indeed. I've somehow missed the invitation mail.
Thanks everyone.


[FEATURE] Ignore Files

Use case
I have some projects in my iCloud documents with .git and node_module folders that i don't really need to sync.
Describe the solution you'd like
Add an ignore to the yml. Allow direct paths or asterisks
eg,
ignore:
  - */node_modules # ignore node modules
  - /projects/examples/.git # ignore specific git folder

Agreed, would be a very useful addition both for paths and extensions.
For backups, I prefer the strategy of "back it up unless I say not to" instead of "only back it up if I say so".


if aria-value/now/min/max is a decimal value, warning "ARIA state and property values must be valid"

According to the spec, a decimal value is fine. What am I missing?
http://www.w3.org/TR/wai-aria/states_and_properties#aria-valuenow

The value of aria-valuenow is a decimal number. If the range is a set of numeric values, then aria-valuenow is one of those values. For example, if the range is [0, 1], a valid aria-valuenow is 0.5. A value outside the range, such as -2.5 or 1.1, is invalid.

aria-valuenow and aria-valuemax warnings

aria-valuemin warning

Thank you!

is there a reason why both integer and 'decimal` values are validated the same way?
https://github.com/GoogleChrome/accessibility-developer-tools/blob/48b283ed84ab8544095b31c4b2052d523f9ffd8a/src/js/AccessibilityUtils.js#L692-L707
    case "integer":
    case "decimal":
        var validNumber = axs.utils.isValidNumber(value);
        if (!validNumber.valid) {
            result.valid = false;
            result.reason = validNumber.reason;
            return result;
        }
        if (Math.floor(validNumber.value) != validNumber.value) { // <--- this is testing decimals as well
            result.valid = false;
            result.reason = '' + value + ' is not a whole integer';
        } else {
            result.valid = true;
            result.value = validNumber.value;
        }
        return result;

Looks like an easy fix

Looks like the intention was to fall through from number to decimal not integer to decimal.

PR #196 will fix this.

Closed by #196


[Doubt] Tooltip information missing

Is your feature request related to a problem? Please describe.
The documentation lacks many information. For example. On tooltip what is the structure? Should be shown in a better way.
For example, I want to know if I can use hex color instead of text "red" for example.

Yes, you can use any CSS-valid color


DispatchError changes after encoding and then decoding

If we have a DispatchError::Module variant like this:
DispatchError::Module { index: 1, error: 1, message: Some("foo") }

After encoding and then decoding, it will become different:
DispatchError::Module { index: 1, error: 1, message: None }

IMHO it needs be fixed as in general variables should be the same. It could cause troubles while doing equal assertion. Like in ORML unit tests, when a event contains DispatchError, comparing the built even in test function with System::events() results unexpected unequal, unless with a manual conversion like here.

This is done by intention, because we don't want to store the message on chain.
I'm open to accept a pr that changes the PartialEq to ignore message.


Use of C++17 Atomic Exchange Causes Compilation Error with C++20

I'm trying to compile ginkgo with C++20, and I get the following error due to this line.
error: ‘memory_order_acq_rel’ is not a member of ‘std::memory_order

This happens due to two things:

C++ made the memory order enum strongly typed in C++20 and hence changed the naming to prevent accidental usage.
The code in the link above depends on implicit conversion of weakly-typed enum to int.

A fix would be to replace all occurrences of memory order with the newer version for newer language modes. There are a couple of ways I can think of to approach this:

Define a memory order macro, something like

#ifdef CPP20
#define MEMORY_ORDER_RELAXED std::memory_order::relaxed
#else
#define MEMORY_ORDER_RELAXED std::memory_order::memory_order_relaxed
#endif

Replace call sites of all functions with an #ifdef everywhere.

Thanks for highlighting this issue. We should probably be able to use OpenMP atomic pragmas instead, which also increases portability. I've been working on some other concurrent algorithms in Ginkgo OpenMP, so I'll tackle that soon.

Thank you for taking a look at this.
Someone pointed out to me that using std:: memory_order_acq_rel instead of std::memory_order:: memory_order_acq_rel should do the trick for both language modes without needing the #ifdefs.
May be that is a more palatable quick-fix solution.


Fixes #11305 Delete tasks corresponding to an entity when the entity …

…is deleted

Describe your changes:
Fixes #11305

I worked on ... because ...

Type of change:

[x] Bug fix
[ ] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

some tests are failing


Incorrect string-merge results when code is compiled with clang

When program_name_29___cpp_integration_cc__ is compiled with clang rather than gcc, it fails. Apparently all the merged strings end up as the string ELF. See https://github.com/davidlattimore/wild/pull/140. We should probably first add an option to allow overriding the compiler - i.e. #179.

I cannot see the wrong output, what happens to be is /home/marxin/Programming/wild/wild/tests/build/cpp-integration.cc-model-large.wild crashes with:
❯ valgrind wild/tests/build/cpp-integration.cc-model-large.wild
==42077== Memcheck, a memory error detector
==42077== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al.
==42077== Using Valgrind-3.23.0 and LibVEX; rerun with -h for copyright info
==42077== Command: /home/marxin/Programming/wild/wild/tests/build/cpp-integration.cc-model-large.wild
==42077==
==42077== Invalid read of size 1
==42077==    at 0x48506A2: strlen (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==42077==    by 0x49DEF57: std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator+=(char const*) (in /usr/lib64/libstdc++.so.6.0.33)
==42077==    by 0x4028F6: main (in /home/marxin/Programming/wild/wild/tests/build/cpp-integration.cc-model-large.wild)
==42077==  Address 0x0 is not stack'd, malloc'd or (recently) free'd

Do we speak about the same issue?

Interesting. I still get output even under valgrind:
valgrind wild/tests/build/cpp-integration.cc-model-large.wild
==13114== Memcheck, a memory error detector
==13114== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==13114== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==13114== Command: wild/tests/build/cpp-integration.cc-model-large.wild
==13114==
ELFELFELFELFELFELFELF
==13114==
==13114== HEAP SUMMARY:
==13114==     in use at exit: 0 bytes in 0 blocks
==13114==   total heap usage: 4 allocs, 4 frees, 73,820 bytes allocated
==13114==
==13114== All heap blocks were freed -- no leaks are possible
==13114==
==13114== For lists of detected and suppressed errors, rerun with: -s
==13114== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

I just tried running in the OpenSUSE docker image and the test there didn't pass linker-diff validation:
wild: /wild/wild/tests/build/cpp-integration.cc-model-large.wild
ld: /wild/wild/tests/build/cpp-integration.cc-model-large.ld
asm._start
  ORIG            `/usr/lib64/gcc/x86_64-suse-linux/14/../../../../lib64/crt1.o`
                  endbr64
                  xor %ebp,%ebp
                  mov %rdx,%r9
                  pop %rsi
                  mov %rsp,%rdx
                  and $0xFFFFFFFFFFFFFFF0,%rsp
                  push %rax
                  push %rsp
                  xor %r8d,%r8d
                  xor %ecx,%ecx

  wild 0x00402778 48 c7 c7 90 28 40 00 mov $0x402890,%rdi  // Mov_rm64_imm32(0x402890) main
  ld   0x00401038 48 8b 3d 49 2f 00 00 mov 0x2F68,%rdi  // Mov_r64_rm64(0x403f88) GOT(main)
  ORIG            48 8b 3d 00 00 00 00 mov 0x1F,%rdi  // R_X86_64_REX_GOTPCRELX -> `main` -4
  TRACE           relaxation.kind=RexMovIndirectToAbsolute value_flags=ADDRESS | CAN_BYPASS_GOT resolution_flags=DIRECT

                  callq *0  //<EMAIL_ADDRESS>                  hlt

section.ltext._ZNSt11char_traitsIcE7compareEPKcS2_m.flags
  wild AXG
  ld AX

section.ltext._ZStneIcSt11char_traitsIcESaIcEEbRKNSt7__cxx1112basic_stringIT_T0_T1_EEPKS5_.flags
  wild AXG
  ld AX

section.ltext._ZSteqIcSt11char_traitsIcESaIcEEbRKNSt7__cxx1112basic_stringIT_T0_T1_EEPKS5_.flags
  wild AXG
  ld AX

section.ltext._ZNSt11char_traitsIcE6lengthEPKc.flags
  wild AXG
  ld AX

We don't do anything special for .ltext sections and probably we should. Our support for large models is incomplete in other ways too.

If I edit the source file test arguments to be:
//#Config:model-large:default
//#CompArgs:-mcmodel=large
//#LinkArgs:--cc=clang -Wl,-z,now

putting clang instead of gcc, the test fails thus:
thread 'main' panicked at /home/andrew/workspace/wild/wild/tests/sources/rust-integration.rs:21:5:
Make sure unwinding works
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at /home/andrew/workspace/wild/wild/tests/sources/rust-integration.rs:21:5:
Make sure unwinding works
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test integration_test::program_name_28___rust_integration_dynamic_rs__ ... ok
/usr/bin/ld: /home/andrew/workspace/wild/wild/tests/build/cpp-integration.model-large-8ead9704af940f25.o: in function `main':
cpp-integration.cc:(.text+0x40): undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string()'
/usr/bin/ld: cpp-integration.cc:(.text+0x6a): undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator+=(char const*)'
/usr/bin/ld: cpp-integration.cc:(.text+0x9b): undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator+=(char const*)'
/usr/bin/ld: cpp-integration.cc:(.text+0xc5): undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator+=(char const*)'
/usr/bin/ld: cpp-integration.cc:(.text+0xef): undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator+=(char const*)'
/usr/bin/ld: cpp-integration.cc:(.text+0x120): undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator+=(char const*)'
/usr/bin/ld: /home/andrew/workspace/wild/wild/tests/build/cpp-integration.model-large-8ead9704af940f25.o:cpp-integration.cc:(.text+0x14a): more undefined references to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator+=(char const*)' follow
/usr/bin/ld: /home/andrew/workspace/wild/wild/tests/build/cpp-integration.model-large-8ead9704af940f25.o: in function `main':
cpp-integration.cc:(.text+0x1b6): undefined reference to `std::cout'
/usr/bin/ld: cpp-integration.cc:(.text+0x1ca): undefined reference to `std::basic_ostream<char, std::char_traits<char> >& std::operator<< <char, std::char_traits<char>, std::allocator<char> >(std::basic_ostream<char, std::char_traits<char> >&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
/usr/bin/ld: cpp-integration.cc:(.text+0x1d9): undefined reference to `std::basic_ostream<char, std::char_traits<char> >& std::endl<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&)'
/usr/bin/ld: cpp-integration.cc:(.text+0x1f0): undefined reference to `std::ostream::operator<<(std::ostream& (*)(std::ostream&))'
/usr/bin/ld: cpp-integration.cc:(.text+0x217): undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string()'
/usr/bin/ld: cpp-integration.cc:(.text+0x24b): undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string()'
/usr/bin/ld: /home/andrew/workspace/wild/wild/tests/build/cpp-integration.model-large-8ead9704af940f25.o: in function `bool std::operator==<char, std::char_traits<char>, std::allocator<char> >(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char const*)':
cpp-integration.cc:(.text._ZSteqIcSt11char_traitsIcESaIcEEbRKNSt7__cxx1112basic_stringIT_T0_T1_EEPKS5_[_ZSteqIcSt11char_traitsIcESaIcEEbRKNSt7__cxx1112basic_stringIT_T0_T1_EEPKS5_]+0x39): undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::size() const'
/usr/bin/ld: cpp-integration.cc:(.text._ZSteqIcSt11char_traitsIcESaIcEEbRKNSt7__cxx1112basic_stringIT_T0_T1_EEPKS5_[_ZSteqIcSt11char_traitsIcESaIcEEbRKNSt7__cxx1112basic_stringIT_T0_T1_EEPKS5_]+0x71): undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::size() const'
/usr/bin/ld: cpp-integration.cc:(.text._ZSteqIcSt11char_traitsIcESaIcEEbRKNSt7__cxx1112basic_stringIT_T0_T1_EEPKS5_[_ZSteqIcSt11char_traitsIcESaIcEEbRKNSt7__cxx1112basic_stringIT_T0_T1_EEPKS5_]+0x8d): undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::data() const'
/usr/bin/ld: /home/andrew/workspace/wild/wild/tests/build/cpp-integration.model-large-8ead9704af940f25.o:(.data.rel.local.DW.ref.__gxx_personality_v0[DW.ref.__gxx_personality_v0]+0x0): undefined reference to `__gxx_personality_v0'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
test integration_test::program_name_29___cpp_integration_cc__ ... FAILED
thread 'main' panicked at /home/andrew/workspace/wild/wild/tests/sources/rust-integration.rs:21:5:
Make sure unwinding works
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at /home/andrew/workspace/wild/wild/tests/sources/rust-integration.rs:21:5:
Make sure unwinding works
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test integration_test::program_name_27___rust_integration_rs__ ... ok
test integration_test::program_name_26___libc_integration_c__ ... ok
test integration_test::program_name_30___rust_tls_rs__ ... ok

failures:

---- integration_test::program_name_29___cpp_integration_cc__ stdout ----
Error: Failed to build program `cpp-integration.cc` with linker `ld` config `model-large`

Caused by:
    Linker failed. Relink with:
    clang --ld-path=/usr/bin/ld -Wl,-z,now -o /home/andrew/workspace/wild/wild/tests/build/cpp-integration.cc-model-large.ld /home/andrew/workspace/wild/wild/tests/build/cpp-integration.model-large-8ead9704af940f25.o /home/andrew/workspace/wild/wild/tests/build/cpp-integration-2.model-large-d2a94c574f4beb01.o

failures:
    integration_test::program_name_29___cpp_integration_cc__

test result: FAILED. 29 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 3.53s

error: test failed, to rerun pass `-p wild --test integration_tests`

Would they be a reproducer for this issue, to allow me to tinker with it and see what the cause it?

OK, got it reproducing same output now. Thanks.


S-1114660 - Initial backend plugin changes for getting the release categories

Release Checklist

All steps below must be completed prior to merging.

Changes Made

Please note all changes made to API, design, functionality, etc.

Author Checklist
Required

[ ] PR title should follow correct format.

MAJOR Release is used when there are breaking changes involved
MINOR Release is used when enhancements are introduced
PATCH Release is used for defects, security, tech chores, etc.
pre-alpha is used for testing releases
Note:

Based on the commit messages, increment the version from the latest release.
Push the bumped npm version in package.json back into the repo.
Push a tag for the new version back into the repo.
For more details on versioning

[ ] Checklist of changes made added to PR description
[ ] Related issue(s) linked to PR

Reviewer Checklist

[ ] Author checklist has been reviewed?
[ ] All acceptance criteria has been met from linked issue
[ ] Run code locally and verify all changes

Related Issue(s)
Resolves #XXXX
Story-######
Defect-######

Checking Yarn install - failed in Actions automation


[BUG] Email link

Describe the bug
When recieving the email about a new ticket the button redirects to the localhost one.
To Reproduce
Steps to reproduce the behavior:

Go to 'Customer Area'
Click on 'Tickets'
Click on '+ Create'
Add the necessary info.
Click on 'Create'
Go to your email
Select the one about the new ticket
Press on the button to view the ticket.
It redirects to localhost/tickets/ticket_id

Expected behavior
The button would redirect to the ticket and not to the localhost. (Example: billing.paymenter.org/tickets/112)
Screenshots

Desktop (please complete the following information):

OS: Windows 10 Home
Browser Crhome
Version 0.9.3

Thanks for the issue, luckily this is a small configuration issue:

Open up your .env file (normally located in /var/www/paymenter).
Change APP_URL to your url with https (eg https://billing.paymenter.org)

I recommend joining our discord so we can easily help you with those issues!


[cloud] Very basic port forwarding

Summary
In the spirit of fast incremental improvements, this is very basic port forwarding. It simply Execs an ssh command. This method has many caveats and is not meant to wide use.
Caveats/TODOs:

Uses ssh command instead of golang forwarding. Using ssh command directly is simpler so not sure we should change that.
May not show an error if local port is not available. In my testing, only protected ports caused an error. Using ExitOnForwardFailure=yes did not seem to work for this. May need to manually ensure port is available.
Does not stop port forwarding at all. There's several options to do this. We can attach stdin/out which would cause this command to block and we can add a clean up function that cancels the forwarding when user does ctrl-c.
Better error message when forwarding does fail (currently just shows Error: exit status 255)

I plan follow up PRs that address these.
How was it tested?
Create VM:
devbox cloud shell
devbox add apacheHttpd
devbox services start apache

Locally:
devbox cloud port-forward 3000:8080
curl localhost:3000

Example with mutagen:
mutagen forward create \
    --name "my-session" \
    tcp:<IP_ADDRESS>:8000 vm-hostname:<IP_ADDRESS>:80

This is hidden because cloud is hidden but I can explicitly mark this as hidden as well.
Sounds good will do. Another UX improvement could be to allow :8080 which automatically finds am unused local port
Sounds good. Need to catch up on mutagen stuff.

This is hidden because cloud is hidden but I can explicitly mark this as hidden as well.
Sounds good will do. Another UX improvement could be to allow :8080 which automatically finds am unused local port
I like this idea.

Sounds good. Need to catch up on mutagen stuff.
Before we get into the mutagen stuff, what do you think would be missing from the current implementation, to deem it "ready for open beta". Trying to think if it makes more sense to polish the ssh approach, and have it ready for beta or if it's best to get started on the mutagen approach as the way to make it ready for beta.

Before we get into the mutagen stuff, what do you think would be missing from the current implementation, to deem it "ready for open beta". Trying to think if it makes more sense to polish the ssh approach, and have it ready for beta or if it's best to get started on the mutagen approach as the way to make it ready for beta.

I think the 2 most important are:

Good error messages when forwarding fails for any reason
Keep devbox process alive and cancel forwarding when it stops (or some other way to stop forwarding)

I can try to mutagen approach and if it's simple enough I'll move to that. If I hit any issues, I can always fallback


TextFormField losing state on validation after getImage() called

Simple form page with TextFormField
Type word inside TextFormField
Call PickedFile pickedFile = await widget.picker.getImage(source: ImageSource.gallery);
When returned from picker, TextFormField will lose state
Call validate from TextFormField after image picked (in my case validator checks if TextFormField's value is empty), word will be there, but value returned from validator will return null

Actually this is just a app state problem caused by using TextFormField inside ListView, using SingleChildScrollView with a Column resolved the issue.


Changes to 3DCursor javadocs

Looks good. Will merge in the afternoon.

Looks good. Can be merged.


Cannot read properties of undefined (reading 'AccountId')

https://issues.apache.org/jira/projects/INFRA/issues/INFRA-26283?filter=allopenissues
https://github.com/apache/incubator-seata-website/actions/runs/11996747206/job/33441555819

solution:  update the secret.


Seattle Specific: Switch Upload/Download in the user form

Users are entering download speeds in the upload boxes because they are used to being given the numbers in download/upload pairings from their providers. Let's switch the form to match what users expect.

This has been updated in master.


Problem with input and popup

Hello!
Trying to use your emoji widget but having troubles.
For one, the image for the 'emoji' selector on the input is coming out strange, like it's been resized.  I have applied no style to the emoji-input.  I am using semantic.ui however.
The second issue is that the popup for the emoji picker is going right off the page.  Any way I can offset it?
Thanks.

This module is still in early development and not yet finished. It for example don't take in consideration page limits when opening the popup. You can however (for now) set it to open above the input field using this snippet <emoji-input  [popupAnchor]="'top'">. I don't know if that will solve your issue.
I can't say when i will have time to look at this. If your in need of change now, don't hesitate to make a pull request.