请教下最近的一次更新之后，训练 sbs_r101_ibn，发现会打印如下警告

是否因为修改了 non-local 模块？并且发现训练时间time稍长，占用显存稍高；
[09/10 23:16:58 fastreid.utils.checkpoint]: Loading checkpoint from /home/user/.cache/torch/checkpoints/msmt_sbs_R101-ibn.pth
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.0.g.weight' has shape (1, 512, 1, 1) in the checkpoint but (256, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.0.g.bias' has shape (1,) in the checkpoint but (256,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.0.W.0.weight' has shape (512, 1, 1, 1) in the checkpoint but (512, 256, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.0.theta.weight' has shape (1, 512, 1, 1) in the checkpoint but (256, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.0.theta.bias' has shape (1,) in the checkpoint but (256,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.0.phi.weight' has shape (1, 512, 1, 1) in the checkpoint but (256, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.0.phi.bias' has shape (1,) in the checkpoint but (256,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.1.g.weight' has shape (1, 512, 1, 1) in the checkpoint but (256, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.1.g.bias' has shape (1,) in the checkpoint but (256,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.1.W.0.weight' has shape (512, 1, 1, 1) in the checkpoint but (512, 256, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.1.theta.weight' has shape (1, 512, 1, 1) in the checkpoint but (256, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.1.theta.bias' has shape (1,) in the checkpoint but (256,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.1.phi.weight' has shape (1, 512, 1, 1) in the checkpoint but (256, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_2.1.phi.bias' has shape (1,) in the checkpoint but (256,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.0.g.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.0.g.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.0.W.0.weight' has shape (1024, 1, 1, 1) in the checkpoint but (1024, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.0.theta.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.0.theta.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.0.phi.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.0.phi.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.1.g.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.1.g.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.1.W.0.weight' has shape (1024, 1, 1, 1) in the checkpoint but (1024, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.1.theta.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.1.theta.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.1.phi.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.1.phi.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.2.g.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.2.g.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.2.W.0.weight' has shape (1024, 1, 1, 1) in the checkpoint but (1024, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.2.theta.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.2.theta.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.2.phi.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.2.phi.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.3.g.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.3.g.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.3.W.0.weight' has shape (1024, 1, 1, 1) in the checkpoint but (1024, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.3.theta.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.3.theta.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.3.phi.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.3.phi.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.4.g.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.4.g.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.4.W.0.weight' has shape (1024, 1, 1, 1) in the checkpoint but (1024, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.4.theta.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.4.theta.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.4.phi.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.4.phi.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.5.g.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.5.g.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.5.W.0.weight' has shape (1024, 1, 1, 1) in the checkpoint but (1024, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.5.theta.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.5.theta.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.5.phi.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.5.phi.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.6.g.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.6.g.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.6.W.0.weight' has shape (1024, 1, 1, 1) in the checkpoint but (1024, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.6.theta.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.6.theta.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.6.phi.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.6.phi.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.7.g.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.7.g.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.7.W.0.weight' has shape (1024, 1, 1, 1) in the checkpoint but (1024, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.7.theta.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.7.theta.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.7.phi.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.7.phi.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.8.g.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.8.g.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.8.W.0.weight' has shape (1024, 1, 1, 1) in the checkpoint but (1024, 512, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.8.theta.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.8.theta.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.8.phi.weight' has shape (1, 1024, 1, 1) in the checkpoint but (512, 1024, 1, 1) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.backbone.NL_3.8.phi.bias' has shape (1,) in the checkpoint but (512,) in the model! Skipped.
WARNING [09/10 23:16:58 fastreid.utils.checkpoint]: 'module.heads.classifier.weight' has shape (1041, 2048) in the checkpoint but (15506, 2048) in the model! Skipped.

因为 fix 了一个小 bug，具体如下
https://github.com/mangye16/ReID-Survey/issues/7
所以导致 non-local 部分参数有变动，所有出现 pre-train model 无法 load 进去的问题。

因为 fix 了一个小 bug，具体如下
mangye16/ReID-Survey#7
所以导致 non-local 部分参数有变动，所有出现 pre-train model 无法 load 进去的问题。

感谢！另外请教下 sbs 设置 NUM_INSTANCE: 16 是和数据集有关么？我改成4之后在验证集上经常会越跑越差

这个和 circle loss 有关

@clw5180 请问msmt数据集是在哪儿下的呢？


BUG: Adding coins doesn't work, symbols missing and sheet cut off.

(Google Translator) Hello! I was waiting for the update and I loved the changes. I noticed that generating coins in sheets is not working! Either by adding it through the form itself or configuring it to be added automatically.
Another issue is that I don't know if it's intentional, but there are two symbols that appear as "squares", but I imagine it must be another one.
*Here on the button to pick up a unique item:

*Here in two places in the permissions section and in the dark theme:

Finally, when the sheet is opened, its automatic size cuts part of the coins at the bottom of it.

Foundry Virtual Tabletop: Version 9, 9.249
Game System: dnd5e, 1.5.7
Active Modules: 4
Performance Mode: 3

OS: Unknown
Client: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.82 Safari/537.36
GPU: ANGLE (NVIDIA, NVIDIA GeForce GTX 1660 Direct3D11 vs_5_0 ps_5_0, D3D11-<IP_ADDRESS>5)
Max Texture Size: 16384

Scene: 3000 x 3000 | Grid Size: 100 | Padding Percentage: 0
Walls: 0 | Ambient Lights: 0 | Ambient Sounds: 0 | Tiles: 0 | Tokens: 2

Actors: 89 | Items: 32 | Journal: 0 | Rollable Tables: 3 |
Playlists: 0 | Compendium Packs: 19 | Chat Messages: 2

Desktop (please complete the following information):

OS: Windows 10
Browser: chrome
Version: last

I think I must be doing something wrong, but I just can't generate coins in the sheet! I tested several configurations.

Here is what I have

Please make sure your on version 3.5.7


Add Javascript Support

Instead of JSON and YAML, I'd prefer to use a JavaScript module. For example, instead of this JSON:
{
  "scripts": {
    "start": "deno run --allow-net server.ts",
    "test": "deno test --allow-net server_test.ts"
  }
}

or this YAML:
# scripts.yaml
scripts:
  start: deno run --allow-net server.ts
  test: deno test --allow-net server_test.ts

I prefer this:
let options = {};
options.scripts = {};
options.scripts.start = "deno run --allow-net server.ts";
options.scripts.test = "deno test --allow-net server_test.ts";
export options;

Granted, my preference is more verbose. However, nothing is more flexible. You could do anything you wanted (programmatically) within this file and Velociraptor should only care about the object that gets exported at the end.

@Lonniebiz Created a PR. Waiting for it to be merged.

Thanks @Lonniebiz for the proposal and @divy-work for the PR!
I wouldn't mind adding this functionality (I initially considered it), but let me just share some considerations about this:

they're effectively Deno scripts and therefore could need some permissions that vr may not have. This essentially would require all permissions to be granted to vr at install time. Probably not a big deal (also the install command would be much shorter), but I was trying to avoid it if possible...
.js configuration files are commonly used, but since Deno's main language is TS wouldn't it be more appropriate to use .ts files? (or at most both of them?)
Every time .ts config files are compiled you would get a bunch of Deno logs which interfere with the output of launched scripts (don't know if it's possible to add the -q flag to an installed script though).

What do you think?

You can support TS, as well, if you like, but since ES6 (where ES Modules and Classes were added to the spec), I personally consider TypeScirpt an antiquated unneeded technology. I'm personally completely against these fake static types that ultimately compile to javascript (which really doesn't have static types, or need them). I feel like everyone has become brainwashed by static type propaganda promoted by a Billion dollar company trying to become the go to place for coding. I know, shocking, huh? I'm sorry to hold back. Here's what I really think.

these config files are effectively Deno scripts and therefore could need some permissions that vr may not have. This essentially would require all permissions to be granted to vr at install time. Probably not a big deal (also the install command would be much shorter), but I was trying to avoid it if possible...

That is true and inevitable. To avoid perm errors the install command must give all perms (which seems fair).

.js configuration files are commonly used, but since Deno's main language is TS wouldn't it be more appropriate to use .ts files? (or at most both of them?)

Yup. I've just added that to the PR.

Every time .ts config files are compiled you would get a bunch of Deno logs which interfere with the output of launched scripts (don't know if it's possible to add the -q flag to an installed script though).

Maybe it is better to let the user know that the config scripts are compiled at runtime so they should expect compile logs from Deno. Though it won't actually interrupt other logs as it is the compiled before any of the configs is processed.
Overall, I think this would be a good feature to introduce as it provides a more dynamic way to make config files.

@Lonniebiz I'm not against you. Keeping whole of Deno community in mind...TS is necessary

@umbopepato This can be closed now.

Just a note: for the moment code assistance in .ts configuration files is obtained by manually applying the ScriptsConfiguration type but this will (hopefully) be handled automatically by the editor extensions.

Just to be clear. This will allow me to accomplish the configuration in a .js file correct? The updated documentation only shows typescript. @divy-work

This will allow me to accomplish the configuration in a .js file correct?

@Lonniebiz no, we're supporting only .ts for the reasons discussed above. You can write JS in TS files though. Also, when this is implemented you will get code assistante for the configuration object without needing to manually add types.


Update docker image location in docs

I used haishanh/cherry docker image to deploy. But not able to use chrome extension, it showed  400 error on /api/bookmark url.
After I changed image to the one from the github, extension started working

Thanks.


Migration script for Data Management

This script is an interactive process, and should be run step-by-step:

It grabs all datasets and makes a CSV file with all combinations of (Institution, Submitter Email, Submitter Name, PI Email, PI Name) for manual clean up. This is needed because it later makes users and groups based on the Submitters, PIs and Institutions, and the details need to be consistent.
After importing the cleaned up data it validates it and updates the datasets in the DB, then triggers an ES update for them.
It dumps a list of all combinations of Institution and Submitter/PI for manual clean up.
It uses the cleaned up Institutions / Users to add users to groups and assign them a role

This script will need some more work before it's ready for use:

I'll need to double-check with someone else that the data clean-ups are valid
After #51 is merged I need to check compatibility with the ESExporter.update_ds function
It will need to be updated for any upcoming ElasticSearch and DB schema changes

All looks good for one time run script. I'd propose not to merge this PR until we're done with other features for the release.

I've pushed some changes:

A bug fix to look up users by not_approved_email as well as email
It now just completely removes the old Submitted_By fields from metadata, as we're no longer doing a live upgrade
Made all datasets group_approved

I'm merging this as the other features are mostly complete, so this is unlikely to have any further changes.


Upgrade to client-go version 6

ks is running on client-go version 3. It's probably time we upgrade.

Closing in favor of #396


pkg_resources can't find entry points with nosetests. but it can with unittest, noses

I'm trying the md3 branch...
When executing nosetests (actually, nosetests markdown/test.py) , the pkg_resources.iter_entry_points call in build_extension function of markdown/core.py can't find entry points for any extensions. But it works with unittest and nose2. Maybe it's a problem of nose...
I think those file tests are useful since they seems more extensive than those unittests.

The md3 branch is no longer being maintained. Any and all work in the md3 branch which is being retained has been merged with the master branch.


Log the wallet git revision on startup

Fixes: #1540

One suggestion (which is not super critical) and then LGTM


Lag when accepting a completion item

Make sure you have done the following

[X] I have updated to the latest version of blink.cmp
[X] I have read the README

Bug Description
I have a big (around 40k lines of code) Playwright project which heavily uses test fixtures which have a noticeable effect on the performance of the LSP server for TypeScript.
I have noticed lag after accepting a completion item, it takes around 1 or 2 seconds and any text written after accepting the completion item is removed when the completion item is inserted.
The wait for the completion items to show up in the completion list is expected (I also have the same issue with nvim-cmp which is probably the fault of the LSP) but the lag after accepting a completion item in which I cannot write anything because it will be removed after the completion item is inserted seems like an issue with blink.cmp (I haven't seen it when using nvim-cmp).
Here is a recording of the issue:
https://github.com/user-attachments/assets/774656d9-5e03-47aa-8369-e4b5c922d713
Relevant configuration
You can see my configuration here: https://github.com/datwaft/nvim.conf/blob/d834a1b01457ddcb34f6644efd1caa345d1182e4/lua/packages/completion.lua
If it is relevant I am accepting with <space> and have the following completion configuration:
completion = {
  list = {
    selection = "manual",
  },
  accept = {
    auto_brackets = {
      enabled = false,
    },
  },
},

neovim version
NVIM v0.11.0-dev-1369+gb03e790cdd
blink.cmp version: branch, tag, or commit
main (c3ef9223a69ededed611b3ef617bac5651b87833)

When you get the change, open ~/.local/share/nvim/lazy/blink.cmp/lua/completion/accept/init.lua and check how long the .resolve call takes. You can use vim.uv.hrtime() to get the current time (in nanoseconds)

I modified ~/.local/share/nvim/lazy/blink.cmp/lua/blink/cmp/completion/accept/init.lua like this:

Here are some of the results:
It took 17583 nanoseconds for `accept`
It took 19333 nanoseconds for `accept`
It took 52500 nanoseconds for `accept`
It took 834666 nanoseconds for `accept`
It took 834750 nanoseconds for `accept`
It took 751750 nanoseconds for `accept`
It took 1170625 nanoseconds for `accept`

Because of how the printed time is growing I think I am doing something wrong, any suggestions?

Btw, I haven't tried the new commit. I am going to use it and see if it helps.

Sorry I should've clarified, put the print inside the :map

NOTE: I am still seeing the lag sometimes.

Haha, once again I should've clarified :joy: The start_time should be before the .resolve and the end_time should inside the :map so we can see how long that async call takes. Sorry for the back and forth on this

😅 🤣
Here are the new results:
It took 408560458 nanoseconds for `accept`
It took 824164041 nanoseconds for `accept`
It took 346669333 nanoseconds for `accept`
It took 25417 nanoseconds for `accept`
It took<PHONE_NUMBER> nanoseconds for `accept`
It took 363493625 nanoseconds for `accept`

It seems like all of those are 1ms or under so they seem to be cached. Did you notice any of these accepts lagging?

It seems like nvim-cmp ignores the resolve if it takes more than 80ms by default, whereas yours are taking up to 1s


#4664 Moved Main Activity and Settings Activity to ViewBinding

Related to #4664
What changes did you make and why?
Moved the MainActivity and SettingsActivity from Butterknife to ViewBinding
Tests performed (required)
Tested prodDebug on OnePlus Nord CE 2 Lite with API level 31

Hmm, I'll check why unit tests are failing

Just for reference, a lot of the unit tests avoid taking the UI through its normal lifecycle and try to mock components instead.  There's a lot of reflection to jam the mock values into place.  A few recent Fragment tests do it correctly using the Google FragmentScenario so you might look at those as a template.

Just for reference, a lot of the unit tests (mistakenly) avoid taking the UI through its normal lifecycle and try to mock components instead. There's a lot of reflection to jam the mock values into place. A few recent Fragment tests do it correctly using the Google FragmentScenario so you might look at those as a template.

Thank you so much @psh, I'll look into this :)


refactor: 1 struct per file

Fixes #4410

Current dependencies on/for this PR:

#4693  👈
master

This stack of pull requests is managed by Graphite.

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 9cb6daff and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
54,212
214,436
855,332

l1_rollup_calldata_gas
259,892
1,019,612
4,059,728

l1_rollup_execution_gas
354,078
1,139,060
4,281,129

l2_block_processing_time_in_ms
1,259 (-1%)
4,734 (-1%)
18,772 (-1%)

note_successful_decrypting_time_in_ms
218 (-3%)
605 (-2%)
2,168 (-4%)

note_trial_decrypting_time_in_ms
27.3 (-37%)
41.7 (-29%)
184 (-7%)

l2_block_building_time_in_ms
21,337
84,554
343,390

l2_block_rollup_simulation_time_in_ms
15,999
63,425
259,048

l2_block_public_tx_process_time_in_ms
5,311 (-1%)
21,047 (-1%)
84,097 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
16,276
33,428 (+5%)

note_history_successful_decrypting_time_in_ms
1,413
2,753 (+1%)

note_history_trial_decrypting_time_in_ms
177 (+4%)
237 (+5%)

node_database_size_in_bytes
18,645,072
35,864,656

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
335 (+1%)
44,664
27,457

private-kernel-ordering
216
45,777
14,627

base-rollup
1,742
175,344
933

root-rollup
82.8
4,192
825

private-kernel-inner
447
73,099
27,457

public-kernel-app-logic
274
32,254
25,379

merge-rollup
7.82 (-1%)
2,712
933

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
15,388
36,001

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
579
1,515

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
0.0289 (-11%)
653


Add thread flag to Denoise options

Is this already implemented?
If so it isn't working because I got the latest version of the addon (downloaded a few minutes ago to test the animated texture sequence rendering) and the denoiser is still maxing my CPU.
So my guess is that it isn't yet, but I thought I'd ask just in case.

Should be:
https://github.com/bsavery/PRMan-for-Blender/blob/master/engine.py#L408
On Sun, Apr 24, 2016 at 11:21 AM, JeannotLandry<EMAIL_ADDRESS>wrote:

Is this already implemented?
If so it isn't working because I got the latest version of the addon
(downloaded a few minutes ago to test the animated texture sequence
rendering) and the denoiser is still maxing my CPU.
So my guess is that it isn't yet, but I thought I'd ask just in case.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/bsavery/PRMan-for-Blender/pull/240#issuecomment-214017126

--
<EMAIL_ADDRESS>508-274-8700

It uses the prman thread setting, which by defualt is -1 (all cores -1)
On Sun, Apr 24, 2016 at 11:22 AM, Brian Savery<EMAIL_ADDRESS>wrote:

Should be:
https://github.com/bsavery/PRMan-for-Blender/blob/master/engine.py#L408
On Sun, Apr 24, 2016 at 11:21 AM, JeannotLandry<EMAIL_ADDRESS>wrote:

Is this already implemented?
If so it isn't working because I got the latest version of the addon
(downloaded a few minutes ago to test the animated texture sequence
rendering) and the denoiser is still maxing my CPU.
So my guess is that it isn't yet, but I thought I'd ask just in case.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/bsavery/PRMan-for-Blender/pull/240#issuecomment-214017126

--
<EMAIL_ADDRESS>508-274-8700

--
<EMAIL_ADDRESS>508-274-8700

Brain, the default settings for rendering of -1 brings my CPU to 88 %, but denoiser still brings my CPU to 99%.

I'll try with -2 see if it'll make a difference.

You might try setting it manually to however many cores you have on your
system
i.e. if you have 8 cores set it to 7 or 6
On Sun, Apr 24, 2016 at 11:33 AM, JeannotLandry<EMAIL_ADDRESS>wrote:

I'll try with -2 see if it'll make a difference.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/bsavery/PRMan-for-Blender/pull/240#issuecomment-214020364

--
<EMAIL_ADDRESS>508-274-8700

I'll give that a quick try. I've tested it with -4 and same thing, PRMan took 48% of CPU and the denoiser took 99%. I'll try entering the number instead of the -1 and let you know.

Yup, that worked, I've set it to 6 (I have 8 cores) and PRMan took 75% of the CPU and the Denoiser as well :) So it doesn't work with the - feature, but it works if you set it manually with a positive number :)
This will have to be specified in the documentation once that is on the way ;) Awesome :) Thanks Brian.
Unrelated question, I would like a to create a few video tutorials to help people get started with this amazing addon and renderman non-commercial. Any ideas on subjects that could be helpful for everyone? If you want you can e-mail me directly on this<EMAIL_ADDRESS>

Brian, unless you have a major concern I will merge this item.


I want to add Rock Paper Scissors Game.

I wish to add a Rock Paper Scissors Game into this repository which i made using HTML, CSS and JavaScript.
Please assign it to me so that i can work on it.
Thank You...

can assign to me?

@subhasish-roy  Welcome to Metaverse!!!!!!!!!🥳
Thanks For raising the Issue. 👍

Please follow contributing.md file for the contribution details

thank you for assigning. will do that.


Frame.GetContentAsync() return content before javascript execution

Frame.GetContentAsync() return content before javascript execution, i want the complete content after javascript executed(at the time of the method call)
Complete minimal example reproducing the issue
E.g.
var content = page.Frames[0].GetContentAsync().GetAwaiter().GetResult();

Expected behavior:
Should return code after javascript execution.
Actual behavior:
Versions

Which version of PuppeteerSharp are you using?
Which .NET runtime and version are you targeting? E.g. .NET framework 4.6.1 or .NET Core 2.0.

Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

@KardoseR You should try to find some hint which tells you that it finished.
Any DOM element you can use with a WaitForSelectorAsync? Any javascript code you can evaluate with WaitForExpressionAsync?
Once you find that it would be a matter of using the right waitFor and then call GetContentAsync.
Also, remember to use await instead of GetAwaiter().GetResult();.

I know the content is already loaded because i can inspect it in the chromium window, i call that method way after that happens...

@KardoseR did you try any of these?

Any DOM element you can use with a WaitForSelectorAsync? Any javascript code you can evaluate with WaitForExpressionAsync?

GetContentAsync calls document.documentElement.outerHTML internally. If you run that on DevTools, do you get what you expect?

So most of the puppeteer commands can be translated to javascript calls? No I dont get what I want because I am trying to query an iframe, in selenium I would call driver.SwitchTo().Frame(0); and then driver.PageSource to get the desired result.

So In short, i would like to be able to get the same result as I would with selenium

WaitForSelectorAsync or WaitForExpressionAsync should help you accomplish what you need.


release_build: Remove log output and hardcoded date

The wget log output is too long and the date needs to be dynamic.
Other topic: I see that an old 202309 release was used to fetch previous assets. Let's delete those.

Started a new run to see that it uses the last release: https://github.com/flatcar/sysext-bakery/actions/runs/7890342342

Nice how quick it finished :heart_eyes: - also reduces environmental impact :seedling: ;)


Update keycloak-core to 25.0.0 in scala-steward-dependencies

About this PR
📦 Updates org.keycloak:keycloak-core from 24.0.5 to 25.0.0 ⚠
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.keycloak", artifactId = "keycloak-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.keycloak", artifactId = "keycloak-core" }
}]

labels: library-update, early-semver-major, semver-spec-major, commit-count:1

Not updating to Keycloak Core v25 until tested


react-native-gradle-plugin

Description
node_modules/react-native-gradle-plugin has name 'react-native-gradle-plugin' which is the same as a project of the main build.
React Native Version
0.71.4
Output of npx react-native info
System:
OS: macOS 13.2.1
CPU: (8) arm64 Apple M2
Memory: 271.20 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 19.4.0 - /opt/homebrew/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 9.2.0 - /opt/homebrew/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.3 - /Users/sahandmahdavi/.rvm/gems/ruby-2.7.5/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: 11.0.17 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.4 => 0.71.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce

build.gradle:

apply plugin: "com.facebook.react"
react {
/* Folders */
//   The root of your project, i.e. where "package.json" lives. Default is '..'
root = file("../")
//   The folder where the react-native NPM package is. Default is ../node_modules/react-native
reactNativeDir = file("../node_modules/react-native")
//   The folder where the react-native Codegen package is. Default is ../node_modules/@react-native/codegen
codegenDir = file("../node_modules/@react-native/codegen")
//   The cli.js file which is the React Native CLI entrypoint. Default is ../node_modules/react-native/cli.js
cliFile = file("../node_modules/react-native/cli.js")
/* Variants */
//   The list of variants to that are debuggable. For those we're going to
//   skip the bundling of the JS bundle and the assets. By default is just 'debug'.
//   If you add flavors like lite, prod, etc. you'll have to list your debuggableVariants.
// debuggableVariants = ["liteDebug", "prodDebug"]

/* Bundling */
//   A list containing the node command and its flags. Default is just 'node'.
// nodeExecutableAndArgs = ["node"]
//
//   The command to run when bundling. By default is 'bundle'
// bundleCommand = "ram-bundle"
//
//   The path to the CLI configuration file. Default is empty.
// bundleConfig = file(../rn-cli.config.js)
//
//   The name of the generated asset file containing your JS bundle
// bundleAssetName = "MyApplication.android.bundle"
//
//   The entry file for bundle generation. Default is 'index.android.js' or 'index.js'
// entryFile = file("../js/MyApplication.android.js")
//
//   A list of extra flags to pass to the 'bundle' commands.
//   See https://github.com/react-native-community/cli/blob/main/docs/commands.md#bundle
// extraPackagerArgs = []

/* Hermes Commands */
//   The hermes compiler command to run. By default it is 'hermesc'
// hermesCommand = "$rootDir/my-custom-hermesc/bin/hermesc"
//
//   The list of flags to pass to the Hermes compiler. By default is "-O", "-output-source-map"
// hermesFlags = ["-O", "-output-source-map"]

}

settings.gradle:

includeBuild('../node_modules/react-native-gradle-plugin')
if (settings.hasProperty("newArchEnabled") && settings.newArchEnabled == "true") {
include(":ReactAndroid")
project(":ReactAndroid").projectDir = file('../node_modules/react-native/ReactAndroid')
}
Snack, code example, screenshot, or link to a repository

build.gradle:

apply plugin: "com.facebook.react"
react {
/* Folders */
//   The root of your project, i.e. where "package.json" lives. Default is '..'
root = file("../")
//   The folder where the react-native NPM package is. Default is ../node_modules/react-native
reactNativeDir = file("../node_modules/react-native")
//   The folder where the react-native Codegen package is. Default is ../node_modules/@react-native/codegen
codegenDir = file("../node_modules/@react-native/codegen")
//   The cli.js file which is the React Native CLI entrypoint. Default is ../node_modules/react-native/cli.js
cliFile = file("../node_modules/react-native/cli.js")
/* Variants */
//   The list of variants to that are debuggable. For those we're going to
//   skip the bundling of the JS bundle and the assets. By default is just 'debug'.
//   If you add flavors like lite, prod, etc. you'll have to list your debuggableVariants.
// debuggableVariants = ["liteDebug", "prodDebug"]

/* Bundling */
//   A list containing the node command and its flags. Default is just 'node'.
// nodeExecutableAndArgs = ["node"]
//
//   The command to run when bundling. By default is 'bundle'
// bundleCommand = "ram-bundle"
//
//   The path to the CLI configuration file. Default is empty.
// bundleConfig = file(../rn-cli.config.js)
//
//   The name of the generated asset file containing your JS bundle
// bundleAssetName = "MyApplication.android.bundle"
//
//   The entry file for bundle generation. Default is 'index.android.js' or 'index.js'
// entryFile = file("../js/MyApplication.android.js")
//
//   A list of extra flags to pass to the 'bundle' commands.
//   See https://github.com/react-native-community/cli/blob/main/docs/commands.md#bundle
// extraPackagerArgs = []

/* Hermes Commands */
//   The hermes compiler command to run. By default it is 'hermesc'
// hermesCommand = "$rootDir/my-custom-hermesc/bin/hermesc"
//
//   The list of flags to pass to the Hermes compiler. By default is "-O", "-output-source-map"
// hermesFlags = ["-O", "-output-source-map"]

}

settings.gradle:

includeBuild('../node_modules/react-native-gradle-plugin')
if (settings.hasProperty("newArchEnabled") && settings.newArchEnabled == "true") {
include(":ReactAndroid")
project(":ReactAndroid").projectDir = file('../node_modules/react-native/ReactAndroid')
}

node_modules/react-native-gradle-plugin has name 'react-native-gradle-plugin' which is the same as a project of the main build.

Closing as duplicate of https://github.com/facebook/react-native/issues/36649


add state_unavailable to sensor update.

Dismissing test (3.8) since it is not related to this PR.


redux-form-material-ui requires redux-form npm build warning

After running npm build for the first time the following warning appears;
npm WARN<EMAIL_ADDRESS>requires a peer of redux-form@6 but none was installed.
Is it safe to ignore this warning?

Both packages are in dependencies. So you could ignore it.


use ghodds yaml

This is a first step that will allow us to start using the openshift v1 structs and remove the ones we've created by hand.
Those structs use json tags so we need to use a yaml library that will respect those instead of yaml tags since we need to print yaml

I need to edit one more file before all tests will pass. Should have it ready to go shortly.

Tests should pass now.
I added a commit for the Registries transform demonstrating how to replace the custom structs with the openshift/api/config/v1 struct


AllJoyn Explorer source code

Hi,
I am trying to develop a UWP application using C# that will discover all AllJoyn producers on the network and create consumer objects for communicating with the devices(producers). It's going to be pretty much like the AllJoyn Explorer.
Is the source code for the AllJoyn Explorer available for developers?
If not can I get some insight or guides to writing such a program?

We are currently not planning to release AllJoynExplorer as source.
However, AllJoynExplorer uses the following source to enumerate and interact with AllJoyn devices: https://github.com/ms-iot/samples/tree/develop/AllJoyn/Platform/DeviceProviders

@zhuridartem Are you guys looking into providing this library as a nuget package for easy consumption? If not I'll be happy to do that, but figured I would ask the owners first. the DeviceProviders library is hugely useful for generic device consumers.

+1 for making the AllJoynExplorer source available.  I've also started a customized version of something similar.  Given this is an app that basically everyone developing for AllJoyn on Windows uses, I think there would be great value in making it available as a reference project.

I put up a nuget package of the DeviceProviders here: https://www.nuget.org/packages/dotMorten.AllJoyn.DeviceProviders I hope you're ok with this.
Still it would be great with an official package released by Microsoft, but I'm happy to maintain this package too.

Closing.
Please use dotMorten's NuGet DeviceProviders or get the source from link above for generic AllJoyn enumeration.

Thanks guys. You made my final year project a success. :+1:
I also found @dotMorten's tutorial on hackster.io very useful.

@koapeadu Glad you found it useful. I just published another library that builds on top of the device providers lib and exposes the common AllJoyn devices in an easy to use way: http://github.com/dotmorten/AllJoynClientLib


Fix clippy issues in tests and add to CI

There were some "errors" detected with explicitly dropping Copy values (mostly I think to discard unchecked Results), the rest is just minor stylistic cleanups that doesn't matter much, but still makes some tests a little more readable.

Looks great, thanks!


move oauth2 token classes to auth_core from zts_core

For structured JWT access token format - we're now following - https://tools.ietf.org/html/draft-bertocci-oauth-access-token-jwt-00

👍


Require annotations option

Implemented annotations selector on pods similarly to the required labels selector. I went ahead and updated the docs and option test. Let me know what you think or if anything should be changed.

Hey, thanks for the review. I fixed everything you commented on.

This is weird case to me... but for a really specific reason that I remember running into about 3 years ago when working on a platform style project within kubernetes that wanted to use some form of selecting pods.
I explicitly remember digging into the differences between labels and annotations, and in the case of what pod-reaper is doing, labels were clearly the way to go. They're used to efficiently run selection queries on the API. In this case, we we'd be running a larger (more broad) query against the API and then filtering out pods based on the pods annotations. In short, I'm pretty confident that labels are the way to go... HOWEVER...
I also remember running into situations with a certain orchestration tool (Spinnaker) that didn't really allow users full control over pod labels and annotations. It's been a long while since I've looked at spinnaker, so I'm not sure if they've actually addressed that or not, but there are likely other tools out there that are abstracting away people's abilities to define what they want in pod layouts.
So in short, my take is: labels are better for this than annotations, but I understand there are situations where this is going to work and the performance hit is pretty unlikely to matter to almost anyone.

For transparency -- looks like spinnaker made the label issue I commented on 3 years ago obsolete around 2 years ago with v2:
https://github.com/spinnaker/spinnaker/issues/1624#issuecomment-308165818

Well I hope this PR doesn't become obsolete 🙂
I don't see too much of an issue keeping it as an option if users need it. Guess it's still up to you if you want to merge it or not.

I don't see too much of an issue keeping it as an option if users need it. Guess it's still up to you if you want to merge it or not.

I've got you! I'm on it :)

Release 2.8.0 when everything clears through CI/Docker builds


Can you share NTIRE2021 HDR dataset to me? My email is<EMAIL_ADDRESS>

Please refer to the NTIRE2022 HDR Challenge to get the dataset.

The training data is only made available to the registered participants. I can not get this dataset from the website.Please share the data.Thanks.


Alerts Section --> Query Builer --> Filter dropdown doesn't work . Not able to change "IS NOT NULL"

What happened:
Dropdown are broken
What you expected to happen:
Dropdown filter works
How to reproduce it (as minimally and precisely as possible):

Go to the Alerts Section
Open Query Builer
Add a new Filter and select a Field
Tryi to change "IS NOT NULL" or "IS ANYTHING" to another option

It should change and give the posibility to configure the filter
It's happens using a ClickHouse Datasource.

Interesting, it looks like the dropdown appears but a new option isn't selected. This is likely something with the state management of the plugin/query. I haven't tested the query builder on this page before so there's likely some differences with this vs the explore/dashboard views.


Make perfLogger potentially undefined rather than using a noop logger

Effectively 100% of the time, ETW has not been loaded. Rather than using a noopLogger object, instead make perfLogger undefined when ETW isn't loaded, and reference with ?. just like our other tracing API. This should be faster, and hopefully observable since we trace some of our most-called APIs like file reads/writes, parsing/binding, module resolution, etc.

@typescript-bot perf test this

Seems like nearly no perf change (which I kind of figured anyway since the JIT will quickly inline noops out of existence).  That said, ?. conveys what's actually happening much better.

Yes, I'd want this to be merged regardless of perf.

I'm almost surprised this didn't hurt perf, since it theoretically adds branching costs

The runtime is surprisingly good at figuring out the downleveled ?.; my own perf testing had shown that even a ternary on null/undefined was faster than ||!

This use to be big perf issue where if you did undefined check before calling function it would be slower compared to noop function. Looks like its not anymore ? @rbuckton might know more if thats true as i havent followed changes to this from runtime perspective to know if it impacts perf or not in recent runtimes.

We did this for tracing back in #42323, so, if there were any perf gotchas, I think they are all solved at this point.


Submission Form - cannot edit uploaded file because Group field is mandatory and has no input values in drop-down

I submit a new Article item.
I upload a file.
In the 'Upload Files' section I add a description, choose 'embargo' as access condition type and choose the dates.
However, The Group field is mandatory, but there are no values to choose from in the drop-down - hence I cannot save any of the previously-entered file metadata.

Thanks, this is a duplicate of #869 (which we are currently working on).  Closing as a duplicate

Thanks, this is a duplicate of #869 (which we are currently working on).  Closing as a duplicate


Ci coverage adjustments

Pull Request Checklist:

[ ] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #xyz

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Documentation has been added / updated (for bug fixes / features)
[ ] HISTORY.rst has been updated (with summary of main changes)

[ ] Link to issue (:issue:number) and pull request (:pull:number) has been added.

[ ] bumpversion patch has been called on this branch
[ ] The relevant author information has been added to .zenodo.json

What kind of change does this PR introduce?

adds the doctests build to the needed builds for CI suite
slight adjustment to the largely neglected makefile

Does this PR introduce a breaking change?
No
Other information:
Coveralls (https://coveralls.io/github/Ouranosinc/xclim) has been adjusted to be a little less discouraging, but a bit more strict (Coveralls will now be a required check). PRs now require the following:

Coverage decreases can be no more than 0.25% from master
Coverage total must remain above 90%

Failing either of these conditions means the PR will be blocked from merging.
Additionally, Codefactor is now permanently ignoring "Complex Method" (Flake8: C901). This isn't great, but we're doing some relatively complex stuff, so let's be easy on ourselves.

Coverage remained the same at 90.318% when pulling 0ea9fa49205b4a78031ed85adc6906ab256c3a91 on ci_coverage_adjustments into abc13c4c19546c3055089ef76737168b2f8b80df on master.

Settings don't seem to be working as expected. Cross-referencing the issue: https://github.com/lemurheavy/coveralls-public/issues/1505


Update kafka to 1.17.3

Updates org.testcontainers:kafka from 1.17.1 to 1.17.3.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.testcontainers", artifactId = "kafka" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.testcontainers", artifactId = "kafka" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, commit-count:1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
92 unchanged lines in 8 files lost coverage.
Overall coverage decreased (-23.9%) to 51.706%

Files with Coverage Reduction
New Missed Lines
%

core/src/main/scala/io/aiven/guardian/kafka/Errors.scala
1
0%

cli-backup/src/main/scala/io/aiven/guardian/kafka/backup/App.scala
3
0%

core-cli/src/main/scala/io/aiven/guardian/cli/MainUtils.scala
4
0%

core-restore/src/main/scala/io/aiven/guardian/kafka/restore/KafkaProducer.scala
6
18.18%

restore-s3/src/main/scala/io/aiven/guardian/kafka/restore/s3/RestoreClient.scala
8
0%

core-backup/src/main/scala/io/aiven/guardian/kafka/backup/KafkaClient.scala
13
44.44%

core-backup/src/main/scala/io/aiven/guardian/kafka/backup/BackupClientInterface.scala
14
75.68%

backup-s3/src/main/scala/io/aiven/guardian/kafka/backup/s3/BackupClient.scala
43
0%

Totals

Change from base Build<PHONE_NUMBER>:
-23.9%

Covered Lines:
197

Relevant Lines:
381

💛  - Coveralls


Fix gatling configuration not being resolved.

This bug prevented from using environment variables in gatling.conf or any other dynamically resolved variables.

Thanks!


Reduce file watching to files/folders that are in use

Can we have a lazy watcher? i.e. it only scans the files directly under the current dir and does not go recursively and it would be invoked to scan once we open a dir in file explorer.
The reason is that we usually have tons of file in a project and also soft-link to other projects that can potentially create loops. And I notice that file scanning really cause vscode to consume too much CPU and mem at the starting.
Hence, while I do NOT want to exclude those folders as I occasionally need to dig into them to see if things are alright, I really want to have an option to keep vscode from crazily scanning my file systems and from freezing the system every time vscode is started.

That shouldn't be too hard to implement from our side, but contributions are appreciated.

I have the same problem:
[2020-02-04 08:24:31.581] [renderer4] [warning] [File Watcher (chokidar)] Watcher is busy catching up with 5385 file changes in 60 seconds. Latest changed path is "/Something/src/buck-out/gen/third-party/blablabla"
[2020-02-04 08:27:50.233] [renderer4] [warning] [File Watcher (chokidar)] Watcher is busy catching up with 6340 file changes in 60 seconds. Latest changed path is "/Something/src/buck-out/gen/blablabla"
[2020-02-04 08:34:26.292] [renderer4] [warning] [File Watcher (chokidar)] Watcher is busy catching up with 5348 file changes in 60 seconds. Latest changed path is "/Something/src/buck-out/bin/blablabla"
[2020-02-04 08:34:26.614] [renderer4] [warning] [File Watcher (chokidar)] Watcher is busy catching up with 5164 file changes in 60 seconds. Latest changed path is "/Something/src/buck-out/project_root/buck-out/bin/blablabla"

@bpasero only for your info in v4 this is changed its lobbyed :) https://github.com/paulmillr/readdirp/issues/105


Fix ros2 tutorials

fixes #483

I'm not getting a lot of feedback of the tests right now... it seems to build fine on my native install though?

Let me see if I can relieve some of the test fails. the ci failed because of flake8 (but this was not very easy to see in the logs now) so I fixed that, but there might be more in the code that needs fixing (perhaps better to do in another PR)

yeah! checks passed now. So it was all my fault :D I'll merge.


Redirect to Dashboard fragment instead of EventList Fragment on pressing back.

Describe the feature you'd like
When the user selects an event from the event list, he is taken to the dashboard fragment. Now if the user selects faq from navigation drawer and presses back after seeing faq, he is taken to event list fragment rather than Dashboard fragment. He again has to select the event from the list. Usually for the user, after selecting an event, he will think he is redirected to a new page, where if he selects any activity from Drawer,  then on pressing back, he will be redirected to dashboard. Redirecting to the list page gives an uneasy user experience.
Screenshots

Would you like to work on the issue?

[x] Yes
[ ] No
[ ] Other

@ShridharGoel @iamareebjamal  do you think this feature should be implemented or not ???
Will work on it accordingly...

I agree with this and this was the existing behaviour before the implementation was made to be changed from above

I agree with this and this was the existing behaviour before the implementation was made to be changed from above

On it !!!

Not on it. It should stay the same

I agree with this and this was the existing behaviour before the implementation was made to be changed from above

Sir are you agreeing with the current scenario or with my proposed scenario.

Your proposed scenario was already done in past and was the default behaviour and I agreed with it. But the requirements were changed to make it like the current scenario. So, I don't agree with the current scenario but it is working as intended

should i close this issue ?


[Android] In Mediapipe Hands: java.lang.RuntimeException: glClear: GL error: 0x501

I'm trying to render a Bitmap at the wrist coordinate of hand. So I'm following this solution. In HandResultGlRenderer.java I'm receiving the HandsResult in renderResult(HandsResult result, float[] projectionMatrix) function.
After getting the wrist coordinate I'm calling another function drawBitmap(landmark.getX(), landmark.getY(),bitmap)
Here's how drawBitmap() looks like:
  private void drawBitmap(float x, float y, Bitmap bitmap) {
    int textureId = loadTexture(bitmap);
    GLES30.glBindTexture(GLES30.GL_TEXTURE_2D, textureId);

    // Define the texture coordinates for the bitmap.
    float[] textureCoordinates = {
            0.0f, 1.0f,
            1.0f, 1.0f,
            0.0f, 0.0f,
            1.0f, 0.0f
    };

    // Define the vertex coordinates for the bitmap.
    float[] vertices = {
            x - (bitmap.getWidth() / 2.0f), y - (bitmap.getHeight() / 2.0f), 0.0f,
            x + (bitmap.getWidth() / 2.0f), y - (bitmap.getHeight() / 2.0f), 0.0f,
            x - (bitmap.getWidth() / 2.0f), y + (bitmap.getHeight() / 2.0f), 0.0f,
            x + (bitmap.getWidth() / 2.0f), y + (bitmap.getHeight() / 2.0f), 0.0f
    };

    // Enable vertex array and texture array.
    GLES30.glEnableVertexAttribArray(positionHandle);
    GLES30.glEnableVertexAttribArray(textureCoordinateHandle);

    // Update the vertex buffer and texture coordinate buffer.
    FloatBuffer vertexBuffer = ByteBuffer.allocateDirect(vertices.length*4)
            .order(ByteOrder.nativeOrder())
            .asFloatBuffer()
            .put(vertices);
    vertexBuffer.position(0);
    FloatBuffer textureCoordinateBuffer = ByteBuffer.allocateDirect(textureCoordinates.length*4)
            .order(ByteOrder.nativeOrder())
            .asFloatBuffer()
            .put(textureCoordinates);
    textureCoordinateBuffer.position(0);

    // Set the vertex and texture coordinate buffer for the shaders.
    GLES30.glEnableVertexAttribArray(positionHandle);
    GLES30.glVertexAttribPointer(positionHandle, 3, GLES30.GL_FLOAT, false, 0, vertexBuffer);

    GLES30.glEnableVertexAttribArray(textureCoordinateHandle);
    GLES30.glVertexAttribPointer(textureCoordinateHandle, 2, GLES30.GL_FLOAT, false, 0, textureCoordinateBuffer);

    // Draw the bitmap.
    GLES30.glDrawArrays(GLES30.GL_TRIANGLE_STRIP, 0, 4);

    // Disable vertex array and texture array.
    GLES30.glDisableVertexAttribArray(positionHandle);
    GLES30.glDisableVertexAttribArray(textureCoordinateHandle);

  }

And here is how loadTexture() looks like:
 private int loadTexture(Bitmap bitmap) {
    // Generate a new texture ID
    int[] textureIds = new int[1];
    GLES30.glGenTextures(1, textureIds, 0);

    // Bind the texture
    GLES30.glBindTexture(GLES30.GL_TEXTURE_2D, textureIds[0]);

    // Set the texture parameters
    GLES30.glTexParameteri(GLES30.GL_TEXTURE_2D, GLES30.GL_TEXTURE_MIN_FILTER, GLES30.GL_LINEAR);
    GLES30.glTexParameteri(GLES30.GL_TEXTURE_2D, GLES30.GL_TEXTURE_MAG_FILTER, GLES30.GL_LINEAR);
    GLES30.glTexParameteri(GLES30.GL_TEXTURE_2D, GLES30.GL_TEXTURE_WRAP_S, GLES30.GL_CLAMP_TO_EDGE);
    GLES30.glTexParameteri(GLES30.GL_TEXTURE_2D, GLES30.GL_TEXTURE_WRAP_T, GLES30.GL_CLAMP_TO_EDGE);

    // Load the bitmap into the texture
    GLUtils.texImage2D(GLES30.GL_TEXTURE_2D, 0, bitmap, 0);

    // Unbind the texture
    GLES30.glBindTexture(GLES30.GL_TEXTURE_2D, 0);

    // Return the texture ID
    return textureIds[0];
  }

But when I'm running the app, the camera is opening as usual, but I when bring my hand near the camera, the app crashes with the following error:
Error information
FATAL EXCEPTION: GLThread 9071
         Process: com.google.mediapipe.apps.hands, PID: 28664
         java.lang.RuntimeException: glClear: GL error: 0x501
         at com.google.mediapipe.glutil.ShaderUtil.checkGlError(ShaderUtil.java:175)
         at com.google.mediapipe.components.GlSurfaceViewRenderer.renderFrame(GlSurfaceViewRenderer.java:101)
         at com.google.mediapipe.solutioncore.SolutionGlSurfaceViewRenderer.onDrawFrame(SolutionGlSurfaceViewRenderer.java:84)
         at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1605)
         at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1284)

It's showing that the error is thrown from ShaderUtil.java, I couldn't debug the issue.
System information
I'm testing on my OnePlus9R

Android Version: 13
API Level: 33
OpenGL ES: 3.2
GPU Vendor: Qualcomm
GPU Renderer: Adreno(TM) 650 @ 670 MHz
Solution: Hands
Programming Language and version ( e.g. C++, Python, Java):

@ayushgdev kindly let me know about any update on this issue, I've been stuck with this issue for weeks

Hello @pritam-ghosh-dev
We are working on it however, GL errors are difficult to debug so it is taking more than median time. Please allow us sometime to debug the issue.

Thanks for looking over this issue

@pritam-ghosh-dev Can you please advice where/how the variable textureCoordinateHandle is defined?

@ayushgdev here is my setUp() method:
public void setupRendering() {
    program = GLES30.glCreateProgram();
    int vertexShader = loadShader(GLES30.GL_VERTEX_SHADER, VERTEX_SHADER);
    int fragmentShader = loadShader(GLES30.GL_FRAGMENT_SHADER, FRAGMENT_SHADER);
    GLES30.glAttachShader(program, vertexShader);
    GLES30.glAttachShader(program, fragmentShader);
    GLES30.glLinkProgram(program);
    textureCoordinateHandle = GLES30.glGetAttribLocation(program, "inputTextureCoordinate");
    samplerHandle = GLES30.glGetUniformLocation(program, "sampler");
    positionHandle = GLES30.glGetAttribLocation(program, "vPosition");
    projectionMatrixHandle = GLES30.glGetUniformLocation(program, "uProjectionMatrix");
    colorHandle = GLES30.glGetUniformLocation(program, "uColor");
  }

Thanks for this gist @pritam-ghosh-dev . Just initial thoughts, this seems like the glThread is getting spun up but after finishing the job, it is not able to return the results back to the main worker. We will get back to you shortly.

okay thanks

hi @ayushgdev any update on the issue?

Hello @pritam-ghosh-dev
This issue is coming from textureCoordinateHandle variable.
textureCoordinateHandle = GLES20.glGetAttribLocation(program, "inputTextureCoordinate");

The line above in setupRendering is returning -1. This means that the inputTextureCoordinate is not an active attribute in the program object, and thus it is not required.
To fix the error, you can simply put a check to use the textureCoordinateHandle only if it has a value > 0 at all references, like below:
if(textureCoordinateHandle > 0)
      GLES30.glEnableVertexAttribArray(textureCoordinateHandle);
...
...
if(textureCoordinateHandle > 0){
      GLES30.glEnableVertexAttribArray(textureCoordinateHandle);
      GLES30.glVertexAttribPointer(textureCoordinateHandle, 2, GLES30.GL_FLOAT, false, 0, textureCoordinateBuffer);
    }

hi @ayushgdev
got your point, made the necessary changes. But still getting the same error.

Commenting coz, stat:awaiting response tag wasn't removed

@pritam-ghosh-dev Have you added condition before this line as well?
GLES30.glEnableVertexAttribArray(textureCoordinateHandle);

There are 3 places in total where it needs to be added. I see two changes in the screenshot.

Yeah sorry, I missed that.
After I made the changes the app isn't crashing, but whenever a wrist is detected, the camera texture is becoming black. Maybe it's because no texture is assigned to the renderer.
I have limited knowledge of OpenGl, any idea on how to fix the camera getting black issue? @ayushgdev

Always happy to help. However, this issue is different than the original issue and the original errors have been resolved. To keep the context of the issue as relevant to the original issue as possible, may I suggest you close this issue and open another one?
This helps community and us to search through the issues in concise manner.

Thanks for the support, I have raised another issue with this continuation


Can we migrate TFS 2010 projects with history to Git using GitTfs-0.25.0? Kindly provide the steps.

To report a good issue, please verify that you validate these points:

[ ] you have read the documentation about command line options and advanced use cases
[ ] upgrade and test with the last version
[ ] specify the version you are using
[ ] include steps you followed to reproduce the problem
[ ] if the problem occurs when using a git-tfs command, please provide the output of the command when using the --debug command line option (providing a gist could be a clever idea ;))

That should be possible.
It depends on your TFVC history.
You should try to know.
Look at the doc. I can't answer better than what I have taken time to wrote
in the doc...

Thanks Phillippe for quick response. I will go through the doc and will be back.

Can you please let me know which kind of permissions require in TFS to clone the TFS projects because i am getting some unauthorized access issue.

Can you please let me know exact which kind of permissions require in TFS to clone the TFS projects because i am getting some unauthorized access issue. But i am able to see the list of branches by connecting the tfs through git command.

I'd like for git-tfs to be able to clone with read-only permissions (the same permissions that you would give to someone who is going to get a working copy of the code but never check in). I've only used git-tfs with admin privileges, though. It's likely that you're running into a permissions bug. Can you try running it again with the --debug flag and sharing the stack trace of the error?

i am able to connect TFS and able to see the branches which can be cloned, but while cloning. i am getting below error
error: a problem occurred when trying to clone the repository. Try to solve the problem described below.
In any case, after, try to continue using command git tfs fetch
System.NullReferenceException: Object reference not set to an instance of an object.
at Sep.Git.Tfs.Util.ChangeSieve.GetChangesToApply(Boolean forceGetChanges)
at Sep.Git.Tfs.Core.TfsChangeset.Apply(String lastCommit, IGitTreeModifier treeBuilder, ITfsWorkspace workspace, IDictionary2 initialTree, Action1 ignorableErrorHandler)
at Sep.Git.Tfs.Core.GitTfsRemote.<>c__DisplayClass21.b__20(ITfsWorkspace workspace)
at Sep.Git.Tfs.VsCommon.TfsHelperBase.WithWorkspace(String localDirectory, IGitTfsRemote remote, TfsChangesetInfo versionToFetch, Action1 action)    at Sep.Git.Tfs.Core.GitTfsRemote.WithWorkspace(TfsChangesetInfo parentChangeset, Action1 action)
at Sep.Git.Tfs.Core.GitTfsRemote.Apply(String parent, ITfsChangeset changeset, IDictionary2 entries, Action1 ignorableErrorHandler)
at Sep.Git.Tfs.Core.GitTfsRemote.FetchWithMerge(Int32 mergeChangesetId, Boolean stopOnFailMergeCommit, Int32 lastChangesetIdToFetch, IRenameResult renameResult, String[] parentCommitsHashes)
at Sep.Git.Tfs.Core.GitTfsRemote.Fetch(Boolean stopOnFailMergeCommit, Int32 lastChangesetIdToFetch, IRenameResult renameResult)
at Sep.Git.Tfs.Commands.Fetch.DoFetch(IGitTfsRemote remote, Boolean stopOnFailMergeCommit)
at Sep.Git.Tfs.Commands.Fetch.FetchRemote(Boolean stopOnFailMergeCommit, IGitTfsRemote remote)
at Sep.Git.Tfs.Commands.Fetch.Run(Boolean stopOnFailMergeCommit, String[] args)
at Sep.Git.Tfs.Commands.Clone.Run(String tfsUrl, String tfsRepositoryPath, String gitRepositoryPath)
Object reference not set to an instance of an object.

Sorry, I won't have to help you and the null ref exception is never really helpfull.
You will have to dig in the source code and help yourself :(

Looks like this issue can be closed due to a lack of further information


Ensure binder pulls in latest version of widget

Changed postBuild to include elements in Docket build file
Test show that now truncated data is sent instead of complete set

Go to https://mybinder.org/v2/gh/jerrysong1324/lux-binder/0f012da5556ddda36eed1da31f0b7f2631209de8 to test


Server Error: no parameter named 'weak_ssl'

Describe the Bug
Getting this error when running puppet agent using puppetlabs-apt version 9.0.2
Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'weak_ssl' (file: /etc/puppetlabs/code/environments/production/modules/apt/manifests/key.pp, line: 54) on Apt_key[legacy key] (file: /etc/puppetlabs/code/environments/production/modules/apt/manifests/key.pp, line: 54) on node
Expected Behavior
I expect to not get this error...
Environment
puppet version 7.3.1
puppetlabs-apt version 9.0.2
puppetlabs-stdlib 8.6.0

Also I have restarted the puppet server as mentioned in other issues here.

solved issue by issuing command:
puppet generate types --force
then restarting the puppet server


Update Docs

Hi,
Please update few things in docs:
In /etc/salt/pillar/ save a file called top.sls >> it should be /srv/pillar/
also:
<EMAIL_ADDRESS>>> /etc/systemd/system/salt-proxy.service
Regards,

Hi @compyy:

In /etc/salt/pillar/ save a file called top.sls >> it should be /srv/pillar/

The pillars directory can be wherever you want. pillar_roots specifies to the master should look: https://github.com/napalm-automation/napalm-salt/blob/master/master#L321-L323
The default location depends also on the platform. On windows, for example, for sure it will not be under /etc/salt/pillar or /srv/pillar.

<EMAIL_ADDRESS>>> /etc/systemd/system/salt-proxy.service

Again, this can be anything you want. Additionally, using the @ you can control the process per device, e.g.: systemctl start salt-proxy@deviceX and will start the process for deviceX without affecting the others.
In your environment, you can call that file what you feel comfortable with /etc/systemd/system/my-custom-irrelevant-name.service is equally valid.
If you notice anything that does not look sane, you are always welcome to submit a PR. If your changes are valid, they will get merged.
Let me know if you have any other concerns.
Mircea

Hello,
I agree but by default it goes into srv/pillar whereas in doc it says /etc/salt/pillar and it generates following error, which has no reference how to fix it, even if you google it.
No proxy key found in pillar or opts for id R1. Check your pillar/opts configuration and contents.  Salt-proxy aborted.
for Service part, i understand the concept of @ now, thanks.

I know @compyy.
Did you see https://www.nanog.org/sites/default/files/1_Ulinic_Network_Automation_At_v1.pdf? (Slide 21 in particular).
pillar_roots and file_roots are two of the most important options to be careful of in the master config. There are many other that may help you, see https://docs.saltstack.com/en/latest/ref/configuration/master.html
I emphasised how those two interact with the rest of the features. If they are not configured correctly, it is not going to work.
Hope that helps.

Ok thanks.


When v-for and ref are used in a parent component with a slot, ref is called repeatedly.

Vue version
3.2.47
Link to minimal reproduction
https://github.com/wht300/vue-error
Steps to reproduce
1、Create a component with a slot

<template>

        <slot></slot>

</template>

2、Do v-for :ref="refs.set" in LayoutWrap

<template>
  <LayoutWrap>
    on slot
    <template v-for="value in list" :key="value">

{{ value }}

    </template>

refs.length:{{ refs.length }}

  </LayoutWrap>

    on div
    <template v-for="value in list" :key="value">

{{ value }}

    </template>

refs2.length:{{ refs2.length }}

</template>

What is expected?
I think this is a Vue bug, the ref function should only be called once in the above case, refs.length should be equal to 3
What is actually happening?
refs.length // 303
System Info
No response
Any additional comments?
No response

I don't think you should use refs.length,but rather use list.length.refs.length and refs.set will loop until the maximum number of updates are reached.

I don't think you should use refs.length,but rather use list.length.refs.length and refs.set will loop until the maximum number of updates are reached.
In the real scenario, the v-for is a custom component.
For example, if you need to iterate through the refs when you submit, and you need to loop through the refs when you call the method expose  out of the custom component, then there will be a problem
like

<template>
  <LayoutWrap>
    on slot
    <template v-for="value in list" :key="value">
      <FormItem :ref="refs.set" :data=value>{{ value }}

    </template>
    <button @click="handleSubmit">submit</button>
  </LayoutWrap>
</template>

When the code runs to refs.forEach, the loop count will be > 3

I believe this is a problem with useTemplateRefsList.
https://github.com/vueuse/vueuse/blob/main/packages/core/useTemplateRefsList/index.ts
useTemplateRefsList is relying on onBeforeUpdate to reset the array, but that won't be called when the template ref is used inside a slot.
Using onBeforeUpdate to reset the array was a common approach for using template refs with v-for, but it couldn't work correctly inside a slot, so Vue 3.2.25 introduced a built-in solution: https://vuejs.org/guide/essentials/template-refs.html#refs-inside-v-for.
To explain in more detail what's happening:

App renders, also rendering its child LayoutWrap.
The template refs from :ref="refs.set" are called.
This changes refs.length. The {{ refs.length }} in the template triggers a re-render. Because it is in the slot, it is the LayoutWrap component that re-renders, not App.
The onBeforeUpdate is on App, not LayoutWrap, so that is not triggered.
Re-rendering LayoutWrap causes the :ref="refs.set" to run again. This adds all the same elements to the array again.
This takes us back to step 3. We keep going round and round until Vue detects the infinite recursion and bails out.

I believe this is a problem with .useTemplateRefsList
https://github.com/vueuse/vueuse/blob/main/packages/core/useTemplateRefsList/index.ts
useTemplateRefsList is relying on to reset the array, but that won't be called when the template ref is used inside a slot.onBeforeUpdate
Using to reset the array was a common approach for using template refs with , but it couldn't work correctly inside a slot, so Vue 3.2.25 introduced a built-in solution: https://vuejs.org/guide/essentials/template-refs.html#refs-inside-v-for.onBeforeUpdate``v-for
To explain in more detail what's happening:

App renders, also rendering its child .LayoutWrap
The template refs from  are called.:ref="refs.set"
This changes . The  in the template triggers a re-render. Because it is in the slot, it is the  component that re-renders, not .refs.length``{{ refs.length }}``LayoutWrap``App
The  is on , not , so that is not triggered.onBeforeUpdate``App``LayoutWrap
Re-rendering  causes the  to run again. This adds all the same elements to the array again.LayoutWrap``:ref="refs.set"
This takes us back to step 3. We keep going round and round until Vue detects the infinite recursion and bails out.

I agree with you that useTemplateRefsList  needs to take this situation into account, but at the same time, there is a problem with the call mechanism of refs.set in :ref="refs.set" on the vue side when it is inside a slot and inside an HTMLElement?
Or does it need to be explained in the documentation?

@wht300 if you don't use refs.length, will there still be this problem?Is this refs.length really necessary to use?

@wht300 if you don't use refs.length, will there still be this problem?Is this refs.length really necessary to use?

I think so.
In some business scenarios
when I call the expose method of a v-for-generated component via refs traversal, the
// Pseudocode, refs are generated from list v-for
const list=[1,2,3,4]
const errorNums=refs.value.map(item=>item.xxx()).filite(Boolean)
const isAllReady =list.length===errorNums.length

If refs.length has an exception, it may cause errorNums.length>list.length when refs.value.map operates, causing an unexpected bug

I don't see a Vue bug here. Using :ref with a function, the function will be called every time it re-renders. The function needs to take account of the case where the passed element or component hasn't changed. useTemplateRefsList isn't doing that.
The changes in 3.2.25 make useTemplateRefsList redundant anyway. If you use const refs = ref([]) with ref="refs" in the template (and likewise for refs2) it should work fine.

After reviewing the code, I now think it should be a lifecycleupdate issue, so I've re-raised an issue
look https://github.com/vuejs/core/issues/8153

After reviewing the code, I now think it should be a lifecycleupdate issue, so I've re-raised an issue
look https://github.com/vuejs/core/issues/8153


Add function to segment logs into user sessions

What are "User Sessions"?
Most user behavior services provide some definition of a user "session" and then segment the log stream into sessions for further behavior.  For example, LogRocket defines a session as:

A session is a series of user interactions on your site, beginning with the first page they visit and ending with either:
a.) a period of inactivity lasting longer than 30 minutes, or
b.) after the user has navigated away from your app for more than 2 minutes. This includes closing the tab or navigating to a different domain on the tab.
"Activity" is defined as any user mouse movement, clicks, or scrolls.
As an example, if your user visits your landing page, then your app, and then refreshes the page all within 30 minutes of each other without closing the tab, the entire experience is recorded in a single session. If the user returns back to your site after another hour, a new session recording starts from the moment that they do the first action.
LogRocket sessions also support recording across multiple tabs, so a user opening a link in your app in a new tab will count as the same session. This means that if your app is running in multiple tabs, each tab would need to be navigated away from in order to end a session after 2 minutes. Otherwise, it wouldn't end until a period of inactivity across all tabs lasting longer than 30 minutes.

