Domů Procházet Nápověda
Registrovat se Přihlásit se
lqb
Repozitáře Veřejná aktivita

lqb synced commits to version/4 at lqb/imgproxy from mirror

před 17 hodinami

lqb synced commits to img-61-new-newrelic-api at lqb/imgproxy from mirror

před 17 hodinami

lqb synchronizoval/a novou referenci img-61-new-newrelic-api do lqb/imgproxy ze zrcadla

před 17 hodinami

lqb synced commits to img-34-improve-integration-tests at lqb/imgproxy from mirror

před 17 hodinami

lqb synchronizoval/a novou referenci img-34-improve-integration-tests do lqb/imgproxy ze zrcadla

před 17 hodinami

lqb synced commits to img-14-svg-instance at lqb/imgproxy from mirror

před 17 hodinami

lqb synchronizoval/a novou referenci img-14-svg-instance do lqb/imgproxy ze zrcadla

před 17 hodinami

lqb synced commits to dev at lqb/nginx-ui from mirror

před 1 dnem

lqb synced commits to dev at lqb/open-webui from mirror

před 1 dnem

lqb synced commits to v0.6.32 at lqb/open-webui from mirror

před 1 dnem

lqb synchronizoval/a novou referenci v0.6.32 do lqb/open-webui ze zrcadla

před 1 dnem

lqb synced commits to main at lqb/open-webui from mirror

před 1 dnem

lqb synced commits to dev at lqb/open-webui from mirror

  • d40c710354 refac
  • f65231becb Merge pull request #18040 from rgaricano/dev-FEAT_Vega_Visualizer FEAT: Add Vega-Lite Char Visualizer Renderer
  • 039358e049 FEAT: Add Vega-Lite Char Visualizer Renderer ### FEAT: Add Vega Char Visualizer Renderer Add suport for Vega-Lite Specifications. Vega-Lite is a "compiled" version of Vega Char Visualizer. For be rendered with Vega it have to be compiled. This PR add the check and compile if necessary, is a complement of recent Vega Renderer Feature added.
  • 59929a8d06 refac
  • 9ff6baf7d9 chore
  • Zobrazit porovnání pro tyto 173 revize »

před 1 dnem

