Trying to execute http calls

Hey @yuval-k,
I hope you are doing well.
I created this PR seeking for some help.
I've been trying to make an HTTP call from my Filter to another service using a proxy call with no success.
What I need to do is to make an HTTP call to another service on my 'onRequestHeaders' event, hold the execution, and only Continue after I get the response.
Here is part of my source code.
onRequestHeaders(headers: u32): FilterHeadersStatusValues {
    log(LogLevelValues.debug, "ExpoFilterContext.onRequestHeaders:" + headers.toString());

    const headers_map = stream_context.headers.request.get_headers();
    log(LogLevelValues.debug, "headers_map: " + headers_map.toString());

    const configuration = this.root_context.configuration;
    const expo_header = stream_context.headers.request.get("x-wmt-expo");
    this.xpa.push(expo_header+":"+configuration);

    stream_context.headers.request.add("x-wmt-expo-request", this.xpa.join(","));
    log(LogLevelValues.debug, "ExpoFilterContext.onRequestHeaders: Injecting x-wmt-expo-request=" + this.xpa.join(","));

    log(LogLevelValues.debug, "trying to execute an httpCall with non converted: " + stream_context.headers.request.get_headers().toString() + ":" + new ArrayBuffer(0).toString() + ":" + ":" + this.context_id.toString());

    let result = this.root_context.httpCall("echo_service",
      stream_context.headers.request.get_headers(),
      new ArrayBuffer(0),
      new Array<HeaderPair>(),
      1000,
      (headers: u32,  body_size: usize, trailers: u32) => {
        log(LogLevelValues.debug, "callback called!");
        log(LogLevelValues.debug, "headers: " + headers.toString() + ", body_size: " + body_size.toString() + ", trailers: " + trailers.toString());
      });

    if (result === WasmResultValues.Ok) {
      log(LogLevelValues.debug, "HttpCallback: " + result.toString());
      return FilterHeadersStatusValues.Continue;
    }

    return FilterHeadersStatusValues.StopIteration;
  }

I'm not sure I'm doing this right. I didn't want to bother you but have been struggling for a couple of days now.
Thank you in advance,
Mario

Here is the error message I got on Envoy:
 [2020-04-10 01:15:32.861][19][debug][wasm] [source/extensions/common/wasm/context.cc:1089] wasm log expo_filter_name expo_filter_root_id: ExpoFilterContext.onRequestHeaders:8 proxy_1        | [2020-04-10 01:15:32.861][19][debug][wasm] [source/extensions/common/wasm/context.cc:1089] wasm log expo_filter_name expo_filter_root_id: ExpoFilterContext.onRequestHeaders: Injecting x-wmt-expo-request=testValue:configuration example proxy_1        | [2020-04-10 01:15:32.861][19][debug][wasm] [source/extensions/common/wasm/context.cc:1089] wasm log expo_filter_name expo_filter_root_id: trying to execute an httpCall with non converted: :[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer]:[object ArrayBuffer]::0 proxy_1        | [2020-04-10 01:15:32.861][19][debug][wasm] [source/extensions/common/wasm/context.cc:1089] wasm log expo_filter_name expo_filter_root_id: trying to execute an httpCall with non converted: echo_service:[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer]:[object ArrayBuffer]::1000:0 proxy_1        | [2020-04-10 01:15:32.861][19][debug][wasm] [source/extensions/common/wasm/context.cc:1089] wasm log expo_filter_name expo_filter_root_id: pairs[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer],[object ArrayBuffer]:[object ArrayBuffer] proxy_1        | [2020-04-10 01:15:32.861][19][critical][wasm] [source/extensions/common/wasm/context.cc:1101] wasm log expo_filter_name expo_filter_root_id: Index out of range proxy_1        | [2020-04-10 01:15:32.861][19][critical][main] [source/exe/terminate_handler.cc:13] std::terminate called! (possible uncaught exception, see trace) proxy_1        | [2020-04-10 01:15:32.861][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers): proxy_1        | [2020-04-10 01:15:32.861][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:92] Envoy version: d29f7a659ba736aab97697a7bcfc69a71bc66b66/1.14.0-dev/Clean/RELEASE/BoringSSL proxy_1        | [2020-04-10 01:15:32.870][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #0: Envoy::TerminateHandler::logOnTerminate()::$_0::operator()() [0x557739c60bbe] proxy_1        | [2020-04-10 01:15:32.878][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #1: [0x557739c60ac9] proxy_1        | [2020-04-10 01:15:32.887][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #2: std::__terminate() [0x55773a1e7893] proxy_1        | [2020-04-10 01:15:32.897][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #3: Envoy::Extensions::Common::Wasm::V8::V8::registerHostFunctionImpl<>()::{lambda()#1}::operator()() [0x557738a601b2] proxy_1        | [2020-04-10 01:15:32.905][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #4: Envoy::Extensions::Common::Wasm::V8::V8::registerHostFunctionImpl<>()::{lambda()#1}::__invoke() [0x557738a600b7] proxy_1        | [2020-04-10 01:15:32.912][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #5: wasm::FuncData::v8_callback() [0x557738a7448f] proxy_1        | [2020-04-10 01:15:32.913][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #6: [0xdc1315dec2a] proxy_1        | [2020-04-10 01:15:32.913][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #7: [0xdc1315d93a1] proxy_1        | [2020-04-10 01:15:32.913][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #8: [0xdc1315d8927] proxy_1        | [2020-04-10 01:15:32.913][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #9: [0xdc1315d608f] proxy_1        | [2020-04-10 01:15:32.914][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #10: [0xdc1315d2210] proxy_1        | [2020-04-10 01:15:32.914][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #11: [0xdc1315cd876] proxy_1        | [2020-04-10 01:15:32.914][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #12: [0xdc1315cc319] proxy_1        | [2020-04-10 01:15:32.914][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #13: [0xdc1315d5dc7] proxy_1        | [2020-04-10 01:15:32.914][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #14: [0x1d59000834fc] proxy_1        | [2020-04-10 01:15:32.922][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #15: v8::internal::Execution::CallWasm() [0x557738b4dc53] proxy_1        | [2020-04-10 01:15:32.929][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #16: wasm::Func::call() [0x557738a737f3] proxy_1        | [2020-04-10 01:15:32.937][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #17: Envoy::Extensions::Common::Wasm::V8::V8::getModuleFunctionImpl<>()::{lambda()#1}::operator()() [0x557738a5d067] proxy_1        | [2020-04-10 01:15:32.946][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #18: Envoy::Extensions::Common::Wasm::Context::onRequestHeaders() [0x557738a25304] proxy_1        | [2020-04-10 01:15:32.954][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #19: Envoy::Extensions::Common::Wasm::Context::decodeHeaders() [0x557738a2789a] proxy_1        | [2020-04-10 01:15:32.961][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #20: Envoy::Http::ConnectionManagerImpl::ActiveStream::decodeHeaders() [0x557739a01469] proxy_1        | [2020-04-10 01:15:32.968][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #21: Envoy::Http::ConnectionManagerImpl::ActiveStream::decodeHeaders() [0x557739a00693] proxy_1        | [2020-04-10 01:15:32.975][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #22: Envoy::Http::Http1::ServerConnectionImpl::onMessageComplete() [0x557739a14336] proxy_1        | [2020-04-10 01:15:32.982][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #23: Envoy::Http::Http1::ConnectionImpl::onMessageCompleteBase() [0x557739a12bc6] proxy_1        | [2020-04-10 01:15:32.990][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #24: Envoy::Http::Http1::ConnectionImpl::$_8::__invoke() [0x557739a1729d] proxy_1        | [2020-04-10 01:15:32.997][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #25: http_parser_execute [0x557739ae7182] proxy_1        | [2020-04-10 01:15:33.005][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #26: Envoy::Http::Http1::ConnectionImpl::dispatchSlice() [0x557739a11caa] proxy_1        | [2020-04-10 01:15:33.012][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #27: Envoy::Http::Http1::ConnectionImpl::dispatch() [0x557739a11a61] proxy_1        | [2020-04-10 01:15:33.018][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #28: Envoy::Http::ConnectionManagerImpl::onData() [0x5577399fcb11] proxy_1        | [2020-04-10 01:15:33.024][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #29: Envoy::Network::FilterManagerImpl::onContinueReading() [0x5577397a589b] proxy_1        | [2020-04-10 01:15:33.031][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #30: Envoy::Network::ConnectionImpl::onReadReady() [0x5577397a199a] proxy_1        | [2020-04-10 01:15:33.037][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #31: Envoy::Network::ConnectionImpl::onFileEvent() [0x5577397a0cfd] proxy_1        | [2020-04-10 01:15:33.044][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #32: Envoy::Event::FileEventImpl::assignEvents()::$_0::__invoke() [0x55773979bf10] proxy_1        | [2020-04-10 01:15:33.050][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #33: event_process_active_single_queue [0x557739ae0adb] proxy_1        | [2020-04-10 01:15:33.058][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #34: event_base_loop [0x557739adf36e] proxy_1        | [2020-04-10 01:15:33.065][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #35: Envoy::Server::WorkerImpl::threadRoutine() [0x557739791af8] proxy_1        | [2020-04-10 01:15:33.072][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #36: Envoy::Thread::ThreadImplPosix::ThreadImplPosix()::$_0::__invoke() [0x557739c96c63] proxy_1        | [2020-04-10 01:15:33.072][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #37: start_thread [0x7fcb0a7476db] proxy_1        | [2020-04-10 01:15:33.072][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:104] Caught Aborted, suspect faulting address 0x1 proxy_1        | [2020-04-10 01:15:33.072][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers): proxy_1        | [2020-04-10 01:15:33.072][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:92] Envoy version: d29f7a659ba736aab97697a7bcfc69a71bc66b66/1.14.0-dev/Clean/RELEASE/BoringSSL proxy_1        | [2020-04-10 01:15:33.072][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #0: __restore_rt [0x7fcb0a752890] proxy_1        | [2020-04-10 01:15:33.079][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #1: [0x557739c60ac9] proxy_1        | [2020-04-10 01:15:33.079][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #2: std::__terminate() [0x55773a1e7893] proxy_1        | [2020-04-10 01:15:33.079][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #3: Envoy::Extensions::Common::Wasm::V8::V8::registerHostFunctionImpl<>()::{lambda()#1}::operator()() [0x557738a601b2] proxy_1        | [2020-04-10 01:15:33.079][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #4: Envoy::Extensions::Common::Wasm::V8::V8::registerHostFunctionImpl<>()::{lambda()#1}::__invoke() [0x557738a600b7] proxy_1        | [2020-04-10 01:15:33.079][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #5: wasm::FuncData::v8_callback() [0x557738a7448f] proxy_1        | [2020-04-10 01:15:33.079][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #6: [0xdc1315dec2a] proxy_1        | [2020-04-10 01:15:33.079][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #7: [0xdc1315d93a1] proxy_1        | [2020-04-10 01:15:33.080][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #8: [0xdc1315d8927] proxy_1        | [2020-04-10 01:15:33.080][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #9: [0xdc1315d608f] proxy_1        | [2020-04-10 01:15:33.080][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #10: [0xdc1315d2210] proxy_1        | [2020-04-10 01:15:33.080][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #11: [0xdc1315cd876] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #12: [0xdc1315cc319] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #13: [0xdc1315d5dc7] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #14: [0x1d59000834fc] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #15: v8::internal::Execution::CallWasm() [0x557738b4dc53] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #16: wasm::Func::call() [0x557738a737f3] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #17: Envoy::Extensions::Common::Wasm::V8::V8::getModuleFunctionImpl<>()::{lambda()#1}::operator()() [0x557738a5d067] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #18: Envoy::Extensions::Common::Wasm::Context::onRequestHeaders() [0x557738a25304] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #19: Envoy::Extensions::Common::Wasm::Context::decodeHeaders() [0x557738a2789a] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #20: Envoy::Http::ConnectionManagerImpl::ActiveStream::decodeHeaders() [0x557739a01469] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #21: Envoy::Http::ConnectionManagerImpl::ActiveStream::decodeHeaders() [0x557739a00693] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #22: Envoy::Http::Http1::ServerConnectionImpl::onMessageComplete() [0x557739a14336] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #23: Envoy::Http::Http1::ConnectionImpl::onMessageCompleteBase() [0x557739a12bc6] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #24: Envoy::Http::Http1::ConnectionImpl::$_8::__invoke() [0x557739a1729d] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #25: http_parser_execute [0x557739ae7182] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #26: Envoy::Http::Http1::ConnectionImpl::dispatchSlice() [0x557739a11caa] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #27: Envoy::Http::Http1::ConnectionImpl::dispatch() [0x557739a11a61] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #28: Envoy::Http::ConnectionManagerImpl::onData() [0x5577399fcb11] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #29: Envoy::Network::FilterManagerImpl::onContinueReading() [0x5577397a589b] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #30: Envoy::Network::ConnectionImpl::onReadReady() [0x5577397a199a] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #31: Envoy::Network::ConnectionImpl::onFileEvent() [0x5577397a0cfd] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #32: Envoy::Event::FileEventImpl::assignEvents()::$_0::__invoke() [0x55773979bf10] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #33: event_process_active_single_queue [0x557739ae0adb] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #34: event_base_loop [0x557739adf36e] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #35: Envoy::Server::WorkerImpl::threadRoutine() [0x557739791af8] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #36: Envoy::Thread::ThreadImplPosix::ThreadImplPosix()::$_0::__invoke() [0x557739c96c63] proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #37: start_thread [0x7fcb0a7476db] proxy_1        | ActiveStream 0x55773b383600, stream_id_:<PHONE_NUMBER>2965424882, state_.has_continue_headers_: 0, state_.is_head_request_: 1, state_.decoding_headers_only_: 0, state_.encoding_headers_only_: 0 proxy_1        | request_headers_: proxy_1        |   ':authority', 'localhost' proxy_1        |   ':path', '/' proxy_1        |   ':method', 'HEAD' proxy_1        |   'user-agent', 'curl/7.54.0' proxy_1        |   'accept', '*/*' proxy_1        |   'x-wmt-expo', 'testValue' proxy_1        |   'x-forwarded-proto', 'http' proxy_1        |   'x-request-id', '2d6d11ab-450f-4040-8e51-7b3db66531a9' proxy_1        |   'x-wmt-expo-request', 'testValue:configuration example' proxy_1        | request_trailers_: null proxy_1        | response_headers_: null proxy_1        | response_trailers_: null proxy_1        | &stream_info_: proxy_1        |   StreamInfoImpl 0x55773b383748, protocol_: 1, response_code_: null, response_code_details_: null, health_check_request_: 0, route_name_: proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:104] Caught Segmentation fault, suspect faulting address 0x0 proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers): proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:92] Envoy version: d29f7a659ba736aab97697a7bcfc69a71bc66b66/1.14.0-dev/Clean/RELEASE/BoringSSL proxy_1        | [2020-04-10 01:15:33.081][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #0: __restore_rt [0x7fcb0a752890] proxy_1        | [2020-04-10 01:15:33.088][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #1: [0x557739c60ac9] proxy_1        | [2020-04-10 01:15:33.088][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #2: std::__terminate() [0x55773a1e7893] proxy_1        | [2020-04-10 01:15:33.088][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #3: Envoy::Extensions::Common::Wasm::V8::V8::registerHostFunctionImpl<>()::{lambda()#1}::operator()() [0x557738a601b2] proxy_1        | [2020-04-10 01:15:33.088][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #4: Envoy::Extensions::Common::Wasm::V8::V8::registerHostFunctionImpl<>()::{lambda()#1}::__invoke() [0x557738a600b7] proxy_1        | [2020-04-10 01:15:33.088][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #5: wasm::FuncData::v8_callback() [0x557738a7448f] proxy_1        | [2020-04-10 01:15:33.088][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #6: [0xdc1315dec2a] proxy_1        | [2020-04-10 01:15:33.089][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #7: [0xdc1315d93a1] proxy_1        | [2020-04-10 01:15:33.089][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #8: [0xdc1315d8927] proxy_1        | [2020-04-10 01:15:33.089][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #9: [0xdc1315d608f] proxy_1        | [2020-04-10 01:15:33.089][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #10: [0xdc1315d2210] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #11: [0xdc1315cd876] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #12: [0xdc1315cc319] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #13: [0xdc1315d5dc7] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:98] #14: [0x1d59000834fc] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #15: v8::internal::Execution::CallWasm() [0x557738b4dc53] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #16: wasm::Func::call() [0x557738a737f3] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #17: Envoy::Extensions::Common::Wasm::V8::V8::getModuleFunctionImpl<>()::{lambda()#1}::operator()() [0x557738a5d067] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #18: Envoy::Extensions::Common::Wasm::Context::onRequestHeaders() [0x557738a25304] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #19: Envoy::Extensions::Common::Wasm::Context::decodeHeaders() [0x557738a2789a] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #20: Envoy::Http::ConnectionManagerImpl::ActiveStream::decodeHeaders() [0x557739a01469] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #21: Envoy::Http::ConnectionManagerImpl::ActiveStream::decodeHeaders() [0x557739a00693] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #22: Envoy::Http::Http1::ServerConnectionImpl::onMessageComplete() [0x557739a14336] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #23: Envoy::Http::Http1::ConnectionImpl::onMessageCompleteBase() [0x557739a12bc6] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #24: Envoy::Http::Http1::ConnectionImpl::$_8::__invoke() [0x557739a1729d] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #25: http_parser_execute [0x557739ae7182] proxy_1        | [2020-04-10 01:15:33.090][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #26: Envoy::Http::Http1::ConnectionImpl::dispatchSlice() [0x557739a11caa] proxy_1        | [2020-04-10 01:15:33.091][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #27: Envoy::Http::Http1::ConnectionImpl::dispatch() [0x557739a11a61] proxy_1        | [2020-04-10 01:15:33.091][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #28: Envoy::Http::ConnectionManagerImpl::onData() [0x5577399fcb11] proxy_1        | [2020-04-10 01:15:33.091][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #29: Envoy::Network::FilterManagerImpl::onContinueReading() [0x5577397a589b] proxy_1        | [2020-04-10 01:15:33.091][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #30: Envoy::Network::ConnectionImpl::onReadReady() [0x5577397a199a] proxy_1        | [2020-04-10 01:15:33.091][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #31: Envoy::Network::ConnectionImpl::onFileEvent() [0x5577397a0cfd] proxy_1        | [2020-04-10 01:15:33.091][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #32: Envoy::Event::FileEventImpl::assignEvents()::$_0::__invoke() [0x55773979bf10] proxy_1        | [2020-04-10 01:15:33.091][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #33: event_process_active_single_queue [0x557739ae0adb] proxy_1        | [2020-04-10 01:15:33.091][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #34: event_base_loop [0x557739adf36e] proxy_1        | [2020-04-10 01:15:33.091][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #35: Envoy::Server::WorkerImpl::threadRoutine() [0x557739791af8] proxy_1        | [2020-04-10 01:15:33.091][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #36: Envoy::Thread::ThreadImplPosix::ThreadImplPosix()::$_0::__invoke() [0x557739c96c63] proxy_1        | [2020-04-10 01:15:33.091][19][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:96] #37: start_thread [0x7fcb0a7476db]

I was able to advance and get to the point that I can make the HTTP call, but now there is an exception on the Envoy side. I believe the issue might still be in the headers serialization, but I don't have time to continue my investigation today. Will pick it up tomorrow.
Please let me know if you have any suggestions...
Thanks, Mario

the envoy model is a bit more complicated than that:
when httpCall returns ok, it doesn't mean the http request finished.
only when the callback is called, you know it had finished. this may or may not happen when httpCall returns.
In addition, once the http call returns, it will be in the context of the root context. you'll need to switch back to the request context to continue the request (proxy_continue_request), assuming you hit StopIteration .
I know it's a lot to take in... essentially the web assembly api is very similar to the envoy internal api in that regard.

Hey @yuval-k, Thanks for the reply.
You are right about the envoy model, I should probably only stop iteration if the call returned Ok and log the error and continue if it fails, like this:
   if (result === WasmResultValues.Ok) {
      log(LogLevelValues.debug, "Stop Iteration to wait for HTTP response.");
      return FilterHeadersStatusValues.StopIteration;
    }

  log(LogLevelValues.debug, "Error trying to make HTTP call. Continue iteration...");
  return FilterHeadersStatusValues.Continue;

However, I'm not sure I understood how the setEffectiveContext() work. How will the BaseContext know what is the effectiveContext to assign the response? Do I need to pass the context_id to the callback function? How could I do that?
Thanks again,
Mario

you want to save the current context (i.e. this) in the callback, and then call ctx.setEffectiveContext() to set the context back to the request context.

Hey @yuval-k,
I finally figure out a way to get the HTTP calls working as expected. However, the number of changes in the project is huge and I kinda lost track of them.
I'm sorry for such a long PR, but I think I'm getting there now. I hope you can find the time to review it.
Here is the current version of my plugin:
// @ts-ignore - this export is valid and should not trigger validation issues
export * from "@solo-io/proxy-runtime/proxy"; // this export the required functions for the proxy to interact with us.
import { LogLevelValues, log, Context, ContextHelper, FilterHeadersStatusValues, registerRootContext, RootContext, RootContextHelper, stream_context, WasmResultValues, HeaderPair } from "@solo-io/proxy-runtime";

class ExpoFilterContext extends Context {

  xpa: Array<string>;

  constructor(context_id:u32,  root_context: RootContext) {
    super(context_id, root_context);
    log(LogLevelValues.debug, "ExpoFilterContext - context id: " + this.context_id.toString()  + ", root_context_id: " + this.root_context.context_id.toString());
    this.xpa = new Array<string>();
  }

  onRequestHeaders(headers: u32): FilterHeadersStatusValues {
    log(LogLevelValues.debug, "ExpoFilterContext - context id: " + this.context_id.toString()  + " onRequestHeaders(headers: " + headers.toString() + ")");

    const configuration = this.root_context.getConfiguration();
    const expo_header = stream_context.headers.request.get("x-wmt-expo");
    this.xpa.push(expo_header+":"+configuration);

    stream_context.headers.request.add("x-wmt-expo-request", this.xpa.join(","));
    log(LogLevelValues.debug, "ExpoFilterContext - context id: " + this.context_id.toString()  + " Injecting x-wmt-expo-request=" + this.xpa.join(","));

    let result = this.root_context.httpCall("echo_service",
      stream_context.headers.request.get_headers(),
      new ArrayBuffer(0),
      new Array<HeaderPair>(),
      10,
      this.context_id,
      (origin_context_id: u32, headers: u32,  body_size: usize, trailers: u32) => {
        log(LogLevelValues.debug, "ExpoFilterContext - callback called - origin_context_id: " + origin_context_id.toString() + ", headers: " + headers.toString() + ", body_size: " + body_size.toString() + ", trailers: " + trailers.toString());
        stream_context.headers.request.add("x-wmt-expo-from-another-service", headers.toString());
      });

    if (result === WasmResultValues.Ok) {
      log(LogLevelValues.debug, "ExpoFilterContext - context id: " + this.context_id.toString()  + " Http call executed with result: " + result.toString() + ". Stop Iteration on context id: " + this.context_id.toString());
      return FilterHeadersStatusValues.StopIteration;
    }

    log(LogLevelValues.debug, "ExpoFilterContext - context id: " + this.context_id.toString()  + " Failed to execute http call with result: " + result.toString());
    return FilterHeadersStatusValues.Continue;
  }

  onResponseHeaders(headers: u32): FilterHeadersStatusValues {
    log(LogLevelValues.debug, "ExpoFilterContext - context id: " + this.context_id.toString()  + " ExpoFilterContext.onResponseHeaders:" + headers.toString());

    stream_context.headers.response.add("x-wmt-expo-response", this.xpa.join(","));
    log(LogLevelValues.debug, "ExpoFilterContext - context id: " + this.context_id.toString()  + " ExpoFilterContext.onResponseHeaders: Injecting x-wmt-expo-response=" + this.xpa.join(","));

    return FilterHeadersStatusValues.Continue;
  }

}

registerRootContext(
  (context_id: u32) => {
    log(LogLevelValues.debug, "createRootContext(context_id: " + context_id.toString() + ")");
    return RootContextHelper.wrap(new RootContext(context_id));
  },
  (context_id: u32, root_context: RootContext) => {
    log(LogLevelValues.debug, "createContext(context_id: " + context_id.toString() + ", root_context: " + root_context.context_id.toString() + ")");
    return ContextHelper.wrap(new ExpoFilterContext(context_id, root_context));
  },
  "expo_filter_root_id");

I'm being super careful to not let my plugin make calls to the proxy without going thru the API. If you see, I'm not importing the interfaces to call the proxy directly from my plugin and that is very intentional. From what I've seen in examples in C++, people can go crazy with those, but I think it  is important to keep the separation of concerns there.

Ok @yuval-k,
I've made the changes you asked.


feat(wallet-connect): Check if app exists as a Safe App

What it solves
resolves #167
How this PR fixes it
We are checking if an app exists as a Safe App. In this case we are asking the user for decide to use the Safe App or continue using Wallet Connect
As part of this task we are revamping the whole UI following this designs and workflow
https://www.figma.com/file/iicHRaXd0ypyttJqq2WMga/Wallet-Connect?node-id=13%3A3195
How to test it

Open Wallet Connect app
Open any Dapp as Uniswap o Sushiswap in a new window and try to connect
When connecting => If the app exists as a safe app should prompt the user to open it if preferred
User can choose to continue using the Wallet Connect app
When executing transaction from the dapps the safe popup should appear

Check figma designs for the complete flow

Hola guys! Loving the new design. I have a couple of suggestions.
For this screen:

When a user reaches it connection has already been stablished via wallet connect. What we do is:
-if the user chooses to open the dapp we terminate the session and open the safe app.
-If the user chooses to keep using wallet connect we keep it.
Maybe we should change the trying to connect message?
Regarding that screen also, if we refresh the page the session is lost (which is expected) but if we instead leave the app and move to another section on the safe the session will be kept. I think it would be to terminate it as well.
What do you think @dasanra @yagopv @liliiaorlenko ?

Hola guys! Loving the new design. I have a couple of suggestions.
For this screen:
When a user reaches it connection has already been stablished via wallet connect. What we do is:
-if the user chooses to open the dapp we terminate the session and open the safe app.
-If the user chooses to keep using wallet connect we keep it.
Maybe we should change the trying to connect message?
Regarding that screen also, if we refresh the page the session is lost (which is expected) but if we instead leave the app and move to another section on the safe the session will be kept. I think it would be nice to terminate it as well.
What do you think @dasanra @yagopv @liliiaorlenko ?

I think better to keep message as is it, because no matter if we already connected app or not, we need to encourage user to use Safe app instead and creating passive message that "you have already been connected but if u want u can user Safe app" is not ideal strategy. In this case not showing exact state of the system is better for us to not let person use app that is optimised :P
Also, do you think we need a designs for the screen when we show that the last connection has been lost, in case user made a mistake? @dasanra
And another question from the design: Are we changing the style of the buttons or its more depended on a react team?

Also, do you think we need a designs for the screen when we show that the last connection has been lost, in case user made a mistake? => Not sure about what's this about :( When we show that state ?
Are we changing the style of the buttons or its more depended on a react team? => Do you mean about the button not being exactly the same as the one in the design ? We are using a library under our control => https://components.gnosis-safe.io/?path=/docs/inputs-button--simple-button

All bueno, gracias Yago ;)


