Error when running npm install

I get the following error message when I try to run "npm install":

make: *** [binding.target.mk:131: Release/obj.target/binding/src/binding.o] Error 1
make: Leaving directory '/home/user/mautic-theme-skeleton/node_modules/node-sass/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/user/mautic-theme-skeleton/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:314:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
gyp ERR! System Linux 5.4.0-62-generic
gyp ERR! command "/usr/bin/node" "/home/user/mautic-theme-skeleton/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /home/user/mautic-theme-skeleton/node_modules/node-sass
gyp ERR! node -v v12.20.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2021-02-10T17_45_24_359Z-debug.log

npm -v
6.14.10
node -v
v12.20.1

The error indicates the issue during node-sass compilation. There might be some more lines before the fragment you published which could explain the root cause.
Anyway check what prevents node-sass from beining installed maybe you don't have some library required by node-sass

These are all the error messages before that one. However, I have node-sass installed for other sites in this same machine and it compiles without errors. Could this mean that the package is probably outdated or incompatible with my current node/npm setup?
In file included from ../../nan/nan_converters.h:67,
                 from ../../nan/nan.h:221,
                 from ../src/binding.cpp:1:
../../nan/nan_converters_43_inl.h: In static member function ‘static Nan::imp::ToFactoryBase<v8::Boolean>::return_t Nan::imp::ToFactory<v8::Boolean>::convert(v8::Local<v8::Value>)’:
../../nan/nan_converters_43_inl.h:18:51: warning: ‘v8::MaybeLocal<v8::Boolean> v8::Value::ToBoolean(v8::Local<v8::Context>) const’ is deprecated: ToBoolean can never throw. Use Local version. [-Wdeprecated-declarations]
   18 |       val->To ## TYPE(isolate->GetCurrentContext())                            \
      |                                                   ^
../../nan/nan_converters_43_inl.h:22:1: note: in expansion of macro ‘X’
   22 | X(Boolean)
      | ^
In file included from /home/user/.node-gyp/12.20.1/include/node/v8-internal.h:14,
                 from /home/user/.node-gyp/12.20.1/include/node/v8.h:27,
                 from /home/user/.node-gyp/12.20.1/include/node/node.h:67,
                 from ../../nan/nan.h:52,
                 from ../src/binding.cpp:1:
/home/user/.node-gyp/12.20.1/include/node/v8.h:2664:59: note: declared here
 2664 |                 V8_WARN_UNUSED_RESULT MaybeLocal<Boolean> ToBoolean(
      |                                                           ^~~~~~~~~
/home/user/.node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
  328 |   declarator __attribute__((deprecated(message)))
      |   ^~~~~~~~~~
In file included from ../../nan/nan_converters.h:67,
                 from ../../nan/nan.h:221,
                 from ../src/binding.cpp:1:
../../nan/nan_converters_43_inl.h: In static member function ‘static Nan::imp::ValueFactoryBase<bool>::return_t Nan::imp::ToFactory<bool>::convert(v8::Local<v8::Value>)’:
../../nan/nan_converters_43_inl.h:37:57: warning: ‘v8::Maybe<bool> v8::Value::BooleanValue(v8::Local<v8::Context>) const’ is deprecated: BooleanValue can never throw. Use Isolate version. [-Wdeprecated-declarations]
   37 |   return val->NAME ## Value(isolate->GetCurrentContext());                     \
      |                                                         ^
../../nan/nan_converters_43_inl.h:40:1: note: in expansion of macro ‘X’
   40 | X(bool, Boolean)
      | ^
In file included from /home/user/.node-gyp/12.20.1/include/node/v8-internal.h:14,
                 from /home/user/.node-gyp/12.20.1/include/node/v8.h:27,
                 from /home/user/.node-gyp/12.20.1/include/node/node.h:67,
                 from ../../nan/nan.h:52,
                 from ../src/binding.cpp:1:
/home/user/.node-gyp/12.20.1/include/node/v8.h:2702:51: note: declared here
 2702 |                 V8_WARN_UNUSED_RESULT Maybe<bool> BooleanValue(
      |                                                   ^~~~~~~~~~~~
/home/user/.node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
  328 |   declarator __attribute__((deprecated(message)))
      |   ^~~~~~~~~~
In file included from ../../nan/nan_new.h:189,
                 from ../../nan/nan.h:222,
                 from ../src/binding.cpp:1:
../../nan/nan_implementation_12_inl.h: In static member function ‘static Nan::imp::FactoryBase<v8::Function>::return_t Nan::imp::Factory<v8::Function>::New(Nan::FunctionCallback, v8::Local<v8::Value>)’:
../../nan/nan_implementation_12_inl.h:103:42: error: cannot convert ‘v8::Isolate*’ to ‘v8::Local<v8::Context>’
  103 |   return scope.Escape(v8::Function::New( isolate
      |                                          ^~~~~~~
      |                                          |
      |                                          v8::Isolate*
In file included from /home/user/.node-gyp/12.20.1/include/node/node.h:67,
                 from ../../nan/nan.h:52,
                 from ../src/binding.cpp:1:
/home/user/.node-gyp/12.20.1/include/node/v8.h:4276:22: note:   initializing argument 1 of ‘static v8::MaybeLocal<v8::Function> v8::Function::New(v8::Local<v8::Context>, v8::FunctionCallback, v8::Local<v8::Value>, int, v8::ConstructorBehavior, v8::SideEffectType)’
 4276 |       Local<Context> context, FunctionCallback callback,
      |       ~~~~~~~~~~~~~~~^~~~~~~
In file included from ../src/binding.cpp:1:
../../nan/nan.h: In constructor ‘Nan::Utf8String::Utf8String(v8::Local<v8::Value>)’:
../../nan/nan.h:1064:78: warning: ‘v8::Local<v8::String> v8::Value::ToString(v8::Isolate*) const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
 1064 |       v8::Local<v8::String> string = from->ToString(v8::Isolate::GetCurrent());
      |                                                                              ^
In file included from /home/user/.node-gyp/12.20.1/include/node/v8-internal.h:14,
                 from /home/user/.node-gyp/12.20.1/include/node/v8.h:27,
                 from /home/user/.node-gyp/12.20.1/include/node/node.h:67,
                 from ../../nan/nan.h:52,
                 from ../src/binding.cpp:1:
/home/user/.node-gyp/12.20.1/include/node/v8.h:2684:31: note: declared here
 2684 |                 Local<String> ToString(Isolate* isolate) const);
      |                               ^~~~~~~~
/home/user/.node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
  328 |   declarator __attribute__((deprecated(message)))
      |   ^~~~~~~~~~
In file included from ../src/binding.cpp:1:
../../nan/nan.h: In member function ‘void Nan::AsyncWorker::SaveToPersistent(const char*, const v8::Local<v8::Value>&)’:
../../nan/nan.h:1855:64: warning: ‘bool v8::Object::Set(v8::Local<v8::Value>, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
 1855 |     New(persistentHandle)->Set(New(key).ToLocalChecked(), value);
      |                                                                ^
In file included from /home/user/.node-gyp/12.20.1/include/node/v8-internal.h:14,
                 from /home/user/.node-gyp/12.20.1/include/node/v8.h:27,
                 from /home/user/.node-gyp/12.20.1/include/node/node.h:67,
                 from ../../nan/nan.h:52,
                 from ../src/binding.cpp:1:
/home/user/.node-gyp/12.20.1/include/node/v8.h:3499:22: note: declared here
 3499 |                 bool Set(Local<Value> key, Local<Value> value));
      |                      ^~~
/home/user/.node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
  328 |   declarator __attribute__((deprecated(message)))
      |   ^~~~~~~~~~
In file included from ../src/binding.cpp:1:
../../nan/nan.h: In member function ‘void Nan::AsyncWorker::SaveToPersistent(const v8::Local<v8::String>&, const v8::Local<v8::Value>&)’:
../../nan/nan.h:1861:42: warning: ‘bool v8::Object::Set(v8::Local<v8::Value>, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
 1861 |     New(persistentHandle)->Set(key, value);
      |                                          ^
In file included from /home/user/.node-gyp/12.20.1/include/node/v8-internal.h:14,
                 from /home/user/.node-gyp/12.20.1/include/node/v8.h:27,
                 from /home/user/.node-gyp/12.20.1/include/node/node.h:67,
                 from ../../nan/nan.h:52,
                 from ../src/binding.cpp:1:
/home/user/.node-gyp/12.20.1/include/node/v8.h:3499:22: note: declared here
 3499 |                 bool Set(Local<Value> key, Local<Value> value));
      |                      ^~~
/home/user/.node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
  328 |   declarator __attribute__((deprecated(message)))
      |   ^~~~~~~~~~
In file included from ../src/binding.cpp:1:
../../nan/nan.h: In member function ‘void Nan::AsyncWorker::SaveToPersistent(uint32_t, const v8::Local<v8::Value>&)’:
../../nan/nan.h:1867:44: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
 1867 |     New(persistentHandle)->Set(index, value);
      |                                            ^
In file included from /home/user/.node-gyp/12.20.1/include/node/v8-internal.h:14,
                 from /home/user/.node-gyp/12.20.1/include/node/v8.h:27,
                 from /home/user/.node-gyp/12.20.1/include/node/node.h:67,
                 from ../../nan/nan.h:52,
                 from ../src/binding.cpp:1:
/home/user/.node-gyp/12.20.1/include/node/v8.h:3508:22: note: declared here
 3508 |                 bool Set(uint32_t index, Local<Value> value));
      |                      ^~~
/home/user/.node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
  328 |   declarator __attribute__((deprecated(message)))
      |   ^~~~~~~~~~
In file included from ../src/binding.cpp:1:
../../nan/nan.h: In member function ‘v8::Local<v8::Value> Nan::AsyncWorker::GetFromPersistent(const char*) const’:
../../nan/nan.h:1873:61: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
 1873 |         New(persistentHandle)->Get(New(key).ToLocalChecked()));
      |                                                             ^
In file included from /home/user/.node-gyp/12.20.1/include/node/v8-internal.h:14,
                 from /home/user/.node-gyp/12.20.1/include/node/v8.h:27,
                 from /home/user/.node-gyp/12.20.1/include/node/node.h:67,
                 from ../../nan/nan.h:52,
                 from ../src/binding.cpp:1:
/home/user/.node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
 3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
      |                                                   ^~~
/home/user/.node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
  328 |   declarator __attribute__((deprecated(message)))
      |   ^~~~~~~~~~
In file included from ../src/binding.cpp:1:
../../nan/nan.h: In member function ‘v8::Local<v8::Value> Nan::AsyncWorker::GetFromPersistent(const v8::Local<v8::String>&) const’:
../../nan/nan.h:1879:55: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
 1879 |     return scope.Escape(New(persistentHandle)->Get(key));
      |                                                       ^
In file included from /home/user/.node-gyp/12.20.1/include/node/v8-internal.h:14,
                 from /home/user/.node-gyp/12.20.1/include/node/v8.h:27,
                 from /home/user/.node-gyp/12.20.1/include/node/node.h:67,
                 from ../../nan/nan.h:52,
                 from ../src/binding.cpp:1:
/home/user/.node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
 3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
      |                                                   ^~~
/home/user/.node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
  328 |   declarator __attribute__((deprecated(message)))
      |   ^~~~~~~~~~
In file included from ../src/binding.cpp:1:
../../nan/nan.h: In member function ‘v8::Local<v8::Value> Nan::AsyncWorker::GetFromPersistent(uint32_t) const’:
../../nan/nan.h:1884:57: warning: ‘v8::Local<v8::Value> v8::Object::Get(uint32_t)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
 1884 |     return scope.Escape(New(persistentHandle)->Get(index));
      |                                                         ^
In file included from /home/user/.node-gyp/12.20.1/include/node/v8-internal.h:14,
                 from /home/user/.node-gyp/12.20.1/include/node/v8.h:27,
                 from /home/user/.node-gyp/12.20.1/include/node/node.h:67,
                 from ../../nan/nan.h:52,
                 from ../src/binding.cpp:1:
/home/user/.node-gyp/12.20.1/include/node/v8.h:3557:51: note: declared here
 3557 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(uint32_t index));
      |                                                   ^~~
/home/user/.node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
  328 |   declarator __attribute__((deprecated(message)))
      |   ^~~~~~~~~~
In file included from ../src/binding.cpp:1:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../../nan/nan.h:2208:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
 2208 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
      |                                                              ^
In file included from /usr/include/c++/9/cassert:44,
                 from /home/user/.node-gyp/12.20.1/include/node/node_object_wrap.h:26,
                 from ../../nan/nan.h:54,
                 from ../src/binding.cpp:1:
../../nan/nan_object_wrap.h: In destructor ‘virtual Nan::ObjectWrap::~ObjectWrap()’:
../../nan/nan_object_wrap.h:24:25: error: ‘class Nan::Persistent<v8::Object>’ has no member named ‘IsNearDeath’
   24 |     assert(persistent().IsNearDeath());
      |                         ^~~~~~~~~~~
In file included from ../../nan/nan.h:2698,
                 from ../src/binding.cpp:1:
../../nan/nan_object_wrap.h: In member function ‘void Nan::ObjectWrap::MakeWeak()’:
../../nan/nan_object_wrap.h:67:34: warning: ‘void v8::PersistentBase<T>::MarkIndependent() [with T = v8::Object]’ is deprecated: Weak objects are always considered independent. Use TracedGlobal when trying to use EmbedderHeapTracer. Use a strong handle when trying to keep an object alive. [-Wdeprecated-declarations]
   67 |     persistent().MarkIndependent();
      |                                  ^
In file included from /home/user/.node-gyp/12.20.1/include/node/v8-internal.h:14,
                 from /home/user/.node-gyp/12.20.1/include/node/v8.h:27,
                 from /home/user/.node-gyp/12.20.1/include/node/node.h:67,
                 from ../../nan/nan.h:52,
                 from ../src/binding.cpp:1:
/home/user/.node-gyp/12.20.1/include/node/v8.h:570:22: note: declared here
  570 |       V8_INLINE void MarkIndependent());
      |                      ^~~~~~~~~~~~~~~
/home/user/.node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
  328 |   declarator __attribute__((deprecated(message)))
      |   ^~~~~~~~~~
In file included from /usr/include/c++/9/cassert:44,
                 from /home/user/.node-gyp/12.20.1/include/node/node_object_wrap.h:26,
                 from ../../nan/nan.h:54,
                 from ../src/binding.cpp:1:
../../nan/nan_object_wrap.h: In static member function ‘static void Nan::ObjectWrap::WeakCallback(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’:
../../nan/nan_object_wrap.h:124:26: error: ‘class Nan::Persistent<v8::Object>’ has no member named ‘IsNearDeath’
  124 |     assert(wrap->handle_.IsNearDeath());
      |                          ^~~~~~~~~~~
../src/binding.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE render(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/binding.cpp:285:98: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
  285 |     int status = uv_queue_work(uv_default_loop(), &ctx_w->request, compile_it, (uv_after_work_cb)MakeCallback);
      |                                                                                ^~~~~~~~~~~~
../src/binding.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE render_file(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/binding.cpp:321:98: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
  321 |     int status = uv_queue_work(uv_default_loop(), &ctx_w->request, compile_it, (uv_after_work_cb)MakeCallback);
      |                                                                                ^~~~~~~~~~~~
In file included from ../../nan/nan.h:52,
                 from ../src/binding.cpp:1:
../src/binding.cpp: At global scope:
/home/user/.node-gyp/12.20.1/include/node/node.h:737:43: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
  737 |       (node::addon_register_func) (regfunc),                          \
      |                                           ^
/home/user/.node-gyp/12.20.1/include/node/node.h:771:3: note: in expansion of macro ‘NODE_MODULE_X’
  771 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
      |   ^~~~~~~~~~~~~
../src/binding.cpp:359:1: note: in expansion of macro ‘NODE_MODULE’
  359 | NODE_MODULE(binding, RegisterModule);
      | ^~~~~~~~~~~
In file included from ../src/binding.cpp:1:
../../nan/nan.h: In instantiation of ‘void Nan::imp::SetMethodAux(T, v8::Local<v8::String>, v8::Local<v8::FunctionTemplate>, ...) [with T = v8::Local<v8::Object>]’:
../../nan/nan.h:2394:20:   required from ‘void Nan::SetMethod(HandleType<T>, const char*, Nan::FunctionCallback) [with T = v8::Object; HandleType = v8::Local; Nan::FunctionCallback = void (*)(const Nan::FunctionCallbackInfo<v8::Value>&)]’
../src/binding.cpp:351:42:   required from here
../../nan/nan.h:2378:3: warning: ‘bool v8::Object::Set(v8::Local<v8::Value>, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
 2378 |   recv->Set(name, GetFunction(tpl).ToLocalChecked());
      |   ^~~~
In file included from /home/user/.node-gyp/12.20.1/include/node/v8-internal.h:14,
                 from /home/user/.node-gyp/12.20.1/include/node/v8.h:27,
                 from /home/user/.node-gyp/12.20.1/include/node/node.h:67,
                 from ../../nan/nan.h:52,
                 from ../src/binding.cpp:1:
/home/user/.node-gyp/12.20.1/include/node/v8.h:3499:22: note: declared here
 3499 |                 bool Set(Local<Value> key, Local<Value> value));
      |                      ^~~
/home/user/.node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
  328 |   declarator __attribute__((deprecated(message)))
      |   ^~~~~~~~~~
make: *** [binding.target.mk:131: Release/obj.target/binding/src/binding.o] Error 1
make: Leaving directory '/home/user/mautic-theme-skeleton/node_modules/node-sass/build'

That might be the case. You should try to update node-sass version in package.json


adonis2/dbRDA/permanova automation wrappers?

The OMA section "Testing differences in community composition between sample groups" currently shows how to do dbRDA/PERMANOVA with vegan::adonis2. It might be beneficial to standardize this for TreeSE objects to support reporting (tables) and visualization. Not sure, however, if benefits outweight the costs. To discuss & consider.

Done.


Separate files

This pull request does the following:

Allows the user to not have to concatenate all the css into one file, but continue to have separate files

Use case here: may want to have separate files for dynamic loading, separation for certain media (i.e. print).

Added the following:

Options:

separateFiles -- boolean
prefix for files should separateFiles be chosen so as to not overwrite originals

Thanks and let me know.
Richard

+1 , hope it merged

+1 I was just going to ask for this separate file support and see what I could do to help. Thanks. Our previous model under uncss was two separate files and I would love to keep that.
        uncss: {
            dist: {
                files: {
                    './dist/css/small.css': ['./server/views/mobile/uncss.html', './app/**/*.html'],
                    './dist/css/large.css': ['./server/views/desktop/uncss.html', './app/**/*.html']
                }
            },
            options: {
                uncssrc: '.uncssrc'
            }
        },

@mrourke Please merge this PR


travis-ci error, "must be logged in to publish packages"

npm ERR! publish Failed PUT 401
npm ERR! code E401
npm ERR! You must be logged in to publish packages. : mock-server-local
npm ERR!


feat: Add osvscanner.json extractor

Add/migrate osv-scanner.json extractor to use the scalibr format. This is intended to replace the current extractor located here: pkg/lockfile/osv-vuln-results.go
This is extractor is intended to stay in osv-scanner and not moved to osv-scalibr as it is very osv-scanner specific.

I know this is done in another CL but I think it's better to state that lockfilescalibr is temporary.
also is this extractor something new? or we are just copying from existing codebase?

Codecov Report
Attention: Patch coverage is 63.41463% with 15 lines in your changes missing coverage. Please review.

Project coverage is 68.35%. Comparing base (4069367) to head (77dd1ab).
Report is 1 commits behind head on v2.

Files with missing lines
Patch %
Lines

...lescalibr/language/osv/osvscannerjson/extractor.go
63.41%
15 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##               v2    #1338      +/-   ##
==========================================
- Coverage   68.36%   68.35%   -0.02%
==========================================
  Files         185      186       +1
  Lines       17817    17858      +41
==========================================
+ Hits        12180    12206      +26
- Misses       4961     4976      +15
  Partials      676      676

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


(US-76) feat: add language selector in footer

The gif is not capturing the selector correctly

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
0

Relevant Lines:
39

💛  - Coveralls

I just thought of pushing the fixes of today so you guys can take a look of the progress so far.

Selector border remove
Cypress tests added
Issue reverting back to english fixed.
Pending: Styling the opened box selector.

Thanks for the help on the style @jessgusclark .

Selector style done
Cypress tests done
Issue reverting back to english done.


Doxygen comment above struct declarations

It's a small nit, but I was trying to compile the generated files with clang's -Wdocumentation and noticed that the Doxygen comments for the message structs isn't actually valid Doxygen.
In file included from tests/main.c:6:
tests/files/c_source/motohawk.h:50:5: error: '@param' command used in a comment
      that is not attached to a function declaration [-Werror,-Wdocumentation]
 * @param enable Value as on the CAN bus.
    ^~~~~
tests/files/c_source/motohawk.h:54:5: error: '@param' command used in a comment
      that is not attached to a function declaration [-Werror,-Wdocumentation]
 * @param average_radius Value as on the CAN bus.
    ^~~~~
tests/files/c_source/motohawk.h:58:5: error: '@param' command used in a comment
      that is not attached to a function declaration [-Werror,-Wdocumentation]
 * @param temperature Value as on the CAN bus.
    ^~~~~

I think this is because @param isn't actually meant to be put on struct attributes.
This StackOverflow question gives a workaround, if you want to have the comment outside the struct, the way to do this is something like
/** @struct motohawk_example_message_t
 *  @brief Signals in message ExampleMessage.
 *  @var motohawk_example_message_t::enable
 *  Value as on the CAN bus.
 *            Range: -
 *            Scale: 1
 *            Offset: 0
 *  @var motohawk_example_message_t::average_radius
 *  Value as on the CAN bus.
 *            Range: 0..50 (0..5 m)
 *            Scale: 0.1
 *            Offset: 0
 *  @var motohawk_example_message_t::temperature
 *  Value as on the CAN bus.
 *            Range: -2048..2047 (229.52..270.47 degK)
 *            Scale: 0.01
 *            Offset: 250
 */

Alternatively, this can be placed inside the struct above each member, if you want to fix this.

Hello,
I enabled -Wdocumentation for clang and modified the generator to output one comment per struct member. Looks much cleaner than the old big struct comment.
/**
 * Signals in message ExampleMessage.
 *
 * Example message used as template in MotoHawk models.
 *
 * All signal values are as on the CAN bus.
 */
struct motohawk_example_message_t {
    /**
     * Range: -
     * Scale: 1
     * Offset: 0
     */
    uint8_t enable;

    /**
     * Range: 0..50 (0..5 m)
     * Scale: 0.1
     * Offset: 0
     */
    uint8_t average_radius;

    /**
     * Range: -2048..2047 (229.52..270.47 degK)
     * Scale: 0.01
     * Offset: 250
     */
    int16_t temperature;
};

Cool, seems like a good approach!


feat(saya): add config file arg for saya bin

Closes issue #1504
(WIP)

@glihm I start working on this issue, but need a few more details. First of all I want to make sure that I understood the issue correctly, can you please check the PR and let me know.
Second is, does this JSON file should be in the project? If so, which path will be a good location for it.
Thanks in advance.

Hey @Jonatan-Chaverri! Thank you for the contribution. :rocket:

I start working on this issue, but need a few more details.

Awesome, would you mind commenting on the issue, in order to assign it to you?

First of all I want to make sure that I understood the issue correctly, can you please check the PR and let me know.

Yup! You're on the right track! This is what we want, having a one file configuration to load the SayaConfig. As the configuration of the different components will evolve and may be somehow relatively "big", such file can help a lot.
From what's I've seen, here could be the following steps:

Adding the support for serde on SayaConfig.
Error handling on the JSON loading.
Adding some tests to ensure the correct behavior.

Second is, does this JSON file should be in the project? If so, which path will be a good location for it.

You will definitely need to commit at least 1 configuration for testing. We may also include an example configuration file (additionally to the tests files), yes.

Thanks in advance.

Thank to you, let's do it! :)

As it's a WIP, I converted it into a draft, feel free to reach out if you have any question or need some feedback!

@glihm please take a look at the changes and let me know what you think. Thanks.

@glihm please take a look at the changes and let me know what you think. Thanks.

The design chosen for the genesis work required more flexibility on how the content of the JSON is processed. In the case of Saya's configuration file, it will only contains simple values.
Would you mind proposing a new commit where only serde and serde_json are used without introducing new types?
Don't hesitate if you've doubt on how to achieve this.

@glihm ok, implemented the requested changes, please check again. Thanks.

Looks good thank you for the update!

You can remove the example file since we have the test file, it should be fine for now.
Could you ensure you've run the scripts like bash scripts/rust_fmt.sh and bash scripts/clippy.sh.
We may add a comment in the help to explicitly say that the config file takes precedence over every other CLI arguments.

Also could we use the default katana url please? http://localhost:5050. Thanks!

@glihm done! Please check again. Thanks.

Hey @Jonatan-Chaverri thanks for the update.
To ensure you're prepared for the CI, don't hesitate to run locally:
cargo nextest run --all-features

If everything goes well, it should be fine for the CI as well. Could you please have a look?

@glihm now its ready to pass the CI. The major change I did was to add a deserialize function for URL. Please check again. Thanks.

@Jonatan-Chaverri awesome, thank you for the work done here!
I've pushed some minor fixes, one due to celestia namespace limit, and the other one to ensure rpc-url is always given (but optional). Which allows one to do:
saya --config-file ./path/config.json

without having to give --rpc-url, which is non optional. :+1:


Added lots of German translations and fixed some small issues here and there

I've added German TTS and Info-Texts to many of the raids, changed the TTS of some German callouts to fit the default Microsoft Hedda Desktop voice for better pronounciation and I've also added the French localization for o8n while I was at it.
There might be some things you have to look over, like o8n at the end, where I've just copy&pasted the timeline translations from o8s, but there're still lots of leftover God Kefka lines which I didn't look up.

Okay I've just edited the missing mistakes.
Also, I've tried to test the changes, but somehow the timeline isn't registering that my game is set to German and still displays the English timeline. Just to reproduce I'll list the steps I took:
i. Set the game back to German
ii. Set the parsing language in the FFXIV settings from ACT back to German
iii. Disabled test.js (because it was starting the test.js instead of the o8s.js while testing)
iv. Went to middle LaNoscea and started the timeline via /echo :Kefka:28C2:
I've also added the German line for the Timeline-Reset:
'The limit gauge resets!': 'Der Limitrausch-Balken wurde geleert.',
And afterwards I tried the whole thing again:
i. Went to middle LaNoscea
ii. Started the timeline via /echo :Kefka:28C2:
iii. Tried resetting the timeline via /echo Der Limitrausch-Balken wurde geleert. => Didn't work
iv. Tried resetting the timeline via /echo The limit gauge resets! => Worked
And as it turns out the timeline starts and works perfectly - though the timeline-replace doesn't seem to work :/

Thanks for the triggers.  I'll just go ahead and commit this patch now.  More followup can be done in other patches.
I haven't figured out how to have cactbot detect your language.  I know there's some login message like "Welcome to WORLD!" and "Welcome to FINAL FANTASY XIV" in English.  Maybe I could use that to key off of.
At any rate, for now you need to add an option for language in cactbot/user/raidboss.js and set Options.Language = 'de' for it to work.  Take a look at https://github.com/quisquous/cactbot/blob/master/user/raidboss-example.js for more options help too.
One other thing I need German translations for is all of the healer lb3s and the status effects for Weakness and Brink of Death, e.g. https://github.com/quisquous/cactbot/blob/master/CactbotOverlay/WipeDetector.cs#L46 and https://github.com/quisquous/cactbot/blob/master/CactbotOverlay/WipeDetector.cs#L23.


Update to headers 0.2.

The commit says 0.1 but it's actually 0.2

Fixed.

r? @Manishearth

@bors-servo r+

:pushpin: Commit 1d22ded has been approved by Manishearth

:hourglass: Testing commit 1d22ded493a08df4ed158f3db6db545f6664b34c with merge a6e0e2e4f4299a8117adfd46a7e069822875e8e1...

:sunny: Test successful - checks-travis
Approved by: Manishearth
Pushing a6e0e2e4f4299a8117adfd46a7e069822875e8e1 to master...


Error while install-module navcontainerhelper -force

Hi Freddy,
I have another server and it run fine (*) in the early of August.
* install the newest navcontainerhelper
* New-BCContainer from bcinsider (BCArtifactUrl)
 But now, when I've tried to install the newest navcontainerhelp, I've got the error.
 I've tried to find the solution but I could not get any luck.
  ===================================================================
  PS C:\Windows\system32> install-module navcontainerhelper -force
  WARNING: Unable to resolve package source 'https://www.powershellgallery.com/api/v2/'.
  PackageManagement\Install-Package : No match was found for the specified search criteria and module name
  'navcontainerhelper'. Try Get-PSRepository to see all available registered module repositories.
  At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\2.2.1\PSModule.psm1:9683 char:34
  + ... talledPackages = PackageManagement\Install-Package @PSBoundParameters
  +                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  + CategoryInfo          : ObjectNotFound: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package], Ex
  ception
  + FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

https://github.com/microsoft/navcontainerhelper/issues/1261

Dear Freddy,
Thank you for the information.
Renee
From: Freddy Kristiansen<EMAIL_ADDRESS>Sent: Monday, September 7, 2020 3:48 PM
To: microsoft/navcontainerhelper<EMAIL_ADDRESS>Cc: renee_lu 呂玉雯<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/navcontainerhelper] Error while install-module navcontainerhelper -force (#1271)
#1261https://github.com/microsoft/navcontainerhelper/issues/1261
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/navcontainerhelper/issues/1271#issuecomment-688115748, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKJ4YT73HSI55HINFZGYH3TSESF2PANCNFSM4Q5VN55A.


Assembly load change

I thought maybe better to rely on the library more than a specific rule, just to load the assembly.

I wish to avoid stuff that breaks if I rename ValidationLibrary.Rules, because we don't actually care that much where the rules are, we just care that rules are loaded.


[Not a contribution]  Prometheus metrics do not include the Host label

It seems that metrics do not include the host label.
At the moment, it is not possible to filter stats (requests and latency) by host label.
is this something that could be added ?

Dear contributor,
We're closing this issue as there hasn't been any update to it for a long time. If the issue is still relevant in the latest version, please feel free to reopen it. We're more than happy to revisit it again.
Please have a look at our pledge to the community for more information.
Sincerely,
Kong Gateway Team


feat: support the option to use aws-sdk-v2

With AWS announcing in January that the v1 AWS SDK for Go will have its support ending on July 31, 2025, I decide to take a stab at introducing non-breaking change to  support the v2 SDK.
I chose to propagate all the AWS SDK options to the client and remove any support for parsing the region from key arn or loading credentials from csv/ini files. All of this extra functionality is still available through the sdk options, refer to AWS's documentation .
Let me know what you think.

Thanks for looking into implementing this. We certainly should have support for V2.
But this implementation looks overly complicated to me. Would it be better to simply have one new ClientOption "WithKMSV2"? And then require that the user always needs to create these KMS v2 client themselve. Then, we don't need to handle the options of these clients ourselves.
The timeout could be another ClientOption. (But I guess the timeout will not be needed anymore once https://github.com/tink-crypto/tink-go/issues/6 is resolved.)

👋 Thank you for your feedback!

But this implementation looks overly complicated to me. Would it be better to simply have one new ClientOption "WithKMSV2"? And then require that the user always needs to create these KMS v2 client themselve. Then, we don't need to handle the options of these clients ourselves.

This is what I initially planned, and then pivoted when I realized the current v1 implementation offered up ways to specify credentials, and we now need the timeout. The implementation tries its best to separate all options, ensuring that the code is not burdened with the responsibility to constantly check  whether a v1-specific option has been already been set, it only needs to check this one place.
Removing the load and kms options is a easy change, which leads us to the timeout 🤔

The timeout could be another ClientOption. (But I guess the timeout will not be needed anymore once tink-crypto/tink-go#6 is resolved.)

Would this timeout now apply to the v1-sdk as well, since it would become a 'v1 option'? If so, we would have to change the v1 Encrypt/Decrypt calls to use their WithContext variant and make sure we aren't changing any current timeout behavior. Or add new branches to use WithContext if the timeout is set.  If not, I'm not sure of a good way to let users know this is only valid for v2, simply naming it with some v2 prefix/suffix?
Finally, would you say a v2 implementation would be blocked until [tink-crypto/tink-go#6] is complete?

Yes. But I think it should be even simpler. I don't think we want to add the timeout, because I think that will not be needed anymore once we add the context directly to the remote encrypt/decrypt calls, which we will add soon. I think the additional API really should just be a WithV2KMS option. And I don't think we need the "Aead builder", I'd prefer to not refactor the code, just add the new KMS and don't change the old code path.

Yes. But I think it should be even simpler. I don't think we want to add the timeout, because I think that will not be needed anymore once we add the context directly to the remote encrypt/decrypt calls, which we will add soon. I think the additional API really should just be a WithV2KMS option. And I don't think we need the "Aead builder", I'd prefer to not refactor the code, just add the new KMS and don't change the old code path.

Hmm.. alright. Seeing as how the timeout is needed, I'm not sure how best to do this. I'll hold off until the context change comes through.


HDDS-4003. Delete the redundant word of the description

What changes were proposed in this pull request?
Delete the redundant word of the description
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4003

@bharatviswa504 Thanks for the review.
Can you help assign JIRA to me?
My JIRA account is john28152815

@john28152815 I have assigned this to you.
I have added you to the contributor list, you can assign yourself if you are interested in picking up any open Jiras from now.

Thank You @john28152815 for the contribution.


Setup.md suggests the wrong path to pinentry-mac on apple silicon

Summary
On Mac OS X,setup.md suggests adding the line

pinentry-program /usr/local/bin/pinentry-mac

to gpg-agent.conf. This is the wrong path for those who installed pinentry-mac as an arm binary using brew (on apple silicon).
Steps To Reproduce

Install gopass as suggested in setup.md, including running echo "pinentry-program /usr/local/bin/pinentry-mac" >> ~/.gnupg/gpg-agent.conf.
Clone a password store.
Try to decrypt some password by running gopass show SECRET.
You should get gpg: public key decryption failed: No pinentry

Expected behavior
setup.md should suggest adding the correct path to pinentry-mac, either by asking the user to run which pinentry-mac or by specifying /opt/homebrew/bin/pinentry-mac for apple silicon users.
Environment

OS: Mac OS X Monterey
OS version: 12.0.1
gopass Version: 1.12.8
Installation method: brew

I should get my hands on Apple Silicon for the first time soon. I'll try to reproduce while I set up gopass and update the instructions accordingly.


name tag only on nodes

A user can add a point with only a name= tag. iD should not allow saving of a point with only a name tag.
Currently if a user adds a point, the last feature shown in the list is Point. When selected the user is given a text box to name the point. Additional tags can be added but I'm seeing users only add the name tag.
Example of a name only tag http://www.openstreetmap.org/node/4080838264
(The user has been contacted to fix.)

That's a good point.. We have a validation to warn users if they have left a feature untagged, but this check should exclude the name tag.


Improve database existingSecret functionality

The current existingSecret options is not great. It forces you to create a secret with the full database URI including host and credentials.
I think the chart should support passing each param separately.
Ideal format (taken from bitnami/keycloak)
externalDatabase:
  host: tools-pg
  user: bn_keycloak
  database: bitnami_keycloak
  existingSecret: bn-keycloak.tools-pg.credentials.postgresql.acid.zalan.do
  existingSecretUserKey: username
  existingSecretPasswordKey: password

The big benefit is that i can re-use the generated secret from posgres operator very easily and in current setup i have to create a new secret with full DB url which is not great. It also does not allow me to take advantage of automatic credential rotation.
current setup:
database:
  type: postgresql
  existingSecret: vaultwarden-pg
  existingSecretKey: uri

proposed setupp:
database:
  type: postgresql
  existingSecret: vaultwarden-pg
  host: tools-pg
  user: bn_keycloak
  database: bitnami_keycloak
  existingSecret: bn-keycloak.tools-pg.credentials.postgresql.acid.zalan.do
  existingSecretUserKey: username
  existingSecretPasswordKey: password
  # existingSecretKey: uri

If existingSecretKey is set then use it, else use individual settings.

I also would be very happy to use this feature in combination with the postresql operator. I spent a couple of hours trying to figure out how to get this to work. I'll submit a PR soon with technical details and publish a patched chart to immediatelly use. Then let's discuss how and if we can get this merged.


Fix tests marked RunnableOnService that aren't

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace "<Jira issue #>" in the title with the actual Jira issue
number, if there is one.
[x] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Tests must make exclusively assertions about the contents of
PCollections to be marked RunnableOnService. Tests making assertions
about the client result cannot be ported between runners and do not meet
this requirement.
RunnableOnService tests that expect a specific exception as a result of
the pipeline failing are not portable. Remove the RunnableOnService
category from DoFnTest, DoFnWithContextTest, and WithTimestampTest tests
which expect exceptions.

This should fix the RunnableOnService Jenkins failures as seen in Jenkins RunnableOnService #24
There's no obvious JIRA issue associated with those failures.

R: @davorbonaci

LGTM.
These are runner-specific now. We should revert it once we can get runners to behave similarly.

Reverted RunnableOnService.java


Does Azure Have Access to Data in PaaS SQL

The vulnerability assessment is attractive feature, but my organization would like to understand once turn this feature on, does it mean MS Azure now is able to access my data in the database?
[Enter feedback here]

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

ID: 65b5f76e-bbb3-b97c-bfb5-63788db27e26
Version Independent ID: a33d089e-16dd-7223-288f-fbb5c8784c99
Content: SQL Vulnerability Assessment rules reference guide - Azure SQL Database
Content Source: articles/azure-sql/database/sql-database-vulnerability-assessment-rules.md
Service: sql-db-mi
Sub-service: security
GitHub Login: @barmichal
Microsoft Alias: mibar

@RonnieQuan Thank you for your feedback! We will review and update as appropriate.

@RonnieQuan We are going ahead and assigning this case to our author for further review.
@barmichal Please check the question from the Cx and help with the same. If this has to be shifted to monitoring team, please convey that as well.

@NavtejSaini-MSFT  Any update on this issue?

Any update on this issue?

Any update on this issue?

Any update on this issue?

Hi @RonnieQuan ,
Thank you so much for contacting Microsoft and our apologies for the delay in response! We beg for your patience as we're working through a long backlog of Git Issues.
Let me see what I can do to get this addressed for you.
Thanks!
Masha from the SQL Docs team
#assign:MashaMSFT

Hi @RonnieQuan,
Thank you for your question.
When you turn any capability within Azure (not only SQL vulnerability assessment), Microsoft does not get any access on your data. In case Microsoft needs to access to your data for any purpose, we are plighted to get your explicit consent before we initiate any kind of manipulation.
In the case of SQL vulnerability assessment, we do not have access to your data, and the scan results are stored in your own storage account.
Best,
D.

#please-close


🐛 [Bug] Could not implicitly convert NumPy data type: i64 to TensorRT

Bug Description
TensorRT engine produces error when ran on Jetson for fcn_resnet model. However, it does not produce error when ran on desktop.
Dynamo frontend is used for creating a TensorRT engine.
Error : [TRT] [E] Could not implicitly convert NumPy data type: i64 to TensorRT.
To Reproduce
Steps to reproduce the behavior:
The following are relevant code for loading and converting to a TensorRT model.
input_data = torch.randn(args.input_shape, device=DEVICE)
model = torch.hub.load("pytorch/vision", 'fcn_resnet50', pretrained=True)
model.eval().to(DEVICE)

input_data = input_data.to(torch.float16)
model = model.to(torch.float16)

exp_program = torch.export.export(model, tuple([input_data]))
model = torch_tensorrt.dynamo.compile(
    exported_program=exp_program,
    inputs=[input_data],
    min_block_size=args.min_block_size,
    optimization_level=args.optimization_level,
    enabled_precisions={dtype},
    # Set to True for verbose output
    # NOTE: Performance Regression when rich library is available
    # https://github.com/pytorch/TensorRT/issues/3215
    debug=True,
    # Setting it to True returns PythonTorchTensorRTModule which has different profiling approach
    use_python_runtime=True,
)

for _ in range(100):
    _ = model(input)

Expected behavior

Environment

Build information about Torch-TensorRT can be found by turning on debug messages

Jetson Orion Developer Kit

Torch-TensorRT Version (e.g. 1.0.0):  2.4.0a0
PyTorch Version (e.g. 1.0):
CPU Architecture: aarch64
OS (e.g., Linux): Ubuntu 22.04
How you installed PyTorch (conda, pip, libtorch, source): nvcr.io/nvidia/pytorch:24.06-py3-igpu
Build command you used (if compiling from source):
Are you using local sources or building from archives: nvcr.io/nvidia/pytorch:24.06-py3-igpu
Python version: 3.10.12
CUDA version: 12.6.68
GPU models and configuration:
Any other relevant information: Jetpack 6.1 L4T 36.4.0

Additional context
Here's a screenshot for relevant comparison
Desktop:

Jetson:

What version of TensorRT are you using on jetson vs x86?

What version of TensorRT are you using on jetson vs x86?

On jetson I am using 24.06 PyTorch igpu image that comes with TensorRT <IP_ADDRESS>
On dekstop, the TensorRT version 10.1.0 is used.

I think this issue might be related to this PR : https://github.com/pytorch/TensorRT/pull/3258.
I am facing same issue with GoogleNet model : https://github.com/pytorch/TensorRT/issues/3185
I guess not all models are supported via Torch-TensorRT library yet!

@apbose can you look at this bug?

Overall my inclination is that there is version mismatch somewhere since this passes on x86 and there isn't any aarch64 specific behavior

Also you can try out the nightly or latest stable version instead of 2.4.0a0


MS2109: Detecting input signal

First of all a huge thanks for this project. Without it, my project USBKVM wouldn't have been possible in its current form.
On my board, I have an LED next to HDMI connector that should light up if there's an input signal. I've connected both of the MS2109's GPIOs to my MCU which in turn controls the LED.
By default, GPIO0 is active (low) when the UVC device is open which isn't all that useful for my application. Is there a way to patch the configuration/firmware in the EEPROM to get it to be active if there's an input signal?
I've tried reading the address mentioned in https://github.com/BertoldVdb/ms-tools/issues/7#issuecomment-1431494947 but for me, it only reads 1 briefly when plugging in an HDMI source.

Try the LSB of 0xc77a or 0xfa8c (LSB of 0xfa8c is copied into 0xc77a


minor update

It's fine by me :) Let's see how this works. (Maybe later optionally add a bit more 'open source' in the text below across the page.)


Admin Account / Password

Is there a reason why you include your admin.yaml file in this repository?
It seems like it is not delivered with the downloadable archive on the grav website, but if people use the repository as a base for some reason, they install credentials that a decent password tool cracks in less than 2 seconds.

I believe this was committed by mistake, thanks for the ping

Fixed in repo


Any chance for a Vim plugin?

This project looks perfect for answering the "Why is my data this shape?" question. Any plans for Vim users, or making the project easily consumable by other plugin writers?
Thanks.

@jeaye I would love for there to be a vim plugin! I'm just not the person to write it. However, if someone were interested in taking that on, I'd be happy to provide guidance, docs or anything like that.

I think the important thing would be to document the nrepl operations, and how to interact at that level. This should allow vim developers to build on nrepl abstractions that vim plugins like fireplace/acid provide.

@SevereOverfl0w I'll put this on my near-term todo list. thanks

I'll just add: would-be plugin authors are welcome to contact me about ways to improve the nrepl interface. I built it around exactly what I needed to accomplished what I wanted for emacs, so it might not be as well suited for other editors.

https://github.com/bpiel/sayid/issues/8

https://github.com/bpiel/sayid/issues/13

I've created a proof of concept for a Vim plugin.
https://github.com/arsenerei/vim-sayid
I'll be adding more to it, but here's a preview.

Badass. Thanks for putting in the work! This is absolutely something I'd use, especially since I'm already in bed with vim-fireplace.

I've added the following to vim-sayid:

Persistent Sayid buffer
Buffer commands for exploration
Syntax highlighting

The plugin feels usuable at this point, so I would certainly appreciate some feedback. :)


Checking if there any missing flows to be captured by the collector

Hello there,
I am using Goflow2 right now for PoC and also I have a netflow collector that already exists in my environment.
Actually, I have a doubt or in other words how can I make sure that Goflow collector actually captures all the flows exported from the collector? How can I check if there any missing flows? When I check for example the number of flows in a time window of 5 minutes in Clickhouse, actually I find a difference when aggregating the total number of flows received between Goflow and the collector I have in my environment. So from where we can start to investigate more in that case cause I believe that the flows are the same which are exported from the router ( flow exporter) so what are the diffrences/configurations that can be configured from the collector side?
Also, To have more accurate results, the CacheActiveTout in the exporter is configured to be 300 seconds to avoid cache saturation and loss of data, so is there a corresponding conf. from the collector side(goflow) to be done ?

Hello,
Thank you for evaluating GoFlow2.
Please specify which version you are using. There is a bug in v2.0.0 but fixed in main.
You can check the number of flows received using the Prometheus endpoint.
How many flows per second are you emitting?
I'm missing a lot of information on your environment to provide guidance. Have a look at the performance doc too.

Actually I am using now goflow v2, when running the containers the goflow2 can't start as it cant find format=bin and its logs are :
2023-12-27 08:59:49 time="2023-12-27T06:59:49Z" level=fatal msg="Format bin not found"
2023-12-27T06:59:50.792073374Z time="2023-12-27T06:59:50Z" level=fatal msg="Format bin not found"
2023-12-27T06:59:52.514715087Z time="2023-12-27T06:59:52Z" level=fatal msg="Format bin not found"
2023-12-27T06:59:54.731755935Z time="2023-12-27T06:59:54Z" level=fatal msg="Format bin not found"
2023-12-27T06:59:56.286318676Z time="2023-12-27T06:59:56Z" level=fatal msg="Format bin not found"
2023-12-27T06:59:58.926916197Z time="2023-12-27T06:59:58Z" level=fatal msg="Format bin not found"
2023-12-27T07:00:02.831912213Z time="2023-12-27T07:00:02Z" level=fatal msg="Format bin not found"
While When I comment this line in the docker-compose file , it starts but have a problem in consuming the flows topic in the clickhouse.

Can you give me the whole command line and more information about your environment (docker versions, etc).

Docker Version:
Client:
Cloud integration: v1.0.35+desktop.5
Version:           24.0.6
API version:       1.43
Go version:        go1.20.7
Git commit:        ed223bc
Built:             Mon Sep  4 12:32:48 2023
OS/Arch:           windows/amd64
Context:           default
Server: Docker Desktop 4.24.0 (122432)
Engine:
Version:          24.0.6
API version:      1.43 (minimum version 1.12)
Go version:       go1.20.7
Git commit:       1a79695
Built:            Mon Sep  4 12:32:16 2023
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          1.6.22
GitCommit:        8165feabfdfe38c65b599c4993d227328c231fca
runc:
Version:          1.1.8
GitCommit:        v1.1.8-0-g82f18fe
docker-init:
Version:          0.19.0
GitCommit:        de40ad0
The cmd in the goflow2 container :
goflow2:
build:
context: ../../
dockerfile: Dockerfile
args:
VERSION: compose
LDFLAGS: -X main.version=compose
image: netsampler/goflow2
depends_on:
- kafka
ports:
- 8080:8080
- 6343:6343/udp
- 7779:2055/udp
restart: always
command:
- -transport.kafka.brokers=<IP_ADDRESS>:6011
- -transport=kafka
- -transport.kafka.topic=flows
- -format=bin

Can you run docker images?
Then make sure you have the latest version of netsampler/goflow2 by doing docker pull netsampler/goflow2 or adding :e4a14c2 after the image name:
image: netsampler/goflow2:e4a14c2

It solved the issue !! But there is one last problem regarding the format.
Using a dummy netflow generator for testing purposes and here are the format of the flows inside the clickhouse:

and here are the format inside the flows topic of Kafka :

What am I missing? I am using the ' Protobuf ' format in create.sh of clickhouse

For ClickHouse: some data is stored as raw binary for performance. I don't know dbweaver but using direct SQL, the IP addresses in a text form can be obtained using functions like the following:
SELECT if(etype = 0x800, IPv4NumToString(reinterpretAsUInt32(substring(reverse(src_addr), 13,4))), IPv6NumToString(src_addr)) as srcip

I would also recommend to avoid passing queries to flows since it's a "transition" table before flows_raw. The data that is queried will be removed and not inserted.
For Kafka: the data is serialized as protobuf which is a binary format. You need other tools to explore this.
This won't be compatible with ClickHouse without modifications, but if you change -format=json or -format=text instead of -format=bin, you'll be able to have a human readable message inside Kafka, albeit a lower performance.

Yes It is readable but my issue that when I choose -format=json or -format=text , Nothing is consumed in the clickhouse and the db is empty.

Yes: it's on purpose to optimize query performance and storage. Other behaviors won't be supported.
If you wish to use JSON, you need to edit the various flows_* tables from a Protobuf format into JSON and make sure the names are correctly mapped from the JSON payload into the columns.
This will also break the Grafana dashboards shipping within the compose.

Closing as stale


How to merge html and js

webpack4, How to merge html and js. Not a reference path

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template and reopen, or open a new issue.


Fix deprecation in dsl tut

This should unbreak master from the last merge.

master is broken anyway because of deprecation, and you can see the trainwreck behind it.  This is is now broken by a latent issue captured in #1891.
I think we should merge this and start clearing out the above linked tickets.  Travis can't get any redder.
Sorry, everyone.  I moved fast and broke things.


Using an event callback parameter with @bind:after isn't supported.

Description
There's a statement on the page:

Using an event callback parameter ([Parameter] public EventCallback<string> ValueChanged { get; set; }) with @bind:after isn't supported.

And it's very confusing.
EventCallback is something that is exposed by the component itself, if it needs to notify parent about the changes, but bind:after is a directive used by the parent component. That's why I do not get the statement. Could you provide some code example, please?
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/components/data-binding?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/data-binding.md
Document ID
3f912dfc-5ba5-6c6c-ba93-1ae78508a5cc
Article author
guardrex

Hello @voroninp ... I'll take a look, but I'm buried in .NET 8 Blazor work for the next two weeks. If you can't wait for an answer, open an issue on the PU repo to ask them what the remark means ...
https://github.com/dotnet/aspnetcore/issues
Please add ...
cc: @guardrex https://github.com/dotnet/AspNetCore.Docs/issues/30960

... to the bottom of your opening comment so that I can follow along. If they provide the answer, I can quickly shoot it in without disturbing my push to get the .NET 8 Blazor docs finished in time.

I'll include that answer in the docs ... but can't do it at the moment. I'm BURIED in 8.0 work right now ⛰⛏😩.
Leave this issue open. It will automatically close later when my PR merges.

@guardrex , not the problem at all. Thanks for the very much awaited update for .NET 8

Also, as a proposal. Maybe the order of binding and event handling sections should be reversed because binding is based on the events.

Looking at this now ...
I was only going to cross-link from this remark to the event handling doc, BUT I can see that the event handling doc only has two event handling conceptual examples that use bound data (i.e., @bind in examples). Both of those examples can be refactored to avoid bound data (🔪@bind) and still make the event handling concepts clear. Therefore, I like your idea of re-ordering the articles so that the event handling article comes first in ToC. Then, I'll still place a cross-link on this remark referring to the EventCallback/EventCallback<T> guidance of the event handling article.


Repackage to latest boilerplate

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

13 of 13 (100.0%)  changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 98.945%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
375

Relevant Lines:
379

💛  - Coveralls


sfunc is not a function

Hello,
I'm running into this issue when running vite build and was hoping you can shed some light on it:
node_modules/vite-plugin-vsharp/d/vsharp.js:225
  (0, _sharp["default"])(img)[sfunc](opts[extname]).toBuffer(function (err, buffer, info) {
                                    ^

TypeError: (0 , _sharp.default)(...)[sfunc] is not a function
    at vsharpIt (node_modules/vite-plugin-vsharp/d/vsharp.js:225:37)
    at node_modules/vite-plugin-vsharp/d/vsharp.js:139:13
    at Array.forEach (<anonymous>)
    at doSharp (node_modules/vite-plugin-vsharp/d/vsharp.js:136:25)
    at node_modules/vite-plugin-vsharp/d/vsharp.js:144:11
    at next (node_modules/vite-plugin-vsharp/d/vsharp.js:71:25)
    at node_modules/vite-plugin-vsharp/d/vsharp.js:82:11
    at FSReqCallback.oncomplete (node:fs:205:5)

Node.js v18.3.0

Thank you so much for your work on this plugin.

While further investigating, I believe it's related to how it's picking up the files on my project, which is Laravel based.
I'll keep updating this thread with my findings

While messing with this, I figured out that this is running before the static images are copied into the out folder, meaning:
I'm using a plugin viteStaticCopy to copy some images from one folder into my projects public folder so they are accessible to the application, however this plugin runs at the same time as viteStaticCopy which makes things hard because the files have are not there yet.
I changed the plugin to read a list of files from the original folder where they will be copied from, now the problem is not all files have been copied and as such the plugin breaks with a file not found.
Not sure if I explained it proper, but basically even after adding the enforce: 'post' to the plugin it seems to be just running alongside the others.
Any pointers would be appreciated, I will continue to investigate but would really appreciate some feedback when you have the time.
Thanks

@nsouto hello there, sorry for the slow response. having read about your thread i realize that this might not be the problem of the plugin.
first, you can try to add enforce: pre to the copy plugin and enforce: post to the vsharp plugin at the same time, if that still doesn't work, i recommend you to use other tools (like Gulp) to integrate the workflow of your project.
here is a short example that might help you a little bit.

install gulp with npm

npm i gulp -D

add gulpfile.js to the root of your project

const gulp = require('gulp')
const exec = require('child_process').exec

function copyImages() {
  let glob = ['public/images', 'someOtherFolder/blahblah.jpg']
  return gulp.src(glob)
    .pipe(gulp.dest('dist/images'))
}

function viteBuild(cb) {
  exec('npx vite build', function (err, stdout, stderr) {
    console.log(stdout)
    console.log(stderr)
    cb(err)
  })
}

exports.build = gulp.series(copyImages, viteBuild)

modify scripts in your package.json

 "scripts": {
+  "build": "gulp build"
-  "build": "vite build"
 }

don't forget to disable the copy plugin in vite.config.js, now try npm run build again.

good luck man!😉

@nsouto. I'm also using Vite to copy static assets from /resources/img in Laravel project. I've solved the issue with this config option:
    plugins: [
        laravel({
            input: ['resources/css/app.css', 'resources/js/app.js'],
            refresh: true,
        }),
        vsharp({
        vsharp({
+           excludePublic: ["public/build/*"],
        }),
    ],


[WIP] deps: Bump com_google_protobuf -> 3.19.3

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue] Fix #19497
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

requires patch update

/lgtm deps


[Outlook] (office2019) Distinguish between types of one-time purchase…

… (#1818)

[Outlook] (office 2019) Distinguish between types of one-time purchase

Update to retail

Docs Build status updates of commit 58d819e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/requirement-sets/outlook-api-requirement-sets.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Extend configuration to support metal-stack cloud provider.

How to categorize this PR?

/area networking
/kind enhancement
What this PR does / why we need it:
This PR adds few more fields required for the cilium extension to integrate well with metal-stack. These are:

IPv4NativeRoutingCIDR: Enables native routing mode in order to leverage routing capabilities of our network setup without the need of tunneling
BPFLoadBalancingMode: Allows configuring DSR mode, which has some attractive traits like preserving original source IPs from external traffic and avoiding an extra hop for the reply to external requests
Devices: Necessary due to our BGP unnumbered approach where the node IP is sitting on the lo device for peering with leaf switches
MTU: Falsely determined when it cannot be specified explicitly for the setup as described for field "Devices"

The PR also adds PSPs for Hubble because these are missing for some reason.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

Thank you @Gerrit91 for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below.

I have now run this version of the extension in the provider-local setup. It's working without any hacks! To test the changes further, I also modified the MTU, which was working too.
It not possible for me to test this build on our real Gardener landscape, which is still on g/g v1.42 and therefore incompatible with the current head of this extension. However, the PR is based on a branch that we made on an earlier version of this extension, which I verified is working: https://github.com/metal-stack/gardener-extension-networking-cilium/pull/1

Thank you for the PR, I tested it on a gardener cluster and it worked well! Can you please also run make generate and add the generated files.

Hey @DockToFuture, thanks for taking a look. Sorry for the delay, I am now back from vacation so I can react faster now to comments. I rebased this pull request to latest master, the generated files did not really differ from what was there before though.

When I run make generate I get another chart value for example/controller-registration.yaml. The rest is the same.

/test

Can you update the example/controller-registration.yaml @Gerrit91 so that we get the PR merged?

Hey.
I am a bit puzzled because my make generate creates a different controller registration and claims this one to be correct even when running make verify-extended. I even unpacked the helm chart ($chart | base64 -d | gzip -d | tar xf -) and did a recursive directory diff. There was no difference in the chart files.
Rebased the PR now and just removed the changed controller-registration.yaml.
Do you have any idea what could cause this behavior? I am running on Ubuntu 22.04, go 1.19, removed the hack/tools/bin folder to ensure dependencies are correct... :(

/test

/lgtm


fix csv format

[Refactor]: Changed output formatters to be classes
Fixed CSV output format repeating headers for each row

@nogatzur Please see the last commit, I reverted my change to classes to keep it as close as possible to the original code so that I can merge the bug fix. Further refactors can be done at your discretion.


Cross-module definition doesn't work

This happens because the framework path for the project is not getting passed to the swift compiler.
$ swift --help
...
  -F <value>              Add directory to framework search path
...

With -F, cursorinfo across modules works (I'm on bebf0d1):
cat <<EOF | sourcekitd-repl
{
  key.request: source.request.cursorinfo,
  key.compilerargs: [
    "-sdk",
    "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk",
    "-F",
    "/Users/chrismwendt/Library/Developer/Xcode/DerivedData/langserver-swift-decoewqzatmxuugoqscoirgsoekn/Build/Products/Debug",
    "/Users/chrismwendt/langserver-swift/Sources/LanguageServer/main.swift",
  ],
  key.offset: 368,
  key.sourcefile: "/Users/chrismwendt/langserver-swift/Sources/LanguageServer/main.swift",
}
EOF

And returns:
{
  key.kind: source.lang.swift.ref.class,
  key.name: "RequestBuffer",
  key.usr: "s:12BaseProtocol13RequestBufferC",
  key.typename: "RequestBuffer.Type",
  key.annotated_decl: "<Declaration>class RequestBuffer</Declaration>",
  key.fully_annotated_decl: "<decl.class><syntaxtype.keyword>class</syntaxtype.keyword> <decl.name>RequestBuffer</decl.name></decl.class>",
  key.typeusr: "_T012BaseProtocol13RequestBufferCmD",
  key.modulename: "BaseProtocol"
}

The correct path can be obtained by running this build command (similar to the one listed in the README:
$ xcodebuild -project langserver-swift.xcodeproj -scheme langserver-swift -showBuildSettings | grep "TARGET_BUILD_DIR"
   TARGET_BUILD_DIR = /Users/chrismwendt/Library/Developer/Xcode/DerivedData/langserver-swift-decoewqzatmxuugoqscoirgsoekn/Build/Products/Debug

The -scheme langserver-swift can be obtained with swift package dump-package | jq -r .name, but it's probably not safe to assume that there is a scheme with the same name as the package.
I'm thinking about running those commands and passing it to the compiler at https://github.com/chrismwendt/langserver-swift/blob/bebf0d10c51c8c0fa71d557b4fcf90fb92e64615/Sources/LanguageServerProtocol/Types/Server.swift#L179
@RLovelett Does this approach make sense?

Hmm, the USR s:12BaseProtocol13RequestBufferC from main.swift doesn't match anything:
$ sourcekitten index --file /Users/chrismwendt/langserver-swift/Sources/BaseProtocol/Types/RequestBuffer.swift --compilerargs -- /Users/chrismwendt/langserver-swift/Sources/BaseProtocol/Types/RequestBuffer.swift
...
"key.usr" : "s:13RequestBufferAAC"
...

It looks like all the USRs in RequestBuffer.swift begin with s:13 instead of s:12. Are they not supposed to match? How might I stitch these together?

The correct path can be obtained by running this build command (similar to the one listed in the README

Those paths are meant to be generated by SwiftPM. That is the whole point of including SwiftPM as a dependency. That it will know how to properly build those. So the fix for this should come from SwiftPM. Or that is my off-the-cuff gut response.
I would first look through the .build directory and see if it contains the path you are looking for first. If it's in there then we can work backwards on how to extract that info from SwiftPM. If it is not, then we'll have to figure out how to coerce SwiftPM to build that info for us.

It looks like all the USRs in RequestBuffer.swift begin with s:13 instead of s:12. Are they not supposed to match? How might I stitch these together?

So when you compile main.swift are you using the same module that you are sending to the index?
Because they should match. If they don't match I don't know how you would be able to reliably match them. The only thing that feels like might be true is that if you are not sending the exact same compiler args for  then it might not end up with the same USR because it sees it as a different module and tries to de-conflict it with a new USR.
Another way that I've thought this might have to work is that you make use of Module Interface Generation. Basically find the module that defines the type in main.swift. Then generate the interface which will contain the USR local to the module. Then use find_usr to get the definition.

So when you compile main.swift are you using the same module that you are sending to the index?

Ah-hah! I just had to pass ALL of the Swift files under Sources/ in the key.compilerargs array.
Now the USRs are the same and -F is unnecessary! 🎉  🎊
Do you have an example of source.request.editor.open.interface and find_usr working? I can't figure out what to specify for key.modulename - I keep getting the error "Could not load module".


refactor(driver): fix warnings by 'cargo clippy' for driver

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

issue #191
2. What is the scope of this PR (e.g. component or file name):

KCLVM/driver

Is there any IRC channel like slack or something? @Peefy

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 87.787%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2293

Relevant Lines:
2612

💛  - Coveralls

Dont merge it yet, there is an issue in the commit.

Is there any IRC channel like slack or something? @Peefy

See https://github.com/kcl-lang/community to join our slack. Welcome!


Update event handlers if changed

If value property has changed the framework will re-set it's value to the Lumin RT node. This is not happening for event handlers !  Currently, the framework does not replace the event handlers.
The framework needs to unsubscribe the previous callback and subscribe the new one.

MXSCOMP-226


[TC-0059] Backend Auth + Roles Check

Checking auth token on all routes that are not annotated with the public decorator
Validating auth token
Checking Reflector to see if route is annotated with a Roles decorator
Validating user assigned role if the current route requires a role

changing branches in order to link to jira


Update introduction.rst

Bad Source Naming
Incorrect: ArXiV
Correct: arXiv

Per the README we don't accept small contributions like this.
Thanks.


Video block

When trying to save an edited video block you get the error An invalid form control with name='width' is not focusable.
C5 version 8.2.1

Need to have this verified on the develop branch – I can't seem to do it

This problem occurs when you want to edit the blok and 'Set Max Width' is not checked. The 'width' input is hidden and can not be focused because of this.
How to reproduce in Chrome:

Add a new instance of the blok to the page
Keep the Video Size on 'Default Video Dimensions'
Save the blok and publish the page
Go to edit mode
Edit the block
Save the block

The following error is visible in the console: 'An invalid form control with name='width' is not focusable'.
I have created a fix for this issue: #6049


Don't redirect to home page on empty CMSEditLink

CMSEditLink can sometimes be empty. In this case, clicking on this will take the user out of the CMS and to their site's home page (<a href="" />). This took a lot of tracking down. =(

Does it make sense to keep the <a> without the href attribute? Should the logic be around the whole link?

I think it does. An anchor isn't necessarily a link, although that is the most common use case.
E.g. removing it (or changing the tag type) could have wider impact with CSS or bound JS for example. Things that are otherwise invisible in this PR.

Ok, it makes sense, didn't know it was valid, but TIL https://stackoverflow.com/a/19167175


nextinspace: 1.0.6 -> 2.0.3

Motivation for this change
https://github.com/not-stirred/nextinspace/releases
Things done

Built on platform(s)

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

1 package built:

nextinspace


fix: add aria hidden attribute to style tag

Add aria hidden attribute to style tag to avoid screen readers to read its content
fix #691

Thank you @froston


[Check ID] Downgrade com.google.fonts/check/caret_slope to WARN

Observed behaviour
We currently FAIL if the caret slope rise and run values are wrong for italic glyphs. But according to @vv-monsalve, no applications these days display a slanted cursor caret!
Expected behaviour
We shouldn't FAIL for non-problems.

If it is not a real problem, should we then deprecate the check?
Or would you prefer to keep it as a WARN? Any hope this will someday be supported at all?

It appears that some applications still support it.

After the latest tests I performed, it's not in use on Adobe apps, Pages, Libre Office in macOS.
Only Word seemed to be working ok with them.
@kenmcd what OS and app versions are these?

Or would you prefer to keep it as a WARN? Any hope this will someday be supported at all?

I would keep it as a WARN. Caret values are part of the hhea table from the OT spec, so they should be supported. However, multiple apps seem not to be using them to represent a slanted cursor.

@kenmcd what OS and app versions are these?

Word Office 2024 Preview on Windows 11 Pro 23H2
Microsoft® Word LTSC MSO (Version 2403 Build 16.0.17425.20176) 64-bit
Word Office 2019 on Windows 10 Pro 22H2
Microsoft® Word 2019 MSO (Version 2402 Build 16.0.17311.20000) 64-bit
I installed 2021 over 2019 and this is what it still says.
Affinity Publisher 2.4.1 on Windows 10 Pro 22H2


Display a message when there was no supported password reset method

Successfully fixed that issue. Will display error messages.


got run error message

Hi, I tried to clone your project so I can run it on my home server. My npm ver
I got following error. And nodejs version is v18.13.0.
`~/retropatcher# npm run dev

dev
next dev

sh: 1: next: not found`
BTW, the link (https://strt-slct.com/analogue-pocket-patches )in your retropatcher web is not reachable.
Thanks for creating the tool.

It works after I install next module with npm install next


Critical Cases Flag/Status

A Reviewer should be able to set a "critical" flag on a document after it has been approved/rejected.
This state marks studies which have been critical and can serve as examples for future reference.
This could be implemented with additional states that can be accessed after documents reached state 6 or 7. The documents should still be accessible in the normal lists and have their own filter group.

A temporary solution could be to take a note during the review process. In this case, it is already possible to find this document very easy by using the search bar. For better results, the reviewers could agree on special keyword, (e.g. CRITICAL) for tagging it.


Repeatable templates are inefficient with changes to observable lists

This issue was originally filed by @danschultz

When binding to an observable list with a repeatable template, it'll destroy and recreate all of the elements whenever the list changes. The template should be able to know which new elements to create, and which ones to remove based on the change events that are dispatched by the list.
What steps will clearly show the issue / need for enhancement?
See attached project.
What is the current output?
All elements are destroyed and recreated.
What would you like to see instead?
Smarter removals and insertions of elements based on list changes. The template should be able to know which elements to create, and which should be removed based on the change events that are dispatched by the list.
What version of the product are you using? On what operating system?
Polymer 0.10.0-pre.9
Dart Editor version 1.4.0.dev_02_02 (DEV)
Dart SDK version 1.4.0-dev.2.2

Attachment:
polymer_repeat_elements.zip (449.65 KB)

This issue has been moved to dart-lang/polymer-dart#494.


HexagonCellLayer documentation refers to a seemingly non-existent getRadius(d) method

The coverage section of the HexagonCellLayer documentation states that
The radius of hexagon is calculated by `coverage * getRadius(d)`

but as best I can tell it's simply coverage * radius.
It'd be very nice to have a hexagon-specific radius so that you could have e.g. radius represent counts and color represent rates (for instance to not give too much visual weight to sparsely populated areas) like ScatterplotLayer provides.
Is the documentation incorrect, is there work in that direction off on another branch, or am I just wrong and misreading things? Thanks!

You are right. It is a typo, radius is calculated by coverage * radius
We currently don't have plans to support getRadius. Have you thought about subclassing the hexagon layer and add another attributes?

@shaojingli we have a doc bug, would be good to get a PR up asap.


Submodule rapidjson

We should submodule it just like the other libraries we use.

be aware that, when the initial migration happened, I already tried this and found out that upstream is not designed be imported like that.
Could work around it by just manually setting paths and stuff.


Default boolean schema value is not shown in parameters dropdown

Current Behavior
Default boolean schema parameters don't say "default to: ..." in the parameters section.
Expected Behavior
Default boolean schema parameters should say "default to: ..." in the parameters section.
Steps to Reproduce
I have created a reproducable example using a random API I found:
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="utf-8" />
    <title>Boolean value test</title>
    <script<EMAIL_ADDRESS>    <link rel="stylesheet"<EMAIL_ADDRESS></head>
<body>
    <elements-api
      apiDescriptionUrl="https://api.apis.guru/v2/specs/amadeus.com/amadeus-hotel-search/3.0.8/swagger.json"
      router="hash"
      layout="sidebar"
    />
</body>
</html>

This is how it looks:

This endpoint has a "bestRateOnly" parameter. Here is the schema for it:
{
"default": true,
"description": "Used to return only the cheapest offer per hotel or all available offers.",
"in": "query",
"name": "bestRateOnly",
"required": false,
"type": "boolean"
}

Notice that its default value is set to true. While this is correctly displayed in the request query parameters here:

It does not say "defaults to: true" in the parameters section:

However,  it does say "defaults to: 1" e.g. for the "adults" parameter.
My question is: Is this behavior intentional? If not, is there a way to still show "defaults to: ..." in the Parameters section?

Is this behavior intentional? If not, is there a way to still show "defaults to: ..." in the Parameters section?
This is not intentional and would be a nice enhancement. Feel free to submit a PR if desired.


series_premiere BUG

2016-01-28 08:30 VERBOSE  series        premieren       Found different quality for The.Leftovers.S02E05.Kein.Platz.in.der.Herberge.German.DD51.Dubbed.DL.720p.HDTV.x264-TVS. Was 720p hdtv h264 dd5.1, overriding with 720p hdtv h264.
2016-01-28 08:30 CRITICAL task          premieren       BUG: Unhandled error in plugin series_premiere: 'latin-1' codec can't encode character u'\u2013' in position 23: ordinal not in range(256)
Traceback (most recent call last):
  File "/home/manuel/flexget-dev/flexget/task.py", line 438, in __run_plugin
    return method(*args, **kwargs)
  File "/home/manuel/flexget-dev/flexget/event.py", line 22, in __call__
    return self.func(*args, **kwargs)
  File "/home/manuel/flexget-dev/flexget/plugins/filter/series_premiere.py", line 62, in on_task_metainfo
    if guess_entry(entry, allow_seasonless=allow_seasonless, config=group_settings):
  File "/home/manuel/flexget-dev/flexget/plugins/metainfo/series.py", line 43, in guess_entry
    allow_seasonless=allow_seasonless)
  File "/home/manuel/flexget-dev/flexget/plugins/parsers/plugin_parsing.py", line 70, in parse_series
    return parser.parse_series(data, name=name, **kwargs)
  File "/home/manuel/flexget-dev/flexget/plugins/parsers/parser_guessit.py", line 315, in parse_series
    guess_result = guessit_api.guessit(data, options=guessit_options)
  File "/home/manuel/flexget-dev/local/lib/python2.7/site-packages/guessit/api.py", line 71, in guessit
    string = string.encode("latin-1")
UnicodeEncodeError: 'latin-1' codec can't encode character u'\u2013' in position 23: ordinal not in range(256)

seams to be a python problem
http://stackoverflow.com/questions/24358361/removing-u2018-and-u2019-character
how to fix this?

found it,it comes from rss
DC’s.Legends.of.Tomorrow.S01E01.Pilot.Part.1.720p.WEB-DL.DD5.1.H.264-LoT
http://serienjunkies.org/dcs-legends-of-tomorrow/dcs-legends-of-tomorrow-season-1-hdtv-1080p/

it seams to crash on u'\u2013'  u'\u2018'  u'\u2019' thats all crashs i have till now

Try not to use guessit, see if that works

this works, but didnt find much on imdb :D

Why imdb? Use tvmaze lookup

Didnt find anything too...
So, guessit is the Problem for latin Error?

No way tvmaze didn't find anything. And yeah, this is definitely a guessit issue but with all other issues it's experiencing currently, it's of no use to even try to address this.
The problem is that we have conflicting dependencies since we require v2 of guessit but subliminal requires a lower version so it downgrades it during installation.
Once this business is resolved it would be possible to address guessit issues again.
Until then I suggest we pick this up in the forums, tvmaze should work.

Ok,  hope for fast fix :)
Thx

https://github.com/guessit-io/guessit/issues/263#issuecomment-177129718

Requirements updated here too, thanks for reporting


Add script to get a refresh token from device code login

Add script to get a refresh token from device code login by Ioannis.


Fix global-node-modules RPM build

Port global-node-modules changes from Debian to RPM build

It might makes sense to add more detail to the commit message.  Something like: "upgrade global-node-modules to be inline with what we use in deb"


Radio commands

you can now pass to Radio a LabelCommand and InputCommand insted an only componetCommand

Coverage decreased (-0.1%) to 99.854% when pulling a2803f81c82a37e9ee2d1d655495f7043a348398 on nacho into 929c2c8429987966ae1f8041459f6be5b0435e34 on master.

Coverage decreased (-0.1%) to 99.854% when pulling a2803f81c82a37e9ee2d1d655495f7043a348398 on nacho into 929c2c8429987966ae1f8041459f6be5b0435e34 on master.


Markdown Support Feature

I also would like to add a Markdown support, which converts “.md” files to “.txt” file. Besides, i also add a syntax to implement a header line in your program

Thank you for your contribution!


Shortcut Guide for Alt key

Description of the new feature / enhancement
Enable Shortcut Guide for Alt key, which fetches hotkeys, and allows text customization to avoid overlap
Scenario when this would be used?
Customized Shortcut, or holding Windows Key
Supporting information
No response

is the ask to have you press only alt and have the guide show up?  /needinfo


Free support barycenter examples

Hello,
I have been working on your free support barycenter examples.
https://github.com/rflamary/POT/blob/master/examples/plot_free_support_barycenter.py
I went through the code and there is something which looks wrong to me. To plot your figure you used :
for (x_i, b_i) in zip(measures_locations, measures_weights):
color = np.random.randint(low=1, high=10 * N)
pl.scatter(x_i[:, 0], x_i[:, 1], s=b * 1000, label='input measure')
but I think it should be $s=b_i * 1000$ instead of $s=b * 1000$.
I can make a PR to correct it if it is a mistake.

ideed it looks fishy
Please correct in a PR if it looks better afterards ;)

Fixed in PR #98


Temp work around for uploader_id

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[x] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Ignores the uploader_id as a try-catch. YouTube probably changed something.
If we want the uploader_id from YouTube we will need to update this instead of just ignoring it.

This helps #31758

default=None already fixes the problem. This is not the failing code.


Improve Makefile.mingw

Adds conditionals and more env vars to accomodate the different mingw
environments out there.
For example, to cross-compile a debug build on Arch Linux you could execute:
CXX=/usr/bin/x86_64-w64-mingw32-g++ \
PKGCONFIG=x86_64-w64-mingw32-pkg-config \
DEBUG=1 make -e mingw

While on msys2 mingw-w64 you could just do:
make mingw STATIC=1
Switching to pkg-config makes static linking very easy here.
Defaults to release build (without DEBUG=1 set)
strips the binary like the linux makefile does.
Also fixed build, at least msys2 mingw needs the math define.

Hmm was there something useful in this? I just got back to look at this PR but you closed it.

Hm, yeah this had all the changes needed to build the project on msys2 distro of mingw on windows at the time. (would need to recompile to see if -D_USE_MATH_DEFINES flag is still needed.)
I've closed it since it wasn't merged for a while so it would need to be rebased on the new script, also for consistency you'd probably want to adapt all the other makefiles to use pkgconfig and the variables this has too.
It's a lot more adaptable for users wanting to build this imo since you don't have to patch the makefile just to change g++ to something else.

I made some fixes to the build process so that the mingw cross compilation
works, namely fabsf() was not defined when running on the CI box. Similarly
the makefile has a change so that I can switch the compiler(s) without a
modification. Maybe those fixes do the same thing as your changes?
to 22. elok. 2019 klo 23.25 Teteros<EMAIL_ADDRESS>kirjoitti:

Hm, yeah this had all the changes needed to build the project on msys2
distro of mingw on windows at the time. (would need to recompile to see if
-D_USE_MATH_DEFINES flag is still needed.)
I've closed it since it wasn't merged for a while so it would need to be
rebased on the new script, also for consistency you'd probably want to
adapt all the other makefiles to use pkgconfig and the variables this has
too.
It's a lot more adaptable for users wanting to build this imo since you
don't have to patch the makefile just to change g++ to something else.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kometbomb/prototracker-modular/pull/29?email_source=notifications&email_token=AAIIV2K6ITGNXZFYLCPCOZ3QF3YZHA5CNFSM4G44FCDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD46JFZQ#issuecomment-524063462,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIIV2PJG6S7LV6HZYBF5ADQF3YZHANCNFSM4G44FCDA
.