Why do we need "User Sessions"?
Sessions are a particularly useful unit by which to analyze user behavior since they represent a logical clustering of activity. Answers to simple questions such as:

How long did the user's first session last?
How long are a user's session, on average?
What actions did the user perform in their session?
all provide quite a bit of insight into whether and how users engage with an application. Generally speaking, they are a great entry point to begin building one's understanding of UX in your app.

Proposed change
We should add a method that segregates the entire log stream into appropriate session buckets according to some definition of a "user session." It need not necessarily be the LogRocket definition shared above; however, I am proposing that as a reasonable starting point.

A key function for this already exists, detect_deadspace.
https://github.com/apache/flagon-distill/blob/9aafe6aace33d602cfcc9e509a6eb2126d1fa8a9/distill/segmentation/segment.py#L408
Doing a simple URL filter followed by a detect_deadspace call should produce user session segments as described.


Automate Individual Package Documentation Build

With the switch from monolithic gem to individual gems, we need to replace the previous build process that identifies new releases and generates the documentation. The new mechanism should be aware of package-specifc git tags (google-cloud-datastore:v1.2.0 vs. v1.2.0) and create a new version for the appropriate gem.

@blowmage To be clear, when a new version of an individual gem is released, a new version of the gcloud-common "bundled" gem will also be released, and new documentation published for both the individual and the bundled gems?
See previous discussion on gcloud-common:

when a subpackage gets a feature, our umbrella package gets a feature... which is a feature, so we should tag it as one.


Error executing Lua callback Cannot find color 'CurSearch'

Good day
I've recently installed ide.nvim and I'm getting some errors when running :IdeProjectCreate
I'm getting the following error:
Error executing Lua callback: ...pack/packer/start/ide.nvim/lua/ide/ui/dialogs/dialog.lua:211: Cannot find color 'CurSearch'
stack traceback:
        [C]: in function 'error'
        ...pack/packer/start/ide.nvim/lua/ide/ui/dialogs/dialog.lua:211: in function 'hl'
        ...pack/packer/start/ide.nvim/lua/ide/ui/dialogs/dialog.lua:248: in function 'cb'
        ...te/pack/packer/start/ide.nvim/lua/ide/ui/base/buffer.lua:140: in function 'commit'
        ...pack/packer/start/ide.nvim/lua/ide/ui/dialogs/dialog.lua:240: in function 'render'
        ...te/pack/packer/start/ide.nvim/lua/ide/ui/base/buffer.lua:44: in function 'refresh'
        ...te/pack/packer/start/ide.nvim/lua/ide/ui/base/window.lua:45: in function 'show'
        ...pack/packer/start/ide.nvim/lua/ide/ui/dialogs/dialog.lua:94: in function 'popup'
        ...re/nvim/site/pack/packer/start/ide.nvim/lua/ide/init.lua:130: in function 'project_create'
        ...re/nvim/site/pack/packer/start/ide.nvim/lua/ide/init.lua:191: in function <...re/nvim/site/pack/packer/start/ide.nvim/lua/ide/init.lua:190>

Details:

nvim --version:

NVIM v0.8.0-1210-gd367ed9b2
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by runner@fv-az505-656

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/share/nvim"

Run :checkhealth for more info

lsb_release -a

No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye

Terminal: gnome-terminal

Steps to reproduce:

Install using packer as directed on readme
Run :IdeProjectCreate

It seems that the color group CurSearch is not found, may I know which color scheme are you using?

I got this error message too with tokyonight.nvim

@LoneExile: I can reproduce the issue with tokyonight, thanks!

This commit https://github.com/Dax89/ide.nvim/commit/3aacb6d27943c03bea53c826ed32496f730a377c changes the UI's primary color from CurSearch to Cursor and it looks like it works with tokyo night too.

lol I get this for Cursor, which is definitely defined in my colorscheme.

The problem is that nvim_get_hl_by_name doesn't always return the real RGB representation of a specific color group, I have added a workaround if reverse flag is set (like dracula color scheme one for Cursor group) and I set the highlighting entirely.
Check if it works now!

That fixed it, thank you!


Zipper does´t recognize folders which starts with underscore like "_folder"

I Read Test.zip extract on /Test and create Result.zip
Zipper::make(storage_path('/app/tests/Test.zip'))->extractTo(storage_path('/app/tmp/Test/'));
Zipper::make(storage_path('/app/tests/Result.zip'))->add(storage_path('/app/tmp/Test/'));

Test.zip contains:
/_rels
/docProps
/xl
Content_Types.xml

Result.zip contains:
/docProps
/xl
Content_Types.xml

Extra: inside to docProps, there is another folder _rels, but in this case worked.

Having the same issue. Trying to find the source of the problem but no luck yet.


Library design and adoption

I created this library because I was sick of seeing the same piece/class copied over and over across different projects. This problem is why projects like Composer exist.
When having a brief conversion with Ondrej for the usage of this library, one point of concern is that the different tools may change a tiny bit the way the number of CPU cores are detected based on the system.
I think this library could afford to provide a bit more details on the source and/or allow to veto some sources.
Usages found:

[x] https://github.com/vimeo/psalm/pull/8833 Vimeo
[x] https://github.com/phpstan/phpstan-src/pull/2047 PHPStan
[ ] https://github.com/paratestphp/paratest/pull/703 Paratest
[x] https://github.com/infection/infection/pull/1767 Infection
[x] https://github.com/webmozarts/console-parallelization/pull/189 ConsoleParallelization
Phan
[x] https://github.com/symplify/symplify/pull/4495 Rector
Similar package: https://github.com/WyriHaximus/php-cpu-core-detector
[ ] https://github.com/phpstan/phpstan-src/pull/2049#issuecomment-1344659398