Removes all references to ie_mob

ie_mob has been marked as a dead browser by browserslist and is thus no longer returned in caniuse-api queries when it depends on latest browserslist.
This pull request removes all references to ie_mob from the codebase and documentation.
Fixes #191

Hey @robinweser is this good to merge?

Yeah, I'm about to do that asap!


🎉 1.1.5

ℹ About this release

Version: 1.1.5
Type: patch
Last Release: 1.1.4 (4/15/2024, 8:18:02 PM) [?]
Commits to merge: 9 [?]

🐛 Bug Fixes

Correct year in order emails (9ef1f04)

📦 Dependencies

Update @prisma/client from ^5.12.1 to ^5.13.0
Update @sentry/node from ^7.109.0 to ^7.112.2
Update ical-generator from ^7.0.0 to ^7.1.0
Update mailparser from ^3.6.9 to ^3.7.0

📦 Development Dependencies

Update prisma from ^5.12.1 to ^5.13.0

:tada: This PR is included in version 1.1.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v1.1.5

Your semantic-release bot :package::rocket:


hi, i really need help

I have bug when try to use

Please update to latest version, thanks!
Feel free to reopen


Please update cocoapods

DPRadialMenu in Github is newer than Cocoapods.
There isn't important feature in Cocoapods.

Simply add the following line to your Cocoapods:
pod 'DPRadialMenu', :git => 'https://github.com/dariopellegrini/DPRadialMenu.git'
It will use the latest commit in the repo instead of the Cocoapods version.
Hope this helps.


HA cluster with [default backend - 404] issues

I'm presented with a default backend - 404 message into Rancher 2.3.2 UI. The issue is namespace cattle-system is not created on initial install:
[root@ip-10-25-55-90 ~]# kubectl get ingress -n cattle-system -o wide
No resources found in cattle-system namespace.

What do you recommend me to look into, in order to force the creation of this particular namespace? Into past, I simply terminated one of the EC2 instances part of HA cluster and everything would be fixed. However, this is not the case anymore, please see the details below.
[root@ip-10-25-55-90 ~]# kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.3", GitCommit:"b3cbbae08ec52a7fc73d334838e18d17e8512749", GitTreeState:"clean", BuildDate:"2019-11-13T11:23:11Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"20c265fef0741dd71a66480e35bd69f18351daea", GitTreeState:"clean", BuildDate:"2019-10-15T19:07:57Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}

[root@ip-10-25-55-90 ~]# docker version
Client:
 Version:         1.13.1
 API version:     1.26
 Package version: docker-1.13.1-103.git7f2769b.el7.centos.x86_64
 Go version:      go1.10.3
 Git commit:      7f2769b/1.13.1
 Built:           Sun Sep 15 14:06:47 2019
 OS/Arch:         linux/amd64

Server:
 Version:         1.13.1
 API version:     1.26 (minimum version 1.12)
 Package version: docker-1.13.1-103.git7f2769b.el7.centos.x86_64
 Go version:      go1.10.3
 Git commit:      7f2769b/1.13.1
 Built:           Sun Sep 15 14:06:47 2019
 OS/Arch:         linux/amd64
 Experimental:    false

[root@ip-10-25-55-90 ~]# uname -a
Linux ip-10-25-55-90.us-west-2.compute.internal 3.10.0-1062.9.1.el7.x86_64 #1 SMP Fri Dec 6 15:49:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

[root@ip-10-25-55-90 ~]# getenforce
Enforcing

After a HA node forceful termination:
[root@ip-10-25-55-90 ~]# kubectl get nodes
NAME           STATUS   ROLES                      AGE     VERSION
<IP_ADDRESS>   Ready    controlplane,etcd,worker   4h42m   v1.15.5
<IP_ADDRESS>    Ready    controlplane,etcd,worker   4h42m   v1.15.5
<IP_ADDRESS>   Ready    controlplane,etcd,worker   6m49s   v1.15.5

[root@ip-10-25-55-90 ~]# kubectl logs -l app=ingress-nginx -n ingress-nginx
Trace[2101995302]: [39.392446138s] [39.392446138s] Objects listed
W0108 20:58:39.239597       6 reflector.go:302] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:156: watch of *v1.Service ended with: too old resource version: 7150 (29941)
E0108 20:58:39.326044       6 leaderelection.go:359] Failed to update lock: Operation cannot be fulfilled on configmaps "ingress-controller-leader-nginx": the object has been modified; please apply your changes to the latest version and try again
I0108 20:58:39.326169       6 leaderelection.go:245] successfully acquired lease ingress-nginx/ingress-controller-leader-nginx
E0108 20:59:05.771436       6 reflector.go:283] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:155: Failed to watch *v1.Endpoints: Get https://<IP_ADDRESS>:443/api/v1/endpoints?resourceVersion=29997&timeout=9m45s&timeoutSeconds=585&watch=true: dial tcp <IP_ADDRESS>:443: connect: connection refused
E0108 20:59:05.773413       6 reflector.go:283] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:159: Failed to watch *v1.Pod: Get https://<IP_ADDRESS>:443/api/v1/namespaces/ingress-nginx/pods?labelSelector=app%3Dingress-nginx%2Ccontroller-revision-hash%3D58496446c5%2Cpod-template-generation%3D1&resourceVersion=29941&timeout=5m43s&timeoutSeconds=343&watch=true: dial tcp <IP_ADDRESS>:443: connect: connection refused
E0108 20:59:05.773546       6 reflector.go:283] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:157: Failed to watch *v1.Secret: Get https://<IP_ADDRESS>:443/api/v1/secrets?resourceVersion=29941&timeout=9m4s&timeoutSeconds=544&watch=true: dial tcp <IP_ADDRESS>:443: connect: connection refused
E0108 20:59:05.840584       6 reflector.go:283] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:158: Failed to watch *v1.ConfigMap: Get https://<IP_ADDRESS>:443/api/v1/configmaps?resourceVersion=29993&timeout=9m19s&timeoutSeconds=559&watch=true: dial tcp <IP_ADDRESS>:443: connect: connection refused
E0108 20:59:05.845916       6 reflector.go:283] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:179: Failed to watch *v1beta1.Ingress: Get https://<IP_ADDRESS>:443/apis/networking.k8s.io/v1beta1/ingresses?resourceVersion=29941&timeout=5m4s&timeoutSeconds=304&watch=true: dial tcp <IP_ADDRESS>:443: connect: connection refused
W0108 20:59:05.942360       6 reflector.go:302] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:156: watch of *v1.Service ended with: very short watch: k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:156: Unexpected watch close - watch lasted less than a second and no items received
I0108 20:58:39.228863       6 trace.go:82] Trace[1969699216]: "Reflector k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:156 ListAndWatch" (started: 2020-01-08 20:57:59.875012063 +0000 UTC m=+16376.631257911) (total time: 39.35381324s):
Trace[1969699216]: [39.353791158s] [39.353791158s] Objects listed
W0108 20:58:39.240190       6 reflector.go:302] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:158: watch of *v1.ConfigMap ended with: too old resource version: 29936 (29941)
W0108 20:58:39.240286       6 reflector.go:302] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:155: watch of *v1.Endpoints ended with: too old resource version: 29939 (29941)
E0108 20:59:05.777405       6 reflector.go:283] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:158: Failed to watch *v1.ConfigMap: Get https://<IP_ADDRESS>:443/api/v1/configmaps?resourceVersion=29993&timeout=5m15s&timeoutSeconds=315&watch=true: dial tcp <IP_ADDRESS>:443: connect: connection refused
E0108 20:59:05.778824       6 reflector.go:283] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:155: Failed to watch *v1.Endpoints: Get https://<IP_ADDRESS>:443/api/v1/endpoints?resourceVersion=29997&timeout=9m7s&timeoutSeconds=547&watch=true: dial tcp <IP_ADDRESS>:443: connect: connection refused
E0108 20:59:05.779290       6 reflector.go:283] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:179: Failed to watch *v1beta1.Ingress: Get https://<IP_ADDRESS>:443/apis/networking.k8s.io/v1beta1/ingresses?resourceVersion=29941&timeout=5m39s&timeoutSeconds=339&watch=true: dial tcp <IP_ADDRESS>:443: connect: connection refused
E0108 20:59:05.881460       6 reflector.go:283] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:156: Failed to watch *v1.Service: Get https://<IP_ADDRESS>:443/api/v1/services?resourceVersion=29941&timeout=9m0s&timeoutSeconds=540&watch=true: dial tcp <IP_ADDRESS>:443: connect: connection refused
W0108 20:59:05.942258       6 reflector.go:302] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:157: watch of *v1.Secret ended with: very short watch: k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:157: Unexpected watch close - watch lasted less than a second and no items received
W0108 20:59:05.942307       6 reflector.go:302] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:159: watch of *v1.Pod ended with: very short watch: k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:159: Unexpected watch close - watch lasted less than a second and no items received
I0108 21:00:02.192547       6 nginx.go:274] Starting NGINX Ingress controller
I0108 21:00:02.233884       6 event.go:258] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"ingress-nginx", Name:"udp-services", UID:"010cf349-89e0-4f7f-b6f1-93bfc6a59517", APIVersion:"v1", ResourceVersion:"577", FieldPath:""}): type: 'Normal' reason: 'CREATE' ConfigMap ingress-nginx/udp-services
I0108 21:00:02.233914       6 event.go:258] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"ingress-nginx", Name:"nginx-configuration", UID:"227a6a97-f01c-4042-89e7-cfebf1f88c2a", APIVersion:"v1", ResourceVersion:"575", FieldPath:""}): type: 'Normal' reason: 'CREATE' ConfigMap ingress-nginx/nginx-configuration
I0108 21:00:02.233940       6 event.go:258] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"ingress-nginx", Name:"tcp-services", UID:"e3acad8b-e1f2-4b5a-bd6d-f0d402450d3c", APIVersion:"v1", ResourceVersion:"576", FieldPath:""}): type: 'Normal' reason: 'CREATE' ConfigMap ingress-nginx/tcp-services
I0108 21:00:03.393150       6 nginx.go:318] Starting NGINX process
I0108 21:00:03.393259       6 leaderelection.go:235] attempting to acquire leader lease  ingress-nginx/ingress-controller-leader-nginx...
I0108 21:00:03.395352       6 controller.go:133] Configuration changes detected, backend reload required.
I0108 21:00:03.400099       6 status.go:86] new leader elected: nginx-ingress-controller-g59h6
I0108 21:00:03.463933       6 controller.go:149] Backend successfully reloaded.
I0108 21:00:03.463978       6 controller.go:158] Initial sync, sleeping for 1 second.

[root@ip-10-25-55-90 ~]# kubectl -n kube-system logs -l k8s-app=kube-dns
.:53
2020-01-08T20:59:24.848Z [INFO] CoreDNS-1.3.1
2020-01-08T20:59:24.848Z [INFO] linux/amd64, go1.11.4, 6b56a9c
CoreDNS-1.3.1
linux/amd64, go1.11.4, 6b56a9c
2020-01-08T20:59:24.848Z [INFO] plugin/reload: Running configuration MD5 = 45cd9f91917cc54711e243e0d08537a7

I found the issue, googleapis.com was restricted:
[root@ip-10-25-55-90 ~]# /bin/helm init --home /var/lib/helm --kubeconfig /opt/rancher/kube_config_cluster.yaml --service-account tiller
Creating /var/lib/helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Error: error initializing: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Get https://kubernetes-charts.storage.googleapis.com/index.yaml: read tcp <IP_ADDRESS>:39052-><IP_ADDRESS>:443: read: connection reset by peer


e.destroy is not a function

npx create-docz-app my-docz-app
npx: installed 1 in 2.288s
Creating a new Docz app in D:\coder\component-libray\my-docz-app.
Downloading files for example basic. This might take a moment.
Aborting installation.
Unexpected error. Please report it as a bug:
TypeError: e.destroy is not a function
at C:\Users\admin\AppData\Roaming\npm-cache_npx\2268\node_modules\create-docz-app\dist\index.js:2:35630
at Array.forEach ()
at C:\Users\admin\AppData\Roaming\npm-cache_npx\2268\node_modules\create-docz-app\dist\index.js:2:35573
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async Promise.all (index 0)

I'm having the same response trying to use the react-router example.

So many bugs with docz ecosystem.
fail project list:
npx create-docz-app my-docz-app

fail again:
yarn create docz-app docz-app-typescript --example typescript

I'm having the same issue start as OP when running the command above and also when trying to add docz to an existing project, any updates on this one? on mac BigSur 11.6.1


BetterDiscord

when i got in my discord settings after everything is installed when i got to the better discord settings nor my themes or plugins options is there so i can add plugins or anything its like normal discord

i got that same issue too its just like a normal discord and i cant see my plugins or theme options

BetterDiscord/BetterDiscord#1404

this usually happens when u install canary or ptb. try using stable, it happened to me too


[FEATURE REQUEST] Generic graph structure

Description
The CFG graph structure should be abstracted away, since more components could benefit from the same structure. One example of these are the callgraphs, that could be implemented as a graph backed from an adjacency matrix and that will surely need a fixpoint algorithm.
Motivation
Reducing code duplication and increase encapsulation and modularity.

Commits 6d1a6fc310e53d756c570b5ea344abafd266a1e7 and ad2536f586d2dc4133ce129940bdf7631d3cbf2c are part of this issue.


Don't use root permissions

Hi Sergej,
a properly installed node/npm does not required root permissions. Therefore you should remove sudo from your install example.
bad: sudo npm install ...
good: npm install ...

Tips for fixing npm permissions: https://docs.npmjs.com/getting-started/fixing-npm-permissions

This article is helpful as well: http://blog.michaelarestad.com/2015/08/24/how-to-unfuck-permissions/

Sorry for delay, guys. It's holiday time ;)
You right. Some time ago I had it without sudo too. Then I saw how other packages document the install -g command.
I will remove the [sudo] prefix from the install line and add the two links to the readme to reduce user requests (aka support). Thanks.


Harbor appliance is always setting/preferring "IP address" as hostname in harbor.cfg

Harbor Build: 0.4.5
Steps:

Follow https://github.com/vmware/harbor/blob/master/docs/installation_guide_ova.md  - with DHCP
Boot the Harbor appliance
Identifier of the machine "hostname" in harbor.cfg is always set to IP address. Harbor must prefer Hostname as primary network identifier

logs.tar.gz
config.tar.gz
Otherwise the https certs will have to be generated using IP address as SAN. Ideally Harbor should trust both FQDN and IP address (IP can be specified as SAN) along with FQDN in subject CN
https://github.com/vmware/harbor/blob/master/docs/installation_guide_ova.md to use SSL Cert: & SSL Cert: Key

Fixed by #1058 .


[Support] Wireguard no RX despite packets being sent back from pivpn

In raising this issue, I confirm the following:

[X] I have read and understood the contributors guide.
[X] The issue I am reporting can be replicated.
[] The issue I am reporting can be is directly related to the pivpn installer script.
[X] The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

Issue
After installing and setting up pivpn I tried connecting to it without success. In android app i see TX counter going up but no RX.
I checked tcpdump from pivpn and I see packets coming in and going back to the device. When I do "sudo wg show" i see that RX counter is going up.
Have you searched for similar issues and solutions?
Yes i did search but I couldn't find anything remotely close to my issue.

Console output of      curl -L install.pivpn.io | bash
My issue is not related to the installer.

Console output of      pivpn add or pivpn add nopass
My issue is not related to client creation

Console output of      pivpn debug
::: Generating Debug Output
::::            PiVPN debug              ::::
=============================================
::::            Latest commit            ::::
commit 7fdbe44df5319b7c99a4481c754acd8c0c6c98fa
Author: 4s3ti<EMAIL_ADDRESS>Date:   Tue Jan 26 17:24:10 2021 +0100

    Merge branch 'test'

    Merge test branch into master,
    Check LatestChanges.md for details
=============================================
::::        Installation settings        ::::
PLAT=Raspbian
OSCN=buster
USING_UFW=0
IPv4dev=eth0
dhcpReserv=1
IPv4addr=<IP_ADDRESS>/24
IPv4gw=<IP_ADDRESS>
install_user=pi
install_home=/home/pi
VPN=wireguard
pivpnPORT=51820
pivpnDNS1=<IP_ADDRESS>
pivpnDNS2=
pivpnHOST=REDACTED
INPUT_CHAIN_EDITED=0
FORWARD_CHAIN_EDITED=0
pivpnPROTO=udp
pivpnDEV=wg0
pivpnNET=<IP_ADDRESS>
subnetClass=24
ALLOWED_IPS="<IP_ADDRESS>/0, ::0/0"
UNATTUPG=1
INSTALLED_PACKAGES=(unattended-upgrades)
=============================================
::::  Server configuration shown below   ::::
[Interface]
PrivateKey = server_priv
Address = <IP_ADDRESS>/24
ListenPort = 51820
### begin s20plus ###
[Peer]
PublicKey = s20plus_pub
PresharedKey = s20plus_psk
AllowedIPs = <IP_ADDRESS>/32
### end s20plus ###
=============================================
::::  Client configuration shown below   ::::
[Interface]
PrivateKey = s20plus_priv
Address = <IP_ADDRESS>/24
DNS = <IP_ADDRESS>

[Peer]
PublicKey = server_pub
PresharedKey = s20plus_psk
Endpoint = REDACTED:51820
AllowedIPs = <IP_ADDRESS>/0, ::0/0
=============================================
::::    Recursive list of files in       ::::
::::    /etc/wireguard shown below       ::::
/etc/wireguard:
configs
keys
wg0.conf

/etc/wireguard/configs:
clients.txt
s20plus.conf

/etc/wireguard/keys:
s20plus_priv
s20plus_psk
s20plus_pub
server_priv
server_pub
=============================================
::::            Self check               ::::
:: [OK] IP forwarding is enabled
:: [OK] Iptables MASQUERADE rule set
:: [OK] WireGuard is running
:: [OK] WireGuard is enabled (it will automatically start on reboot)
:: [OK] WireGuard is listening on port 51820/udp
=============================================
:::: Having trouble connecting? Take a look at the FAQ:
:::: https://github.com/pivpn/pivpn/wiki/FAQ
=============================================
:::: WARNING: This script should have automatically masked sensitive       ::::
:::: information, however, still make sure that PrivateKey, PublicKey      ::::
:::: and PresharedKey are masked before reporting an issue. An example key ::::
:::: that you should NOT see in this log looks like this:                  ::::
:::: YIAoJVsdIeyvXfGGDDadHh6AxsMRymZTnnzZoAb9cxRe                          ::::
=============================================
::::            Debug complete           ::::
:::
::: Debug output completed above.
::: Copy saved to /tmp/debug.log
:::

Have you taken any steps towards solving your issue?
  I looked at FAQ but it just said to open an issue when I can see packets coming out from pivpn but no connection

Packet capture outputs
S20+ (my wireguard client)  connecting over LTE to my VPS and VPS connecting over OpenVPN to my home Linux server ( this is my way of port forwarding because I have CGNAT on my home connection as I use LTE )
root@vps711608:~# tcpdump -n -i any "port 51820"
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes
05:58:25.138430 IP <IP_ADDRESS>.10845 > REDACTED.51820: UDP, length 148
05:58:25.138609 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:30.175139 IP <IP_ADDRESS>.10845 > REDACTED.51820: UDP, length 148
05:58:30.175279 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:35.342011 IP <IP_ADDRESS>.10845 > REDACTED.51820: UDP, length 148
05:58:35.342100 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:40.349891 IP <IP_ADDRESS>.10845 > REDACTED.51820: UDP, length 148
05:58:40.349958 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
^C
8 packets captured
8 packets received by filter
0 packets dropped by kernel

My home Linux server connecting over LAN to my pivpn
root@vpn:~# tcpdump -n -i any "port 51820"
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked v1), capture size 262144 bytes
05:58:25.153596 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:25.153663 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:30.187484 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:30.187541 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:35.354009 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:35.354079 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:40.361466 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:40.361542 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:45.360549 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:45.360647 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
^C
10 packets captured
12 packets received by filter
0 packets dropped by kernel

My pivpn receiving tx packet and responding back to them to my s20+ client.
pi@ZeroPi:~ $ sudo tcpdump -n -i any "port 51820"
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes
05:58:25.159762 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:25.177498 IP <IP_ADDRESS>.51820 > <IP_ADDRESS>.10845: UDP, length 92
05:58:30.193664 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:30.210713 IP <IP_ADDRESS>.51820 > <IP_ADDRESS>.10845: UDP, length 92
05:58:35.360190 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:35.377181 IP <IP_ADDRESS>.51820 > <IP_ADDRESS>.10845: UDP, length 92
05:58:40.367811 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:40.384730 IP <IP_ADDRESS>.51820 > <IP_ADDRESS>.10845: UDP, length 92
05:58:45.366932 IP <IP_ADDRESS>.10845 > <IP_ADDRESS>.51820: UDP, length 148
05:58:45.383827 IP <IP_ADDRESS>.51820 > <IP_ADDRESS>.10845: UDP, length 92
^C
10 packets captured
10 packets received by filter
0 packets dropped by kernel

IPtables weren't edited
pi@ZeroPi:~ $ sudo iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
pi@ZeroPi:~ $ sudo iptables -t nat -S
-P PREROUTING ACCEPT
-P INPUT ACCEPT
-P POSTROUTING ACCEPT
-P OUTPUT ACCEPT
-A POSTROUTING -s <IP_ADDRESS>/24 -o eth0 -m comment --comment wireguard-nat-rule -j MASQUERADE

wg show output
pi@ZeroPi:~ $ sudo wg show
interface: wg0
  public key: REDACTED=
  private key: (hidden)
  listening port: 51820

peer: REDACTED=
  preshared key: (hidden)
  endpoint: <IP_ADDRESS>:10845
  allowed ips: <IP_ADDRESS>/32
  transfer: 15.18 KiB received, 9.43 KiB sent

S20+ (my wireguard client) connecting over LTE to my VPS and VPS connecting over OpenVPN to my home Linux server ( this is my way of port forwarding because I have CGNAT on my home connection as I use LTE )

If you have this working setup, you don't need to install PiVPN on your home Pi. Just connect the Samsung phone to the VPS and setup routing and forwarding on both VPS + home Linux server to reach the local network.

That's actually a good idea, probably easier as well. Thank you.
I also checked connecting directly to the Pi IP from my home network and wireguard works so it's entirely my forwarding issue.

when you do "pivpn -d", the output says following.
:: [OK] WireGuard is listening on port 51820/udp
Hence, I changed my router port forwarding to both "tcp/udp" and it works.


I debugged this when starting from zero so you don't have to

Some changes I ended up making to get this project "running on my machine", I figure it might be useful to someone else one day.
Main things include:

README changes of a couple extra needed components that were painful to track down
Some link format shenanigans - not sure how this code is working for GOG without github urls in this format.
Different way of pulling item info from the AE network for item stats. This way does not cause over-memory issues (at least with four sticks of t3.5 memory in a server)
Tweaking the Postgres script to be "create" instead of "alter". Also flip-flopping table create order to help dependencies settle out.

May be worth adding an item regarding the "Max rows" you can request from Supabase (Under Settings, API). When I set this up we were only able to see ~5 hours worth of records for each item and increasing this is currently showing me just over a week

That would be a very good note to add to the README. I had just decided not to debug that little matter.
@nzbasic I see some data retention code that would be useful here. There is duplication with some differences between supabase/functions/index.ts and scr/util/supabase/clean.ts. I'm not sure how supabase functions work, but I can't find anywhere in the repo where the "clean" function is called/consumed/applied, so I assume there is some setup on the supabase project.
Did you end up setting up retention (and if so how), or is that a WIP?

Well done on getting this to work!.. I didn't really expect anyone to attempt it
For cleanup I use pg_cron which calls that clean edge function on a timer
I suppose you could also add it as a route e.g. api/clean and then call it from OC on a timer

Ah wonderful! I seem to need to run it a few times to clean up properly, but that might be due to running it without cleanup for a while and the "Max Rows" I mentioned before coming into play
When I find the time I'll put some instructions together on how I ran that unless one of you gets to it before me

@SarcasticMax I'm simply too fast.
I was working on getting the data retention code running and the Supabase function couldn't handle my millions of rows (accumulated with no old-data-deletion 😬) with CPU limits and that row-fetch limit you mentioned. I also thought that using an edge function for this seemed overcomplicated, so I "fixed" it by implementing the data retention code in SQL instead. That's in supabase/setup_clean_job.sql. It's certainly more performance and doesn't require also setting up a supabase function. I also added some instructions to the README.
Note that if you check out my currently-running app, there's something still goofy with my modified item-grabber script. It's getting the strangely-specific value of 16,272 for all fluids. I'll need to debug that. The script is also causing lovely lag spikes on the server so I'm going to attempt some optimization.

I'm glad to see we both had the same issue with large scale historical data. The SQL file you created did the trick in a fraction (a really small fraction) of the time my solution was heading towards
Are the drops of liquids all reporting under the same name/damage value? The original item scan is running against labels
If you have a liquid in your system that's remained at a steady 16,272 that could be the first match it's pulling instead?

You were right, it's the first fluid. Wet Concrete is such a boring fluid to snap to.
Side note, my server buddy had a thing to say about the existing implementation. Some work required.

@nzbasic what kind of performance does the script get on the gog server? It's wild that it's dragging so much.

Looking at the changes you made, is it to do with the individual searches for every filter, compared to the original of one search and filtering from there?
I'm still using the original OC script on my server and we don't see a performance hit

https://github.com/Hermanoid/GTNH-AE2-OC-GOG/blob/main/oc/main/src/AE2.lua#L61
If you are calling getItemsInNetwork with a filter in a loop over some items, you will get an insane amount of lag. We originally did this due to running out of memory (on a max RAM oc) when calling without a filter. The fix for memory is either increasing the memory sticks in the config file, or getting up to the creative memory stick. You can also clean up the network to remove any trash items or items with excessive NBT
The lag comes from the filter, it has to call a convert() function on every item in your network in order to fetch the metadata for the item so that it can check against the filter. So OC is calling this function for all items in your ae2 multiplied by the number of filtered items


"has underlying svelte-native code changed?" when using radSideDrawer

So I followed the process of importing and registering the RadSideDrawerElement from the svelte-native-nativescript-ui repo, but when I do this, I get "has underlying svelte-native code changed?" errors.
I've tried the following

cleaning and rebuilding
uninstalling and reinstalling the plugin
diving into the HMR plugin to understand what's throwing this error, but I can't see what's causing it
paring back the app to a basic radSideDrawer component with a single label in the MainContent and the Drawer content

I cannot seem to get this to work, am I doing something wrong?

I wasn't able to resolve this in my original code (which was based on svelte-native-template) so I just used the nativescript-ui demo and manually moved existing code across. I suspect I was doing something dumb with navigation, but what or how I do not know


unixPB: Block port 80 on jckservices by default

Fixes an issue flagged by Eclipse as discussed in the recent PMC meetings. This has been implemented on the machine.
Signed-off-by: Stewart X Addison<EMAIL_ADDRESS>
Checklist

[ ] commit message has one of the standard prefixes
[ ] faq.md updated if appropriate
[ ] other documentation is changed or added (if applicable)
[ ] playbook changes run through VPC or QPC (if you have access)
[ ] VPC/QPC not applicable for this PR
[ ] for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

Rebased to fix linter

I don't know what the linter is playing at but it appears to be flagging something unrelated to this PR so I would not block approving and merging this on the basis of this failure:

Error: Unexpected error code 1 from execution of: ansible-playbook --syntax-check -i localhost, ansible/playbooks/nagios/play_setup_server.yml
You can skip specific rules or tags by adding them to your configuration file:
# .config/ansible-lint.yml
warn_list:  # or 'skip_list' to silence them completely
  - internal-error  # Unexpected internal error.

@sxa I ran it with debug on:
##[debug]Evaluating condition for step: 'ansible_lint'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: ansible_lint
##[debug]Loading inputs
##[debug]Loading env
Run # Ansible code static analysis
##[debug]/usr/bin/bash -e /home/runner/work/_temp/d689f02a-51a0-47a2-9eae-b8ac2b883847.sh
WARNING  Ignore loading rule from /opt/hostedtoolcache/Python/3.11.1/x64/lib/python3.11/site-packages/ansiblelint/rules/galaxy.py due to No module named 'pytest'
WARNING  Listing 1 violation(s) that are fatal
internal-error: Unexpected error code 1 from execution of: ansible-playbook --syntax-check -i localhost, ansible/playbooks/nagios/play_setup_server.yml
Warning: laybooks/nagios/play_setup_server.yml:1 [WARNING]: Could not match supplied host pattern, ignoring: Nagios_Server
ERROR! Attempting to decrypt but no vault secrets found
Error: Unexpected error code 1 from execution of: ansible-playbook --syntax-check -i localhost, ansible/playbooks/nagios/play_setup_server.yml
You can skip specific rules or tags by adding them to your configuration file:
.config/ansible-lint.yml
warn_list:  # or 'skip_list' to silence them completely

internal-error  # Unexpected internal error.
      Rule Violation Summary

count tag            profile rule associated tags
1 internal-error min     core
Failed after : 1 failure(s), 0 warning(s) on 466 files.
Error: Process completed with exit code 2.
##[debug]Finishing: ansible_lint

@sxa I ran it with debug on:

Yep I had a chat with @steelhead31 yesterday and it's a known issue that he will be dealing with as he's working on the nagios setup playbooks and therefore independent of this PR.

Latest checks are after rebasing to pick up new linter fixes - all linting has passed :-)

Adding Shelley as extra reviewer purely because she's been in the PMC meetings regarding this :-)


add CRTM v2.4.1 for JEDI/UFO applications

Please describe the package or library you would like to add to spack-stack.
This is a request to add CRTM v2.4.1 from https://github.com/JCSDA/crtm release/crtm_jedi_v2.4.1 branch, which is tagged at
v2.4.1-jedi.   Unless there's a need identified via this PR., the develop branch should not change.   If necessary, I will issue a new tag if the develop branch does change.
An associated binary file tarball is located at:
https://ftp.ssec.wisc.edu/pub/s4/CRTM/file/crtm_coefficients_2.4.1_skylab_4.0.tar.gz
This will be transitioned to UCAR gdex once I've got enough testing / feedback from users.
What applications will be using this package or library?
JCSDA UFO + downstream applications
Is there already a package or library in spack-stack that provides this, or related, functionality?
Prior CRTM packages
Will This Package be Needed in a NOAA Operational Application?
No, this is not recommended.  In fact, it should not be used operationally, since we'll be transitioning all capabilities in v2.4.1 into v3.0.0, and no further development will occur in the v2.x versions of CRTM.
CRTM is public domain code.

We'll need this version in JCSDA public so that it can be installed by people w/o access to JCSDA-internal.

@climbfuji I've now switched CRTM v2.4.1 to public, and updated the top comment accordingly.   No need to do anything with internal for this release (the hashes no longer match up anyway) -- I'll just ask everyone to use public.


