chore: Configure Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

deps/swc/Cargo.toml (cargo)
deps/swc/bindings/Cargo.toml (cargo)
deps/swc/bindings/binding_core_node/Cargo.toml (cargo)
deps/swc/bindings/binding_core_wasm/Cargo.toml (cargo)
deps/swc/bindings/binding_html_node/Cargo.toml (cargo)
deps/swc/bindings/binding_minifier_node/Cargo.toml (cargo)
deps/swc/bindings/binding_minifier_wasm/Cargo.toml (cargo)
deps/swc/bindings/binding_typescript_wasm/Cargo.toml (cargo)
deps/swc/bindings/node_macro_deps/Cargo.toml (cargo)
deps/swc/bindings/swc_cli/Cargo.toml (cargo)
deps/swc/xtask/Cargo.toml (cargo)
.github/workflows/audit.yml (github-actions)
.github/workflows/ci.yml (github-actions)
.github/workflows/release.yml (github-actions)
.github/workflows/scorecard.yml (github-actions)
.github/workflows/update-swc.yml (github-actions)
deps/swc/bindings/binding_core_wasm/example/package.json (npm)
deps/swc/bindings/binding_core_wasm/package.json (npm)
deps/swc/bindings/binding_minifier_wasm/package.json (npm)
deps/swc/bindings/binding_typescript_wasm/package.json (npm)
lib/package.json (npm)
package.json (npm)
.nvmrc (nvm)

Configuration Summary
Based on the default config's presets, Renovate will:

Start dependency updates only once this onboarding PR is merged
Enable Renovate Dependency Dashboard creation.
Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
Group known monorepo packages together.
Use curated list of recommended non-monorepo package groupings.
Apply crowd-sourced package replacement rules.
Apply crowd-sourced workarounds for known problems with packages.
Show all Merge Confidence badges for pull requests.
Run Renovate on following schedule: on monday

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

What to Expect
With your current configuration, Renovate will create 74 Pull Requests:

chore(deps): update rust crate lexical to v7 [security]

Branch name: renovate/major-vulnerabilityalerts
Merge into: main
Upgrade lexical to 7.0.0

chore(deps): replace dependency npm-run-all with npm-run-all2 ^5.0.0

Schedule: ["on monday"]
Branch name: renovate/npm-run-all-replacement
Merge into: main
Upgrade npm-run-all to ^5.0.0

chore(deps): update github/codeql-action action to v3.27.9

Schedule: ["on monday"]
Branch name: renovate/github-codeql-action-3.27.x
Merge into: main
Upgrade github/codeql-action to df409f7d9260372bd5f19e5b04e83cb3c43714ae

chore(deps): update rust crate allocator-api2 to v0.2.21

Schedule: ["on monday"]
Branch name: renovate/allocator-api2-0.2.x-lockfile
Merge into: main
Upgrade allocator-api2 to 0.2.21

chore(deps): update rust crate anyhow to v1.0.94

Schedule: ["on monday"]
Branch name: renovate/anyhow-1.0.x-lockfile
Merge into: main
Upgrade anyhow to 1.0.94

chore(deps): update rust crate assert_cmd to v2.0.16

Schedule: ["on monday"]
Branch name: renovate/assert_cmd-2.0.x-lockfile
Merge into: main
Upgrade assert_cmd to 2.0.16

chore(deps): update rust crate assert_fs to v1.1.2

Schedule: ["on monday"]
Branch name: renovate/assert_fs-1.1.x-lockfile
Merge into: main
Upgrade assert_fs to 1.1.2

chore(deps): update rust crate chrono to v0.4.39

Schedule: ["on monday"]
Branch name: renovate/chrono-0.4.x-lockfile
Merge into: main
Upgrade chrono to 0.4.39

chore(deps): update rust crate crossbeam-queue to v0.3.12

Schedule: ["on monday"]
Branch name: renovate/crossbeam-queue-0.3.x-lockfile
Merge into: main
Upgrade crossbeam-queue to 0.3.12

chore(deps): update rust crate flate2 to v1.0.35

Schedule: ["on monday"]
Branch name: renovate/flate2-1.0.x-lockfile
Merge into: main
Upgrade flate2 to 1.0.35

chore(deps): update rust crate lightningcss to v1.0.0-alpha.61

Schedule: ["on monday"]
Branch name: renovate/lightningcss-1.0.x-lockfile
Merge into: main
Upgrade lightningcss to 1.0.0-alpha.61

chore(deps): update rust crate napi-build to v2.1.4

Schedule: ["on monday"]
Branch name: renovate/napi-build-2.1.x-lockfile
Merge into: main
Upgrade napi-build to 2.1.4

chore(deps): update rust crate napi-derive to v2.16.13

Schedule: ["on monday"]
Branch name: renovate/napi-derive-2.16.x-lockfile
Merge into: main
Upgrade napi-derive to 2.16.13

chore(deps): update rust crate pathdiff to v0.2.3

Schedule: ["on monday"]
Branch name: renovate/pathdiff-0.2.x-lockfile
Merge into: main
Upgrade pathdiff to 0.2.3

chore(deps): update rust crate pretty_assertions to v1.4.1

Schedule: ["on monday"]
Branch name: renovate/pretty_assertions-1.4.x-lockfile
Merge into: main
Upgrade pretty_assertions to 1.4.1

chore(deps): update rust crate proc-macro2 to v1.0.92

Schedule: ["on monday"]
Branch name: renovate/proc-macro2-1.0.x-lockfile
Merge into: main
Upgrade proc-macro2 to 1.0.92

chore(deps): update rust crate quote to v1.0.37

Schedule: ["on monday"]
Branch name: renovate/quote-1.0.x-lockfile
Merge into: main
Upgrade quote to 1.0.37

chore(deps): update rust crate relative-path to v1.9.3

Schedule: ["on monday"]
Branch name: renovate/relative-path-1.9.x-lockfile
Merge into: main
Upgrade relative-path to 1.9.3

chore(deps): update rust crate rkyv to v0.8.9

Schedule: ["on monday"]
Branch name: renovate/rkyv-0.8.x-lockfile
Merge into: main
Upgrade rkyv to 0.8.9

chore(deps): update rust crate ryu-js to v1.0.1

Schedule: ["on monday"]
Branch name: renovate/ryu-js-1.0.x-lockfile
Merge into: main
Upgrade ryu-js to 1.0.1

chore(deps): update rust crate semver to v1.0.24

Schedule: ["on monday"]
Branch name: renovate/semver-1.0.x-lockfile
Merge into: main
Upgrade semver to 1.0.24

chore(deps): update rust crate serde_json to v1.0.133

Schedule: ["on monday"]
Branch name: renovate/serde_json-1.0.x-lockfile
Merge into: main
Upgrade serde_json to 1.0.133

chore(deps): update rust crate sourcemap to v9.0.1

Schedule: ["on monday"]
Branch name: renovate/sourcemap-9.0.x-lockfile
Merge into: main
Upgrade sourcemap to 9.0.1

chore(deps): update rust crate swc_core to v9.0.2

Schedule: ["on monday"]
Branch name: renovate/patch-swc-monorepo
Merge into: main
Upgrade swc_core to 9.0.2

chore(deps): update rust crate syn to v2.0.90

