Skip to content

#575 fix slf4j bindings#576

Merged
mergify[bot] merged 1 commit into
mainfrom
fix/575-slf4j-bindings
Oct 19, 2022
Merged

#575 fix slf4j bindings#576
mergify[bot] merged 1 commit into
mainfrom
fix/575-slf4j-bindings

Conversation

@arcade-player
Copy link
Copy Markdown
Contributor

What does this PR do?

fix slf4j binding

Motivation

akf4h binding is broken

Related issues

#575

@mergify mergify Bot merged commit c861018 into main Oct 19, 2022
@lvca lvca deleted the fix/575-slf4j-bindings branch June 20, 2025 00:12
mergify Bot added a commit that referenced this pull request Nov 19, 2025
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 3.14.1 to 3.14.2.
Changelog

*Sourced from [js-yaml's changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md).*

> [3.14.2] - 2025-11-15
> ---------------------
>
> ### Security
>
> * Backported v4.1.1 fix to v3
>
> [4.1.1] - 2025-11-12
> --------------------
>
> ### Security
>
> * Fix prototype pollution issue in yaml merge (<<) operator.
>
> [4.1.0] - 2021-04-15
> --------------------
>
> ### Added
>
> * Types are now exported as `yaml.types.XXX`.
> * Every type now has `options` property with original arguments kept as they were
>   (see `yaml.types.int.options` as an example).
>
> ### Changed
>
> * `Schema.extend()` now keeps old type order in case of conflicts
>   (e.g. Schema.extend([ a, b, c ]).extend([ b, a, d ]) is now ordered as `abcd` instead of `cbad`).
>
> [4.0.0] - 2021-01-03
> --------------------
>
> ### Changed
>
> * Check [migration guide](https://github.com/nodeca/js-yaml/blob/master/migrate_v3_to_v4.md) to see details for all breaking changes.
> * Breaking: "unsafe" tags `!!js/function`, `!!js/regexp`, `!!js/undefined` are
>   moved to [js-yaml-js-types](https://github.com/nodeca/js-yaml-js-types) package.
> * Breaking: removed `safe*` functions. Use `load`, `loadAll`, `dump`
>   instead which are all now safe by default.
> * `yaml.DEFAULT_SAFE_SCHEMA` and `yaml.DEFAULT_FULL_SCHEMA` are removed, use
>   `yaml.DEFAULT_SCHEMA` instead.
> * `yaml.Schema.create(schema, tags)` is removed, use `schema.extend(tags)` instead.
> * `!!binary` now always mapped to `Uint8Array` on load.
> * Reduced nesting of `/lib` folder.
> * Parse numbers according to YAML 1.2 instead of YAML 1.1 (`01234` is now decimal,
>   `0o1234` is octal, `1:23` is parsed as string instead of base60).
> * `dump()` no longer quotes `:`, `[`, `]`, `(`, `)` except when necessary, [#470](https://redirect.github.com/nodeca/js-yaml/issues/470), [#557](https://redirect.github.com/nodeca/js-yaml/issues/557).
> * Line and column in exceptions are now formatted as `(X:Y)` instead of
>   `at line X, column Y` (also present in compact format), [#332](https://redirect.github.com/nodeca/js-yaml/issues/332).
> * Code snippet created in exceptions now contains multiple lines with line numbers.
> * `dump()` now serializes `undefined` as `null` in collections and removes keys with
>   `undefined` in mappings, [#571](https://redirect.github.com/nodeca/js-yaml/issues/571).
> * `dump()` with `skipInvalid=true` now serializes invalid items in collections as null.
> * Custom tags starting with `!` are now dumped as `!tag` instead of `!<!tag>`, [#576](https://redirect.github.com/nodeca/js-yaml/issues/576).
> * Custom tags starting with `tag:yaml.org,2002:` are now shorthanded using `!!`, [#258](https://redirect.github.com/nodeca/js-yaml/issues/258).
>
> ### Added
>
> * Added `.mjs` (es modules) support.
> * Added `quotingType` and `forceQuotes` options for dumper to configure
>   string literal style, [#290](https://redirect.github.com/nodeca/js-yaml/issues/290), [#529](https://redirect.github.com/nodeca/js-yaml/issues/529).
> * Added `styles: { '!!null': 'empty' }` option for dumper
>   (serializes `{ foo: null }` as "`foo:` "), [#570](https://redirect.github.com/nodeca/js-yaml/issues/570).

... (truncated)


Commits

* [`9963d36`](nodeca/js-yaml@9963d36) 3.14.2 released
* [`10d3c8e`](nodeca/js-yaml@10d3c8e) dist rebuild
* [`5278870`](nodeca/js-yaml@5278870) fix prototype pollution in merge (<<) ([#731](https://redirect.github.com/nodeca/js-yaml/issues/731))
* See full diff in [compare view](nodeca/js-yaml@3.14.1...3.14.2)
  
[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility\_score?dependency-name=js-yaml&package-manager=npm\_and\_yarn&previous-version=3.14.1&new-version=3.14.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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-automerge-start)
[//]: # (dependabot-automerge-end)
---
Dependabot commands and options
  
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show  ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will 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](https://github.com/ArcadeData/arcadedb/network/alerts).
mergify Bot added a commit that referenced this pull request May 10, 2026
…o 5.21.2 in /studio [skip ci]

Bumps [enhanced-resolve](https://github.com/webpack/enhanced-resolve) from 5.21.0 to 5.21.2.
Release notes

*Sourced from [enhanced-resolve's releases](https://github.com/webpack/enhanced-resolve/releases).*

> v5.21.2
> -------
>
> ### Patch Changes
>
> * Fix TsconfigPathsPlugin circular project references causing stack overflow, add support for extending from unscoped npm packages, and use `stat` instead of `readFile` for existence checks in extends resolution. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#575](https://redirect.github.com/webpack/enhanced-resolve/pull/575))
> * perf: dedupe miss paths in `DirectoryExistsPlugin`/`FileExistsPlugin` and prune the per-resolve `TsconfigPathsPlugin` context scan. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#574](https://redirect.github.com/webpack/enhanced-resolve/pull/574))
> * perf: drop a dead Map lookup in `findMatch` and flatten `AliasFieldPlugin`'s cache check. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#574](https://redirect.github.com/webpack/enhanced-resolve/pull/574))
> * perf: hot-path tweaks in `ImportsFieldPlugin`, `AliasUtils`, and `util/entrypoints`. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#574](https://redirect.github.com/webpack/enhanced-resolve/pull/574))
> * perf: cut per-resolve allocations in `Resolver.parse`, `loadDescriptionFile`, and `TsconfigPathsPlugin._selectPathsDataForContext`. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#574](https://redirect.github.com/webpack/enhanced-resolve/pull/574))
>
> v5.21.1
> -------
>
> ### Patch Changes
>
> * Allocation-free reductions on hot-path code: hoist `/#/g`, `/\$/g` and `/\\/g` to module-level constants and gate the corresponding `.replace` calls behind `includes(…)` so paths/queries/requests without the match char skip the regex state machine entirely (the common case); share a single `EMPTY_NO_MATCH` tuple instead of allocating `[[], null]` per "no match" / "no condition matched" return; switch `directMapping`'s `for...of` over `mappingTarget` and inner results to indexed loops to avoid iterator-object allocation per call; inline `isConditionalMapping` at its two hot-path call sites and merge the duplicate `default` / `conditionNames.has(condition)` branches in `computeConditionalMapping`; replace `invalidSegmentRegEx.exec(…) !== null` with `.test(…)` (no match-array allocation); drop the dead `deprecatedInvalidSegmentRegEx.test(…) !== null` clause in `ImportsFieldPlugin` (`.test` returns boolean; `true !== null` and `false !== null` are both true, so it was `&& true`); drop the redundant `relativePath.length === 0` guard before `!startsWith("./")` in `ExportsFieldPlugin` (the empty-string case is already covered). (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#558](https://redirect.github.com/webpack/enhanced-resolve/pull/558))
> * restore plugin compatibility for `[...resolveContext.stack]` iteration (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#569](https://redirect.github.com/webpack/enhanced-resolve/pull/569))
> * fix `TsconfigPathsPlugin` to support `resolveSync` with `useSyncFileSystemCalls` (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#572](https://redirect.github.com/webpack/enhanced-resolve/pull/572))


Changelog

*Sourced from [enhanced-resolve's changelog](https://github.com/webpack/enhanced-resolve/blob/main/CHANGELOG.md).*

> 5.21.2
> ------
>
> ### Patch Changes
>
> * Fix TsconfigPathsPlugin circular project references causing stack overflow, add support for extending from unscoped npm packages, and use `stat` instead of `readFile` for existence checks in extends resolution. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#575](https://redirect.github.com/webpack/enhanced-resolve/pull/575))
> * perf: dedupe miss paths in `DirectoryExistsPlugin`/`FileExistsPlugin` and prune the per-resolve `TsconfigPathsPlugin` context scan. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#574](https://redirect.github.com/webpack/enhanced-resolve/pull/574))
> * perf: drop a dead Map lookup in `findMatch` and flatten `AliasFieldPlugin`'s cache check. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#574](https://redirect.github.com/webpack/enhanced-resolve/pull/574))
> * perf: hot-path tweaks in `ImportsFieldPlugin`, `AliasUtils`, and `util/entrypoints`. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#574](https://redirect.github.com/webpack/enhanced-resolve/pull/574))
> * perf: cut per-resolve allocations in `Resolver.parse`, `loadDescriptionFile`, and `TsconfigPathsPlugin._selectPathsDataForContext`. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#574](https://redirect.github.com/webpack/enhanced-resolve/pull/574))
>
> 5.21.1
> ------
>
> ### Patch Changes
>
> * Allocation-free reductions on hot-path code: hoist `/#/g`, `/\$/g` and `/\\/g` to module-level constants and gate the corresponding `.replace` calls behind `includes(…)` so paths/queries/requests without the match char skip the regex state machine entirely (the common case); share a single `EMPTY_NO_MATCH` tuple instead of allocating `[[], null]` per "no match" / "no condition matched" return; switch `directMapping`'s `for...of` over `mappingTarget` and inner results to indexed loops to avoid iterator-object allocation per call; inline `isConditionalMapping` at its two hot-path call sites and merge the duplicate `default` / `conditionNames.has(condition)` branches in `computeConditionalMapping`; replace `invalidSegmentRegEx.exec(…) !== null` with `.test(…)` (no match-array allocation); drop the dead `deprecatedInvalidSegmentRegEx.test(…) !== null` clause in `ImportsFieldPlugin` (`.test` returns boolean; `true !== null` and `false !== null` are both true, so it was `&& true`); drop the redundant `relativePath.length === 0` guard before `!startsWith("./")` in `ExportsFieldPlugin` (the empty-string case is already covered). (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#558](https://redirect.github.com/webpack/enhanced-resolve/pull/558))
> * restore plugin compatibility for `[...resolveContext.stack]` iteration (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#569](https://redirect.github.com/webpack/enhanced-resolve/pull/569))
> * fix `TsconfigPathsPlugin` to support `resolveSync` with `useSyncFileSystemCalls` (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#572](https://redirect.github.com/webpack/enhanced-resolve/pull/572))


Commits

* [`605c5ca`](webpack/enhanced-resolve@605c5ca) chore(release): new release ([#576](https://redirect.github.com/webpack/enhanced-resolve/issues/576))
* [`56002a6`](webpack/enhanced-resolve@56002a6) perf: skip empty-query concat, bound star scan, flatten alias predicate ([#574](https://redirect.github.com/webpack/enhanced-resolve/issues/574))
* [`32ed958`](webpack/enhanced-resolve@32ed958) chore: improve AGENTS.md to enforce upstream workflow and project scripts ([#577](https://redirect.github.com/webpack/enhanced-resolve/issues/577))
* [`f28d8b9`](webpack/enhanced-resolve@f28d8b9) fix: TsconfigPathsPlugin circular references, unscoped pkg extends, and perf ...
* [`292aee5`](webpack/enhanced-resolve@292aee5) chore(deps-dev): bump axios from 1.15.0 to 1.16.0 ([#573](https://redirect.github.com/webpack/enhanced-resolve/issues/573))
* [`d484b47`](webpack/enhanced-resolve@d484b47) chore(release): new release ([#561](https://redirect.github.com/webpack/enhanced-resolve/issues/561))
* [`2f41af2`](webpack/enhanced-resolve@2f41af2) fix: make TsconfigPathsPlugin work with sync file systems ([#571](https://redirect.github.com/webpack/enhanced-resolve/issues/571)) ([#572](https://redirect.github.com/webpack/enhanced-resolve/issues/572))
* [`e1f07eb`](webpack/enhanced-resolve@e1f07eb) fix: compatibility with old stack entry logic
* [`c573946`](webpack/enhanced-resolve@c573946) chore: add AGENTS.md and CLAUDE.md for AI-assisted development ([#570](https://redirect.github.com/webpack/enhanced-resolve/issues/570))
* [`37eafd5`](webpack/enhanced-resolve@37eafd5) chore(deps-dev): bump the dependencies group with 2 updates ([#565](https://redirect.github.com/webpack/enhanced-resolve/issues/565))
* Additional commits viewable in [compare view](webpack/enhanced-resolve@v5.21.0...v5.21.2)
  
[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility\_score?dependency-name=enhanced-resolve&package-manager=npm\_and\_yarn&previous-version=5.21.0&new-version=5.21.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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-automerge-start)
[//]: # (dependabot-automerge-end)
---
Dependabot commands and options
  
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show  ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants