build(deps): bump vite from 7.0.4 to 7.1.7 in /app/vmui/packages/vmui #3
Conversation
This file contains hidden or 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
…fixes (VictoriaMetrics#630) Co-authored-by: Aliaksandr Valialkin <[email protected]>
… sockets SOCK_DGRAM Unix sockets must have unixgram network type instead of unixpacket network type. Updates VictoriaMetrics#570
This placeholder matches any word (see https://docs.victoriametrics.com/victorialogs/logsql/#word for word definition) or any quoted string put into single quoted, double quotes or backticks.
… and grep with VictoriaLogs at the "resource efficiency" point
…and SIEM use cases
…pipes after the `sort` pipe Optimize the following cases: - "sort ... | offset 0" -> "sort ..." - "sort ... | limit 0" -> "limit 0" - "sort ... offset N | offset M" -> "sort ... offset N+M" - "sort ... offset N limit M | offset X" -> "sort ... offset N+X limit M-X" This is a follow-up for 81a5cf2 Updates VictoriaMetrics#634 Updates VictoriaMetrics#620
…pes() when the query has zero local pipes Add tests for the splitQueryToRemoteAndLocal() function for all the supported pipes. Updates VictoriaMetrics#52
…ining columns by name is needed at ProcessFacetsRequest() Updates VictoriaMetrics#648 Updates VictoriaMetrics#651 This is a follow-up for 2163794
Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…s from pushing down the remaining pipes to vlstorage This prevents from the proper optimization for selecting last N logs. See VictoriaMetrics#620 (comment)
…calculating hits at the /select/logsql/hits endpoint See VictoriaMetrics#641 Thanks to @func25 for the initial pull request at VictoriaMetrics#644
…select/logsql/hits The `join` pipe doesn't drop or modify _time field, so it is safe to use during log hits' calculations. See VictoriaMetrics#641
…safeForHits() There is no need in mentioning a special case for union() pipe, for join() pipe and any other pipe exceptions, which are going to be added in the future, since this is superflouos information, which can become outdated or misleading over time. This is a follow-up for fb6dafb Updates VictoriaMetrics#641
… into TestParseQuery_OptimizeOffsetLimitPipes This is a follow-up for faadf97 Updates VictoriaMetrics#642
…ipe combinations - Merge '| limit X | limit Y' into '| limit min(X, Y)' - Merge '| offset X | offset Y' into 'offset X+Y' - Replace '| limit X | offset Y' with 'limit 0' if Y >= X This is a follow-up for faadf97
…toriaMetrics#639) Co-authored-by: Aliaksandr Valialkin <[email protected]>
- Make the changelog entry more user-readable. - Add the description for the -storageNode.usernameFile command-line flag to the list of command-line flags at https://docs.victoriametrics.com/victorialogs/#list-of-command-line-flags Updates VictoriaMetrics#459 Updates VictoriaMetrics#685
Reason for revert: this functionality is non-trivial, so it needs additional maintenance efforts in the future. This functionality is non-core for VictoriaLogs web UI (aka 'nice to have feature'). It is already provided by vmalert web UI ( https://docs.victoriametrics.com/victoriametrics/vmalert/#web ). I doubt we'll have enough capacity for providing high-quiality maintenance for this functionality. It is better to revert it instead of providing half-baked functionality for our users. Updates VictoriaMetrics#522 Updates VictoriaMetrics/VictoriaMetrics#8989 Updates VictoriaMetrics#5
…D headers are set by proxy or remove it completely (VictoriaMetrics#664)" This reverts commit 97ffbff. Reason for revert: this functionality depends on the commit 2d4b343 , which is going to be reverted. The reason for reverting the 2d4b343 is that it mixes multiple unrelated features in a single commit. This functionality must be implemented in a distinct pull request dedicated solely for this functionality at both VictoriaLogs server side and VictoriaLogs web UI. Updates VictoriaMetrics#664 Updates VictoriaMetrics#5 Updates VictoriaMetrics#656
…ct/vmalert requests to VMAlert (#5)" This reverts commit 2d4b343. Reason for revert: this commit mixes two unrelated features: - Proxying vmalert requests ( VictoriaMetrics#90 ) - Introducing vmui config handler at /select/vmui/config.json ( there should be a separate feature request with the explanation why this handler is needed ) - Returning AccountID and ProjectID response headers ( VictoriaMetrics#656 ) It is better from the maintenance and git history investigation PoV to split the implementation of these features into separate pull requests. This commit also has a few issues in the code, which must be addressed in the follow-up pull requests: - The description of the `-vmalert.proxyURL` command-line flag misses a whitespace between the `vmalert.` and `See`. - The description of the `-vmalert.proxyURL` command-line flag contains non-canonical link to docs - https://docs.victoriametrics.com/victorialogs#vmalert . It must be https://docs.victoriametrics.com/victorialogs/#vmalert - The `r.URL.Path = strings.TrimPrefix(path, "/select")` line isn't needed in the code block, which returns vmui config to the client. Updates VictoriaMetrics#5
…heir number differs from the current concurrency level This case is possible if the remote side has different concurrency level (for example, because of the limit on the number of CPU cores). Updates VictoriaMetrics#682
…ders to use during query execution This option may help increasing query performance on storage systems with high read latencies such as NFS, Ceph or S3. Set the default value for concurrent readers to 2*NumCPU, where NumCPU is the number of available CPU cores. This should mask read IO latency for typical HDD-based and SSD-based storage systems. See https://docs.victoriametrics.com/victorialogs/logsql/#concurrent_readers-query-option for details.
…query option in the `Performance tips` chapter This is a follow-up for be7d05b
…ntUniqProcessor and statsCountUniqHashProcessor These tests cover the logic implemented in the commit 5283603 Updates VictoriaMetrics#682
…:[start, end]` filter at Query.addTimeFilterNoSubqueries(), using string representation with nanosecond precision Previously the boundaries were formatted there as numeric values. This could lead to improper parsing of such boundaries at the vlstorage side: - Negative numbers could be imporperly parsed as timestamps relative to the current time. - Numbers with less than 15 decimal digits could be improperly parsed as microseconds, milliseconds or seconds instead of nanoseconds. This could lead to incorrect `lastN` optimization at getLastNQueryResults() function, which is triggered when `limit=N` query arg is passed to `/select/logsql/query`. This optimization uses binary search on the _time filter in order to find the time range with the last N logs for the given query. This optimization could put negative values to `_time:[start, end]` filter. These values were improperly parsed at the vlstorage side in cluster version of VictoriaLogs, which could lead to unexpected results. The issue didn't trigger in single-node VictoriaLogs, since the `[start, end]` string representation of the time filter wasn't parsed here - instead, maxTimestamp and minTimestamp values from the filterTime struct were used directly. These values were set to correct values ad the Query.addTimeFilterNoSubqueries(). Updates VictoriaMetrics#587
It has been appeared that waiting for all the responses from all the vlstorage nodes may signficantly slow down returning the last N logs for the given query on the given time range, since the query performance becomes always limited by the slowest vlstorage nodes. Previously the fastest vlstorage nodes could return more than 2*N logs, which will immediately trigger cancelation of requests to the remaining slower vlstorage nodes. Return back the previous algorithm - e.g. do not wait for all the responses from all the vlstorage nodes. Instead, start processing the responses as soon as they are returned by different vlstorage nodes in an independent way. This approach has a drawback - when the error is triggered by slower vlstorage nodes after the faster vlstorage nodes start returning the response, then this error is returned back to the client after some query results were already returned to the client. This is still better comparing to the `last N` query slowdown, since this should be very rare event. See VictoriaMetrics#72 (comment)
… logs when the time range is smaller than a few seconds The binary search over a small time range such as a few seconds requires ~30 iterations until it converges to nanosecond precision. Such small time ranges usually contain small number of logs even on highly loaded systems with hundreds of thousands of logs ingested per second. So it is faster to run the query with the `| sort by (_time desc) limit N` pipe at the end on this time range instead of running ~30 iterations for the binary search. This shaves off more than a half of iterations for the binary search in typical production cases, and improves the `last N logs` query performance by ~2x on average (e.g. when the limit=N query arg is passed to /select/logsql/query). Thanks to @yuriydzobak for the comment at VictoriaMetrics#72 (comment) , which helped identifying and lifting this performance bottleneck.
… the `allow_partial_response` query option docs
…erying docs at the `High availability` chapter
…eld values at `facets` pipe
…)` filters to LogsQL
These filters can be used as faster alternatives to `i()` filter.
For example, `contains_common_case("Error")` matches log messages with at least one of the following words:
- Error
- error
- ERROR
While `equals_common_case("VictoriaLogs")` matches log messages equal to one of the following words:
- VictoriaLogs
- victorialogs
- VICTORIALOGS
- Victorialogs
- victoriaLogs
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 7.0.4 to 7.1.7. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v7.1.7/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 7.1.7 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
sagar-gharte
force-pushed
the
master
branch
from
a8358c0 to
fbce6b1
Compare
Author
|
A newer version of vite exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
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.
Bumps vite from 7.0.4 to 7.1.7.
Release notes
Sourced from vite's releases.
... (truncated)
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
693d255release: v7.1.798a3484fix(hmr): wait forimport.meta.hot.prunecallbacks to complete before runni...9f32b1dfix(hmr): trigger prune event when import is removed from non hmr module (#20...9f2247cfix(deps): update all non-major dependencies (#20811)105abe8fix(glob): handle glob imports from folders starting with dot (#20800)4c4583cfix(build): fix ssr environmentemitAssets: truewhen `sharedConfigBuild: t...9bc9d12fix(client): use CSP nonce when rendering error overlay (#20791)54377f7release: v7.1.688af2aefix(deps): update all non-major dependencies (#20773)d785e72chore(deps): update rolldown-related dependencies (#20772)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vite since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.