[GH] (fury): Workflow run "Fury CI" is working again!

2025-01-08 Thread GitBox
The GitHub Actions job "Fury CI" on fury.git has succeeded. Run started by GitHub user theweipeng (triggered by theweipeng). Head commit for run: d6c2c9d8e29a8c102573160369a89ca5e4a4c44a / weipeng feat: removed HPS because we can now use --expose_externalize_string to detect the encoding of a

Re: [PR] feat(javascript): removing HPS [fury]

2025-01-08 Thread via GitHub
chaokunyang commented on PR #2001: URL: https://github.com/apache/fury/pull/2001#issuecomment-2579354917 @theweipeng Should we still keep `hps` since https://github.com/nodejs/node/pull/56147 will be available for newer nodejs version? -- This is an automated message from the Apache Git

[GH] (fury): Workflow run "Fury CI" failed!

2025-01-08 Thread GitBox
The GitHub Actions job "Fury CI" on fury.git has failed. Run started by GitHub user theweipeng (triggered by theweipeng). Head commit for run: 55fd23f5bc8b75499927039563d4a4bee0ff36fa / weipeng feat: removed HPS because we can now use --expose_externalize_string to detect the encoding of a str

[PR] feat(javascript): removing HPS [fury]

2025-01-08 Thread via GitHub
theweipeng opened a new pull request, #2001: URL: https://github.com/apache/fury/pull/2001 ## What does this PR do? Removed HPS because we can now use `--expose_externalize_string` to detect the encoding of a string. Additionally, we have submitted a PR (https://github.com/nodejs/nod

[GH] (fury): Workflow run "Fury CI" failed!

2025-01-08 Thread GitBox
The GitHub Actions job "Fury CI" on fury.git has failed. Run started by GitHub user chaokunyang (triggered by chaokunyang). Head commit for run: bc9af7f17d50aa2bf77c866ccca6490c15064eaf / chaokunyang add more tests Report URL: https://github.com/apache/fury/actions/runs/12674051942 With regar

[GH] (fury): Workflow run "Fury CI" failed!

2025-01-08 Thread GitBox
The GitHub Actions job "Fury CI" on fury.git has failed. Run started by GitHub user chaokunyang (triggered by chaokunyang). Head commit for run: bc9af7f17d50aa2bf77c866ccca6490c15064eaf / chaokunyang add more tests Report URL: https://github.com/apache/fury/actions/runs/12674051942 With regar

[GH] (fury): Workflow run "Fury CI" failed!

2025-01-08 Thread GitBox
The GitHub Actions job "Fury CI" on fury.git has failed. Run started by GitHub user chaokunyang (triggered by chaokunyang). Head commit for run: ee4bbd06be9eb7d97f1adc0863d3f1987f57c9e5 / chaokunyang add vectorized isLatin1 check function Report URL: https://github.com/apache/fury/actions/runs

Re: [PR] feat(c++): add simd accelerated c++ ascii/latin1 check funcion [fury]

2025-01-08 Thread via GitHub
chaokunyang commented on PR #1999: URL: https://github.com/apache/fury/pull/1999#issuecomment-2577884346 @pandalee99 latin1 check function alse added -- 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

Re: [PR] feat(c++): add simd accelerated c++ ascii check funcion [fury]

2025-01-08 Thread via GitHub
chaokunyang commented on PR #1999: URL: https://github.com/apache/fury/pull/1999#issuecomment-2577823419 > @chaokunyang Maybe,This feature is already implemented in `string_util.cc` > > ```c++ > bool isLatin(const std::string &str) { > const char *data = str.data(); > size

[GH] (fury): Workflow run "Fury CI" failed!

2025-01-08 Thread GitBox
The GitHub Actions job "Fury CI" on fury.git has failed. Run started by GitHub user chaokunyang (triggered by theweipeng). Head commit for run: d9655a4a3a4456ef10145d93f7a6478f80295943 / chaokunyang fix test Report URL: https://github.com/apache/fury/actions/runs/12671304833 With regards, Git

