Deprecated method call on Waterfall

Server Environment

OS [Linux, MacOS, Windows] version: CentOS (Linux) 7.9.2009
Java version [java -version]: 20.0.1
Server version [/version]: git:Waterfall-Bootstrap:1.20-R0.1-SNAPSHOT:ec41547:536
NetworkInterceptor version [/version NetworkInterceptor]: 3.4.0

Configuration
methods:
  - security-manager
  - proxy-selector
check-for-updates: true
update-source: Hangar
enable-metrics: true
mode: allow
logging:
  enabled: true
  include-traces: false
  mode: file
  truncate-file-on-start: true
blocking:
  enabled: true
mapping:
  enabled: true
  timer: 1000
trusted-plugins:
  - ChessCraft
  - LuckPerms
  - Plan
  - SystemProperties
blocked-plugins: []
targets:
  - 'api.mojang.com'
  - 'sessionserver.mojang.com'
  - 'launcher.mojang.com'
  - 'launchermeta.mojang.com'
  - 'api.papermc.io'
...

Error from waterfall log
[17:02:46 INFO] [NetworkInterceptor]: Interceptors: [security-manager, proxy-selector]
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by me.lucko.networkinterceptor.interceptors.SecurityManagerInterceptor (file:/home/ram/BungeeCord/plugins/NetworkInterceptor-3.4.0.jar)
WARNING: Please consider reporting this to the maintainers of me.lucko.networkinterceptor.interceptors.SecurityManagerInterceptor
WARNING: System::setSecurityManager will be removed in a future release

I'm fairly certain this has to do with Java deprecating the use of SecurityManager.
As far as I know, there's nothing I can do about it. There doesn't seem to be an alternative in the works, either:
https://openjdk.org/jeps/411


Update Trainer.push_to_hub to use **kwargs

Resolves #290
Hello!
Pull Request overview

Update Trainer.push_to_hub to use **kwargs, with the goal to allow it to work regardless of the underlying huggingface_hub version.

Details
huggingface_hub has made a lot of changes to the interface for push_to_hub, causing #290. I was left with a choice: implement according to the new version, or the old version. In the end, I opted for "both" via **kwargs and a docstring that matches a newish version, alongside a link to https://huggingface.co/docs/huggingface_hub/package_reference/mixins#huggingface_hub.ModelHubMixin.push_to_hub.
This should allow it to work for more versions of huggingface_hub.
Additionally...
I updated create_model_card to not put temporary paths in the README. This happened whenever you did Trainer.push_to_hub, as that creates a temporary folder, calls save_pretrained with that folder, which then calls create_model_card with the full path as the "model name".
This simple band-aid fix checks whether the model_name is a temporary folder. If so, it only keeps the last two sections of the folder, e.g. tomaarsen/setfit_test. This should be relatively robust, and otherwise users are always free to update their SetFit README's.
I'd like to merge this and then push for 0.7.0 @lewtun We can't turn this into 0.6.1 as it's technically a breaking change (e.g. Trainer.push_to_hub(repo_path_or_name="blabla") will break)

Tom Aarsen

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_6c3czend9t/clone/recipe/meta.yaml:14: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_6c3czend9t/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
WARNING: /tmp/abs_6c3czend9t/clone/recipe/meta.yaml:41: missing_description: The recipe is missing a description
ERROR: /tmp/abs_6c3czend9t/clone/recipe/meta.yaml:41: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: /tmp/abs_6c3czend9t/clone/recipe/meta.yaml:41: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_6c3czend9t/clone/recipe/meta.yaml:41: missing_license_family: The recipe is missing the about/license_family key.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_88isr1vwoi/clone/recipe/meta.yaml:14: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_88isr1vwoi/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_88isr1vwoi/clone/recipe/meta.yaml:41: missing_dev_url: The recipe is missing a dev_url
WARNING: /tmp/abs_88isr1vwoi/clone/recipe/meta.yaml:41: missing_description: The recipe is missing a description
ERROR: /tmp/abs_88isr1vwoi/clone/recipe/meta.yaml:41: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: /tmp/abs_88isr1vwoi/clone/recipe/meta.yaml:41: missing_license_family: The recipe is missing the about/license_family key.
Errors were found


blackCauldron7/surround.nvim is not available

Repo https://github.com/blackCauldron7/surround.nvim is no longer available. Maybe the user has been deleted?

Does anyone have a full history fork? I have only a shallow clone via packer.

My local part starts from
commit 59a0ef7d7f8da05f9e03075186b6de754e85c42c
Author:     blackCauldron7<EMAIL_ADDRESS>AuthorDate: Thu Dec 16 11:38:03 2021 +0530
Commit:     blackCauldron7<EMAIL_ADDRESS>CommitDate: Thu Dec 16 11:40:30 2021 +0530

    add new option space_on_closing_char
---
 .gitignore              |   2 +
 README.md               | 113 ++++++++
 lua/surround/init.lua   | 769 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 lua/surround/parser.lua | 379 +++++++++++++++++++++++++++
 lua/surround/utils.lua  | 220 ++++++++++++++++
 plugin/surround.vim     |   3 +
 6 files changed, 1486 insertions(+)

It turns out a gap in the history of about 2 months.
how to export history from here: https://sourcegraph.com/github.com/blackCauldron7/surround.nvim

Note there was no license associated with this code so generally would full copyright of blackCauldron7. Copying and reproducing may be a legally bad idea. I do not feel personally this was intentional though but be aware.

Then it makes sense to remove this repository from the list?
full repo: https://github.com/Mephistophiles/surround.nvim

I sincerely hope the original author is ok.

Is there a canonical fork yet, or is it still to be decided?


add changelog for v2.0.0-rc.2 release

Summary

add changelog for v2.0.0-rc.2 release

Can I sneak in https://github.com/sigstore/cosign/pull/2708 too?

Codecov Report

Merging #2707 (39266b4) into main (01bd21d) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main    #2707   +/-   ##
=======================================
  Coverage   30.15%   30.15%
=======================================
  Files         146      146
  Lines        9363     9363
=======================================
  Hits         2823     2823
  Misses       6103     6103
  Partials      437      437

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@haydentherapper It is a draft PR, we want to cut a rc.2 in few hours.

Are we planning to cut cosign 2.0 from this RC? If so, I would like to get the change in since it changes the expectation for what a user should pass in for timestamp requests. If we are going to have another RC or you’ll cut 2.0 from HEAD, that’d be fine.
It’s very late here so I won’t be able to test til morning, and I’m pretty sure there’s a bug.

@haydentherapper We also want that change in for cosign 2.0, but it doesn't have tests against non-sigstore TSAs and as you mention it may contain a bug. I'd vote for cutting this RC with what we got and cut a new RC with your changes or any others next week. Unless I am missing a different timeline for the next week.

SG!

@haydentherapper, we can cut an RC.3 later


Input.Date Adaptive card Bug - Choosing year from calendar.

Copied bug from: https://github.com/microsoft/AdaptiveCards/issues/6719
Details from original post:
Problem Statement
In Input.Date Adaptive card, How to change the year easily?? Should I need to choose different year date by click back button?

Previously, the Input.Date adpative card used to look like the following:

Is this feature deprecated by https://adaptivecards.io/explorer ??
If so, why they make it complex to choose a date??
Awaiting your reply,
Regards.
Proposed solution
I am not able to choose the year that is very earlier.
There is no drop down enabled to choose year.

Awaiting your reply,
Regards.
Alternatives or Workarounds
No response---
Document Details
⚠ Do not edit this section.It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3fb4394d-25b1-8752-3996-fe3a2934732d
Version Independent ID: 6d391381-89d0-117c-27cc-00043bd26a36
Content: Cards reference - Teams
Content Source: msteams-platform/task-modules-and-cards/cards/cards-reference.md
Product: msteams
GitHub Login: @surbhigupta12
Microsoft Alias: surbhigupta12

Thanks for informing about this, I will confirm with internal team and get back to you.

I tried few scenario and was not able to change UI look and feel. I will get back to you with update as soon as I hear from the internal team.
Thanks

We have confirmed internally and this is an known issue and team is working on it. It would get fix in upcoming quarter.
Thanks


Unable to type in Chinese in integrated terminal

Issue Type: Bug
打开内置终端 无法输入中文，
VS Code version: Code 1.53.0 (8490d3dde47c57ba65ec40dd192d014fd2113496, 2021-02-03T20:36:38.611Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 x 3192)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: enabledrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.86GB (11.40GB free)

Process Argv
--crash-reporter-id f85a41a1-239d-4bd7-a4a1-dc3c12e2b6be

Screen Reader
no

VM
0%

Extensions (6)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.1.14

vsc-material-theme
Equ
33.1.2

vsc-material-theme-icons
equ
1.2.2

git-graph
mhu
1.28.0

vscode-language-pack-zh-hans
MS-
1.53.2

vetur
oct
0.32.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30211402
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt600cf:30251589

I can reproduce:

It's not new, I can reproduce this on both 1.52 and 1.51 (didn't try to find a working one). xterm.js in browser works fine.

me too

me too

The terminal can't input Chinese characters, but the CMD in Windows system can input Chinese normally. The installed version is 1.53. How can I input Chinese

+1

+1

+1

+1

+10086

+100000086

I met same bug, I found that Windows builtin input method can use normally, some other input methods cannot input Chinese. When I met this bug, I thought that it's because of the input method I am using. BTW, VS Code in GNU/Linux works normally too.

It's not only Chinese but also Japanese, Thai, Kazakh, Russian. Even emoji.
I guess this may caused by unicode.

We can review they commits on version 1.52 -> 1.53?

According to https://github.com/rime/weasel/issues/605#issuecomment-774664102, There are to many commits after 1.51. We may not able to review them.

I met same bug, I found that Windows builtin input method can use normally, some other input methods cannot input Chinese. When I met this bug, I thought that it's because of the input method I am using. BTW, VS Code in GNU/Linux works normally too.

Thanks your reply, I try windows native input methods, it works!

I have this problem too. My version is 1.53.But what I have found so far is that the QQ input method and the Microsoft input method can input Chinese, while the sogou input method cannot input Chinese.

After some shallow track.

Seems caused by xterm.paste

Gathered some old comments from not-related issues here:

I'm experiencing the same problem on terminal, when inputing with CJK IME, the selected word will not be filled, or it will ignore some characters. I also tried the latest inside build but can still get this problem.

