text:
bug: panicked at 'write epoch must greater than max current epoch

Describe the bug
Three CNs panic when running nexmark q7 with 2 compactors for 2 hours:

CN1:

thread 'risingwave-streaming-actor' panicked at 'write epoch must greater than max current epoch, write epoch3003390916427776, sealed epoch3003390916427776', src/storage/src/hummock/local_version_manager.rs:421:9
stack backtrace:
   0: rust_begin_unwind
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/panicking.rs:142:14
   2: risingwave_storage::hummock::local_version_manager::LocalVersionManager::write_shared_buffer_inner
             at ./ebs/risingwave/src/storage/src/hummock/local_version_manager.rs:421:9
   3: risingwave_storage::hummock::local_version_manager::LocalVersionManager::write_shared_buffer::{{closure}}
             at ./ebs/risingwave/src/storage/src/hummock/local_version_manager.rs:403:13
   4: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
   5: risingwave_storage::hummock::state_store::<impl risingwave_storage::store::StateStore for risingwave_storage::hummock::HummockStorage>::ingest_batch::{{closure}}
             at ./ebs/risingwave/src/storage/src/hummock/state_store.rs:504:18
   6: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
   7: <async_stack_trace::StackTraced<F> as core::future::future::Future>::poll
             at ./ebs/risingwave/src/utils/async_stack_trace/src/lib.rs:172:23
   8: <futures_util::future::future::fuse::Fuse<Fut> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/future/future/fuse.rs:86:37
   9: <risingwave_storage::monitor::monitored_store::MonitoredStateStore<S> as risingwave_storage::store::StateStore>::ingest_batch::{{closure}}
             at ./ebs/risingwave/src/storage/src/monitor/monitored_store.rs:194:51
  10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  11: risingwave_storage::write_batch::WriteBatch<S>::ingest::{{closure}}
             at ./ebs/risingwave/src/storage/src/write_batch.rs:91:58
  12: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  13: risingwave_storage::write_batch::KeySpaceWriteBatch<S>::ingest::{{closure}}
             at ./ebs/risingwave/src/storage/src/write_batch.rs:150:29
  14: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  15: risingwave_stream::executor::source::state::SourceStateHandler<S>::take_snapshot::{{closure}}
             at ./ebs/risingwave/src/stream/src/executor/source/state.rs:75:33
  16: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  17: risingwave_stream::executor::source::source_executor::SourceExecutor<S>::take_snapshot::{{closure}}
             at ./ebs/risingwave/src/stream/src/executor/source/source_executor.rs:214:63
  18: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  19: risingwave_stream::executor::source::source_executor::SourceExecutor<S>::into_stream::{{closure}}
             at ./ebs/risingwave/src/stream/src/executor/source/source_executor.rs:349:47
  20: <futures_async_stream::try_stream::from_generator::GenTryStream<G> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-async-stream-0.2.5/src/lib.rs:430:31
  21: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:120:9
  22: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:120:9
  23: futures_util::stream::stream::StreamExt::poll_next_unpin
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/mod.rs:1626:9
  24: <futures_util::stream::stream::next::Next<St> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/next.rs:32:9
  25: risingwave_stream::executor::wrapper::trace::metrics::{{closure}}
             at ./ebs/risingwave/src/stream/src/executor/wrapper/trace.rs:86:44
  26: <futures_async_stream::try_stream::from_generator::GenTryStream<G> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-async-stream-0.2.5/src/lib.rs:430:31
  27: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:120:9
  28: futures_util::stream::stream::StreamExt::poll_next_unpin
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/mod.rs:1626:9
  29: <futures_util::stream::stream::next::Next<St> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/next.rs:32:9
  30: <async_stack_trace::StackTraced<F> as core::future::future::Future>::poll
             at ./ebs/risingwave/src/utils/async_stack_trace/src/lib.rs:172:23
  31: <futures_util::future::future::fuse::Fuse<Fut> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/future/future/fuse.rs:86:37
  32: risingwave_stream::executor::wrapper::trace::stack_trace::{{closure}}
             at ./ebs/risingwave/src/stream/src/executor/wrapper/trace.rs:120:70
  33: <futures_async_stream::try_stream::from_generator::GenTryStream<G> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-async-stream-0.2.5/src/lib.rs:430:31
  34: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:120:9
  35: futures_util::stream::stream::StreamExt::poll_next_unpin
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/mod.rs:1626:9
  36: <futures_util::stream::stream::next::Next<St> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/next.rs:32:9
  37: risingwave_stream::executor::wrapper::epoch_check::epoch_check::{{closure}}
             at ./ebs/risingwave/src/stream/src/executor/wrapper/epoch_check.rs:31:44
  38: <futures_async_stream::try_stream::from_generator::GenTryStream<G> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-async-stream-0.2.5/src/lib.rs:430:31
  39: <core::pin::Pin<P> as core::future::future::Future>::poll
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/future.rs:124:9
  40: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:120:9
  41: risingwave_stream::executor::simple::SimpleExecutorWrapper<E>::execute_inner::{{closure}}
             at ./ebs/risingwave/src/stream/src/executor/simple.rs:69:5
  42: <futures_async_stream::try_stream::from_generator::GenTryStream<G> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-async-stream-0.2.5/src/lib.rs:430:31
  43: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:120:9
  44: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:120:9
  45: futures_util::stream::stream::StreamExt::poll_next_unpin
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/mod.rs:1626:9
  46: <futures_util::stream::stream::next::Next<St> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/next.rs:32:9
  47: risingwave_stream::executor::wrapper::trace::metrics::{{closure}}
             at ./ebs/risingwave/src/stream/src/executor/wrapper/trace.rs:86:44
  48: <futures_async_stream::try_stream::from_generator::GenTryStream<G> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-async-stream-0.2.5/src/lib.rs:430:31
  49: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:120:9
  50: futures_util::stream::stream::StreamExt::poll_next_unpin
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/mod.rs:1626:9
  51: <futures_util::stream::stream::next::Next<St> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/next.rs:32:9
  52: <async_stack_trace::StackTraced<F> as core::future::future::Future>::poll
             at ./ebs/risingwave/src/utils/async_stack_trace/src/lib.rs:172:23
  53: <futures_util::future::future::fuse::Fuse<Fut> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/future/future/fuse.rs:86:37
  54: risingwave_stream::executor::wrapper::trace::stack_trace::{{closure}}
             at ./ebs/risingwave/src/stream/src/executor/wrapper/trace.rs:120:70
  55: <futures_async_stream::try_stream::from_generator::GenTryStream<G> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-async-stream-0.2.5/src/lib.rs:430:31
  56: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:120:9
  57: futures_util::stream::stream::StreamExt::poll_next_unpin
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/mod.rs:1626:9
  58: <futures_util::stream::stream::next::Next<St> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/next.rs:32:9
  59: risingwave_stream::executor::wrapper::epoch_check::epoch_check::{{closure}}
             at ./ebs/risingwave/src/stream/src/executor/wrapper/epoch_check.rs:31:44
  60: <futures_async_stream::try_stream::from_generator::GenTryStream<G> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-async-stream-0.2.5/src/lib.rs:430:31
  61: <core::pin::Pin<P> as core::future::future::Future>::poll
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/future.rs:124:9
  62: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:120:9
  63: <risingwave_stream::executor::dispatch::DispatchExecutor as risingwave_stream::executor::StreamConsumer>::execute::{{closure}}
             at ./ebs/risingwave/src/stream/src/executor/dispatch.rs:255:9
  64: <futures_async_stream::try_stream::from_generator::GenTryStream<G> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-async-stream-0.2.5/src/lib.rs:430:31
  65: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:120:9
  66: <&mut S as futures_core::stream::Stream>::poll_next
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:104:9
  67: <tokio_stream::stream_ext::next::Next<St> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-stream-0.1.9/src/stream_ext/next.rs:42:9
  68: <minitrace::future::InSpan<T> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/minitrace-0.4.0/src/future.rs:118:19
  69: <async_stack_trace::StackTraced<F> as core::future::future::Future>::poll
             at ./ebs/risingwave/src/utils/async_stack_trace/src/lib.rs:172:23
  70: <futures_util::future::future::fuse::Fuse<Fut> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/future/future/fuse.rs:86:37
  71: risingwave_stream::executor::actor::Actor<C>::run::{{closure}}
             at ./ebs/risingwave/src/stream/src/executor/actor.rs:111:16
  72: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  73: risingwave_stream::task::stream_manager::LocalStreamManagerCore::build_actors::{{closure}}
             at ./ebs/risingwave/src/stream/src/task/stream_manager.rs:608:32
  74: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  75: async_stack_trace::manager::TraceReporter::trace::{{closure}}::{{closure}}::{{closure}}
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/macros/select.rs:507:49
  76: <tokio::future::poll_fn::PollFn<F> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/future/poll_fn.rs:38:9
  77: async_stack_trace::manager::TraceReporter::trace::{{closure}}::{{closure}}
             at ./ebs/risingwave/src/utils/async_stack_trace/src/manager.rs:99:21
  78: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  79: <tokio::task::task_local::TaskLocalFuture<T,F> as core::future::future::Future>::poll::{{closure}}
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/task/task_local.rs:345:35
  80: tokio::task::task_local::LocalKey<T>::scope_inner
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/task/task_local.rs:231:19
  81: <tokio::task::task_local::TaskLocalFuture<T,F> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/task/task_local.rs:342:13
  82: async_stack_trace::manager::TraceReporter::trace::{{closure}}
             at ./ebs/risingwave/src/utils/async_stack_trace/src/manager.rs:105:14
  83: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  84: <risingwave_stream::task::stream_manager::LocalStreamManagerCore::build_actors::__Enum15994158506141524639<__Variant0,__Variant1> as core::future::future::Future>::poll
             at ./ebs/risingwave/src/stream/src/task/stream_manager.rs:610:17
  85: <tokio_metrics::task::Instrumented<T> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-metrics-0.1.0/src/task.rs:2365:19
  86: <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tracing-0.1.36/src/instrument.rs:272:9
  87: tokio::runtime::task::core::CoreStage<T>::poll::{{closure}}
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/core.rs:165:17
  88: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/loom/std/unsafe_cell.rs:14:9
  89: tokio::runtime::task::core::CoreStage<T>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/core.rs:155:13
  90: tokio::runtime::task::harness::poll_future::{{closure}}
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:480:19
  91: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/panic/unwind_safe.rs:271:9
  92: std::panicking::try::do_call
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panicking.rs:492:40
  93: std::panicking::try
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panicking.rs:456:19
  94: std::panic::catch_unwind
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panic.rs:137:14
  95: tokio::runtime::task::harness::poll_future
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:468:18
  96: tokio::runtime::task::harness::Harness<T,S>::poll_inner
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:104:27
  97: tokio::runtime::task::harness::Harness<T,S>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:57:15
  98: tokio::runtime::task::raw::RawTask::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/raw.rs:84:18
  99: tokio::runtime::task::LocalNotified<S>::run
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/mod.rs:381:9
 100: tokio::runtime::thread_pool::worker::Context::run_task::{{closure}}
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/thread_pool/worker.rs:435:13
 101: tokio::coop::with_budget::{{closure}}
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/coop.rs:102:9
 102: std::thread::local::LocalKey<T>::try_with
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/thread/local.rs:445:16
 103: std::thread::local::LocalKey<T>::with
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/thread/local.rs:421:9
 104: tokio::coop::with_budget
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/thread_pool/worker.rs:434:9
 105: tokio::coop::budget
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/coop.rs:72:5
 106: tokio::runtime::thread_pool::worker::Context::run_task
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/thread_pool/worker.rs:434:9
 107: tokio::runtime::thread_pool::worker::Context::run
 108: tokio::runtime::thread_pool::worker::run::{{closure}}
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/thread_pool/worker.rs:386:17
 109: tokio::macros::scoped_tls::ScopedKey<T>::set
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/macros/scoped_tls.rs:61:9
 110: tokio::runtime::thread_pool::worker::run
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/thread_pool/worker.rs:383:5
 111: tokio::runtime::thread_pool::worker::Launch::launch::{{closure}}
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/thread_pool/worker.rs:362:45
 112: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/blocking/task.rs:42:21
 113: <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tracing-0.1.36/src/instrument.rs:272:9
 114: tokio::runtime::task::core::CoreStage<T>::poll::{{closure}}
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/core.rs:165:17
 115: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/loom/std/unsafe_cell.rs:14:9
 116: tokio::runtime::task::core::CoreStage<T>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/core.rs:155:13
 117: tokio::runtime::task::harness::poll_future::{{closure}}
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:480:19
 118: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/panic/unwind_safe.rs:271:9
 119: std::panicking::try::do_call
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panicking.rs:492:40
 120: std::panicking::try
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panicking.rs:456:19
 121: std::panic::catch_unwind
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panic.rs:137:14
 122: tokio::runtime::task::harness::poll_future
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:468:18
 123: tokio::runtime::task::harness::Harness<T,S>::poll_inner
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:104:27
 124: tokio::runtime::task::harness::Harness<T,S>::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:57:15
 125: tokio::runtime::task::raw::RawTask::poll
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/raw.rs:84:18
 126: tokio::runtime::task::UnownedTask<S>::run
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/mod.rs:418:9
 127: tokio::runtime::blocking::pool::Task::run
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/blocking/pool.rs:91:9
 128: tokio::runtime::blocking::pool::Inner::run
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/blocking/pool.rs:325:17
 129: tokio::runtime::blocking::pool::Spawner::spawn_thread::{{closure}}
             at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/blocking/pool.rs:300:13
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

CN2:

2022-09-13T10:01:43.602294Z  WARN risingwave_storage::hummock::compactor::shared_buffer_compact: Shared Buffer Compaction failed with error: ObjectStore failed with IO error TransientError: connection closed before message completed.                                                                                backtrace of `TracedHummockError`:                                                                                0: <risingwave_storage::hummock::error::HummockError as core::convert::From<risingwave_storage::hummock::error::HummockErrorInner>>::from                                                                                at ./ebs/risingwave/src/storage/src/hummock/error.rs:63:10                                                                                1: <T as core::convert::Into<U>>::into                                                                                at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/convert/mod.rs:550:9                                                                                2: risingwave_storage::hummock::error::HummockError::object_io_error                                                                                at ./ebs/risingwave/src/storage/src/hummock/error.rs:73:9                                                                                3: core::ops::function::FnOnce::call_once                                                                                at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/ops/function.rs:248:5                                                                                4: core::result::Result<T,E>::map_err                                                                                at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/result.rs:855:27                                                                                5: <risingwave_storage::hummock::sstable_store::StreamingUploadWriter as risingwave_storage::hummock::sstable::writer::SstableWriter>::finish::{{closure}}
...
2022-09-13T10:01:48.739852Z ERROR risingwave_storage::monitor::monitored_store: Failed in sync: Hummock error: ObjectStore failed with IO error TransientError: connection closed before message completed.                                                                                backtrace of inner error:                                                                                0: <risingwave_storage::hummock::error::HummockError as core::convert::From<risingwave_storage::hummock::error::HummockErrorInner>>::from                                                                                at ./ebs/risingwave/src/storage/src/hummock/error.rs:63:10                                                                                1: <T as core::convert::Into<U>>::into
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/convert/mod.rs:550:9
2: risingwave_storage::hummock::error::HummockError::object_io_error
...
2022-09-13T10:01:48.740045Z ERROR risingwave_stream::task::stream_manager: Failed to sync state store after receiving barrier prev_epoch 3003390457675776 due to Hummock error: ObjectStore failed with IO error TransientError: connection closed before message completed.
thread 'risingwave-streaming-actor' panicked at 'write epoch must greater than max current epoch, write epoch3003390916427776, sealed epoch3003390916427776', src/storage/src/hummock/local_version_manager.rs:421:9
stack backtrace:
   0: rust_begin_unwind
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/panicking.rs:142:14
   2: risingwave_storage::hummock::local_version_manager::LocalVersionManager::write_shared_buffer_inner

CN3:

thread 'risingwave-streaming-actor' panicked at 'upstream error: RemoteInput tonic error: status: Unknown, message: "error reading a body from connection: broken pipe", details: [], metadata: MetadataMap { headers: {} }                                                                                backtrace of `StreamExecutorError`:                                                                                0: <risingwave_stream::executor::error::StreamExecutorError as core::convert::From<risingwave_stream::executor::error::StreamExecutorErrorInner>>::from                                                                                at ./ebs/risingwave/src/stream/src/executor/error.rs:89:10                                                                                1: <T as core::convert::Into<U>>::into                                                                                at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/convert/mod.rs:550:9                                                                                2: <risingwave_stream::executor::error::StreamExecutorError as core::convert::From<anyhow::Error>>::from                                                                                at ./ebs/risingwave/src/stream/src/executor/error.rs:139:9                                                                                3: <T as core::convert::Into<U>>::into                                                                                at ./rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/convert/mod.rs:550:9                                                                                4: risingwave_stream::executor::exchange::input::RemoteInput::run::{{closure}}                                                                                at ./ebs/risingwave/src/stream/src/executor/exchange/input.rs:191:27                                                                                5: <futures_async_stream::try_stream::from_generator::GenTryStream<G> as futures_core::stream::Stream>::poll_next                                                                                at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-async-stream-0.2.5/src/lib.rs:430:31                                                                                6: <risingwave_stream::executor::exchange::input::RemoteInput as futures_core::stream::Stream>::poll_next                                                                                at ./ebs/risingwave/src/stream/src/executor/exchange/input.rs:201:9                                                                                7: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next                                                                                at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:120:9                                                                                8: futures_util::stream::stream::StreamExt::poll_next_unpin                                                                                at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/mod.rs:1626:9                                                                                9: <risingwave_stream::executor::merge::SelectReceivers as futures_core::stream::Stream>::poll_next                                                                                at ./ebs/risingwave/src/stream/src/executor/merge.rs:240:19                                                                                10: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next                                                                                at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-core-0.3.23/src/stream.rs:120:9                                                                                11: futures_util::stream::stream::StreamExt::poll_next_unpin                                                                                at ./home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.23/src/stream/stream/mod.rs:1626:9

Looks like CN3's panic is caused by failure in CN1 and CN2.
To Reproduce

Modify risedev-bench to start a 3-cn 2-compactor cluster.
Create sources:

CREATE SOURCE person (
    "id" BIGINT,
    "name" VARCHAR,
    "email_address" VARCHAR,
    "credit_card" VARCHAR,
    "city" VARCHAR,
    "state" VARCHAR,
    "date_time" TIMESTAMP,
    "extra" VARCHAR
) with (
    connector = 'nexmark',
    nexmark.table.type = 'Person',
    nexmark.split.num = '8',
    nexmark.min.event.gap.in.ns = '0'
) ROW FORMAT JSON;

CREATE SOURCE auction (
    "id" BIGINT,
    "item_name" VARCHAR,
    "description" VARCHAR,
    "initial_bid" BIGINT,
    "reserve" BIGINT,
    "date_time" TIMESTAMP,
    "expires" TIMESTAMP,
    "seller" BIGINT,
    "category" BIGINT,
    "extra" VARCHAR
) with (
    connector = 'nexmark',
    nexmark.table.type = 'Auction',
    nexmark.split.num = '8',
    nexmark.min.event.gap.in.ns = '0'
) ROW FORMAT JSON;

CREATE SOURCE bid (
    "auction" BIGINT,
    "bidder" BIGINT,
    "price" BIGINT,
    "channel" VARCHAR,
    "url" VARCHAR,
    "date_time" TIMESTAMP,
    "extra" VARCHAR
) with (
    connector = 'nexmark',
    nexmark.table.type = 'Bid',
    nexmark.split.num = '8',
    nexmark.min.event.gap.in.ns = '0'
) ROW FORMAT JSON;

Create MView:

CREATE MATERIALIZED VIEW nexmark_q7
AS
SELECT
    B.auction,
    B.price,
    B.bidder,
    B.date_time
from
    bid B
    JOIN (
        SELECT
            MAX(price) AS maxprice,
            window_end as date_time
        FROM
            TUMBLE(bid, date_time, INTERVAL '10' SECOND)
        GROUP BY
            window_end
    ) B1 ON B.price = B1.maxprice
WHERE
    B.date_time BETWEEN B1.date_time - INTERVAL '10' SECOND
    AND B1.date_time;

Wait for 2hrs.

Expected behavior

No panic.
Object store error is properly handled.

Additional context
commit: 531140508954b13cae4ddc436562719f550e9afb
cn1.log
cn2.log
cn0.log
compactor-0.log
compactor-1.log
Compactor occasionally failed to write to s3 with "error writing a body to connection: Broken pipe (os error 32)"

We have accumulated 4.4GB meta node log so it is hard to include in the issue. I will submit a PR to fix the excessive logging.

If our buffer_size is too large, we will suspend the write batch in the shared buffer. But we will also return that the write is finished. So our barrier will be collected and sealed_epoch will be updated

Produced again.
thread 'risingwave-streaming-actor' panicked at 'write epoch must greater than max current epoch, write epoch3014005900640256, sealed epoch3014005900640256', src/storage/src/hummock/local_version_manager.rs:423:9

Logs: risingwave-log.tgz

Closed by #5364

authors: fuyufjh hzxa21 xxhZs


text:
PG-incompatibility: alias of set returning function in FROM

Describe the bug
This works in both PostgreSQL and RisingWave:
select id from generate_series(1, 5, 1) as t(id);

This only works in PostgreSQL but not in RisingWave:
select id from generate_series(1, 10, 1) as id;

Hi @CAJan93, I have updated the issue description based on my testing. Does it reflect the original bug you intend to report?
About this issue, it seems PostgreSQL is handling set returning function which outputs a single column specially, that as id would rename both the table and its only column to id:
test=# select id.id from generate_series(1, 5) id;
 id
----
  1
  2
  3
  4
  5
(5 rows)

test=# select id.id from jsonb_each('{"a":1,"b":true}') id;
ERROR:  column id.id does not exist
LINE 1: select id.id from jsonb_each('{"a":1,"b":true}') id;
               ^

test=# select id.key from jsonb_each('{"a":1,"b":true}') id;
 key
-----
 a
 b
(2 rows)

Yap, new title works @xiangjinwu. Thank you very much for changing it and looking into the solution already 👍

source: gharchive/issue

repo: risingwavelabs/risingwave

license_type: permissive

license_source: github-api


text:
feat(ci): test standalone cluster in main-cron, with e2e test

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Passed. Will run it 2 more times to make sure it's stable.

source: gharchive/pull-request


text:
Update Copy links.user.js

Display only ticket numbers not the full URL

Unfortunately it only works in slack for mac

repo: ritaschaff/zendesk-userscripts


text:
Customer Browser: Microsoft-Edge Doesn't Work

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[ ] Other: <!-- Please describe: -->

Current behavior
If I choose edge as the custom browser in live server setting, live server doesn't open html page. Nothing happens. If I make edge browser as default browser in MacOS and change the custom browser setting to null, live server opens html page.
Expected behavior
Choose edge as custom browser and have live server open an html page.
Environment
Browser:

- [ ] Chrome (desktop) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] IE version XX
- [x] Edge version 05.0.1343.33 (Official build) (arm64)

For Tooling issues:

- Live Server: v5.7.9
- Platform:  macOS Monterey 12.6
- Visual Studio Code: 1.71.1

Others
I've tried uninstalling and re-installing the extension. I think it was yesterday when I first noticed this new behavior. The only recent change I can think if is applying update to macOS 12.6. Live server works as intended when set to chrome and firefox.  Also doesn't with blisk.

Figured out a workaround by using the AdvanceCustomBrowserCmdLine and specifying location of Edge Borwser:
liveServer.settings.AdvanceCustomBrowserCmdLine": "/Applications/Microsoft Edge.app/Contents/MacOS/Microsoft Edge",

repo: ritwickdey/vscode-live-server

license: mit

license_source: bigquery


text:
Open with Live Server with unsupported files (not html/svg) should open files instead of root folder

Steps:

Select a file with an unsupported extension in the VS Code Explorer (e.g. test.xml)
Run command: Open with Live Server.

Expected result:

File is loaded live server / opened in my browser (Chrome) without inserted javascript. This would be a fallback mode: there is no live reload but I can still see my file in the virtual browser if I want to.

Actual result:

The root directory is opened in the browser.
Workaround: manually select the file to view it in the browser.

That sounds nice!

authors: jawn ritwickdey


text:
chore(cluster): remove default provisioning config

Fixes RVT-4433

#1643  👈 (View in Graphite)
main

How to use the Graphite Merge Queue
Add the label merge-queue to this PR to add it to the merge queue.
You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has required the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

repo: rivet-gg/rivet


text:
The “Job Title” is not displayed properly when the job name is too long.

Description: The “Job Title” is not displayed properly when the job
name is too long.
-Env:
Device: MacBook Pro
Google Chrome Version 61.0.3163.100 (Official Build) (64-bit)
Mozilla Firefox 55.0.3 (64-bit)
REPRODUCIBILITY LEVEL:
Always
STEPS:
Steps

Open the Crafter studio with the Zentro Restaurant blueprint.
Click on the sidebar to display the menu.
Expand the component section.
On the components section, click on the edit button of team component.
Go to the content section and type a 50 characters “Job Title”
Go to the preview and check the “Meet Zentro chefs” section.

*Note this bug also causes team member images are not arranged properly,
https://www.screencast.com/t/kCZkAmq3c4wu
CURRENT RESULT:
Title: The “Job title” is not displayed properly when the job name is too long.

EXPECTED RESULT:
Title: The “Job Title” should be displayed properly when the job name contains the maximum characters length.

The bug is still present when  use 50 characters

The bug is still present

repo: rivetlogic/craftercms-bp-restaurant

license: MIT


text:
🛑 Fontsss is down

In cd92e7e, Fontsss (https://fontsss.com) was down:

HTTP code: 500
Response time: 189 ms

Resolved: Fontsss is back up in 0b82dcc.

repo: rizalrenaldi/ruptime


text:
handle dpdk port "siblings"

When releasing a DPDK port and asking for detaching/freeing its associated HW resources, care must be taken not to break port "siblings" that were sharing those HW resources.
See testpmd or OVS:
https://git.dpdk.org/dpdk/tree/app/test-pmd/testpmd.c#n3674
https://github.com/openvswitch/ovs/blob/main/lib/netdev-dpdk.c#L1747

Which hardware relies on siblings ?
I'd like to test https://github.com/rjarry/grout/compare/main...christophefontaine:grout:issue_40

authors: christophefontaine david-marchand

repo: rjarry/grout


text:
[Core] Container action spaces in Policy

For useful applied tasks, we need to allow container action spaces. Currently raises an error, need where this actually causes a problem.

Currently being worked on. Will be completed including test cases within the next days.

repo: rlgraph/rlgraph


text:
Creating Clients

Hello, I cannot understand how the mechanism of authorization through HTTP Auth is implemented.
I did not find in the documentation how to add usernames and passwords for clients, and the plugin description uses the path like http://127.0.0.1:8080/mqtt/superuser, which does not work...
can you tell me how to create users?

Hello, I cannot understand how the mechanism of authorization through HTTP Auth is implemented.
I did not find in the documentation how to add usernames and passwords for clients, and the plugin description uses the path like http://127.0.0.1:8080/mqtt/superuser, which does not work...
can you tell me how to create users?

You need to prepare the HTTP API service for Auth verification. The APIs that need to be implemented are:
/mqtt/auth
/mqtt/superuser
/mqtt/acl
Request parameter reference: https://github.com/rmqtt/rmqtt/blob/master/rmqtt-plugins/rmqtt-auth-http.toml
Response parameters: If the status code returns 200, the verification is successful; if you need to cache the result, please return the string ignore in the Body.

oooh i got it,  i'll try it
thanks so much for the help

repo: rmqtt/rmqtt


text:
Question/Request

Hiya! again amazing server, is there any way of configuring rmqtt as a broker bridge to communicate/proxy messages across brokers?
Thanks!

Hello, thank you for your interest in rmqtt, this feature is not yet supported.
---- Replied Message ----
| From | Anton @.> |
| Date | 03/17/2024 05:49 |
| To | @.> |
| Cc | @.***> |
| Subject | [rmqtt/rmqtt] Question/Request (Issue #55) |
Hiya! again amazing server, is there any way of configuring rmqtt as a broker bridge to communicate/proxy messages across brokers?
Thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Starting from version 0.5.0, the "rmqtt-bridge-ingress-mqtt" and "rmqtt-bridge-egress-mqtt" plugins are supported.

authors: akrizs rmqtt


text:
Add Multi-Asset user journey

Added the user journey for the Multi-Asset implementation that explores the main features of the standard.

This pull request has no longer sense since the updates of the smart contracts for evm.
There will be a new pull request updated.

repo: rmrk-team/evm-multiasset-demo


text:
Cross contract check when equipping

This PR adds the following:

[X] Makes cross contract call in equip() function to call ensure_token_can_be_equipped_with_asset_into_slot(). To make this work I made the ensure_token_can_be_equipped_with_asset_into_slot part of the equippable trait and moved the implementation of it to lib.rs.
[X] Introduce missing e2e test to cover equip. I created a new file for this purpose as suggested. This integration test introduces a new example with an avatar and sword contract which is somewhat similar to the MergedEquippable user story. Through this example, the equipping functionality is tested.

AFAIK there are no unit tests that cover this functionality, hence there is nothing to be updated.
Closes: #33

Integration test started to fail again. Can you take a look what is the problem now?

Instead of adding new test file, can you integrate this test into existing one? The tests need some reshuffle and adding new file will make it even more complicated.

@Maar-io Ok, I will move the test into merged_equippable.spec.ts, but I think it would be a good idea to then rename this file to equip.spec.ts. What do you think about this?

Integration test started to fail again. Can you take a look what is the problem now?

@Maar-io The integration test failure is not caused by this PR, it is the same error as the one in the main branch. Locally everything works well for me.

Integration test started to fail again. Can you take a look what is the problem now?

@Maar-io The integration test failure is not caused by this PR, it is the same error as the one in the main branch. Locally everything works well for me.

No problem, we can open new issue and fix the integration test in the main

I have moved the test to merged_equippable.spec.ts and renamed the file to equip.spec.ts.

authors: Maar-io Szegoo

repo: rmrk-team/rmrk-ink


text:
Motor only for web?

Hey,I've been looking into motor's source code and it's lovely but I have one question. Is motor going to be used just for web or desktop too? Because right now the sound and graphics api does not work on linux at least.
Also why are you using SDL's opengl implementation and glsl? You can use #include GL/glew.h and put -s FULL_ES2=1 and it will work just fine on web.

Hi,
in theory it should work on the desktop, too. Sometimes I break stuff,
because I only test the web version regularly. On my Debian and Arch
machines both, audio and graphics work fine. What Linux distro are you
using?
I had quite a few problems when switching to SDL2, after that I only had
access to legacy GL functionality. That's why I switched to GLEW.
Cheers,
rnlf
On 09/06/2015 12:39 PM, Muresan Vlad aka Mury wrote:

Hey,I've been looking into motor's source code and it's lovely but I
have one question. Is motor going to be used just for web or desktop
too? Because right now the sound and graphics api does not work on
linux at least.
Also why are you using SDL's opengl implementation and glsl? You can
use #include and put -s FULL_ES2=1 and it will work just fine on web.
—
Reply to this email directly or view it on GitHub
https://github.com/rnlf/motor/issues/7.

I'm using Arch Linux too. Right now the only thing I'm able to do is to change the background color. Drawing textures,fonts or playing sounds does not work at all. Also why is your build script made in python? :) Wouldn't it be easy to make a make file or cmake ?

From what I see here: https://github.com/rnlf/motor/blob/master/src/graphics/graphics.c#L65-L66 your using gl 3.2? I think it would be a better idea to use 2.0 so that anyone can have access to use motor2d.

Murii:

What really bothers me is that motor does not work on desktop...I tried to fix this issue but I'm not exactly sure what it's wrong(I guess it's related to opengl,I'll have a closer look today).
Edit 1: glew returns 0 in console -_-*
Edit 2: if printf("%d\n", glewInit()); is moved below SDL_INIT_VIDEO or after, then the printf function will return 1 but motor crashes before the window is created.

Murii, I cannot reproduce that problem. For me glew and SDL initialization work just fine. What do you mean with "glew returns 0 in console"? If glewInit returns 1, that actually means that an error occured, 0 indicates success.
I just used OpenGL 3.2 as a default goto version for today. Since the desktop version is intended just for debugging, I don't really care about the GL version used. Is there any desktop hardware available today that doesn't support GL 3.2?

"Is there any desktop hardware available today that doesn't support GL 3.2?" - probably not? Anyway if you say the correct value for glewInit should be 0( I thought 0 means false :) ) then can you tell me why the module love.graphics does not work? I tried printing a text using : love.graphics.print("Hey",200,200,100);

There may be a problem with loading the default font. Could you try just clearing the window with a different background color, something along the lines
love.graphics.setBackgroundColor(255,0,0)
love.graphics.clear()

Could you link your full test program?

function love.load()
end
function love.update(dt)
print(dt)
end
function love.draw()
love.graphics.print("Yesasgasg",100,100,100)
love.graphics.setBackgroundColor(255,0,0)
love.graphics.clear()
end

Okay, so basic OpenGL is working, which is a good start. Could you next try to draw a colored rectangle:
function love.draw()
love.graphics.setColor(255,255,0)
love.graphics.rectangle('fill', 10, 10, 200, 200)
end

If that works, then it's probably really a problem with the font loading, I will look into it, if you can confirm it.

It does not work.

One way to fix this problem is by adding glewExperimental = true and specify the version of the shaders

authors: Murii rnlf

repo: rnlf/motor


text:
Manage not available when part of organisation

I’m a member of MessageKit org but can’t manage any of the issues/prs even though I should be able to!

Bug Report Dump (Auto-generated)

Version 1.13.0 (1190)
Device: iPhone 6s Plus (iOS 11.2)
TestFlight: true

@rnystrom
https://github.com/rnystrom/GitHawk/blob/710dae03883a56fcf2cf277cf0579602e4fa0d78/Classes/Issues/GithubClient%2BIssues.swift#L282-L300
Looks like the current API we use is very much just for collaborators
Maybe we should look to refactor that a tiny bit to use this endpoint:
https://developer.github.com/v3/repos/collaborators/#review-a-users-permission-level
This will give us the users permission level out of admin, read, write or none. Where write (I assume) is labels/milestones but covering cases like teams/collab/owner/orgs/etc

@Sherlouk did you test out that API to check your permissions on that repo? So you should have write permissions? I just want to make sure that returns the proper permissions before changing things.

I just tried to check your permissions and got a 403 forbidden
{
    "message": "Must have push access to view collaborator permission.",
    "documentation_url": "https://developer.github.com/v3/repos/collaborators/#review-a-users-permission-level"
}

Do you have push access to that repo?

What about using the team API?
https://developer.github.com/v3/orgs/teams/#get-team-membership
@Sherlouk can you try accessing your membership for that org?
https://api.github.com/teams/30243544/memberships/sherlouk

@rnystrom
https://api.github.com/repos/messagekit/messagekit/collaborators/sherlouk/permission?access_token=revoked
{
  "permission": "write",
  "user": {
    "login": "Sherlouk",
    ...
    "type": "User",
    "site_admin": false
  }
}

https://api.github.com/teams/30243544/memberships/sherlouk
Just giving me a Not Found error

Great!!
Sent with GitHawk

Brill!
I've confirmed it on MessageKit (Part of the Org), IGListKit (Collab within an Org), GitHawk (Collab) which are all "write" as well as one of my repos where it's "admin". Both of these need access to manage :)
Looking forward to it

authors: Sherlouk rnystrom

repo: rnystrom/GitHawk


text:
React.createElement: type should not be null, undefined, boolean, or number.

When I upgraded to the 0.6.2 version of react-cropper. I kept getting the following error when React was trying to render it to the page.
warning.js:45Warning: React.createElement: type should not be null, undefined, boolean, or number. It should be a string (for DOM elements) or a ReactClass (for composite components).
So I create a brand new project and used your example from the readme
var Cropper = require('react-cropper');
var Demo = React.createClass({
  _crop: function(){
    // image in dataUrl
    console.log(this.refs.cropper.getCroppedCanvas().toDataURL());
  },

  render: function() {
    return (
      <Cropper
        ref='cropper'
        src='http://fengyuanchen.github.io/cropper/img/picture.jpg'
        style={{height: 400, width: '100%'}}
        // Cropper.js options
        aspectRatio={16 / 9}
        guides={false}
        crop={this._crop} />
    );
  }
});

I still experienced the same issue. Changing the line
var Cropper = require('react-cropper'); to var Cropper = require('react-cropper').default;
cleared the problem.
It may be worth adding a note to the readme in case others experience the same problem.
Thanks for your work on react-cropper.

Could you tell me how do you build your code? Webpack or browserify? And what version did you use? If you can put your project on Github that will be very helpful.

Github project https://github.com/simax/react-cropper-demo/tree/master

I think I know what's going on. It's because babeljs change the way export module. http://stackoverflow.com/questions/33505992/babel-6-changes-how-it-exports-default

import Cropper from 'react-cropper'
https://github.com/roadmanfong/react-cropper-demo/blob/master/main.js
This works too.
I added require function usage in README.md, Thank you for your feedback.

@roadmanfong Unfortunately this module will not work with import in my case, since there is server-side rendering and I have to do.
const Cropper = __CLIENT__ ? require('react-cropper') : null;
Then it took me some time to learn I had to put .default as well. This is why I think your component should take care of the server-side rendering issue.

authors: OKNoah roadmanfong simax

repo: roadmanfong/react-cropper


text:
'gap' alias removed (accidentely) from git plugin

the commit 5b75cc7880de1931a0507800d90eb77ed659fa46 removes gap alias on line 77

See discussion here about gg* and gap: https://github.com/robbyrussell/oh-my-zsh/pull/2790#issuecomment-110689393

This was no accident! it was murder! cold-blooded murder I tell you!!!
More seriously though, gap is a program — see #3682.
Until we build a safe aliasing system for OMZ, you can set the gap alias in your personal config, or you are welcome to suggest a new alias for git add --patch.

Also please close #3983.

authors: doomspork groolot ncanceill

repo: robbyrussell/oh-my-zsh


text:
oh-my-zsh.sh tries to install dpkg into Fedora

Describe the bug
Oh my zsh wants to install dpkg. Getting this message Install package 'dpkg' to provide command 'dpkg'? [N/y].
To Reproduce
Simply turn on terminal, the problem is coming from .zshrc from source $ZSH/oh-my-zsh.sh (no problem when commented).
Expected behavior
None
System:

OS: Fedora 30
Zsh version: zsh 5.7.1 (x86_64-redhat-linux-gnu)
Terminal emulator: All terminals affected