NOTIFY change tracking policy fixes

This PR fixes some issues with documents using the NOTIFY change tracking policy, namely:

Committing a document of this kind multiple times raised an Undefined index notice as reported in #740. Fixed the error and created a test case for it.
Committing only a single document made the UnitOfWork lose changes of all other managed documents with NOTIFY change tracking policy. Fixed this too and also created a test case for it.
Additionally I found that the current test case for the this change tracking policy (namely: UnitOfWorkTest::testChangeTrackingNotify) used a document without the required @ODM\ChangeTrackingPolicy("NOTIFY") annotation as its test subject, so the test didn't test what it supposed to test. I added the missing annotation to this dummy document.

@banrobert thank you for PR! Before I get to review could you please take a look at failing test on Travis?

Updated the test case that failed previously, it should work now.

@banrobert cool thanks, could you remove that two commits (434045a8c092b2610e4fb0eec3d9e5ae3507c30a and 0d06d666fdb319c14c6d47a0312c9b23ca678aa7) at all? Once that is done PR's good to be merged.
As for #1149 I'll poke rest of the team for thoughts, FWIW I think it does make sense to implement it.

Removed the commits, never rebased before, didn't know this was possible, cool feature.
And regarding #1149 i would also say that implementing the single document flush differently than the ORM but making it clearer by not flushing anything else that is not related to the document in question is the way to go. Hope the team agrees!

Merged, thank you @banrobert!


visualize testlog

How to directly visualize the following files with nuboard without re-testing, since the tests have already been conducted.
aggregator_metric metrics nuboard_1705383876.nuboard runner_reports simulation summary

Please try using python nuplan/planning/script/run_nuboard.py simulation_path=xxx with your nuboard file.


chore: publish at_auth for at_commons major version

- What I did

changes to publish at_auth
- How I did it
modified pubspec and change log
- How to verify it
tests should pass

functional test failure will be resolved with at_onboarding_cli publish


Change logs to default (not compact) format

This prints all the spans tags next to them in the span list which is more readable.
Before
2022-07-20 16:54:50 DEBUG Send message every interval:xtra_actor_request:xtra_message_handler:Handle SyncAnnouncements:Fetch announcement: daemon::oracle: Fetching announcement event_id=/x/BitMEX/BXBT/2022-07-21T17:00:00.price?n=20 interval_secs=60 actor_type=daemon::oracle::Actor message_type=daemon::oracle::SyncAnnouncements

After
2022-07-20 17:01:48 DEBUG Send message every interval{interval_secs=60}:xtra_actor_request{actor_type=daemon::oracle::Actor message_type=daemon::oracle::SyncAnnouncements}:xtra_message_handler:Handle SyncAnnouncements:Fetch announcement: daemon::oracle: Fetching announcement event_id=/x/BitMEX/BXBT/2022-07-20T19:00:00.price?n=20

bors r+


Issues installing monitoring resources

Describe the bug
Monitoring installation is causing two issues!
The monitoring ansible role is no longer need as the operator installs the monitoring resources. Accordingly the role fails if it is run and therefore should be removed
Also, a hardcoded namespace in one the enmasse Prometheus causes falrse alerts when EnMasse is installed to a different namespace. This need to be fixed

These issues have been fixed in the following PRs
https://github.com/EnMasseProject/enmasse/pull/4222
https://github.com/EnMasseProject/enmasse/pull/4200


