Skip to content

Conversation

geoand
Copy link
Contributor

@geoand geoand commented May 14, 2025

This is a draft for now I as I have identified were the problem needs to be addressed, but we need to decide which server options we are going to be setting on these two instances

Copy link
Member

@cescoffier cescoffier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We would need to pass the limit.

Now, the AWS lambda server is sub-configured, and would need a lot more work.

@geoand
Copy link
Contributor Author

geoand commented May 14, 2025

My question was actually what other params should we be passing that we currently are not?

@geoand geoand changed the title WIP: Deal with max headers size in Amazon Lambda Deal with max headers size in Amazon Lambda May 15, 2025
@geoand geoand requested a review from cescoffier May 15, 2025 11:42
@geoand geoand marked this pull request as ready for review May 15, 2025 11:42
@geoand
Copy link
Contributor Author

geoand commented May 15, 2025

For now, I only passed the option needed to fix the issue in question

Copy link

quarkus-bot bot commented May 15, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 1fedf26.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.


Flaky tests - Develocity

⚙️ JVM Integration Tests - JDK 17

📦 integration-tests/opentelemetry

io.quarkus.it.opentelemetry.LoggingResourceTest.testException - History

  • Condition with Lambda expression in io.quarkus.it.opentelemetry.LoggingResourceTest was not fulfilled within 2 minutes. - org.awaitility.core.ConditionTimeoutException
org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.it.opentelemetry.LoggingResourceTest was not fulfilled within 2 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1129)
	at io.quarkus.it.opentelemetry.LoggingResourceTest.testException(LoggingResourceTest.java:113)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)

⚙️ JVM Integration Tests - JDK 21

📦 integration-tests/opentelemetry

io.quarkus.it.opentelemetry.LoggingResourceTest.testException - History

  • Condition with Lambda expression in io.quarkus.it.opentelemetry.LoggingResourceTest was not fulfilled within 2 minutes. - org.awaitility.core.ConditionTimeoutException
org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.it.opentelemetry.LoggingResourceTest was not fulfilled within 2 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1129)
	at io.quarkus.it.opentelemetry.LoggingResourceTest.testException(LoggingResourceTest.java:113)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)

@cescoffier cescoffier merged commit 698b15c into quarkusio:main May 16, 2025
73 of 74 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.24 - main milestone May 16, 2025
@geoand geoand deleted the #47483 branch May 16, 2025 07:49
@gsmet gsmet modified the milestones: 3.24 - main, 3.23.0 May 20, 2025
@jmartisk jmartisk modified the milestones: 3.23.0, 3.20.2 Jun 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Max header size configuration property is not used with AWS Lambda HTTP extension

4 participants