Schedule: ["on monday"]
Branch name: renovate/syn-2.0.x-lockfile
Merge into: main
Upgrade syn to 2.0.90

chore(deps): update rust crate url to v2.5.4

Schedule: ["on monday"]
Branch name: renovate/url-2.5.x-lockfile
Merge into: main
Upgrade url to 2.5.4

chore(deps): update rust crate vergen to v9.0.2

Schedule: ["on monday"]
Branch name: renovate/vergen-9.0.x-lockfile
Merge into: main
Upgrade vergen to 9.0.2

chore(deps): update rust crate wasmer to v5.0.4

Schedule: ["on monday"]
Branch name: renovate/wasmer-5.0.x-lockfile
Merge into: main
Upgrade wasmer to 5.0.4

chore(deps): update rust-wasm-bindgen monorepo (patch)

Schedule: ["on monday"]
Branch name: renovate/patch-rust-wasm-bindgen-monorepo
Merge into: main
Upgrade js-sys to 0.3.76
Upgrade wasm-bindgen to 0.2.99
Upgrade wasm-bindgen-futures to 0.4.49

chore(deps): update serde monorepo to v1.0.216 (patch)

Schedule: ["on monday"]
Branch name: renovate/patch-serde-monorepo
Merge into: main
Upgrade serde to 1.0.216
Upgrade serde_derive to 1.0.216

chore(deps): update step-security/harden-runner action to v2.10.2

Schedule: ["on monday"]
Branch name: renovate/step-security-harden-runner-2.10.x
Merge into: main
Upgrade step-security/harden-runner to 0080882f6c36860b6ba35c610c98ce87d4e2f26f

chore(deps): update tokio-tracing monorepo (patch)

Schedule: ["on monday"]
Branch name: renovate/patch-tokio-tracing-monorepo
Merge into: main
Upgrade tracing to 0.1.41
Upgrade tracing-subscriber to 0.3.19

fix(deps): update rust crate clap to v4.5.23

Schedule: ["on monday"]
Branch name: renovate/patch-all-patch-patch
Merge into: main
Upgrade clap to 4.5.23

chore(deps): update actions/upload-artifact action to v4.5.0

Schedule: ["on monday"]
Branch name: renovate/actions-upload-artifact-4.x
Merge into: main
Upgrade actions/upload-artifact to 6f51ac03b9356f520e9adb1b1b7802705f340c2b

chore(deps): update docker/setup-buildx-action action to v3.8.0

Schedule: ["on monday"]
Branch name: renovate/docker-setup-buildx-action-3.x
Merge into: main
Upgrade docker/setup-buildx-action to 6524bf65af31da8d45b59e8c27de4bd072b392f5

chore(deps): update github/codeql-action action to v3.28.0

Schedule: ["on monday"]
Branch name: renovate/github-codeql-action-3.x
Merge into: main
Upgrade github/codeql-action to 48ab28a6f5dbc2a99bf1e0131198dd8f1df78169

chore(deps): update minor updates (minor)

Schedule: ["on monday"]
Branch name: renovate/all-minor-updates
Merge into: main
Upgrade @biomejs/biome to 1.9.4
Upgrade esbuild to ^0.24.0

chore(deps): update rust crate arbitrary to v1.4.1

Schedule: ["on monday"]
Branch name: renovate/arbitrary-1.x-lockfile
Merge into: main
Upgrade arbitrary to 1.4.1

chore(deps): update rust crate base64 to 0.22.0

Schedule: ["on monday"]
Branch name: renovate/base64-0.x
Merge into: main
Upgrade base64 to 0.22.0

chore(deps): update rust crate browserslist-rs to 0.17.0

Schedule: ["on monday"]
Branch name: renovate/browserslist-rs-0.x
Merge into: main
Upgrade browserslist-rs to 0.17.0

chore(deps): update rust crate cargo_metadata to 0.19.0

Schedule: ["on monday"]
Branch name: renovate/cargo_metadata-0.x
Merge into: main
Upgrade cargo_metadata to 0.19.0

chore(deps): update rust crate changesets to 0.3.0

Schedule: ["on monday"]
Branch name: renovate/changesets-0.x
Merge into: main
Upgrade changesets to 0.3.0

chore(deps): update rust crate codspeed-criterion-compat to v2.7.2

Schedule: ["on monday"]
Branch name: renovate/codspeed-criterion-compat-2.x-lockfile
Merge into: main
Upgrade codspeed-criterion-compat to 2.7.2

chore(deps): update rust crate dialoguer to 0.11.0

Schedule: ["on monday"]
Branch name: renovate/dialoguer-0.x
Merge into: main
Upgrade dialoguer to 0.11.0

chore(deps): update rust crate hashbrown to 0.15.0

Schedule: ["on monday"]
Branch name: renovate/hashbrown-0.x
Merge into: main
Upgrade hashbrown to 0.15.0

chore(deps): update rust crate indexmap to v2.7.0

Schedule: ["on monday"]
Branch name: renovate/indexmap-2.x-lockfile
Merge into: main
Upgrade indexmap to 2.7.0

chore(deps): update rust crate jsonc-parser to 0.26.0

Schedule: ["on monday"]
Branch name: renovate/jsonc-parser-0.x
Merge into: main
Upgrade jsonc-parser to 0.26.0

chore(deps): update rust crate lru to 0.12.0

Schedule: ["on monday"]
Branch name: renovate/lru-0.x
Merge into: main
Upgrade lru to 0.12.0

chore(deps): update rust crate miette to v7.4.0

Schedule: ["on monday"]
Branch name: renovate/miette-7.x-lockfile
Merge into: main
Upgrade miette to 7.4.0

chore(deps): update rust crate ntest to 0.9.0

Schedule: ["on monday"]
Branch name: renovate/ntest-0.x
Merge into: main
Upgrade ntest to 0.9.0

chore(deps): update rust crate once_cell to v1.20.2

Schedule: ["on monday"]
Branch name: renovate/once_cell-1.x-lockfile
Merge into: main
Upgrade once_cell to 1.20.2

chore(deps): update rust crate regex to v1.11.1

Schedule: ["on monday"]
Branch name: renovate/regex-1.x-lockfile
Merge into: main
Upgrade regex to 1.11.1

chore(deps): update rust crate reqwest to 0.12.0

Schedule: ["on monday"]
Branch name: renovate/reqwest-0.x
Merge into: main
Upgrade reqwest to 0.12.0

chore(deps): update rust crate serde-wasm-bindgen to 0.6.0

Schedule: ["on monday"]
Branch name: renovate/serde-wasm-bindgen-0.x
Merge into: main
Upgrade serde-wasm-bindgen to 0.6.0

chore(deps): update rust crate sourcemap to v9.1.2

Schedule: ["on monday"]
Branch name: renovate/sourcemap-9.x-lockfile
Merge into: main
Upgrade sourcemap to 9.1.2

chore(deps): update rust crate tempfile to v3.14.0

Schedule: ["on monday"]
Branch name: renovate/tempfile-3.x-lockfile
Merge into: main
Upgrade tempfile to 3.14.0

chore(deps): update rust crate tokio to v1.42.0

Schedule: ["on monday"]
Branch name: renovate/tokio-1.x-lockfile
Merge into: main
Upgrade tokio to 1.42.0

