[pull] master from grafana:master #111
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.29.0 to 0.31.0. - [Commits](golang/crypto@v0.29.0...v0.31.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
Quite a lot of gosec ones about integers under/overflows - I tried to fix the ones that weren't problematic, but there were quite a lot.
Bumps the golangx group with 1 update in the / directory: [golang.org/x/net](https://github.com/golang/net). Updates `golang.org/x/net` from 0.31.0 to 0.32.0 - [Commits](golang/net@v0.31.0...v0.32.0) --- updated-dependencies: - dependency-name: golang.org/x/net dependency-type: direct:production update-type: version-update:semver-minor dependency-group: golangx ... Signed-off-by: dependabot[bot] <[email protected]>
See #4107 for contextcheck Revive also doesn't make as much sense for code that is not supposed to be used directly by third parties, especially given the size of the API.
Merge browser in k6
ubuntu-latest become ubuntu-24.04 and this breaks browser tests for some reason.
It seems like quite a lot of tests are not passing on windows. Unfortunately given the volume fixing them right now seems unlikely. So I opened #4118 This tests have not been ran on windows it seems ever, before the move of the codebase to core.
* Introduces --json flag for k6 version sub-command * Align terms with registry * Moving version related logic to cmd * Ensure that extension version match before grouping * Simplify JSON details marshaling
* Report usages of the deprecated 'ext.loadimpact' option * Align the report with existing keys --------- Co-authored-by: Oleg Bespalov <[email protected]>
…d run (#4092) * Create test run before starting output.Cloud * Create the cloud test run earlier * Cloud local execution creates the test run before delegating * Move the cloud test run creation into the test configuration * Keep the compatibility w/old behavior in Cloud output * Remove the Cloud-specific handling code of the cloud local execution * Apply suggestions from code review Co-authored-by: Oleg Bespalov <[email protected]> --------- Co-authored-by: Oleg Bespalov <[email protected]>
* Add release notes for v0.57.0 --------- Co-authored-by: ankur22 <[email protected]> Co-authored-by: Oleg Bespalov <[email protected]> Co-authored-by: oleiade <[email protected]> Co-authored-by: Mihail Stoykov <[email protected]> Co-authored-by: codebien <[email protected]> Co-authored-by: Daniel González Lopes <[email protected]> Co-authored-by: Joan López de la Franca Beltran <[email protected]> Co-authored-by: Heitor Tashiro Sergent <[email protected]>
Merge Prometheus remote write output
Previously the reject of the promise was happening on the event loop, but the argument which is a TypeError was created off it in a goroutine. The goroutine isn't really needed, so the code is somewhat simplified and handling more corner cases.
This will cover most cases, but we can still improve it later. It feels safer to fallback to a 256-color scheme rather than enabling TrueColor from the get go.
The test is testing how constant arrival rate is starting iterations over time. But it used time.Sleep of 1 second which means that it doesn't actually check every second it checks and then it waits for 1 second and then again. This seems to move enough, especially on windows, that it sometimes fails. This PR uses time.Ticker to make it check every second, making it more likely that it won't drift.
* Avoid hardcoding signtool path in package-windows build step Closes #4105 * Move signtool.exe fetching into package-windows step * Add ampersand so pwsh calls signtool * Comment out unnecessary steps for testing * Revert changes needed for testing build
Bumps the golangx group with 3 updates in the / directory: [golang.org/x/crypto](https://github.com/golang/crypto), [golang.org/x/net](https://github.com/golang/net) and [golang.org/x/time](https://github.com/golang/time). Updates `golang.org/x/crypto` from 0.32.0 to 0.33.0 - [Commits](golang/crypto@v0.32.0...v0.33.0) Updates `golang.org/x/net` from 0.34.0 to 0.35.0 - [Commits](golang/net@v0.34.0...v0.35.0) Updates `golang.org/x/sync` from 0.10.0 to 0.11.0 - [Commits](golang/sync@v0.10.0...v0.11.0) Updates `golang.org/x/term` from 0.28.0 to 0.29.0 - [Commits](golang/term@v0.28.0...v0.29.0) Updates `golang.org/x/time` from 0.9.0 to 0.10.0 - [Commits](golang/time@v0.9.0...v0.10.0) Updates `golang.org/x/sys` from 0.29.0 to 0.30.0 - [Commits](golang/sys@v0.29.0...v0.30.0) Updates `golang.org/x/text` from 0.21.0 to 0.22.0 - [Release notes](https://github.com/golang/text/releases) - [Commits](golang/text@v0.21.0...v0.22.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-type: direct:production update-type: version-update:semver-minor dependency-group: golangx - dependency-name: golang.org/x/net dependency-type: direct:production update-type: version-update:semver-minor dependency-group: golangx - dependency-name: golang.org/x/sync dependency-type: direct:production update-type: version-update:semver-minor dependency-group: golangx - dependency-name: golang.org/x/term dependency-type: direct:production update-type: version-update:semver-minor dependency-group: golangx - dependency-name: golang.org/x/time dependency-type: direct:production update-type: version-update:semver-minor dependency-group: golangx - dependency-name: golang.org/x/sys dependency-type: indirect update-type: version-update:semver-minor dependency-group: golangx - dependency-name: golang.org/x/text dependency-type: indirect update-type: version-update:semver-minor dependency-group: golangx ... Signed-off-by: dependabot[bot] <[email protected]>
…d311f111a build(deps): bump the golangx group across 1 directory with 7 updates
Bumps [github.com/evanw/esbuild](https://github.com/evanw/esbuild) from 0.24.2 to 0.25.0. - [Release notes](https://github.com/evanw/esbuild/releases) - [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md) - [Commits](evanw/esbuild@v0.24.2...v0.25.0) --- updated-dependencies: - dependency-name: github.com/evanw/esbuild dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Bump buf.build/prometheus * Move buf.build/prom to direct deps block
…#4554) Bumps the googles group with 1 update in the / directory: [google.golang.org/grpc](https://github.com/grpc/grpc-go). Updates `google.golang.org/grpc` from 1.69.4 to 1.70.0 - [Release notes](https://github.com/grpc/grpc-go/releases) - [Commits](grpc/grpc-go@v1.69.4...v1.70.0) Updates `google.golang.org/genproto/googleapis/api` from 0.0.0-20241015192408-796eee8c2d53 to 0.0.0-20241202173237-19429a94021a - [Commits](https://github.com/googleapis/go-genproto/commits) Updates `google.golang.org/genproto/googleapis/rpc` from 0.0.0-20241015192408-796eee8c2d53 to 0.0.0-20241202173237-19429a94021a - [Commits](https://github.com/googleapis/go-genproto/commits) --- updated-dependencies: - dependency-name: google.golang.org/grpc dependency-type: direct:production update-type: version-update:semver-minor dependency-group: googles - dependency-name: google.golang.org/genproto/googleapis/api dependency-type: indirect update-type: version-update:semver-patch dependency-group: googles - dependency-name: google.golang.org/genproto/googleapis/rpc dependency-type: indirect update-type: version-update:semver-patch dependency-group: googles ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
It changes the default path for the config file from the legacy $HOME/loadimpact/ directory to an owner's agnostic $HOME/k6/.
Co-authored-by: Oleg Bespalov <[email protected]>
Co-authored-by: Oleg Bespalov <[email protected]>
* Add request to the PageOnEvent type
This is where the request will be set for the page.on handler to read.
* Add a new page on request event
* Add a onRequest method
This method is to be called when a new request is about to be sent
from chrome to the WuT. It takes the request and send it to the page.on
handler where the user test script can read the request data from.
* Add call to onRequest from network manager
* Update the page on mapping with the request event
* Refactor metricInterceptor to eventInterceptor
* Fix request.Timing
This is a temporary fix.
When working with page.on('request') the timing values haven't yet been
received, which are part of the response object. This will need to be
fixed later when we can wait for a response while working with
page.on('request').
* Add a test for page.on('request')
* Remove call to Body.Close() from server
* Refactor test to work with tb.url
* Refactor test to reduce boilerplate code
The issue was that HeadersArray was out of order. If they're put in
order then the comparison can be made.
* Refactor test to work with slices.IndexFunc
This is to use it from the mapping layer.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )