Scope function call differently from function definition

TS and JS Grammar Extension version:  0.0.18 / latest
This issue is likely Sublime Text specific, which relies on scoping to provide simple navigation in all languages:

Go to symbol: by listing all symbols with scopes like entity.name.function.ts
Go to definition: by finding a matching entity.name.function.ts for a variable.function.ts.

Because the TypeScript grammar labels function calls as entity.name.function.ts, the symbol list is polluted with invocations and Go To Definition does not know which entry to navigate to.
If no regressions are caused in themes / other editors, it would be great if Sublime's guidelines could be used: (from https://www.sublimetext.com/docs/3/scope_naming.html#variable)

Function and method names should be scoped using the following, but only when they are being invoked. When defined, they should use entity.name.function.

variable.function

Code
function myFunc() {
}

myFunc();
myFunc();
myFunc();

Results
Go to definition hover:

Go to symbol:
I was able to fix the symptoms by changing to "variable.function.ts" in the function-call matcher at https://github.com/Microsoft/TypeScript-TmLanguage/blob/master/TypeScript.tmLanguage#L3791
The syntax did use variable.function before, but it was changed in https://github.com/Microsoft/TypeScript-TmLanguage/pull/270/commits/55c8c9e50df3fea842bb36cb6e1e4b4bcfddb507 , perhaps in response to https://github.com/Microsoft/TypeScript-TmLanguage/issues/72.

Function calls now have 'meta.function-call' scope by f2cdd8b and that should help with the themes. Unless there is absolute need I don't think we can change the scope to variable.function as that doesn't seem to be common use (eg. look at the grammar at atom/language-javascript )

Thanks for responding - is there a plan to eventually remove entity.name.function.ts where meta.function-call was added?
As this is not a theming issue, there is no other workaround (short of maintaining a fork of this syntax) for ST3 users.

As such there is no plan to replace entity.name.function with variable.function (in function usage scenarios). I am adding @mjbvz and @aeschli to see what they think as they would need to make changes to vscode themes if we decide to change this.

Forgot to add that switching to variable.function is not really important, meta.function-call is fine (also commonly used in the ST3 syntaxes).
Several other of the VS Code syntaxes (go, python, ruby) only apply entity.name.function to function definitions, but several others (rust, c#) apply to invocations as well.

I think using entity.name.function only for function declarations is the right thing to do, but none of the grammars in our repo uses variable.function. I know that the Sublime doc lobbies for it but my guess it will result in a  lot of functions colored as variables. IMO most common is support.function even I understand that this is not 100% correct. meta.function-call is also used and I wouldn't not object to support it.

@sheetalkamat It doesn't help, because of vscode-textmate issue 52, which means you can't style entity.name.function - meta.function-call differently from entity.name.function.


Changed IM_USED (226) to CONFLICT (409)

Changed the HttpStatus code from IM_USED (226) which is a success message to CONFLICT which is an error status code (409)! This is send when an email is in use.

Thanks a lot @mjza


Unable to reproduce the paper results

Hi,
I'm currently trying to reproduce the results from a paper, but I've noticed some discrepancies with the paper's results.
For COCO:
CUDA_VISIBLE_DEVICES=0,1,2,3 vit=l task=ovd dataset=coco bash scripts/train.sh

[10/29 09:19:44 d2.evaluation.coco_evaluation]: target AP50: 0.4874418084766285
[10/29 09:19:44 d2.evaluation.coco_evaluation]: base AP50: 0.5425877731149755
[10/29 09:19:44 d2.evaluation.coco_evaluation]: all AP50: 0.5281649823634078

In this result, the "target AP" is only 0.487, which is not matching the paper's value of 50.0.
For LVIS:
CUDA_VISIBLE_DEVICES=4,5,6,7 vit=l task=ovd dataset=lvis bash scripts/train.sh

[10/30 05:21:34 d2.evaluation.lvis_evaluation]: Evaluation results for bbox:
|   AP   |  AP50  |  AP75  |  APs   |  APm   |  APl   |  APr   |  APc   |  APf   |
|:------:|:------:|:------:|:------:|:------:|:------:|:------:|:------:|:------:|
| 30.528 | 46.628 | 32.179 | 20.129 | 39.120 | 44.962 | 32.268 | 29.912 | 30.450 |

Here, the "APr" is only 32.2680, which does not match the paper's value of 34.3.
I used 4 GPUs for training purpose. Can you please help me identify what might be causing these discrepancies? Thank you.
Best,

In general, I suggest you evaluate more checkpoints and find the best one, because the performance of few-shot models usually vary a lot. Just taking the last epoch model may not guarantee the best performance on novel. This is also shown in the training log in the google drive. For the COCO one I could pretty much guarantee this.
For the LVIS, I remember the reported box APr is 32.6, so your number is pretty close. The mask APr is 34.3. So I suggest you could train a segmentation head on top of your existing model while freezing the box and cls branch (the fastest way).


Battery Drain

Hi
Using this function in iOS and it is working amazingly well. However we do have an issue with battery drain. Other than reducing the frequency of locations would it be feasible to adjust location frequency for example if the battery drops below say 20% or some customisable value so that it can be enabled or disabled in the config settings. I realise the plugin has battery management to a point, i.e sleeps when no movement, but maybe another option as suggested would be useful.
At 70mph I'm getting a reading about every 1 minute based on the following settings:-
logLevel: nativescript_background_geolocation_lt_1.BackgroundGeolocation.LOG_LEVEL_VERBOSE,             desiredAccuracy: nativescript_background_geolocation_lt_1.BackgroundGeolocation.DESIRED_ACCURACY_NAVIGATION,             distanceFilter: 75,             stopTimeout: 1,             elasticityMultiplier: 3,             autoSync: true,             stopOnTerminate: false,             startOnBoot: true,             foregroundService: true,             preventSuspend: true,             heartbeatInterval: 60*30,             httpRootProperty: 'location',

You’re free to execute #setConfig at any time.  The battery level is provided to each location emitted to location event.
Be aware that http requests are a big consumer of battery.


Added docs on gh-pages.

Signed-off-by: Pavel Kirilin<EMAIL_ADDRESS>

Codecov Report

Merging #40 (71b0680) into release/0.0.8 (0e8b7c6) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release/0.0.8      #40   +/-   ##
==============================================
  Coverage          65.83%   65.83%
==============================================
  Files                 35       35
  Lines               1039     1039
==============================================
  Hits                 684      684
  Misses               355      355

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


layers: Change include order of loader platform.

This fixes a bug where on Windows, windows.h would include
winsock.h before winsock2.h, causing numerous warnings.

+1

Cherry picked and pushed to master.


Adding a school

Here is the school website: collegekarr.fr (French)

@KiLOIG Pull request merged. Thank you!


 Error: Cannot find module 'nan'
npm ERR! Require stack:
npm ERR! - /home/gabriel/work/ghabxph/indy-sdk/wrappers/nodejs/[eval]
npm ERR!     at Function.Module._resolveFilename (node:internal/modules/cjs/loader:900:15)
npm ERR!     at Function.Module._load (node:internal/modules/cjs/loader:745:27)
npm ERR!     at Module.require (node:internal/modules/cjs/loader:972:19)
npm ERR!     at require (node:internal/modules/cjs/helpers:88:18)
npm ERR!     at [eval]:1:1
npm ERR!     at Script.runInThisContext (node:vm:132:18)
npm ERR!     at Object.runInThisContext (node:vm:309:38)
npm ERR!     at node:internal/process/execution:77:19
npm ERR!     at [eval]-wrapper:6:22
npm ERR!     at evalScript (node:internal/process/execution:76:60) {
npm ERR!   code: 'MODULE_NOT_FOUND',
npm ERR!   requireStack: [ '/home/gabriel/work/ghabxph/indy-sdk/wrappers/nodejs/[eval]' ]
npm ERR! }
npm ERR! gyp: Call to 'node -e "require('nan')"' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:327:20)
npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:277:12)
npm ERR! gyp ERR! System Linux 4.15.0-122-generic
npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd /home/gabriel/work/ghabxph/indy-sdk/wrappers/nodejs
npm ERR! gyp ERR! node -v v15.0.1
npm ERR! gyp ERR! node-gyp -v v7.1.2
npm ERR! gyp ERR! not ok

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/gabriel/.npm/_logs/2020-10-27T09_09_37_484Z-debug.log
➜  nodejs git:(gab/research) ✗

I will also try to solve this on the fly in my working repo: https://github.com/ghabxph/indy-sdk.git and share the fix.
My goal: My goal is to get start working with indy-sdk. I wish to be able to run the setup without issue and learn the API.

Hi everyone!
So, if you experience this kind of issue, solution is downgrade your node to version 12. I downgraded mine to node 12.19.0
My original node version is v15.
I am now going to close this ticket!
➜  nodejs git:(gab/research) ✗ npm i
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/cryptiles. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/boom. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.

><EMAIL_ADDRESS>install /home/gabriel/work/ghabxph/indy-sdk/docs/how-tos/write-did-and-query-verkey/nodejs/node_modules/indy-sdk
> node-gyp rebuild

make: Entering directory '/home/gabriel/work/ghabxph/indy-sdk/wrappers/nodejs/build'
make: Warning: File 'indynodejs.target.mk' has modification time 2.1 s in the future
  CXX(target) Release/obj.target/indynodejs/src/indy.o
../src/indy.cc: In static member function ‘static void IndyCallback::onMainLoopReentry(uv_async_t*)’:
../src/indy.cc:234:65: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(0, Nan::New<v8::Number>(icb->handle0));
                                                                 ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/indy.cc:235:65: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(1, Nan::New<v8::Number>(icb->u32int0));
                                                                 ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/indy.cc:243:52: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(0, toJSString(icb->str0));
                                                    ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/indy.cc:244:65: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(1, Nan::New<v8::Number>(icb->i64int0));
                                                                 ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/indy.cc:252:52: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(0, toJSString(icb->str0));
                                                    ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/indy.cc:253:97: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(1, Nan::NewBuffer(icb->buffer0data, icb->buffer0len).ToLocalChecked());
                                                                                ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/indy.cc:258:52: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(0, toJSString(icb->str0));
                                                    ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/indy.cc:259:52: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(1, toJSString(icb->str1));
                                                    ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/indy.cc:264:52: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(0, toJSString(icb->str0));
                                                    ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/indy.cc:265:52: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(1, toJSString(icb->str1));
                                                    ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/indy.cc:266:68: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(2, Nan::New<v8::Number>(icb->timestamp0));
                                                                    ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/indy.cc:271:52: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(0, toJSString(icb->str0));
                                                    ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/indy.cc:272:52: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(1, toJSString(icb->str1));
                                                    ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/indy.cc:273:52: warning: ‘bool v8::Object::Set(uint32_t, v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                 tuple->Set(2, toJSString(icb->str2));
                                                    ^
In file included from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8-internal.h:14:0,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:27,
                 from /home/gabriel/.cache/node-gyp/12.19.0/include/node/node.h:67,
                 from ../node_modules/nan/nan.h:56,
                 from ../src/indy.cc:4:
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8.h:3508:22: note: declared here
                 bool Set(uint32_t index, Local<Value> value));
                      ^
/home/gabriel/.cache/node-gyp/12.19.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
  SOLINK_MODULE(target) Release/obj.target/indynodejs.node
  COPY Release/indynodejs.node
make: warning:  Clock skew detected.  Your build may be incomplete.
make: Leaving directory '/home/gabriel/work/ghabxph/indy-sdk/wrappers/nodejs/build'
npm notice created a lockfile as package-lock.json. You should commit this file.
added 7 packages from 3 contributors and audited 109 packages in 9.844s

2 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

➜  nodejs git:(gab/research) ✗ node -v
v12.19.0


Promote std.process.Config.preExecFunction to a delegate

std.process.Config.preExecFunction is now a delegate instead of a function pointer, and can therefore capture an environment, for example:
import core.sys.linux.sys.prctl : PR_SET_PDEATHSIG, prctl;
import std.process : Config, execute;

void runProgram(int pdeathsig)
{
    execute(
        ["program"],
        config: Config(
            preExecFunction: () @trusted =>
                prctl(PR_SET_PDEATHSIG, pdeathsig, 0, 0, 0) != -1,
        ),
    );
}

Despite function pointers implicitly converting to delegates, this is a backwards-incompatible change, as user code may rely on the field being a function pointer. For example, code like the following will no longer compile:
import std.process : Config;

nothrow pure @nogc @safe
bool f() { return true; }

void example()
{
    auto config = Config(preExecFunction: &f);
    bool function() g = config.preExecFunction;
}

Despite function pointers implicitly converting to delegates

This is not true, you cannot assign a function pointer to a delegate.
If you are making a function literal, then yes, the compiler can make it a delegate (with a null context pointer). Otherwise, you need to use the function std.functional.toDelegate.

For Phobos v2, we want to avoid breaking changes, so I suggest keeping preExecFunction and adding preExecDelegate. It could be an error if both are set at the same time.

How about making it a delegate, and adding a setter taking a function and converting it to a delegate using std.functional.toDelegate?

@dkorpel How about calling both if both are set?
@CyberShadow There would also be a getter, what would it do?

How about calling both if both are set?

That also works

@chloekek Phobos 3 is under active development right now, that would be the ideal time to make the name change. We're not working on the process module yet, so we'll need to remember it for later.

@CyberShadow There would also be a getter, what would it do?

I am struggling for a use case where you will want to get the function pointer that you placed in std.process.Config. It might not be worth worrying about.

I added preExecDelegate as a separate field in the latest commit. If both
preExecFunction and preExecDelegate are given, both are called.


Using the sorting method leads to an analysis error in PyCharm

PyCharm does not see the asc and desc methods in model fields.
MyModel.timestamp.asc() displayed as error.
query.asc(MyModel.timestamp) looks fine.
Of course both methods work fine.

Yes, it's mentionned in the docs already but maybe it's not explicit that it might raise errors with pycharm as well.

Maybe changing this "note" to a warning could help ?


small simplifications, fix 404 jquery on login layout

Hi, I hope you don't mind this pull request. I'm trying to make pull request for hacktoberfest and I'm good in CI. Your project looks exactly the way I would start any project in CI.
Best regards,
arysom
p.s. default credentials don't seem to work in fresh installation on my localhost

Thanks for recommendation.........


servermaster(engine): add list masters/executors api

What problem does this PR solve?

Issue Number: ref https://github.com/pingcap/tiflow/issues/6867
What is changed and how it works?
Add an API to list masters and executors and expose it to gRPC gateway.
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

Codecov Report

Merging #6864 (4a5de0a) into master (435053b) will decrease coverage by 5.0536%.
The diff coverage is 50.0000%.

Flag
Coverage Δ

cdc
?

dm
51.9357% <50.0000%> (-0.0705%)
:arrow_down:

engine
62.6444% <ø> (-0.3820%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #6864        +/-   ##
================================================
- Coverage   59.4341%   54.3805%   -5.0537%
================================================
  Files           787        415       -372
  Lines         89743      51546     -38197
================================================
- Hits          53338      28031     -25307
+ Misses        31702      20817     -10885
+ Partials       4703       2698      -2005

rest LGTM.

/merge

/run-integration-test


Cannot get the initialization models

Hi, yjxiong,
I'm trying to reproduce the results of TSN.
But I failed to get the initialization models through "bash scripts/get_init_models.sh"
It showed the error message "404 Not Found".
Thanks.

Hi, the server is temporarily unavailable. The link should be back into service in a while.
Sorry for any inconvenience caused.

Hi @ks-mengxi ,
The server is back online. Please try again downloading the init models.

Hi yjxiong,
Thank you for your help.
I can download them now.


(Request) add epsxe

PackageIdentifier: epsxe
PackageVersion: 2.0.5
PackageLocale: en-US
Publisher: epsxe
PackageName: epsxe
License: open source
ShortDescription: Playstation emulator
Installers:
Architecture: x64
InstallerType: exe
InstallerUrl: http://www.epsxe.com/files/ePSXe205.zip
ManifestType: singleton
ManifestVersion: 1.0.0

This should be sent to the games bucket.


Elmish.Remoting version

Hello! I modified the project using Elmish.Remoting and simplified a lot of the communication between client and server. Could you create a branch where I can send a pull request?

cc @forki @alfonsogarciacaro

Hi @Nhowka! Sorry, I wasn't watching the repo and didn't get the notification. I just created the remoting branch. Can you please send the PR there? One question, what is the main difference between Elmish.Remoting and Fable.Remoting? Websockets vs HTTP communication?

Fable.Remoting creates a stateless bridge where you can call functions defined on a record through HTTP requests.
Elmish.Remoting is stateful, you can send messages to the client's elmish dispatch and have a similar update function on the server. It is more like an extension to elmish with a set of messages to be processed by the server and another for the client.
On this case, the state on the server is the user data. The token is used as another way of login if the communication is broken, but it's not transmitted again on every message. Stuff that was using promises  could be translated to server messages, without much need of changing the client messages that it would receive when the promise was fulfilled.

Awesome, thanks a lot for the explanation!


WELD-2115, refactor Weld API BOM, move dependencies to build aggregat…

…or, adjust api parent.

Removed parent from BOM, this required to add group ID
Properties and dep. management moved to build aggregator
BOM only retained API and SPI version(s)
Changed api/parent/pom.xml parent from BOM to build aggregator

BOM was used to get all the deps and their versions, since they are in build aggr. this had to be adjusted
rest of API depends on parent so it should be OK

Merged.


Fix fatal error of surrogte pair

Current implementation of surrogate pair doesn't take codepoints over U+20000 into consideration. This is invalid since original specification of UTF-16 is valid until U+10FFFF.

@feross LGTM

Thanks @hakatashi

Published as 3.5.2 – thanks!


TEIIDTOOLS-145 Adds delete confirmation dialog

Adds delete confirmation modal dialog to dataservice and datasource summary pages.  The user must confirm before the item is deleted.  This should help prevent accidental deletion if a user mistakenly clicks the delete action.

Made couple changes after discussing with Dan.  merging.


improvement grant executable permissions to all script files with shebang

Proposed changes
I think it's useful to ensure that all script files with shebang (#!) have executable permissions, allowing us to simply exec ./*.sh, and let the shebang determine the interpreter.

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.08 seconds
stream load tsv:          528 seconds loaded<PHONE_NUMBER>9 Bytes, about 135 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.0 seconds inserted 10000000 Rows, about 344K ops/s
storage size:<PHONE_NUMBER>8 Bytes


Fix: code quality issues

Description
Hi :wave: I work at DeepSource, I ran DeepSource analysis on the forked copy of this repo and found some interesting code quality issues in the codebase, opening this PR so you can assess if our platform is right and helpful for you.
Summary of changes

Replaced ternary syntax with if expression
Removed redundant None default
Used is to compare type of objects
Iterated dictionary directly
Removed unnecessary lambda expression
Refactored unnecessary else / elif when if block has a return statement
Refactored unnecessary else / elif when if block has a raise statement
Added .deepsource.toml to continuously analyze and detect code quality issues

This is interesting!
I've decided to apply a subset of these - the if and elif blocks are a deliberate style choice from me, because I find code clearer when it has if/else as opposed to relying on early termination. Likewise the iteration against .keys() on dictionaries.


NO JIRA: fix timeouts for evaluation of the SE Status

On Friday (December 2nd) the mocked tests start failling with:

I have measured it locally and that procedure takes 9.9 seconds.

Run no. 1: the issue is still valid :(

The issue is described here: https://issues.redhat.com/browse/MGDOBR-1302

After migration to REST API v2 the Smart Events UI :: Dev :: Quality Checks have started failing.


Change host on Gateway Objects has no effect

Istio 0.8 on Ubuntu running on IBM Cloud Private <IP_ADDRESS> with k8s 1.9.1
kubectl edit commands on Gateway Objects have no effect.
I have crated the gateway:
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: bookinfo-gateway
spec:
  selector:
    istio: ingressgateway # use istio default controller
  servers:
  - port:
      number: 80
      name: http
      protocol: HTTP
    hosts:
    - "*"

Then I edit the object with kubectl edit gateway bookinfo-gateway and change the hosts from "*" to "bookinfo.com".
But in the logs of istio-ingressgateway-xxx pod there are no traces as there are when you remove/create gateways:
[2018-06-03 00:44:33.705][215][info][upstream] external/envoy/source/server/lds_api.cc:74] lds: remove listener '<IP_ADDRESS>_80'
[2018-06-03 00:44:45.130][215][info][upstream] external/envoy/source/server/lds_api.cc:62] lds: add/update listener '<IP_ADDRESS>_80'

And if I tray to add other gateway with hosts set to "*" I gett the error:

[2018-06-03 00:51:24.660][215][warning][upstream] external/envoy/source/common/config/grpc_mux_impl.cc:218] gRPC config for type.googleapis.com/envoy.api.v2.Listener update rejected: Error adding/updating listener <IP_ADDRESS>_80: error adding listener '<IP_ADDRESS>:80': multiple filter chains with the same matching rules are defined
[2018-06-03 00:51:24.660][215][warning][config] bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_mux_subscription_lib/common/config/grpc_mux_subscription_impl.h:70] gRPC config for type.googleapis.com/envoy.api.v2.Listener rejected: Error adding/updating listener <IP_ADDRESS>_80: error adding listener '<IP_ADDRESS>:80': multiple filter chains with the same matching rules are defined

And after I remove the first one, the edited one I see the trace:
 [2018-06-03 00:52:20.133][215][info][upstream] external/envoy/source/server/lds_api.cc:62] lds: add/update listener '<IP_ADDRESS>_80'
And the second one starts to work.

The problem was the VirtualService no the Gateway

Hi @jxadro , what problems on VirtualService cause this? How did you fix them?

I found the reason, I have two gateways who were both listening the 80 number, I deleted one, it works.


AttributeError: 'ConfigDict' object has no attribute 'test'