[GH] (fury): Workflow run "Fury CI" failed!

2025-01-08 Thread GitBox
The GitHub Actions job "Fury CI" on fury.git has failed. Run started by GitHub user chaokunyang (triggered by theweipeng). Head commit for run: d9655a4a3a4456ef10145d93f7a6478f80295943 / chaokunyang fix test Report URL: https://github.com/apache/fury/actions/runs/12671304833 With regards, Git

[GH] (fury): Workflow run "Lint PR" is working again!

2025-01-08 Thread GitBox
The GitHub Actions job "Lint PR" on fury.git has succeeded. Run started by GitHub user chaokunyang (triggered by chaokunyang). Head commit for run: d9655a4a3a4456ef10145d93f7a6478f80295943 / chaokunyang fix test Report URL: https://github.com/apache/fury/actions/runs/12671603740 With regards,

[I] [Nodejs] npm install failed on CI [fury]

2025-01-08 Thread via GitHub
chaokunyang opened a new issue, #2000: URL: https://github.com/apache/fury/issues/2000 ### Search before asking - [X] I had searched in the [issues](https://github.com/apache/fury/issues) and found no similar issues. ### Version main ### Component(s) Ja

[GH] (fury): Workflow run "Fury CI" failed!

2025-01-08 Thread GitBox
The GitHub Actions job "Fury CI" on fury.git has failed. Run started by GitHub user chaokunyang (triggered by chaokunyang). Head commit for run: d9655a4a3a4456ef10145d93f7a6478f80295943 / chaokunyang fix test Report URL: https://github.com/apache/fury/actions/runs/12671304833 With regards, Gi

[GH] (fury): Workflow run "Lint PR" failed!

2025-01-08 Thread GitBox
The GitHub Actions job "Lint PR" on fury.git has failed. Run started by GitHub user chaokunyang (triggered by chaokunyang). Head commit for run: d9655a4a3a4456ef10145d93f7a6478f80295943 / chaokunyang fix test Report URL: https://github.com/apache/fury/actions/runs/12671304626 With regards, Gi

[PR] c++(feat): add simd accelerated c++ ascii check funcion [fury]

2025-01-08 Thread via GitHub
chaokunyang opened a new pull request, #1999: URL: https://github.com/apache/fury/pull/1999 ## What does this PR do? add simd accelerated c++ ascii check funcion ## Related issues ## Does this PR introduce any user-facing change? - [ ] Does

[GH] (fury): Workflow run "Lint PR" failed!

2025-01-08 Thread GitBox
The GitHub Actions job "Lint PR" on fury.git has failed. Run started by GitHub user chaokunyang (triggered by chaokunyang). Head commit for run: d209c7ed75549fb59860408ca9151db16bb64e90 / chaokunyang add simd accelerated c++ ascii check funcion Report URL: https://github.com/apache/fury/action

Re: [I] [Java] Deserializing one pojo into another type [fury]

2025-01-08 Thread via GitHub
chaokunyang commented on issue #1998: URL: https://github.com/apache/fury/issues/1998#issuecomment-2577045468 cc @orisgarno -- 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.

Re: [PR] fix(java): Compatible mode on de/serialize api failed to deserialize [fury]

2025-01-08 Thread via GitHub
chaokunyang commented on PR #1996: URL: https://github.com/apache/fury/pull/1996#issuecomment-2577025783 #1870 is handling field type inconsistency, here we are handling pojo root type inconsistentcy, they are different issue -- This is an automated message from the Apache Git Service

[I] [Java] Deserializing one pojo into another type [fury]

2025-01-08 Thread via GitHub
chaokunyang opened a new issue, #1998: URL: https://github.com/apache/fury/issues/1998 ### Feature Request Continuing the discussion in https://github.com/apache/fury/issues/1972#issuecomment-2569043551, we need to support deserializing one pojo into another type without the need to