chore(deps): update rust crate tracing-chrome to 0.7.0

Schedule: ["on monday"]
Branch name: renovate/tracing-chrome-0.x
Merge into: main
Upgrade tracing-chrome to 0.7.0

chore(deps): update rust crate unicode-id-start to v1.3.1

Schedule: ["on monday"]
Branch name: renovate/unicode-id-start-1.x-lockfile
Merge into: main
Upgrade unicode-id-start to 1.3.1

chore(deps): update rust crate unicode-width to 0.2.0

Schedule: ["on monday"]
Branch name: renovate/unicode-width-0.x
Merge into: main
Upgrade unicode-width to 0.2.0

chore(deps): update rust crate virtual-fs to 0.20.0

Schedule: ["on monday"]
Branch name: renovate/virtual-fs-0.x
Merge into: main
Upgrade virtual-fs to 0.20.0

chore(deps): update rust crate wasmer-wasix to 0.34.0

Schedule: ["on monday"]
Branch name: renovate/wasmer-wasix-0.x
Merge into: main
Upgrade wasmer-wasix to 0.34.0

chore(deps): update wagoid/commitlint-github-action action to v6.2.0

Schedule: ["on monday"]
Branch name: renovate/wagoid-commitlint-github-action-6.x
Merge into: main
Upgrade wagoid/commitlint-github-action to 0184f5a228ee06430bb9e67d65f73a1a6767496a

chore(deps): update dependency jest to v29

Schedule: ["on monday"]
Branch name: renovate/major-jest-monorepo
Merge into: main
Upgrade jest to ^29.0.0

chore(deps): update dependency ubuntu to v24

Schedule: ["on monday"]
Branch name: renovate/ubuntu-24.x
Merge into: main
Upgrade ubuntu to 24.04

chore(deps): update dependency webpack to v5

Schedule: ["on monday"]
Branch name: renovate/webpack-5.x
Merge into: main
Upgrade webpack to ^5.0.0

chore(deps): update dependency webpack-cli to v6

Schedule: ["on monday"]
Branch name: renovate/webpack-cli-6.x
Merge into: main
Upgrade webpack-cli to ^6.0.0

chore(deps): update dependency webpack-dev-server to v5

Schedule: ["on monday"]
Branch name: renovate/webpack-dev-server-5.x
Merge into: main
Upgrade webpack-dev-server to ^5.0.0

chore(deps): update rust crate crc to v3

Schedule: ["on monday"]
Branch name: renovate/crc-3.x
Merge into: main
Upgrade crc to 3.0.0

chore(deps): update rust crate dashmap to v6

Schedule: ["on monday"]
Branch name: renovate/dashmap-6.x
Merge into: main
Upgrade dashmap to 6.0.0

chore(deps): update rust crate rustc-hash to v2

Schedule: ["on monday"]
Branch name: renovate/rustc-hash-2.x
Merge into: main
Upgrade rustc-hash to 2.0.0

chore(deps): update rust crate siphasher to v1

Schedule: ["on monday"]
Branch name: renovate/siphasher-1.x
Merge into: main
Upgrade siphasher to 1.0.0

chore(deps): update rust crate sourcemap to v9

Schedule: ["on monday"]
Branch name: renovate/sourcemap-9.x
Merge into: main
Upgrade sourcemap to 9.0.0

chore(deps): update rust crate thiserror to v2

Schedule: ["on monday"]
Branch name: renovate/thiserror-2.x
Merge into: main
Upgrade thiserror to 2.0.0

🚸 Branch creation will be limited to maximum 3 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

This PR has been generated by Renovate Bot.

We have a copy of swc in the source code, we dont want renovate bumping it. Also we already have dependabot in place

A misconfigured personal access token with the right to see public repository triggered this. The token is removed by now.


Authorisation support

Not ready for merging yet, but posting to start discussion.
Authentication can be managed through serverconfig.py (see example).

This is very interesting @jbu! I like the outline. I have a basic issue with how we're doing the actual authorisation though: I think it should be done in the backend, rather than the frontend. I think we should split this out into a separate module, called ga4gh.authz, which has a class called (say) PermissionsManager. In frontend.config, we do something like
permissionsManager = authz.PermissionsManager(app.config["PERMISSIONS"])
theBackend.setPermissionsManager(permissionsManager)

Then, in the backend, we check for authorisation at each of the entry points for the various methods. For example, in getVariantSet we might have:
def getVariantSet(self, id_, userId):
     dataset = self._getDatasetFromCompoundId(id_)
     self._permissionsManager.checkPermissions(userId, dataset)
     return self.runGetRequest(dataset.getVariantSetIdMap(), id_)

The trouble is, there's a bunch of different ways in which we can get the dataset for different queries. The only way we can be sure of getting the authorisation done properly is by doing it after we've parsed the incoming requests and we know its context. I think the backend is probably the right place for this.

Authorization often needs to be done a different levels of the
data hierarchy depending on the project.  Authorization at only
the DataSet level would not work for TCGA, where different files
have different access restrictions and this even changed over
the course of the project.
One can image cases where access restrictions could apply to
ranges of BAM files.  Say access to certain genes is not as
restricted as non-coding regions.
IMHO, authorization will have to permeate down into the depths
of back end eventually.
Jerome Kelleher<EMAIL_ADDRESS>writes:

The trouble is, there's a bunch of different ways in which we can get the
dataset for different queries. The only way we can be sure of getting the
authorisation done properly is by doing it after we've parsed the incoming
requests and we know its context. I think the backend is probably the right
place for this.

I agree @diekhans --- I think the approach I've outlined above should provide the flexibility we need. Part of idea of farming the real work out to the new authz module is to make room for these more complex situations.  By making the backend delegate the actual checking to the authz module, hopefully we'll be able to keep things nice and clean, and also make it all testable.

Closing this PR due to inactivity.


Why are there two requests when I use "network only"

when i use "network only" to get a picture. I find there are two request in Chrome dev tool.

Will this take up network？
I think Just need a network request

This is normal and does not represent an additional network request.
There's background explaining what you see at https://stackoverflow.com/a/33655173/385997


take_split return is not intuitive

take_split() doesn't precise what is returned and implementation do:
fn take_split(&self, count: usize) -> (Self, Self) {
  let (prefix, suffix) = self.split_at(count);
  (suffix, prefix)
}

That really not intuitive when you are expected std nomenclature and it's more logical to return it as std do it. Plus, I think this function should return either a Result or a Option (like std should) to avoid unexpected panic.
Open https://github.com/rust-lang/rust/issues/90410.

I don't think there's an issue with take_split, it's consistent with the rest of nom. Could you avoid opening an issue then immediately opening a PR for an architecture change or new feature without waiting for my opinion? This was not necessary


enh: allow to define request body render style

This PR adds a new property requestBodyRenderStyle in order to allow customizations on the request body section.
My proposal is to have two modes:

splitted mode, which renders two panes, one for the expected schema and other for the body input
default mode, which renders the request section on tabs

The following picture shows the splitted mode render:

thanks this may cause an issue on narrow screen and/or in view mode. in that case they should be stacked.
can you confirm if the UI is responsive and adjusts itself per the screen factor? will be great if  you can post a screenshot