I think this task did its job. If more projects are interested in integrating this library there should be enough examples for it now.


[poco] build failure

Host Environment

OS: Ubuntu x64
Compiler: gcc 9.3, clang v10.0.0-4ubuntu1
install-arm64-android-dbg-out.log

To Reproduce
Steps to reproduce the behavior:
./vcpkg install poco:arm64-android
Failure logs
Computing installation plan...
The following packages will be built and installed:

pcre[core]:arm64-android -> 8.44#8
poco[core]:arm64-android -> 1.10.1#5
zlib[core]:arm64-android -> 1.2.11#10
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet arm64-android...
Could not locate cached archive: /home/xyz/.cache/vcpkg/archives/0f/0f0b2f4ca66459d394d84a5cdaa9296292554774.zip
Could not locate cached archive: /home/xyz/.cache/vcpkg/archives/db/dbc7a870bdf7e60268575609e72546b73018b093.zip
Could not locate cached archive: /home/xyz/.cache/vcpkg/archives/cf/cf1df4f53b879d2eff7fa7230e17e5f0d416cafd.zip
Starting package 1/3: pcre:arm64-android
Building package pcre[core]:arm64-android...
-- Using community triplet arm64-android. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: /home/xyz/vcpkg_arm/triplets/community/arm64-android.cmake
-- Using cached /home/xyz/vcpkg_arm/downloads/pcre-8.44.zip
-- Cleaning sources at /home/xyz/vcpkg_arm/buildtrees/pcre/src/pcre-8-5bdacbc1cb.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/xyz/vcpkg_arm/downloads/pcre-8.44.zip
-- Applying patch pcre-8.44_suppress_cmake_and_compiler_warnings-errors.patch
-- Applying patch export-cmake-targets.patch
-- Using source at /home/xyz/vcpkg_arm/buildtrees/pcre/src/pcre-8-5bdacbc1cb.clean
-- Configuring arm64-android-dbg
-- Configuring arm64-android-rel
-- Building arm64-android-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:146 (message):
Command failed: /home/xyz/vcpkg_arm/downloads/tools/cmake-3.20.1-linux/cmake-3.20.1-linux-x86_64/bin/cmake --build . --config Debug --target install -- -v -j2
Working Directory: /home/xyz/vcpkg_arm/buildtrees/pcre/arm64-android-dbg
See logs for more information:
/home/ngld-m-dev/xyz/buildtrees/pcre/install-arm64-android-dbg-out.log

Call Stack (most recent call first):
scripts/cmake/vcpkg_build_cmake.cmake:105 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_cmake.cmake:45 (vcpkg_build_cmake)
ports/pcre/portfile.cmake:55 (vcpkg_install_cmake)
scripts/ports.cmake:142 (include)
Error: Building package pcre:arm64-android failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with ./vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: pcre:arm64-android
Vcpkg version: 2021-01-13-unknownhash
Additional context
Additional packages have installed successfully.

Please provide failure log /home/ngld-m-dev/xyz/buildtrees/pcre/install-arm64-android-dbg-out.log.
Thanks.

@JackBoosY There is a link to the log file under the Host Environment section.  But it's attached here too.
Thanks.
install-arm64-android-dbg-out.log

[48/75] /home/xyz/Android/Sdk/ndk/21.3.6528147/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++ --target=aarch64-none-linux-android21 --gcc-toolchain=/home/xyz/Android/Sdk/ndk/21.3.6528147/toolchains/llvm/prebuilt/linux-x86_64 --sysroot=/home/xyz/Android/Sdk/ndk/21.3.6528147/toolchains/llvm/prebuilt/linux-x86_64/sysroot -DHAVE_CONFIG_H -Dpcrecpp_EXPORTS -I. -I/home/xyz/vcpkg_arm/buildtrees/pcre/src/pcre-8-5bdacbc1cb.clean -g -DANDROID -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -frtti -fexceptions  -fPIC   -O0 -fno-limit-debug-info    -fPIC -MD -MT CMakeFiles/pcrecpp.dir/pcrecpp.cc.o -MF CMakeFiles/pcrecpp.dir/pcrecpp.cc.o.d -o CMakeFiles/pcrecpp.dir/pcrecpp.cc.o -c /home/xyz/vcpkg_arm/buildtrees/pcre/src/pcre-8-5bdacbc1cb.clean/pcrecpp.cc
FAILED: CMakeFiles/pcrecpp.dir/pcrecpp.cc.o
/home/xyz/Android/Sdk/ndk/21.3.6528147/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++ --target=aarch64-none-linux-android21 --gcc-toolchain=/home/xyz/Android/Sdk/ndk/21.3.6528147/toolchains/llvm/prebuilt/linux-x86_64 --sysroot=/home/xyz/Android/Sdk/ndk/21.3.6528147/toolchains/llvm/prebuilt/linux-x86_64/sysroot -DHAVE_CONFIG_H -Dpcrecpp_EXPORTS -I. -I/home/xyz/vcpkg_arm/buildtrees/pcre/src/pcre-8-5bdacbc1cb.clean -g -DANDROID -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -frtti -fexceptions  -fPIC   -O0 -fno-limit-debug-info    -fPIC -MD -MT CMakeFiles/pcrecpp.dir/pcrecpp.cc.o -MF CMakeFiles/pcrecpp.dir/pcrecpp.cc.o.d -o CMakeFiles/pcrecpp.dir/pcrecpp.cc.o -c /home/xyz/vcpkg_arm/buildtrees/pcre/src/pcre-8-5bdacbc1cb.clean/pcrecpp.cc
/home/xyz/vcpkg_arm/buildtrees/pcre/src/pcre-8-5bdacbc1cb.clean/pcrecpp.cc:885:17: error: use of undeclared identifier 'strtoq'; did you mean 'strtol'?
  long long r = strtoq(str, &end, radix);
                ^~~~~~
                strtol