Hello author, thank you very much for your outstanding contribution.
In Evaluation，To evaluate on SBD with InterFormer-Tiny, run: CUDA_VISIBLE_DEVICES=0,1,2,3 bash tools/dist_clicktest.sh work_dirs/interformer_tiny_coco_lvis_320k/iter_320000.pth 4 --dataset sbd --size_divisor 32.
I encountered an error while running：Traceback (most recent call last):
File "/home/student1/wbj/InterFormer/tools/clicktest.py", line 316, in
main()
File "/home/student1/wbj/InterFormer/tools/clicktest.py", line 219, in main
dataset = build_dataset(cfg.data.test)
File "/home/student1/anaconda3/envs/py38_wbj/lib/python3.8/site-packages/mmcv/utils/config.py", line 50, in getattr
raise ex
AttributeError: 'ConfigDict' object has no attribute 'test'
How should I solve it?
The full output of the error：
(py38_wbj) student1@user-PowerEdge-R555:~$ CUDA_VISIBLE_DEVICES=0,1 bash /home/student1/wbj/InterFormer/tools/dist_clicktest.sh "/home/student1/wbj/InterFormer/work_dirs/interformer_tiny_coco_lvis_320k/iter_320000.pth" 2 --dataset berkeley --size_divisor 32
/home/student1/anaconda3/envs/py38_wbj/lib/python3.8/site-packages/torch/distributed/launch.py:178: FutureWarning: The module torch.distributed.launch is deprecated
and will be removed in future. Use torchrun.
Note that --use_env is set by default in torchrun.
If your script expects --local_rank argument to be set, please
change it to read from os.environ['LOCAL_RANK'] instead. See
https://pytorch.org/docs/stable/distributed.html#launch-utility for
further instructions
warnings.warn(
WARNING:torch.distributed.run:

Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.

2023-07-05 01:55:19,481 - mmseg - INFO - Multi-processing start method is None
2023-07-05 01:55:19,482 - mmseg - INFO - OpenCV num_threads is 32 2023-07-05 01:55:19,482 - mmseg - INFO - OMP num threads is 1 2023-07-05 01:55:20,168 - mmseg - INFO - Multi-processing start method is None2023-07-05 01:55:20,169 - mmseg - INFO - OpenCV num_threads is32
2023-07-05 01:55:20,169 - mmseg - INFO - OMP num threads is 1
Traceback (most recent call last):
File "/home/student1/wbj/InterFormer/tools/clicktest.py", line 316, in
main()
File "/home/student1/wbj/InterFormer/tools/clicktest.py", line 219, in main
dataset = build_dataset(cfg.data.test)
File "/home/student1/anaconda3/envs/py38_wbj/lib/python3.8/site-packages/mmcv/utils/config.py", line 50, in getattr
raise ex
AttributeError: 'ConfigDict' object has no attribute 'test'
Traceback (most recent call last):
File "/home/student1/wbj/InterFormer/tools/clicktest.py", line 316, in
main()
File "/home/student1/wbj/InterFormer/tools/clicktest.py", line 219, in main
dataset = build_dataset(cfg.data.test)
File "/home/student1/anaconda3/envs/py38_wbj/lib/python3.8/site-packages/mmcv/utils/config.py", line 50, in getattr
raise ex
AttributeError: 'ConfigDict' object has no attribute 'test'
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: 1) local_rank: 0 (pid: 11982) of binary: /home/student1/anaconda3/envs/py38_wbj/bin/python
Traceback (most recent call last):
File "/home/student1/anaconda3/envs/py38_wbj/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home/student1/anaconda3/envs/py38_wbj/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/student1/anaconda3/envs/py38_wbj/lib/python3.8/site-packages/torch/distributed/launch.py", line 193, in
main()
File "/home/student1/anaconda3/envs/py38_wbj/lib/python3.8/site-packages/torch/distributed/launch.py", line 189, in main
launch(args)
File "/home/student1/anaconda3/envs/py38_wbj/lib/python3.8/site-packages/torch/distributed/launch.py", line 174, in launch
run(args)
File "/home/student1/anaconda3/envs/py38_wbj/lib/python3.8/site-packages/torch/distributed/run.py", line 752, in run
elastic_launch(
File "/home/student1/anaconda3/envs/py38_wbj/lib/python3.8/site-packages/torch/distributed/launcher/api.py", line 131, in call
return launch_agent(self._config, self._entrypoint, list(args))
File "/home/student1/anaconda3/envs/py38_wbj/lib/python3.8/site-packages/torch/distributed/launcher/api.py", line 245, in launch_agent
raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
/home/student1/wbj/InterFormer/tools/clicktest.py FAILED
Failures:
[1]:
time      : 2023-07-05_01:55:22
host      : user-PowerEdge-R555
rank      : 1 (local_rank: 1)
exitcode  : 1 (pid: 15984)
error_file: <N/A>
traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html
Root Cause (first observed failure):
[0]:
time      : 2023-07-05_01:55:22
host      : user-PowerEdge-R555
rank      : 0 (local_rank: 0)
exitcode  : 1 (pid: 15982)
error_file: <N/A>
traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html

Hello,
The error message you've shared suggests that there might be an issue with how the 'test' attribute is being set in the 'merge_from_dict' function on line 135 in 'clicktest.py'. The way this function operates could vary between different versions of the library, which could be the root of your issue.
Could you confirm your library version for us? Meanwhile, you might also want to check your MMCV version:
import mmcv
print(mmcv.__version__)

I installed the various packages according to the prompts, after import mmcv and print(mmcv.version), my mmcv version is 1.6.0

Considering I can't directly test in your environment, I recommend using an additional configuration file for testing, strictly following the basic paradigm of open-mmlab. Here are the steps:

In your test configuration file directory, i.e., work_dirs/interformer_tiny_coco_lvis_320k, create a new folder named intertest_sbd (or any other name of your choice). Within intertest_sbd, create a new configuration file config.py. Below is an example (for SBD, the content is taken from the set_test_cfg function starting from line 56 in clicktest.py):

_base_ = ['../interformer_tiny_coco_lvis_320k.py']  # Note: This must point to your previous test configuration file

pipeline = [
    dict(type='LoadImageFromFile'),
    dict(type='LoadSBDAnnotations'),
    dict(
        type='Resize',
        img_scale=None,
        ratio_range=(1.0, 1.0),
        keep_ratio=True),
    dict(type='RandomFlip', prob=0.0),
    dict(
        type='Normalize',
        mean=[123.675, 116.28, 103.53],
        std=[58.395, 57.12, 57.375],
        to_rgb=True),
    dict(
        type='Pad',
        size=(None if args.size is None else to_2tuple(args.size)),
        size_divisor=(args.size_divisor if args.size is None else None),
        pad_val=0,
        seg_pad_val=0),
    dict(
        type='ObjectSampler',
        num_samples=1,
        max_num_merged_objects=1,
        min_area_ratio=0.0),
    dict(type='DefaultFormatBundle'),
    dict(type='Collect', keys=('img', 'gt_semantic_seg'))
]

data = dict(
    test=dict(
        type=dataset,
        data_root='data/sbd/benchmark_RELEASE/dataset',
        pipeline=pipeline
))

model = dict(
    test_cfg=dict(
        num_clicks=20,
        inner_radius=5,
        outer_radius=0
))

Comment out line 178 in clicktest.py which is cfg = set_test_cfg(cfg, args). This is because the above configuration already realizes this part to prevent overwriting.

Use ln -s src_file tar_file to create a symbolic link to your downloaded iter_320000.pth weight file in the intertest_sbd folder (i.e., in the same directory as config.py), and then start the test command. Make sure to change the path to intertest_sbd. Also, note that when using ln -s, the source path must be an absolute path.

Lastly, please note that you can refer to the set_test_cfg function in clicktest.py to adapt this example for testing other datasets.

Sorry for the confusion. In step 3, you can directly copy iter_320000.pth into the new intertest_sbd directory. The use of ln -s is to create a symbolic link, serving the same purpose as copy without actually duplicating the file iter_320000.pth. Indeed, clicktest.py requires an input of the weight file to be tested, in this case iter_320000.pth, and will automatically load a .py configuration file located in the same directory. Please ensure there is only one .py file in this directory.


Deadlock in CI

One simple code change triggers a deadlock in CI, when running the bats tests.
The current investigation shows that:

the change in itself does not seem responsible for the deadlock. It just changes the timing of some actions
there seems to be an issue with the node creation where the process starting a background node does not stop

fixed with https://github.com/build-trust/ockam/pull/7329


Test discovery fails if the pdb format is "portable"

Using version 2.1.1 of the test adapter, in VS2017 Update 2, the test discovery fails with this error:
Exception System.InvalidOperationException, Exception converting MyTest.
Upgrading the Mono.Cecil package to the latest version (0.10.0-beta6), or using full pdb format fixes the issue.

IIRC, we can't target .NET 2 if we use the latest Mono.Cecil.

I guess this adapter also needs https://github.com/nunit/nunit3-vs-adapter/pull/350

Who wants to take this?

We should implement nunit/nunit3-vs-adapter#350 although it will not fix this for Update 2 of 2017. Those changes are coming in 15.3 and even now they are hidden behind a feature flag, From the RFC,

While the changes for CLI will be available in a future release, changes for IDE are already available in Visual Studio 2017 Update 3 Preview 3 and newer builds but is hidden behind a feature flag.

There's a port of nunit/nunit3-vs-adapter#350 to nunit2 here: https://github.com/nunit/nunit-vs-adapter/pull/160. @jnm2 @rprouse @OsirisTerje can you please review this?

Team members receive a notice when you submit a PR but it sometimes takes a few days before someone has time to review it.

@codito Will review this as soon as I have 3.9 out for the NUnit3TestAdapter.

+1 On VS 2017 15.7.2.  Changing to full debug symbols fixes the issue.


Add combos involving vertex color to Alpha and MetallicRoughness, and change how we test UV1

Added new combos, changed a few property names, and changed the column order on some MD tables. Also removed Textures from some combos, and drastically changed how we're testing using a second UV.
Fixes #191, #192, #193, #195, #196, and #203

In PBRMetallicRoughness test, move tests 14 and 15 to be below test 10, to keep all base color texture tests together

New MetallicRoughness order. This was more difficult to do than I thought.

An here is the new Alpha order


Lint core/withcontexts.py using flake8

Changes (in order)

Update .flake8
Use ruff format to resolve stylistic errors
Resolve remaining errors manually

Won't merge. Please see comment https://github.com/numba/numba/pull/9831#issuecomment-2532150637

Since this is only modifying one file, I don't consider this a large-scale change. Also, because of the limited scope it is feasible to have a human review the changes. However it will need to be run through some additional testing to ensure we don't break anything.


more production users?!?!

Big thanks to all the production users who've allowed us to put their company logo on the README...
I'm curious if there are any more lurkers who watch the repository, run NSQ in production, and might be willing to share their use case / give us permission to add their logo?
:heart_eyes: :sparkling_heart: :sparkles:

thanks @hden, added!


Why do you use mixed training?

Hello, I notice that in the training script, you set the mixed_training argument as True for all the time
runner = PyramidDiTForVideoGeneration(
        model_path,
        model_dtype,
        model_name=model_name,
        use_gradient_checkpointing=args.gradient_checkpointing,
        gradient_checkpointing_ratio=args.gradient_checkpointing_ratio,
        return_log=True,
        model_variant=model_variant,
        timestep_shift=args.schedule_shift,
        stages=[1, 2, 4],      # using 3 stages
        stage_range=[0, 1/3, 2/3, 1],
        sample_ratios=sample_ratios,     # The sample proportion in a training batch
        use_mixed_training=True,
        use_flash_attn=args.use_flash_attn,
        load_text_encoder=args.load_text_encoder,
        load_vae=args.load_vae,
        max_temporal_length=args.max_frames,
        frame_per_unit=args.frame_per_unit,
        use_temporal_causal=args.use_temporal_causal,
        corrupt_ratio=args.corrupt_ratio,
        interp_condition_pos=args.interp_condition_pos,
        video_sync_group=args.video_sync_group,
)

It seems to be that the dit is trained on float32, which consumes a lot. Why do you set so? Whether this is necessary? And is there a drop in performance when just training on bfloat16?

Sorry, maybe I understand it wrongly


[http-server-csharp] OkResponse is generated as a model

We have an operation that just returns 200 without body content:
op hello(): OkResponse;

usually we write this in a way that the op returns void, but because of this issue , I cannot do it.
In the generation result, OkResponse is generated as an empty model, this should not happen especially the operation with OkResponse
is generated as this without a return body type:
public interface ISayHi
{
    Task HelloAsync();
}

Generally, void is synonymous with 204


Delete release-drafter.yml

GitHub now has an easy-to-use button to automatically add release notes.
Therefore it's not necessary to use this yaml for an app we experimented with a while back.

I'd stll prefer automation if y'all have a goal of releasing things to GitHub releases. In my experience, they only generate confusion and unnecessary bug reports as people use the wrong artifacts so I'd rather not use them at all.

I'd stll prefer automation if y'all have a goal of releasing things to GitHub releases. In my experience, they only generate confusion and unnecessary bug reports as people use the wrong artifacts so I'd rather not use them at all.

Agree, automation is great. But this file specifically was for a GitHub app we no longer use (because it was buggy).  https://github.com/apps/release-drafter


Create a terraform module for jupyter-ui charm

Context
According to the terraform modules organization spec, this is the first step to provide a terraform solution module. We need to create a terraform module for each charm.
What needs to get done
Create a terraform module for this charm that complies with the spec.
Definition of Done
Charm has a terraform module

Closed by #407 and #408


recommend not connecting to ClickHouse via MySQL

Try Discussion?
Thank you for your outstanding contribution. I have read your paper and think it is great, but I suggest not using MySQL to support the connection to ClickHouse. It is better to use the native ClickHouse driver.
This is because the upstream library r2d2-mysql depends on https://github.com/blackbeam/rust-mysql-simple/tree/master, which performs some handshake operations when connecting to the database server, such as querying max_allowed_packet. Some of these commands are not supported by ClickHouse, which may lead to unsuccessful connections and make it difficult for users to get started directly.

Other
Feel free to ask here if you think it's more suitable.

Hi @hanson-young , thank you for starting this discussion! Indeed, we do observe some issues using mysql to connect to clickhouse both in terms of functionality (e.g., authentication) and performance. And it will be ideal if we can add a native clickhouse driver in connectorx. (I saw there are several clickhouse drivers in rust, not sure which one is the best choice.)
We may not have time to support this in this month. Please feel free to contribute and let me know if you have any questions!

Hi @wangxiaoying, I think it could also be related to my problem.
My team and I using clickhouse over HTTPS, which is not supported by the current version of r2d2-mysql.
After researching this topic, I found that ClickHouse has released its Rust library for use with ClickHouse.
https://github.com/ClickHouse/clickhouse-rs
If you don't have anything strong against it, I could start working on implementation of native support of their native library for clickhouse.

I would be also thrilled if we could use the native/http(s) protocol. I would be willing to take it as well. @Spar9a

Hi @wangxiaoying, I think it could also be related to my problem.
My team and I using clickhouse over HTTPS, which is not supported by the current version of r2d2-mysql.
After researching this topic, I found that ClickHouse has released its Rust library for use with ClickHouse. https://github.com/ClickHouse/clickhouse-rs
If you don't have anything strong against it, I could start working on implementation of native support of their native library for clickhouse.

I think it looks good! Please feel free to open a PR on this and let me know if you need my help on anything.

@hohmannr Yeah, I'll take it and try to finish it in the short term because I see some good points in improving the existing services on my team.
@wangxiaoying Great, I am starting to work on it.
I will be in touch regarding problems or questions!

@hohmannr Yeah, I'll take it and try to finish it in the short term because I see some good points in improving the existing services on my team.
@wangxiaoying Great, I am starting to work on it.
I will be in touch regarding problems or questions!

I think it would improve the lives of a lot of people, can't wait to see it merged


Feature request: control flip state from widget parameters

I'm trying to use this library but In my case I needed the flip_card to be "uncontrolled" (I'm sorry for the react.js terminology)
ie. this widget would dispatch onTap events and would react to isFront from parameters provided from the parent Widget.
Is it possible to do this with the current version of the lib? Is there any plans to support something like this?

Could you please elaborate, I am not really familiar with react terminology, if you want to flip the card without touching it there is a controller built in to change it manually. Hope this solves it for you

I'm looking for something similar to what @canastro is after: Being able to provide a parameter like "isFront: true" that determines the face that is showing. You'd then use onTap callback to set the value of isFront. It would allow declaratively controlling which side is showing and avoids issues where toggling state can result in the ui being out of sync with the intended ui state.

Providing a controller, then calling flipCardController.controller!.forward()  and backward in a didUpdateWidget should work.


File explorer should persist highlight the selected file/files when showing right-click menu

otherwise, this will make users to confuse that which is the file/files operating

Dup of https://github.com/microsoft/vscode/issues/123771
fyi @joaomoreno


Client Lag occurs when RS is tied to a power setup that is browning out

Issue description:  Client Lag occurs when RS is in a brown out scenario (power is consumed more quickly than you can produce)
What happens:
When there is a sever power spike, and the power storage fully drains, the RS controller/grids etc will trigger on and off rapidly causing client lag.  If I move out of range of the RS system, the lag goes away
As this was also on a server, I had the admins watch to see if there was server side performance (there was nothing to note)....
What you expected to happen:
In this case some sort of detection to see if the RS system is "flapping?" and then not switch the visual cues?
Steps to reproduce:
Setup assumes you also have enderio along with RS.

Setup a powergen + capacitor setup + RS system such that you produce only slightly more than you consume.
Set the RS controller so it is disabled when it gets a redstone signal, and attach a lever to it (turned off)...controller should still be active
setup about 8-10 smelteries/sag mills on the system (with the highest capacitors on it), and load them up so they continually operate.
Attach them to your power grid
Navigate back to your RS area....
You should see the RS controller turn on and off VERY rapidly, and the game client will lag
Flip the controller lever to disable the RS controller
Now the client lag should go away...
...