This bug happens at around 1.52.0 (maybe, I don't update VSCode in time), and it occurs when you're inputing CJK letters with some CJK IME (for my example, this bug happens with QQ Pinyin, but with Microsoft Pinyin it works fine).

This comment was posted at https://github.com/microsoft/vscode/issues/112621#issuecomment-767302336 , but it may not related to the original topic (happens on Source Control panel) and I didn't notice this issue at that time.

Originally posted by @ccloli in https://github.com/microsoft/vscode/issues/112978#issuecomment-767324290

I'm using vscode from VSCode-win32-x64-1.52.1.zip on windows 10. Inputing chinese is ok when editing documents with any chinese IME. When inputing in the terminal, it is not ok with sogou IME and ok with Microsoft PinYin IME.
Inputing chinese is ok for vscode-1.45.1
Originally posted by @ysiw in https://github.com/microsoft/vscode/issues/112856#issuecomment-755145706

@Kingwl I see some repros show ???, but some others simply do nothing.
For everyone have this issue, can you please confirm which behavior you are experiencing?

Gathered some old comments from not-related issues here:

Well, I think #112978 is the same problem describe here.
In detail, when you input x letters in terminal, they are not showing in terminal, then if you input y letters, then y - x of last letters will be shown in terminal.
Also this is not limited to CJK letters, when you input English letter with these CJK IME (you can press Enter to send your input Elnglish letters), they will be gone, too.
For example, if you input abc def ghi jklmn opqrst uv wxyz in sequence, the input letters will like abcmntyz

@yume-chan Seems It's will write ? if you are paste or using Microsoft Pinyin. Otherwise It will be ignored.

Please support Sogou Pinyin input method, which is our common input method tool

I have this problem too. My version is 1.53.But what I have found so far is that the QQ input method and the Microsoft input method can input Chinese, while the sogou input method cannot input Chinese.

really? I tried the Microsoft Chinese input Method, whatever i input will be doubled, like: 112233啊啊

Gathered some old comments from not-related issues here:

~Well, I think #112978 is the same problem describe here.~ Okay, looks like it's not a same issue, I got nothing instead of ???, but I'm in 1.52.1 instead of 1.53.0. I also tried the latest insider build (1.54.0-insider, afd102c), the behavior is the same as previous version and doesn't get ???.
In detail, when you input x letters in terminal, they are not showing in terminal, then if you input y letters, then y - x of last letters will be shown.
Also this is not limited to CJK letters, when you input English letter with these CJK IME (you can press Enter to send your input Elnglish letters), they will be gone, too.
For example, if you input abc def ghi jklmn opqrst uv wxyz in sequence, the input letters will be like abcmntyz (sometimes I got abcmnopqrstyz which is a bit weird, it seems that before inputing opqrst, x is reset to 0).

BTW, pasting text with Chinese letters into terminal works fine, it only happens when inputing with some CJK IME (some IME like Microsoft Pinyin works fine here).

EXACTELY THE SAME!!!

I tested this and found the following:

The ? issue seems specific to powershell 5, upgrading to pwsh 7 fixes the issue (plus it's way better, you should do this if you use powershell)
The non input problem we believe is a third party IME that has some problems.

Not one, but multiple third-party IMEs. They all worked fine before 1.52 and still work fine in all other programs and even in code editors after 1.52.
So definitely something has been changed in either Electron, Code or Xterm.js that affected these IMEs.
If you believe it's those IMES' fault, at least we need some directions to how we can "fix" them to conform the way you require.

Tested with a fresh new Windows VM, seems that the first version which has the bug is 1.52.0. Since I don't find a way to get the subversion of Insider build, so I can't tell which day of release introduces the bug.
What's interesting is that, when you install QQ Pinyin for the first time, it asks you to choose an input mode. The first mode is "Game Compatible Mode", and it's designed to use with game or have compatible problem with some program, with this mode you'll get a more stable input experience. The second mode is "Single-line Input Mode", and it's more likely to the modern Microsoft Pinyin, which put input letters into the program UI, and as it describes it may have compatible problem.

So if I switch to the modern single-line mode, the problem is gone:

But if I disable it (use the old compatible mode, which keeps the input letters in the IME UI), the problem is shown:

Tested with a fresh new Windows VM, seems that the first version which has the bug is 1.52.0. Since I don't find a way to get the subversion of Insider build, so I can't tell which day of release introduces the bug.
What's interesting is that, when you install QQ Pinyin for the first time, it asks you to choose an input mode. The first mode is "Game Compatible Mode", and it's designed to use with game or have compatible problem with some program, with this mode you'll get a more stable input experience. The second mode is "Single-line Input Mode", and it's more likely to the modern Microsoft Pinyin, which put input letters into the program UI, and as it describes it may have compatible problem.

So if I switch to the modern single-line mode, the problem is gone:

But if I disable it (use the old compatible mode, which keeps the input letters in the IME UI), the problem is shown:

Thxxx! QQ pinyin Works well !

QQ pinyin Works!

Tested with some other IMEs, like a very old version of QQ Pinyin (before it merges to Sogou Pinyin), the latest Sogou Pinyin, Microsoft Bing IME, and some integrated IME in Windows 7, ALL of them can input correctly, but most of them are having a UI bug, which both shows the input letters in the IME UI and VSCode UI, but other programs like explorer.exe, it only shows the input letters in the IME UI.

事实上 vscode 将这个bug标记为：Backlog， 并没有在recovery 2 plan中。是不打算修复吗？还是？@vscode

I guess the "game compatible mode" uses Input Method Manager (IMM) API while "single line mode" uses Text Services Framework (TSF) API. IMM has been deprecated and TSF is the replacement.
I remember while developing the Chromium-based Microsoft Edge, Microsoft developers actually had some pr's for Chromium around TSF support, and those pr's did cause some issue with Microsoft Edge canary and Chromium (I encountered one that is when deleting, characters got repeated)
I can't remember the exact version numbers that had these issues, but maybe Electron is currently using one of those bad ones. So hopefully these issues will go away when Electron upgrade to a newer version of Chromium.

Any progress?

is there any progress? I have the same problem

@heartacker xterm.js 的作者 @Tyriar 认为这是第三方输入法自己的问题，所以把这个 issue 移出了恢复迭代

@heartacker xterm.js 的作者 @Tyriar 认为这是第三方输入法自己的问题，所以把这个 issue 移出了恢复迭代

我最初也以为是输入法问题，因为我使用 Rime 输入法出现了这个问题，但是用系统内建输入法之后就正常了，于是提了这个issue
https://github.com/rime/weasel/issues/605
但是上面有其他用户提到了其他的输入法也出现了同样的问题，而且我自己使用 Rime 输入法在之前版本的VSCode中运作正常，所以原因应该不在输入法上。

is there any progress? I have the same problem
我暂时用了微软拼音输入法，没问题
搜狗输入法不能输入中文

@heartacker xterm.js 的作者 @Tyriar 认为这是第三方输入法自己的问题，所以把这个 issue 移出了恢复迭代

Is it possible to make it compatible with these IMEs? As based on latest comments, it still happens on Sogou Pinyin (thought I didn't reproduce it), and I guess Sogou Pinyin, QQ Pinyin and Rime are the top 3 using 3rd-party IMEs in China (at least Sogou Pinyin is definitely the most one), and all of them are well in previous version (1.51-).

I guess the "game compatible mode" uses Input Method Manager (IMM) API while "single line mode" uses Text Services Framework (TSF) API. IMM has been deprecated and TSF is the replacement.

Is this also apply to Linux distributions? Since the original issue I commented is on Arch Linux.
@Reilkay What's your IME using on Arch Linux? And are you still experiencing the same problem in latest VSCode?
@Reilkay 你在 Arch Linux 上使用的输入法是什么？在最新的 VSCode 下是否仍存在无法在终端输入中文的问题？

Is this also apply to Linux distributions? Since the original issue I commented is on Arch Linux.

@ccloli No, clearly #112978's behavior is different from this one.

搜狗输入法就没法输入中文，自带输入法就可以。。。难受

after 1.52 version, vscode behaves like this, maybe we should find out changes which cause this problem. Some input methods call special system APIs or output text to UI in a different way. but i think vscode should support them if possible.

I have this problem too. My version is 1.53.2.

This issue deserves attention because it has hit a large number of Chinese developers.
I thought I have to consider downgrading the version of VSCode until this problem has been fixed.

This issue deserves attention because it has hit a large number of Chinese developers.
I thought I have to consider downgrading the version of VSCode until this problem has been fixed.

How to downgrading?
I not found old version in the VSCode home page.

This issue deserves attention because it has hit a large number of Chinese developers.
I thought I have to consider downgrading the version of VSCode until this problem has been fixed.

How to downgrading?
I not found old version in the VSCode home page.

You can find previous version here.
https://code.visualstudio.com/updates/v1_50

This issue deserves attention because it has hit a large number of Chinese developers.
I thought I have to consider downgrading the version of VSCode until this problem has been fixed.

How to downgrading?
I not found old version in the VSCode home page.

You can find previous version here.
https://code.visualstudio.com/updates/v1_50

Thanks!

Is there any progress ?
I'm sure it's an urgent issue.

Version 1.54.1 is released, but this bug is stiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiill able to reproduced.👿

I also encounter this problem. Any progress?
Sogou Pinyin input method
版本: 1.54.1 (system setup)
提交: f30a9b73e8ffc278e71575118b6bf568f04587c8
日期: 2021-03-04T22:38:31.419Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

1.52 can work normally.

I think this issue occurred in ^1.52.0, versions before that work as expected, as a workaround, we could use commands like git commit instead of git commit -m.

So for now, the following IMEs on Windows are having the same problem with integrated terminal:

Sogou Pinyin
QQ Pinyin (with default game compatible mode)
Baidu Pinyin
Rime (Weasel)
And an IME on Arch Linux (#112978, well yume-chan said it's not the same problem, but another contributer has marked it as duplicated with this one)? I've tried running an Arch Linux with lxde in a VM, but all fcitx IMEs are working fine, maybe it occurs on IBus?

To VSCode developers or contributers, the issue has been existed for about 3 months since 1.52.0 released, and from my side I don't see any progress on it, feeling a bit upset.
If you're not familiar with these IMEs, at least you can try Rime, it's an opensource IME, maybe it can helps you to find the problem.
BTW, for the working IMEs, probably they're also having another issue that both showing input letters on VSCode UI and IME UI.

To VSCode end-user, if you're still having this problem, maybe you can try the following options:

If you're using QQ Pinyin, switch to Single-line mode (单行模式), this should work fine.
Try Microsoft Pinyin, it's finally usable in Windows 10, without input lag on Windows 8.
Rollback to any version before v1.52.0, you can download any version you like before Nov 2020.
Input your text on another window, and copy & paste them into VSCode terminal (well I've been used like this for months)
Start a terminal window directly, or try Windows Terminal, this may also speed up the command with lots of outputs, since the VSCode terminal's stdio performance is a bit "oof".

And an IME on Arch Linux (#112978, well yume-chan said it's not the same problem, but another contributer has marked it as duplicated with this one)? I've tried running an Arch Linux with lxde in a VM, but all fcitx IMEs are working fine, maybe it occurs on IBus?

fcitx-rime can work fine on openSUSE, but I didn't try iBus rime.

By using git bisect and verify commits between v1.51.1 and v1.52.0, seems that 4b49bae9037bedcee2038905d3b4f65cbc42668b introduces the issue, anyone can review and verify it?

@ccloli wow,that's a huge progress. i am also deploying developing environment to verify the commit

the changes in this commit, is about css stylesheet of xterm.js, just 4 lines changes cause this problem. let's try to find out why

Aye, after I do these changes, VS Code works fine.

By using git bisect and verify commits between v1.51.1 and v1.52.0, seems that 4b49bae introduces the issue, ~anyone can review and verify it?~

Aye, after I do these changes, VS Code works fine.

By using git bisect and verify commits between v1.51.1 and v1.52.0, seems that 4b49bae introduces the issue, ~anyone can review and verify it?~

Not really, Chinese symbols will be repeated twice.

it doesn't work for me to disable the three properties.

Not really, Chinese symbols will be repeated twice.

@Python-37 Well, by removing padding it works fine again, and don't see the input letters are repeated.

I guess maybe it's because when padding is 0, some functions may not working properly.
I tested it with checking padding: 0 or not, and it's fun that, when inputing without IME, onInput event is not trigger until you press space (so maybe xterm handles input function by onKeyDown?). However, when using these IMEs, with default padding (behavior before v1.52.0), your input letters are keep in the textarea until you press Enter; with zero padding (current behavior), your old input will override your last input. Maybe xterm detects IME input with textarea value length?

At least I think revert that commit should fix the issue, but I cannot verify it directly, since node-gyp throws errors when I checkout to newer version.

i think in my environment , the problem may be different.
the solutions doesn't help.
i made textarea show up by change z-index in css.
i found that things are weird, you can totally see the chinese characters are typed in the textarea,
but they can't be rendered into display area.

i think in my environment , the problem may be different.
the solutions don't help.
i made textarea to the top level by changing z-index and opacity in css.
i found that things are weird, you can clearly see the chinese characters are typed in the textarea,
but they can't be rendered into display area.

by the way, Microsoft PinYin works very well.

i found that Microsoft PinYin always works well . Even i type in chinese characters using Sogou IME before.
i guess that's because vscode connect to System Input API directly instead of getting words from textarea.

@ZhyMC Well, I built it just now, can you help me to verify if it works for you?
https://1drv.ms/u/s!As4fpXfOPou9ghCE3bCZXVu8u1gk?e=SeLPHO
https://pan.baidu.com/s/1RrvKGtkKYWMMgVpSjy6mIQ us4x

@ccloli cool,  i am downloading.

bad news, doesn't work even that's a fixed prebuilt.

That's a sad story, I only tested it with QQ Pinyin. 😢
For me it breaks on v1.52.0, but some comments said they worked fine in v1.52.0, and having issue in latter version, maybe there are some other commits are related to this issue.
If you're willing to try which commits occurs the issue, you can clone the repo and follow wiki to setup develop enviornment, then use git bisect (Chinese translation) to mark good commits and bad commits, until you find the first occured commit.

@ccloli Before your tip, i don't even know that git has git bisect command. That's quite a good way to find what causes the problem, i will try to fix it in my environment.

I setup a fresh new Windows 10 VM (20H2, Enterprise, x64, with VirtualBox) and grab some versions of VSCode and IMEs. By testing these various versions of VSCode and IMEs, seems that there are at least 2 reasons that blocks terminal input.

VSCode Version
Sogou Pinyin
Baidu Pinyin
Microsoft Pinyin
Rime (Weasel)
QQ Pinyin

1.51.1
✔
✔
✔
✔
✔

1.52.0
✔
✔
✔
✖
✖

1.52.1
✔
✔
✔
✖
✖

1.53.0
✖
✖
✔
✖
✖

1.54.1
✖
✖
✔
✖
✖

1.55.0-fixed
✖
✖
✔
✔
✔

So if you're trying to find the broken commit for Sogou Pinyin, you can try git bisect bad 1.53.0 and git bisect good 1.52.1.

Detailed screen recording videos
https://user-images.githubusercontent.com/8115912/110276716-b9cc3f00-800e-11eb-99d0-1adcc0d0b2f9.mp4
https://user-images.githubusercontent.com/8115912/110276709-b20c9a80-800e-11eb-85f1-3e214d47c83e.mp4
https://user-images.githubusercontent.com/8115912/110276713-b5078b00-800e-11eb-87a9-53796e6ef6c7.mp4
https://user-images.githubusercontent.com/8115912/110276715-b8027b80-800e-11eb-9e2d-1cb61f6d1a3a.mp4

I setup a fresh new Windows 10 VM (20H2, Enterprise, x64, with VirtualBox) and grab some versions of VSCode and IMEs. By  testing these various versions of VSCode and IMEs, seems that there are at least 2 reasons that blocks terminal input.
Nice work, so there is somewhere changed we still didn't find between 1.52.1 and 1.53.0 caused sogou pinyin and baidu pinyin IME cannot work functionally.🤨

@Python-37 the sheet shows that there are not only one reason causes the problem.

hey guys , i have made progress using git bisect

somebody can verify this.
if it is verified, maybe the issue comes from the upstream : Electron.

i verified it again!
By using git reset --hard 94142bd and git reset --hard HEAD~ to compare the commit 94142bd7e0dbc073fe6abf130d7b7066a7beb1d6 and its last commit.
As this commit bump Electron to a new version, so i must re-compile it by run yarn.
so i can't show a git, but that's real.
Bumping the dependency : Electron to a new version causes the problem,
To solve this, i think we should create a new issue on https://github.com/electron/electron and refer it to this issue, since it is a problem comes from upstream.

what's more , the last commit of this bad commit is 962bedc4f47b26e4a6ddc917ee2a4d9445531fb9, this shows VSCODE update itself to 1.53.0, which can explain why after 1.53.0, something is going wrong.

the bad commit is: 94142bd
Bumping the dependency : Electron to a new version causes the problem,

@ZhyMC If that's true, at least for Sogou Pinyin, it would be what's @yume-chan said:

^ So definitely something has been changed in either Electron, Code or Xterm.js that affected these IMEs.
^ I can't remember the exact version numbers that had these issues, but maybe Electron is currently using one of those bad ones. So hopefully these issues will go away when Electron upgrades to a newer version of Chromium.

Though it's still weird that only integrated terminal is affected, the other modules of VSCode is fine. And it seems that it cannot be fixed by a simple downgrade, since 1.53.0 updates Electron from 9.x to 11.x, which crosses 2 major version. So hopefully it would be fixed by newer Electron, or xterm does some compatibility works.
BTW, looks like Electron upgrade only affects to Sogou Pinyin (as previous comment, QQ Pinyin and Rime are because of some css layout issue, and revert them can still works on latest build with newer Electron).

You are right, that's weird why only integrated terminal is affected after upgrading electron to 11.x.
Is there some ways to separate integrated terminal out and try to debug?

oh, that's interesting, i create a new project under<EMAIL_ADDRESS>and install a xterm.js@latest as a dependency.

index.html
<!doctype html>
  <html>
    <head>
      <link rel="stylesheet" href="../node_modules/xterm/css/xterm.css" />
      <script src="../node_modules/xterm/lib/xterm.js"></script>
    </head>
    <body>
      <div id="terminal"></div>
      <script>
        var term = new Terminal();
        term.open(document.getElementById('terminal'));
        term.write('Hello from \x1B[1;3;31mxterm.js\x1B[0m \r\n$ ')
        term.onData(e => {
      switch (e) {
        case '\r': // Enter
        case '\u0003': // Ctrl+C
          term.write('\r\n$ ');
          break;
        case '\u007F': // Backspace (DEL)
          // Do not delete the prompt
          if (term._core.buffer.x > 2) {
            term.write('\b \b');
          }
          break;
        default: // Print all other characters for demo
          term.write(e);
      }
    });
      </script>
    </body>
  </html>

hey guys, i think i found the reason.
in /src/browser/input/CompositionHelper.ts of xtermjs/xterm.js
we can find the code snippet:
if (ev.keyCode === 229) {
    // If the "composition character" is used but gets to this point it means a non-composition
    // character (eg. numbers and punctuation) was pressed when the IME was active.
    this._handleAnyTextareaChanges();
    return false;
}

i set up a keydown listener by using DevTools, and print the ev.keyCode when i am typing in words.
By seaching in google, i found that 229 is a special keyCode event fired with that when you typing Chinese or characters of some other languages.

so the issue is caused by electron 11.x the event with that keyCode 229 would never fired when typing Chinese.

And that explains the comment above:

i made textarea to the top level by changing z-index and opacity in css.
i found that things are weird, you can clearly see the chinese characters are typed in the textarea,
but they can't be rendered into display area.

maybe xterm.js can provide a alternative solution instead of using the event.

@ccloli can you test these input methods :'Sogou Pinyin | Baidu Pinyin | Microsoft Pinyin | Rime (Weasel) | QQ Pinyin'  . Will they fire the event ? i have no conditions to perform that test

so the issue is caused by electron 11.x the event with that keyCode 229 would never fired when typing Chinese for some IME like Sogou IME and Baidu IME.

Well, not exactly. In fact, when you set a listener to keydown event, you'll find on Electron 9 it'll fire the event when you complete the inputs, while on newer Electron like 12, keydown event is never fired.
https://user-images.githubusercontent.com/8115912/110315282-ffefc580-8043-11eb-9816-98c79fa4147a.mp4
https://user-images.githubusercontent.com/8115912/110315303-041be300-8044-11eb-82a6-1d9c1de96d9a.mp4
So there are 3 behaviors:

Microsoft Pinyin will fire keyup, keydown, input event when you input, and the input value is what you input right now
Rime and QQ Pinyin will fire keyup and keydown event when you input, but input value is your previous input; it won't fire input event until you complete it, and at this time the input value is the final input
Sogou Pinyin and Baidu Pinyin will only fire keyup event when you input, and input value is your previous input; it won't fire input and keydown event until you complete it, and at this time the input value is the final input; and in newer Electron 12, keydown event is never fired.

@ccloli So, there is always one event of 'keydown','keyup','input' at least will be fired when inputing ? maybe that's the solution for xterm.

If the browser runtime doesn't pass any events to xterm after user completed the input, xterm has not chances to fix the problem.

@ZhyMC  Yep, so we've already dig in deep enough, there are at least two major issue needs to be resolved:

A css style issue of Xterm that makes input textarea with 0 width, makes QQ Pinyin and Rime not working anymore. This may can be fixed by a simple revert.
A runtime environment issue of Electron that doesn't dispatch keydown event when using Sogou Pinyin, so that Xterm cannot measure IME has completed the inputs.

Until you're willing to dive into how Xterm or Electron works, maybe we should let VSCode's contributors to complete the rest job, I guess.

Well, i have done a little more work to investigate.
In MDN Web Docs:
docs/Web/API/Element/compositionstart_event

The compositionstart event is fired when a text composition system such as an input method editor starts a new composition session.
For example, this event could be fired after a user starts entering a Chinese character using a Pinyin IME.

And xterm depends on this web event totally to compose console string by ComposeHelper.
But , you see, Sogou Pinyin wouldn't fire the compositionstart when input starting.
In Chrome (not chromium or Electron), browser work very well on firing this event with Sogou Pinyin.
What's more important, i think that xterm will break its design if a hacking codes inserted into its source.
So, maybe it's necessary to ask the developers or maintainers to focus on the problem,
A web stardard like compositionstart , browsers should follow what it specifies.
or maybe IMEs using not good API, can't make electron ( or chromium) the fire the event,
but in old versions of electron, they can handle Sogou IME well.

or maybe IMEs using not good API, can't make electron ( or chromium) the fire the event,

Yep, when I was testing keyboard event, it's clear that compare to QQ Pinyin and Rime, Sogou Pinyin is a bit ugly, since I think firing keydown event when typing is more reasonable.
Though QQ Pinyin and Rime doesn't change value in time, as they're keeping input text in themselves (so there is no input event), at least the other events (keydown, keypress, keyup) are dispatched correctly.
But Sogou Pinyin only fires keyup event, think about that, you can release a key press without pressing it, that's confused in logical.
Still can't believe that even though QQ Pinyin has merged to Sogou, Inc., they're using different implementations on engine. lol

BTW, QQ Pinyin's single-line mode is more likely to Microsoft Pinyin, so it works well in latest VSCode.

Anyway, I tested Electron 9 and 12, except Sogou Pinyin and Baidu IME, all the others can dispatch CompositionEvent correctly on both versions.

The non input problem we believe is a third party IME that has some problems.

So at this time, I'm totally agreed with Xterm author's opinion. 🤣

@ccloli
Hahaha, at this time, i think the best solution is uninstalling the Sogou IME and try something else. And revert the commit which causes the css style problem.

So, the final solution is switch to QQ pinyin or Rime, and do these changes? https://github.com/microsoft/vscode/issues/115814#issuecomment-792254020
Maybe we should new a pull request.@ccloli  @ZhyMC

最好的办法还是切换输入法，插件会自动升级，旧版本的VSCode上插件会出现不可用的情况，例如Vetur

搜狗输入法可以输入了。搜狗热更新了，搜狗接锅。

屁咧~哈哈哈~他们把官网的10.1版本回滚了, 现在套着个10.x的皮, 安装出来的确是8.8正式版.

屁咧~哈哈哈~他们把官网的10.1版本回滚了, 现在套着个10.x的皮, 安装出来的确是8.8正式版.
I don't think they could roll back the version of their software because of a bug only encountered in the programmer community.

maybe they just dont want to update the installer. and do autoupdate in the users' machine.

hot update is nb

可以可以

Rime users can try this.
https://github.com/rime/weasel/issues/605#issuecomment-797862135

1.54.3  worked

I've merged in the fix from xterm.js, thanks all! Please try out insiders on Monday to verify it works.

Nice work! > I've merged in the fix from xterm.js, thanks all! Please try out insiders on Monday to verify it works.

I've merged in the fix from xterm.js, thanks all! Please try out insiders on Monday to verify it works.

Checked and confirmed that both QQ Pinyin and Rime (Weasel) work fine on today's Insider build.

I've merged in the fix from xterm.js, thanks all! Please try out insiders on Monday to verify it works.

I've checked with Rime IME, Rime works fine in the latest insider release, and I've closed the issue in https://github.com/rime/weasel/issues/605, nice work.

@Python-37 I did very little 😅 all thanks should go to you and the others that helped investigate ❤


Some logging documentation

Following the merging of #6095 I think its reasonable to add some specific information about logging in the post 1.9 world.

Codecov Report

Merging #6498 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6498      +/-   ##
==========================================
- Coverage   40.27%   40.26%   -0.01%
==========================================
  Files         403      403
  Lines       54068    54068
==========================================
- Hits        21775    21773       -2
- Misses      29276    29278       +2
  Partials     3017     3017

Impacted Files
Coverage Δ

models/repo_list.go
66.84% <0%> (-1.06%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bf5af87...5e16c9a. Read the comment docs.


[Synapse] Why does creating base Trigger type not set name but return no error

A number of trigger tests required this change:
- TriggerCreateOrUpdateTriggerOperation createOperation = await TriggerClient.StartCreateOrUpdateTriggerAsync(triggerName, new TriggerResource(new Trigger()));
+ TriggerCreateOrUpdateTriggerOperation createOperation = await TriggerClient.StartCreateOrUpdateTriggerAsync(triggerName, new TriggerResource(new ScheduleTrigger(new ScheduleTriggerRecurrence())));

else the returned trigger does not have the requested name.
And I can confirm using the derived "works", however why is this necessary? Should we not allow instancing Trigger by itself?

Given the age of this issue, closing this as stale.  If tests are still failing, please file a new issue.


Parameters to improve region training

Are there any parameters in the config.yaml file that I can change to improve the training of regions?
Right now I have reached the total_loss score of 0.1351 when running 20000 iterations on 307 training images and 96 validation images, and if I just increase the number of max iterations or lower the learning rate, it doesn't influence the result much. Also, the total_loss score seems to be really good, yet when trying to recognize the regions inside the Loghi pipeline, it's far from ideal.

Can you try and visualize the results using the visualizer.py. That way we can better see what the results are doing, as well as what the GT looks like. Maybe I can give suggestions based on that. Also when you say far from ideal, what sort of issues are you running into

Thank you, I will try to use the visualizer.
Here's a simple illustration, below are a couple of examples of perfect region detection:

If we have some information in the right margin of the page, the post in the middle should be violet (bibliographic post), if however there's nothing in the margins or the information stands in the left margin, the post in the middle should be orange.
Then when we have many posts on one page, the model gets confused and we get plenty of various regions in the middle. Moreover, quite often the model fails to recognize different posts and creates one single region for several posts:

Thank you very much for the images. I'm not sure why the visualization tool doesn't work it might be because the docker doesn't have a graphic interface. In that case, run with the --save flag (I think. Check the -h flag to be certain). But it will give similar images to what you have sent.
For the problem of regions being both purple and red. Is there anything that distinguishes these classes except the textual data. If the only way to tell them apart is through the text, laypa alone will not be enough. Since it doesn't actually read the text and does it mainly based on layout. For example could you tell these regions apart when squinting? If not then you'll probably need to do something with the text itself. You can try to combine these region classes and then post processing for example. If they are visually distinct we'll have to look deeper at the problem.
For the problem of the regions not being apart there might be something. First have a look at the GT if a lot of whitespace is labeled as being part of a class. This has proven to be a major reason for why whitespace is incorrectly assigned. But also know that this is just a problem that can occur when pixels are labeled incorrect. If you know that they will all look like this, you should also have a look at instance segmentation. That unfortunately is not completely finished in laypa. But when working with separated blocks of text might work very well.

For the problem of regions being both purple and red. Is there anything that distinguishes these classes except the textual data.

Yes, the main thing here is not the textual data, but that some textual data exists in the margins. The text in the middle should have a violet class if there also exists some data in the right margin, like here:

or here:

Then when there's nothing in the right margin, it should be orange, like here:

The model is actually sometimes quite good at predicting these cases and assigns the various classes correctly, so I guess it somehow can detect if there is something in the margins or not.

First have a look at the GT if a lot of whitespace is labeled as being part of a class. This has proven to be a major reason for why whitespace is incorrectly assigned.

Thanks for the suggestion. How can I understand if a lot of whitespace is labeled as part of a class? Would this f.ex. be such a case?

Just so I'm clear what would the GT for this type of data look like?

Here's what the GT for that picture looks like:

Here's what I get with Laypa:

Just as a comparison, here's what I get with kraken (I was curious what it can get me so I tried that project as well)

I think you are currently using 1024 for the smallest side? At least that was the default value. You can try to experiment with this value. Or change the resize mode to be scaling.

Thanks for the tips! To try this, do I need to change some parameters in the config file?

Nice to see that kraken performs so well :+1: Maybe it's more suited to your particular problem.
But I don't think the methods are that dissimilar, so why it performs better is something I'm very interested in. But that's for me to figure out :smile:

To try this, do I need to change some parameters in the config file?

Yes, This is done using the PREPROCESS.RESIZE and INPUT.RESIZE parameters and their subparameters

Hi again, I have now experimented with the RESIZE parameter, which unfortunately didn't influence the result. Will be grateful for any other ideas :)
Some further observations: kraken segmentation performs better in terms of detecting regions, but is quite worse than Laypa in terms of drawing correct baselines.

Thank you for your observations.
I'm not sure what to do next to improve results on your side. Maybe it's possible to combine the results from Kraken and Laypa.
I am gonna try to see if implementing the loss method used in Kraken (multiple BCE loss) might improve the region results of Laypa. However, I'm not sure when I'll have time for this, and when it will be finished (vacation also coming up :smile:).

Vacation is important :) Thanks for all your help and have a good rest!


Fix panic create container when sb is fail

When testing cri-o, in some cases e.g. the sandbox is fail, the podInfraState may be nil, then create container will panic ocid.
This fix added a check to podInfraState.
Signed-off-by: Harry Zhang<EMAIL_ADDRESS>

I'm fine with this as long as we understand why the sandbox is nil..
I had the very same panic but didn't fix it because I have my ocid dir messed up by testing and so I ended up creating a container while removing sandbox files under the ocid root directory. That ended up with your panic as well.
I believe conceptually when creating a container in a sandbox it can't be nil. If that's the case adding this fix would be fine I guess..

@resouer you need to sign your commit

I believe conceptually when creating a container in a sandbox it can't be nil

Yes, it's what I'm thinking.

@mrunalp wdyt?

I think technically this should be an assertion as it indicates a bug in the code. Returning an error here hides the real problem. We need to fix the real data race here and maybe consider adding assertions that crash rather than returning errors.

I think technically this should be an assertion as it indicates a bug in the code. Returning an error here hides the real problem. We need to fix the real data race here and maybe consider adding assertions that crash rather than returning errors.

Agree, I'm pretty sure this bug appears when we mess up /var/lib/ocid as I remember triggering it that way.

adding assertions that crash
Do you mean recover the crash, leave it as is, or figure out how to avoid this crash from up layer code? Sorry, not quite follow here :/

Agree, I'm pretty sure this bug appears when we mess up /var/lib/ocid as I remember triggering it that way.

Yes, I can confirm that.

adding assertions that crash
Do you mean recover the crash, leave it as is, or figure out how to avoid this crash from up layer code? Sorry, not quite follow here :/

Agree, I'm pretty sure this bug appears when we mess up /var/lib/ocid as I remember triggering it that way.

Yes, I can confirm that.

@resouer Yes, we should figure out why it happens and fix the root cause. If we want to add check like this then it should't propagate the error but should crash the server like an assertion.

@mrunalp Make sense, let's close this one. I am keep playing cri-o and the root cause should be another topic I believe.


 I don't like /reloadnbe and /reloadnobedexplosions is far too long. I think a good compromise would be /nbe reload, complete with tab completion. However, is it worth having a nested style command for just one command? Perhaps we could also add /nbe info for knowing if sleeping is allowed in this world or not, when multi-world support is eventually added.
Thoughts?

I like the idea of /nbe info. We could pull information from the config and give administrators a somewhat-detailed analysis of what's going on in this world (or even other worlds) without them having to go into the config.

/nbe info sounds like terrible feature bloat for a terrible reason. Add /nbe reload and keep it at that. There's no reason to add commands just because one nested command seems odd. This entire plugin is supposed to be simple and easy to use, not bloated with a bunch of commands and unnecessary features.

There's no reason that we couldn't keep it simple and easy to use while also having optional commands for administrators though, right?

/nbe info sounds like terrible feature bloat for a terrible reason. Add /nbe reload and keep it at that. There's no reason to add commands just because one nested command seems odd. This entire plugin is supposed to be simple and easy to use, not bloated with a bunch of commands and unnecessary features.

I agree with this. Multi-world support will already bloat the plugin up enough. Can't we just leave this plugin be without adding and adding and adding? Do people truly even want more commands?

Added /nbe as of https://github.com/TehBrian/NoBedExplosions/commit/46967307b3ae9ebd67e4f3f197dda7e2dc308a6b.


fluxctl version command should print the client and server versions

Like kubectl or helm, fluxctl should print both client and server versions. If fluxd is not accessible (port forward crashes or no pods are available) the version command should print the client version only.

It would involve an addition to the HTTP API, which is non-trivial (I removed the hacktoberfest label again after realising that)


Requested change to TapTree1.jpg

I think the last node should be key4.
Also consider moving to keyA, keyB as we use letters in the next image

Thank you. Addressed here in #101.


updates from Daisy Marc and Emily

Please use this template to ensure easier processing of your pull request
Category

[x ] Content fix
[x ] New article

Docs Build status updates of commit 731d283:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/power-automate-vs-logic-apps.md
:bulb:Suggestion
View
Details

.frontmatter/content/mediaDb.json
:white_check_mark:Succeeded

.frontmatter/templates/article.md
:white_check_mark:Succeeded

CHANGELOG.md
:white_check_mark:Succeeded

Community/TOC.md
:white_check_mark:Succeeded
View

Community/how-to-share-org-wide-communications-in-microsoft-365.md
:white_check_mark:Succeeded
View

Community/identifying-your-sharepoint-champions.md
:white_check_mark:Succeeded
View

Community/importing-data.md
:white_check_mark:Succeeded
View

Community/index.yml
:white_check_mark:Succeeded
View

Community/information-architecture-site-topology.md
:white_check_mark:Succeeded
View

Community/intranet-content-sources.md
:white_check_mark:Succeeded
View

Community/library-scenarios.md
:white_check_mark:Succeeded
View

Community/microsoft-365-search-technologies.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--management-of-content.md
:white_check_mark:Succeeded
View

frontmatter.json
:white_check_mark:Succeeded

Community/power-automate-vs-logic-apps.md

Line 38, Column 28: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/power-platform/admin/wp-data-loss-prevention' will be broken in isolated environments. Replace with a relative link.
Line 38, Column 126: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/logic-apps/block-connections-connectors' will be broken in isolated environments. Replace with a relative link.
Line 44, Column 39: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-functions/functions-compare-logic-apps-ms-flow-webjobs#compare-microsoft-power-automate-and-azure-logic-apps' will be broken in isolated environments. Replace with a relative link.
Line 67, Column 1: [Suggestion: duplicate-alt-text - See documentation] Alt text 'Mobile view of Power Automate' is duplicated. Within an article, alt text must be unique.
Line 69, Column 262: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/logic-apps/export-from-microsoft-flow-logic-app-template' will be broken in isolated environments. Replace with a relative link.
Line 82, Column 1: [Suggestion: duplicate-alt-text - See documentation] Alt text 'Mobile view of Power Automate' is duplicated. Within an article, alt text must be unique.
Line 92, Column 83: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/logic-apps/manage-logic-apps-with-visual-studio' will be broken in isolated environments. Replace with a relative link.
Line 120, Column 51: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/learn/browse/?terms=Automate&products=power-platform' will be broken in isolated environments. Replace with a relative link.
Line 124, Column 87: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/learn/browse/?products=azure&terms=Logic%20Apps' will be broken in isolated environments. Replace with a relative link.

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


Add down/up movement in fuzzy-finder list using tab/shift-tab

I recently discovered this behaviour in the chrome address bar and find it incredibly usefull compared to using arrow of additional character

I'm not sure this should be the default but I'm not sure it shouldn't either. I don't think it will conflict with any of the various fuzzy-finder behaviors ...
/cc @atom/feedback


Supporting Vault Implicit OIDC Flow for User UI Login

Adding support for users to authenticate with a Vault implicit OIDC token.

Not ready for review yet, PR is open to generate staging image


feat: Hero Pattern video

Hero Pattern Video
Description

Hero Pattern Video
Webm as primary
Mp4 as fallback video
PNG as img fallback

Needs background color fixed
https://user-images.githubusercontent.com/3803431/173866141-86c435bc-e3e7-45a3-9948-c16f883dda44.mov
Review Checklist

[ ] I have added documentation for new/changed functionality in this PR or in openfga.dev
[x] The correct base branch is being used, if not main

New files seem to have the correct background colour, but we should try to test this across more browsers/devices to make sure.

One thing I've noticed is that the videos seem to have a tiny border of padding on them (in the files) so the pattern seems to change size from the static image pattern when the browser loads the video and makes the switch.
Also, what file size should we be aiming for? These videos are under a megabyte each; as long as they're not render blocking that's probably fine for our page load, but we should still be conscious of how much bandwidth we're consuming.

@matldupont is there a way to use the SVG version as a fallback so that we don't even need the .png?

I've found that forcing Chrome and Safari to use mp4 and letting Firefox use webm seems to resolve colour rendering issues across all three browsers. I'd appreciate it if someone could double-check my work. 🙇
@rhamzeh @adriantam


Update navigation header to include phase banner

Ticket: https://trello.com/c/6hvQZTVK/259-update-navigation-header

@alex-ju - all changes have been done except for moving the template.


Exclude file from coverage report

Is there a way to exclude some files from the report without affecting the tests?
Something like:
remapOptions: {
  exclude: 'PATH'
}

As this lib only reports on whatever was instrumented, you would need to not instrument those sources to exclude them from being reported on. Assuming you were using webpack with the istanbul instrumenter loader, you can exclude files via webpacks config:
test: /src\/.+\.ts$/,
exclude: [
  /node_modules/,
  /\.spec\.ts$/,
  /path\/to\/some\/file/.ts/
],
loader: 'istanbul-instrumenter-loader',
enforce: 'post'

Actually I have an embedded webpack inside angular cli, so I only have access to karma config file.

Ah ok, in which case the CLI has baked in support for this: https://github.com/angular/angular-cli/pull/4966

Thanks so much didn't know about that!


Commit transforms done with editor gizmo on tool mode switch.

Supplementary but not dependent on: #86805 and #86804
This affects 2D and 3D.
Currently you can switch gizmo tool modes while an edit is in progress, the tool will switch, but the previous tools action will continue, which is a bit strange.
https://github.com/godotengine/godot/assets/105675984/97ef63e7-98ae-4f86-92fb-f03c0d5b1204
This PR will prevent this, by committing the transform in the editor when switching tool modes which seems like the more expected and less confusing result.
https://github.com/godotengine/godot/assets/105675984/90a9d681-5c91-40c6-acc0-f29a21e9cf30

When making several additions from suggestions please use the batch feature, it's next to the commit one 🙂

When making several additions from suggestions please use the batch feature, it's next to the commit one 🙂

Thanks 😅

Changes made and tested.
Thanks for your help AThousandShips.

Ok, I think it's good. Let me know if I missed anything.


lapack-netlib/SRC/*.F files not pre-processed

When I try to "make" OpenBLAS 0.3.0, I run into problems with *.F files in lapack-netlib. It seems as if the make rules were not properly set up for that extension. Here is an excerpt from the compilation log:
gfortran -O2 -Wall -m64 -fPIC -c -o ssytrd_sy2sb.o ssytrd_sy2sb.f
gfortran    -F -o ssytrd_sb2st.f ssytrd_sb2st.F
ssytrd_sb2st.f:233:2:

 #if defined(_OPENMP)
  1
Warning: Illegal preprocessor directive

(...)

f951: Warning: command line option ‘-F-o’ is valid for C/C++/ObjC/ObjC++ but not for Fortran

In the end the build fails due to undefined references or multiple definitions to routines defined in those *.F files.
I was able to build OpenBLAS successfully only after renaming *.F to *.f, and changing the compiler invocation in Makefile.rule from
FC = gfortran

to
FC = gfortran -cpp

so that it preprocesses all files using the C preprocessor. My compiler is gfortran 7.3.1, but the same happens with the current experimental gfortran 9.0.0. And I got stuck on the very same point with ifort 2018.

Where does the gfortran -F come from in your log excerpt ?

That's what I ask myself. I suppose that my make (GNU Make 4.2.1), when asked to produce a specific .o, uses some default .F -> .f rule, followed by .f -> .o. All this instead of using .F -> .o that is provided in the Makefile. But that's a speculation; I am not very strong with make.

Anything in your environment, CFLAGS etc that could cause this ? And/or do you see this -F flag in the make.inc that gets created in lapack-netlib by the toplevel Makefile ?

All right, half of the problem (the strange make rule) solved itself when I cleaned my working copy of the repository, which got messy due to switching of different compilers. Still, I am not able to make ifort correctly pre-process the *.F files.
When I use FC = ifort, the compilation fails with:
ifort -O2 -i8 -fopenmp -fPIC -c dsytrd_sb2st.F -o dsytrd_sb2st.o
dsytrd_sb2st.F(484): #error: #if: syntax error.

When I use FC = ifort -fpp, it ends the same:
ifort -fpp -O2 -i8 -fopenmp -fPIC -c dsytrd_sb2st.F -o dsytrd_sb2st.o
dsytrd_sb2st.F(484): #error: #if: syntax error.

I have ifort 18.0.1 and all I did with respect to the release-0.3.0 branch is the following:
diff --git a/Makefile.rule b/Makefile.rule
index 62bf63df..8a2481fe 100644
--- a/Makefile.rule
+++ b/Makefile.rule
@@ -19,10 +19,10 @@ VERSION = 0.3.0.dev

 # C compiler including binary type(32bit / 64bit). Default is gcc.
 # Don't use Intel Compiler or PGI, it won't generate right codes as I expect.
-# CC = gcc
+CC = icc

 # Fortran compiler. Default is g77.
-# FC = gfortran
+FC = ifort

 # Even you can specify cross compiler. Meanwhile, please set HOSTCC.

diff --git a/Makefile.system b/Makefile.system
index 9720b317..dcd82be3 100644
--- a/Makefile.system
+++ b/Makefile.system
@@ -424,7 +424,7 @@ CCOMMON_OPT    += -fopenmp
 endif

 ifeq ($(C_COMPILER), INTEL)
-CCOMMON_OPT    += -openmp
+CCOMMON_OPT    += -fopenmp
 endif

 ifeq ($(C_COMPILER), PGI)
@@ -704,7 +704,7 @@ FCOMMON_OPT += -i8
 endif
 endif
 ifeq ($(USE_OPENMP), 1)
-FCOMMON_OPT += -openmp
+FCOMMON_OPT += -fopenmp
 endif
 endif

Searching for "ifort" and "#if: syntax error" returns a hit on a stackoverflow posting where someone apparently had the same problem a month ago (without telling here...) and managed to solve (or work around) it by changing the #if defined on that source line to an #ifdef.
To me this seems to be a bug in ifort 18.0.1 ...
Note that the same #if defined (_OPENMP) && _OPENMP >= 201307L also occurs in two other source files there, it is unclear if they also triggered the error

Thank you very much for support, I should be able to do this research on my own next time. It turns out that if I drop the trailing L, leaving just
#if defined (_OPENMP) && _OPENMP >= 201307

these lines compile well. I tried updating to ifort 18.0.2 without any effect, so I will discuss this issue with Intel people.

I noticed this was commented on in the stackoverflow thread as well. Arguably the "L" designation on the constant is C/C++ idiom and not valid fortran, so support for it may be implementation dependent (and as it serves no useful purpose, I guess I should just remove it - was probably thinking of the more common STDC_VERSION test when I wrote that)


Collections to kotools.types.collection package

Description
Move all declarations related to collections to the kotools.types.collection package.
Checklist

[x] Implement.
[x] Test.
[x] Refactor.
[x] Update Work in progress section in changelog.
[ ] Complete this comment.

Done.

Replace existing builders of all collections like the builders of NotBlankString.

Update the serialization of the following types:

[ ] NotEmptyList
[ ] NotEmptySet
[ ] NotEmptyMap.


Decoding quality is very poor in some situation.

For example, decoding original.mp4 by libopenh264 and encoding again by libx264 results in:
https://github.com/cisco/openh264/assets/32232575/8b2f36db-d92a-4df9-a927-210338b9e076
while decoding the same video by h264 decoder in ffmpeg and encoding again by libx264 results in:
https://github.com/cisco/openh264/assets/32232575/9c9de0d2-568e-4ae2-ac94-909d9e8af46a
Is any important feature of h264 missing from openh264?

Still poor quality with your latest fixes waiting fro review?

README.md
README.md

Still poor quality with your latest fixes waiting fro review?

Yes. The pull request https://github.com/cisco/openh264/pull/3707 fixes only the reordering of the decoded frames. I guess this issue is in the decoding algorithm.

Just tested viewing this mp4 in firefox and it looks better but some artifacts are still there


Fix MySQL and PostgreSQL GitHub Actions

Fixes #3347
Changes proposed in this PR:

Replace webdrivers gem with selenium-webdriver gem (https://github.com/titusfortner/webdrivers states "If you can update to the latest version of Selenium (4.11+), please do so and stop requiring this gem.")
Disable rack-attack from throttling "/users/sign_in" path on Rails test environment
Address Faker deprecation warning NOTE: Faker::Internet.safe_email is deprecated; use email instead. It will be removed on or after 2023-10. (More here: https://github.com/faker-ruby/faker/pull/2733)
Small changes to enable existing tests to pass (here: https://github.com/DMPRoadmap/roadmap/pull/3375/commits/a5710adda20baa288f5a4451526d9f49de8c37ef)
Fix mysql.yml and postgres.yml workflows by removing duplicate node-version: statements

@aaronskiba looks good as it clearly gets rid of breaking Github actions. Not sure why Marta's commits included. Might be better to pull code from development again and add your changes.

@aaronskiba looks good as it clearly gets rid of breaking Github actions. Not sure why Marta's commits included. Might be better to pull code from development again and add your changes.

Thanks. My bad, I branched off main. The PR can now be found here: https://github.com/DMPRoadmap/roadmap/pull/3376


bug: Multiple modules of the same type are swapped between protocol setup and execution

Overview
In protocols with multiple modules of the same type, the wrong module will be controlled.
Steps to reproduce
I've tested this with two Temperature Module GEN1s and a non-refresh OT-2 running the v5.0 beta.
@nusrat813 has tested this with a refresh OT-2 running v4.7.

Load the two Temperature Modules into slots 1 and 3.
Plug the right module into the left  USB port and the left module into the right  USB port.
Upload the test protocol.
Confirm that in the module setup, the USB ports match reality. It should look like this:
Run the protocol.

Test protocol
metadata = {"apiLevel": "2.11"}

def run(protocol):
    tip_rack = protocol.load_labware("opentrons_96_tiprack_300ul", 2)
    tm_right = protocol.load_module("temperature module", 3)
    tm_left = protocol.load_module("temperature module", 1)
    plate_right = tm_right.load_labware("biorad_96_wellplate_200ul_pcr")
    plate_left = tm_left.load_labware("biorad_96_wellplate_200ul_pcr")

    pipette = protocol.load_instrument("p300_single_gen2", mount="left", tip_racks=[tip_rack])

    tm_right.set_temperature(40)
    tm_left.set_temperature(20)

    pipette.transfer(150, plate_right["A1"], plate_left["A1"])

Current behavior
The module on the right goes to 20 °C and the module on the left goes to 40 °C.
Expected behavior
The opposite. The module on the right should go to 40 °C and the module on the left should go to 20 °C.

Possibly caused by #9253.

Investigation results on v5.0.1:

PAPIv2 / ProtocolEngine

Modules are "consumed" in descending order by port number

App

Modules are assumed to be "consumed" in ascending order by port number

App instructions

Users are instructed to plug modules in according to deck slot

Conclusions:

The app and the API disagree on how load order maps to physical port order
The app's instructions are straight up wrong and I can't think of any way we could make the system behave as the instructions specify

we have a similar issue with two mag-modules but the issue is semi-random and occurs or not in the same protocol at a given code locations (works in the beginning of the protocol and swaps the deviced further on)
I suggest the program be improved to avoid having to sort anything, devices are declared on top of the code and should be addressed correctly I believe.
the fact our error is semi random suggests a more complex issue with USB ports being somehow wrongly addressed/incremented! ([ ref:_00Df44lpsm._5002S1SsrOb:ref ])

@splaisan Can you tell me what you see as:

The version of your Opentrons App:
Your OT-2's server version:

(In these example screenshots, mine is 5.1.0-beta.0, but yours will probably say something different.)
The modules swapping themselves in the middle of a protocol is pretty alarming. Can you share your full protocol file along with any custom labware definitions that might be required to run it?

@SyntaxColoring I am working with this customer in Salesforce, but they are on 5.0.2 app and robot server version.
@splaisan Please provide your protocol here or in our email correspondence.

Hi @braldrich
I already provided the protocol with my above-linked ticket few days ago. and explained our issue in the ticket.
Can you access this directly? I am not at the lab now.

Archive.zip
Protocols here


https://laravel-world.com has no Frontend?

Hi, Author
This is great package
If I'm not mistaken the current domain purpose only for API?
it would be good if we add some UI to show the Data
I would love to help creating the UI, what do you think?
also, I like to know where the source truth from this coutry and city seeder, and perhaps is there any step to update the seeder in proper way

We could use reactjs and tailwindcss for this, or even better with NextJS
what do you think?

@sluxzer i think your idea of using react and tailwind is perfect however please access the stack below:
React + PrimeReact + Primeflex
https://primereact.org/
https://primeflex.org/
Let me know what do you think?

I'll looking it to it.
anyway, this feature will great for https://hacktoberfest.com/


Presence of Xcode project causing builds to fail

https://swiftpackageindex.com/GEOSwift/GEOSwift/builds has builds that are failing because xcodebuild is seeing the Xcode project in the repo root. We keep that there in order to support Carthage. What we do in our CI pipelines is delete the xcodeproj before building the Swift package with xcodebuild. It's a bit of a hack, so if there are better ways to do this, I'm definitely open. I'd love for our project to show more green on the package index though.

Hi Andrew, we've got a process in place to direct our build system to pick up schemes defined in an Xcode project file (see details here:
https://blog.swiftpackageindex.com/posts/the-swift-package-index-metadata-file-first-steps/)
So I think we could pick up those schemes without having to introduce a workaround to ignore your project file if you added a .spi.yml file like the following:
version: 1
builder:
  configs:
  - platform: macos
    scheme: GEOSwift-macOS
  ...

If that doesn't work for your case I think we could extend this file with an attribute to ignore the project file for a given (or all) platforms.

Hi Andrew, we've got a process in place to direct our build system to pick up schemes defined in an Xcode project file (see details here:
https://blog.swiftpackageindex.com/posts/the-swift-package-index-metadata-file-first-steps/)
So I think we could pick up those schemes without having to introduce a workaround to ignore your project file if you added a .spi.yml file like the following:
version: 1
builder:
  configs:
  - platform: macos
    scheme: GEOSwift-macOS
  ...

If that doesn't work for your case I think we could extend this file with an attribute to ignore the project file for a given (or all) platforms.

Our Xcode project is configured for Carthage (not generated by SPM) and for it to build, you have to run $ carthage update after cloning to build the dependencies.
One question I do have is about this bit from the Builds FAQ:

How are packages built?
The build system runs either xcodebuild or swift build depending on the platform and specified Swift versions.
When running xcodebuild, we apply some heuristics to find the correct scheme to build. If a package contains a single scheme (as reported by xcodebuild -list), the build system will use that scheme. If xcodebuild -list reports multiple schemes, the build system will choose the one ending in -Package. Otherwise, it will try removing any Xcode project and workspace files and rely on SPM’s scheme discovery to autogenerate a package scheme.

From what I can tell from this log, for example, the build system indicates that it did not find any scheme ending in -Package, but I can't tell whether it tries the part in that final sentence about removing the Xcode project and workspace files. That's exactly what would be required, so I'm not sure why it'd be failing.

Our Xcode project is configured for Carthage (not generated by SPM) and for it to build, you have to run $ carthage update after cloning to build the dependencies.
One question I do have is about this bit from the Builds FAQ:

How are packages built?
The build system runs either xcodebuild or swift build depending on the platform and specified Swift versions.
When running xcodebuild, we apply some heuristics to find the correct scheme to build. If a package contains a single scheme (as reported by xcodebuild -list), the build system will use that scheme. If xcodebuild -list reports multiple schemes, the build system will choose the one ending in -Package. Otherwise, it will try removing any Xcode project and workspace files and rely on SPM’s scheme discovery to autogenerate a package scheme.

From what I can tell from this log, for example, the build system indicates that it did not find any scheme ending in -Package, but I can't tell whether it tries the part in that final sentence about removing the Xcode project and workspace files. That's exactly what would be required, so I'm not sure why it'd be failing.

Right, I was thinking it might take more than just picking the right scheme.
You're right that the deletion should kick in but there might be some other condition interfering. I'll take a closer look!

Right, I was thinking it might take more than just picking the right scheme.
You're right that the deletion should kick in but there might be some other condition interfering. I'll take a closer look!

Turns out rm -rf "*.xcodeproj" does not delete the project folder. TIL that double quotes don't glob and I cannot believe in almost three decades of Unix use I've not encountered this 😮
It needs to be rm -rf *.xcodeproj.
I always thought ' doesn't glob while " does - but the difference is only $ expansion, not globs.
Will push the fix shortly and rebuild your packages. Thanks a lot for spotting this!

Turns out rm -rf "*.xcodeproj" does not delete the project folder. TIL that double quotes don't glob and I cannot believe in almost three decades of Unix use I've not encountered this 😮
It needs to be rm -rf *.xcodeproj.
I always thought ' doesn't glob while " does - but the difference is only $ expansion, not globs.
Will push the fix shortly and rebuild your packages. Thanks a lot for spotting this!

Looks like it's all working now:

https://swiftpackageindex.com/GEOSwift/GEOSwift/builds
Thanks again for the report!

Looks like it's all working now:

https://swiftpackageindex.com/GEOSwift/GEOSwift/builds
Thanks again for the report!

Very interesting. Thanks for the fix!

Very interesting. Thanks for the fix!

Another question — 2 related repos are suffering from the same problem (geos, GEOSwiftMapKit). Is there a way for me to rerun the builds without pushing any changes?

Another question — 2 related repos are suffering from the same problem (geos, GEOSwiftMapKit). Is there a way for me to rerun the builds without pushing any changes?

Other than by pushing changes and/or releases, we currently don't support that, no. But I'll just reset those builds for you and they should be refreshed in a couple of hours.

Other than by pushing changes and/or releases, we currently don't support that, no. But I'll just reset those builds for you and they should be refreshed in a couple of hours.

Thank you

Thank you


GraphiQL doesn't seem to work with GraphQL-java

I'm just playing with adding GraphQL to my project, and so am using GraphQL-java for it.
I've added a single controller (Spring MVC) that serves up the example GraphQL schema from the readme file, both consuming application/graphql to take the incoming query directly and consuming application/json to take a JSON object with the query and variables in separate fields, as this is what GraphiQL sends.
I have then pointed GraphiQL - both the OSX Electron app version and the webapp version - at my endpoints, and I can successfully run queries against it. However, some part of the introspection doesn't work which means that:

I don't get autocomplete on the queries
I don't get the documentation showing up
When the page first loads, I get the schema showing up in the results pane (http://graphql-swapi.parseapp.com doesn't do this)

I've not yet gone through the schema that is produced to see what the issue is, but I will do soon.

 Doing that and it all works. :)


 It was green with previous workflow, but it is now red Meaning it fails

That's not the CircleCI badge. I removed them since those CI's are redundant (and disabled)


chore: update url in pyproject.toml file

Description
#1
Type of change docs
Features (Optional)
changed the urls

can this simple url fix be merged and then we deal with broken tests separately?
re: tests, looks like something to do with the fact that dtypes can be different on different platforms? (https://stackoverflow.com/questions/49751000/how-does-numpy-determine-the-array-data-type-when-it-contains-multiple-dtypes#:~:text=in general U%23%2C you need to note that it consists of two parts%3B the U which denotes a Unicode dtype and the %23 shows the number of elements that it can hold --but it can be different in different platforms.)


Opening rrd file with same application id as current one does not work

Describe the bug
When trying to load a different rrd file with the same application_id as the current one, nothing happens. (both by drag and drop, and by using the load dialog).
Opening from the terminal starts a separate Rerun instance, which I think is good.
To Reproduce
Create two rrd files
import rerun as rr
import numpy as np
import time

rr.init("test", spawn=True)

rr.save("test1.rrd")
rr.log("image", rr.Image(0.3 * np.random.rand(100,100,3)))

time.sleep(5.0)

rr.save("test2.rrd")
rr.log("image", rr.Image(np.random.rand(100,100,3)))

Drag and drop one of the two files into the viewer (rrd file shows up).
Drag and drop the other file into the viewer (-> nothing changes).
Expected behavior
Open the new rrd file. Showing both in the list of recent recordings.
Rerun version
rerun_py 0.10.0-alpha.7+dev [rustc 1.72.1 (d5c2e9c34 2023-09-13), LLVM 16.0.5] x86_64-unknown-linux-gnu main 47414c8, built 2023-10-24T12:00:38Z

This is probably due to:

https://github.com/rerun-io/rerun/issues/3793

tldr: Both rrd files actually have the same application id and recording id because in Python, recording id is set to authkey() by default which is random but constant per process


Add-Migration has no 'IgnoreChanges' parameter

When I run Add-Migration InitialCreate –IgnoreChanges in package manager console, I get Add-Migration : A parameter cannot be found that matches parameter name 'IgnoreChanges'.
I just created this project yesterday and I'm running VS2019 which shows no relevant updates available.

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

ID: 30985321-a087-4ba8-1ef2-1311532ceaf5
Version Independent ID: 97a0e081-b208-8042-5964-02bccb4a1db0
Content: Code First Migrations with an existing database - EF6
Content Source: entity-framework/ef6/modeling/code-first/migrations/existing-database.md
Product: entity-framework
Technology: entity-framework-6
GitHub Login: @divega
Microsoft Alias: avickers

@steamwings - That could be product issue. Are you using EF Core or EF6?

It's an ASP.NET Core project. I can see I have the EF6 tools component installed, but I don't see a separate component to install for EF Core.

Can you share a repro project which we can investigate?
Moving this to EF6 repo.


added my profile to readme in "little bit of everything"

What type of PR is this? (check all applicable)

[ ] 🚀 Added Name
[ ] ✨ Feature
[ ] ✅ Joined Community
[ ] 🌟 ed the repo
[ ] 🐛 Grammatical Error
[ ] 📝 Documentation Update
[ ] 🚩 Other

Description
#575
Add Link of GitHub Profile

Thanks for opening this pull request! Do join our discord server DevSpace, a place for Awesome Developer's :)

already joined 👍


az login missing documentation for return object

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
In the documentation for az login there is no mention of nor description for the object that az login returns.
To Reproduce

Read the documentation for az login.

Expected behavior
You can find information about the object that the az login command returns.
Actual behavior
There is no mention at all that az login returns an object at all, let alone anything about the object.
Environment summary
N/A
Additional context
It would be very handy to have reference documentation for the objects returned for all of the az commands.

Due to the limitation of Bash and Command Prompt that only string can be returned (unlike PowerShell), az login returns a JSON in the form of
[
  {
    "cloudName": "AzureCloud",
    "id": "00000000-0000-0000-0000-000000000000",
    "isDefault": true,
    "name": "xxx",
    "state": "Enabled",
    "tenantId": "00000000-0000-0000-0000-000000000000",
    "user": {
      "name"<EMAIL_ADDRESS>      "type": "user"
    }
  },
  ...
]

For other commands like az storage account show, the returned JSON is the same as those defined in Azure REST API.

Thanks for the prompt response @jiasli. Even thought the az login command returns a string, it's in the form of a JSON object (the "O" in JSON) and should be documented. If other commands simply return the same JSON object(s) as the REST API, stating that with a link to the reference documentation for the REST API object would be sufficient.

Thanks for the great suggestion. We are considering linking CLI and underlying REST API in the doc in the future.


iFrame based menu

It is MVP - not finished yet!

Thank you so much for your work and idea.
We have added Paul patches to our upstream.
I propose to carry out all changes there now.


mcunet-10fps inference failing shows nonperson always

With the help of the tinyengine/tutorial I am able to run the mcunet_5ps(default) and able to see the inference is working fine, so tried changing model to mcunet_10fps in tinyengine/tutorial/examples/vww.py file able to run the code but the inference is failing (always showing no person though the person is present).
anything I need to take care to run mcunet_10fps?
@meenchen @RaymondWang0 please help, thanks in advance.

@meenchen @RaymondWang0 not sure you both have seen the issue, kindly reminding the issue.

Hi @brainchip-india,
In the tutorial, the application code assumes the resolution of the model is 80x80, but for mcunet_10fps, it is actually 64x64. You will need to change the data loading part in the main.cpp for different models.

Thanks @meenchen it worked, it's better you log it somewhere in the Readme for newbies like me.


[Bug]  Small problem with responsiveness of select2 when using for tags

Bug report
What I did
I simply used
    $this->crud->addField([
        'type' => 'relationship',
        'name' => 'assignmentTypes',
        'label' => 'Incarichi',
        'placeholder' => 'Scegli uno o più incarichi'
    ]);

to generate a select2 for tags
What I expected to happen
It works, it looks well also resizing screen
What happened
At smaller screen, tags are not looking weel

What I've already tried to fix it
Nothing, It is not a big problem
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
PHP VERSION:
PHP 8.0.3 (cli) (built: Mar  2 2021 23:33:56) ( NTS Visual C++ 2019 x64 )
Copyright (c) The PHP Group
Zend Engine v4.0.3, Copyright (c) Zend Technologies
LARAVEL VERSION:
v8.34.0@81892ca110795a9c46c7e198cba7763bfd2af0bf
BACKPACK VERSION:
4.1.40@ecbe7676535d3c9121227329d62cad9978d29fee

Hi @realtebo, thank you for reporting the issue.
I've created a PR (https://github.com/Laravel-Backpack/CRUD/pull/3679) to fix this issue, let's close this one and move conversation there 🙌


Is 'name' an xray supported attribute?

If it is, a Dataset constructor should take a list of DataArrays, and use their names as keys? (and anywhere else you need to provide a dict-like mapping with names)
If it's not, we potentially shouldn't be using it in the internals.
I think it's the first, given it's in the docs (although not throughout the docs).

DataArray.name is a valid attribute -- it's filled in with the key corresponding to DataArrays in Datasets. Dataset.name is not valid. This is analogous to the situation on DataFrame and Series.
Converting a list of DataArrays into a Dataset does sound like a useful thing, but to me that functionality is would be a closer fit for a hypothetical merge function (#417). I was envisioning as taking a list of Dataset objects, but it would be straightforward to merge in DataArray objects, too.

Great, that's clear, cheers @shoyer


V3

This removes the caching function, adds the ability to upload images to assets, and better docs.
BREAKING CHANGE: Project.getCommentReplies now has id first, earlier it was last.

Thanks to uwv on scratch for helping with the code!


Console doesn't show anything

All it says is the that the platform is windows, that the server started, and "If your device doesn't show up after connecting the device, please make sure dev mode is enabled on headset and cable or usb port is not damaged." I know the port and cable works because I've been using it with quest link just fine, and I double checked that I had dev mode on in the headset.

@Komrade6788 Having the same issue. Have you find a solution since then? Tried reinstalling, giving admin priorities, but to no avail.

Having the same problem in Bazzite linux. HMD keeps connecting over WiFi and won't use the cable.

For me, this turned out to be the lack of detailed instructions on enabling developer mode for the Quest 2. Most guides show just enabling it in the headset, this is no longer enough. You must install the mobile app on your phone, connect to the headset, and enable developer mode via the app.


feature: Add the durations of operations to the logs

Feature Request
Describe the Feature Request
We have a quite number of logs to inform the admins/developers. It would be nice to also add the durations of operations (especially for Agents)

We do not need this for now.


Create 57-Insert-Interval.cs

File(s) Modified: 57-Insert-Interval.cs
Language(s) Used: c#.
Submission URL: _https://leetcode.com/submissions/detail/787873123/_

Thanks, @notauserx!


Replaced broken Tallycoin widget with a button to the donation page

The Tallycoin widget is currently broken on the homepage seemingly due to a code upgrade on their end.
This PR removes the widget and replaces it with a simple button that links to the PodcastIndex campaign page: https://tallycoin.app/@podcastindex/support-podcastindex-t5x9vv/
Screenshot:

Thank you brother Eric. 🙏


count(): Parameter must be an array or an object that implements Countable

Version information

Laravel: v5.7.19
Voyager: v1.1.10
PHP: 7.2
Database: MySQL 5.7.21

Description
ErrorException (E_ERROR)
count(): Parameter must be an array or an object that implements Countable (View: resources/views/vendor/voyager/events/browse.blade.php)
Steps To Reproduce
Steps to reproduce the behavior:

Just create a new BREAD Events
Then when trying to create first event
Then on the Event List page, it shows this error
The error is somewhere in this line, in the

File- project/vendor/tcg/voyager/resources/views/bread/browse.blade.php
Line number - 112
Line - @if (count(json_decode($data->{$row->field})) > 0)

The problem is that with PHP7.X versions only entities implementing Countable interface can be used as a countable and count() function is only able to use countables. So while count(json_decode('{}', true))  is working as expected, count(json_decode('{}')) will throw an error. (check this: https://3v4l.org/4JF9V)
But anyway, I guess checking the condition with empty would be more performant than counting the vals and checking the result with > 0
I can open a detailed PR if nobody is picking this up.

In the http://php.net/manual/en/function.json-decode.php explains it clearly why the use of true make it work as expected:

In the http://php.net/manual/en/function.json-decode.php explains it clearly why the use of true make it work as expected:

that's why I said that :) arrays, even when they're empty, are countable.

Yes, but json_decode without the explicit use of the second argument, it defaults to false, therefore it's not converted to associative array.

Fixed in https://github.com/the-control-group/voyager/pull/3909 commit https://github.com/the-control-group/voyager/pull/3909/commits/469dad1b1616bfcde0111ef9300d6a746653adbc


Wrong SourceIdentifier for Config Rule

Awesome code guys, but I found this, the line 813 from file aws-config-enable-rules.yaml uses for the rule rS3BucketServerSideEncryptionEnabledConfigRule the source identifier S3_BUCKET_PUBLIC_WRITE_PROHIBITED, but it should be S3_BUCKET_SERVER_SIDE_ENCRYPTION_ENABLED according to s3-bucket-server-side-encryption-enabled
Thanks in advance,

This looks like automated job-hunting spam, so I'm closing it. If the author wants to clarify exactly what genuine problem they're reporting, and what the suggested action is, we can revisit.

heheheheh, thanks for the offer bro, but I'm not looking for job, the problem that you have is the line 813 of the file cloud-platform-infrastructure/cloudformation/aws-account-baseline-templates/aws-config-cloudtrail-logging/aws-config-enable-rules.yaml, you mention as description "Checks for explicit denies on put-object requests without server side encryption.", basically you're saying that it checks is a bucket is encrypted or no, but you are using an AWS manged rule that checks for public access NOT for SSE, to be clear you are using the wrong rule, and again, really good job, it's awesome.
Looks like this ritgh now:
        SourceIdentifier: S3_BUCKET_PUBLIC_WRITE_PROHIBITED
Should be like this:
        SourceIdentifier: S3_BUCKET_SERVER_SIDE_ENCRYPTION_ENABLED


Problems on Binary Search in C++

Hi..... @smv1999
Please assign me to add some problems on binary search in cpp ?
Problems:

First and last occurrence of an element in a sorted array.
Count the frequency of an element in a sorted array.
Number of times a sorted array is rotated.
Find the element in an rotated sorted array.

/assign

Please review @smv1999

@smv1999 this issue is open or not??

Closing this issue


Add a Requirements title question

The first question for building a brief needs to be a title that it can be referred to later.
Words taken from the prototype and agreed with Ralph.

:+1:

Oh, I just did the same thing with locations (https://github.com/alphagov/digitalmarketplace-frameworks/pull/191), should've checked first


Data Grid Widget

Feel free to comment additional suggestions.
Background
Although the table API is powerful, it is not the most friendly API for users wanting to quickly display data and requires a lot of manual setup. A higher level API written on top of the table API is desired. Something similar to the 0.6 simple table API but more powerful.
Required Functionality

Performant - easily display 100k's of rows
Easy
Column level control item types
Per-column settings
Sizing policies
Row/column appending
Row/column insertion
Sorting
Row/column deletion
Filtering
Selections
Reordering
Other settings

Methods
This will be object oriented and thus will be operated on through various methods. Below are the current public non-obvious methods:

insert_column(...) &  insert_row(...)
append_row(...) &  append_column(...)
delete_row(...) & delete_column(...)
get_cell_value(...) &  set_cell_value(...)
hide_column(...) &  show_column(...)
hide_row(...) &  show_row(...)
get_column(...) & set_column(...)
get_row(...) & set_row(...)
get_selections(...) & set_selections(...)
highlight_row(...) & highlight_column(...) & highlight_cell(...) & undoing these

Here are some suggestions. Not sure if they are superfluous or too difficult, but here goes.

Easy way to make the font of the header and first column (column #0, I guess) bold or set a specific font (maybe has already been solved in the Tables API and therefore also in Datagrid).
Aligning the values in the cell (left, centre, right), especially to the right for numbers.
Get the row(s), column(s) or cell(s) that are selected by the user.

With regard to performant, I'd like to add that it should be performant to

load data, e.g. from a Pandas dataframe
interact with the datagrid, e.g. show, scroll, filter data and the like.

Be able to retrieve the filters, etc. that have been applied to the data by the end user. For example, if the end user wants to export the data selection, you would need to know the applied filters.

This seems very interesting for my project!
I’d like to have the ability to fill the table from the top, in anti-chronological order without any fuss.
i.e. appending a row results in it being displayed just under the header.
I haven’t found a reliable way to do this in the current table implementation and using the before parameter of dpg.table_row() doesn’t seem to work.

Please add this feature, and this will be very useful for date science baed project, thank you!


The RefType regex for character is capturing extraneous punctuation

Here are some examples

The captured punctuation is also included the < and > of HTML tags making it difficult to strip the tags from the text when rendering.

Closed by commit fcc44a9a0cf86b001f5c74388535c0e2670d0d13


Change Property Prefix from "_" to "$" so that angular built-in functions ignore them

Angular's built in functions like angular.copy() and angular.toJson() automatically ignore object properties that are prefixed with $.
This PR changes the names of "_uiSelectChoiceDisabled" and "_uiSelectChoiceLocked" to "$uiSelectChoiceDisabled" and "$uiSelectChoiceLocked" respectively to make use of this feature when using ui-select as a model for rest resources.

Just a note that this could be a breaking change.

I'd prefer another solution, because you also can use a string list in a repeat: #1661


can't change nor see orders in other language

hi, I am having an issue with changing orders from admin dashboard or can't see them in other language that I have added. In the lang folder, I copy and paster english version and changed it to other language. I have translated all to that language. Everything working fine except that I can't see nor change orders from dashboard. and having "500 error".

@Shayboniyshoh your error log ?

@Shayboniyshoh your error log ?

in the language other than Default English and Tai lang, When I click to any order from the notification list on the first picture above, I am having 500 Server Error as below picture.

Hi!
ErrorException
Trying to access array offset on value of type null
\app\Models\ShopProduct.php:252
foreach ($products as $key => $product) {
$arrProduct[$product->id] = $product->getFull()['name'] . ' (' . $product->sku . ')'; // here 252 line
}


Cannot truncate a table referenced in a foreign key constraint

CDbCommand n'a pas pu exécuter la commande SQL : SQLSTATE[42000]: Syntax error or access violation: 1701 Cannot truncate a table referenced in a foreign key constraint (unep28.craft_import_entries, CONSTRAINT craft_import_entries_versionId_fk FOREIGN KEY (versionId) REFERENCES unep28.craft_entryversions (id)). The SQL statement executed was: TRUNCATE TABLE craft_entryversions

Likewise. Same problem

Only way could resolve this was by using DELETE FROM craft_entryversions rather than TRUNCATE craft_entryversions - like @migswd this also seems to be a result of using the Import plugin at https://github.com/boboldehampsink/import
There does appear to be a DELETE cascade in the definition of the Records for the import plugin but not UPDATE so not sure if that is the cause of the problem

The plugin doesn’t truncate the entryversions table any longer, so this should be fixed.


BUILD-400: feature file for rhel entitlement using shared secret

Test scenario for rhel entitlement subscription using shared secret

/assign @gabemontero

/assign @jitendar-singh
for qe-approve label

/approve
/lgtm

/label px-approved

/label docs-approved
@rolfedh already has doc's cooking for this story under through my Jira items

/label qe-approved
this PR is from QE :-)


chore(github-template): update issue template

Coverage remained the same at 97.652% when pulling 2d6d45c0e934328cc24166fa58d749cecbe70155 on daern91-patch-1 into 4d66e87462b05115ea09fc7314aaa2684ca22db9 on master.


udc_train.py not working 1.1.0

cell = tf.nn.rnn_cell.LSTMCell(

AttributeError: module 'tensorflow.python.ops.nn' has no attribute 'rnn_cell'

#45 resolves this problem.


(PUP-7848) Fix problem with VAR pattern and longer segments

This is yet another fix of the same problem as earlier believed to be
fixed. When input such as $aaaaa::bbbbb::ccccc::UPPER was encountered
the regexp matcher for variable/name ended up taking an enormous amount
of time. The initial regexp triggered this problem on very short
sequences. The updated worked for short sequences, but not for longer
(also took a very long time to complete).
The regexp is now updated with a more complex negative lookahead of ''
as the problem is to prevent that a segment other than the last starts
with ''.
Tests are updated to have longer sequences, and also includes the
original reported name.

CLA signed by all contributors.