/home/xyz/Android/Sdk/ndk/21.3.6528147/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/stdlib.h:91:6: note: 'strtol' declared here
long strtol(const char* __s, char** __end_ptr, int __base);
     ^
/home/xyz/vcpkg_arm/buildtrees/pcre/src/pcre-8-5bdacbc1cb.clean/pcrecpp.cc:917:26: error: use of undeclared identifier 'strtouq'; did you mean 'strtoul'?
  unsigned long long r = strtouq(str, &end, radix);
                         ^~~~~~~
                         strtoul
/home/xyz/Android/Sdk/ndk/21.3.6528147/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/stdlib.h:93:15: note: 'strtoul' declared here
unsigned long strtoul(const char* __s, char** __end_ptr, int __base);
              ^
2 errors generated.

The upstream should suitable for android arch.

Thanks for posting this issue. This issue should be a upstream issue, upstream should suitable for android arch. And this issue hasn’t been updated more than 3 months, if it is still an issue, please reopen this issue.


ui-router support

Is there a reason you chose not to use the ui-router?

Firstly, i would say ui-router is a great component.
The thing is ui-router was involved at first while this idea of "create a generator" came into my mind. It was almost two years ago, and ui-router indeed have some issues that blocked my work. And at that time, i thought it is better to use simplest solution in a generator which can reduce the learning curve on both angularjs itself and generator-es6-angular.
So i add angular-route by default.
It's fine, you want to use ui-router as replacement of angular-route, following files should be modified for this purpose:
js/fw/config/RouterConfig.js
js/fw/ext/main.js
js/features/common/ui/RouteIndicator.js
And Routes.js in each feature folder


[Feature Request]: Close Toast on Click Anywhere on the Toast

Hello,
I am currently using your toast component and I appreciate its functionality. However, I've encountered a usability issue that could enhance the user experience significantly.
Issue: Currently, the toast can only be dismissed by clicking a close button, typically located in a corner. This requires precise mouse movement and interaction, which can be inconvenient for users.
Feature Request: I propose an enhancement where clicking anywhere on the toast itself would dismiss it. This would provide a more intuitive and faster way for users to close the toast, especially when they are in a hurry or not focused on precision.
This feature would align with common user expectations and improve the overall usability of the toast component.
Regards

@kronos1345 The toast can be currently dismissed by swiping down as well. If you want to close on click, you can add an onClick event to the toast and dimiss them programatically.

Don't you think this should be added to the toast as a configuration at least?
if you feel like it's not worth adding as a feature, would you mind mentioning how to dismiss the toast programmatically while being able to use the features such as toast types and rich colors and so on?

how do u add a onClick event to the toast? find no option to do this. Do we have to create a custom toast just to do this?


Hello,

I have added your pjax plugin from wordpress repository and it is working fine but I have found some issues, php/javascripts are not working from the other plugins and some plugins are also not working properly. I don't know how to fix this.
I want to add Pjax-api that you have added here and I want to add it to Wordpress. How to integrate it?
Thank you once again for making a great plugin. All the best.

Unfortunately I ended the support of that plugin.


test(oxc_transformer): define replaces nested incorrectly

See #7598

I am sorry, I just copy tests from the issue and did not notice there exists a pr related to tests, closed in favor of https://github.com/oxc-project/oxc/pull/7640/files,

No problem 👍


Panic in RawLeafBuilder::Append

Hey, just had redb panic while inserting into a Table<u128, &[u8]>.
This was on windows and the last process to access the database had crashed with the database open.
I can't repro anymore -- after restarting the same data should have been inserted in the same order, but I'm not 100% sure on that.
ecc6299db9ec823\redb-0.15.0\src\tree_store\btree_base.rs:780:9
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/2c8cc343237b8f7d5a3c3703e3a87f2eb2c54a74/library\std\src\panicking.rs:575
   1: core::panicking::panic_fmt
             at /rustc/2c8cc343237b8f7d5a3c3703e3a87f2eb2c54a74/library\core\src\panicking.rs:64
   2: core::slice::index::slice_end_index_len_fail_rt
             at /rustc/2c8cc343237b8f7d5a3c3703e3a87f2eb2c54a74/library\core\src\slice\index.rs:77
   3: core::slice::index::slice_end_index_len_fail
             at /rustc/2c8cc343237b8f7d5a3c3703e3a87f2eb2c54a74/library\core\src\slice\index.rs:69
   4: redb::tree_store::btree_base::RawLeafBuilder::append
   5: redb::tree_store::btree_base::LeafBuilder::build
   6: redb::tree_store::btree_mutator::MutateHelper<K,V>::insert_helper
   7: redb::tree_store::btree_mutator::MutateHelper<K,V>::insert_helper
   8: redb::tree_store::btree_mutator::MutateHelper<K,V>::insert_helper
   9: redb::tree_store::btree_mutator::MutateHelper<K,V>::insert_helper
  10: redb::tree_store::btree_mutator::MutateHelper<K,V>::insert
  11: redb::tree_store::btree::BtreeMut<K,V>::insert
  12: <redb::table::Table<u128,&[u8]> as beam::db::EntriesMut>::write_data```

Well that's not good. I'll look around a bit. I've been planning to refractor a bunch of that code. Let me know if you are able to reproduce it. It'll be hard to debug without a repro

Do you use any Durability::None transactions? I found a data corruption issue that could occur, if a crash occurred when using that.

Ah, actually no, I'm pretty sure this was caused by the cache poisoning issue that I fixed in b4fed9a12d29495973b0381f7233b0de4033c3bb


fix missing profile photo and access token for foreign scopes at Microsoft auth provider

Hey, I just made a Pull Request!

This change re-adds the loading of the logged-in user's profile picture
as well as the "skip profile" logic for foreign scopes
which got lost while migrating the Microsoft auth provider to the new module.
Additionally, it uses the 96x96 size instead of 48x48.
The image is used on the profile card on the settings page (/settings)
rendered as 96x96 and was blurry due to the upscaling.
Replaces the types.d.ts file with type declarations with the use of
@types/passport-microsoft.
Closes: #20677
Closes: #20699
Signed-off-by: Patrick Jungermann<EMAIL_ADDRESS>:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks for the pointer. I was already looking into how to adapt some of the few authenticator.test.ts. We may have lost a few more things during the migration. I will look into porting at least the related test cases over to the new setup.

@Rugvip @jamieklassen
It took me some time, however, I was able to port and adjust all tests.
I made the photo loading more stable as well compared to the previous version here.
Also, as it was a simple change, I've added the fix for the other issues to this PR, too. The PR description was adjusted accordingly.
Please let me know if you see room for improvement.

oh dang, seems to have conflicts now

@freben I took care of the conflicts.

@Rugvip @freben
since the fixes got merged, should we revert the revert of v1.19.3 and use again @backstage/plugin-auth-backend-module-microsoft-provider?

@pjungermann Is it really a straight revert? Feel free to make a PR that untangles things again if you have the opportunity!