Version (Make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge: <IP_ADDRESS>5
Refined Storage: 1.2.12

Does this issue occur on a server? yes, but it does not cause server lag (that we could tell)
If a (crash)log is relevant for this issue, link it here:
[pastebin/gist/etc link here]

Duplicate of #566


Podman complains about health check syntax errors

There are two containers where the healthcheck fails in podman due to a syntax error, studio and pgmeta.

pgmeta

https://github.com/supabase/cli/blob/71c2abdac3ab092c8bf8ac84b40f77b20821dfb3/internal/start/start.go#L901

studio

https://github.com/supabase/cli/blob/71c2abdac3ab092c8bf8ac84b40f77b20821dfb3/internal/start/start.go#L947
When I change these two lines to a noop, the containers start successfully. For example:
-					Test:     []string{"CMD", "node", `--eval='fetch("http://<IP_ADDRESS>:8080/health").then((r) => {if (r.status !== 200) throw new Error(r.status)})'`},
+					Test:     []string{"CMD", "node", `--version`},

Log (it's not pretty):
Health:
  FailingStreak: 2

  Log:

  - End: 2024-07-18T20:19:42.26441464+03:00
    ExitCode: 1
    Output: "[eval]:1\n'fetch(\"http://<IP_ADDRESS>:3000/api/profile\",\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nSyntaxError: Invalid or unexpected token\n    at makeContextifyScript (node:internal/vm:185:14)\n    at node:internal/process/execution:107:22\n    at [eval]-wrapper:6:24\n    at runScript (node:internal/process/execution:101:62)\n
alScript (node:internal/process/execution:133:3)\n    at node:internal/main/eval_string:51:3\n\nNode.js v20.15.0"
    Start: 2024-07-18T20:19:42.236295233+03:00

  - End: 2024-07-18T20:19:52.356312244+03:00
    ExitCode: 1
    Output: "[eval]:1\n'fetch(\"http://<IP_ADDRESS>:3000/api/profile\",\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nSyntaxError: Invalid or unexpected token\n    at makeContextifyScript (node:internal/vm:185:14)\n    at node:internal/process/execution:107:22\n    at [eval]-wrapper:6:24\n    at runScript (node:internal/process/execution:101:62)\n
alScript (node:internal/process/execution:133:3)\n    at node:internal/main/eval_string:51:3\n\nNode.js v20.15.0"
    Start: 2024-07-18T20:19:52.328284657+03:00

Ref: https://github.com/supabase/cli/pull/2359

Could you report the podman version you are using? It seems fine on 5.0.2 based on the linked PR.

$ podman version
Client:       Podman Engine
Version:      5.1.2
API Version:  5.1.2
Go Version:   go1.22.5
Built:        Tue Jan  1 03:00:00 1980
OS/Arch:      linux/amd64

Experiencing this as well on a fresh installation of everything.
Windows 11 (PowerShell)
Supabase CLI 1.191.3
Podman 5.2.2
Starting Supabase with --ignore-health-check allows for everything to work properly.

should be resolved by https://github.com/supabase/cli/pull/2656 in npx supabase@beta start


Ignore other libraries in coverage

Currently the coverage report on travis includes other libraries and takes many times longer than the actual tests to generate. We should disable coverage for everything but the holocube module itself.

I agree and I'll look into this.

The PR referenced above addresses this. Closing.


Transfer is in a very sorry state right now

Everything transfer is kinda busted - see #204, #191, #178.
Stuff used to work somewhat, but was very unstable and performance heavy.
I tried adding some caching, but that broke everything because FAPI's getVersion isn't actually implimented.
I plan to redo all of transfer in the near future, directly interfacing with FAPI. That will be a lot of work though and will take a bit.

:waaaaagh_perish:

Use 441th build for now, its the most stable build so far.

branch has been created.
300 errors that need to be rewritten, this will take a bit. Afterwards a lot of testing will be needed. In the meantime, 441 works.

see #226


Cannot determine if contact is in MISSED state - getStatus() returns ERROR

If I let a contact fall into the MISSED state, the CCP red banner shows the contact as Missed chat, but if I do:
contact.getState() or contact.getStatus()
... the returned state is ERROR.
I've also tried:
contact.getAgentConnection().getState()

which returns DISCONNECTED as the state.
How can I determine if a contact is in the MISSED state?

Hi,
Unfortunately we doesn't build the contact status in a elaborative way right now, rather we just pass back the contact status from the back end API request, which couldn't easily tell if the contact is in missed state from the single request itself.
You can use the following code snippets to determine if the contact is in missed state:
isContactMissed() {
  return contact.getStatus().type === CONTACT_STATUS.ERROR &&
    contact.getInitialConnection().getStatus().type === CONTACT_STATUS.CONNECTED &&
    contact.getAgentConnection().getStatus().type ===  CONTACT_STATUS.DISCONNECTED;
}

We'll evaluate to provide such API to Streams as well.
Thanks.

@yaminli-aws thanks for the response, i'll use the method you suggested for getting missed state.


GPU Video Decoding is Broken in Windows 7

Describe the bug
In Windows 10 and Chromium 120, the browser is able to do GPU video decoding via D3D11VideoDecoder using NVIDIA Geforce GT 640.
However in Windows 7 and Supermium (126 R6), the browser won't use GPU for video decoding (D3D11VideoDecoder will fail).
This GPU supports HW encoding and decoding of H264.
GPU page report: GPU Internals.zip
To Reproduce
Steps to reproduce the behavior:

Try to play H264 content via the browser (fastest way is to install enhanced-h264ify extension and play a video from Youtube)
Leave it playing and go to chrome://media-internals on a new tab
Find your content (starts with blob and end with kPlay)
See if it uses D3D11VideoDecoder or not

Expected behavior
Supermium should initialize D3D11VideoDecoder for videos.
Screenshots

Desktop (please complete the following information):
OS: Windows 7 Enterprise x64 Service Pack 1 (Platform Update installed)
Browser: Supermium 126.0.6478.254 x86 (Shouldn't matter, right?)
GPU: NVIDIA GeForce GT 640 (475.14)
Additional context
I thought D3D11VideoDecoder actually worked in Windows 7 but for some reason I couldn't get it running (I installed DirectX Runtime to see if it makes a difference but it didn't).

Try to run Supermium with the --disable-gpu-driver-bug-workarounds command line, see more here.

You have been sending the same comment to every "GPU" related issue, I don't think you're reading it completely though. If you have checked my GPU report, you would have noticed that GPU workarounds section is missing which means I've already enabled that option. Also, I never needed to use it to get the Video Decoding working.
Also can be seen in the command line options in the same HTML:

I also noticed that it doesn't detect the D3D11 Feature Level of my GPU while Chromium 120 detects it in Windows 10.
Running Chromium 120 in Windows 7 with VxKex didn't give me the wanted result either, so I think something is broken in Supermium where it limits the usage of D3D11VideoDecoder for Windows 10 only.
Tried Supermium + Windows 10 combination as well and I was able to get it working that way, but my problem is Windows 7-specific so it still continues in it.

Looks like win32ss decided to skip my issues or GPU accelerated video decoding is simply out of his scope. I'll do everything I can to avoid using this half-finished browser if it won't become useful for me. Thankfully, Firefox ESR is supported until 2025, so I can use that to log into the sites which will cause problem in Chromium 109.
My Recommendation:
DO NOT USE SUPERMIUM IF YOU NEED GPU VIDEO DECODING. IT CAN'T DO IT ANYMORE.

@win32ss
Hardware decoding (essentially just H264) doesn't work on Windows 7 with any backend API in Supermium. I'm unsure about XP/Vista as they don't ship with that codec in the first place (or if their drivers even support hardware decoding, if a decoder is retroactively installed).

something is broken in Supermium where it limits the usage of D3D11VideoDecoder for Windows 10 only. Tried Supermium + Windows 10 combination as well and I was able to get it working that way, but my problem is Windows 7-specific so it still continues in it.

No, it works in Windows 8.1 perfectly. Maybe it works with Windows 8.0 too, I will test it maybe with Windows 7 on the same PC.

I'm unsure about XP/Vista as they don't ship with that codec in the first place

Vista SP2 user here; a fully updated OS with Platform Update Supplement (PUS) has Windows Media Foundation (WMF), d3d11 and an OS-supplied h264 decoder; but Google have, since Chrome 25, blacklisted/disabled H/W-h264-decoding under Vista :disappointed: ; in chrome://gpu/ one gets:

Problems Detected for Hardware GPU
Hardware video decode is only supported in win7+: 159458
Disabled Features: accelerated_video_decode

https://issues.chromium.org/issues/40953931#comment15

Disable accelerated_video_decode on windows that's earlier than win7.
This should not change anything because it's never supported on older windows.
Blacklisting the feature only let chrome know earlier, to avoid a renderer hang.

I have checked your GPU Internals and compared them to mine. It could be because you have no entries in the Video Acceleration Information Encoding section.
My PC:

Your PC:

@win8-png
Encode capabilities have no bearing on whether or not decode is functional. While the GPU Internals page shows that, at least on a theoretical level, H264 decoding is supported; it still won't work under Windows 7 in Supermium, no matter what hardware or software configuration (Chromium 109 and below have no issues with hardware decoding).

I looked through some old commits and realized that the D3D11 video decoder was never used on Windows 7 as it was blocked by an explicit version check; the DXVA video decoder was always being used instead.
The problem is that the old decoder has a very different structure compared to the current decoders and can't be easily restored.
I am looking into alternatives but finding the right one can be confusing. Until a few minutes ago, I was under the impression that DXVA2 was linked to D3D9Ex and thus needed Vista (as this page says: https://learn.microsoft.com/en-us/windows/win32/medfound/about-dxva-2-0), but then this example uses standard D3D9 and works on XP even though the readme for this sample says Vista is required: https://github.com/microsoft/Windows-classic-samples/blob/main/Samples/Win7Samples/multimedia/mediafoundation/dxva2_videoproc/dxva2vp.cpp
Indeed the DXVA2 option looks like the most straightforward option as it works well with D3D9 and has the closest structure to the current D3D11 setup.

@win32ss
I'm pretty sure that D3D11 decoding was first introduced in Windows 8 and never supplied to Windows 7. Windows 7 always used DXVA decoding instead, this is probably why @win8-png has working hardware decode as he uses Windows 8.
MPC-HC cannot use D3D11 as a hardware decoder in Windows 7 either, it'll just tell you that it's only supported on Windows 8+.

After doing some Googling for D3D11VideoDecoder, I found a question about it not working in Vivaldi browser here. People saying there that the D3D9/DXVA decoder has been disabled in Chromium since January 2023 where Windows 7/8.1 support ended.
Someone said there that he runs Vivaldi with DXVA by using --enable-features=DXVAVideoDecoding and --disable_d3d11_video_decoder (maybe only first flag of it is important):

I've managed to enable VDAVideoDecoder in vivaldi 6.1.3035.302 with these args: --enable-features=DXVAVideoDecoding --disable_d3d11_video_decoder
Seems like DXVAVideoDecoder was disabled by default in vivaldi after it's deprecation.

Something on the screen now, faster than I thought, but still need some more work to make this ready for use:

Maybe the folks at the VLC project could help with this, or at least their code could be useful. The VLC player appropriately uses DXVA2 on Vista and 7 and D3D11 on Windows 8+.
On another note, is the D3D11 decoder even necessary? For example, the nvidia driver's DXVA2 profiles include up to HEVC and VP9, which covers almost everything typical in the wild. Does anyone have an authoritative list of the codecs that lack DXVA(2) support but can be decoded using D3D11?

I also found out that the main Supermium fallback video decoder, the FFmpeg video decoder, also supports DXVA2. However this code isn't configured to build in Supermium at this time, and the documentation for the configuration script to change the build options for the build of FFmpeg is in the Google intranet. I will weigh my options.

@win32ss
Technical question; all browsers on Windows 7 always only supported DXVA2 1920x1080 h264 baseline, main and high profile hardware decoding. However, DXVA2, even on Windows 7, is capable of leveraging h265, vp8 and vp9 (as long as the graphics card supports those codecs) in video players and ffmpeg when using it to decode/encode.
Does this mean, that when Supermium uses ffmpeg for DXVA2 decoding now/at some point, those other codecs can now be utilized inside of the browser too?

Yes, as long as the other codecs prioritize FFmpeg, which I believe some do not, like VPx (which prefers the VpxVideoDecoder). This could be changed though.

There were some significant issues with the FFmpeg solution. It was clear that they would not be resolved in the short term, so I went ahead and started a DXGI/D3D11 port from Windows 8.1 to Vista/7. D3D11VideoDecoder now works, at least on H264 videos. But this comes at a cost of some UI rendering issues in the browser, which will either be resolved by disabling UI GPU compositing or various patches to the D3D11 runtime:

However, webpage rendering has improved considerably over the previous renderers on my Vista setup, eliminating glitches and even GPU process crashes that occurred before.
Any GPUs that support feature level 11.0 and up (GTX 400 series and up, or Ivy Bridge integrated graphics and up) will be able to use this rendering support.
I hope to eventually try working with the D3D12 runtime as well.

@win32ss
Are you still open for the ffmpeg implementation in the future? The D3D11VideoDecoder will obviously only work on DX11.0(+) graphics hardware and Vista(+), thus excluding older hardware and XP.

Yes, I'll still do something for systems with weaker to no D3D11 support. But its final form has yet to be determined, and it will only be done after my WASAPI-to-winmm wrapper is completed, which should help prove the viability of wrapping modern interfaces around legacy interfaces while allowing Windows 2000/XP to use Core Audio instead of the old audio codepaths that are prone to breakage.

Here are my benchmarks for gpu rendering on my pc, i hope it will be useful

and opengl without workarounds just break the browser

My gpu supports directx 10.1 soo.... it wuldnt be able to use the new renderer?

Also... there is something that i cant understand.... why if i play normally a video my gpu usage is 7-8-9%

BUT if i keep the youtube video ui active my Gpu usage spikes to 23% - 26% ????

Here are my benchmarks for gpu rendering on my pc, i hope it will be useful

Well, I have executed this fix: https://github.com/ptrumpis/OpenCL-AMD-GPU/tree/main    and now I seem to HAVE opengl

I have installed this fix, it worked on detecting actual opengl version but Nope, Opengl Still breaks the browser......

https://github.com/ptrumpis/OpenCL-AMD-GPU/tree/main

wat is happening

The GPU is always used, but a video decoder interface such as D3D11VideoDecoder or DXVA is needed to use the video rendering engine of the GPU, which is the most efficient method.
Furthermore, the new binaries seem to have some issues on Windows 7 because of a codepath taken on that system and not on Vista. This will need to be corrected.

The GPU is always used, but a video decoder interface such as D3D11VideoDecoder or DXVA is needed to use the video rendering engine of the GPU, which is the most efficient method.
Furthermore, the new binaries seem to have some issues on Windows 7 because of a codepath taken on that system and not on Vista. This will need to be corrected.

Great! Looking forward to those fixes!!!

The GPU is always used, but a video decoder interface such as D3D11VideoDecoder or DXVA is needed to use the video rendering engine of the GPU, which is the most efficient method.
Furthermore, the new binaries seem to have some issues on Windows 7 because of a codepath taken on that system and not on Vista. This will need to be corrected.

And what about OpenGL?

Edit the last post instead posting again so the thread could be kept cleaner. You can't do anything for now since your GPU doesn't support even D3D11_0 which is required for D3D11Decoder to work. You'd need to have VDAVideoDecoder in your browser to get acceleration, which seems to be removed in v117 or so.
If you want to have GPU accelerated video decoding, use Chromium 109 (last official version for 7&8.1) .


Problem clicking on collections

Clicking on Collection, gives:
Error: collection not found at /usr/home/synbiohub/synbiohub/lib/get-sbol.js:81:25 at /usr/home/synbiohub/synbiohub/node_modules/async/lib/async.js:154:25 at /usr/home/synbiohub/synbiohub/lib/get-sbol.js:74:17 at /usr/home/synbiohub/synbiohub/node_modules/sbolstack-frontend/lib/store.js:109:13 at Request._callback (/usr/home/synbiohub/synbiohub/node_modules/sbolstack-frontend/lib/getSBOL.js:24:13) at Request.self.callback (/usr/home/synbiohub/synbiohub/node_modules/request/request.js:200:22) at emitTwo (events.js:87:13) at Request.emit (events.js:172:7) at Request.(/usr/home/synbiohub/synbiohub/node_modules/request/request.js:1067:10) at emitOne (events.js:82:20) at Request.emit (events.js:169:7) at IncomingMessage.(/usr/home/synbiohub/synbiohub/node_modules/request/request.js:988:12) at emitNone (events.js:72:20) at IncomingMessage.emit (events.js:166:7) at endReadableNT (_stream_readable.js:893:12) at doNTCallback2 (node.js:429:9) at process._tickCallback (node.js:343:17)

Seems to work now.


Switch use of deprecated funcargnames attribute to fixturenames

https://docs.pytest.org/en/latest/deprecations.html#removal-of-funcargnames-alias-for-fixturenames

Thanks @mikix! I've taken this over and fixed that failing test at https://github.com/rlucioni/pytest-django-ordering/pull/10.

Oh thank you @rlucioni! I had it on my TODO, but was not finding time for it. Thanks.


threadpool=cached can not recycle idle thread

Environment

Dubbo version: 2.7.5 / 2.7.12
Java version: JDK1.8

my dubbo config
dubbo.protocol.threads=5
dubbo.protocol.corethreads=2
dubbo.protocol.alive=15000
dubbo.protocol.threadpool=cached

I hope idle thread will be recycle after 15 seconds.
Invoke some service, jstack java process show as follow, 5 thread idle:
"Dubbo-thread-5" #108 daemon prio=5 os_prio=0 tid=0x0000000033e54000 nid=0x2410 waiting on condition [0x000000004761e000]
        at org.apache.dubbo.common.threadlocal.InternalRunnable.run(InternalRunnable.java:41)
"Dubbo-thread-4" #107 daemon prio=5 os_prio=0 tid=0x0000000033e53800 nid=0x395c waiting on condition [0x000000004751f000]
        at org.apache.dubbo.common.threadlocal.InternalRunnable.run(InternalRunnable.java:41)
"Dubbo-thread-3" #106 daemon prio=5 os_prio=0 tid=0x0000000033e51000 nid=0x3858 waiting on condition [0x000000004741e000]
        at org.apache.dubbo.common.threadlocal.InternalRunnable.run(InternalRunnable.java:41)
"Dubbo-thread-2" #97 daemon prio=5 os_prio=0 tid=0x0000000033e4c800 nid=0x2210 waiting on condition [0x000000004637f000]
        at org.apache.dubbo.common.threadlocal.InternalRunnable.run(InternalRunnable.java:41)
"Dubbo-thread-1" #96 daemon prio=5 os_prio=0 tid=0x0000000033e47800 nid=0x12e8 waiting on condition [0x000000004526e000]

But after 15 seconds or more, these idle thread still alive, unexpectedly been recycled.

Please check if the service is blocked.

Please check if the service is blocked.

No! In fact there are no any more request. Maybe you can test in local host, it should be repeated again.


React v16 support

<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>Thanks

PRs are most welcome

Fix released!


Example in readme breaks non feign-form clients

The example in the readme to include:

@Configuration
public class MultipartSupportConfig {
...
}

Breaks other feign clients that do need feign-form. The relevant part of the stacktrace is:

feign.codec.EncodeException: class com.concur.ais.cloudelements.model.ElementInstance is not a type supported by this encoder.
at feign.codec.Encoder$Default.encode(Encoder.java:90)
at feign.form.spring.SpringFormEncoder.encode(SpringFormEncoder.java:35)
at feign.ReflectiveFeign$BuildEncodedTemplateFromArgs.resolve(ReflectiveFeign.java:351)
at feign.ReflectiveFeign$BuildTemplateByResolvingArgs.create(ReflectiveFeign.java:213)
at feign.SynchronousMethodHandler.invoke(SynchronousMethodHandler.java:72)
at feign.ReflectiveFeign$FeignInvocationHandler.invoke(ReflectiveFeign.java:103)
at com.sun.proxy.$Proxy125.createInstance(Unknown Source)

The Spring documentation here indicates that the @Configuration annotation is not needed, and actually harmful if the class is included in ComponentScanning:

FooConfiguration does not need to be annotated with @Configuration. However, if it is, then take care to exclude it from any @ComponentScan that would otherwise include this configuration as it will become the default source for feign.Decoder, feign.Encoder, feign.Contract, etc., when specified. This can be avoided by putting it in a separate, non-overlapping package from any @ComponentScan or @SpringBootApplication, or it can be explicitly excluded in @ComponentScan.

Thanks a lot for your comment, I will fix readme asap

done


Discription of InsertionSort all laguage files added

Added-
C++ directory with it's file
Java directory with it's file
Python directory with it's file

I will be adding more Codes and file for DS and Sorting and Searching

@Sk70249 : : It would be great if you can add the description along with the issue number.
Feel free to use our contribution guidelines (https://github.com/fnplus/interview-techdev-guide/blob/master/CONTRIBUTING.md) for reference
Please resolve the conflicts and submit for review. Thanks.

@Sk70249  : Please resolve the conflicts and submit for review with the Issue linked to this PR. Thanks.

Thanks for contributing!


Bot verification

The bot is unable to join servers as it is unverified

This is not due to lack of verification, the bot is verified. This is most likely due to certain privileged gateway intents being enabled but not being whitelisted for them. This issue can be temporarily resolved but disabling the intents from the developer console. This will allow the bot to be added to servers while awaiting response from discord's support team to be whitelisted. Apply at dis.gd/contact

This was resolved after closing both gateways since they are unnecessary, thank you for reporting this!


git: alias: add contribute command

Motivation: octomation/maintainer/issues/56 is implemented and now it's possible to simplify flow.
$ git contribute 2021 some commit message

https://github.com/kamilsk/dotfiles/commit/d19edea4e4a08a325acece3ddb41f5c5312a0133


Add Dask Cluster class to config file

It'd be nice to steal the feature from flint that allows a user to specify the Dask Cluster Class in the config YAML. @tjgalvin can this be ported into Arrakis?

It can be. What is the current branch one should be working from?

Lets go with imager

Fixed with #49


Activator incompatibility

On occasion VolumeBar9 and Activator will crash the Springboard, I think because of the hook on VolumeControl.
Hard to test; hard to reproduce.
Log files:

SpringBoard-2016-08-31-071058.symbolicated.ips.txt
SpringBoard-2016-08-31-071058.syslog.txt

Probably not a incompatibility? All the logs I've seen crash on -[VolumeBar resetTimer]

Logs with activator uninstalled:

SpringBoard-2016-08-31-212650.symbolicated.ips.txt
SpringBoard-2016-08-31-212650.syslog.txt

This confirms that it's definitely something with only VolumeBar9.

When adding logging to the tweak, the problem seems to disappear. Still hard to know for sure. Below is what was added.
VolumeBar.xm
-(void)resetTimer {
  HBLogDebug(@"in resetTimer");
  if(hide != nil) {
    HBLogDebug(@"hide exists");
    [hide invalidate];
    HBLogDebug(@"hide invalidated");
    hide = nil;
    HBLogDebug(@"hide = nil now");
    hide = [NSTimer scheduledTimerWithTimeInterval:_delayTime target:self selector:@selector(_hideHUD) userInfo:nil repeats:NO];
    HBLogDebug(@"new hide created");
  }
}

Tweak.xm
%hook VolumeControl

-(void)increaseVolume {
  HBLogDebug(@"hooked increaseVolume");
  if(active && vbar != nil) {
    HBLogDebug(@"calling resetTimer");
    [vbar resetTimer];
  }

  %orig;
}

%end

One report has come in that the crash is actually from pressing the volume buttons and calling resetTimer while the banner is animating away.

I was able to reproduce it in this way! Sweet, should be a relatively easy fix to disable any functionality of resetTimer after hideHUD has been called.


Improves server min/max port range

Adds a simple LFSR RNG which can generate all ports in the [min_port, max_port] range in random order for each client connection
Uses an LFSR per client to attempt binding ports until one is bound
If the client connected without a port request, only returns failure if all ports in the range are already bound
If client requests a port, it is checked against both min and max

This seems like a good approach, thanks. Would likely just use Fastrand though, which is less code and also less dependencies.
Code matters because bore is really small in amount of code and I would hope to keep it that way.
By the way, it's been a while and the {max port, bind to 0 behavior} are clearlys issue that a lot of people are interested in, thanks to everyone who expressed this. I'll set a reminder to get back to this in 2 weeks (but no promises).

I opted to implement an LFSR because it has the property that it will generate every number once before cycling, meaning we'll never waste any time checking a port we already checked (for a given client connection) without needing to explicitly track the ports we've already attempted to bind. If you use and RNG without this property you either 1) waste time rechecking ports you've already checked, or 2) need to track which ports you've tried already.
There is a crate which provides the LFSR we'd want here, so if you'd rather add a dependency than a few lines of code then that's an option.

Thanks for the feedback! That is true and a valid property of Galois fields generated by a single element, but there are downsides in that the linear recurrence is a pretty poor quality random number generator, and duplicate recurrences would overlap. Mathematically to find a free port with probability 1-δ, when at least ε proportion of the ports are currently available, it suffices to check -2 ε ln(δ) times (up to a second-order term in ε). So we can guarantee very high success rate (99.999%) at utilizing most ports (say, 80% of ports) with only 115 i.i.d. random checks.
use std::{net::TcpListener, time::Instant};

fn main() {
    let l1 = TcpListener::bind("<IP_ADDRESS>:1234").unwrap();
    let start = Instant::now();
    let l2 = TcpListener::bind("<IP_ADDRESS>:1234");
    assert!(l2.is_err());
    println!("{:?}", start.elapsed());
    drop(l1);
}

I just benchmarked it, and binding to a port that's already in use takes 10-20 µs on my machine, which isn't really a significant overhead. I'll probably just have it attempt binding about 150 times.

The implementation you suggest is quadratic in complexity as the number of used ports grows, since the LFSR needs to check every single port until it finds a working one (and moreover, always in the same order), which could lead to unintentional denial of service.

I don't think the bolded bit is true, as I start the search at a different place for each client connection.
Given your benchmarking, it seems checking many ports will be less costly than I imagined (I didn't take the time to check and just defaulted to what I still think is the more performant solution). The LFSR implementation is 60 lines (plenty of which are boilerplate) almost straight from the Wikipedia article, not sure why you're treating it like it is some magic that users couldn't parse. As far as the dependencies, rand is only used to seed the LFSR, so replace that with fastrand and you'll solve the "size of dependencies" problem.

Thanks for the contribution! I think I've made my decision.

Sure. Can you clarify if this still holds when using a random starting port?

The implementation you suggest is quadratic in complexity as the number of used ports grows, since the LFSR needs to check every single port until it finds a working one (and moreover, always in the same order), which could lead to unintentional denial of service.

Yeah, the behavior when many ports are used is what I intended to convey — if only ε proportion of ports are currently available, the LFSR would need to check 1/ε ports before finding one, and in particular it becomes quadratic once there are no more ports available since each future request requires checking all 65536 ports. Checking that many ports takes a while, so regardless I'd like to avoid doing that!

Makes sense. But if you stop after 150, you'll be turning away clients when there are actually ports available. I wanted to avoid that.
In my case, the [min_port, max_port] range is only ~2500 ports, so it's not as bad as 65k, but I get your point.


Feature filter from second configuration source is not respected when the base configuration does not specify a filter

I have run into something yesterday that cost me quite a bit of time and headache to figure out, and is incorrect behavior in my opinion.
If I specify the following feature flag in my appsettings.json:
  "FeatureManagement": {
    "Manage_Folders": true
  }

And override this value in Azure App Configuration with:
{
	"id": "Manage_Folders",
	"description": "Enable folder management",
	"enabled": true,
	"conditions": {
		"client_filters": [
			{
				"name": "Microsoft.Targeting",
				"parameters": {
					"Audience": {
						"Users": [],
						"Groups": [],
						"DefaultRolloutPercentage": 50
					}
				}
			}
		]
	}
}

This does not work as expected, as the filter is never evaluated and the feature is turned on for 100% of the requests.
In other situations, the behavior is correct and the filter is evaluated using the values supplied in Azure App Configuration:

Situation 1: toggle set to false

appsettings.json
  "FeatureManagement": {
    "Manage_Folders": false
  }

Azure App Configuration:
{
	"id": "Manage_Folders",
	"description": "Enable folder management",
	"enabled": true,
	"conditions": {
		"client_filters": [
			{
				"name": "Microsoft.Targeting",
				"parameters": {
					"Audience": {
						"Users": [],
						"Groups": [],
						"DefaultRolloutPercentage": 50
					}
				}
			}
		]
	}
}

Situation 2: A filter is also specified in appsettings.json, which is correctly overridden by the values from Azure App Configuration

appsettings.json
  "FeatureManagement": {
    "Manage_Folders": {
      "EnabledFor": [
        {
          "Name": "Percentage",
          "Parameters": {
            "Default": "0"
          }
        }
      ]
    }
  }

Azure App Configuration:
{
	"id": "Manage_Folders",
	"description": "Enable folder management",
	"enabled": true,
	"conditions": {
		"client_filters": [
			{
				"name": "Microsoft.Targeting",
				"parameters": {
					"Audience": {
						"Users": [],
						"Groups": [],
						"DefaultRolloutPercentage": 50
					}
				}
			}
		]
	}
}

Currently I managed to find a workaround for my usecase, but this behavior is incorrect in my opinion.

Hello @robertvandiest
I agree with your sentiment. This concern is also detailed in this previous issue: https://github.com/microsoft/FeatureManagement-Dotnet/issues/74.
I'd like to continue the conversation there if possible.
I would say the issue is a bit tricky here, and I'd like to know if you can provide the scenario that motivates you to do this to help see if it can drive a solution. The issue arises due to how .NET core configuration system works, which is a layer underneath this library.
I will close this issue in hopes that we can continue in the existing issue thread.


corrected setup instructions

There have been issues without setting up the atmodat checker. In this branch they are removed.

I am fine with that and you can merge at any. Should we maybe remove the comment instruction above the changed line?

I am fine with that and you can merge at any. Should we maybe remove the comment instruction above the changed line?

Do you mean this part: (only necessary for developers) ?

Do you mean this part: (only necessary for developers) ?

Yes. But I would also be okay to leave it in

Do you mean this part: (only necessary for developers) ?

Yes. But I would also be okay to leave it in

I would leave it on for the moment to make it clear that it is only for development purposes. But we should consider to leave the whole line out for the final revised version of the checker.


[FLINK-10863][tests] Assign UIDs to all operators in DataStreamAllrou…

…ndTestProgram
What is the purpose of the change
This PR assigns UIDs to all operators in DataStreamAllroundTestProgram so that testing adding/removing stateful operators will work properly.

Thanks for the review @tillrohrmann! Merging.


feat(router): redirect with token parameters

allow redirect to contain token parameters for router config
this closes feature request #483

Any updates on this? Would be really nice to have.

@davismj Can you review this? It looks like an interesting feature.

@jagonalez Sorry for the wait. Sincerely appreciate your hard work as always.
@djensen47 Thanks for your patience. Merged!

@jagonalez would you mind creating another PR for docs?
Or explain a bit on how it works.. so we could update the docs with a use case?

@jagonalez @davismj @EisenbergEffect
This new design of redirect disabled the old usage of redirect as in #607
It also causes regression in #605
This looks like a very isolated change, can we revert this commit for now?
Need to revise the design and add test coverage to ensure not breaking #605 and #607.


LLava Unity demo ?

Hi, any chance to get a unity demo of Llava ?
Llama is working great but i can't make Llava works.
Thanks,

Hi
I'll look into it and write you back.


Feature Request: Line Numbers (Legal Documents)

Typst seems like a good potential choice for people in the legal community to be able to write court filings. However, some courts require that legal documents include line numbers in the left-hand column. LaTeX has lineno for this, but I don't see the ability to do it with Typst. If a developer needs some examples of courts' local rules that shows the format I'd be happy to post them.

Are line numbers in these type of documents only needed to review and easily refer to a specific line?
- I don't like *this* on the line 24.
- Change *this* on the line 451 to *this*.
- I like what you did on the line 69.

Or line numbers have more use cases than this?

Line numbers are probably going to pass the set margins, right? If you set left margin to 3cm then the line number would appear somewhere in the first 3 cm from the left.
If so, then there is probably going to be the next options:
font: string | array
size: relative length
offset: rect

font is either a string or an array of fallback fonts. size is the size of the font. offset, I can't find a good example in the doc., but it can take something like:
offset: (
  left: relative length,
  right: relative length,
  top: relative length,
  bottom: relative length,
  x: relative length,
  y: relative length,
  rest: relative length,
)

If offset is auto (default), then it, for example, has right: 0.5cm, so that it would be usable by default.
One problem is that you have to somehow include and "on/off" switch somewhere in the Typst settings.
P.S. This is just an example/markup, and I'm also still new to the Typst.

A primitive such as line (similar to par) would be a great addition for per-line styling, which would also enable a modification of adding a number offset into the margin for each line.

Alright, well recently we got #2341, which greatly resembles what would be needed to accomplish this.
Otherwise, yes, line-numbering everything would be helpful with paper reviews, etc.

I was just coming to leave an issue about this. This is very important in academic journals or even in draftsmen in the hands of reviewers.

FWIW I am using this for now.
Main idea:

split up the input by parbreaks (numbering should skip these)
for each chunk between parbreaks, layout the content and calculate its height
divide the height of the chunk by the line height to get the number of lines (should be parameterized 🙃 )
make a grid, put the original content in the right half, put the line numbers in the left half, offset everything to the left to maintain placement of the original content

(Messy) Code below

number_content works with multiple paragraphs, inline equations, figures. I haven't tested with other types of content yet. Haven't tested multiple columns, probably will not work without modification. Haven't tested headers.

Credit:

pad_int is from https://github.com/dasayan05/typst-ai-conf-templates
inspiration for the approach is from https://github.com/dasayan05/typst-ai-conf-templates cvpr template

the template basically does the same thing, but globally for the entire page, without considering parbreaks.

Improvements:

You could probably avoid numbering the figures (and whatever other content you want to avoid skipping numbering for) by splitting on these in addition to parbreaks.

// #let l = state("lineno", 10)
#let l = counter("mycounter")
// #set page()
#set text(size: 10pt)

#let pad_int(i, N: 3) = {
  // pad an integer with leading zeros
  let s = str(i)
  let n_pads = N - s.len()
  for _ in range(n_pads) {
    s = "0" + s
  }
  [#s]
}

#let number_content(text_input) = {
  layout(
    size => style(
      styles => [
      #let (height) = measure(block(width: size.width, text_input), styles)
      #let numlines = int(calc.floor(height.height / 10pt))
      #let RULERWIDTH = 0.6in

      #move(
        grid(
          columns: (RULERWIDTH, 100%),
          gutter: 0pt,
          [
          #set text(
            rgb(50%, 50%, 100%),
            weight: "bold",
            font: "Times",
            size: 10pt,
            spacing: 65%,
          )
          // #set par(leading: 0.45em)
          #set align(left)
          #let start = locate(loc => [#l.at(loc)])

          #if numlines == 0 {
            numlines = 1
          }

          #for i in range(0, numlines) {
            l.step()
            [#l.display(pad_int) #linebreak()]
          }
          ],
          [
          #text_input
          ],
        ),
        dx: -RULERWIDTH,
        dy: 0pt,
      )
      ],
    ),
  )
}