Extensions can't have the same name in ./package.json and ./pkg/<-PKG->/package.json

Extensions can't have the same name in ./package.json and ./pkg/<-PKG->/package.json, otherwise automated build will fail.
Fix this issue and also change the creators package so that the name for the root package.json is given a different name by default.

I don't think changing the creators package is needed...


deps: bump node-libcurl to latest prerelease version

This is related to the following issue:
https://github.com/Kong/insomnia/issues/997
And should unblock this:
https://github.com/Kong/insomnia/issues/1847
Some code is based on the previous PR: https://github.com/Kong/insomnia/pull/1528
Some notes:
Prebuilt binary
node-libcurl has been providing prebuilt binaries for Electron, however the current non-prerelease version, 2.1.1, does not provide binaries for Electron v3. I've added it back starting with 2.1.2-1.
Right now Insomnia is not using the prebuilt binaries, because the project uses electron-rebuild and it does not support node-pre-gyp, I've opened an issue there about adding support: https://github.com/electron/electron-rebuild/issues/367
If support is not added the prebuilt binaries can still be used by changing the bootstrap script on the root package.json to the following:
npm install && lerna bootstrap -- --runtime=electron --target=v3.1.13 --disturl=https://www.electronjs.org/headers && lerna run --parallel --stream bootstrap

And removing the electron-rebuild call from the insomnia-app bootstrap script.
This would simplify Insomnia build as there would be no need to build the native dependencies from source anymore. For the scripts used to build libcurl and their dependencies for node-libcurl itself, see this directory: https://github.com/JCMais/node-libcurl/tree/develop/scripts/ci
If Insomnia still needs to have control over the libcurl build, those environment variables:
https://github.com/Kong/insomnia/blob/8162772dae9ec11333783d9be5c9bd9caf50efd2/.github/workflows/release-core.yml#L49
https://github.com/Kong/insomnia/blob/8162772dae9ec11333783d9be5c9bd9caf50efd2/.github/workflows/release-designer.yml#L49
Must be changed to npm_config_curl_static_build: true, which is the environment variable that would cause the following gyp variable to become true: https://github.com/JCMais/node-libcurl/blob/9aa421d2f39306a6e42afe84afe528164edd44c3/binding.gyp#L11
Curl.getVersionInfoString
Curl class now has a new static method getVersionInfoString, which returns more information than getVersion, it should be almost identical to the output of curl -V:
getVersion:

libcurl/7.69.1-DEV OpenSSL/1.1.1d zlib/1.2.11 WinIDN libssh2/1.9.0_DEV nghttp2/1.40.0

getVersionInfoString:

Version: libcurl/7.69.1-DEV OpenSSL/1.1.1d zlib/1.2.11 WinIDN libssh2/1.9.0_DEV nghttp2/1.40.0
Protocols: dict, file, ftp, ftps, gopher, http, https, imap, imaps, ldap, ldaps, pop3, pop3s, rtsp, scp, sftp, smb, smbs, smtp, smtps, telnet, tftp
Features: AsynchDNS, IDN, IPv6, Largefile, SSPI, Kerberos, SPNEGO, NTLM, SSL, libz, HTTP2, HTTPS-proxy

Just to not introduce that many changes, I've kept the current implementation of the wrapper to use getVersion.
Test actuallySend() › sends a generic request
This test was missing the HTTPAUTH option before, don't know why.
Uncommited files not ignored
After running the project those files were generated:
packages/openapi-2-kong/dist/index.js
packages/openapi-2-kong/dist/index.js.map

And they are not on .gitignore list, should they be added?

And they are not on .gitignore list, should they be added?

I have added them into .gitignore now 😄 #2165

Thanks for kicking off this effort @JCMais! I added a bunch of stuff to this PR and merged it in #2223
Having prebuilt versions for Electron is a life saver 👍

@gschier glad it worked.
I will release a new version of node-libcurl sometime later this week with the changes made on the current pre-release version and a few other improvements.


support sharded graphite using metrics/expand instead of index.json

