Int32Value with Node 12

Hello. I was receiving lots of errors when installing node-opus.
They all seemed to point to wrong amount of arguments to v8::Value::Int32Value.
It might be related to the change https://github.com/nodejs/node/commit/b1e5491ae9
I was running Docker with node:latest (version 12). The solution for me was to change repository to node:11 instead. Now I only get deprecated warnings. It seems that Node 12 isn't compatible with the compiling. I might be wrong...
This happened:
><EMAIL_ADDRESS>install /opt/nodejs/node_modules/node-opus
> node-gyp rebuild

make: Entering directory '/opt/nodejs/node_modules/node-opus/build'
  CC(target) Release/obj.target/libopus/deps/opus/src/opus.o
  CC(target) Release/obj.target/libopus/deps/opus/src/opus_decoder.o
  CC(target) Release/obj.target/libopus/deps/opus/src/opus_encoder.o
  CC(target) Release/obj.target/libopus/deps/opus/src/opus_multistream.o
  CC(target) Release/obj.target/libopus/deps/opus/src/opus_multistream_encoder.o
  CC(target) Release/obj.target/libopus/deps/opus/src/opus_multistream_decoder.o
  CC(target) Release/obj.target/libopus/deps/opus/src/repacketizer.o
  CC(target) Release/obj.target/libopus/deps/opus/src/analysis.o
  CC(target) Release/obj.target/libopus/deps/opus/src/mlp.o
  CC(target) Release/obj.target/libopus/deps/opus/src/mlp_data.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/bands.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/celt.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/celt_encoder.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/celt_decoder.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/cwrs.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/entcode.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/entdec.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/entenc.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/kiss_fft.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/laplace.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/mathops.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/mdct.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/modes.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/pitch.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/celt_lpc.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/quant_bands.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/rate.o
  CC(target) Release/obj.target/libopus/deps/opus/celt/vq.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/CNG.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/code_signs.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/init_decoder.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/decode_core.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/decode_frame.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/decode_parameters.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/decode_indices.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/decode_pulses.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/decoder_set_fs.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/dec_API.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/enc_API.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/encode_indices.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/encode_pulses.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/gain_quant.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/interpolate.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/LP_variable_cutoff.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/NLSF_decode.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/NSQ.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/NSQ_del_dec.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/PLC.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/shell_coder.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/tables_gain.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/tables_LTP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/tables_NLSF_CB_NB_MB.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/tables_NLSF_CB_WB.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/tables_other.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/tables_pitch_lag.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/tables_pulses_per_block.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/VAD.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/control_audio_bandwidth.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/quant_LTP_gains.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/VQ_WMat_EC.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/HP_variable_cutoff.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/NLSF_encode.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/NLSF_VQ.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/NLSF_unpack.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/NLSF_del_dec_quant.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/process_NLSFs.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/stereo_LR_to_MS.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/stereo_MS_to_LR.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/check_control_input.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/control_SNR.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/init_encoder.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/control_codec.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/A2NLSF.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/ana_filt_bank_1.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/biquad_alt.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/bwexpander_32.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/bwexpander.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/debug.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/decode_pitch.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/inner_prod_aligned.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/lin2log.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/log2lin.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/LPC_analysis_filter.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/LPC_inv_pred_gain.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/table_LSF_cos.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/NLSF2A.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/NLSF_stabilize.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/NLSF_VQ_weights_laroia.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/pitch_est_tables.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/resampler.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/resampler_down2_3.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/resampler_down2.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/resampler_private_AR2.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/resampler_private_down_FIR.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/resampler_private_IIR_FIR.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/resampler_private_up2_HQ.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/resampler_rom.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/sigm_Q15.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/sort.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/sum_sqr_shift.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/stereo_decode_pred.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/stereo_encode_pred.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/stereo_find_predictor.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/stereo_quant_pred.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/apply_sine_window_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/corrMatrix_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/encode_frame_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/find_LPC_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/find_LTP_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/find_pitch_lags_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/find_pred_coefs_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/LPC_analysis_filter_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/LTP_analysis_filter_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/LTP_scale_ctrl_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/noise_shape_analysis_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/prefilter_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/process_gains_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/regularize_correlations_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/residual_energy_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/solve_LS_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/warped_autocorrelation_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/wrappers_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/autocorrelation_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/burg_modified_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/bwexpander_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/energy_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/inner_product_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/k2a_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/levinsondurbin_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/LPC_inv_pred_gain_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/pitch_analysis_core_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/scale_copy_vector_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/scale_vector_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/schur_FLP.o
  CC(target) Release/obj.target/libopus/deps/opus/silk/float/sort_FLP.o
  AR(target) Release/obj.target/deps/opus.a
  COPY Release/opus.a
  CXX(target) Release/obj.target/node-opus/src/node-opus.o
In file included from ../src/node-opus.cc:7:0:
../src/node-opus.cc: In static member function 'static void OpusEncoder::Encode(const Nan::FunctionCallbackInfo<v8::Value>&)':
../src/common.h:44:54: error: no matching function for call to 'v8::Value::Int32Value()'
  CHECK_ARG( I, IsNumber(), VAR = info[I]->Int32Value(), VAR = DEFAULT )
                                                      ^
../src/common.h:29:70: note: in definition of macro 'CHECK_ARG'
  if ( info.Length() <= (I) || !info[I]->CHECK ) { DO_FALSE; } else { DO_TRUE; }
                                                                      ^~~~~~~
../src/node-opus.cc:100:4: note: in expansion of macro 'OPT_INT_ARG'
    OPT_INT_ARG( 1, maxPacketSize, MAX_PACKET_SIZE );
    ^~~~~~~~~~~
In file included from ../src/node-opus.cc:2:0:
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note: candidate: v8::Maybe<int> v8::Value::Int32Value(v8::Local<v8::Context>) const
   V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const;
                                        ^~~~~~~~~~
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note:   candidate expects 1 argument, 0 provided
In file included from ../src/node-opus.cc:7:0:
../src/node-opus.cc: In static member function 'static void OpusEncoder::ApplyEncoderCTL(const Nan::FunctionCallbackInfo<v8::Value>&)':
../src/common.h:40:32: error: no matching function for call to 'v8::Value::Int32Value()'
  int VAR = info[I]->Int32Value()
                                ^
../src/node-opus.cc:151:4: note: in expansion of macro 'REQ_INT_ARG'
    REQ_INT_ARG( 0, ctl );
    ^~~~~~~~~~~
In file included from ../src/node-opus.cc:2:0:
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note: candidate: v8::Maybe<int> v8::Value::Int32Value(v8::Local<v8::Context>) const
   V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const;
                                        ^~~~~~~~~~
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note:   candidate expects 1 argument, 0 provided
In file included from ../src/node-opus.cc:7:0:
../src/common.h:40:32: error: no matching function for call to 'v8::Value::Int32Value()'
  int VAR = info[I]->Int32Value()
                                ^
../src/node-opus.cc:152:4: note: in expansion of macro 'REQ_INT_ARG'
    REQ_INT_ARG( 1, value );
    ^~~~~~~~~~~
In file included from ../src/node-opus.cc:2:0:
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note: candidate: v8::Maybe<int> v8::Value::Int32Value(v8::Local<v8::Context>) const
   V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const;
                                        ^~~~~~~~~~
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note:   candidate expects 1 argument, 0 provided
In file included from ../src/node-opus.cc:7:0:
../src/node-opus.cc: In static member function 'static void OpusEncoder::ApplyDecoderCTL(const Nan::FunctionCallbackInfo<v8::Value>&)':
../src/common.h:40:32: error: no matching function for call to 'v8::Value::Int32Value()'
  int VAR = info[I]->Int32Value()
                                ^
../src/node-opus.cc:166:4: note: in expansion of macro 'REQ_INT_ARG'
    REQ_INT_ARG( 0, ctl );
    ^~~~~~~~~~~
In file included from ../src/node-opus.cc:2:0:
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note: candidate: v8::Maybe<int> v8::Value::Int32Value(v8::Local<v8::Context>) const
   V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const;
                                        ^~~~~~~~~~
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note:   candidate expects 1 argument, 0 provided
In file included from ../src/node-opus.cc:7:0:
../src/common.h:40:32: error: no matching function for call to 'v8::Value::Int32Value()'
  int VAR = info[I]->Int32Value()
                                ^
../src/node-opus.cc:167:4: note: in expansion of macro 'REQ_INT_ARG'
    REQ_INT_ARG( 1, value );
    ^~~~~~~~~~~
In file included from ../src/node-opus.cc:2:0:
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note: candidate: v8::Maybe<int> v8::Value::Int32Value(v8::Local<v8::Context>) const
   V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const;
                                        ^~~~~~~~~~
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note:   candidate expects 1 argument, 0 provided
In file included from ../src/node-opus.cc:7:0:
../src/node-opus.cc: In static member function 'static void OpusEncoder::SetBitrate(const Nan::FunctionCallbackInfo<v8::Value>&)':
../src/common.h:40:32: error: no matching function for call to 'v8::Value::Int32Value()'
  int VAR = info[I]->Int32Value()
                                ^
../src/node-opus.cc:181:4: note: in expansion of macro 'REQ_INT_ARG'
    REQ_INT_ARG( 0, bitrate );
    ^~~~~~~~~~~
In file included from ../src/node-opus.cc:2:0:
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note: candidate: v8::Maybe<int> v8::Value::Int32Value(v8::Local<v8::Context>) const
   V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const;
                                        ^~~~~~~~~~
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note:   candidate expects 1 argument, 0 provided
In file included from ../src/node-opus.cc:7:0:
../src/node-opus.cc: In static member function 'static void OpusEncoder::New(const Nan::FunctionCallbackInfo<v8::Value>&)':
../src/common.h:44:54: error: no matching function for call to 'v8::Value::Int32Value()'
  CHECK_ARG( I, IsNumber(), VAR = info[I]->Int32Value(), VAR = DEFAULT )
                                                      ^
../src/common.h:29:70: note: in definition of macro 'CHECK_ARG'
  if ( info.Length() <= (I) || !info[I]->CHECK ) { DO_FALSE; } else { DO_TRUE; }
                                                                      ^~~~~~~
../src/node-opus.cc:213:4: note: in expansion of macro 'OPT_INT_ARG'
    OPT_INT_ARG( 0, rate, 48000 );
    ^~~~~~~~~~~
In file included from ../src/node-opus.cc:2:0:
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note: candidate: v8::Maybe<int> v8::Value::Int32Value(v8::Local<v8::Context>) const
   V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const;
                                        ^~~~~~~~~~
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note:   candidate expects 1 argument, 0 provided
In file included from ../src/node-opus.cc:7:0:
../src/common.h:44:54: error: no matching function for call to 'v8::Value::Int32Value()'
  CHECK_ARG( I, IsNumber(), VAR = info[I]->Int32Value(), VAR = DEFAULT )
                                                      ^
../src/common.h:29:70: note: in definition of macro 'CHECK_ARG'
  if ( info.Length() <= (I) || !info[I]->CHECK ) { DO_FALSE; } else { DO_TRUE; }
                                                                      ^~~~~~~
../src/node-opus.cc:214:4: note: in expansion of macro 'OPT_INT_ARG'
    OPT_INT_ARG( 1, channels, 1 );
    ^~~~~~~~~~~
In file included from ../src/node-opus.cc:2:0:
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note: candidate: v8::Maybe<int> v8::Value::Int32Value(v8::Local<v8::Context>) const
   V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const;
                                        ^~~~~~~~~~
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note:   candidate expects 1 argument, 0 provided
In file included from ../src/node-opus.cc:7:0:
../src/common.h:44:54: error: no matching function for call to 'v8::Value::Int32Value()'
  CHECK_ARG( I, IsNumber(), VAR = info[I]->Int32Value(), VAR = DEFAULT )
                                                      ^
../src/common.h:29:70: note: in definition of macro 'CHECK_ARG'
  if ( info.Length() <= (I) || !info[I]->CHECK ) { DO_FALSE; } else { DO_TRUE; }
                                                                      ^~~~~~~
../src/node-opus.cc:215:4: note: in expansion of macro 'OPT_INT_ARG'
    OPT_INT_ARG( 2, application, OPUS_APPLICATION_AUDIO );
    ^~~~~~~~~~~
In file included from ../src/node-opus.cc:2:0:
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note: candidate: v8::Maybe<int> v8::Value::Int32Value(v8::Local<v8::Context>) const
   V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const;
                                        ^~~~~~~~~~
/root/.node-gyp/12.1.0/include/node/v8.h:2569:40: note:   candidate expects 1 argument, 0 provided
../src/node-opus.cc: In static member function 'static void OpusEncoder::Init(v8::Local<v8::Object>)':
../src/node-opus.cc:239:77: error: no matching function for call to 'v8::FunctionTemplate::GetFunction()'
    exports->Set( Nan::New("OpusEncoder").ToLocalChecked(), tpl->GetFunction() );
                                                                             ^
In file included from ../src/node-opus.cc:2:0:
/root/.node-gyp/12.1.0/include/node/v8.h:5947:46: note: candidate: v8::MaybeLocal<v8::Function> v8::FunctionTemplate::GetFunction(v8::Local<v8::Context>)
   V8_WARN_UNUSED_RESULT MaybeLocal<Function> GetFunction(
                                              ^~~~~~~~~~~
/root/.node-gyp/12.1.0/include/node/v8.h:5947:46: note:   candidate expects 1 argument, 0 provided
make: *** [Release/obj.target/node-opus/src/node-opus.o] Error 1
node-opus.target.mk:156: recipe for target 'Release/obj.target/node-opus/src/node-opus.o' failed
make: Leaving directory '/opt/nodejs/node_modules/node-opus/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:196:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:256:12)
gyp ERR! System Linux 4.9.125-linuxkit
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/nodejs/node_modules/node-opus
gyp ERR! node -v v12.1.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Yeah; This is a known issue. A V8 update broke the API (again) and I hadn't gotten around to fixing it.
Fixed now in v0.3.2


Fix all eslint errors

Pull Request Description
Fixes all eslint errors - now npx eslint . in app/ide-desktop should show no errors and no warnings.
Also fixes an incorrect lint rule (the rule to catch early returns (?) did not work properly for try-catch)
Important Notes
This changes quite a few files (unfortunately) so QA should be done to check all affected files
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

QA 🟢


Any plans to upgrade to the latest versions of titan and tinkerpop?

I saw this old branch was around and wondered if there were plans to update this library to the latest versions of the tinkerpop and titan?

Datastax gave Titan to the community, and JanusGraph picked up in its place. I am on the JanusGraph TSC now, and we are working on getting a release out as our highest priority. As soon as JanusGraph get a release out and have artifacts in Maven I can build against, it would be possible to build this plugin against a much more recent version of TinkerPop.

Experimental support can be found in my fork here

I will be merging this PR that adds support: https://github.com/awslabs/dynamodb-titan-storage-backend/pull/107 . Closing


Use of Undefined variable: Uncaught TypeError

Under Implementing Message Sending, this error is returned: "Uncaught TypeError: Cannot read property 'push' of undefined at FriendlyChat.saveMessage"
The issue is the use of: this.messagesRef.push INSTEAD OF this.messageRef.push
Best regard

It looks to me that this.messagesRef is used throughout (in the code and in the codelab instructions). Maybe we fixed it since you filed this bug but if you still see these please re-open and point me to where these issues are.


Istio Ingress Gateway is healthy in case of "certificate signed by unknown authority" error

Bug Description
Hello!
We're using custom, issued by our own CA, certificates in Istio.
During the last certificates changing one of our istio-ingress-gateway pods wasn't restarted (it must be done for the correct work) due to human error. It led to the error messages in log:
{"level":"error","time":"2021-12-13T13:24:04.890986Z","scope":"xdsproxy","msg":"failed to create upstream grpc client: rpc error: code = Unavailable desc = connection error: desc = \"transport: authentication handshake failed: x509: certificate signed by unknown authority\""}
It's ok and I know how to fix it - just do a restart of this pod and it's all. But I noticed one interesting moment, the readiness probe of this pod is healthy.
To my mind, it's not correct behaviour, cause in fact pod can't produce customer's traffic.
  readinessProbe:
    failureThreshold: 30
    httpGet:
      path: /healthz/ready
      port: 15021
      scheme: HTTP
     initialDelaySeconds: 10
     periodSeconds: 2
     successThreshold: 1
     timeoutSeconds: 1

As a workaround, I wanted to create an alert about such behaviour of istio-ingress-gateway pod, but I didn't find any istio metrics which can describe that pod isn't healthy due to "a certificate signed by unknown authority" error.
If I missed smth, could somebody point me out to the right metric?
Version
istioctl version
client version: 1.8.2
control plane version: 1.8.2
data plane version: 1.8.2 (13 proxies)

kubectl version --short
Client Version: v1.16.1
Server Version: v1.16.9

Additional Information
No response

@qurname2 Does istioctl proxy-status show everything as SYNCED for the ingress gateway in this failed state? Or do any secrets show as WARMING for istioctl proxy-config secrets <ingress_pod_name> -n istio-system

I guess what would help here is a metric reported by agent on whether xds connection is up, which you can alert on if there is any unconnected proxy?

@GregHanson the affected ingress gateway doesn't show in istioctl ps output, it's not SYNCED

@bianpengyuan, yes, exactly, it will help a lot in such a case.
As a workaround, I wanted to create an alert about such behaviour of istio-ingress-gateway pod, but I didn't find any istio metrics which can describe that pod isn't healthy due to "a certificate signed by unknown authority" error.

@bianpengyuan @howardjohn Hi, Guys! Do you have a plan to do smth with this issue?

seems  same issue as https://github.com/istio/istio/issues/36723

@bianpengyuan @howardjohn Hi, Guys!  Will get to this.

@bianpengyuan @howardjohn Hi, Guys!  Will get to this.

we had an similar issues as https://github.com/istio/istio/issues/36723, when will you do this? anything I can help?

we had an similar issues as #36723, when will you do this? anything I can help?

Oh I just plan to add the metric to track xds connection, which can be alerted on.

yes, there's step one of my plan, and I'think about add a mechanism which allow pilot-agent reload the root certs.

Ok feel free to take over the work. @zirain thanks a lot!

with https://github.com/istio/istio/pull/36764, you can add a alert to monitor this.
k exec -it httpbin-74fb669cc6-2x7gc -cistio-proxy -- curl <IP_ADDRESS>:15020/stats/prometheus | grep istiod
# HELP istio_agent_istiod_connection_terminations The total number of connection errors to Istiod
# TYPE istio_agent_istiod_connection_terminations counter
istio_agent_istiod_connection_terminations{type="cancelled"} 1
istio_agent_istiod_connection_terminations{type="error"} 10

Form a long-term point of view, let pilot-agent reload the root certs seems good, but that will take a bit long time to implement.


Postgre with enforced SSL

No support available for Postgre with enforced SSL activity. Documentation also doesnt talks about it, wish if this can be updated with same.

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

ID: 79c3f263-04ba-ea60-1927-c2fedde96d61
Version Independent ID: fe35a13a-a960-9a50-1b89-aa79abe514b9
Content: Copy data from Azure Database for PostgreSQL using Azure Data Factory
Content Source: articles/data-factory/connector-azure-database-for-postgresql.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@Gaurav8032 Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Hi @Gaurav8032 which connector are you talking about? PostgreSql or Azure PostgreSql?
For PostgreSql, currently we do not expose the SSL settings but we are going to change the behavior recently.
For Azure PostgreSql, it can support SSL settings in a connection string (https://docs.microsoft.com/en-us/azure/data-factory/connector-azure-database-for-postgresql).
To enable SSL, you can put a connection string like this in Advanced tab:
Server=;Database=;Port=;UID=;Password=;EncryptionMethod=<0/1/6>;ValidateServerCertificate=<0/1>.

Property Name
Description
Options

EncryptionMethod (EM)
The method the driver uses to encrypt data sent between   the driver and the database server.
0 (No Encryption) / 1 (SSL) / 6 (RequestSSL)

ValidateServerCertificate (VSC)
Determines whether the driver validates the certificate   that is sent by the database server when SSL encryption is enabled   (Encryption Method=1).
0 (Disabled) / 1 (Enabled)

This issue is for Azure Postgres SQL. We tried using SSL=True and Required (Require) mode also but Linked Service JSON doesnt accepts it and throws error saying that - Error 8S01 SSL property required. This is happening because Azure Postgres SQL has SSL enabled and ADF is not able to talk to it while this property is switched on. Can you test same case ?

Hi @Gaurav8032 please see comment above. The correct property name is EncryptionMethod or EM. Its default value is 0, which means No Encryption. You can set it to 1 or 6 and try again

Doc has been updated to describe the SSL related properties. Those options are now available on ADF authoring UI as well.
#please-close

@Gaurav8032 We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


IBM Milestone 2: RAS Manual / Automation

This is also done. Both Manual and automation wherever required.


Implement calibration save and load

This PR implements saving and loading of calibration data to disk.

Hi @apsun, I've made some changes to the PR. Please recheck when you have time :)


[Quickdraw] I am here to learn how to open and close issues on Github! 🤠

I am here to learn how to open and close issues on Github! 🤠
I will close it in 10 seconds 🤞

I am here to learn how to open and close issues on GitHub! 🤠


Event Handler Issue after upgrade WinRT

I have tried sample program for RadioButton checked event handler , previous version  is working fine below code
RadioButton RButton;
RButton.Checked({ this,&App::RdButtonClick });
void RdButtonClick(IInspectable const& sender, RoutedEventArgs const& args)
{
}
After upgrade a new WinRT version is not working , its throw an compile time error
Error
Severity	Code	Description	Project	File	Line	Suppression State
Error	LNK2019	unresolved external symbol "public: struct winrt::event_token __thiscall winrt::impl::consume_Windows_UI_Xaml_Controls_Primitives_IToggleButton::Checked(struct winrt::Windows::UI::Xaml::RoutedEventHandler const &)const " (?Checked@?$consume_Windows_UI_Xaml_Controls_Primitives_IToggleButton@URadioButton@Controls@Xaml@UI@Windows@winrt@@@impl@winrt@@QBE?AUevent_token@3@ABURoutedEventHandler@Xaml@UI@Windows@3@@Z) referenced in function
Please let me know , how to fix this
Thanks
Vinoth.

Vinoth, you can fix this by adding:
#include "winrt/Windows.UI.Xaml.Controls.Primitives.h"
Generally, when you see a link error for an unresolved C++/WinRT artifact, you can fix it by #including the namespace header for that artifact.  In a future release, we hope to distribute C++/WinRT in module form as well, which will eliminate these kinds of errors.

Thanks Scott , Its working fine

@Scottj1s , Using ListBox -> SelectionChanged event it throw an compile time error
lstBox.SelectionChanged({ this, &App::lstBoxSelectionChange });
Severity	Code	Description	Project	File	Line	Suppression State
Error	C2280	'void *winrt::Windows::Foundation::IUnknown::operator new(::size_t)': attempting to reference a deleted function	CreateCpp	C:\CPPWinRT\winrt\base.h	3360
Please let me know , how to fix it
Thanks.
Vinoth.

The error seems to be unrelated to the code snippet you provided. Can you provide a standalone repro? Hint: you should never use "new" to create a C++/WinRT type. For example, the following code:
new ListBox;

Will produce the following compiler error:
error C2280: 'void *winrt::Windows::Foundation::IUnknown::operator new(::size_t)': attempting to reference a deleted function

This is intentional. Simply create the ListBox on the stack:
ListBox box;

@kennykerr  yes , am not using new keyword
please find the sample in the here https://github.com/rvinothrajendran/CPP-WinRT-Samples/tree/master/ListBox/CreateCpp
thanks.
Vinoth.

That's a misleading compiler error. I haven't looked into why that is, but your event handler's second parameter should be SelectionChangedEventArgs rather than SelectionChangedEventHandler. Change that and it should compile.

Vinoth, your event handler has a typo (wrong event args type) - it should be:
void lstBoxSelectionChange(IInspectable const& sender, SelectionChangedEventArgs const & args)

Thanks @kennykerr and @Scottj1s , its working fine.


Authorization

Can you design for authorization with api request on server ?

Yes, sure we will make a design for api requests with authorization. Thank you for feedback.


Add Initialise readonly auto property from constructor parameter

I also did a little refctoring to share some code that hopefully isn't too controversial.
I'm afraid I didn't check if this is an up for grabs issues, but I value immutability and found myself wanting this functionality so added it.
I'm also not sure what the Visual Studio Default Coding style is (there's no link), but the output is the same as the existing refactorings so I think its ok.
Cheers
Cedd

I've fixed up compilation of the 2017 project, but it looks like the tests have been failing for some time, so I've left those.

Thank you for your contribution!


update tutorial

@yeasy I found the reason for build failure is that binary is unable to download, this url seems to be outdated. Do you know where can we download binary files (fabric-bin) now?

@yeasy I found the reason for build failure is that binary is unable to download, this url seems to be outdated. Do you know where can we download binary files (fabric-bin) now?

ok, I found we can download from fabric releases: https://github.com/hyperledger/fabric/releases/


Fuzzy search with multi-word

and booleans

Also find a way to display fuzzy option in CSS search form

Not working with complex queries, so disabled
Not implemented on homepage but working on results page


Merge Sort [C#]

This issue is about Merge Sort.

[x] Issue Title is in form Algo/DS Name [Language].
[x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
[x] This Algo/DS is worth adding to this repository.
[x] Assign this issue to me (I want to work on this).

[x] I ensure that I am not already assigned to 2 or more issues.

[x] I will send my PR only after I'm assigned to this issue by any maintainer.
[x] I understand that I will be unassigned from this issue if I fail to send a PR for this within a week.

Assign this issue to me (I want to work on this).

@AkshGautam, @DimaMukhin is already assigned to this one, explore other issues on the repository.

Add me for solving this issue

@bunyy  Sorry but this issue is already assigned to @DimaMukhin  please go through other issues in the repo. You will surely find more.


WIP: Add TBH Content Compendia

Adds the classes, spells, equipment, etc. as compendia.
TODO

[ ] Add roll tables for OofA and NPC reactions
[x] Fix arcane-spells.db IDs.

@free-beer Yikes, yeah that's a good point.  I got a little out over my skies 😬 .  I'm happy to delete this public branch while we figure that stuff out.

FYI: Looks like I'm not able to outright delete this PR but I did remove the branch on my fork.

@free-beer @woodzer
Got yah your access. lets see black hack in the list! 🤘🏻

Ta, will look into that as soon as I can.

@free-beer Howdy!  Just wanted to check in with you on this one.  Is there anything I can do to help get this merged?

Apologies, had much on that meant this got completely forgotten about. I can merge this but then I will have to do a release to make it actually available in Foundry.

Okay @atomdmac , I think I've correctly pushed out version 0.6.0 which should include your content.


vsInput.featureIds.featureId_0 throw a compile log

fsInput.featureIds.featureId_0 in fragmentShaderText can compile success,but when i add int value = vsInput.featureIds.featureId_0; in vertexShaderText , it throw a error

i write shader like document saying

https://sandcastle.cesium.com/?src=3D Tiles Next Photogrammetry Classification.html&label=3D Tiles Next
this problem can show in this example


[Communication Services - Cross platform messaging] REST API Review Meeting

This meeting was created by Jorge Garcia Hirota.

It will be used to Track the conversation in the informational Session for the Azure Communication Services Service.

Detailed meeting information and documents provided can be accessed here

Service name: Cross-platform Messaging
Link to previous API version:
Previously the endpoint ("/chat/messages:send") was part of the chat gateway: https://github.com/Azure/azure-rest-api-specs/blob/9b43f4a756a79e05b3bb1dc6bd3ed7a8fd132969/specification/communication/data-plane/Chat/preview/2022-04-21-preview8/communicationserviceschat.json, now we are moving that messaging endpoint to the Cross-platform messaging service
Description of the material to be reviewed/changed: Add a new messaging endpoint to allow Contoso to send fire and forget/ notification messages to external messaging platforms (e.g. WhatsApp).
Latest Arch diagram: https://skype.visualstudio.com/SPOOL/_wiki/wikis/SPOOL.wiki/23345/📡-Cross-Platform-Messaging?anchor=[notification-messages---alerts---threadless-messages](/spool/teams/📡-cross-platform-messaging/🔬9.-design-docs-and-specs/🏛-architecture/notification-messages-%252d-fire-and-forget-%252d-alerts)
Link to swagger: https://github.com/Azure/azure-rest-api-specs/blob/gelli/addMessagingApiSpec/specification/communication/data-plane/Messaging/preview/2022-06-30-preview/communicationservicesmessaging.json
PR for the swagger: https://github.com/Azure/azure-rest-api-specs/pull/20436
Champion scenarios that briefly explain how developers will use your API:
Endpoint: https://{your_acs_resource}.communication.azure.com/messaging/notifications/:send?api-version=2022-06-30-preview
Authorization header:
key: Authorization
value: "HMAC-SHA256 SignedHeaders=date;host;x-ms-content-sha256&Signature=" + signature
Request Body:
to send a text message
{
"channelRegistrationId":"d8fbaac7-c949-4bf1-8ba9-29b467d97547",
"to": ["+1(604)xxx-xxxx"],
"type":"text",
"content":"hiiii"
}
to send a media message
{
"channelRegistrationId":"d8fbaac7-c949-4bf1-8ba9-29b467d97547",
"to": ["+1(604)xxx-xxxx"],
"type":"image",
"mediaUri":"http://image.com"
}
to send a template message
{
"channelRegistrationId":"d8fbaac7-c949-4bf1-8ba9-29b467d97547",
"to": ["+1(604)xxx-xxxx"],
"type":"template",
"template":{
"name":"appiontment_reminder",
"language":"en",
"parameters":["friday", "10am"]
}
}

The response of the 202 for sendMessage is non-standard.  Need to understand this.
Is there a race condition between sendMessage response and event grid event being delivered?  Maybe
We recommend paths for post-actions use ":" and not "/:" -- but it looks like "/:" is already established for this service.
"result" vs "value" ? No strong preference.
Might need to switch from array to object to avoid the need to maintain input order.
Repeatability / idempotency? This will be addressed in the next version of the API
Input as an array of values vs a map of key-value pairs? Will leave as an array for private preview.

Now tracked in #22137


docs: Updating testnet reset from 9am UTC to 5pm UTC

Updating the testnet reset timing from 9am(09:00) UTC to 5pm(17:00) UTC

Preview is available here:http://developers-pr273.previews.kube001.services.stellar-ops.com


CLI is very very slow

Hi all! I'm trying out kpt and I have to say I'm really excited about the solutions it presents to the hard problem of configuration management. Congrats on all the great work!
The only problem is that the CLI is giving me a hard time. I'm seeing unreasonably long run times for simple commands.
I tried installing both from source (go get) and from ready-built packages.
To give an example of what I'm seeing:
$ time kpt pkg diff helloworld
kpt pkg diff helloworld  5.17s user 1.70s system 14% cpu 47.171 total

$ time kpt pkg desc helloworld
   PACKAGE NAME        DIR                         REMOTE                                REMOTE PATH              REMOTE REF   REMOTE COMMIT

  hello-world-set   helloworld   https://github.com/GoogleContainerTools/kpt   /package-examples/helloworld-set   v0.5.0       3f173ad

kpt pkg desc helloworld  0.68s user 0.07s system 2% cpu 30.722 total

These times seem unreasonably long, especially since it doesn't really seem to do anything for most of the time (network and cpu activity seems normal).
Is this something you are seeing as well, or just something that happens on my machine?
What is it doing that makes it run so slow?
Here are some details about my OS:
NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.4 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

@yanniszark Thanks for reporting this. So kpt will try to fetch the openapi schema from the kubernetes cluster defined in your current context on every invocation. There is some more information about it at https://googlecontainertools.github.io/kpt/reference/#openapi-schema.
This might be the reason you experience the kpt commands as being slow. Can you try to run the commands with the --k8s-schema-source=builtin flag and see if it changes anything? This flag will force kpt to use the openapi schema compiled into the binary rather than fetching it from the cluster. The disadvantage is that the schema might not match your version of Kubernetes and will not include information about any CRDs you might be using.

@yanniszark closing this issue. Feel free to reopen if the suggested fix didn't work.


java.lang.IllegalArgumentException Tcp Sockets: No socket with id

Description
Sometimes when the connection gets interrupted while writing data the app will crash with "No socket with id" error. I suspect that this might be due to the write method not catching the errors that is thrown by getTcpClient method.
Steps to reproduce
Steps to reproduce the behavior:

Write on the socket while it simultaneously gets disconnected.

Current behavior
App crashes with error
Expected behavior
Connection can close but app should not crash.
Relevant information

OS
no

react-native
yes

react-native-tcp-socket
yes

@pajkho, this is a common issue if you are trying to use the socket while it has not established a connection yet. Make sure you wait for the connection callback before using the socket.

The issue arises for us when having continuous writes to the tcp connection which doesn't stop until the end event happens. If the connection closes there can be a gap between the close of the connection and the end event where there is new writes which causes this error and the app crashes.
Wouldn't it be more reasonable to try/catch this to prevent the app from crashing and instead call the error event? It shouldn't be possible to crash the app because you mistakenly try to write to a closed connection.

@pajkho, indeed, I will release a fix ASAP.

Hello, this fix is missing in version 6.1.0 socketMap.remove(cId);
https://github.com/Rapsssito/react-native-tcp-socket/blob/418351231efea642385e7bc01ff30eb53e0a6e67/android/src/main/java/com/asterinet/react/tcpsocket/TcpSocketModule.java#L137

Woops. My bad. I will fix it ASAP.

@yang-Ann, this fix is included in the latest version. The solution was to remove socketMap.remove(cId);.

Thank you very much
------------------ 原始邮件 ------------------
发件人: "Rodrigo @.>;
发送时间: 2024年7月9日(星期二) 下午5:37
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [Rapsssito/react-native-tcp-socket] java.lang.IllegalArgumentException Tcp Sockets: No socket with id (Issue #167)
@yang-Ann, this fix is included in the latest version. The solution was to remove socketMap.remove(cId);.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


added ignore hook functionality

Let's split to 2 PRS

insert attach_hooks into the ledger without added functionality
ignore functionality

I thought you wanted to ignore original function for example ignore('concat'). The user will not know the names of the hooks.
Also, code will be much simpler.

Blocked until https://github.com/DeanLa/dovpanda/pull/24 will be merged


PeerJ R3C7

although it is early days, is there any preliminary information on citation patterns for the articles? there is a hint only in "we may need to invest more effort into raising awareness of good practices for citing JOSS articles"

We have a few of sources for data on this:

Crossref's own 'cited by' data that relies upon publishers depositing metadata: https://data.crossref.org/depositorreport?pubid=J299881
Google Scholar: https://scholar.google.com/scholar?start=20&q=10.21105&hl=en&as_sdt=0,21
ADS for citations in the astronomical literature: https://ui.adsabs.harvard.edu/#search/q=bibstem%3AJOSS&sort=date desc%2C bibcode desc

Looking at https://data.crossref.org/depositorreport?pubid=J299881, it seems like a small number of papers (~3) are picking up a decent number of citations the others, the odd one or two. It seems like we could be doing better.
One of the most cited papers is very clear in their README about how to cite. This presumably helps...?

I propose adding a few sentences on preliminary citation statistics:

That said, we have some preliminary citation statistics: according to Google Scholar, \texttt{corner.py}~\cite{cornerpy} and \texttt{Armadillo}~\cite{armadillo} have been cited the most at 116 and 79 times, respectively. Crossref's Cited-by service---which relies on publishers depositing reference information---reports 45 and 28 citations for the same articles~\cite{crossref-cited-by}. Most other articles have received no citations yet, though some have been cited five times or fewer.

I also added a response explaining this.

👍 I think this is sufficient.

maybe change the last sentence to:

While most other articles have received no citations to-date, a few have been cited between one of five times.


Implement Automated Logic to Identify and take advantage of Deep Double Descent Phenomenon

Implement Automated Logic to Identify and Mitigate Deep Double Descent Phenomenon
Feature Request
Summary:
I propose the addition of an automated mechanism within the framework that detects the occurrence of the deep double descent phenomenon and accordingly adjusts model complexity and training strategies, such as disabling early stopping when beneficial.
Motivation:
In my recent project aiming to predict river temperatures using historical covariate data, I observed that none of my approximately 300 AutoGluon experiments outperformed a single Temporal Fusion Transformer (TFT) model, which I adjusted after studying the deep double descent phenomenon as detailed in the paper: https://arxiv.org/abs/1912.02292. The experiments indicated that the "Effective Model Complexity" was not well-suited to the size of my dataset (~84,000 rows), leading to suboptimal generalization.
Details:
Upon adjusting the hyperparameters of the TFT model as follows, I achieved significantly improved results:
hyperparams = {
    "max_epochs": 200, # 100 would have been sufficient
    "early_stopping_patience": None,
    "context_length": 96,
    "hidden_dim": 256, # default 32
    "variable_dim": 128, # default 32
    "num_heads": 16, # default 4
}

The improvement suggests a heuristic that could be formalized within AutoGluon: for neural network training, one should either opt for a relatively small or large model in comparison to the dataset size.
Suggested Implementation:

Integrate a module that monitors training metrics to identify signs of deep double descent.
Develop logic to recommend or automatically adjust model size (e.g., layers, dimensions) based on the dataset's characteristics and the observed training dynamics.
Provide an option to disable early stopping when the model is not yet at the optimal complexity point.

This feature would align with AutoGluon's philosophy of minimizing the need for manual hyperparameter tuning by introducing a data-driven approach to navigate the trade-off between model complexity and generalization.
I believe this enhancement could significantly improve model performance, especially in cases where the current heuristics do not naturally lead to the avoidance of deep double descent.
Thank you for considering this feature request.

Great observation and description! I think a meta-learning approach as you describe could work well. Prior to using meta-learning, we could also expand the diversity of model hyperparameters as done with Tabular in 1.0 via Zeroshot-HPO with TabRepo.


update asylum payment address

Update Asylum Payment address

Greetings, guys!
Sorry for bothering you
We've updated Asylum payment address (also already delivered the third milestone with this address)
Hope that's ok for you!


Generate code coverage reports using CodeCov

Description
$title
Related to #533

Closing as the changes have been applied via: https://github.com/ballerina-platform/module-ballerinax-microsoft.excel/pull/59


Fix theme toggle

✨ Codu Pull Request 💻

Pull Request details:

Unify styles in mobile and desktop view, focus and hover in both working the same way.
Ring offset color in the images is white as well to match the other styles.
Remove the ThemeToggleMobile to have it all together in the Themetoggle file

Any Breaking changes:

None

Associated Screenshots:
( Welcome file extensions include gifs/png screenshots of your feature in action )

Closes #557


Determine our policy for find bar changes

The viewer contains a custom find bar, but we also support the integrated find bar in Firefox. While this might provide a better integration, it does lead to maintenance issues since the integrated find bar in Firefox is practically uncustomizable. This has led to users requesting valid features that we cannot fulfill without introducing a difference in behavior between the custom and the integrated find bar.
The most recent example is #12141, but issues #3565, #8185 and #9831 are also examples of this.
I personally think that supporting the integrated find bar was beneficial and easier before, but is nowadays holding us back from making further changes that users request and that make sense. I therefore open this issue for discussion on this topic.
I see the following options:

Keep a strict policy that differences between the custom/integrated find bar are not accepted. This is what we do now, but as said I feel like it's holding back development.
Accept differences between the implementations. This seems fair to me since a user never uses both find bars at the same time and it would allow us to fulfill fair user requests again.
Drop the integrated find bar support altogether. Aside from simplifying the code and preventing the problems described here, I also don't really see a clear advantage nowadays to use the integrated find bar over the custom one since both do the same and the custom one is even styled nicely according to the PDF.js style, and thus "blends in" more.

I personally favor option 3, but if that is not preferred option 2 seems best to me. I feel like option 1 is no longer viable.
What do you think @brendandahl @Snuffleupagus and others?
(If we decide to go for option 2 or 3, we should introduce #12141 again since it's reverted pending the outcome of this discussion.)

Keep a strict policy that differences between the custom/integrated find bar are not accepted. This is what we do now, but as said I feel like it's holding back development.

Honestly, I do think that this is a reasonable policy and it doesn't really bother me all that much given that the features in question are (somewhat) minor. Also, keeping in mind that the the Firefox PDF viewer is the main reason for this library existing in the first place.

Accept differences between the implementations. This seems fair to me since a user never uses both find bars at the same time and it would allow us to fulfill fair user requests again.

Assuming that the difference are indeed small, I suppose that this might be OK on a case-by-case basis.

Drop the integrated find bar support altogether. Aside from simplifying the code and preventing the problems described here, I also don't really see a clear advantage nowadays to use the integrated find bar over the custom one since both do the same and the custom one is even styled nicely according to the PDF.js style, and thus "blends in" more.

Using the Firefox native browser findbar, with the Firefox PDF viewer, has the distinct advantage of making the PDF viewer feel "part of the browser" itself (rather than being a completely separate entity). Hence I completely understand why you want to use the native browser findbar, and would really advice against taking this route.

Keep a strict policy that differences between the custom/integrated find bar are not accepted. This is what we do now, but as said I feel like it's holding back development.

Honestly, I do think that this is a reasonable policy and it doesn't really bother me all that much given that the features in question are (somewhat) minor. Also, keeping in mind that the Firefox PDF viewer is the main reason for this library existing in the first place.

Accept differences between the implementations. This seems fair to me since a user never uses both find bars at the same time and it would allow us to fulfill fair user requests again.

Assuming that the difference are indeed small, I suppose that this might be OK on a case-by-case basis.

Drop the integrated find bar support altogether. Aside from simplifying the code and preventing the problems described here, I also don't really see a clear advantage nowadays to use the integrated find bar over the custom one since both do the same and the custom one is even styled nicely according to the PDF.js style, and thus "blends in" more.

Using the Firefox browser findbar, together with the Firefox PDF viewer, has the distinct advantage of making the PDF viewer feel "part of the browser" itself (rather than being a completely separate entity). Hence I completely understand why you want to use the browser findbar, and would really advice against taking this route.
Generally speaking: I do believe that the best course of action here would be for someone the actually spend the necessary time looking into good/safe ways of solving issues such as #3565 and #8185 for the Firefox browser findbar integration.
Writing the code would be (almost) trivial, it's determining what to do about things like https://github.com/mozilla/pdf.js/issues/3565#issuecomment-22566903 that's the difficult part.

An integrated findbar was a pretty early requirement in Firefox and I don't think that has changed. I think the main thing keeping us back from #2 is testing for the integrated version and web version. If they're both thoroughly tested I'd be fine with them diverging more.

Keeping the PDF.js findbar consistent with the native Firefox findbar has, over the years with changes/improvements to the PDFFindController, significantly (as far as I'm concerned) simplified maintenance of the relevant code.
Hence I'd suggest, as before, that we settle on option 1 from https://github.com/mozilla/pdf.js/issues/12149#issue-670311856 since that's the simplest solution and carries the least risk of introducing bugs (or confusion inconsistencies) in the find-related code.

Let's indeed go for option 1 then since if the native findbar is still useful it makes things easier if they are in sync indeed.


Badges and release

Pull Request Test Coverage Report for Build 20

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.737%

Totals

Change from base Build 19:
0.0%

Covered Lines:
391

Relevant Lines:
396

💛  - Coveralls


ci: fixes for release automation

Set correct permissions to upload artifacts and switch to a different release action since our old one was archived.

@michi-covalent nothing to change, the existing template assumes that all this automation is already working.


Highlighting of nested generics isn't correct

(Original issue 1451 created by nic0lette on 2018-06-22T18:19:17.113124+00:00)
The highlighting present in this example: http://pygments.org/demo/6751426/ isn't correct/looks off.
The initial "<" of "<T, R : Comparable>" probably shouldn't be highlighted any differently than the second or closing brackets.

(Original comment by jereksel on 2018-07-01T17:18:40.318061+00:00)
Yeah, there seems to be issue when "<" is not after another character: http://pygments.org/demo/6753434/


Latest version of stembuild construct hangs forever

The recent dependency updates pulled in this winrm client library update which changes winrm command "timeout error" handling.
Old working stembuild logs:
Created directory for audit policy
Copied C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\Machine\microsoft\windows nt\Audit\audit.csv
to C:\Windows\system32\GroupPolicy\Machine\Microsoft\Windows NT\Audit\audit.csv
Clearing existing audit policy
Apply Audit policy from C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\Machine\microsoft\windows nt\Audit\audit.csv
Apply security template: C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\Machine\microsoft\windows nt\SecEdit\GptTmpl.inf
Import Machine settings from registry.pol: C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\Machine\registry.pol
Import User settings from registry.pol: C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\User\registry.pol

winrm connection event: unknown error Post "http://<IP_ADDRESS>:5985/wsman": read tcp <IP_ADDRESS>:34002-><IP_ADDRESS>:5985: read: connection timed out

Finished executing setup script 2 of 2.
2023-12-14T14:35:56.530062+00:00 Still preparing VM...
VM has now been shutdown. Run `stembuild package` to finish building the stemcell.
Waiting for stemcell disk packaging and shutdown
Pass 1:   Power state:  poweredOff
Waiting 30 seconds and will check then...
Pass 2:   Power state:  poweredOff
Waiting 30 seconds and will check then...
Waiting loop for stemcell shutdown complete.

Latest hanging stembuild logs:
Created directory for audit policy
Copied C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\Machine\microsoft\windows nt\Audit\audit.csv
to C:\Windows\system32\GroupPolicy\Machine\Microsoft\Windows NT\Audit\audit.csv
Clearing existing audit policy
Apply Audit policy from C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\Machine\microsoft\windows nt\Audit\audit.csv
Apply security template: C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\Machine\microsoft\windows nt\SecEdit\GptTmpl.inf
Import Machine settings from registry.pol: C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\Machine\registry.pol
Import User settings from registry.pol: C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\User\registry.pol

What's happening is that "script 2 of 2" calls sysprep at the end and shuts down the VM and causes a winrm connection timeout that the winrm client library retries forever (new behavior) where previously it would get an unknown error Post "http://<IP_ADDRESS>:5985/wsman": dial tcp <IP_ADDRESS>:5985: i/o timeout and "finish the command" allowing stembuild to proceed.

We found if the windows host and stembuild utility in same subset, It can passed with "no route to host" after almost 5 minutes waiting.
`Created directory for audit policy
Copied C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\Machine\microsoft\windows nt\Audit\audit.csv
to C:\Windows\system32\GroupPolicy\Machine\Microsoft\Windows NT\Audit\audit.csv
Clearing existing audit policy
Apply Audit policy from C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\Machine\microsoft\windows nt\Audit\audit.csv
Apply security template: C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\Machine\microsoft\windows nt\SecEdit\GptTmpl.inf
Import Machine settings from registry.pol: C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\Machine\registry.pol
Import User settings from registry.pol: C:\Program Files\WindowsPowerShell\Modules\BOSH.Sysprep\cis-merge-2019\DomainSysvol\GPO\User\registry.pol
winrm connection event: unknown error Post "http://<IP_ADDRESS>:5985/wsman": dial tcp <IP_ADDRESS>:5985: connect: no route to host
Finished executing setup script 2 of 2.
2024-03-07T01:28:48.140129-08:00 Still preparing VM...
VM has now been shutdown. Run stembuild package to finish building the stemcell.`

Yeah, I don't see a change in our nightly builds. Both back before the change (~November) and now have a 4-5 hang in there, but then continue.
Our CI worker and the VM we're running stembuild against do both run in the same subnet though.
@sneal is the subnet thing possibly why you're experiencing this and we're not?

Hi, @jpalermo  one customer encountered this issue due to they always deploy the stembuild utility and windows vm in different subnet.  They also can constructed stemcell successfully  before this pr merged.
And afterwards comparing with our environment, we found this difference, They customer attempt to modify the ip in same subnet and it's success to construct stemcell.
So we consider this pr change impacts the winrm command execution exit , and then cause the hang situation in customer side.

@jpalermo You will see different results depending up whether on the same subnet or not.
The winrm library we're using now retries on a connection timeout forever and only returns once the command has executed to completion. In our case since we execute a command that shuts the VM down, it'll never complete the command (from the winrm library perspective). Golang will return a different error to the winrm library (timeout vs no route to host) depending upon if stembuild is run in the same or different subnets.
While the winrm library should have some sort of timeout and give clients more control over retry behavior, we really just need to execute the final command (sysprep & shutdown) while simultaneously polling the VM for shutdown via some mechanism. Once shutdown is detected we can continue.

Opened a PR to provide a config flag to disable the new behavior.

@sneal, is this all fixed now?


python311Packages.certipy-ad: 4.5.1 -> 4.7.0

Diff: https://github.com/ly4k/Certipy/compare/refs/tags/4.5.1...4.7.0
Changelog: https://github.com/ly4k/Certipy/releases/tag/4.7.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 244900 run on x86_64-linux 1

6 packages built:

certipy (python310Packages.certipy-ad)
certipy.dist (python310Packages.certipy-ad.dist)
certsync
certsync.dist
python311Packages.certipy-ad
python311Packages.certipy-ad.dist


[Issue] Try to reproduce Call to static method Webmozart\Assert\Assert::uuid() with non-empty-string will always evaluate to true.

I fail to reproduce it in test case but it's kind of hard to debug tests since they're loaded from phar and not very flexible then.
I'm getting:

Call to static method Webmozart\Assert\Assert::uuid() with non-empty-string will always evaluate to true.

Assert::stringNotEmpty($id); // I need both in order to have more precise assertion message
Assert::uuid($id);

with phpstan v1.4 and 1.0.7 extesnion

Are you using phpstan-strict-rules maybe? I managed to reproduce it in am integration kind of test in #86.
But as the error is coming from that rule it might be config only then. I didn't have time yet to debug it.

Are you using phpstan-strict-rules maybe?

yes, I do.
I see a lot of changes in #86 related to non-empty string, will it covert this?

Unfortuntely not, see last comment there. I'm basically waiting on input from Ondrej now. See also #85 where I suggested to revert the changes that broke this for now.

-> #89 / 8b080dcdc09ec190eab27d28a33ecaf93c08ea47

Reproduced in https://github.com/phpstan/phpstan-webmozart-assert/pull/89


Setup Github Actions to build and release new versions to PyPi

Need to setup our Release flow to publish versions of sundew to PyPi

Fixed with the release of v0.1.2


[varLib] Add optional 'simple' supports/region builder

Add an optional 'simple' supports/region builder for 'simple' master configurations, addressing some comments in #2207.
With 'simple' I mean:

There are masters at all corners of the designspace
Intermediates on an axis must be present at all other axis master locations, too. For example, in a wght/wdth system, if there is a wdth intermediate for narrow, the same intermediate must exist for wide.

The resulting model is equivalent with the one build by the "generic" solver, but it will behave better with respect to rounding at the peak positions: intermediate masters always get matched exactly, instead of being (maximally) 0.5 unit off. (This is especially important if 100% metrics compatibility is desired at the master locations: this is currently not possible with the general solver.)
There will be fewer deltas participating at any one point in the designspace, so this will be more efficient at runtime.
However, as Behdad pointed out, the deltas to be stored will likely be larger, so may be stored less efficiently.

A followup could be to add a lib key to the designspace document that turns on the new behavior. But I'd first like to see if there's some support for this PR in general.

Thanks Just.
I'm certainly open this this line of work.
I'm against options that makes designers having to make decisions without knowing exactly what they are choosing. How about we add a tolerance=.5 argument to VariationModel? That satisfies your needs but is automatic.
We can also relax the conditions under which that's attainable. If we cannot guarantee such a model, the object creation would fail.

With a guarantee that tolerance=.5 would never fail.

Without knowing the master values, what does that tolerance mean, though?

My thinking was:

Your general algorithm is pretty fantastic, and should probably always be used by default, as it imposes no restrictions on the master configuration
In some fringe cases (100% master precision requirement, with a simple master configuration), it is better to use the "simple" algorithm
Those cases are truly expert use, so having to set an option explicitly isn't going to be a problem

Alternatively, I could see us always use the simple algorithm when the master configuration allows it.
Advantage:

Zero config

Disadvantages:

No control for the designer
Possibly larger binaries
Not backward compatible for post-processing client code that expects output from the general algorithm

Third option: always use the simple algorithm when the master configuration allows it, with a flag to optionally turn it off: opt-out vs opt-in.

I just realized that the "simple" region configuration is also possible in a system where some "corner masters" are absent. Will think of how to improve the algorithm to accomodate that.
Trivial example: [{}, {'a': 1.0}, {'b': 0.3}, {'b': 0.6}, {'b': 1.0}]

The last commit broadened what can be considered a "simple" model:
A model is "simple" when any two axes that actively cooperate
(ie. have masters at non-zero positions for both axes) have a
complete set of intermediates. For example, if axes "a" and "b"
cooperate, and axis "a" has masters at 0, 0.5 and 1 from the
neutral master, it must have those intermediates at all values
for axis "b" as well.

This property allows us to use a simpler algorithm to compute
the master supports, which will have fewer overlapping regions.

I'm not convinced of how well that is worded, suggestions welcome.

To clarify for the casual passer-by: the alternative "simple" region algorithm proposed here is 100% equavalent to the existing (more general) algorithm: the resulting interpolated shapes will be the same at all positions within the design space. (There's even a unit test that verifies that.)
There will be tiny differences due to different rounding, and that's where the "simple" algorithm is better: it guarantees that the  shapes and metrics at all master positions match the input masters exactly, where the general algorithm may be (maximally) 0.5 units off (which practically may be one unit, depending on rendering environment).

So I'm okay merging this for now, on the condition that we can remove it and reconcile the ideas into the main model soon. I've since solved the modeling theoretical problems I was dealing with. I'll comment here or in another issue.

I'm also ok with leaving this unmerged for now, for reference, if you're confident you can recreate the functionality within the main model. Whichever you find more convenient.

What is the status of this pull request, do we still want to keep it unmerged?

Merging it is probably better than the status quo. But ugh, whitespace merge conflict :(

I'll take a look in the next ten days to see if I can adjust the default algorithm to generate more simple regions.

Hi @justvanrossum. Based on your code here, I modified the generic solver. It's in https://github.com/fonttools/fonttools/pull/2717


Support https

Look at Caddy from go-land

Caddy is using Let's Encrypt, a free CA. There's a promising ruby gem for it https://github.com/unixcharles/acme-client, that might be leveraged to get the appropriate certs before the Sinatra app spins up. If I have free time on the beach tomorrow I'll look into this, but wanted to leave my research in case I don't get to it.


Outdated drivers / wine base image

I was curious to try this out but the netbrain/wine base image seems to be based on bullseye and doesn't have new enough drivers for my Ryzen 6850U. It also doesn't have a Docker file either, so I can't build my own easily without reverse engineering it. I'd like to start with an ubuntu:mantic base really.

it's based on this: https://github.com/netbrain/dockerfiles/tree/master/wine
Feel free to base it on your own image.
What do you mean by that bullseye don't have drivers for your ryzen card? I was not aware that this was even something to take into consideration.

The 3D drivers are userspace components shipped by mesa; the ones in bullseye (libgl1-mesa-dri) are far too old to support modern GPUs, after all bullseye is almost EOL by now.

The container is supposed to be using your host drivers, though.

Hello,
I confirm it does not work with my recent GPU (AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics). Mesa version included in netbrain/wine is indeed too old.
I managed to get Zwift running by rebuilding an image based on a modified version of netbrain/wine in which bullseye is replaced by bookworm.

https://hub.docker.com/layers/netbrain/wine/7.0.0-bookworm/images/sha256-93716a9ea11be31f596a1cf53b0637f3e0eeacf2d32fddbf00d072abdb8a2f31?context=explore

Taking your word for it and upgrading to bookworm :)

I've rebuilded your wine docker image by changing bullseye to bookworm in the Dockerfile (two changes)
@@ -1,4 +1,4 @@
-FROM debian:bullseye-slim
+FROM debian:bookworm-slim

 ENV NVIDIA_VISIBLE_DEVICES \
         ${NVIDIA_VISIBLE_DEVICES:-all}
@@ -32,7 +32,7 @@
        libgl1-mesa-glx libgl1-mesa-glx:i386 \
        libgl1-mesa-dri libgl1-mesa-dri:i386 && \
        wget -qO - http://dl.winehq.org/wine-builds/winehq.key | apt-key add - && \
-       echo "deb https://dl.winehq.org/wine-builds/debian/ bullseye main" > \
+       echo "deb https://dl.winehq.org/wine-builds/debian/ bookworm main" > \
        /etc/apt/sources.list.d/winehq.list && \
        apt-get update && \
        apt-get -y install --install-recommends winehq-stable && \

Ah right, missed that one

The image build fails at winetricks --unattended dotnet20 win10 when building from scratch now.

Yes I'm aware, trying to fix it when I have the time 😅
On Thu, Dec 7, 2023, 19:30 quietvoid @.***> wrote:

The image build fails at winetricks --unattended dotnet20 win10 when
building from scratch now.
—
Reply to this email directly, view it on GitHub
https://github.com/netbrain/zwift/issues/44#issuecomment-1845896136, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACTNC4UUWEUK5N5LMFIIL3YIIDNHAVCNFSM6AAAAAA7YGWZHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBVHA4TMMJTGY
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Sorry for starting this. I also spent 4 hours or so trying to produce an image, but from scratch using a Ubuntu container and Ubuntu's wine package and gave up over similar issues at like 11pm and bought an Apple TV later.
I mean graphics is a lot better on PC in wine but the effort of getting it running and keeping it running is a bit mad.
I think a problem is that the image was past built with wine 7 but now it's wine 8.0.2 or something in the winehq and it may have different bugs causing different winetricks to not work, because you can't pin a specific wine repository state.
Good luck though.

I'm pretty sure I have something very soon. I'll keep you posted
On Thu, Dec 7, 2023, 20:15 Julian Andres Klode @.***>
wrote:

Sorry for starting this. I also spent 4 hours or so trying to produce an
image, but from scratch using a Ubuntu container and Ubuntu's wine package
and gave up over similar issues at like 11pm and bought an Apple TV later.
I mean graphics is a lot better on PC in wine but the effort of getting it
running and keeping it running is a bit mad.
I think a problem is that the image was past built with wine 7 but now
it's wine 8.0.2 or something in the winehq and it may have different bugs
causing different winetricks to not work, because you can't pin a specific
wine repository state.
Good luck though.
—
Reply to this email directly, view it on GitHub
https://github.com/netbrain/zwift/issues/44#issuecomment-1845958029, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACTNC7HR7UTPGKHEU6L2PTYIIIVVAVCNFSM6AAAAAA7YGWZHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBVHE2TQMBSHE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

trying a matrix build now to check which combinations of versions that work with the bookworm distro
https://github.com/netbrain/zwift/actions/runs/7133908520/job/19427595768

Also my latest Dockerfile with the same versions as used in bullseye build seems to work on bookworm. Let's see if the github action get's a successfull build! :crossed_fingers:

I mean graphics is a lot better on PC in wine but the effort of getting it running and keeping it running is a bit mad.

Yeah, that is exactly why i started this project, so it should be a single build to rule them all kind of thing.
I don't blame you for purchasing a Apple TV ;) but your always welcome to try this again in the future :+1:

https://github.com/netbrain/zwift/actions/runs/7134247593
new run started as the other "failed fast".
Seems that we have a couple that is in the green.
How should we proceed with upgrading? just simply use the latest version combination and cross our fingers that it works? or stay on something we know is stable? (i.e wine 7.0, winetricks 2021, wine-mono 7.0) ?

Build from scratch have now replaced the latest container version


replaceTitle not working with RegExp

If you use replaceTitle normally, it's working fine:
replaceTitle:[ 	["abc", "def"] ]
But, if you use RegExp, doesn`t matter what, no replacement is done, here i used the expample from  MMM-CalendarExt2/docs/Configuration/Calendar.md:
replaceTitle:[ 	["/([A-Z])([a-z]+ ?)/g", "$1"] ]
Someone here with the same issue?

Sorry, this is a bug in the documentation.
You need to remove the quotes around the RegExp:
replaceTitle:[ [/([A-Z])([a-z]+ ?)/g, "$1"] ]

With the quotes it just is a string, without them Javascript recognizes them as a RegExp and created an Object of the correct type.


Sentiment (Positivity/Negativity) data for Blogs/Posts

The common positivity/negativity of blogs and social media posts can be used to determine the writer's personality.
https://www.semanticscholar.org/paper/Analyzing-writing-styles-of-bloggers-with-different-Park-Li/7da1b3fd6195ae45a3bd021f391042e0ba365e2e
Here is some sentiment lexicon that can be used to find these patterns (in multiple languages):
English Lexicon: https://github.com/zengyan-97/Sentiment-Lexicon
Universal lexicon: https://github.com/ehsanasgari/UniSent
European Lexicon: https://github.com/opener-project/VU-sentiment-lexicon
Lexicon building: https://github.com/WladimirSidorenko/SentiLex
Lexicon Expansion: https://github.com/uhh-lt/LexiExp
Specific usage: https://github.com/williamleif/socialsent
https://github.com/SentometricsResearch/GWP
https://github.com/aesuli/SentiWordNet
Issue: what about OOV (outside-of-vocabulary) words?

And there are also emotional lexicons https://github.com/JULIELab/MEmoLon


fix: validate that there are pages in context dict before accessing

Otherwise index out of bounds error happens

Coverage remained the same at 89.157% when pulling<PHONE_NUMBER>bd0e0ef53a476ce87403a7465e1e81 on robertomier:fix/context-has-pages into 22f9b2860251476708d27c6ee41c03e89f263015 on Telefonica:master.


SLACK CONNECTION FAILED Only absolute URLs are supported

Using Node 18 we get an error message from fetch "Only absolute URLs are supported"
Drop the version back to Node 16 to resolve the problem.
Output
[4:59:55 AM] [semantic-release] › ✖  SLACK CONNECTION FAILED Only absolute URLs are supported
| AggregateError:
  | SemanticReleaseError: Only absolute URLs are supported
  | at module.exports (/workdir/node_modules/semantic-release-slack-bot/lib/postMessage.js:49:11)
  | at async module.exports (/workdir/node_modules/semantic-release-slack-bot/lib/success.js:123:3)
  | at /workdir/node_modules/semantic-release/lib/plugins/pipeline.js:54:11
  | at async pluginsConf. [as success] (/workdir/node_modules/semantic-release/lib/plugins/index.js:80:11)
  | at async run (/workdir/node_modules/semantic-release/index.js:209:3)
  | at async module.exports (/workdir/node_modules/semantic-release/index.js:269:22)
  | error Command failed with exit code 1.
  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
  | error Command failed.
  | Exit code: 1
  | Command: /usr/local/bin/node
  | Arguments: /opt/yarn-v1.22.19/lib/cli.js run semantic-release --debug
  | Directory: /workdir/apps/cron-coin-gecko
  | Output:
  |
  | info Visit https://yarnpkg.com/en/docs/cli/workspaces for documentation about this command.
  | 🚨 Error: The command exited with status 1

Can you share your configuration?

I have the same problem,
node 18.15.x
semantic-release 20.x
this is the configuration
{
  "branches": [
    {
      "name": "master",
      "channel": "latest",
      "type": "release"
    },
    {
      "name": "beta",
      "channel": "beta",
      "prerelease": true
    }
  ],
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    [
      "@semantic-release/changelog",
      {
        "changelogFile": "CHANGELOG.md"
      }
    ],
    "@semantic-release/github",
    "@semantic-release/npm",
    [
      "@semantic-release/git",
      {
        "assets": [
          "CHANGELOG.md",
          "package.json"
        ]
      }
    ],
    [
      "semantic-release-slack-bot",
      {
        "notifyOnSuccess": true,
        "notifyOnFail": true,
        "markdownReleaseNotes": true,
        "slackWebhook": ${SLACK_RELEASE_BOT_WEBHOOK_URL}
      }
    ]
  ]
}

I've checked that my github action have access to the proper env in `SLACK_RELEASE_BOT_WEBHOOK_URL`. And when i post to this proper url, with postman, it made it to slack.

What is interesting, when just hardcoding url into "slackWebhook" it works fine :). So probably something related to reading env variables of repository, by semantic-release-slack-bot or semantic-release itsef, is broken. (because like i said, i'm logging my SLACK_RELEASE_BOT_WEBHOOK_URL before release phase, and it is there)

Possibly stupid question but shouldn't the config be like this:
-        "slackWebhook": ${SLACK_RELEASE_BOT_WEBHOOK_URL}
+        "slackWebhook": "${SLACK_RELEASE_BOT_WEBHOOK_URL}"


Demo benchmarks don't show fps

... so are next to useless... :(

you dont go to Canvas2DtoWebGL for performance, it is always going to be worse.
maybe benchmark is not the right word, is more  a comparison to see if it look similar or not.


Fix code to pass pmd:check

Upgraded PMD and fixed code.
Changes include:

Add final to parameters
Use constants instead of magic numbers
Do not modify input parameters
Simplify/rearrange boolean logic
Use equals() to compare objects

The travis file has been updated to include pmd:check.

Coverage decreased (-0.05%) to 98.443% when pulling 02d3f5841f2ec6cbeb53dc564cae5cc4e5206db8 on aherbert:fix-pmd into 8eb0e210abb365b4a0bd6abc365e39c04b80f1d3 on apache:master.


Level 9_09 Stackoverflow

Summary
Could anyone offer some help with this please! It does seem I'm stuck in an infinite loop where my events doesn't get removed from PQ in Simulate8... which I couldn't figure out what is causing it. Also, do anyone have any idea as to why stackoverflow occurred in the the midst of printing the statement? (Is there any link to the issue causing the program to fail?) Or if anyone could help to decipher the error message too! Thanks!
Description
Describe the problem and code snippets if necessary
Screenshots (if any):
Insert Images here if necessary

regarding the infinite loop, did you remember updating your new PQ? for example, eventPQ = eventPQ.poll().second(). Also, do take note of calling that line too early/ too late if your simulate adds/deletes new events in the middle. Im not too sure about the second problem :( sorry but perhaps you can see #407 that faces the same stack overflow issue


ggml converted model

Thanks a lot for all the work on this! Is there any place where the converted ggml model is available for download? Want to make sure I got it right 🤔

Appreciate the kind words!
The pytorch checkpoint that's used by whisper.transcribe in this repo is here
https://github.com/akashmjn/tinydiarize/blob/886a8d3523c5bf6e8bfc57f3441f1ce6f4345ad4/whisper/__init__.py#L23
And you can find the mirror for GGML model over on the whisper.cpp repo here  (it's hosted it on HuggingFace)
https://github.com/ggerganov/whisper.cpp/blob/4774d2feb01a772a15de81ffc34b34a1f294f020/models/download-ggml-model.sh#L55
It was converted with the standard conversion script:
https://github.com/ggerganov/whisper.cpp/blob/master/models/convert-pt-to-ggml.py

Thanks for these, confirmed I did it correctly! It works really well!


[BugFix][Oracle-cdc] Supports the incremental phase of the pdb

close #6594
Purpose of this pull request

Does this PR introduce any user-facing change?

How was this patch tested?

Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

Please add testcase

Please update docs

Please add testcase

Ok, I'll add it,


python3Packages.pytest-cases: 3.6.2 -> 3.6.3

Motivation for this change
Update to latest upstream release 3.6.3
Change log: https://github.com/smarie/python-pytest-cases/releases/tag/3.6.3
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 129680 run on x86_64-linux 1

5 packages built:

home-assistant
python38Packages.pysiaalarm
python38Packages.pytest-cases
python39Packages.pysiaalarm
python39Packages.pytest-cases


Outdated link

Hi, the link that hosted the small.en-tdrz pt file expired. Is the file hosted somewhere else?
https://github.com/akashmjn/tinydiarize/blob/7cba47def707514fe68bbd6663f97663ea482158/whisper/__init__.py#L23

over on HuggingFace
https://huggingface.co/akashmjn/tinydiarize-whisper.cpp/tree/main
Files and versions > ggml-small.en-tdrz.bin

The direct link is https://huggingface.co/akashmjn/tinydiarize-whisper.cpp/resolve/main/ggml-small.en-tdrz.bin


⚠ Bofrost.de has degraded performance

In 1e7829c, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1078 ms

Resolved: Bofrost.de performance has improved in fd0b598 after 52 minutes.


It seems that there is a problem with sticker

In my computer, I can receive and send message using v0.2 but the sticker is only one type no matter what sticker I select.

@EricDracula  can you give out more information about your system

System: Linux-4.13.12-1-ARCH
Desktop: Gnome-3.26.2
Electronic: 1.6.15

@EricDracula  Rogar that


Modifying statement for PS

"Convert users from per-user MFA to Conditional Access based MFA" is not what the PS performs as it just changes state for per-user MFA. I believe "Convert per-user MFA enabled and enforced users to disabled" is more appropriate explanation.

Learn Build status updates of commit 8f6149a:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

Line 0, Column 0: [Error: git-clone-failed] Failure to clone the repository `https://github.com/Azure-Samples/cognitive-services-speech-sdk#master`. This could be caused by an incorrect repository URL, please verify the URL on the Docs Portal (https://ops.microsoft.com). This could also be caused by not having the proper permission the repository, please confirm that the GitHub group/team that triggered the build has access to the repository.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@justinha
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

Learn Build status updates of commit 8f6149a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/active-directory/authentication/howto-mfa-userstates.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Update index.tsx [Directions Event Solution page]

Fixed spelling error on Directions Event Solution page (Acknowledgments previously listed "This puzzle draws inspiration from...for groups of thre", should read "three"
You can ignore / delete any irrelevant sections

Postprod
Puzzle URL: <replace_me>

[ ] The puzzle's hints have been exported from Puzzup.
[ ] The puzzle has an emoji in its yaml data.
[ ] The puzzle looks "nice" on the branch frontend.

[ ] Cluephrases and the like are in <Clue> or <Monospace> tags for monospace font.
[ ] Tables are preferred over paragraphs for data.

[ ] The puzzle solution looks "nice" on the branch frontend.
[ ] Images that require attribution have are attributed on the solution page.

Frontend (Next.js)
Frontend changes URL: <replace_me>
Affected page URLS:

<url_1>

Backend (Django)

[ ] I have verified that these changes work when run locally.
[ ] mypy server passes

Closing request / moving to correct location


filter function still called with directories when nodir: true

I just updated to version 4 (was on version 2).
I noticed that with the option nodir: true, the library was actually looking only at the files, which is expected, but unfortunately it does so only at depth 0, and never goes inside of the directories.
It is a bit of a problem, because if one wants to find specific files (using a filter function), you will need instead to do something like:
const path = require('path');
const klawSync = require('klaw-sync');

function filterFn(item) {
  return item.stats.isDirectory() || /[some regex]/.test(path.basename(item.path));
}

const paths = klawSync([FOLDER_PATH], { filter: filterFn });

and then you will need to loop on the paths one more time to filter the directories out yourself.
const files = paths.filter(function(item) {
  return item.stats.isFile();
});

It would great if the default with nodir: true was to traverse all the directories, and call the filter  function only for the files.

@nicolasroger17 it should traverse directories while nodir: true. But, seems like depth limit implementation is buggy and needs to be fixed.

@manidlou @Geelik should we re-open this? The depthLimit looks like it's working, but the original problem of filtering directories even with nodir: true noted by @nicolasroger17 is still not resolved.
His example still doesn't work (with or without) nodir: true if there's no item.stats.isDirectory() || in the filter function.
But maybe a better solution than simply always traversing when nodir: true would be to another option called traverseAll that would ensure all directories are traversed regardless of nodir. This would give the benefit of providing backwards compatibility with the current behavior.
This could be achieved by building on #12 and further simplifying the logic in the for loop like so:
  for (var i = 0; i < paths.length; i += 1) {
    const pi = paths[i];
    const st = opts.fs.statSync(pi);
    const item = { path: pi, stats: st };
    const isUnderDepthLimit = (!opts.rootDepth || pi.split(path.sep).length - opts.rootDepth < opts.depthLimit);
    const filterResult = opts.filter ? opts.filter(item) : true;
    const isDirectory = st.isDirectory();
    const shouldAdd = filterResult && (isDirectory ? !opts.nodir : !opts.nofile);
    const shouldTraverse = isDirectory && isUnderDepthLimit && (opts.traverseAll || filterResult);

    if (shouldAdd) {
        ls.push(item);
    }
    if (shouldTraverse) {
        ls = klawSync(pi, opts, ls);
    }
  }

If you think that makes sense I'll be happy to make a PR.

Yeah i think adding an option is a good idea, it will still allow to filtered out directories with filter if needed and to not bother if we are sure we want to traverse all the tree.

PR welcome!

@manidlou PR made! 😄


/zh-CN/docs/Web/JavaScript/Reference/Global_Objects/Array/includes

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[x] New documentation
[ ] Correction or update

Details

“即使从末尾开始往前跳 fromIndex 的绝对值个索引，然后往后搜寻”  => "即从末尾开始往前跳 fromIndex 的绝对值个索引，然后往后搜寻"

Hello @simplast, could you translate your details in English? I'm not sure I understand what I got from an automatic translation tool :s


Improve data file configuration

Instead of having to rename the TEMPLATE- files.
To update the default files you can just force add the file to commit instead of having two versions of the same file.

The template files are there so that testers know the format of the file
Are they not able to just look at the original version of the file? It still has the same contents as the template files.

The original version of .config has confidential stuff. The problem I'm facing is that we've linked the bot directly to GitHub, so, after every restart, the bot updates all files which results in it overriding any local changes it made. Unless you're able to suggest a solution for this, there's nothing I can do.

we've linked the bot directly to GitHub

If you're using a service such as Heroku or similar and are importing the code from a repository you should try to utilize environment variables for private data.

@ElijahRus250

I'm going to close this because, obviously, a setup with environment variables would be ideal in your situation.


Improve ID of city-owned properties

The PLB dataset is not enough to identify city-owned projects. We'll have to use string-matching like I did in my old script to flag these properties and possibly turn them to "Do Nothing" like the others.

@nlebovits I don't quite understand this ticket. Is it still relevant?

closed by #681


fix(snapshot/timeout): increase nexus and replica snapshot timeout

Increase timeouts for nexus and replica snapshots as it seems sometimes the subsystem pause can take a few seconds. On a particular test it took 11s to pause.
If we increase the IO timeout this might take even longer? So we probably need a way to undo snapshot creation because when we timeout the snapshot might not be created yet so the control-plane can't undo it!

bors merge


Image tags are hardcoded to [neonkube-0.1.0-alpha] in Helm [values.yaml] files

Cluster setup isn't working for v0.2.0-alpha the following services because the image tags are hardcoded to neonkube-0.1.0-alpha in the values files:

neon-acme
neon-cluster-api
neon-cluster-operator

We need a way to inject the correct neonKUBE version number.

FIXED


Memory leak in AugmentationSequence

There seems to be a memory leak in augraphy.AugmentationSequence

My environment
Dockerfile
FROM nvidia/cuda:11.1.1-runtime-ubuntu20.04

ENV DEBIAN_FRONTEND noninteracrive
RUN apt-get update
RUN apt-get upgrade -y
RUN apt-get install -y \
        build-essential git python3 python3-pip \
        ffmpeg libsm6 libxext6 libxrender1 libglib2.0-0

WORKDIR /app
COPY requirements.txt .
RUN pip install --ignore-installed -r requirements.txt

CMD jupyter lab --ip <IP_ADDRESS> --port 1110 --allow-root

Requirements
torch==1.13.1
torchvision==0.14.1
albumentations==1.3.0
augraphy==8.2.4
opencv-python==<IP_ADDRESS>

Сode to reproduce the leak

num_workers = 8
n_epoch = 10
batch_size = 4

ink_phase = [ ]
post_phase = [ ]
paper_phase = [
    agr.AugmentationSequence(
        [
            agr.NoiseTexturize(
                sigma_range=(2, 3),
                turbulence_range=(2, 3),
                p=1
            ),
            agr.BrightnessTexturize(
                texturize_range=(0.999, 0.9999),
                deviation=0.01,
                p=1
            ),
        ],
    p=0.1),
]

pipeline = agr.AugraphyPipeline(ink_phase, paper_phase, post_phase)
def paperfy(image, **params):
    return pipeline(image)

synth_augmentations = A.Compose([
    A.RandomCrop(width=900, height=900),
    A.Lambda(image=paperfy, p=0.8),
    ToTensorV2()
])

train_set = # any dataset with synth_augmentations
trainloader = data.DataLoader(train_set, batch_size=batch_size, num_workers=num_workers, shuffle=True, pin_memory=True, persistent_workers=True)

for epoch in range(n_epoch):
    for i, samples in enumerate(trainloader):
        pass

:fire: workaround: don't use AugmentationSequence or persistent_workers=False

I can see a similar issue here:
https://github.com/pytorch/pytorch/issues/62066
Could you cross check again and see if it is really related to AugmentationSequence?

I have not reviewed the details of the implementation of AugmentationSequence, but this is directly or indirectly related to this module. This is what will happen if we run the same code without it:

persistent_workers=True
removed AugmentationSequencepaper_phase = [
        agr.NoiseTexturize(
            sigma_range=(2, 3),
            turbulence_range=(2, 3),
            p=1
        ),
        agr.BrightnessTexturize(
            texturize_range=(0.999, 0.9999),
            deviation=0.01,
            p=1
        ),
]

memory usage:

Thanks, i was able to reproduce the problem and fix it with this workaround from my end:
https://github.com/sparkfish/augraphy/pull/418
Could you reinstall it from the repo and try again?

fixed!


GH-34977: [C++] Fix "Requires" format in arrow-dataset.pc

Rationale for this change
Requires: arrow_acero;parquet is invalid.
What changes are included in this PR?
Use Requires: arrow-acero parquet.
Are these changes tested?
Yes.
Are there any user-facing changes?
Yes.

Closes: #34977

@github-actions crossbow submit verify-rc-source-ruby-*

+1