notifications  

Messages by Thread

• [PR] fix(pyamber): reject empty tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): reject empty tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): reject empty tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): reject empty tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): reject empty tuples [texera] via GitHub
• [I] Optimized Python silently drops empty tuples [texera] via GitHub
  • Re: [I] Optimized Python silently drops empty tuples [texera] via GitHub
  • Re: [I] Optimized Python silently drops empty tuples [texera] via GitHub
  • Re: [I] Optimized Python silently drops empty tuples [texera] via GitHub
• [PR] fix(pyamber): reject non-string state keys [texera] via GitHub
  • Re: [PR] fix(pyamber): reject non-string state keys [texera] via GitHub
  • Re: [PR] fix(pyamber): reject non-string state keys [texera] via GitHub
  • Re: [PR] fix(pyamber): reject non-string state keys [texera] via GitHub
  • Re: [PR] fix(pyamber): reject non-string state keys [texera] via GitHub
• [I] State serialization can collapse distinct dictionary keys [texera] via GitHub
  • Re: [I] State serialization can collapse distinct dictionary keys [texera] via GitHub
  • Re: [I] State serialization can collapse distinct dictionary keys [texera] via GitHub
• [PR] fix(pyamber): escape state marker collisions [texera] via GitHub
  • Re: [PR] fix(pyamber): escape state marker collisions [texera] via GitHub
  • Re: [PR] fix(pyamber): escape state marker collisions [texera] via GitHub
  • Re: [PR] fix(pyamber): escape state marker collisions [texera] via GitHub
  • Re: [PR] fix(pyamber): escape state marker collisions [texera] via GitHub
• [I] State byte markers can overwrite user dictionaries [texera] via GitHub
  • Re: [I] State byte markers can overwrite user dictionaries [texera] via GitHub
  • Re: [I] State byte markers can overwrite user dictionaries [texera] via GitHub
• [PR] fix(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] fix(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] fix(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] fix(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] fix(pyamber): hash epoch timestamps on Windows [texera] via GitHub
• [I] Tuple hashing fails for local epoch timestamps on Windows [texera] via GitHub
  • Re: [I] Tuple hashing fails for local epoch timestamps on Windows [texera] via GitHub
  • Re: [I] Tuple hashing fails for local epoch timestamps on Windows [texera] via GitHub