index.json?cluster=1 is not supported in all infrastructure types, IMHO there should be a fallback if index.json returns [ ] for discovery using metrics/find or metrics/expand as at least the first one works at our setup (I haven't checked the second one yet)

can you explain in which cases index.json?cluster=1  works and in which it doesn't?


VkWriteDescriptorSetAccelerationStructureNV: AccelerationStructures is NULL

const descriptorAccelerationStructureInfo = new VkWriteDescriptorSetAccelerationStructureNV;
descriptorAccelerationStructureInfo.accelerationStructureCount = 1;
descriptorAccelerationStructureInfo.pAccelerationStructures = topAS;

const accelerationStructureWrite  = new VkWriteDescriptorSet;
accelerationStructureWrite.pNext = descriptorAccelerationStructureInfo;
accelerationStructureWrite.dstSet = descriptorSet;
accelerationStructureWrite.dstBinding = 0;
accelerationStructureWrite.dstArrayElement = 0;
accelerationStructureWrite.descriptorCount = 1;
accelerationStructureWrite.descriptorType = VK_DESCRIPTOR_TYPE_ACCELERATION_STRUCTURE_NV;
accelerationStructureWrite.pImageInfo = null;
accelerationStructureWrite.pBufferInfo = null;
accelerationStructureWrite.pTexelBufferView = null;

const descriptorWrites = [accelerationStructureWrite];
vkUpdateDescriptorSets(device, descriptorWrites.length, descriptorWrites, 0, null);

There is error on line 3,  when I call vkUpdateDescriptorSets it fails because pAccelerationStructures is NULL.

Could you also include the code of topAS?

let topAS = new VkAccelerationStructureNV();
let accelerationStructureInfo = VkAccelerationStructureCreateInfoNV;
accelerationStructureInfo.type = VK_ACCELERATION_STRUCTURE_TYPE_TOP_LEVEL_NV;
accelerationStructureInfo.flags = 0;
accelerationStructureInfo.compactedSize = 0;
accelerationStructureInfo.instanceCount = instanceCount;
accelerationStructureInfo.geometryCount = geometryCount;
accelerationStructureInfo.pGeometries = geometries;

vkCreateAccelerationStructureNV(device, accelerationStructureInfo, null, topAS);

Thanks I'm investigating

@Reon90 I think I found the bug, for confirmation could you send me a dump of descriptorAccelerationStructureInfo.memoryBuffer?
Like this:
...
accelerationStructureWrite.pBufferInfo = null;
accelerationStructureWrite.pTexelBufferView = null;

const descriptorWrites = [accelerationStructureWrite];
vkUpdateDescriptorSets(device, descriptorWrites.length, descriptorWrites, 0, null);

console.log(JSON.stringify(Array.from(new Uint8Array(descriptorAccelerationStructureInfo.memoryBuffer))));

Thanks!

I can after several hours.

Thanks, I have pushed https://github.com/maierfelix/nvk/commit/7637a81a6c500c75a392c8d05da7cd284739a99d which should fix this issue - could you check?

@Reon90 Thank you, was fixed.

Good work, thanks a lot for the feedback!


CI-11237 Update set-up-an-aws-vm-build-infrastructure.md

Correct the user_data and user_data_path usage examples

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65c64bee879b1f0f52eba736--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65c650e6879b1f13a8eba5c2--harness-developer.netlify.app


Creating Window in public App() method always return null

Describe the bug
Creating Window in public App() method always return null
Steps to reproduce the bug
public App()
{
    this.InitializeComponent();
    myWindow = new Window();
    // myWindow always is null !
}

Expected behavior
we should create window in public App() method
Screenshots
No response
NuGet package version
Windows App SDK 1.3.2: 1.3.230602002
Packaging type
Packaged (MSIX), Unpackaged
Windows version
Windows 11 version 22H2 (22621, 2022 Update)
IDE
Visual Studio 2022
Additional context
No response

any update?

@ghost1372 Do you still repro this issue? On 1.4 I see a non-null window get created, and later there is a crash due to #8806. On 1.5, this all works without issue.

Hi @codendone
Yes, still repro

@codendone  i commented below code
//if (CurrentWindow.Content is not Frame rootFrame)
//{
//    CurrentWindow.Content = rootFrame = new Frame();
//}
and in this case i can see that Window is Created, however CurrentWindow.Activate(); does not work and get null refrence exception

Hi @codendone
Still repro, however, if OnLaunched method codes removed/commented, i can see that window is created, and i we write a single line code in OnLaunched method, we get null refrence exception.

Thanks! My repro didn't hit the right scenario.
This is an interesting problem. The problem is that creating the Window results in initializing XAML (since it isn't yet initialized during the App constructor) and initializing XAML causes OnLaunched() to be called (still during the Window constructor). My test code created, used, and even activated the Window all in the App constructor, which worked fine since the order of the calls was what you would expect. Obviously new Window() causing OnLaunched to synchronously be called is not what anyone would expect, and that broke your scenario.
I'm not sure what the fix will be. There are some interesting dependencies here which may make this difficult to fix up.


[Tables] Encoder perf and api refactor

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-data-tables

/azp run python - tables - tests


First Item of Bar Chart Does Not Appear for Certain Widths When Border Radius is Enabled

Description
The first item of the bar chart does not seem to appear for certain widths. The value is there, even on the tooltip, but the bar does not show. When I set the Border Radius to 0 it seems to work again:

Steps to Reproduce

Visit the my codepen example: https://codepen.io/thimows/pen/BaEbdmW
You will see that the first bar does not show.
Set the border radius to 0 under plotOptions and it will show up again.

Reproduction Link
You can see a reproducible example here: https://codepen.io/thimows/pen/BaEbdmW

To follow up, this seems to be caused by a borderRadius and a columnWidth of 100%. Changing the columnWidth to 99% seems to fix it. Maybe there is a small edge case here that is not accounted for?

Adding to this because I am having similar issues with column width 100% and bar charts, for me however I am not using border radius. Reducing column width helped fix my issues but the issue only occurred with 3 data points but was fine for 4 which was strange. Also the first bar seems to be showing fine in your reproduction link
The issue I mentioned is here
https://codepen.io/rogueDovah/pen/GRLeVaN


TypeError Cannot read property 'length' of undefined

I am getting a crash in production: TypeError Cannot read property 'length' of undefined

Here is the function corresponding to the minified version in the crash:
    function show(index, gallery) {
        if (!isOverlayVisible && index >= 0 && index < gallery.length) {
            prepareOverlay(gallery, options);
            showOverlay(index);
            return true;
        }
        if (index < 0) {
            if (options.animation) {
                bounceAnimation('left');
            }
            return false;
        }
        if (index >= imagesElements.length) {
            if (options.animation) {
                bounceAnimation('right');
            }
            return false;
        }

        currentIndex = index;
        loadImage(currentIndex, function() {
            preloadNext(currentIndex);
            preloadPrev(currentIndex);
        });
        updateOffset();

        if (options.onChange) {
            options.onChange(currentIndex, imagesElements.length);
        }

        return true;
    }

Browser:
Mozilla/5.0 (Linux; Android 7.1.1; ASUS_X00DDA Build/NMF26F; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/66.0.3359.158 Mobile Safari/537.36 [FB_IAB/FB4A;FBAV/<IP_ADDRESS>.75;]

I agree, there's definitely something wrong with the first if when showNextImage is called programmatically.

I agree, there's definitely something wrong with the first if when showNextImage is called programmatically.

BTW, the crash is purely from user interactions since I don't call showNextImage in my code. The report was then sent back by sentry.

That doesn't make sense as isOverlayVisible should be equal to false here:
https://github.com/feimosi/baguetteBox.js/blob/dev/src/baguetteBox.js#L608
Therefore the gallery should be hidden and a user has no way to interact with it. Could you debug it further?

Maybe ignore my comment. I have been trying to debug this but unable to because I can't trigger the error myself.

I'm quite busy these days, but I'll try to debug it myself when I have some time.

I'm actually hitting this when I have more than one gallery on the page. All galleries will load fine, and will open the baguettebox, but only the first gallery arrows will respond to click, while the others will throw errors. Oddly enough, arrow keys appear to work for all galleries.
The error (with unminified js):
VM1453 baguetteBox.js:632 Uncaught TypeError: Cannot read property 'length' of undefined
    at show (VM1453 baguetteBox.js:632)
    at showNextImage (VM1453 baguetteBox.js:601)
    at HTMLButtonElement.nextButtonClickHandler (VM1453 baguetteBox.js:87)
show @ VM1453 baguetteBox.js:632
showNextImage @ VM1453 baguetteBox.js:601
nextButtonClickHandler @ VM1453 baguetteBox.js:87

and what my template looks like (the actual code can be derived easily):
{% load static wagtailimages_tags core_tags %}

<link rel="stylesheet" href="{% static 'gallery/css/baguetteBox.css' %}"/>

{% random_id as gallery_id %}

  {% for img in value.images %}
    {% image img.image fill-600x500 as img_thumb %}
    {% image img.image original as img_original %}

        <link rel="preload" href="{{ img_original.url }}">

  {% endfor %}


how to convert wav to hca or awb

if a hca encrypted with a custon key，use vgmstream can decod,does it show that encode is feasible?
If possible，what is the convert command ,such as convert aaa.wav to bbb.hca(encrypted with a custon key).

You can’t make encrypted HCAs with this. Only with CRIWare’s official tools.

Added in e6e0700


Occasionally a response empty appears on online servers

Describe the bug
springcloud-gateway version: 3.1.2
body_bytes_sent: 0 not request_method: OPTIONS  and status: 200
There were 474 of them today,  Total number was  1,454,361
The balance upstream is three springcloud gateway service

we business service can't receive these request. And the log of AccessLogFilter(implements GlobalFilter, Ordered) that I customized in springcloud gateway isn't output.
When I enable it
-Dreactor.netty.http.server.accessLogEnabled=true
Its logs can be output normally
What's really troubling now is that I can't actively reproduce this problem.

It looks like getting a token from Redis and then getting Mono.empty(), Then I used flatMap without judgment (switchIfEmpty)


⚠ Bofrost.fr has degraded performance

In 3ac7369, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1482 ms

Resolved: Bofrost.fr performance has improved in 81ea3cb after 42 minutes.


Prevent running certain workflows on forks

Fixes

Fixes #3693 by @AetherUnbound
Description

This PR prevents the following workflows from running on forks:

generate_pot.yml
issue_automations.yml
label_sync.yml
pr_automations.yml
pr_automations_init.yml
pr_ping.yml
project_thread_update_reminders.yml
release-app.yml
renovate.yml
subscribe_to_label.yml
sync_meta.yml
weekly_updates.yml

Testing Instructions

Merge and find out!
Checklist

[x] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.
[ ] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Thanks for the quick review folks, and no worries! I can add comments in the same places 😄


solving bug in mflike

related to Issue #168

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 74.63%. Comparing base (1b7c793) to head (0c68cb8).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #170      +/-   ##
==========================================
+ Coverage   74.61%   74.63%   +0.01%
==========================================
  Files          33       33
  Lines        2029     2030       +1
==========================================
+ Hits         1514     1515       +1
  Misses        515      515

Files
Coverage Δ

soliket/mflike/mflike.py
80.90% <100.00%> (+0.09%)
:arrow_up:

soliket/mflike/theoryforge_MFLike.py
83.50% <100.00%> (ø)


Downed pilot to infantry & helicopter

During CSAR, a menu should be available to make the downed pilot move towards either:

the infantry dropped by a Mi8
the Mi8 itself, provided it's landed in a reasonable radius

I think this can be closed since we bypassed the need for that by moving the crash sites to accessible areas only


4D5307F1 - Fable 2

Marketplace

Tested on https://github.com/xenia-canary/xenia-canary/commit/9da1abbbce35bf061a9efe162eae9b657bb5b812
Issues:
Ground is entirely missing, minor audio issues including sentences cutting off
Log:
xenia.zip
Screenshot(s):

Labels:
(Recommended labels)

state-gameplay
gpu-drawing-corrupt

I got the same problem.
xenia_log.zip

I as well have the same problem. i7 10700k, DDR4 16GB ram, GTX 1080 SC.
Issues: state of gameplay: gpu-drawing-corrupt
Log:
xenia.zip
Screenshot:

The same problem.
Config: win10 x64, ryzen7 3800x, rtx 2060
Log: xenia.zip

Latest xenia master still has this issue.

Latest xenia master still has this issue.

sir, this is canary.

Latest xenia master still has this issue.

sir, this is canary.

My bad.
Latest Canary stil has no ground visible, patch did not work as well.
Any idea what might be the issue? All the other textures seem to work just fine.

I have not tried this in a while. I will have to download an updated copy and see what issues are present now to help. I am not a dev but definitely interested in helping via reporting of statistics.
Sent from Yahoo Mail on Android
On Wed, Nov 3, 2021 at 17:47, @.***> wrote:
Latest xenia master still has this issue.
sir, this is canary.
My bad.
Latest Canary stil has no ground visible, patch did not work as well.
Any idea what might be the issue? All the other textures seem to work just fine.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

I say this because I am running windows 11 and it has been more stable for me than windows. A lot of issues I had are gone now.
Sent from Yahoo Mail on Android
On Wed, Nov 3, 2021 at 17:53, Timothy @.***> wrote:   I have not tried this in a while. I will have to download an updated copy and see what issues are present now to help. I am not a dev but definitely interested in helping via reporting of statistics.
Sent from Yahoo Mail on Android
On Wed, Nov 3, 2021 at 17:47, @.***> wrote:
Latest xenia master still has this issue.
sir, this is canary.
My bad.
Latest Canary stil has no ground visible, patch did not work as well.
Any idea what might be the issue? All the other textures seem to work just fine.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

GPU Drawing corrupt is finally fixed!

The only real issue I have seen now is at the bottom of the screen where the subtitles appear.
Thank you!
Will be doing a full play though to see if there are any other noticeable issues.

GPU Drawing corrupt is finally fixed!  The only real issue I have seen now is at the bottom of the screen where the subtitles appear. Thank you! Will be doing a full play though to see if there are any other noticeable issues.

Hey!
Which build are you using?
I've awaited this so long I managed to snatch free sub to play it over browser, but the lag there is just horrible, would much rather play it directly.

GPU Drawing corrupt is finally fixed!  The only real issue I have seen now is at the bottom of the screen where the subtitles appear. Thank you! Will be doing a full play though to see if there are any other noticeable issues.

Hey!
Which build are you using?
I've awaited this so long I managed to snatch free sub to play it over browser, but the lag there is just horrible, would much rather play it directly.

ab40271 of Experimental Canary
I have just a few issues with it. If you look at my screenshot and see that the character has no texture that seems to be fixed for me now too.

ab40271 of Experimental Canary I have just a few issues with it. If you look at my screenshot and see that the character has no texture that seems to be fixed for me now too.
Nope, only the child version of the main character has working textures, once you play the grown up version her textures are still broken

Nope, only the child version of the main character has working textures, once you play the grown up version her textures are still broken

The grown up character does get it's texted when you are fully evil or good.

I've been fiddling with almost every setting in the config files and nothing fixes this both on the latest master and canary builds.

What Graphics Device is it talking about? And how can I fix it?

And how do I get it to stop moving my mouse when moving the right control stick?

close steam

Hello.
The game hangs with the error - "Graphics device lost".
The game freezes always happen. The freeze can happen immediately or after 1-2 minutes. The sound continues to play.
I have been using different versions of Xenia canary for half a year.
Windows 11 Pro
CPU - AMD Ryzen 7 5700G
GPU AMD Radeon Vega 64
RAM - 16 Gb
Xenia canary - 6e86eacf5

xenia.log

Currently playing through the Sept 19 build and haven't had any major issues subtitles work some signs are slightly dark but I do not remember if its the game in general or xenia.

Some of the ground textures are not rendering properly on xenia_canary build and master build.
d3d12, Windows 10, rx580 with the latest driver (2023-08-31), i5 12400f, 16gb ddr4.
I think it has something to do with rx580 and AMD drivers.
Xenia_canary version:
https://github.com/xenia-project/xenia/commit/911055c44fd334a5f12d0ce28f7d70c88fb17fd1

Log file:
xenia.log.zip

I've been fiddling with almost every setting in the config files and nothing fixes this both on the latest master and canary builds.

I had the same bug. Changing the xenia-canary.config.toml file helped:
d3d12_readback_resolve = true


Vanilla uPortal Documentation

Small changes to master app config to get it to work
Some small additions to the readme so that deploying is a bit easier.  Even deep links to frame documentation

:+1:


GOOGLE! DON'T RECOMMEND TOYS LIKE THIS UNLESS

GOOGLE! DON'T RECOMMEND TOYS LIKE THIS UNLESS IT DOES NOT SUPPORT PUBSPEC.YAML AND ASSETS

DartPad is not intended as a full app development environment. It is intended as an environment to help people experiment while getting started. Adding the capability to support any package, including code generation, as well as asset uploads, is problematic on both cost and security review fronts.

DartPad is not intended as a full app development environment. It is intended as an environment to help people experiment while getting started. Adding the capability to support any package, including code generation, as well as asset uploads, is problematic on both cost and security review fronts.


Update trainer.py

added the progress bar feature (fastprogress) in epoch summary and also time duration of epoch displayed

FYI Github offers a Draft PR for PRs which are not ready for review.


[firebase_ml_vision] TextBlocks and all of it's children have NULL confidency

Describe the bug
When scanning text using the TextRecognizer class all scanned elements have  confidency field of value null.
To Reproduce
Try using the following code:
    final FirebaseVisionImage visionImage =
        FirebaseVisionImage.fromBytes(availableImage.planes[0].bytes, metadata);
    final TextRecognizer textRecognizer =
        FirebaseVision.instance.textRecognizer();
    final VisionText visionText =
        await textRecognizer.processImage(visionImage);

    for (TextBlock tb in visionText.blocks) {
      debugPrint(tb.confidence.toString());
    }

and see that each block (and all it's children such as lines or elements) has a null value,
Expected behavior
confidence field should represent the confidence of the recognizer's choice to mark this block as a text block.
Additional context
It's been like this since forever, currently using version 0.9.3+5.

Hi @topnax
can you please provide your flutter doctor -v ,
your flutter run --verbose
Thank you

I am closing this issue as now I have read that the confidence field is filled only when using it in the cloud which I am not doing. Thank you very much and sorry for my misunderstanding.


Please, this will save foreign chars posts

URI not properly coded broke the process
curl -H "Content-Type: application/x-www-form-urlencoded" -d "{%:%}" -X POST "http://localhost:3000"
Please let us to deal with this problem at the main code later... We could back to this problem later with some safe function.
Thanks in advance  :)
Tcha-Tcho

i don't understand why need to replace the '+' with ' '. Any one can tell? Thanks.


Notification Priority

I have noticed that notifications using the "push" mode for mobile devices can be seriously delayed. Is there any chance that Amazon has any kind of priority flag that can be set so that notifications are nearly immediate?

Not that I can see. How serious is the delay? Like minutes or longer? It's possible that it is queuing up requests if you have a lot of devices that are also updating. I can investigate whether that queue can be manipulated.

Well, there was a 14 minute difference between a notification reaching my phone, and my wife's. That said, I believe it to be an Android issue with the phone possibly sleeping. Might have to look for a more insistent type of notification that comes through anyhow (like an SMS) for important notifications. Most of what I'm using it for is a daily report on solar production (after sunset) and an afternoon notification of pool and domestic hot water temperatures.
I was wanting to use it for garage door notices (especially left open)...

I was trying to get separate notifications to two different phones for different things, now I'm getting two of each notification on each phone. Any idea how to get back to just one notification each? I had added the second account but have since removed it when I couldn't get it to only send to one phone.


Remove qubit_set v0.15 deprecation.

Yet more v0.15 deprecation removals.

Automerge cancelled: A required status check is not present.
Missing statuses: ['Pytest Windows (3.7)', 'Pytest Windows (3.8)', 'Pytest Windows (3.9)', 'Typescript tests']

Automerge cancelled: A status check is failing.


[Bug]: Unstake button double click

What happened?
Screen Recording 2023-04-01 at 11.27.19
What operating system are you seeing the problem on?
Mac OS
What browsers are you seeing the problem on?
Safari
What wallet extension are you using?
Metamask
Rules

[X] I agree to follow this project's rules

the video was not attached. ill try to reproduce it myself.

I tried to reproduce the issue, but could not. If its related to the form also submitting when clicking the back button, then this is also fixed, but think the update was not published yet.

its possible that the click initiated some form evaluation due to the focus being changed. will look into it. thanks.


doc: [CDS-69089]: Update sync-gitops-applications.md for supporting deployment of commits

Supporting synchronizing commits in GitOps apps
Screenshot:

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[x] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[x] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

review link : https://64827d7f8b22ba007c5e348a--harness-developer.netlify.app/docs/continuous-delivery/gitops/sync-gitops-applications

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


we should make the headers used be a more unique name-space that references CSI.

... would seem unlikely, but we've ran into this being super painful that
The headers
1754 | #   * log-client
  | 1755 | #   * log-origin
  | 1756 | #   * log-request
  | 1757 | #   * log-response
  | 1758 | #   * log-timing
As populated in snippets clash with the existing VCL of big customers as seen in https://fastly.zendesk.com/agent/tickets/318269
renaming the above to be names like
log-lem-client
log-lem-origin
etc  should be enough to make this very unlikely to bite us again.
Even some of the local-variable declarations like:
declare local var.origin_ttfb FLOAT;
We may want to also be defensive on - I think the scopes are mostly different but these are tedious to trace in 370,000 collective lines.

I have a local branch with the proposed changes in it. I am unable to push though. Perhaps I do not have correct permissions on the repo?

fixed in https://github.com/fastly/fastly-lem/releases/tag/1.6

fixed in https://github.com/fastly/fastly-lem/releases/tag/1.6


Update runtime to v0.18.4

Description of changes:

Update runtime to v0.18.4

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.

/lgtm


Sonobuoy v0.50.0 Error attempting to run sonobuoy

I tried to run sonobuoy with the command sonobuoy run --mode=certified-conformance. After that a sonobuoy pod will come up but when trying to get sonobuoy status the following output appears:
ERRO[0000] error attempting to run sonobuoy: missing status annotation "sonobuoy.hept.io/status"
What could be the issue?

Closed due to inactivity.


Upgrade to PHP 7.3

This is the first error that needs to be fixed:
[12-May-2019 15:44:42 Europe/Dublin] PHP Deprecated:  filter_var(): explicit use of FILTER_FLAG_SCHEME_REQUIRED and FILTER_FLAG_HOST_REQUIRED is deprecated in /home/john/Git/fivetoday/vendor/alphadevx/alpha/Alpha/Util/Helper/Validator.php on line 317


Make use of Rapid Gossip Sync

Is your feature request related to a problem? Please describe.
it takes up to 2 mins to sync network graph. This is a problem when initialising lightning node, especially on mobile.
Describe the solution you'd like
RGS should save both bandwidth and time
Describe alternatives you've considered
Not sure if there are any?
Additional context
https://www.notion.so/get10101/TABConf-report-42f7343fd8224381bb4dd6db464038c7?pvs=4
I'm proposing using LDK RGS server, no need to roll out our own for now.

We want to look into this after #1472


[gameinput] Add port to use Microsoft.GameInput from nuget.org

The GameInput API is available as a NuGet package. This adds a new port recipe to use it.
If using the xbox triplets, GameInput from an installed Microsoft GDKX is used instead of the NuGet package which is intended for PC.

The next release of directxtk and directxtk12 will consume this port.

@BillyONeal I know you have a process for these, but I was wondering when this might be merged? I have updates for the directxtk and directxtk12 ports that depend on this.


Changing nickname keep the user's color.

This should be handled inside pickUsername which is the reason the colors change.

You are right. Maybe pickUsername shouldn't change the color in the first place?

Yes, that's what I've been working on coincidentally.

was fixed in https://github.com/quackduck/devzat/commit/0e0ef1a5c79983ed3ef3dc545f4dac31b79a9098


Validate() to return payload(s) that were actually signed

https://www.w3.org/TR/xmldsig-bestpractices/#check-what-is-signed

I think this is the right direction, however I don't want to change an exported signature and break any applications that are already depending on it.  Instead, let's deprecate the Validate method and create a new one to handle this functionality:
// Validate validates the Reference digest values, and the signature value
// over the SignedInfo.
//
// Deprecated: Use ValidateReferences instead
func (v *Validator) Validate() error {
	_, err := v.ValidateReferences()
	return err
}

// ValidateReferences validates the Reference digest values, and the signature value
// over the SignedInfo.
//
// If the signature is enveloped in the XML, then it will be used.
// Otherwise, an external signature should be assigned using
// Validator.SetSignature.
//
// The references returned by this method can be used to verify what was signed.
func (v *Validator) ValidateReferences() ([]string, error) {
	// the code from your Validate changes here
}

This should also fix the failing TravisCI build.

Good idea. I've implemented the changes.


docs:  Adding Docs for new SQLServer Vector store package

Description: Adding Documentation for new SQL Server Vector Store Package.
Changed files -
Added new Vector Store - docs\docs\integrations\vectorstores\sqlserver.ipynb
FeatureTable.Js - docs\src\theme\FeatureTables.js
Microsoft.mdx - docs\docs\integrations\providers\microsoft.mdx
Detailed documentation on API - https://python.langchain.com/api_reference/sqlserver/index.html

@baskaryan I am getting vercel deployment error for unrelated files I havent changed or touched https://langchain-hyca809rb-langchain.vercel.app
Could you help us with fixing this?
Error: MDX compilation failed for file "/vercel/path0/docs/docs/langserve.md"
Cause: Docs markdown link couldn't be resolved: (MIGRATION.md) in source file "/vercel/path0/docs/docs/langserve.md" for version current
Details:
Error: Docs markdown link couldn't be resolved: (MIGRATION.md) in source file "/vercel/path0/docs/docs/langserve.md" for version current
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
make: *** [Makefile:88: vercel-build] Error 1
error Command failed with exit code 2.

@baskaryan I am getting vercel deployment error for unrelated files I havent changed or touched https://langchain-hyca809rb-langchain.vercel.app
Could you help us with fixing this?
Error: MDX compilation failed for file "/vercel/path0/docs/docs/langserve.md" Cause: Docs markdown link couldn't be resolved: (MIGRATION.md) in source file "/vercel/path0/docs/docs/langserve.md" for version current Details: Error: Docs markdown link couldn't be resolved: (MIGRATION.md) in source file "/vercel/path0/docs/docs/langserve.md" for version current error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. make: *** [Makefile:88: vercel-build] Error 1 error Command failed with exit code 2.

I had the same in my PR and I think other PRs have the same issue.
https://github.com/langchain-ai/langchain/pull/28157

@baskaryan requesting help on this Vercel Failure

@efriis can you please help to have the PR unblocked? Thanks!

@eyurtsev @efriis could you help us with unblocking this PR please?

Thanks a lot for the help Erick! Noted about the formatting issues, we'll double check next time


Support IE10 Repeat Syntax

VSCode Version: 1.23.1
OS Version: Windows 8

Steps to Reproduce:

View the following code in IE; https://s.codepen.io/fizzbuzz791/debug/EGBxdq/XBkGRZQpnRNA
Confirm that it's valid syntax and displays a grid with 3 columns
Open a CSS file in VS Code, copy the CSS from codepen and view the following error;

Does this issue occur when all extensions are disabled?: Yes

Closing due to the lack of additional information

Sorry, I completely missed this. Does this link work better?
https://codepen.io/fizzbuzz791/pen/EGBxdq

Yes, thanks!
.grid {
  display: grid;
  display: -ms-grid;
  grid-template-columns: repeat(3, 1fr);
  -ms-grid-columns: (1fr)[3];
}

.cell1 {
  -ms-grid-column: 1;
}

.cell2 {
  -ms-grid-column: 2;
}

.cell3 {
  -ms-grid-column: 3;
}


improved coverage with new tests

The coverage percentage can be improved with three four new, simple tests.
Additional thoughts.

test runtime can be reduced by moving changing _MAX_TRIAL_REQUESTS into a default parameter =5. That'll allow the tests to specify 2 attempts.
most of _get_products can be skipped if valid_page stays false

Let me know if you'd like me to make any of the above changes as part of this pull request. I'm also happy to incorporate other suggestions too

Pull Request Test Coverage Report for Build 170

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+3.9%) to 95.455%

Totals

Change from base Build 165:
3.9%

Covered Lines:
147

Relevant Lines:
154

💛  - Coveralls

Very nice of you @sdolenc
I'll try to merge it soon.
Feel free to implement your other ideas.
I'm not sure I really understand the first one though.


gfx:fonts: Add new Symbols for 30px and 60px

New symbols added:
SYMBOL_PLAY     "Z"
SYMBOL_STOP     "["
SYMBOL_PAUSE    ""
SYMBOL_PREV     "]"
SYMBOL_NEXT     "^"
SYMBOL_SPMUTE   "_"
SYMBOL_SPUNMUTE "`"
Signed-off-by: Ajay Bhargav<EMAIL_ADDRESS>

Let me know if I missed anything

It looks great!
Thank you a lot! :)

I've noticed that the length of the 60 px height symbols are a little bit short. Look at the WiFi symbol, a few columns are missing on the right. Can you correct it?
As you can see I moved the fonts to misc/gfx to increase their re-usability.
Thank you in advance!


VLF highlighting not working correctly on detail level

VLF highlighting isn't working or is inconsistent at detail level.  e.g. Max VLF highlighted orange at just over 1000 at summary level but green at detail level

Included in 2.36.1 🎉


feat: add node 5 support

Refactor code to add support for Node v5

Coverage remained the same at 100.0% when pulling eedb5b65f4dc85149f363d0cf29c090f6b8150f3 on feature/node-5-support into 68d22a8b78037f42220485714df570dbd9e50324 on master.


gulp-sass not found on Windows 7 x64

Struggling to find an answer to this.
I am also very new to the whole gulp/sass/node thing. The answers in here for other relatively similar issues are at the edge of my capacity to be honest. Would really like to get off this base though. Any help appreciated very much.
First up all my versions; followed by my install sequence and messages; third a test to see if sass is there.
Thanks (see below)
$ node -v
v7.7.2
$ gulp -v
[22:53:11] CLI version 3.9.1
[22:53:11] Local version 3.9.1
$ npm -v
4.3.0
When I try to install gulp-sass:
$ npm install gulp-sass
<EMAIL_ADDRESS>C:\Bitnami\wampstack-5.6.30-1\apache2\htdocs\20170302bumwp\wp-content\themes\gulp-dev
`--<EMAIL_ADDRESS>npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN enoent ENOENT: no such file or directory, open 'C:\Bitnami\wampstack-5.6.30-1\apache2\htdocs\20170302bumwp\wp-content\themes\gulp-dev\node_modules\deprecated\package.json'
npm WARN<EMAIL_ADDRESS>No repository field.
and when I test to see if its there:
$ sass -v
bash: sass: command not found

npm WARN enoent ENOENT: no such file or directory, open 'C:\Bitnami\wampstack-5.6.30-1\apache2\htdocs\20170302bumwp\wp-content\themes\gulp-dev\node_modules\deprecated\package.json'

This is not relate to gulp-sass. Looks like npm encounted an issue during install. Remove node_modules and run npm install again.


Revert "Don't populate an empty NextHop in AFTOperations"

Reverts openconfig/gribigo#240
Breaks tests.

Fixed the repo config to make the unit tests blocking.