Re: [PR] Bump serde from 1.0.195 to 1.0.196 in /lang/rust [avro]

[via GitHub]

martin-g merged PR #2717:
URL: https://github.com/apache/avro/pull/2717


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[PR] Bump strum from 0.25.0 to 0.26.1 in /lang/rust [avro]

[via GitHub]

dependabot[bot] opened a new pull request, #2718:
URL: https://github.com/apache/avro/pull/2718

   Bumps [strum](https://github.com/Peternator7/strum) from 0.25.0 to 0.26.1.
   
   Changelog
   Sourced from https://github.com/Peternator7/strum/blob/master/CHANGELOG.md;>strum's 
changelog.
   
   0.26.1
   
   https://redirect.github.com/Peternator7/strum/pull/325;>#325: use 
core instead of std in VariantArray.
   
   0.26.0
   Breaking Changes
   
   The EnumVariantNames macro has been renamed 
VariantNames. The deprecation warning should steer you in
   the right direction for fixing the warning.
   The Iterator struct generated by EnumIter now has new bounds on it. This 
shouldn't break code unless you manually
   added the implementation in your code.
   Display now supports format strings using named fields in 
the enum variant. This should be a no-op for most code.
   However, if you were outputting a string like Hello 
{field}, this will now be interpretted as a format string.
   EnumDiscriminant now inherits the repr and discriminant values from your 
main enum. This makes the discriminant type
   closer to a mirror of the original and that's always the goal.
   
   New features
   
   
   The VariantArray macro has been added. This macro adds an 
associated constant VARIANTS to your enum. The constant
   is a 'static [Self] slice so that you can access all the 
variants of your enum. This only works on enums that only
   have unit variants.
   use strum::VariantArray;
   #[derive(Debug, VariantArray)]
   enum Color {
   Red,
   Blue,
   Green,
   }
   fn main() {
   println!({:?}, Color::VARIANTS); // prints: [Red, 
Blue, Green]
   }
   
   
   
   The EnumTable macro has been experimentally added. 
This macro adds a new type that stores an item for each variant
   of the enum. This is useful for storing a value for each variant of an enum. 