lqb synced commits to use-ubuntu24-java-periodic at lqb/elasticsearch from mirror

  • 80d42d03e5 Run java periodic matrix on ubuntu24 - Use adoptopenjdk17 instead of openjdk17
  • 16e1799589 Make resolve conflict in transport version its own task (#134842) (#135487) This commit moves the action for resolving merge conflicts in transport version files a separate task instead of a command line flag to generate.
  • a73bdfb21e Migrate transport version 8841_051 (#135493) (#135551) Backports the following commits to 8.19: - Migrate transport version 8841_051 (#135493)
  • e008d1fe6b [8.19] Correctly apply field path to JSON processor when adding contents to document root (#135479) (#135495) * Correctly apply field path to JSON processor when adding contents to document root (#135479) Processor now correctly uses ingest document methods to obtain field data. --------- Co-authored-by: Joe Gallo <joegallo@gmail.com> * Remove missing test util --------- Co-authored-by: Joe Gallo <joegallo@gmail.com>
  • 19f69a7ca3 [8.19] Fix MergeWithFailureIT (#135523) Wait for the store to be closed, don't assume it happens immediately. Closes #135443
  • Zobrazit porovnání pro tyto 10 revize »

před 1 dnem

lqb synchronizoval/a novou referenci use-ubuntu24-java-periodic do lqb/elasticsearch ze zrcadla

před 1 dnem

lqb synced commits to updatecli_main_ironbank/template at lqb/elasticsearch from mirror

  • 72da17cdac Add option for Append Processor to skip/allow empty values (#105718) * Add option for Append Processor to skip/allow empty values If one is using templates to generate values, this option can be helpful to avoid adding values that resolve into empty strings Fixes #104813 * Change allow_empty_values to ignore_empty_values * Update docs/changelog/105718.yaml * Handle nulls as well The original version of this PR predated `copy_from`, so the value wouldn't have been able to be null here. But now that `copy_from` exists we should handle null as well as empty strings. * Rewrite setFieldValue in terms of valueNotEmpty Since it handles nulls now, this logic is identical. * Rewrite another setFieldValue arity, too This one is a bit trickier, so I've lampshaded the surprising part with a comment, and also there's a newly added test on main via * Verify an invariant This arity of setFieldValue doesn't handle the single-value ignore_empty_value case (like in a set processor), it only handles the multi-value ignore_empty_values case (like in an append processor). The same thing applies to allow_duplicates, that is also an append-only concern. * This test can't handle nulls anymore * Fix a typo * Declare these once and don't use the return value from processor.execute * Add some empty values into this test * Ignore empty values with getFieldValue and copy_from * Re-add the ignore_empty_values docs * It seems conventional to just label these '9.2' * Add an example * Better quoting * Add a test-only feature * Add some rest tests * Fix typos --------- Co-authored-by: Joe Gallo <joegallo@gmail.com>
  • 23e834934c Enable write load constraint decider via feature flag (#135246)
  • d7b7666959 Add back resetting transport upper bounds (#135322) When upper bounds files have been incorrectly modified, or changes to them are no longer needed, transport version generation should rebuild the upper bound. This commit adds back the ability to reset the upper bound files in these cases and adds scanning for the latest within a branch to find the appropriate id for a given upper bound file.
  • 035c48fc62 Mute org.elasticsearch.xpack.test.rest.XPackRestIT test {p0=esql/60_usage/Basic ESQL usage output (telemetry) snapshot version} #135584
  • e9c2510048 Only disable unlicensed pattern_text templating when mapper is used (#135561) Currently we always set the `index.mapping.pattern_text.disable_templating` setting for every standard-mode index. This is a bit excessive, so this PR updates the logic to only include the setting if pattern_text field mappers are in use.
  • Zobrazit porovnání pro tyto 93 revize »

před 1 dnem

lqb synced commits to updatecli_main_9bc32f73c7425e5d7d6a3e394780b3da48a426b42465b81f2ee642f0d3fe10e3 at lqb/elasticsearch from mirror

  • 5416085290 chore: deps(updatecli): bump "ghcr.io/updatecli/policies/autodiscover... ... y/updatecli" policy to 0.9.1 Made with ❤️️ by updatecli
  • 72da17cdac Add option for Append Processor to skip/allow empty values (#105718) * Add option for Append Processor to skip/allow empty values If one is using templates to generate values, this option can be helpful to avoid adding values that resolve into empty strings Fixes #104813 * Change allow_empty_values to ignore_empty_values * Update docs/changelog/105718.yaml * Handle nulls as well The original version of this PR predated `copy_from`, so the value wouldn't have been able to be null here. But now that `copy_from` exists we should handle null as well as empty strings. * Rewrite setFieldValue in terms of valueNotEmpty Since it handles nulls now, this logic is identical. * Rewrite another setFieldValue arity, too This one is a bit trickier, so I've lampshaded the surprising part with a comment, and also there's a newly added test on main via * Verify an invariant This arity of setFieldValue doesn't handle the single-value ignore_empty_value case (like in a set processor), it only handles the multi-value ignore_empty_values case (like in an append processor). The same thing applies to allow_duplicates, that is also an append-only concern. * This test can't handle nulls anymore * Fix a typo * Declare these once and don't use the return value from processor.execute * Add some empty values into this test * Ignore empty values with getFieldValue and copy_from * Re-add the ignore_empty_values docs * It seems conventional to just label these '9.2' * Add an example * Better quoting * Add a test-only feature * Add some rest tests * Fix typos --------- Co-authored-by: Joe Gallo <joegallo@gmail.com>
  • 23e834934c Enable write load constraint decider via feature flag (#135246)
  • d7b7666959 Add back resetting transport upper bounds (#135322) When upper bounds files have been incorrectly modified, or changes to them are no longer needed, transport version generation should rebuild the upper bound. This commit adds back the ability to reset the upper bound files in these cases and adds scanning for the latest within a branch to find the appropriate id for a given upper bound file.
  • 035c48fc62 Mute org.elasticsearch.xpack.test.rest.XPackRestIT test {p0=esql/60_usage/Basic ESQL usage output (telemetry) snapshot version} #135584
  • Zobrazit porovnání pro tyto 92 revize »

před 1 dnem

lqb synced commits to renovate/main-docker.elastic.co-elasticsearch-elasticsearch-9.x at lqb/elasticsearch from mirror

  • 12c62be4e9 [CI] Update transport version definitions

před 1 dnem

lqb synced commits to renovate/9.1-wolfi-versioned at lqb/elasticsearch from mirror

  • 186e4f1d84 Update wolfi (versioned)
  • 90ee222e7e [9.1] Defer Semantic Text Failures on Pre-8.11 Indices (#135845) (#135869) * Defer Semantic Text Failures on Pre-8.11 Indices (#135845) (cherry picked from commit 66d924132c186333ec4f2232b170d0437974af58) # Conflicts: # server/src/test/java/org/elasticsearch/index/mapper/vectors/DenseVectorFieldMapperTests.java # x-pack/plugin/inference/src/main/java/org/elasticsearch/xpack/inference/mapper/SemanticTextFieldMapper.java * [CI] Auto commit changes from spotless * Update comment --------- Co-authored-by: elasticsearchmachine <infra-root+elasticsearchmachine@elastic.co>
  • 57155e1c81 Migrate transport versions 9108_000 through 9086_000 (#135819) (#135853) Note some versions in between have already been migrated. ES-12334
  • 5377b9bbcb Use lowercase sort order in geo_line YAML tests (#135690) (#135840) This is how it's specified in the Elasticsearch specification, and avoids a false positive during validation.
  • 8a98dc0daf Fix KQL case-sensitivity for keyword fields in ES|QL (#135776) (#135782)
  • Zobrazit porovnání pro tyto 10 revize »

před 1 dnem

lqb synchronizoval/a novou referenci renovate/9.1-wolfi-versioned do lqb/elasticsearch ze zrcadla

před 1 dnem