Recently had the same requirement of numbering paragraphs, not lines, for a legal document. I settled on this solution using numbered lists for now. Maybe it can be of help to some of you?

This is the line number that I need.

Are there any new solutions that will allow us to get nice line numbers?

Another vote for line numbers for scientific papers. Current solution is pandoc to latex, and going from there.
If someone could give me pointers I could take a look myself too.

Consideration: pages with table only should also have their content provoke a line numbering.

@RafailFridman No current news, but I wanted to take a look at this before 0.12.

In case of CVPR/ICML-like templates, I have managed to render lines (see 998f02ac/cvpr). I define a ruler as a couter and locatable content and put it in background kwarg of page. Counter allows to enumerate lines on a specific page in locate(loc => ...) context.
In case of NeurIPS/ACL-like templates, it seems that there is no way to render line numbers in pure Typst without going deeper and modifying document model. I tried to override paragraph rule in order to attach on the left or on the right line number as follows.
#show par: it => {
  place(left + top, float: true, dx: -100pt, { /* generate line numbers here */ })
  it
}

Unfortunately, it does not work since it recursively invokes par rendering routine infinitely.

Any updates on this?

There has been a good deal of discussion on the topic in the academia forge on discord these past few days

Hurray! :tada:

Fantastic. Thank you for the hard work on this!

Kudos!