Skip to content

java.lang.invoke.LambdaConversionException: Invalid receiver type interface org.apache.http.Header; not a subtype of implementation type interface org.apache.http.NameValuePair #1795

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Baratam opened this issue Apr 29, 2020 · 10 comments
Labels
guidance Question that needs advice or information.

Comments

@Baratam
Copy link

Baratam commented Apr 29, 2020

Describe the issue

I have two lambdas, the 1st lambda invokes the 2nd and I am using aws sdk bom to 2.13.5 (software.amazon.awssdk) in my pom, but unable to invoke a lambda from another lambda. received the below error while lambda invoke.I used the same piece of java code which is mentioned in the aws docs, but still getting the error.
The same mentioned in aws docs: https://docs.aws.amazon.com/sdk-for-java/v2/developer-guide/setup-project-maven.html
I couldn't reopen the above thread, so creating this new thread, i also reached aws support, but the support engineer suggested to post the issue over here.
Below are the dependencies i used in my pom, I also tried all scenarios discussed in this chain : #652 (updating httpcore, httclient etc..but nothing works)
Please find the attached zip for dependencies used in my project.
Please find the attached zip for java code used in my project to invoke .
Please find the attached image for my mvn dependency tree .

Error while invoking lambda:
{
"errorMessage": "call site initialization exception",
"errorType": "java.lang.BootstrapMethodError",
"stackTrace": [
"java.lang.invoke.CallSite.makeSite(CallSite.java:341)",
"java.lang.invoke.MethodHandleNatives.linkCallSiteImpl(MethodHandleNatives.java:307)",
"java.lang.invoke.MethodHandleNatives.linkCallSite(MethodHandleNatives.java:297)",
"software.amazon.awssdk.http.apache.ApacheHttpClient.transformHeaders(ApacheHttpClient.java:268)",
"software.amazon.awssdk.http.apache.ApacheHttpClient.createResponse(ApacheHttpClient.java:253)",
"software.amazon.awssdk.http.apache.ApacheHttpClient.execute(ApacheHttpClient.java:233)",
"software.amazon.awssdk.http.apache.ApacheHttpClient.access$500(ApacheHttpClient.java:98)",
"software.amazon.awssdk.http.apache.ApacheHttpClient$1.call(ApacheHttpClient.java:213)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.executeHttpRequest(MakeHttpRequestStage.java:66)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.execute(MakeHttpRequestStage.java:51)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.execute(MakeHttpRequestStage.java:35)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:73)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:42)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:77)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:39)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:64)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:34)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:56)",
"software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:36)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.executeWithTimer(ApiCallTimeoutTrackingStage.java:80)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:60)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:42)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ExecutionFailureExceptionReportingStage.execute(ExecutionFailureExceptionReportingStage.java:37)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ExecutionFailureExceptionReportingStage.execute(ExecutionFailureExceptionReportingStage.java:26)",
"software.amazon.awssdk.core.internal.http.AmazonSyncHttpClient$RequestExecutionBuilderImpl.execute(AmazonSyncHttpClient.java:189)",
"software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.invoke(BaseSyncClientHandler.java:121)",
"software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.doExecute(BaseSyncClientHandler.java:147)",
"software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.execute(BaseSyncClientHandler.java:101)",
"software.amazon.awssdk.core.client.handler.SdkSyncClientHandler.execute(SdkSyncClientHandler.java:45)",
"software.amazon.awssdk.awscore.client.handler.AwsSyncClientHandler.execute(AwsSyncClientHandler.java:55)",
"software.amazon.awssdk.services.lambda.DefaultLambdaClient.invoke(DefaultLambdaClient.java:1645)",
"com.abnamro.nl.solution.polar.application.utils.AwsLambdaInvokeUtil.invoke(AwsLambdaInvokeUtil.java:80)",
"com.abnamro.nl.solution.polar.application.controllers.SegmentController.getSegments(SegmentController.java:64)",
"com.abnamro.nl.solution.polar.application.GetSegmentsApplication.handleRequest(GetSegmentsApplication.java:65)",
"sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)",
"sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)",
"sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)",
"java.lang.reflect.Method.invoke(Method.java:498)"
],
"cause": {
"errorMessage": "Invalid receiver type interface org.apache.http.Header; not a subtype of implementation type interface org.apache.http.NameValuePair",
"errorType": "java.lang.invoke.LambdaConversionException",
"stackTrace": [
"java.lang.invoke.AbstractValidatingLambdaMetafactory.validateMetafactoryArgs(AbstractValidatingLambdaMetafactory.java:233)",
"java.lang.invoke.LambdaMetafactory.metafactory(LambdaMetafactory.java:303)",
"java.lang.invoke.CallSite.makeSite(CallSite.java:302)",
"java.lang.invoke.MethodHandleNatives.linkCallSiteImpl(MethodHandleNatives.java:307)",
"java.lang.invoke.MethodHandleNatives.linkCallSite(MethodHandleNatives.java:297)",
"software.amazon.awssdk.http.apache.ApacheHttpClient.transformHeaders(ApacheHttpClient.java:268)",
"software.amazon.awssdk.http.apache.ApacheHttpClient.createResponse(ApacheHttpClient.java:253)",
"software.amazon.awssdk.http.apache.ApacheHttpClient.execute(ApacheHttpClient.java:233)",
"software.amazon.awssdk.http.apache.ApacheHttpClient.access$500(ApacheHttpClient.java:98)",
"software.amazon.awssdk.http.apache.ApacheHttpClient$1.call(ApacheHttpClient.java:213)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.executeHttpRequest(MakeHttpRequestStage.java:66)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.execute(MakeHttpRequestStage.java:51)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.execute(MakeHttpRequestStage.java:35)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:73)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:42)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:77)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:39)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:64)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:34)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:56)",
"software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:36)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.executeWithTimer(ApiCallTimeoutTrackingStage.java:80)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:60)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:42)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ExecutionFailureExceptionReportingStage.execute(ExecutionFailureExceptionReportingStage.java:37)",
"software.amazon.awssdk.core.internal.http.pipeline.stages.ExecutionFailureExceptionReportingStage.execute(ExecutionFailureExceptionReportingStage.java:26)",
"software.amazon.awssdk.core.internal.http.AmazonSyncHttpClient$RequestExecutionBuilderImpl.execute(AmazonSyncHttpClient.java:189)",
"software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.invoke(BaseSyncClientHandler.java:121)",
"software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.doExecute(BaseSyncClientHandler.java:147)",
"software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.execute(BaseSyncClientHandler.java:101)",
(https://github.com/aws/aws-sdk-java-v2/files/4552736/dependencies.xml.zip)
"software.amazon.awssdk.core.client.handler.SdkSyncClientHandler.execute(SdkSyncClientHandler.java:45)",
"software.amazon.awssdk.awscore.client.handler.AwsSyncClientHandler.execute(AwsSyncClientHandler.java:55)",
"software.amazon.awssdk.services.lambda.DefaultLambdaClient.invoke(DefaultLambdaClient.java:1645)",
"com.abnamro.nl.solution.polar.application.utils.AwsLambdaInvokeUtil.invoke(AwsLambdaInvokeUtil.java:80)",
"com.abnamro.nl.solution.polar.application.controllers.SegmentController.getSegments(SegmentController.java:64)",
"com.abnamro.nl.solution.polar.application.GetSegmentsApplication.handleRequest(GetSegmentsApplication.java:65)",
"sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)",
"sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)",
"sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)",
"java.lang.reflect.Method.invoke(Method.java:498)"
]
}
}

Steps to Reproduce

Create two lambdas within VPC, invoke 2nd lambda from 1st lambda.
Use these in pom groupid: software.amazon.awssdk, version: 2.13.5, artifactId:bom

Current Behavior

Receives error:
"errorMessage": "Invalid receiver type interface org.apache.http.Header; not a subtype of implementation type interface org.apache.http.NameValuePair",
"errorType": "java.lang.invoke.LambdaConversionException",
Please find the attached zip for dependencies used in my project.

Your Environment

  • AWS Java SDK version used: groupid: software.amazon.awssdk, version: 2.13.5, artifactId:bom
  • JDK version used: v8
  • Operating System and version: AWS lambda service
    Please find the attached zip for dependencies used in my project.
    Please find the attached zip for java code used in my project to invoke .
    Please find the attached image for my mvn dependency tree .

dependencies.xml.zip
AwsLambdaInvokeUtil.java.zip
mvn dpn tree

@Baratam Baratam added guidance Question that needs advice or information. needs-triage This issue or PR still needs to be triaged. labels Apr 29, 2020
@bmaizels
Copy link
Contributor

The error itself looks related to this change : apache/httpcomponents-core@6abc8da

The SDK was compiled using a version of httpcore that was built after this change, and your lambda appears to be executing code from a dependency that was built before this change, hence the incompatability.

@Baratam
Copy link
Author

Baratam commented Apr 29, 2020

hi @bmaizels
Thanks for the quick reply but could you please let me what needs to be done now to resolve my issue
i used httpcore version 4.4.13.

@bmaizels
Copy link
Contributor

bmaizels commented Apr 29, 2020

Hi, @Baratam

That's the rub, I believe that you believe you are using httpcore 4.4.13, but the error message is clearly telling us you are not. I believe any version >=4.4.9 would work, but you must be actually using a version earlier than that. I would focus on debugging your dependency tree, or finding a way to prove definitively that you are in fact using 4.4.13. The screenshot you gave shows httpcore version 4.4.4

@Baratam
Copy link
Author

Baratam commented Apr 29, 2020

that's good cath @bmaizels , i will check this, i have to force it to use 4.4.9

@bmaizels
Copy link
Contributor

@Baratam please use whatever version apache httpclient lists as their dependencies. So, for example, if you are using httpclient 4.5.9 then you should be using httpcore version 4.4.11. Always force both versions together.

@debora-ito debora-ito removed the needs-triage This issue or PR still needs to be triaged. label Apr 29, 2020
@Baratam
Copy link
Author

Baratam commented Apr 29, 2020

hi @bmaizels
the httpcore 4.4.4 is downloaded because of I am using aws x-ray 2.4.0, after removing the bom of x-ray, the issue is solved and able to invoke the lambda. the x-ray 2.4.0 is using 4.4.4 version of http core



com.amazonaws
aws-xray-recorder-sdk-bom
2.4.0
pom
import


@bmaizels
Copy link
Contributor

Awesome, thanks for getting back to us. Good luck!

@Baratam
Copy link
Author

Baratam commented Apr 29, 2020

yes, thanks @bmaizels for the very quick responses.
i am doing this change for a different issue i.e. lambda to lambda invocation time which is taking 3secs. its been suggested by aws support engineer to upgrade our aws sdk version form v1.xx.xxx to v2.xx.xx to resolve the lambda invocation time, i will post the issue in detail if it is allowed in this thread ? otherwise i will create a new thread & continue there.

@bmaizels
Copy link
Contributor

@Baratam Please create a new thread, thanks.

@raviranjandutta
Copy link

add this in pom.xml. it will fix the error.

org.apache.httpcomponents httpcore 4.4.9

thll added a commit to Graylog2/graylog2-server that referenced this issue May 21, 2021
Managing and fixing the http client to a specific version works
around resolving the dependency to different versions in plugins.
This would cause unexpected problems as described in
aws/aws-sdk-java-v2#1795
thll added a commit to Graylog2/graylog2-server that referenced this issue May 25, 2021
Managing and fixing the http client to a specific version works
around resolving the dependency to different versions in plugins.
This would cause unexpected problems as described in
aws/aws-sdk-java-v2#1795
Gaya added a commit to Graylog2/graylog2-server that referenced this issue May 25, 2021
* Bump lodash from 4.17.20 to 4.17.21 in /graylog2-web-interface (#10595)

Bumps [lodash](https://github.com/lodash/lodash) from 4.17.20 to 4.17.21.
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@4.17.20...4.17.21)

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Centralize timeout multiplier handling in tests. (#10591)

* Centralize timeout multiplier handling.

In a couple of places we need to set custom timeouts for jest tests. In
these cases we should take the `TIMEOUT_MULTIPLIER` env variable into
account. In order to avoid having to handle that over and over again
(parsing, validating, applying it), this change is adding two functions
to the `jest-preset-graylog` module:

  - `timeoutMultiplier()`: returning the raw multiplier, `1.0` if not
    set or not parseable
  - `applyTimeoutMultiplier(x: number)`: applies the configured timeout
    multiplier to any given timeout

The latter function should be used in tests to apply the multiplier to
any custom timeout override.

* Adding license header.

* Use default values for scaling & interpolation if absent. (#10590)

* Return default value for scaling factor if absent.

* Use `linear` if interpolation mode is absent.

* Allow emptying relative range value inputs in date time picker when entering new value. (#10612)

* Allow to temporary empty relative range value inputs in date time picker.

Before this change it was not possible to temporary empty the relative
range value inputs. When a user tried to remove all numbers, we
automatically inserted a 1. We mainly did this because we are always
updating the form state `onChange`. If we would define for example
`undefined` for the relative range value, we would loose the
information which range type is selected. The range type is
being inferred based on the time range form value.

For example if the form state value for the relative range is 300, the
`RelativeRangeSelect` displays: 5 (value) minutes (type).

With this PR we are implementing a separate state for the `RelativeRangeSelect` which controls the
relative range inputs. We are still updating the form state
`onChange`. Every time the form state changes we are synchronizing the
`RelativeRangeSelect`. When a user empties the range value input, we are
defining `null` for the range form state. By implementing a separate state, we
are able to remember the previous selected range type and consider the
type when the user defines a completely new range value.

* Creating separate component for `RelativeRangeValueInput` and wrapping it with `React.memo`.

Before this change, the range value input cursor lost its position after
the user changed the input value, because the input rerendered multiple
times `onChange`. Now we are only rerendering the
component when necessary. This way react remembers the cursor position.

* Creating tests for new `RelativeRangeSelect` select changes.

* Updating component name.

* Fixing ts error.

* Unifying test names.

* Change back REQUEST_HEADERS access to public (#10621)

* Do not require a defaultValue to be set in Heatmap (#10620)

## Motivation
Prior to this change, the defaultValue was required to be set
for a heatmap. But there is no technical reason for that.

## Description
This change will set the required field to false and adjust the tests.

* Adaptable Dashboard Tabs (#10371)

* Make Dashboard Tabs responsive

* throttled resize & functional component

* fix Nav tab styles

* styles

* stylelint

* tsc

* stylelint-processor-styled-components

* stylelint

* remove flag

* PR feedback

* fixing invalid selector error

* Updating colors to be a bit brighter in Noir

* more active class fix

* note about "failing" lint

* working with sizeme

* couple tests

* stop scrolling after adding new tab & lock new tab to end

* typing and getting proper tab to lock open

* more typescript cleaning

* snapshot

* tsc error

* tests

* feedback from @linuspahl

* tweak naming convention of new tabs to avoid duplicates

* relock active tab after save as

* relock active tab after save as cleanup

* Fixing `Search.dashboard.test`.

* Add tests for logic if query tabs should be displayed as main tabs or in more tabs dropdown.

* Add further tests for query tabs creation and selection.

* Fixing assignment of aria-hidden for query tabs in dropdown.

* Fixing linter warning.

Co-authored-by: Linus Pahl <[email protected]>

* Limit field types retrieval to timerange of query. (#10562)

* Extend `FieldTypesResource` to support optional timerange parameter.

* Include time range in requests, refresh store when time range changes.

* Provide widget field types through context.

* Change wording for field set selection in sidebar.

* Consider global override for field types retrieval.

* Adding/adjusting tests.

* Extracting custom `useCurrentQuery` hook.

* Adding test for field types provider.

* Extending test.

* Adding license headers.

* Migrating `SavedSearchControls` test to testing-library and adjust to change.

* Migrating tests to testing-library.

* Removing unused import.

* Mocking `FieldTypesStore` in test.

* Migrating `ExportModal` to use context instead of store.

* Adjusting tests.

* Removing unused mocks.

* Removing unused mocks, use `PluginStore` instead of mocking it.

* Mocking `FieldTypesStore` in more tests.

* Mocking `WidgetStore` in test.

* Adding field types POST endpoint to integration test API.

* Do not include empty streams list in request.

* Style common `Select` based on `FormGroup` validation state. (#10624)

* Display `Select` styling based on `FormGroup` validation state.

Our form components consider the validation state when being used inside
a `FormGroup`. Before this change our common `Select`component was an
exception. With this change we are updating the styling (mainly the border) accordingly.

* Using darker border color for form components inside `FormGroup`.

* Removing not perfectly working styles.

* Updating snapshots.

* Support form data for `fetch`/`Builder`. (#10638)

* Support form data for `fetch`/`Builder`.

* Simplifying conditional, thanks @edmundoa!

* Fixing message loading when testing message against stream. (#10575)

* Fixing submitting message id/index values.

* Migrate `MessageLoader` component to TS and functional component.

* Fixing indentation.

* Replacing link with proper button, changing wording.

* Use correct variable to decide if form should be expanded.

* Fix focussing message id input when visibility of form changes.

* Improving typing: making `messageId`/`index` props optional, set default values.

* Fixing default value.

* Renaming component to tsx.

* Migrating to typed functional component.

* add inputConfiguration type to PluginExports

 - add svg module definition

* Update graylog2-web-interface/src/@types/graylog-web-plugin/index.d.ts

Co-authored-by: Edmundo Alvarez <[email protected]>

* Update graylog2-web-interface/src/@types/graylog-web-plugin/index.d.ts

Co-authored-by: Edmundo Alvarez <[email protected]>

* Configurations style (#10625)

* Replace CSS file with styled-component

* Avoid clipping by increasing the dd margin

* Add some space after each configlet

* Fix loading of Pipeline simulator page (#10664)

* Fix issue rendering RawMessageLoader component

The `inputs` prop of `RawMessageLoader` now receives an `ImmutableJS.Map`
object but we didn't update usages of that prop. This resulted in an
incorrect behaviour when using the JS standard API with the
`ImmutableJS.Map` object, that could throw an error.

This change uses the ImmutableJS API to work with the `inputs` prop,
ensuring the code behaves as expected.

Fixes #10663

* Make originalMessage proptype optional

* Bump @testing-library/react-hooks (#10670)

Bumps [@testing-library/react-hooks](https://github.com/testing-library/react-hooks-testing-library) from 5.1.3 to 6.0.0.
- [Release notes](https://github.com/testing-library/react-hooks-testing-library/releases)
- [Changelog](https://github.com/testing-library/react-hooks-testing-library/blob/main/CHANGELOG.md)
- [Commits](testing-library/react-hooks-testing-library@v5.1.3...v6.0.0)

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Use more secure TLS default ciphers (#10653)

Our defaults (even with TLS 1.2 and 1.3 only)
were still susceptible to LOGJAM, LUCKY13 and a possible DoS attack.

We programatically use secure defaults for the JDK and for Netty with OpenSSL

Fixes https://github.com/Graylog2/graylog-plugin-enterprise/issues/2202

* Better swagger specs through extracting inline models. (#10637)

* Create proper swagger schema.

* Handle generics properly.

* Fixing corner cases and type names.

* Add visitor to replace `type: any` values.

* Extract inline objects.

* Adding json annotation.

* Fixing reference naming, cleaning up unused code.

* Treat parameters identically to response types.

* Fix multiple issues, keep parameter types inline if not objects.

* Fix primitive method response types.

* Fixing enums and longs.

* Inline non-object models.

* Falling back to value when parameter name is not present.

* Use nickname over method name, if present.

* Include missing import.

* Fix creatable select focus and "create value" option label problem. (#10644)

* Prevent loosing focus when removing content of creatable select input.

Before this change it was possible to loose the react creatable select focus
after removing its content, because we updated the component state unnecessarily.
With this change we ensure that we only update the state when necessary.

* Display "Create value" option label correctly when using `displayKey`
select prop.

* Prevent unnecessary search execution when unfocusing widget. (#10673)

When introducing functionality, which limits search execution to the
widget which is currently edited, a change was added that performs a
search execution when leaving edit mode. Unfortunately the condition
which was used to determine if widget editing is left was too broad, so
it is performed whenever the widget focusing state changes. This leads
to e.g. double search execution when loading a new/saved search.

This PR is changing the condition to check if the previous state
indicates widget editing mode and does not perform a new search
execution otherwise.

* Scratchpad Updates & Tests (#10667)

* Fix Scratchpad Tooltip/Help not appearing

* typo

* Typescript scratchpad & redo status messages

* Scratchpad tests

* snapshot and clear timeout

* Improving `SearchBar` and `DashboardSearchBar` responsiveness. (#10652)

* Improving `SearchBar` responsiveness.

* Improving responsiveness of `DashboardSearchBar`.

* Fixing `SearchBar` test.

* Temporary add `TopRow` component to test test CI behaviour.

* Removing no longer needed search bar `TopRow` component.

* Fix and centralize qualifying relative URLs with credentials. (#10675)

* Adding `urijs` types.

* Migrating `URLUtils` to TS.

* Adding tests.

* Qualify URLs with scheme/hostname from current location if server url is unqualified.

* Reuse function to add session id to URL.

* Make `qualifyUrl` idempotent.

* Fix type errors introduced by typing `urijs`.

* Adding license header.

* Using empty string if server url is not present to avoid using `undefined`.

* Do not pass `undefined` to `URI.session`.

* Adding/fixing missing mocks in test.

* Adding more mocks.

* Exporting through frontend without buffering response in browser. (#10617)

* First dirty working draft.

* Some cleanup.

* Registering media types for file extensions.

* Adding audit events for export jobs.

* Managing endpoint URL centrally.

* Timestamping export jobs, removing expired ones.

* Using UTC all the way.

* Removing `downloadjs`.

* Adding license headers.

* Updating vendor module ids.

* Throwing exception in tests if value is missing.

* Reverting change that replaces anonymous instance with lambda, added comment.

* Removing periodical, replacing with TTL index on mongo collection.

* Serialize `createdAt` field.

* Fixing href.

* Cleaning up `MessagesResource`.

* Removing unused import.

* Reverting unneeded change.

* A-element does not actually need to be in the dom.

* Make use of `qualifyUrlWithSessionCredentials` to include session credentials in URL.

* Returning 404 for invalid export job id.

* Attach link to DOM.

* Fix apache httpclient to version 4.5.13 (#10684)

Managing and fixing the http client to a specific version works
around resolving the dependency to different versions in plugins.
This would cause unexpected problems as described in
aws/aws-sdk-java-v2#1795

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Dennis Oelkers <[email protected]>
Co-authored-by: Linus Pahl <[email protected]>
Co-authored-by: Edmundo Alvarez <[email protected]>
Co-authored-by: Konrad Merz <[email protected]>
Co-authored-by: Kyle Knight <[email protected]>
Co-authored-by: Ousmane Samba <[email protected]>
Co-authored-by: Marco Pfatschbacher <[email protected]>
Co-authored-by: Othello Maurer <[email protected]>
mpfz0r pushed a commit to Graylog2/graylog2-server that referenced this issue May 26, 2021
* Fix apache httpclient to version 4.5.13

Managing and fixing the http client to a specific version works
around resolving the dependency to different versions in plugins.
This would cause unexpected problems as described in
aws/aws-sdk-java-v2#1795

* Expose docker network of graylog backend test container

Expose the docker network, so that other containers that need to be
launched during a test can use the same network.
aws-sdk-java-automation added a commit that referenced this issue Oct 27, 2021
…d9f69ed92

Pull request: release <- staging/e37adab4-80b1-4aa0-b22c-f1dd9f69ed92
luca-digrazia pushed a commit to luca-digrazia/DatasetCommitsDiffSearch that referenced this issue Sep 4, 2022
    * Fix apache httpclient to version 4.5.13

    Managing and fixing the http client to a specific version works
    around resolving the dependency to different versions in plugins.
    This would cause unexpected problems as described in
    aws/aws-sdk-java-v2#1795

    * Expose docker network of graylog backend test container

    Expose the docker network, so that other containers that need to be
    launched during a test can use the same network.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
guidance Question that needs advice or information.
Projects
None yet
Development

No branches or pull requests

4 participants