This is an experimental feature because
   I'm not convinced the current api surface area is correct.
   use strum::EnumTable;
   #[derive(Copy, Clone, Debug, EnumTable)]
   enum Color {
   Red,
   Blue,
   Green,
   
   
   
   
   
   ... (truncated)
   
   
   Commits
   
   See full diff in https://github.com/Peternator7/strum/commits;>compare view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=strum=cargo=0.25.0=0.26.1)](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)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[PR] Bump serde from 1.0.195 to 1.0.196 in /lang/rust [avro]

[via GitHub]

dependabot[bot] opened a new pull request, #2717:
URL: https://github.com/apache/avro/pull/2717

   Bumps [serde](https://github.com/serde-rs/serde) from 1.0.195 to 1.0.196.
   
   Release notes
   Sourced from https://github.com/serde-rs/serde/releases;>serde's releases.
   
   v1.0.196
   
   Improve formatting of invalid type error messages involving 
floats (https://redirect.github.com/serde-rs/serde/issues/2682;>#2682)
   
   
   
   
   Commits
   
   https://github.com/serde-rs/serde/commit/ede9762a583c3cc3b87c10a53551828fad339525;>ede9762
 Release 1.0.196
   https://github.com/serde-rs/serde/commit/d438c2d67bf30e3edab31c2272c4829c12cf4cb5;>d438c2d
 Merge pull request https://redirect.github.com/serde-rs/serde/issues/2682;>#2682 from 
dtolnay/decimalpoint
   https://github.com/serde-rs/serde/commit/bef110b92a171ac568a47339f5bd97938a8c9da2;>bef110b
 Format Unexpected::Float with decimal point
   https://github.com/serde-rs/serde/commit/b971ef11d1b53da7673e0c8199e87509c003c1a8;>b971ef1
 Merge pull request https://redirect.github.com/serde-rs/serde/issues/2681;>#2681 from 
dtolnay/workspacedeps
   https://github.com/serde-rs/serde/commit/29d9f693996d199748136d5561a971ed68626724;>29d9f69
 Fix workspace.dependencies default-features future compat warning
   https://github.com/serde-rs/serde/commit/aecb4083bde754155752f5d7d442b64eb7dc636f;>aecb408
 Sort workspace dependencies
   https://github.com/serde-rs/serde/commit/1c675ab3a38e46df4e62465800970f8b20a2055d;>1c675ab
 Merge pull request https://redirect.github.com/serde-rs/serde/issues/2678;>#2678 from 
rodoufu/workspaceDependencies
   https://github.com/serde-rs/serde/commit/dd619630a337139424725697ccd9a9f7596a2d3a;>dd61963
 Adding workspace dependencies
   https://github.com/serde-rs/serde/commit/111803ab0768d010c606f2fc0d0add12750d5eef;>111803a
 Merge pull request https://redirect.github.com/serde-rs/serde/issues/2673;>#2673 from 
Sky9x/msrv-badge
   https://github.com/serde-rs/serde/commit/0024f74f34fbbdc44a7b22457faebe36c5cbe7f8;>0024f74
 Use shields.io's MSRV badges
   See full diff in https://github.com/serde-rs/serde/compare/v1.0.195...v1.0.196;>compare 
view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde=cargo=1.0.195=1.0.196)](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)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[PR] Bump strum_macros from 0.25.3 to 0.26.1 in /lang/rust [avro]

[via GitHub]

dependabot[bot] opened a new pull request, #2716:
URL: https://github.com/apache/avro/pull/2716

   Bumps [strum_macros](https://github.com/Peternator7/strum) from 0.25.3 to 
0.26.1.
   
   Changelog
   Sourced from https://github.com/Peternator7/strum/blob/master/CHANGELOG.md;>strum_macros's
 changelog.
   
   0.26.1
   
   https://redirect.github.com/Peternator7/strum/pull/325;>#325: use 
core instead of std in VariantArray.
   
   0.26.0
   Breaking Changes
   
   The EnumVariantNames macro has been renamed 
VariantNames. The deprecation warning should steer you in
   the right direction for fixing the warning.
   The Iterator struct generated by EnumIter now has new bounds on it. This 
shouldn't break code unless you manually
   added the implementation in your code.
   Display now supports format strings using named fields in 
the enum variant. This should be a no-op for most code.
   However, if you were outputting a string like Hello 
{field}, this will now be interpretted as a format string.
   EnumDiscriminant now inherits the repr and discriminant values from your 
main enum. This makes the discriminant type
   closer to a mirror of the original and that's always the goal.
   
   New features
   
   
   The VariantArray macro has been added. This macro adds an 
associated constant VARIANTS to your enum. The constant
   is a 'static [Self] slice so that you can access all the 
variants of your enum. This only works on enums that only
   have unit variants.
   use strum::VariantArray;
   #[derive(Debug, VariantArray)]
   enum Color {
   Red,
   Blue,
   Green,
   }
   fn main() {
   println!({:?}, Color::VARIANTS); // prints: [Red, 
Blue, Green]
   }
   
   
   
   The EnumTable macro has been experimentally added. 
This macro adds a new type that stores an item for each variant
   of the enum. This is useful for storing a value for each variant of an enum. 
This is an experimental feature because
   I'm not convinced the current api surface area is correct.
   use strum::EnumTable;
   #[derive(Copy, Clone, Debug, EnumTable)]
   enum Color {
   Red,
   Blue,
   Green,
   
   
   
   
   
   ... (truncated)
   
   
   Commits
   
   See full diff in https://github.com/Peternator7/strum/commits;>compare view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=strum_macros=cargo=0.25.3=0.26.1)](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)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump env_logger from 0.10.2 to 0.11.0 in /lang/rust [avro]

[via GitHub]

dependabot[bot] closed pull request #2703: Bump env_logger from 0.10.2 to 
0.11.0 in /lang/rust
URL: https://github.com/apache/avro/pull/2703


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[PR] Bump env_logger from 0.10.2 to 0.11.1 in /lang/rust [avro]

[via GitHub]

dependabot[bot] opened a new pull request, #2715:
URL: https://github.com/apache/avro/pull/2715

   Bumps [env_logger](https://github.com/rust-cli/env_logger) from 0.10.2 to 
0.11.1.
   
   Release notes
   Sourced from https://github.com/rust-cli/env_logger/releases;>env_logger's 
releases.
   
   v0.11.1
   What's Changed
   
   fix(fmt): Fix passing of WriteStyle when using Target::Pipe by https://github.com/Bobo1239;>@​Bobo1239 in https://redirect.github.com/rust-cli/env_logger/pull/302;>rust-cli/env_logger#302
   
   New Contributors
   
   https://github.com/Bobo1239;>@​Bobo1239 made 
their first contribution in https://redirect.github.com/rust-cli/env_logger/pull/302;>rust-cli/env_logger#302
   
   Full Changelog: https://github.com/rust-cli/env_logger/compare/v0.11.0...v0.11.1;>https://github.com/rust-cli/env_logger/compare/v0.11.0...v0.11.1
   v0.11.0
   What's Changed
   
   refactor(fmt): More anstream prep by https://github.com/epage;>@​epage in https://redirect.github.com/rust-cli/env_logger/pull/297;>rust-cli/env_logger#297
   fix(fmt): Improve terminal styling support by https://github.com/epage;>@​epage in https://redirect.github.com/rust-cli/env_logger/pull/298;>rust-cli/env_logger#298
   refactor: Split out env_filter package  by https://github.com/epage;>@​epage in https://redirect.github.com/rust-cli/env_logger/pull/299;>rust-cli/env_logger#299
   feat(filter): Add a Logger decorator by https://github.com/epage;>@​epage in https://redirect.github.com/rust-cli/env_logger/pull/300;>rust-cli/env_logger#300
   
   Full Changelog: https://github.com/rust-cli/env_logger/compare/v0.10.2...v0.11.0;>https://github.com/rust-cli/env_logger/compare/v0.10.2...v0.11.0
   
   
   
   Changelog
   Sourced from https://github.com/rust-cli/env_logger/blob/main/CHANGELOG.md;>env_logger's
 changelog.
   
   [0.11.1] - 2024-01-27
   Fixes
   
   Allow styling with Target::Pipe
   
   [0.11.0] - 2024-01-19
   Breaking Change
   
   Removed bespoke styling API
   
   env_logger::fmt::Formatter::style
   env_logger::fmt::Formatter::default_styled_level
   env_logger::fmt::Style
   env_logger::fmt::Color
   env_logger::fmt::StyledValue
   
   
   Removed env_logger::filter in favor of 
env_filter
   
   Compatibility
   MSRV changed to 1.71
   Features
   
   Automatically adapt ANSI escape codes in logged messages to the current 
terminal's capabilities
   Add support for NO_COLOR and CLICOLOR_FORCE, 
see https://bixense.com/clicolors/;>https://bixense.com/clicolors/
   
   Fixes
   
   Print colors when is_test(true)
   
   
   
   
   Commits
   
   https://github.com/rust-cli/env_logger/commit/7113ad4bd937a56b260a799f8952f3e61d0eaea7;>7113ad4
 chore: Release
   https://github.com/rust-cli/env_logger/commit/9f73bde4ba4d14085e0248af8eef87b506290443;>9f73bde
 docs: Update changelog
   https://github.com/rust-cli/env_logger/commit/489ba1886aab76760ab4fce702d9fdd6f77f1bdf;>489ba18
 Merge pull request https://redirect.github.com/rust-cli/env_logger/issues/302;>#302 from 
Bobo1239/main
   https://github.com/rust-cli/env_logger/commit/6f31706a184ebe6332c1a4d083702a06b56cfb87;>6f31706
 fix(fmt): Fix passing of WriteStyle when using Target::Pipe
   https://github.com/rust-cli/env_logger/commit/8f4361ba4439acb69068be0e181d2d1300b7218d;>8f4361b
 chore: Release
   https://github.com/rust-cli/env_logger/commit/ba41ebb6d2d726403560cd987b1c5b3c6797f817;>ba41ebb
 docs: Update changelog
   https://github.com/rust-cli/env_logger/commit/5e226cb2b73d6c9f1b21886a4b504afdea1ebfcf;>5e226cb
 chore: Release
   https://github.com/rust-cli/env_logger/commit/23441be565bcc4c65604a5e04d3990967e596ff4;>23441be
 Merge pull request https://redirect.github.com/rust-cli/env_logger/issues/300;>#300 from 
epage/other
   https://github.com/rust-cli/env_logger/commit/6c2ea8028236fe80c1da0a354b19808bf440858d;>6c2ea80
 style(filter): Clean up
   https://github.com/rust-cli/env_logger/commit/2d3526001061bacbf4a4c47767a318986c2c61b0;>2d35260
 feat(filter): Add a Logger decorator
   Additional commits viewable in https://github.com/rust-cli/env_logger/compare/v0.10.2...v0.11.1;>compare 
view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=env_logger=cargo=0.10.2=0.11.1)](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 

[PR] Bump serde_json from 1.0.111 to 1.0.113 in /lang/rust [avro]

[via GitHub]

dependabot[bot] opened a new pull request, #2714:
URL: https://github.com/apache/avro/pull/2714

   Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.111 to 1.0.113.
   
   Release notes
   Sourced from https://github.com/serde-rs/json/releases;>serde_json's 
releases.
   
   v1.0.113
   
   Add swap_remove and shift_remove methods on 
Map (https://redirect.github.com/serde-rs/json/issues/1109;>#1109)
   
   v1.0.112
   
   Improve formatting of invalid type error messages involving 
floats (https://redirect.github.com/serde-rs/json/issues/1107;>#1107)
   
   
   
   
   Commits
   
   https://github.com/serde-rs/json/commit/09d865b34b9701be52764dc9bf571b1a16e9d3dc;>09d865b
 Release 1.0.113
   https://github.com/serde-rs/json/commit/5aeab4eaf69d7959f013f8081865c264d6c00551;>5aeab4e
 Merge pull request https://redirect.github.com/serde-rs/json/issues/1109;>#1109 from 
serde-rs/remove
   https://github.com/serde-rs/json/commit/ca3c2ca3696cab79b8b279be7569ee1647250f1e;>ca3c2ca
 Add swap_remove and shift_remove methods on Map
   https://github.com/serde-rs/json/commit/7fece969e3b480ec620419d65c2aeb08776bebcb;>7fece96
 Release 1.0.112
   https://github.com/serde-rs/json/commit/6a6d2bbd9e8b8bd72573b863f12a4ec991f33232;>6a6d2bb
 Merge pull request https://redirect.github.com/serde-rs/json/issues/1107;>#1107 from 
serde-rs/unexpectedfloat
   https://github.com/serde-rs/json/commit/83d7bad54ba5db3a44198d6df0ff2e81621683fa;>83d7bad
 Format f64 in error messages using ryu
   https://github.com/serde-rs/json/commit/107c2d1c42817f0d71f07a4d5b0ea2f29dbce8b8;>107c2d1
 Merge pull request https://redirect.github.com/serde-rs/json/issues/1106;>#1106 from 
serde-rs/invalidvalue
   https://github.com/serde-rs/json/commit/62ca3e4c01c2e62cd5c2a32e9104f386e5ce7808;>62ca3e4
 Handle Unexpected::Unit in Error::invalid_value
   https://github.com/serde-rs/json/commit/296fafb8f32e8442ef8e4d5725c15ffca726b288;>296fafb
 Factor out JSON-specific Display impl for serde::de::Unexpected
   https://github.com/serde-rs/json/commit/e56cc696bd7c112e5dd4ccfa23d094c3a1c1c1ff;>e56cc69
 Merge pull request https://redirect.github.com/serde-rs/json/issues/1105;>#1105 from 
keienWang/master
   Additional commits viewable in https://github.com/serde-rs/json/compare/v1.0.111...v1.0.113;>compare 
view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde_json=cargo=1.0.111=1.0.113)](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)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: Make Apache Avro a proper Java module.

[Niels Basjes]

Yes, Dropping the runtime support for Java 8 is enough of a reason to bump
to AVRO 2.0.0 for me.

On Mon, Jan 8, 2024 at 6:09 PM Stephen Kittelson
 wrote:

> More and more libraries these days are dropping support for JDK 8 (at least
> Spring Boot 3, Jakarta EE 11, Mockito 5, among others), so I personally
> think it would be fine to drop support for JDK 8 in 1.12.0, or maybe even
> bump the Avro release to 2.0.0 with the removal of JDK 8 support?
>
> On Mon, Jan 8, 2024 at 2:38 AM Martin Grigorov 
> wrote:
>
> > Hi,
> >
> > I think this is a good idea!
> >
> > Some PRs (mostly by dependabot) are not merged because Avro needs to be
> JDK
> > 8 compatible and the dependencies require a newer JDK...
> > I am not sure whether Avro 1.12.0 still needs to be JDK 8 compatible or
> > not.
> >
> > Martin
> >
> > On Sat, Jan 6, 2024 at 5:55 PM Chad Preisler 
> > wrote:
> >
> > > Hello,
> > >
> > > I'm wondering if there is any interest in making Apache Avro a proper
> > Java
> > > module? The following changes are required.
> > >
> > > - Add or generate the module-info.java file.
> > > - Change the POM file to build a multi-release jar.
> > > - Replace xerial Snappy with Apache commons-compress Snappy (see
> > additional
> > > information below).
> > > - Update dependencies (like slf4) to the current versions.
> > > - Build with newer JDK. I'm using 21.
> > >
> > > Regarding the Snappy compressor, the next version of Apache
> > > commons-compress (1.25.1) can be swapped in for Xerial with no issues.
> > All
> > > of the existing unit tests will work without changes. Xerial is not a
> > > proper Java module at this time, and it uses JNI which could make it
> > tricky
> > > (especially if the goal is to use jlink).
> > >
> > > For me, the motivation here is to use Avro with modularized
> > > applications and custom runtime images using jlink.
> > >
> > > I currently have this working locally, and I can contribute my changes.
> > >
> > > Please let me know what you think.
> > >
> > > Thanks,
> > >
> > > Chad
> > >
> >
>


-- 
Best regards / Met vriendelijke groeten,

Niels Basjes

Re: Make Apache Avro a proper Java module.

[Niels Basjes]

Hi,

I have been working on this one over the holidays:
https://github.com/apache/avro/pull/2699
I'm now able to build with Java 21 and still maintain backwards
compatibility for the final artifact with Java 8.

This also includes running (almost all) tests for the main avro module
under all JDKs (8, 11, 17 and 21).

>From what I see now this change set would allow updating a lot of things
(dependencies, adding multirelease, etc.) without losing Java 8 support.

There are however a few rough edges; I had to remove the usage Unsafe and I
found that some tests simply fail on newer JDKs because of changes in the
way Java does things (mainly regarding reflection, modules and security).

Note that if we put dropping Java 8 support up for a vote I would +1 it.

Niels Basjes





On Mon, Jan 8, 2024 at 8:39 PM Chad Preisler 
wrote:

> I can do both depending on the timeline for 1.12.0. If you are cutting a
> release this week, that probably won't work. I don't think it will take
> long to switch to JDK 11 as your default, but I'm not familiar with testing
> changes to the github actions. Basically there will be some learning curve
> for me. You may want to consider adding JDK 21 and updating maven to the
> latest also.
>
> I'm happy to help and will have a decent amount of time to work on it this
> month.
>
> Let me know.
>
> On Mon, Jan 8, 2024 at 11:51 AM Ismaël Mejía  wrote:
>
> > +1 to move to Java 11. Most of our downstream projects have moved out of
> > Java 8 and the fact that we are getting behind on our own dependencies
> is a
> > sign of the current state of the ecosystem. So good to move, and no need
> to
> > change the full version. 1.12.0 should be good.
> >
> > We should probably tackle this in two different issues/PRs (1) to change
> > the baseline for development/support to Java 11 (build system, docker
> > image, github actions, enforce plugin, etc)  and (2) for the proper Java
> 11
> > modules. Would you be up to prepare also a PR for (1) if we all agree
> Chad?
> >
> >
> >
> > On Mon, Jan 8, 2024 at 6:08 PM Stephen Kittelson
> >  wrote:
> >
> >> More and more libraries these days are dropping support for JDK 8 (at
> >> least
> >> Spring Boot 3, Jakarta EE 11, Mockito 5, among others), so I personally
> >> think it would be fine to drop support for JDK 8 in 1.12.0, or maybe
> even
> >> bump the Avro release to 2.0.0 with the removal of JDK 8 support?
> >>
> >> On Mon, Jan 8, 2024 at 2:38 AM Martin Grigorov 
> >> wrote:
> >>
> >> > Hi,
> >> >
> >> > I think this is a good idea!
> >> >
> >> > Some PRs (mostly by dependabot) are not merged because Avro needs to
> be
> >> JDK
> >> > 8 compatible and the dependencies require a newer JDK...
> >> > I am not sure whether Avro 1.12.0 still needs to be JDK 8 compatible
> or
> >> > not.
> >> >
> >> > Martin
> >> >
> >> > On Sat, Jan 6, 2024 at 5:55 PM Chad Preisler  >
> >> > wrote:
> >> >
> >> > > Hello,
> >> > >
> >> > > I'm wondering if there is any interest in making Apache Avro a
> proper
> >> > Java
> >> > > module? The following changes are required.
> >> > >
> >> > > - Add or generate the module-info.java file.
> >> > > - Change the POM file to build a multi-release jar.
> >> > > - Replace xerial Snappy with Apache commons-compress Snappy (see
> >> > additional
> >> > > information below).
> >> > > - Update dependencies (like slf4) to the current versions.
> >> > > - Build with newer JDK. I'm using 21.
> >> > >
> >> > > Regarding the Snappy compressor, the next version of Apache
> >> > > commons-compress (1.25.1) can be swapped in for Xerial with no
> issues.
> >> > All
> >> > > of the existing unit tests will work without changes. Xerial is not
> a
> >> > > proper Java module at this time, and it uses JNI which could make it
> >> > tricky
> >> > > (especially if the goal is to use jlink).
> >> > >
> >> > > For me, the motivation here is to use Avro with modularized
> >> > > applications and custom runtime images using jlink.
> >> > >
> >> > > I currently have this working locally, and I can contribute my
> >> changes.
> >> > >
> >> > > Please let me know what you think.
> >> > >
> >> > > Thanks,
> >> > >
> >> > > Chad
> >> > >
> >> >
> >>
> >
>


-- 
Best regards / Met vriendelijke groeten,

Niels Basjes

Re: [PR] AVRO-3927: [Rust] fix array/map deserilaize with custom attribute [avro]

[via GitHub]

martin-g merged PR #2708:
URL: https://github.com/apache/avro/pull/2708


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [VOTE][LAZY] Support for UUIDs encoded as Fixed[16]

[Driesprong, Fokko]

I went ahead and merged the spec-update. Thanks everyone for the input, and
I'm looking forward to getting this out!

Kind regards, Fokko

Op wo 24 jan 2024 om 10:55 schreef Oscar Westra van Holthe - Kind <
opw...@apache.org>:

> +1 for UUIDs encoded as fixed from me as well.
>
> A already remarked, an automatic conversion from strings would be very
> helpful. However, this has a big influence on schema resolution and should
> be dealt with separately.
>
>
> Kind regards,
> Oscar
>
> --
> Oscar Westra van Holthe - Kind 
>
> Op di 23 jan. 2024 03:27 schreef Jack Klamer :
>
> > +1 for what it's worth.
> >
> > Although, it would be nice to also officially make fixed promotable
> strings
> > as well. Allowing old UUID string schema to read newer UUID encodings.
> >
> > Best,
> > Jack
> >
> > On Mon, Jan 22, 2024 at 1:40 PM Ryan Blue  wrote:
> >
> > > +1 for storing as 16-byte fixed.
> > >
> > > On Mon, Jan 22, 2024 at 1:44 AM Martin Grigorov 
> > > wrote:
> > >
> > > > I just want to add that it would be nice to add an interop test, e.g.
> > an
> > > > Avro file written by one SDK should be readable by the other SDKs.
> > > >
> > > > On Fri, Jan 19, 2024 at 11:58 AM Driesprong, Fokko
> >  > > >
> > > > wrote:
> > > >
> > > > > Hey everyone,
> > > > >
> > > > > Last December I proposed support for encoding UUIDs as fixed[16]
> > > > >  >,
> > as
> > > > > this
> > > > > has several advantages
> > > > > <
> > > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/16_oSWrEM7AFUCTe0uuraAEHxywezLfoEz5ahzwvhGUk/edit#heading=h.43xuauwfk7ow
> > > > > >.
> > > > > I know that this was over the holidays, so I would like to revisit
> > > this.
> > > > > Let me know if there are any questions or concerns, or feel free to
> > > jump
> > > > in
> > > > > on the PR . There are
> also
> > > > > implementations already for Java
> > > > >  (thanks
> > > > > Christophe!), and one for Rust (thanks Martin!). If there are no
> > > > concerns,
> > > > > I would like to move this forward next week, and also see if we can
> > > start
> > > > > the release process.
> > > > >
> > > > > Kind regards,
> > > > > Fokko
> > > > >
> > > >
> > >
> > >
> > > --
> > > Ryan Blue
> > > Tabular
> > >
> >
>

Re: [PR] AVRO-3918: Add support for UUID encoded as `fixed[16]` [avro]

[via GitHub]

Fokko merged PR #2672:
URL: https://github.com/apache/avro/pull/2672


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] AVRO-2987: pkg-config has a broken `Requires:` section [avro]

[via GitHub]

martin-g closed pull request #1018: AVRO-2987: pkg-config has a broken 
`Requires:` section
URL: https://github.com/apache/avro/pull/1018


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] AVRO-2989: lang/c: libsnappy has no pkg-config entry [avro]

