commits  

Messages by Thread

• • Re: [PR] perf(python): Directly access the key-value pairs of a dict [fury] via GitHub
  • Re: [PR] perf(python): Directly access the key-value pairs of a dict [fury] via GitHub
  • Re: [PR] perf(python): Directly access the key-value pairs of a dict [fury] via GitHub
• Re: [D] How to provide a custom string ID for class registration rather than int ID? [fury] via GitHub
  • Re: [D] How to provide a custom string ID for class registration rather than int ID? [fury] via GitHub
  • Re: [D] How to provide a custom string ID for class registration rather than int ID? [fury] via GitHub
  • Re: [D] How to provide a custom string ID for class registration rather than int ID? [fury] via GitHub
  • Re: [D] How to provide a custom string ID for class registration rather than int ID? [fury] via GitHub
• (fury) branch main updated: feat(java): configurable buffer size limit (#1963) chaokunyang
• Re: [I] [Scala] Expose register on ThreadSafeFury [fury] via GitHub
• [PR] fix(java): Fix flakiness in ExpressionVisitorTest#testTraverseExpression [fury] via GitHub
  • Re: [PR] fix(java): Fix flakiness in ExpressionVisitorTest#testTraverseExpression [fury] via GitHub
  • Re: [PR] fix(java): Fix flakiness in ExpressionVisitorTest#testTraverseExpression [fury] via GitHub
  • Re: [PR] fix(java): Fix flakiness in ExpressionVisitorTest#testTraverseExpression [fury] via GitHub
• [I] [Python] support latin1/utf16 encoding for python string [fury] via GitHub
  • Re: [I] [Python] support latin1/utf16 encoding for python string [fury] via GitHub
  • Re: [I] [Python] support latin1/utf16 encoding for python string [fury] via GitHub
  • Re: [I] [Python] support latin1/utf16 encoding for python string [fury] via GitHub
  • Re: [I] [Python] support latin1/utf16 encoding for python string [fury] via GitHub
• Re: [I] [Scala] support default not-null value in COMPATIBLE mode. [fury] via GitHub
• [I] [Kotlin] Kotlin default value support in CompatibleMode [fury] via GitHub
  • Re: [I] [Kotlin] Kotlin default value support in CompatibleMode [fury] via GitHub
• (fury-site) branch main updated: Update companies.json chaokunyang
• (fury-site) branch main updated: add quarkus adrestus (#204) chaokunyang
• [PR] add quarkus adrestus [fury-site] via GitHub
  • Re: [PR] add quarkus adrestus [fury-site] via GitHub
• Re: [I] [Question] How to register a custom serializer with ThreadSafeFury? [fury] via GitHub
  • Re: [I] [Question] How to register a custom serializer with ThreadSafeFury? [fury] via GitHub
  • Re: [I] [Question] How to register a custom serializer with ThreadSafeFury? [fury] via GitHub
• [I] [C++] To support the utf8 utf16 and using simd to accelerate the optimization [fury] via GitHub
  • Re: [I] [C++] To support the utf8 utf16 and using simd to accelerate the optimization [fury] via GitHub
  • Re: [I] [C++] To support the utf8 utf16 and using simd to accelerate the optimization [fury] via GitHub
• [PR] feat(java): configurable buffer size limit [fury] via GitHub
  • Re: [PR] feat(java): configurable buffer size limit [fury] via GitHub
  • Re: [PR] feat(java): configurable buffer size limit [fury] via GitHub
• (fury) branch main updated: feat(java): use varint for jdk compatible serializers (#1960) chaokunyang
• (fury) branch main updated: chore(Rust): fix lint problems (#1962) chaokunyang
• [PR] chore(Rust): fix lint problems [fury] via GitHub
  • Re: [PR] chore(Rust): fix lint problems [fury] via GitHub
• [I] Fury Rust compile error [fury] via GitHub
• [PR] feat(java): use varint for jdk compatible serializers [fury] via GitHub
  • Re: [PR] feat(java): use varint for jdk compatible serializers [fury] via GitHub
• [I] When using `buildThreadSafeFuryPool(10, 60)` for init ThreadSafePool, the following exception occurs: [fury] via GitHub
  • Re: [I] When using `buildThreadSafeFuryPool(10, 60)` for init ThreadSafePool, the following exception occurs: [fury] via GitHub
• [I] [Question] <title>Can MemoryBuffer achieve a smaller size than arrays? Does it support automatic garbage collection? Is there documentation for using MemoryBuffer? [fury] via GitHub
  • Re: [I] [Question] <title>When I serialize this object, enough space is allocated, but it still throws a java.lang.OutOfMemoryError: Java heap space [fury] via GitHub
  • Re: [I] [Question] <title>When I serialize this object, enough space is allocated, but it still throws a java.lang.OutOfMemoryError: Java heap space [fury] via GitHub
  • Re: [I] [Question] <title>When I serialize this object, enough space is allocated, but it still throws a java.lang.OutOfMemoryError: Java heap space [fury] via GitHub
  • Re: [I] [Question] <title>When I serialize this object, enough space is allocated, but it still throws a java.lang.OutOfMemoryError: Java heap space [fury] via GitHub
  • Re: [I] [Question] <title>When I serialize this object, enough space is allocated, but it still throws a java.lang.OutOfMemoryError: Java heap space [fury] via GitHub
  • Re: [I] [Question] <title>When I serialize this object, enough space is allocated, but it still throws a java.lang.OutOfMemoryError: Java heap space [fury] via GitHub
  • Re: [I] [Question] <title>When I serialize this object, enough space is allocated, but it still throws a java.lang.OutOfMemoryError: Java heap space [fury] via GitHub
  • Re: [I] [Question] <title>When I serialize this object, enough space is allocated, but it still throws a java.lang.OutOfMemoryError: Java heap space [fury] via GitHub
  • Re: [I] [Question] <title>When I serialize this object, enough space is allocated, but it still throws a java.lang.OutOfMemoryError: Java heap space [fury] via GitHub
  • Re: [I] [Question] <title>When I serialize this object, enough space is allocated, but it still throws a java.lang.OutOfMemoryError: Java heap space [fury] via GitHub
• Re: [I] Who is Using Apache Fury? [fury] via GitHub
  • Re: [I] Who is Using Apache Fury? [fury] via GitHub
  • Re: [I] Who is Using Apache Fury? [fury] via GitHub
• [I] [RFC] Remove pyfury python implementation, use pure cython only [fury] via GitHub
  • Re: [I] Remove most pyfury pure python serializers, use pure cython only [fury] via GitHub
• [I] [Java] Type annotation hints for serialization [fury] via GitHub
• [I] Deserialization creates duplicate instances [fury] via GitHub
  • Re: [I] Deserialization creates duplicate instances [fury] via GitHub
  • Re: [I] Deserialization creates duplicate instances [fury] via GitHub
  • Re: [I] Deserialization creates duplicate instances [fury] via GitHub
  • Re: [I] Deserialization creates duplicate instances [fury] via GitHub
• Re: [I] [Question] <title>How does Fury perform in terms of speed and size when serializing and deserializing Java arrays? [fury] via GitHub
  • Re: [I] [Question] <title>How does Fury perform in terms of speed and size when serializing and deserializing Java arrays? [fury] via GitHub
• [I] [Question] <title>What does java.lang.RuntimeException: Deserialize failed, type of read objects are: [... [fury] via GitHub
  • Re: [I] [Question] <title>What does java.lang.RuntimeException: Deserialize failed, type of read objects are: [... [fury] via GitHub
  • Re: [I] [Question] <title>What does java.lang.RuntimeException: Deserialize failed, type of read objects are: [... [fury] via GitHub
  • Re: [I] [Question] <title>What does java.lang.RuntimeException: Deserialize failed, type of read objects are: [... [fury] via GitHub
  • Re: [I] [Question] <title>What does java.lang.RuntimeException: Deserialize failed, type of read objects are: [... [fury] via GitHub
  • Re: [I] [Question] <title>What does java.lang.RuntimeException: Deserialize failed, type of read objects are: [... [fury] via GitHub
  • Re: [I] [Question] <title>What does java.lang.RuntimeException: Deserialize failed, type of read objects are: [... [fury] via GitHub
  • Re: [I] [Question] <title>What does java.lang.RuntimeException: Deserialize failed, type of read objects are: [... [fury] via GitHub
  • Re: [I] [Question] <title>What does java.lang.RuntimeException: Deserialize failed, type of read objects are: [... [fury] via GitHub
  • Re: [I] [Question] <title>What does java.lang.RuntimeException: Deserialize failed, type of read objects are: [... [fury] via GitHub
• (fury) branch main updated: fix(java): fix find constructor error in generated serializer class caused by duplicated class classloading for Fury (#1948) chaokunyang
• [I] [Question] <title>is content type defined and standardized? [fury] via GitHub
  • Re: [I] [Question] is content type defined and standardized? [fury] via GitHub
  • Re: [I] [Question] is content type defined and standardized? [fury] via GitHub
  • Re: [I] [Question] is content type defined and standardized? [fury] via GitHub
  • Re: [I] [Question] is content type defined and standardized? [fury] via GitHub
• [I] [Question] [Java]: Configurable buffer size limit [fury] via GitHub
  • Re: [I] [Java] Configurable buffer size limit [fury] via GitHub
  • Re: [I] [Java] Configurable buffer size limit [fury] via GitHub
  • Re: [I] [Java] Configurable buffer size limit [fury] via GitHub
• [I] Flink types serialization codegen error: no such constructor: org.apache.flink.table.data.binary.BinaryStringDataFuryCodec_0.<init>(Fury,Class)void/invokeSpecial [fury] via GitHub
  • Re: [I] Flink types serialization codegen error: no such constructor: org.apache.flink.table.data.binary.BinaryStringDataFuryCodec_0.<init>(Fury,Class)void/invokeSpecial [fury] via GitHub
  • Re: [I] Flink types serialization codegen error: no such constructor: org.apache.flink.table.data.binary.BinaryStringDataFuryCodec_0.<init>(Fury,Class)void/invokeSpecial [fury] via GitHub
• [PR] perf(python): Pre-allocate size for the dictionary [fury] via GitHub
  • Re: [PR] perf(python): Pre-allocate size for the dictionary [fury] via GitHub
• (fury) branch main updated: perf(python): Pre-allocate size for the dictionary (#1949) chaokunyang
• [PR] fix(java): fix duplicate classloading in flink user classloader [fury] via GitHub
  • Re: [PR] fix(java): fix find constructor error in generated serializer class caused by duplicated class classloading for Fury [fury] via GitHub
• (fury) branch main updated: fix(java): ClassLoaderFuryPooled#setFactoryCallback cannot effect old Fury (#1946) chaokunyang
• [PR] fix(java):ClassLoaderFuryPooled#setFactoryCallback cannot effect old Fury [fury] via GitHub
  • Re: [PR] fix(java): ClassLoaderFuryPooled#setFactoryCallback cannot effect old Fury [fury] via GitHub
• Re: [I] [Question] Could use Python bindings instead of Cython [fury] via GitHub
  • Re: [I] [Question] Could use Python bindings instead of Cython [fury] via GitHub
  • Re: [I] [Question] Could use Python bindings instead of Cython [fury] via GitHub
  • Re: [I] [Question] Could use Python bindings instead of Cython [fury] via GitHub
  • Re: [I] [Question] Could use Python bindings instead of Cython [fury] via GitHub
  • Re: [I] [Question] Could use Python bindings instead of Cython [fury] via GitHub
  • Re: [I] [Question] Could use Python bindings instead of Cython [fury] via GitHub
• (fury) branch main updated: fix(java): Move schema caching to unsafe trait to avoid issues when using non-inferred schema. (#1944) chaokunyang
• [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
  • Re: [I] [Question] For the Java PB object generated by Protobuf, the serialization and deserialization using Fury are slower than using Protobuf. [fury] via GitHub
• [PR] fix(java): Move schema caching to unsafe trait to avoid issues when using non-inferred schema. [fury] via GitHub
  • Re: [PR] fix(java): Move schema caching to unsafe trait to avoid issues when using non-inferred schema. [fury] via GitHub
• (fury) branch main updated: feat(python): Implement collection serialization protocol (#1942) chaokunyang
• [I] [Java] ReplaceResolveSerializer circular references copy bug [fury] via GitHub
• [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
  • Re: [PR] feat(python): Implement collection serialization protocol [fury] via GitHub
• Re: [PR] feat(python): guide cython to optimize code generation [fury] via GitHub
• Re: [I] 【Java】remove guava jar reference [fury] via GitHub
• [I] `radial_scale` parameter of `actor.odf_slicer` has some issues [fury] via GitHub
  • Re: [I] `radial_scale` parameter of `actor.odf_slicer` has some issues [fury] via GitHub
  • Re: [I] `radial_scale` parameter of `actor.odf_slicer` has some issues [fury] via GitHub
  • Re: [I] `radial_scale` parameter of `actor.odf_slicer` has some issues [fury] via GitHub
  • Re: [I] `radial_scale` parameter of `actor.odf_slicer` has some issues [fury] via GitHub
  • Re: [I] `radial_scale` parameter of `actor.odf_slicer` has some issues [fury] via GitHub
• (fury-site) branch main updated: Update 2024-11-10-fury_0_9_0_release.md (#203) chaokunyang
• (fury-site) branch chaokunyang-patch-2 created (now a01cf73f) chaokunyang
  • (fury-site) 01/01: Update 2024-11-10-fury_0_9_0_release.md chaokunyang
• [PR] Update 2024-11-10-fury_0_9_0_release.md [fury-site] via GitHub
  • Re: [PR] Update 2024-11-10-fury_0_9_0_release.md [fury-site] via GitHub
• (fury-site) branch chaokunyang-patch-2 deleted (was a01cf73f) chaokunyang
• (fury-site) branch main updated: Fix：CSS media queries solve mobile adaptation issues (#202) chaokunyang
• [PR] Fix：CSS media queries solve mobile adaptation issues [fury-site] via GitHub
  • Re: [PR] Fix：CSS media queries solve mobile adaptation issues [fury-site] via GitHub
• (fury) branch main updated: chore: bump release version to 0.9.0 (#1940) chaokunyang
• [GH] (fury): Workflow run "❄️ Lint" is working again! GitBox
  • [GH] (fury): Workflow run "❄️ Lint" is working again! GitBox
  • [GH] (fury): Workflow run "❄️ Lint" is working again! GitBox
  • [GH] (fury): Workflow run "❄️ Lint" is working again! GitBox
  • [GH] (fury): Workflow run "❄️ Lint" is working again! GitBox
  • [GH] (fury): Workflow run "❄️ Lint" is working again! GitBox
  • [GH] (fury): Workflow run "❄️ Lint" is working again! GitBox
  • [GH] (fury): Workflow run "❄️ Lint" is working again! GitBox
  • [GH] (fury): Workflow run "❄️ Lint" is working again! GitBox
  • [GH] (fury): Workflow run "❄️ Lint" is working again! GitBox
  • [GH] (fury): Workflow run "❄️ Lint" is working again! GitBox
  • [GH] (fury): Workflow run "❄️ Lint" is working again! GitBox
• Re: [PR] Fix：SSR issue by wrapping client-side code with <BrowserOnly> in HomePageLanguageCard [fury-site] via GitHub
  • Re: [PR] Fix：SSR issue by wrapping client-side code with <BrowserOnly> in HomePageLanguageCard [fury-site] via GitHub
• (fury-site) branch main updated: release fury 0.9.0 (#200) chaokunyang
• [GH] (fury-site): Workflow run "Deploy" is working again! GitBox
  • [GH] (fury-site): Workflow run "Deploy" is working again! GitBox
• [I] [Site]: navigator break website build [fury-site] via GitHub
  • Re: [I] [Site]: navigator break website build [fury-site] via GitHub
  • Re: [I] [Site]: navigator break website build [fury-site] via GitHub
  • Re: [I] [Site]: navigator break website build [fury-site] via GitHub
  • Re: [I] [Site]: navigator break website build [fury-site] via GitHub
• [GH] (fury): Workflow run "❄️ Lint" failed! GitBox

• Earlier messages
• Later messages