Skip to content

[SQL] Fixes for #1843 and #1844 - #1845

Merged
mihaibudiu merged 1 commit into
mainfrom
issue1843
Jun 6, 2024
Merged

[SQL] Fixes for #1843 and #1844#1845
mihaibudiu merged 1 commit into
mainfrom
issue1843

Conversation

@mihaibudiu

Copy link
Copy Markdown
Contributor

Is this a user-visible change (yes/no): no

Fixes #1843
Fixes #1844

Signed-off-by: Mihai Budiu <mbudiu@feldera.com>
@mihaibudiu

Copy link
Copy Markdown
Contributor Author

These could use more tests, but at least the rust error are gone

@mihaibudiu mihaibudiu closed this Jun 6, 2024
@mihaibudiu mihaibudiu reopened this Jun 6, 2024
@mihaibudiu
mihaibudiu merged commit 5e2cd47 into main Jun 6, 2024
@mihaibudiu
mihaibudiu deleted the issue1843 branch June 6, 2024 17:48
blp added a commit that referenced this pull request Jul 30, 2026
CPU Jitter Entropy's health check can fail on freshly-started VMs/containers
(timing signal too regular in the first seconds of process life), which
aws-lc treats as fatal and abort()s with no stderr output. This has been
crashing pipelines and coordinators seconds after startup during the first
TLS handshake (#1845), matching aws-lc-rs#1072.

Set AWS_LC_SYS_NO_JITTER_ENTROPY=1 in .cargo/config.toml for CI/local builds,
and explicitly in the pipeline compiler's cargo invocation, which env_clear()s
and needs it forwarded separately since it builds the pipeline binary that
actually hits the abort.

Fixes: feldera/cloud#1845

Signed-off-by: Ben Pfaff <blp@feldera.com>
jessemenning pushed a commit to jessemenning/feldera that referenced this pull request Jul 31, 2026
CPU Jitter Entropy's health check can fail on freshly-started VMs/containers
(timing signal too regular in the first seconds of process life), which
aws-lc treats as fatal and abort()s with no stderr output. This has been
crashing pipelines and coordinators seconds after startup during the first
TLS handshake (feldera#1845), matching aws-lc-rs#1072.

Set AWS_LC_SYS_NO_JITTER_ENTROPY=1 in .cargo/config.toml for CI/local builds,
and explicitly in the pipeline compiler's cargo invocation, which env_clear()s
and needs it forwarded separately since it builds the pipeline binary that
actually hits the abort.

Fixes: feldera/cloud#1845

Signed-off-by: Ben Pfaff <blp@feldera.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[SQL] SQL program generates uncompilable Rust [SQL] Following program generates incompilable Rust

1 participant