• [PR] fix(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] fix(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] fix(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] fix(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] fix(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
• [I] Arrow tuple reading fails across different column chunk boundaries [texera] via GitHub
  • Re: [I] Arrow tuple reading fails across different column chunk boundaries [texera] via GitHub
  • Re: [I] Arrow tuple reading fails across different column chunk boundaries [texera] via GitHub
  • Re: [I] Arrow tuple reading fails across different column chunk boundaries [texera] via GitHub
• [PR] fix(pyamber): validate executor definitions [texera] via GitHub
  • Re: [PR] fix(pyamber): validate executor definitions [texera] via GitHub
  • Re: [PR] fix(pyamber): validate executor definitions [texera] via GitHub
  • Re: [PR] fix(pyamber): validate executor definitions [texera] via GitHub
  • Re: [PR] fix(pyamber): validate executor definitions [texera] via GitHub
• [I] Optimized Python accepts ambiguous operator definitions [texera] via GitHub
  • Re: [I] Optimized Python accepts ambiguous operator definitions [texera] via GitHub
  • Re: [I] Optimized Python accepts ambiguous operator definitions [texera] via GitHub
• [PR] fix(pyamber): validate table row fields [texera] via GitHub
  • Re: [PR] fix(pyamber): validate table row fields [texera] via GitHub
  • Re: [PR] fix(pyamber): validate table row fields [texera] via GitHub
  • Re: [PR] fix(pyamber): validate table row fields [texera] via GitHub
  • Re: [PR] fix(pyamber): validate table row fields [texera] via GitHub
• [I] Optimized Python can relabel inconsistent table fields [texera] via GitHub
  • Re: [I] Optimized Python can relabel inconsistent table fields [texera] via GitHub
  • Re: [I] Optimized Python can relabel inconsistent table fields [texera] via GitHub
• Re: [PR] feat(frontend): add model file upload and version creation [texera] via GitHub
  • Re: [PR] feat(frontend): add model file upload and version creation [texera] via GitHub
  • Re: [PR] feat(frontend): add model file upload and version creation [texera] via GitHub
  • Re: [PR] feat(frontend): add model file upload and version creation [texera] via GitHub
• [PR] fix(pyamber): validate materialization configuration [texera] via GitHub
  • Re: [PR] fix(pyamber): validate materialization configuration [texera] via GitHub
  • Re: [PR] fix(pyamber): validate materialization configuration [texera] via GitHub
  • Re: [PR] fix(pyamber): validate materialization configuration [texera] via GitHub
  • Re: [PR] fix(pyamber): validate materialization configuration [texera] via GitHub
• [I] Optimized Python silently truncates materialization inputs [texera] via GitHub
  • Re: [I] Optimized Python silently truncates materialization inputs [texera] via GitHub
  • Re: [I] Optimized Python silently truncates materialization inputs [texera] via GitHub
• [PR] fix(amber): exclude control channels from port alignment [texera] via GitHub
  • Re: [PR] fix(amber): exclude control channels from port alignment [texera] via GitHub
  • Re: [PR] fix(amber): exclude control channels from port alignment [texera] via GitHub
  • Re: [PR] fix(amber): exclude control channels from port alignment [texera] via GitHub
  • Re: [PR] fix(amber): exclude control channels from port alignment [texera] via GitHub
• [I] Control channels block data port alignment [texera] via GitHub
  • Re: [I] Control channels block data port alignment [texera] via GitHub
  • Re: [I] Control channels block data port alignment [texera] via GitHub
• [PR] fix(pyamber): avoid duplicate storage writers [texera] via GitHub
  • Re: [PR] fix(pyamber): avoid duplicate storage writers [texera] via GitHub
  • Re: [PR] fix(pyamber): avoid duplicate storage writers [texera] via GitHub
  • Re: [PR] fix(pyamber): avoid duplicate storage writers [texera] via GitHub
  • Re: [PR] fix(pyamber): avoid duplicate storage writers [texera] via GitHub
• [I] Repeated output port registration starts duplicate storage writers [texera] via GitHub
  • Re: [I] Repeated output port registration starts duplicate storage writers [texera] via GitHub
  • Re: [I] Repeated output port registration starts duplicate storage writers [texera] via GitHub
• [PR] fix(pyamber): remove stale channel membership [texera] via GitHub
  • Re: [PR] fix(pyamber): remove stale channel membership [texera] via GitHub
  • Re: [PR] fix(pyamber): remove stale channel membership [texera] via GitHub
  • Re: [PR] fix(pyamber): remove stale channel membership [texera] via GitHub
  • Re: [PR] fix(pyamber): remove stale channel membership [texera] via GitHub
• [I] Reassigned input channels remain in old port alignment sets [texera] via GitHub
  • Re: [I] Reassigned input channels remain in old port alignment sets [texera] via GitHub
  • Re: [I] Reassigned input channels remain in old port alignment sets [texera] via GitHub
• [PR] fix(pyamber): compare table row counts [texera] via GitHub
  • Re: [PR] fix(pyamber): compare table row counts [texera] via GitHub
  • Re: [PR] fix(pyamber): compare table row counts [texera] via GitHub
  • Re: [PR] fix(pyamber): compare table row counts [texera] via GitHub
  • Re: [PR] fix(pyamber): compare table row counts [texera] via GitHub
  • [PR] fix(pyamber): compare table row counts [texera] via GitHub
  • Re: [PR] fix(pyamber): compare table row counts [texera] via GitHub
  • Re: [PR] fix(pyamber): compare table row counts [texera] via GitHub
  • Re: [PR] fix(pyamber): compare table row counts [texera] via GitHub
  • Re: [PR] fix(pyamber): compare table row counts [texera] via GitHub
  • Re: [PR] fix(pyamber): compare table row counts [texera] via GitHub
  • Re: [PR] fix(pyamber): compare table row counts [texera] via GitHub
  • Re: [PR] fix(pyamber): compare table row counts [texera] via GitHub
• [I] Python tables with different row counts compare equal [texera] via GitHub
  • Re: [I] Python tables with different row counts compare equal [texera] via GitHub
  • Re: [I] Python tables with different row counts compare equal [texera] via GitHub
• [PR] fix(pyamber): keep empty Iceberg ranges empty [texera] via GitHub
  • Re: [PR] fix(pyamber): keep empty Iceberg ranges empty [texera] via GitHub
  • Re: [PR] fix(pyamber): keep empty Iceberg ranges empty [texera] via GitHub
  • Re: [PR] fix(pyamber): keep empty Iceberg ranges empty [texera] via GitHub
  • Re: [PR] fix(pyamber): keep empty Iceberg ranges empty [texera] via GitHub
• [I] Empty Iceberg range returns records [texera] via GitHub
  • Re: [I] Empty Iceberg range returns records [texera] via GitHub
  • Re: [I] Empty Iceberg range returns records [texera] via GitHub
  • Re: [I] Empty Iceberg range returns records [texera] via GitHub
• [PR] fix(pyamber): preserve VFS resource type case [texera] via GitHub
  • Re: [PR] fix(pyamber): preserve VFS resource type case [texera] via GitHub
  • Re: [PR] fix(pyamber): preserve VFS resource type case [texera] via GitHub
  • Re: [PR] fix(pyamber): preserve VFS resource type case [texera] via GitHub
  • Re: [PR] fix(pyamber): preserve VFS resource type case [texera] via GitHub
• [I] Python VFS decoder rejects runtime statistics and console message URIs [texera] via GitHub
  • Re: [I] Python VFS decoder rejects runtime statistics and console message URIs [texera] via GitHub
  • Re: [I] Python VFS decoder rejects runtime statistics and console message URIs [texera] via GitHub
• [PR] fix(pyamber): flush broadcast batch to all receivers [texera] via GitHub
  • Re: [PR] fix(pyamber): flush broadcast batch to all receivers [texera] via GitHub
  • Re: [PR] fix(pyamber): flush broadcast batch to all receivers [texera] via GitHub
  • Re: [PR] fix(pyamber): flush broadcast batch to all receivers [texera] via GitHub
  • Re: [PR] fix(pyamber): flush broadcast batch to all receivers [texera] via GitHub
• [I] Broadcast flush drops pending tuples for later receivers [texera] via GitHub
  • Re: [I] Broadcast flush drops pending tuples for later receivers [texera] via GitHub
  • Re: [I] Broadcast flush drops pending tuples for later receivers [texera] via GitHub
• [PR] fix(pyamber): clear flushed shuffle batches [texera] via GitHub
  • Re: [PR] fix(pyamber): clear flushed shuffle batches [texera] via GitHub
  • Re: [PR] fix(pyamber): clear flushed shuffle batches [texera] via GitHub
  • Re: [PR] fix(pyamber): clear flushed shuffle batches [texera] via GitHub
  • Re: [PR] fix(pyamber): clear flushed shuffle batches [texera] via GitHub
• [I] Hash and range flushes resend pending tuples [texera] via GitHub
  • Re: [I] Hash and range flushes resend pending tuples [texera] via GitHub
  • Re: [I] Hash and range flushes resend pending tuples [texera] via GitHub
• [PR] fix(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): hash large binary tuples [texera] via GitHub
  • [PR] fix(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] fix(pyamber): hash large binary tuples [texera] via GitHub
• Re: [PR] feat(agent-service): add stateless /recommend endpoint (V1 hardcoded) [texera] via GitHub
  • Re: [PR] feat(agent-service): add stateless /recommend endpoint (V1 hardcoded) [texera] via GitHub
• Re: [PR] fix(sync): handle missing position events without breaking sync stream [texera] via GitHub
  • Re: [PR] fix(sync): handle missing position events without breaking sync stream [texera] via GitHub
  • Re: [PR] fix(sync): handle missing position events without breaking sync stream [texera] via GitHub
• Re: [PR] fix(frontend): prevent editing description without write access [texera] via GitHub
  • Re: [PR] fix(frontend): prevent editing description without write access [texera] via GitHub
  • Re: [PR] fix(frontend): prevent editing description without write access [texera] via GitHub
• [I] Hash partitioning crashes on LARGE_BINARY keys [texera] via GitHub
  • Re: [I] Hash partitioning crashes on LARGE_BINARY keys [texera] via GitHub
  • Re: [I] Hash partitioning crashes on LARGE_BINARY keys [texera] via GitHub
• [PR] fix(pyamber): include schema in tuple equality [texera] via GitHub
  • Re: [PR] fix(pyamber): include schema in tuple equality [texera] via GitHub
  • Re: [PR] fix(pyamber): include schema in tuple equality [texera] via GitHub
  • Re: [PR] fix(pyamber): include schema in tuple equality [texera] via GitHub
  • Re: [PR] fix(pyamber): include schema in tuple equality [texera] via GitHub
• [I] Python tuples ignore schema during equality checks [texera] via GitHub
  • Re: [I] Python tuples ignore schema during equality checks [texera] via GitHub
  • Re: [I] Python tuples ignore schema during equality checks [texera] via GitHub
• [I] Add unit test coverage for the replay-log writer and manager [texera] via GitHub
  • Re: [I] Add unit test coverage for the replay-log writer and manager [texera] via GitHub
• [PR] fix(pyamber): hash strings as UTF-16 [texera] via GitHub
  • Re: [PR] fix(pyamber): hash strings as UTF-16 [texera] via GitHub
  • Re: [PR] fix(pyamber): hash strings as UTF-16 [texera] via GitHub
  • Re: [PR] fix(pyamber): hash strings as UTF-16 [texera] via GitHub
  • Re: [PR] fix(pyamber): hash strings as UTF-16 [texera] via GitHub
• [I] Python Unicode hashes disagree with Scala for supplementary characters [texera] via GitHub
  • Re: [I] Python Unicode hashes disagree with Scala for supplementary characters [texera] via GitHub
  • Re: [I] Python Unicode hashes disagree with Scala for supplementary characters [texera] via GitHub
• [PR] fix(pyamber): hash binary bytes as signed [texera] via GitHub
  • Re: [PR] fix(pyamber): hash binary bytes as signed [texera] via GitHub
  • Re: [PR] fix(pyamber): hash binary bytes as signed [texera] via GitHub
  • Re: [PR] fix(pyamber): hash binary bytes as signed [texera] via GitHub
  • Re: [PR] fix(pyamber): hash binary bytes as signed [texera] via GitHub
• [I] Python binary hashes disagree with Scala for non-ASCII bytes [texera] via GitHub
  • Re: [I] Python binary hashes disagree with Scala for non-ASCII bytes [texera] via GitHub
  • Re: [I] Python binary hashes disagree with Scala for non-ASCII bytes [texera] via GitHub
• [PR] test(frontend): close eight small service and component gaps [texera] via GitHub
  • Re: [PR] test(frontend): close eight small service and component gaps [texera] via GitHub
  • Re: [PR] test(frontend): close eight small service and component gaps [texera] via GitHub
  • Re: [PR] test(frontend): close eight small service and component gaps [texera] via GitHub
  • Re: [PR] test(frontend): close eight small service and component gaps [texera] via GitHub
  • Re: [PR] test(frontend): close eight small service and component gaps [texera] via GitHub
  • Re: [PR] test(frontend): close eight small service and component gaps [texera] via GitHub

• Earlier messages
• Later messages