General Grievance: Watch (?-i:gamegrid_studio)(?# fiverr)

General Grievance requests the watch of the watch_keyword (?-i:gamegrid_studio)(?# fiverr). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

(?-i:gamegrid_studio)(?# fiverr) has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Add docs for 'ledgerutil verify'

Type of change

Documentation update

Description
This patch adds a command reference for the 'ledgerutil verify' subcommand.
Related issues
The merged PR for the target subcommand: #4018

@Mergifyio backport release-2.5


Example DatePicker overview glitches when using browser zoom functionality

Found: 4.2.0
This was reported on this Ext.NET forum thread: DateField Picker Month & Year Not showing properly
There's a Sencha forum thread complaining of the same thing: Datefield browser zoom out to 90% messes up Month/Year picker
Sencha states browser zooming is not supported by ExtJS at all on that thread, so that's one thing not going to be fixed.
But in the same thread somebody posted a CSS override that fixes this, and this can be applied to our example as well as a sample fix for that.

This is not support for IE 8


Capture build operations for work execution in general

This is a (draft) proposal for build operations to generalize ExecuteTaskBuildOperationType and ExecuteTaskActionBuildOperationType (with the intent of completely replacing later) to cover every type of work in Gradle. Adoption should be incremental, with the new types being adopted for first:

tasks
artifact transforms
worker API actions

From @ldaley:

one thing to keep in mind is that the build scan event stream is not hierarchical. If the hierarchical relationship needs to be preserved to comprehend what is going on, we’ll have to encode that in the build scan events. Unfortunately this isn’t as simple as adding a long getParentUniqueId() in the flattened model, unless that ID is stable across builds. Said another way, the linkages have to be via stable identifiers.


How to use fsdp with having some of the layers weight frozen?

Continuing from #258
When I freeze the weight and bias of output_proj of [ChromaStemConditioner](https://github.com/facebookresearch/audiocraft/blob/main/audiocraft/modules/conditioners.py#L509), and have fsdp.use = true, the error is raised,

ValueError: FlatParameter requires uniform requires_grad

Seems like as default, FSDP needs all the requires_grad values same.
But when constructing FSDP, if use_orig_params=True is passed to the FSDP constructor, then it is possible to have different requires_grad values.
But I found in the original audiocraft/optim/fsdp.py code, use_orig_params=True is already being passed to _FSDPFixStateDict.
Why is it not possible to have only some of the layers' weights frozen, even use_orig_params=True value is passed to the constuctor?

Oh it seems like I must assign requires_grad after wrapping with FSDP. Thanks!


Error with Cythonzing

Hi Evgeni,
I have followed the instructions you have provided, downloaded the library, and run the setup.py. However, I do get this error

Error compiling Cython file:
------------------------------------------------------------
...

        self.children_impurity(&impurity_left, &impurity_right)

        return impurity_right + impurity_left

    cdef double impurity_improvement(self, double impurity) nogil:
        ^
------------------------------------------------------------

hellinger_distance_criterion.pyx:26:9: Signature not compatible with previous declaration

Error compiling Cython file:
------------------------------------------------------------
...
    cdef int update(self, SIZE_t new_pos) nogil except -1
    cdef double node_impurity(self) nogil
    cdef void children_impurity(self, double* impurity_left,
                                double* impurity_right) nogil
    cdef void node_value(self, double* dest) nogil
    cdef double impurity_improvement(self, double impurity_parent,
                                   ^
------------------------------------------------------------

C:\ProgramData\Anaconda3\lib\site-packages\sklearn\tree\_criterion.pxd:65:36: Previous declaration is here
Traceback (most recent call last):
  File "setup.py", line 11, in <module>
    ext_modules=cythonize('hellinger_distance_criterion.pyx', language_level = "3"),
  File "C:\ProgramData\Anaconda3\lib\site-packages\Cython\Build\Dependencies.py", line 1102, in cythonize
    cythonize_one(*args)
  File "C:\ProgramData\Anaconda3\lib\site-packages\Cython\Build\Dependencies.py", line 1225, in cythonize_one
    raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: hellinger_distance_criterion.pyx`````

Could you please let me know how to fix this issue? Also, is there any update about incorporating this split method into Sklearn?

Many thanks in advance for your response.

Regards,
Nader

Hi,
I can see that this particular function's declaration has been changed in
https://github.com/scikit-learn/scikit-learn/commit/22f232efc608e3d90b833c72c9fd3da1b4eacd97
Looks like it is part of the 0.24.1 version. If it is okay, you can try downgrading your sklearn to before 0.24.1. I have used it once, and it worked once upon a time.
Also, we can already use this criterion in sklearn, it is just not defined in the sklearn repository itself. sklearn split criterion, afaik supports external criterion.


policy: Fix attestation load for tag verification

Currently, attestations are loaded assuming the approval target is a Git tree. Entries for tags don't have trees. Separately, we can add support for approval attestations for tags that know not to compute merge trees when approving a tag, instead using the commit ID the tag is expected to point to.
I included this patch in #556 which does add the support for approving a tag using expected commit ID as the to. Testing for this case requires 556 (we need a new version of the reference authorization).
Partially addresses #554 as verification will now work correctly.

How on earth did coverage increase? https://coveralls.io/builds/70111120


typing error

in desktop flow section ( two legacy methods of of creating flows )
have two word of (of )word ..
thanks :)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6870e9fe-dca9-66a8-1cd0-0000b83f385c
Version Independent ID: ca5edb5e-80c3-05ef-b5aa-7c607f5cc706
Content: Overview of the types of flows in Power Automate - Power Automate
Content Source: articles/flow-types.md
Service: power-automate
GitHub Login: @MSFTMan
Microsoft Alias: deonhe

@Anassawalhaa Thanks for reporting the issue. This issue has been resolved and will be pushed live by end of day today. Closing the issue.


Jenkins slave cf cli dockerfile

Install latest version of CF CLI into a jenkins agent container

Merging my own branch ;-)


Workflow Submission Job

This job functions as the "workflow engine" within REANA, responsible for orchestrating all the steps and jobs within a workflow. It serves as the central control point for managing the entire workflow.

Resolved in REANA here


Display help without any precondition.

JIRA: PDC-1630 PDC-1631

Coverage decreased (-7.06%) to 81.627% when pulling 1f11f88d8da0f93303472455de1abc2c38cc846b on PDC-1630-1631_display_help_without_any_precondition into add020d4d7a224c5fe76c8276f55f173859d53cc on master.

looks good for me

:+1:


How to plot a top down map of the room scene

Greetings.
Just wanted to ask if there is any tool in either habitat-lab / habitat-sim or soundspaces repositories that allows to plot a top down or bird's eye view of a map with the actual 3D scene information, like in the papers ?
For example, the following two figures from the SS v1 and SAVi papers, respectively ?

I was also wondering how to recover the information about the "Path with sound" and "Path when silent" for the plots, as in the exceprt below:

Thank you for your time.

Hi @dosssman, the first top-down map was created using meshlab by overlaying the acoustic pressure field on top of the mesh file.
And for the second visualization in SAVi, we used another 3D mesh viewer, which I believe is this one: https://gltf-viewer.donmccurdy.com/.
By "how to recover the information" do you mean how did I plot the trajectory with blue and red according to if these steps are sounding? I think I basically color-coded the trajectory according to whether there is sound in this function: https://github.com/facebookresearch/sound-spaces/blob/3768a5073fb305723676b07cb2a78b62f0d7f6c6/ss_baselines/common/utils.py#L231.

Hello again.
My gratitude for taking the time to check upon this issue.
Duly noted regarding the top down map plotting. I will looking a bit more into the tools you have suggested.
Regarding

[...] how to recover the information about the "Path with sound" and "Path when silent" for the plots, as in the exerpt below:

If my understanding is correct, in SAVI, the sound is only emitted for part of an episode, usually at the beginning, so the agent has to remember it and make association with the category of the object to be able to find it later and solve the task.
I was referring to the ability to plot the path when the sound of the target object is ringing in blue, while the rest  of the path that is silent is plotted in red on the top_down_map.
I have actually used the plot_top_down_map, but it does not seem to contain anything related to sound (silent or not).
Will be looking into it a bit more in the meantime, but would definitely appreciate any further insights in case you recall how it was done for the paper.
Thanks a lot for the help.

@dosssman I think I hard-coded that coloring part but that code might not be in the soundspaces repo. Basically, I passed the variable of the length of the sound from the simulator class to the plotting function and the plot the path with sound with one color and the path without sound with another. This should be pretty straightforward.

@ChanganVR Thanks a lot for the answer.
I was wondering about where one should check whether the current time step is silent or not ?
Thanks again for your time.

@dosssman I simply checked whether the current audio spectrogram/waveforms are all zeros. This is a bit of an artificial scenario because, in the real world, there is never complete silence. But given the assumption of the task, this worked well.

Thanks a lot for the answer.


[Discussion] Should Repository be marked as anti-pattern?

Hi there,
Should repository pattern be marked as anti-pattern?
It seems it behave like a helper or a multi-task manager that is doing too much and responsible for both reading and writing information. Depends on system/platform, such repository classes can require a lot of dependencies because of breaking SRP and it becomes a big deal to instantiate them which is possible performance bottleneck.
As an example of better way of dealing with data, I can suggest adding CQRS pattern and referrer it from repository one.
What's you point of view?
Thanks!

Hi @roma-glushko,
I think that the Repository pattern is no anti-pattern. Instead it is a very important pattern in Domain Driven Design to encapsulate persistence and provide a simple facade to it. Clients of the repository don't care how those requested aggregates are persisted.
It also works very well with CQRS architectures where it supports the Command side of the application in getting and updating domain objects.
I don't think there is a design pattern that violates the Single Responsiblity Principle per se. It all depends on concrete implementation. That being said the SRP is also the single most misunderstood principle of the 5 SOLID principles.

A class should have only one reason to change.

It's about reasons to change. Most of the time the reading and writing of data in the repository happens from the same table(s) stored in a database so there is only one reason to change it: if the database structure changes. And that will cause reading AND writing to change.
For me, the repository is only the facade to persistence. Most of my implementations use a Unit Of Work to persist changes and a Loader of some sort to actually load data from a database. That's 2 dependencies, so 3 classes in total which is not a performance bottleneck.
Adding CQRS is a good idea though 👍


Add a new scoring mode accounting for max historical usage of all tasks

This adds a new strategy for offer scoring that will additionally take into account:

the max historical recorded usage for all active tasks currently on a slave
the system load if it is higher than the predicted maximum
the estimated max usage of tasks about to be added to the host

It also makes the free/used resource weights for long/non-long running tasks configurable in the yaml

🚢


speed up hittesting for mesh

For large areas (even 2x2) -- using the path clipper technique proved to be faster than barycentric coords, and it is 'perfect' in that it is well-defined even when the point in question is on the edge of the triangle. (i.e. there will be no cracks).
For single-point tests, this new API is twice as fast as path clipper, so we expose it if you know you only want to test a single point. This uses a interior-angle-sign test -- crazy fast with no divides
Note: barycentric technique loses out everywhere :)

See related PR: https://github.com/rive-app/rive-recorder/pull/101


The PowerShell session has terminated due to an error / Debug adapter process has terminated unexpectedly

VSCode Version: Code 1.13.1 (379d2efb5539b09112c793d3d9a413017d736f89, 2017-06-14T18:21:47.485Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author
Version

vscode-eslint
dbaeumer
1.2.11

beautify
HookyQR
1.1.1

mssql
ms-mssql
1.0.0

csharp
ms-vscode
1.10.0

PowerShell
ms-vscode
1.4.1

debugger-for-chrome
msjsdiag
3.1.5

code-settings-sync
Shan
2.8.1

Steps to Reproduce:
1.Debugging a set of Powershell scripts, functions call each other; we pass data back and forth.
Not too unique.
2. Using Azure Powershell Cmdlets.  Version 4.0.2

Reading your description it seems that the issue originates from an extension and not VS Code itself. Thereby I will close this issue and kindly ask you to report this issue against the extension repository.
Most extensions are on GitHub as well so it should be easy to file it against the extension. If you open an extension on the market place, click on the Support link to find out more.

Thanks again for your feedback!


[Question] It's slow to trigger win-vind function from Command-line

Because of #111，I try another ways to map functions from insert mode as the link described with Autohotkey.
But functions called from command line have a large delay (approximately 0.5s - 1s instead of instantly) which is inconvenient for daily using such as switch mode.

That's right.
The the interval time of synchronous timer is hard-coded.
https://github.com/pit-ray/win-vind/blob/12ea669c77d62f0b30d677f9de66229d1421287c/src/core/entry.cpp#L113
In this implementation, the main process read the function name periodically in the shared memoris and the sub process write the function name passed by --func.
I would like to improve this behavior in the next version.
If you have any solutions, please let me know.
Thanks.


[Event Request] Codeunit 10752 SII Doc. Upload Management - OnBeforeExecutePendingRequestsPerDocument

We need a new event in Codeunit 10752 "SII Doc. Upload Management" named OnBeforeExecutePendingRequestsPerDocument:
[IntegrationEvent(false, false)]
local procedure OnBeforeExecutePendingRequestsPerDocument(var SIIDocUploadState: Record "SII Doc. Upload State"; var TempSIIHistoryBuffer: Record "SII History" temporary; var XMLDoc: DotNet XmlDocument; var IsInvokeSoapRequest: Boolean; SIISessionId: Integer)
begin
end;
called from:
local procedure ExecutePendingRequestsPerDocument(var SIIDocUploadState: Record "SII Doc. Upload State"; var TempSIIHistoryBuffer: Record "SII History" temporary; var XMLDoc: DotNet XmlDocument; var IsInvokeSoapRequest: Boolean; SIISessionId: Integer)
var
DotNetExceptionHandler: Codeunit "DotNet Exception Handler";
IsSupported: Boolean;
Message: Text;
begin
//INIT INSERT
OnBeforeExecutePendingRequestsPerDocument(SIIDocUploadState, TempSIIHistoryBuffer, XMLDoc, IsInvokeSoapRequest, SIISessionId);
//END INSERT
TempSIIHistoryBuffer.SetRange("Document State Id", SIIDocUploadState.Id);
if TempSIIHistoryBuffer.FindSet then
repeat
......
......
......

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Controller-Actions can only be public, non static functions

fixes #114

Regarding the failing test:
Since the class in the fixture is not a Subclass of AbstractController, the rector should indeed skip this class.
I know that a Controller-Class is not required to inherit from AbstractRector, but this is usually the case. If we don't want to rely on this we can check for the Controller-Suffix in the class-name.
Let me know, what you think!

Since the class in the fixture is not a Subclass of AbstractController, the rector should indeed skip this class.

Agreed :+1:
Please also add test case to cover your original issue.

Please also add test case to cover your original issue.

Since my issue was with a custom rule, I wrote a low-level Test-Case for ControllerMethodAnalyzer, I hope that's OK.

I wrote a low-level Test-Case for ControllerMethodAnalyzer, I hope that's OK.

Oh, I thought this rule is broken.
Okay, but better use service container test and avoid any mocking. It's pain to maintain and does not any value.

Okay, but better use service container test and avoid any mocking. It's pain to maintain and does not any value.

Thanks for the tip. I'll try that tomorrow

Thank you :+1:


UNABLE TO BUILD

The how_to_build_driver_compiler.md contains too many broken link and it builds failed with the error after following the instruction in the markdown file:
In file included from /mnt/disk1/workspace/npu_plugin/src/vpux_utils/src/ov/config.cpp:8:
/mnt/disk1/workspace/npu_plugin/src/vpux_utils/include/vpux/utils/IE/config.hpp:10:10: fatal error: intel_npu/al/config/config.hpp: No such file or directory
   10 | #include "intel_npu/al/config/config.hpp"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

ANY UPDATES?

It is still in progress. Lately my colleagues added new manual in https://github.com/openvinotoolkit/npu_compiler/blob/develop/src/vpux_driver_compiler/README.md


Faros Destination: Only output final state message

Description

Provide description here

Type of change

[ ] Bug fix
[ ] New feature
[ ] Breaking change

Related issues

Fix #1

Migration notes

Describe migration notes if any

Extra info

Add any additional information

lgtm! thanks for confirming. Just one comment left.