Following patch resolved issue for my (Fedora):
diff --git a/plugins/fzf/fzf.plugin.zsh b/plugins/fzf/fzf.plugin.zsh
index 64614829..f5b09dc8 100644
--- a/plugins/fzf/fzf.plugin.zsh
+++ b/plugins/fzf/fzf.plugin.zsh
@@ -58,6 +58,7 @@ function setup_using_base_dir() {

 function setup_using_debian_package() {
+    command -v dpkg || return 1
     dpkg -s fzf &> /dev/null
     if (( $? )); then
         # Either not a debian based distro, or no fzf installed. In any case skip ahead

Can you submit that in PR form?

authors: KSonny4 mcornella mgeeky


text:
Added a logo to Pydemy

With this pull request, Pydemy gains a logo.

Done

repo: robelasefa/pydemy


text:
Wrong icon for 'license.js'

Hey
when naming a file license.js, the license-icon is used. When using license.spec.js, the correct icon is displayed. Is this behavior expected? In my case, the js-icon would have been the correct one.

Some additional information:
vscode: 1.8.0
vscode-icons: 4.2.0

@robertohuertasm filename overrides languageId

@JimiC I was aware of that but didn't expect this greedy behavior. This seems like a bug in VSCode to me. Filename classes should only be added to files with the exact match. cc @aeschli, maybe you can give us a hand here. Is this the expected behavior?

@robertohuertasm I know you knew. Just wanted to point out the cause.

It seems that only happens with filenames that have no extension. Of course, we haven't had this issue before because we were mainly using file extensions.
I'm going to raise an issue in vscode's repo about this.

I've also submitted a PR #17865

It seems that the PR has been merged! :+1:

What does this mean for us? Do we have to fix anything or do we need to wait for the next update?

What does this mean for us? Do we have to fix anything or do we need to wait for the next update?

The next vscode will be in a few days (January release). We could wait a bit or close it. If somebody opens another issue we could point him/her to the right direction.

The next vscode will be in a few days (January release). We could wait a bit or close it. If somebody opens another issue we could point him/her to the right direction.

I didn't close it just to wait for the new functionality to be deployed and test it again just in case.

I didn't close it just to wait for the new functionality to be deployed and test it again just in case.

I've checked this in the Insiders version and it works so I'm closing this.

Confirming.

authors: JimiC flxbe jens1o robertohuertasm

repo: robertohuertasm/vscode-icons


text:
bug: Uncaught (in promise) Error: "Badge" plugin is not implemented on android

Describe the bug
When trying to use this plugin on Android, I'm getting the following error
Uncaught (in promise) Error: "Badge" plugin is not implemented on android
Test device: Galaxy A7 running Android 10
Testing method: ionic build; ionic cap copy android, then build in Android Studio 4.1.3 on Ubuntu via WSL and deploy directly to device
Plugin version: 1.0
Capacitor: 3.0.0-rc1 (also tried with rc0)
Ionic-native/core: 5.32.1
This is a React app working with a Drupal backend.
When I build my app for iOS and test on an iPhone X, the badges work as expected, so I know my code at least works some of the time.
To Reproduce
Steps to reproduce the behavior:
Here's code that causes the error, which is run when the user logs in:
export const badgeSetCount = async (count: number): Promise<void> => {
  console.log('making a call to badge', count);
  Badge.checkPermissions().then(
    async (permissionStatus) => {
      console.log('checking badge permissions', permissionStatus);
      if (permissionStatus.display === 'granted') {
        await Badge.set({ count });
      }
    },
  );
};

And here's code that causes the error when the user logs out:
export const badgeClear = async (): Promise<void> => {
  await Badge.clear();
};

Expected behavior
Badges are set with no error.
Smartphone (please complete the following information):

Device: Galaxy A7
OS: Android 10
Browser Ionic React App

Additional context
I'm pretty new to app development so I might be missing something obvious.
When I updated to Capacitor 3, to make sure I did the upgrade correctly, I removed the old android project and created a new one from scratch (to ensure I didn't fail to make one of the small manual changes that would otherwise be required).
Other capacitor 3 plugins in the app (for example, storage) are working (the login cookie is set properly).  Also, I can upload a file with the Camera plugin.

Thank you very much for the support.
I have managed to get the badges to display on Android, but only some of the time.  Even when the badge is displayed, it doesn't get updated correctly.  This is a launcher supported by ShortcutBadger.  However, this is really a separate problem from the original issue so if I can find exact steps to reproduce it (still debugging), I'll create a new issue later.
Again, thank you for developing this plugin; for my app, it's really helpful to have a badge count, and you made it possible.

Glad the plugin helps you and thanks a lot!
Feel free to open a new issue. I will try to help.
Of course, the problem should be reproducible.

authors: ptmkenny robingenz

repo: robingenz/capacitor-badge


text:
Cannot run the code from documentation!!!

Firstly, I would like to thanks for your contribution in this great work and make the code available for the public. And I am working on my project and I would like to study the deep learning methods for EEG analysis. I follow the code documentation, but I have problem to run the code.

I copy paste the code from :https://robintibor.github.io/braindecode/notebooks/TrialWise_Decoding.html

But I get an error when I run it. The error is

"179 events found
Events id: [1 2 3]
90 matching events found
Loading data for 90 events and 497 original time points ...
0 bad epochs dropped"

I attach the code I used for you to check if there are any problem for the package.Thank you very much !

brainConvNets.zip

? But does it crash? Seens like hust some logging?

repo: robintibor/braindecode


text:
Should the serializer/parser know about names ?

Currently in nmp we only know about the id switched on, not the name of the packet, it's needed to do the mapping there.
Does it make sense for the serializer/parser to know about "names" ?
What are "packet names" ? Just type names as currently (but knowing the type read in the meta is apparently confusing so that's not a good solution) ? Maybe it could be possible to add some meta information in the switch ?
Or maybe the mapping id to packet name shouldn't be the job of the serializer/parser and should be let to users ? (as it currently done in nmp)

Ah, I know of a good way to solve that problem: have the possibility of giving names to switch cases, just like container fields have names.

Possibilities:
have names in switch fields
{
        "name": "value",
        "type": [
          "switch",
          {
            "compareTo": "type",
            "fields": [
              {"value":"0","type":"end","name":"end"},
              {"value":"1","type":"byte","name":"byte"},
              {"value":"2","type":"short","name":"short"},
              {"value":"3","type":"int","name":"int"},
              {"value":"4","type":"long","name":"long"},
              {"value":"5","type":"float","name":"float"},
              {"value":"6","type":"double","name":"double"},
              {"value":"7","type":"byteArray","name":"byteArray"},
              {"value":"8","type":"string","name":"string"},
              {"value":"9","type":"list","name":"list"},
              {"value":"10","type":"compound","name":"compound"},
              {"value":"11","type":"intArray","name":"intArray"}
            ]
          }
        ]
      }

It's kind of ugly and it doesn't quite solve the problem of the field that would hold the name.
Hiding the compared field ? (https://github.com/PrismarineJS/node-minecraft-protocol/pull/274#discussion_r43066274)
a new "mapper" type that would transform the id to name and vice-versa:
["mapper", {"fromField":"typeId",
                 "toField":"typeName","conversions":{"0":"end","1":"byte","2":"short",...}}]

It looks cleaner but it kind of add a level of serialization/parsing, but maybe that's ok.

repo: roblabla/ProtoDef


text:
Tech Debt: Finish Converting Forms to Formik

Convert the rest of the frontend forms from redux-form to formik and remove redux-form from our package.json dependencies.

To Bill: datepicker the entry period in creating a show does not allow me to select ranges, closes after you select start date. Firefox v58.0.1


text:
support requirements property

Hi, maybe adding a requirements property to each chart section could tell helmfile to install dependencies first? Is that an idea? Is there a way to know if dependencies are ready?

Does installing a chart that has dependencies included currently not work?

Hi @Morriz - I don't think this is something helmfile needs to do, helm already provides a way to package dependencies (charts) within charts.
If there's another use case here, can you try to describe it? If not I'll close this in a few days.

authors: Morriz gtaylor roboll

repo: roboll/helmfile


text:
Prescriptive directory structure for "magic" values files

I've written a helmfile containing abut 40 releases and I'm having to repeat myself a lot:
Example:
  - name: heapster
    namespace: kube-system
    chart: stable/heapster
    version: 0.3.2
    values:
      - "./values/logging/heapster/common.yaml"
      - "./values/logging/heapster/{{ .Environment.Name }}.yaml"
    secrets:
      - "./values/logging/heapster/common-secrets.yaml"
      - "./values/logging/heapster/{{ .Environment.Name }}-secrets.yaml"

  - name: kubernetes-dashboard
    namespace: kube-system
    chart: stable/kubernetes-dashboard
    version: 0.10.0
    values:
      - "./values/kube-system/kubernetes-dashboard/common.yaml"
      - "./values/kube-system/kubernetes-dashboard/{{ .Environment.Name }}.yaml"
    values:
      - "./values/kube-system/kubernetes-dashboard/common-secrets.yaml"
      - "./values/kube-system/kubernetes-dashboard/{{ .Environment.Name }}-secrets.yaml"

One feature I really like about Ansible is that it automatically looks for it's values files for each "playbook" in a certain directory structure, and looks in multiple locations in a known order, allowing easy environment specific overrides, etc.
I think it would be really nice if helmfile automatically looked for a values/<namespace>/<release-name> directory and then automatically loaded (in order):

A common file regardless of environment (maybe values.yaml or common.yaml).
An environment specific file (e.g production.yaml).
Any files explicitly listed in the helmfile.yaml (in order).

And then a similar process for secrets (either in a secrets/<namespace>/<release-name> directory or in values/<namespace>/<release-name>, with files suffixed with -secrets treated as secrets e.g production-secrets.yaml.)
Another things is that if helmfile can't stat the file, it errors out (which is great in that it stops mistakes from missing files), but it would be nice if a a switch could be set so that a certain file and/or directory not existing is a warning, not an error.
Example Directory Tree:
values/
    kube-system/                      # 'kube-system' namespace
        dashboard/                    # 'dashboard' release
            production.yaml           #  production Environment specific values
            production-secrets.yaml   #  production Environment specific secrets
            staging.yaml              #  staging Environment specific values
            values.yaml               #  contains values common to all Environments
        heapster/
            values.yaml               #  only common values.yaml is provided, no environment specific values are needed.
    web/                              # 'web' namespace
        [..]                          # sub-directories similar to above

Then my helmfile.yaml could be simplified to:
  - name: heapster
    namespace: kube-system
    chart: stable/heapster
    version: 0.3.2

  - name: kubernetes-dashboard
    namespace: kube-system
    chart: stable/kubernetes-dashboard
    version: 0.10.0

I have similar boilerplate that I use over and over again
accounts/
  dev/
  stg
    prometheus/
       values.yaml
       secrets.yaml
releases/
  prometheus/
    values.yaml

Hi I am a bit confused about the syntax.
I do see:
     # IMPORTANT: {{` {{ .Release.Name }} `}} is surrounded by {{` and `}} not to be executed on the loading time of helmfile.yaml.
     # We need to defer it until each release is actually processed by sync|diff|apply|etc.

but why does that happen? Is it a special syntax? I have tried searching without results :(

@fzyzcjy Hey. That's because helmfile.yaml itself is a go template file that should render a YAML document. So, it renders in two phases. The first phase renders the whole helmfile.yaml. The second phase renders go template expressions embedded in releases[].values and so on.
{{` {{ .Release.Name }} `}}

This is a go template comment. This makes the first phase to render
{{ .Release.Name }}

which is then rendered by the second phase.

@mumoshu Thanks!

authors: fzyzcjy mattparkes mumoshu sstarcher


text:
Error is not processed by nest logger when wrong token is passed

Generate error what is not handled by nest logger if wrong token is passed for example https://github.com/robot-mafia/nestjs-telegraf/blob/194419dc799f0872fcf4000a5e1266c462dac8c7/lib/utils/create-bot-factory.util.ts#L16
const bot = new Telegraf<any>(options.token, options.options);

  bot.use(...(options.middlewares ?? []));
  bot.catch((err, ctx) =>
    Logger.error(err, `Telegraf: ${ctx.botInfo.username}`), // that not help
  );

  if (options.launchOptions !== false) {
    bot.launch(options.launchOptions);  // here thrown error
  }

Can catch it with
if (options.launchOptions !== false) {
    bot
      .launch(options.launchOptions)
      .catch((err) => Logger.error(err.stack, 'Telegraf')); // that
  }

With change will be
[FrameworkX] 15680  - 12/08/2024, 1:00:00 PM   ERROR [Telegraf] Error: 404: Not Found
    at new TelegramError (/home/projects/app/node_modules/telegraf/lib/core/network/error.js:6:9)
    at <anonymous> (/home/projects/app/node_modules/telegraf/lib/core/network/client.js:315:31)
    at processTicksAndRejections (native:7:39)

repo: robot-mafia/nestjs-telegraf


text:
Variables are read from one file while it's used in a keyword defined in a second file

Variables are read from one file while it's used in a keyword defined in a second file.
For example: if you have a file 'x' that has a keyword and that keyword has a variable 'a', and another file 'y' that has the same variable name 'a'. Both of them are imported as resources in test file 'z'. When using the keyword in file 'x', it will run it but with the value of the variable 'a' which is defined in file 'y'.

Could you please clarify this?

So consider you have project with a test file and 2 helper files. Both of the helper files "x' & 'y' ,which have a variable with the same name  "name" but different values, and the test file imports both the helper files.
When calling in the test file a keyword from file 'x' that uses variable "name", Then it will not use the assigned value for 'name' in file 'x' but the value of 'name' in the file 'y'.
Hope this makes any sense.
Thank you.

Does it adhere to this statement from UserGuide or not?
All variables from a variable file are available in the test data file that imports it. If several variable files are imported and they contain a variable with the same name, the one in the earliest imported file is taken into use. Additionally, variables created in Variable tables and set from the command line override variables from variable files.

So if you have variable ${a} defined in x.robot:
*** Variables***
${a}  4

and y.robot
*** Variables***
${a}  5

and test.robot:
*** Settings ***
Resource    x.robot
Resource    y.robot

Test
    Log    ${a}

It should print 4.

Does it adhere to this statement from UserGuide or not?
All variables from a variable file are available in the test data file that imports it. If several variable files are imported and they contain a variable with the same name, the one in the earliest imported file is taken into use. Additionally, variables created in Variable tables and set from the command line override variables from variable files.

So if you have variable ${a} defined in x.robot:
*** Variables***
${a}  4

and y.robot
*** Variables***
${a}  5

and test.robot:
*** Settings ***
Resource    x.robot
Resource    y.robot

Test
    Log    ${a}

It should print 4.

So I have to keep the variables names unique across the whole project!

So I have to keep the variables names unique across the whole project!

Variable names does not need to be unique - but if you're using multiple imports they should be unique (or you need to be aware of how it works). If you're depending in import order to resolve variable value it will quickly create kind of spaghetti code. I've encountered such situation where I saw multiple (and nested too) imports and if there was not unique variable name I was not able to guess its value without running the code.
Example of reusing variable name:
imp.resource
*** Variable ***
${common_value}    10

*** Keywords ***
My Common Keyword
    Should Be True  ${common_value} < ${common_but_different}

test1.robot
*** Settings ***
Resource  imp.resource

*** Variables ***
${common_but_different}  5

*** Test Cases ***
Test
    My Common Keyword

test2.robot
*** Settings ***
Resource  imp.resource

*** Variables ***
${common_but_different}  15

*** Test Cases ***
Test
    My Common Keyword

So it's safe to reuse as long you're aware how it will behave.

Variable names does not need to be unique - but if you're using multiple imports they should be unique (or you need to be aware of how it works). If you're depending in import order to resolve variable value it will quickly create kind of spaghetti code. I've encountered such situation where I saw multiple (and nested too) imports and if there was not unique variable name I was not able to guess its value without running the code.
Example of reusing variable name:
imp.resource
*** Variable ***
${common_value}    10

*** Keywords ***
My Common Keyword
    Should Be True  ${common_value} < ${common_but_different}

test1.robot
*** Settings ***
Resource  imp.resource

*** Variables ***
${common_but_different}  5

*** Test Cases ***
Test
    My Common Keyword

test2.robot
*** Settings ***
Resource  imp.resource

*** Variables ***
${common_but_different}  15

*** Test Cases ***
Test
    My Common Keyword

So it's safe to reuse as long you're aware how it will behave.

Noted, thank you :)

Noted, thank you :)

The current design related to handling variables isn't great in this regard, but changing it is both a lot of work and pretty badly backwards incompatible. I'm pretty sure we need to do something to it in the future, but we already have #2970 about it so this issue can be closed.

authors: HafezM bhirsz pekkaklarck

repo: robotframework/robotframework


text:
Yolov5 模型,打开量化并指定输出结点为神经网络的最终结点,则得到的数据大部分为0.0

重现步骤:
基于 examples/onnx/yolov5/test.py
在244行,将
ret = rknn.load_onnx(model=ONNX_MODEL,outputs=['396', '458', '520'])
改为
ret = rknn.load_onnx(model=ONNX_MODEL,outputs=['output'])
在306行, 将
input0_data = outputs[0]
input1_data = outputs[1]
input2_data = outputs[2]
改为
input0_data = outputs[0]
结果:
检查 input0_data, 会发现,大部分数据都是0
但是,如果关闭量化, 即在252行, 将
ret = rknn.build(do_quantization=QUANTIZE_ON, dataset=DATASET)
改为
ret = rknn.build(do_quantization=False, dataset=DATASET)
并仍指定输出结点为 'output', 则numpy array input0_data的大部分数量都是有效的.

在进行量化的情况下，在output节点包含坐标信息和置信度信息，坐标的数值范围为[0,img_size]（通常为640/416），而置信度的数值范围为[0,1]。量化过程中置信度的值会由于尺度太小，与坐标 concat 到同一个 tensor 时造成置信度值的精度丢失，所以会出现你说的output节点大部分数据都是0的情况。
这个问题是量化的特性，而非bug。
推荐使用example的输出形式去做量化。或者你可以考虑修改模型，避免将 position 和 score 合并到同一个tensor里面。

明白了,和我预想的一样.量化时,使用8bit整数类型来表示一个数据,为了保证在同一批数据中,最大的值不致溢出,最小的数就变成0了.

遇到了一个同样的问题，模型是centernet，i16量化精度没有损失，u8量化惨不忍睹。怀疑是这个问题，但是我的输出也是分开写的。配置方式大概是：
ret = rknnobj.load_onnx(model=model_path,
outputs=['kp_scores','kp_regs','kp_offset']
)
模型输出节点截图：

不知道是不是这个问题

可以试下精度分析，把掉精度多的层做个混合i16量化，具体请看userguide相关内容

在进行量化的情况下，在output节点包含坐标信息和置信度信息，坐标的数值范围为[0,img_size]（通常为640/416），而置信度的数值范围为[0,1]。量化过程中置信度的值会由于尺度太小，与坐标 concat 到同一个 tensor 时造成置信度值的精度丢失，所以会出现你说的output节点大部分数据都是0的情况。
这个问题是量化的特性，而非bug。
推荐使用example的输出形式去做量化。或者你可以考虑修改模型，避免将 position 和 score 合并到同一个tensor里面。

但是我量化后在模拟器中连接板子使用板子上的npu进行推理验证时候（即设置ret = rknn.init_runtime(target='rv1126')）这时候推理结果没有问题，但是后面使用C++部署在板子上推理时候发现就出现了置信度的数值由于尺度太小而被置零现象。这是为什么？对于同一个量化模型使用模拟器调用板子npu推理验证的和板子上部署推理出现了不同的结果（这里指置信度被置零问题）

authors: ZYJ-DE-GIT liangbch yinzeq zen-xingle

repo: rockchip-linux/rknn-toolkit


text:
Add application framework

Add an application framework which provides a standard widget interface, a set
of common widgets, and a high level application layer which manages all events.
The intent is to provide a high level framework that provides a more familiar
application development experience - similar to what one might see in Flutter, a
browser, GTK, etc.
The design is heavily influenced by Flutter, with a mix of Elm in there as well.
Notably this design uses far more mutation than in either, but this works to our
advantage in a language like Zig.
A widget must provide two functions: handleEvent and draw. Handle event
takes a context and an event. The context includes an ArrayList(Command) which
the widget may add commands to - such as "set the mouse shape to pointer", "give
this widget focus", "schedule an event to occur in 500 ms". The draw function
takes in a context as well. The DrawContext provides minimum and maximum size
constraints for the widget, as well as an arena allocator. The arena must be
used for all per-frame allocations in the draw context. draw returns a
Surface, which is an allocated buffer of terminal Cells. From here, the
application layer builds a tree of Surfaces which it uses to composite the
final scene, hit test for mouse events, and manage focus.
Unlike Elm, input events are sent to the focused widget instead of the root. The
design allows for adding a capturing phase, target phase, and bubbling phase for
all input events. Currently we only use target and bubbling (like Flutter), but
this can be extended to include capturing as well.

Demo of the fuzzy example. This example comes in at 235 LOC.
https://github.com/user-attachments/assets/a4637742-93ed-4d09-91cf-10740f17487b

repo: rockorager/libvaxis


text:
ImportError!

ImportError: cannot import name 'dense_features' from 'tensorflow.python.feature_column' (/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/python/feature_column/init.py)

tensorflow version <=1.14

So, how to solve this problem? I also met this.

authors: Freakwill rockyzhengwu zhengcong1

repo: rockyzhengwu/FoolNLTK


text:
No CallMethodActionExample

I am looking for an example of the above. I tried to modify the sample that I downloaded to use the above mentioned Method and the application crashed. What could I be doing wrong?

<recognizer:GestureRecognizer GestureModifier="Any" TriggerOnGesture="SwipeUp">
<ei:ChangePropertyAction PropertyName="Background"
TargetName="TouchArea"
Value="LightBlue" />
<ei:CallMethodAction MethodName="Test" TargetObject="TouchArea" />

Hi @dukefama,
You should be able to use any of the actions provided by Microsoft Expression Interactivity Core pretty much the same as the ChangePropertyAction available here: https://github.com/rodrigoelp/wpfgesturerecognizer/blob/master/src/SampleApp/MainWindow.xaml
Your code should look like
<Window x:Name="This">
  <Grid x:Name="TouchArea">
    <recognizer:GestureRecognizer TriggerOnGesture="SwipeDown">
      <ei: CallMethodAction TargetObject="{Binding ElementName=This}" MethodName="SomeMethod" />
    </recognizer:GestureRecognizer>
</Grid>
</Window>

With a code behind
public partial class MainWindow : Window {
    public void SomeMethod(object sender, RoutedEventArgs args) {
        Trace.TraceInformation("this should work");
    }
}

Sorry, I keep getting this error ,
could not find method named on object of type that matches the expected
signature CallMethodAction, Would you know why? And thanks for the swift
response.
On Tue, Aug 16, 2016 at 9:39 AM, Rod Landaeta notifications@github.com
wrote:

Hi @dukefama https://github.com/dukefama,
You should be able to use any of the actions provided by Microsoft
Expression Interactivity Core pretty much the same as the
ChangePropertyAction available here: https://github.com/rodrigoelp/
wpfgesturerecognizer/blob/master/src/SampleApp/MainWindow.xaml
Your code should look like

With a code behind
public partial class MainWindow : Window {
public void SomeMethod(object sender, RoutedEventArgs args) {
Trace.TraceInformation("this should work");
}
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rodrigoelp/wpfgesturerecognizer/issues/13#issuecomment-240038905,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE0L-QhXZU7K-SN2o-JbF7w6clu-YOpOks5qgXc_gaJpZM4Jkjmb
.

--
Famakinwa Babatunde
Software Developer/ 3d Animator
Blog: http://dukefama.wordpress.com
www.schoolsbox.com

@dukefama, please be aware I do not know the entirety of your code so providing something that might be useful is going to be pretty difficult for me unless you provide a bigger example than what you posted.
Now, looking at the code I can see that:

When you are referencing the TargetObject you are pointing to the TouchArea which (again, assuming that you copied parts of my example) is a Grid. Any Grid does not have a method named Test giving you this issue.

Assuming you do have a valid object that is going to receive the call. Do you have the right name? Is it really Test? WPF isn't precisely helpful when indicating this issue as it just provides the exception.

My suggestion, first check the TargetObject you are trying to use does exist and has the method defined. It does not matter if the method is void Test() or void Test(object sender, RoutedEventArgs args) as long as is reachable by WPF, this means the method isn't private nor internal.
Are you using MVVM? is the TargetObject part of your context? Is it a control?

This is the modifications I made to the example.
`

<i:Interaction.Triggers>
<recognizer:GestureRecognizer TriggerOnGesture="SwipeDown">
<ei:ChangePropertyAction PropertyName="Background"
TargetName="TouchArea"
Value="#000080" />
<ei:ChangePropertyAction PropertyName="Text"
TargetName="GestureRecognizedAs"
Value="Last gesture was Swipe Down with a single touch" />
</recognizer:GestureRecognizer>
<recognizer:GestureRecognizer GestureModifier="TwoFingers" TriggerOnGesture="SwipeDown">
<ei:ChangePropertyAction PropertyName="Background"
TargetName="TouchArea"
Value="#19198c" />
<ei:ChangePropertyAction PropertyName="Text"
TargetName="GestureRecognizedAs"
Value="Last gesture was Swipe Down with two touches" />
</recognizer:GestureRecognizer>
<recognizer:GestureRecognizer GestureModifier="ThreeFingers" TriggerOnGesture="SwipeDown">
<ei:ChangePropertyAction PropertyName="Background"
TargetName="TouchArea"
Value="#323299" />
<ei:ChangePropertyAction PropertyName="Text"
TargetName="GestureRecognizedAs"
Value="Last gesture was Swipe Down with three touches" />
</recognizer:GestureRecognizer>
<recognizer:GestureRecognizer GestureModifier="FourFingers" TriggerOnGesture="SwipeDown">
<ei:ChangePropertyAction PropertyName="Background"
TargetName="TouchArea"
Value="#4c4ca6" />
<ei:ChangePropertyAction PropertyName="Text"
TargetName="GestureRecognizedAs"
Value="Last gesture was Swipe Down with four touches" />
</recognizer:GestureRecognizer>
<recognizer:GestureRecognizer GestureModifier="FiveFingers" TriggerOnGesture="SwipeDown">
<ei:ChangePropertyAction PropertyName="Background"
TargetName="TouchArea"
Value="#6666b2" />
<ei:ChangePropertyAction PropertyName="Text"
TargetName="GestureRecognizedAs"
Value="Last gesture was Swipe Down with five touches" />
</recognizer:GestureRecognizer>
<recognizer:GestureRecognizer GestureModifier="Any" TriggerOnGesture="SwipeUp">
<ei:ChangePropertyAction PropertyName="Background"
TargetName="TouchArea"
Value="LightBlue" />
<ei:CallMethodAction MethodName="Test" TargetObject="TouchArea" />
</recognizer:GestureRecognizer>
<recognizer:GestureRecognizer TriggerOnGesture="SwipeRight">
<ei:ChangePropertyAction PropertyName="Background"
TargetName="TouchArea"
Value="LightGreen" />
<ei:ChangePropertyAction PropertyName="Text"
TargetName="GestureRecognizedAs"
Value="Last gesture was Swipe Right" />
</recognizer:GestureRecognizer>
<recognizer:GestureRecognizer TriggerOnGesture="SwipeLeft">
<ei:ChangePropertyAction PropertyName="Background"
TargetName="TouchArea"
Value="DarkGreen" />
<ei:ChangePropertyAction PropertyName="Text"
TargetName="GestureRecognizedAs"
Value="Last gesture was Swipe Left" />
</recognizer:GestureRecognizer>
<recognizer:GestureRecognizer TriggerOnGesture="Tap">
<ei:ChangePropertyAction PropertyName="Background"
TargetName="TouchArea"
Value="LightPink" />
<ei:ChangePropertyAction PropertyName="Text"
TargetName="GestureRecognizedAs"
Value="Last gesture was a Tap" />
</recognizer:GestureRecognizer>
</i:Interaction.Triggers>

public void Test()
{
MessageBox.Show("I am touched");
}`
Please kindly tell me what I am doing wrong. Thanks a lot

Yup, so the target of your CallMethodAction is pointing to the Grid named TouchArea  instead of the object on which you defined the method.
Look at
<ei:CallMethodAction TargetObject="TouchArea" />

You are indicating to WPF that needs to use that object as the target of the action (whatever that action is going to be) and that object is defined at the top as a Grid
<Grid x:Name="TouchArea" />

To pass the action to the right object, you need to provide a name to the object associated via the TargetObject (which in this case is the MainWindow object)
One way to fix it is,

Define a name for the Window tag.
Use that name on the TargetObject property of the CallMethodAction tag.

That should fix your issue.

authors: dukefama rodrigoelp

repo: rodrigoelp/wpfgesturerecognizer


text:
Logout/Delete account fails

'NoneType' object has no attribute 'language' (/base/data/home/apps/e~rogerthat-server/20180529t134853.410060501450369130/add_1_monkey_patches.py:127)
Traceback (most recent call last):
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/277b61042b697c7a_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1511, in __call__
    rv = self.handle_exception(request, response, e)
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/277b61042b697c7a_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1505, in __call__
    rv = self.router.dispatch(request, response)
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/277b61042b697c7a_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1253, in default_dispatcher
    return route.handler_adapter(request, response)
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/277b61042b697c7a_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1077, in __call__
    return handler.dispatch()
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/277b61042b697c7a_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 547, in dispatch
    return self.handle_exception(e, self.app.debug)
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/277b61042b697c7a_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 545, in dispatch
    return method(*args, **kwargs)
  File "/base/data/home/apps/e~rogerthat-server/20180529t134853.410060501450369130/rogerthat/pages/account.py", line 66, in post
    reason = localize(user_profile.language, "Your account has been deleted on your request")
AttributeError: 'NoneType' object has no attribute 'language'

I know this is a server error, but the user should not be able to delete his account 2 times

repo: rogerthat-platform/rogerthat-ios-client


text:
Error while installing pappy via pip on Kali Rolling 2017.2

pip install pappy
Collecting pappy
  Using cached pappy-0.91.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-pJrzAI/pappy/setup.py", line 2, in <module>
        from Pyrex.Distutils.extension import Extension
    ImportError: No module named Pyrex.Distutils.extension

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-pJrzAI/pappy/

OS: 4.12.0-kali2-amd64 #1 SMP Debian 4.12.12-2kali1 (2017-09-13) x86_64 GNU/Linux
Python: Python 2.7.13
Pip: pip 9.0.1 from /usr/lib/python2.7/dist-packages (python 2.7)

Same with Archlinux, Python 3.6.6, Python 2.7.15, pip 18.0 from /usr/lib/python2.7/site-packages/pip (python 2.7) and pip 18.0 from /usr/lib/python3.6/site-packages/pip (python 3.6).

pyres is not in your setup.py, is not available on pypi for our python/pip versions, and is not listed on your requirements.

authors: RickTorresJr noraj

repo: roglew/pappy-proxy


text:
Camera is accessible via ssh but web app is failing

Hi,
A few days ago my camera wasn't available anymore using webrtc, but it is available using the YI app.
When I try to access it it looks like this, with the following error on the browser console:
Error: <path> attribute d: Expected number, "…2.097898,1.5862amundomario, role…".

I still have ssh access, so I tried looking at dmesg logs and this is what I got:
[    0.558622] sunxi-mmc sdc1: smc 1 p1 err, cmd 55, RTO !!
[    0.559456] sunxi-mmc sdc1: smc 1 p1 err, cmd 55, RTO !!
[    0.560292] sunxi-mmc sdc1: smc 1 p1 err, cmd 55, RTO !!
[    0.560334] sunxi-mmc sdc1: sdc set ios:clk 400000Hz bm OD pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B
[    0.561258] sunxi-mmc sdc1: smc 1 p1 err, cmd 1, RTO !!
[    0.561288] sunxi-mmc sdc1: sdc set ios:clk 0Hz bm PP pm OFF vdd 0 width 1 timing LEGACY(SDR12) dt B
[    0.640374] sunxi-codec-machine sndcodec: [sunxi_card_dev_probe] register card finished.
[    0.640993] NET: Registered protocol family 17
[    0.641042] NET: Registered protocol family 15
[    0.641072] Key type dns_resolver registered
[    0.641667] Registering SWP/SWPB emulation handler
[    0.646981] sunxi-rtc rtc: setting system clock to 2024-07-15 22:46:00 UTC (1721083560)
[    0.647816] snddaudio snddaudio0: codec: snd-soc-dummy, codec_dai: snd-soc-dummy-dai.
[    0.648350] snddaudio snddaudio0: snd-soc-dummy-dai <-> daudio0 mapping ok
[    0.649647] ALSA device list:
[    0.649656]   #0: sun8iw19-codec
[    0.649659]   #1: snddaudio0
[    0.649716] Warning: unable to open an initial console.
[    0.654072] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
[    0.655696] devtmpfs: mounted
[    0.655934] Freeing unused kernel memory: 108K
[    0.655938] This architecture does not have kernel memory protection.
[    0.672107] random: fast init done
[    0.693970] sunxi-mmc sdc0: sdc set ios:clk 0Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B
[    0.694023] sunxi-mmc sdc0: Switching to 1.8V signalling voltage ok
[    0.712051] sunxi-mmc sdc0: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B
[    0.719726] mmc0: host does not support reading read-only switch, assuming write-enable
[    0.720435] sunxi-mmc sdc0: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 4 timing LEGACY(SDR12) dt B
[    0.721263] sunxi-mmc sdc0: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 4 timing UHS-SDR104 dt B
[    0.721348] sunxi-mmc sdc0: sdc set ios:clk 150000000Hz bm PP pm ON vdd 21 width 4 timing UHS-SDR104 dt B
[    0.721492] mmc0: new ultra high speed SDR104 SDHC card at address 1388
[    0.722897] mmcblk0: mmc0:1388 USD00 14.7 GiB
[    0.724792]  mmcblk0: p1
[    1.179488] udevd[535]: could not create /run/udev: No such file or directory
[    3.106481] sunxi-wlan wlan: bus_index: 1
[    3.226115] sunxi-mmc sdc1: sdc set ios:clk 0Hz bm PP pm UP vdd 21 width 1 timing LEGACY(SDR12) dt B
[    3.244017] sunxi-mmc sdc1: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B
[    3.264710] sunxi-mmc sdc1: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B
[    3.267205] sunxi-mmc sdc1: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B
[    3.269088] sunxi-mmc sdc1: smc 1 p1 err, cmd 8, RTO !!
[    3.272346] sunxi-mmc sdc1: card claims to support voltages below defined range
[    3.283552] sunxi-mmc sdc1: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing SD-HS(SDR25) dt B
[    3.283674] sunxi-mmc sdc1: sdc set ios:clk 50000000Hz bm PP pm ON vdd 21 width 1 timing SD-HS(SDR25) dt B
[    3.283834] sunxi-mmc sdc1: sdc set ios:clk 50000000Hz bm PP pm ON vdd 21 width 4 timing SD-HS(SDR25) dt B
[    3.284607] mmc1: new high speed SDIO card at address 0001
[    3.298770] random: crng init done
[    3.444617] [sc3335_mipi]V4L2_IDENT_SENSOR = 0xcc1a
[    3.457021] sunxi_gpadc_init,1779, success
[    3.457829] input: sunxi-gpadc0 as /devices/virtual/input/input0
[    3.457891] sunxi_gpadc_probe success
[    5.313401] libphy: 5020000.eth: probed
[    5.313810] sunxi-gmac 5020000.eth eth0: eth0: Type(6) PHY ID 0000ffff at 31 IRQ poll (5020000.eth-0:1f)
[    5.315821] sunxi-gmac 5020000.eth eth0: Initialize hardware error
[    5.703674] cpld_periph: loading out-of-tree module taints kernel.
[    5.709632]
[    5.709632] [CPLD_PERIPH] ir_led_ctl: 0, ircut_direction: 0 audio_ctl:0
[    5.709833]
[    5.709833] [CPLD_PERIPH] cpld_init ok, [ ver=Aug 16 2021, 10:46:41 ]
[    5.709901] can't request wifi_en gpio[198]
[    5.710265] [CPLD_PERIPH] pwm init ok.
[    5.710273] [CPLD_PERIPH] timer init ok.
[    5.710277] timer resolution:4 MHZ
[    5.710280] [CPLD_PERIPH] HZ = 250
[    7.146822] hw8_xy:[0],hw12_ab_cd_ratio[0],hw23_26_x_step:[0],hw27_30_y_step:[0]
[    7.477738] Adding 65532k swap on /tmp/sd/swapfile.  Priority:-1 extents:20 across:66684k SS
[    9.255462] [CPLD_PERIPH] Timer closed.
[    9.255474] [CPLD_PERIPH] Timer opened.
[   11.322889] cedar_ve: VE real_fre=300000000
[   11.597112] snddaudio snddaudio0: codec_dai set sysclk failed
[   11.597123] snddaudio snddaudio0: codec_dai set set_pll failed.
[   11.597129] snddaudio snddaudio0: codec dai set fmt failed
[   11.597148] snddaudio snddaudio0: codec_dai set clkdiv failed
[   12.071981] -----> wait adc hw ready
[   12.120795] snddaudio snddaudio0: codec_dai set sysclk failed
[   12.120805] snddaudio snddaudio0: codec_dai set set_pll failed.
[   12.120810] snddaudio snddaudio0: codec dai set fmt failed
[   12.120829] snddaudio snddaudio0: codec_dai set clkdiv failed
[   12.191300] [sc3335_mipi]V4L2_IDENT_SENSOR = 0xcc1a
[   12.288111] into set sensor hfilp the value:1
[   12.288657] [VIN]sensor_flip_option:isp0 reset!!!
[   12.288710] into set sensor hfilp the value:1
[   12.289244] [VIN]sensor_flip_option:isp0 reset!!!
[   12.290152] cedar_ve: VE real_fre=300000000
[   12.290225] cedar_ve: VE real_fre=300000000
[   12.292928] cedar_ve: VE real_fre=300000000
[   18.432185] [CPLD_PERIPH] Timer closed.
[   19.540012] -----> wait adc hw ready
[   19.588912] snddaudio snddaudio0: codec_dai set sysclk failed
[   19.588940] snddaudio snddaudio0: codec_dai set set_pll failed.
[   19.588946] snddaudio snddaudio0: codec dai set fmt failed
[   19.588966] snddaudio snddaudio0: codec_dai set clkdiv failed
[   19.593162] [sc3335_mipi]V4L2_IDENT_SENSOR = 0xcc1a
[   19.633215] [sc3335_mipi]V4L2_IDENT_SENSOR = 0xcc1a
[   19.665329] cedar_ve: VE real_fre=300000000
[   19.756452] cedar_ve: VE real_fre=300000000
[   20.005739] cedar_ve: VE real_fre=300000000
[   45.912825]
[   45.912825] [PID_LIST] pid_list_init ok, [ ver=Aug 16 2021, 10:46:40 ]

I thought about running unbrick but in my backup file I can only see .conf files, not the .bin files mentioned in the wiki.
Is there a way to solve it without unbrick?
If not, is there a way to perform a backup that includes the bin files using ssh?
Thanks a lot!

I have formatted the sd card and reinstalled the hack and everything is back to normal.
I'm still wondering how to get the bin files described in the unbrick guide.

Solved by formatting the sd card and reinstall the hack

Good to know.


text:
Vale cannot handle parenthesis in search terms

The SSG has a number of word usage guidance items that includes parenthesis. Vale does not like parenthesis in search terms, and doesn't seem to be able to search for the escaped characters, for example \( or \).
Example rule (red-hat-network-satellite-server.yml):
extends: substitution
message: "Use '%s' instead of '%s'."
link: https://redhat-documentation.github.io/supplementary-style-guide/#red-hat-network-satellite-server
ignorecase: true
level: error
action:
  name: replace
source: Red Hat
swap:
    Red Hat Satellite (Server) : Red Hat Network Satellite Server

In Atom, the following error is displayed:
E201 Invalid value provided [/home/kquinn/openshift-docs/.vale/styles/Red-Hat-CCS/SupplementaryStyleGuide/red-hat-network-proxy-server.yml:10:5]:

   9  swap:
  10*     Red Hat Proxy (Server) : Red Hat Network Proxy Server

capture group not supported; use '(?:' instead of '('

Execution stopped with code 1.

Need to do this:
"You need to use Red Hat Proxy (Server) and then set nonword: true to drop the word boundaries (\b)."
From jdkato on Vale slack 😎

I think we can close this.

repo: rolfedh/studious-fortnight


text:
Unimplemented rpc error for MaxBlobSize

something wrong rpc error: code = Unimplemented desc = unknown method MaxBlobSize for service da.DAService
10:12AM ERR DA layer submission failed error="unable to get DA max blob size" attempt=11 module=BlockManager

this is happening because celestia-da (main branch and last release) used go-da 57bc36006772 which does not have MaxBlobSize.
we should update this to use 93600f2 which has the api MaxBlobSize.

I have a PR , please review it -> https://github.com/rollkit/celestia-da/pull/40

repo: rollkit/celestia-da