[via GitHub]

martin-g closed pull request #1020: AVRO-2989: lang/c: libsnappy has no 
pkg-config entry
URL: https://github.com/apache/avro/pull/1020


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] AVRO-3932: [C] fix variable reference in CMakeLists.txt [avro]

[via GitHub]

martin-g merged PR #2713:
URL: https://github.com/apache/avro/pull/2713


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Created] (AVRO-3932) [C]: fix variable reference in CMakeLists.txt

[Martin Tzvetanov Grigorov (Jira)]

Martin Tzvetanov Grigorov created AVRO-3932:
---

 Summary: [C]: fix variable reference in CMakeLists.txt
 Key: AVRO-3932
 URL: https://issues.apache.org/jira/browse/AVRO-3932
 Project: Apache Avro
  Issue Type: Bug
  Components: c
Affects Versions: 1.11.3
Reporter: Martin Tzvetanov Grigorov
Assignee: Martin Tzvetanov Grigorov


https://github.com/apache/avro/pull/2713

{code}
@ZLIB_PKG@ can't be replaced as expected since we upgrade cmake from 2.4 to 3.1 
in this commit: 664c2fc.
You can find more details here: 
https://cmake.org/cmake/help/latest/policy/CMP0053.html.
So we should change @ZLIB_PKG@ to ${ZLIB_PKG} or add cmake_policy(SET CMP0053 
OLD)
{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)