How can we move the new side panel to the right?

We use to be able to execute move panel right for moving the terminal panels to the right, however in the latest version of vscode (not sure where it started) that cmd has been deprecated, now we can only move the panel from the left side or docked on the bottom.
How can we move the panel to the right? im almost certain im doing something wrong
main content | terminal panels stacked vertically | explorer panels stacked vertically
the above UX is essential,

toggling the terminal/explorer does not cause the main content to jump around if the main content is flush left
on extra wide monitors you can effectively use the entire screen real estate

vscode error
Moving the panel with this command has been deprecated in favor of "Move Views From Panel To Side Panel" and "Move Views From Side Panel To Panel" for similar functionality.

pinging @sbatten (bot made an assignment which surprised me)

The new panel is limited to being placed opposite the side bar. I will leave this issue open to gather feedback.

@webdev03 Could you upvote? People deserve options.

See https://stackoverflow.com/a/70982514/836330 for a partial "workaround" in the meantime.

As noted in #142075, these arbitrary changes are baffling in that they remove functionality we have been used to for years without solving any issue faced by users. It's unclear who decided on the changes and why, it looks like changing it for the sake of it. In more details

It is longer possible to have both the terminal and the sidebar to the right of the editor. Why? What problem is removing existing functionality supposed to solve?
When the terminal is in vertical view, it is no longer possible to make it full screen. Again, whose decision, and what problem were they trying to solve?
It is possible to move the "views" out of the "panel". Then CTRL-J will toggle the visibility of an empty  "panel". What's the point of that? Who needs to view an empty panel?
Conversely, there if is no shortcut to toggle the side panel visibility. Don't you collect metrics on how we use the editor? Hiding the terminal, editing code, showing the terminal again, sometimes maximised, sometimes not, it's what we do. All. Day. These changes completely destroy that. And to what benefit?
The abstractions are hard to understand and explain to non initiated. The wording in the menu "Move views to panels" is too crypting. "Panels"? "Views"? And "Sidebar" and "Side Panel" are too similar. As a user, why should I learn your jargon, and why should I care? The "panel" is an abstraction used by VSC developers. We users don't care about your implementation details, we care about concrete elements like the "Terminal". As you probably know, the number 1 rule in UX is "don't make me think".
The menu entry "Terminal" in the menubar has always been associated with the terminal in the panel, now it opens a completely separate terminal in one of the document windows. Why? Why have two separate things doing the same thing? Why have the menu control only the one and not the other? You do understand how chaotic it all gets when you have terminals in the side panels, and terminals in the editor window, and you are trying to remember what is in which window and which shortcut makes what panel appear... AAARGGH

The whole design decision is a complete train wreck. I urge you to reconsider. Thanks.

Conversely, there is no shortcut to toggle the side panel visibility.

@gotofritz on this particular point I assume you know you can assign whatever shortcut suits you:

The menu entry "Terminal" in the menubar has always been associated with the terminal in the panel, now it opens a completely separate terminal in one of the document windows.

For me this only happens after I set "terminal.integrated.defaultLocation": "editor"
This capability arrived last year (see https://code.visualstudio.com/updates/v1_58#_terminals-in-the-editor-area).

Conversely, there is no shortcut to toggle the side panel visibility.

@gotofritz on this particular point I assume you know you can assign whatever shortcut suits you:

Yes of course. I wanted to flag that changing an existing shortcut to toggle a (potentially) empty panel, while the expected functionality is left to individual users to wire up manually in the preferences, is not ideal IMHO

The menu entry "Terminal" in the menubar has always been associated with the terminal in the panel, now it opens a completely separate terminal in one of the document windows.

For me this only happens after I set "terminal.integrated.defaultLocation": "editor"
This capability arrived last year (see https://code.visualstudio.com/updates/v1_58#_terminals-in-the-editor-area).

You are right, thanks for the tip... there are so many obscure terminal preferences settings that I may well have changed that manually in my desperate quest to bring back the old functionality

See https://stackoverflow.com/a/70982514/836330 for a partial "workaround" in the meantime.

Putting terminals in a dedicated editor group on one side could be improved by addressing this issue:
#16927 - Allow a maximized editor group to use the full width rather than leaving 220px per group for each of the other editor groups. Also make View: Toggle Editor Group Sizes and friends remember the original group splitbar position when maximizing a group, reinstating that when toggling back from maximized. Currently it resets to even distribution, in the same way double-clicking on the splitbar does.

@sbatten as I've stated elsewhere this is not a missing feature. It is a broken feature thus a breaking change in 1.64.0!

@webdev03 Could you upvote? People deserve options.

Upvoted, although this shouldn't be up for voting. This whole thing should be rolled back.

This is an absolute joke, how is it possible to make such a regression in your softwares functionality! This feature has been working for years.

Apparently no-one who uses that functionality does so with Insiders. Or if they do, I haven't seen an issue raised about it ahead of 1.64 shipping as Stable yesterday.
Workaround for the moment is to revert to 1.63. Installation links are at https://code.visualstudio.com/updates/v1_63 and you may also want to turn off update checks.
I am confident that the team (of which I am not a member) will be taking this feedback seriously.

I'd like to add some general and specific thoughts here.
General thoughts
In general, having an additional panel might be useful for some users. Adding such a new panel, however, should not break anyone's workflow who does NOT need another panel. In an ideal case, users who don't need it should not even recognize that it has been introduced. In a semi-ideal case, they should at least be able to re-configure their previous workflow in the new environment. Both cases are not true for the introcution of the side panel, which makes this a breaking change and should be announced accordingly, in my opinion.
Missed opportunities
I assume that the developers didn't put enough effort into evaluating existing workflows and maybe didn't even notice the impacts of this change. It could have easily been designed non-breaking, e.g. as follows:

Rename the existing "Panel" to "Primary Panel", keeping all functionality and keybindings as they are, just a change of wording.
Add a new general "Secondary Panel" with the same functionality as the existing panel.
Duplicate all existing panel-commands, so that there is a version for the primary and one for the secondary panel.
Make the secondary panel be able to be placed at any location, just like the primary panel (left, right, top, bottom).

I don't see why the new side panel has been designed so different from the already existing panel. If I needed another panel, why force a specific layout? Who says I couldn't need two side panels? One at the left and one at the right? Or two bottom panels?
However, now that the new side panel has been introduced, it might be too late to design it this way, because that would make it another breaking change. I still think that this would be the most flexible, least surprising way, though.
The workaround
I don't think that the proposed "workaround" by putting the terminal into an editor group on the right side can replace previous workflows. The missing possibility to maximize the terminal has already been noted here. However, there are more limitations:

The terminal cannot be hidden. In order to hide it, one would have to close the editor group and open a new terminal, which is not the same.
There is no command to open another terminal in the same editor group. When having the terminal in the panel, this is possible using the Terminal: Create Terminal command.

Running Terminal: Create Terminal while having a terminal open in an editor group, the new terminal is opened in the (side) panel.
Running Terminal: Create New Terminal in Editor Area opens the terminal in the left-most editor-group, which is not the right one.
Running Terminal: Create New Terminal in Editor Area to the Side opens the terminal in a new editor group, having the terminal side by side.

Splitting the terminal vertically does not work anymore. In the panel this can be done using the command Terminal: Split Terminal. When having a terminal open in an editor group, this creates a terminal in a new editor group on the right side.
The terminal cannot be resized using hotkeys. In the panel this is possible using the Terminal: Resize Terminal [Up/Left/Right/Down] commands. (As a side note, these commands do not work with the new side panel as well, which is already tracked in #142176).

Proposed steps
Taking into account all the above, I see two options in order to make previous workflows possible again:

The clean solution

Create a fix release (fast!) with the new side panel removed, restoring all previous functionality.
Take the time to re-implement the side panel in the form of a secondary panel like proposed above under "Missed opportunities".

The fix solution

Do not tie the position of the vertical panel to the position of the side bar. Make it configurable independently, so that it can be on the left or on the right.
Add a command View: Toggle Maximized Side Panel analogous to View: Toggle Maximized Panel.
Make the Terminal: Resize Terminal [Up/Left/Right/Down] commands work with the side panel again (see #142176, as already mentioned).

The bottom line
Of course the fix solution would be the easier one, but in my opinion it is far less sustainable as it bears the risk of future insonsistencies. From a developer's perspective, having two differently designed UI objects providing essentially the same functionality just leads to a higher maintenance effort due to more corner cases.

Apparently no-one who uses that functionality does so with Insiders. Or if they do, I haven't seen an issue raised about it ahead of 1.64 shipping as Stable yesterday.

I don't think that this is a valid criteria for introducing breaking changes. This is similar to the reasoning that was in The Hitchhiker's Guide to the Galaxy:

Oh, you could comment on this issue it was on the Galactic Bulletin Board. (of course it didn't matter that humanity didn't know about the existence of the bulletin board nor had the tools to travel interstellar travel.

To give you a very specific example, this is what I can't do with 1.64.0:

Note that #141569 is very closely related to this issue, in fact, that bug was introduced with the same change. If you vote for this please also vote for that.

Workaround for the moment is to revert to 1.63. Installation links are at https://code.visualstudio.com/updates/v1_63 and you may also want to turn off update checks.
Reverting to 1.63.2 worked like a charm :) but where do I turn off automatic updates?

I am confident that the team (of which I am not a member) will be taking this feedback seriously.
Me too! :D looking forward to the next smooth release (most of them have been. Really)!

Stay positive! Work together!

the decision to have the "side panel" and "side bar" (these names.. 🥴) limited to being opposite each other is, to put it mildly, confusing.  my workflow has pivoted for years around vertically oriented (Side bar | Terminal | Editors ) and frequent toggling of the first two / maximizing terminal.

I'm sitting here writing code (workflow = Side bar | Terminal | Editors same workflow I've used for years) and notice that I have an update available.  I need a break so I start update, go get coffee, come back and nearly have a heart attack.  I learned something new about myself today though - when that happened my heart literally started racing and I got short of breath - I didn't realize how important my layout was to me (I just never thought about it).
There seems to be no way to go back to Side bar | Terminal | Editors unless I revert to 1.63.  That's a pretty crummy thing to do to someone.

I have mentioned this on https://github.com/microsoft/vscode/issues/132893 comment https://github.com/microsoft/vscode/issues/132893#event-5934002677 back in December.
There I asked if we can move the new Side Bar at the Left right next to the Explorer Side Bar and that it would be great for ultra wide monitors, and I only got a single response.

I didn't expect my proposal to be a thing just a thought, but frankly, I never expected a decision like this to get rid of the Panel "Move to the Left" as a column as it was before.
It was working and it's now broken. Please fix it by either reverting the Panel "Move to Left/Right" as a column option, or by making the new Side Bar be able to stick with the Side Panel at either side right or left.

[...]. I'm going to have to settle for the editor left | terminal right so the side-bar is on the left.

We don't have to settle. If they don't fix this we can simply fork the codebase and use that.

A note for those using WSL that're downgrading to the previous version:
You'll also need to manually downgrade your "Remote - WSL" extension from v0.64.2 to v0.63.13 (or just reinstall)!

If you use snaps, you can revert to revision 85 (version 1.63.2):
sudo snap revert code --revision 85

It is a shame that people have to revert and no one from the team (apart from a bot) is addressing this breaking change.

@sbatten will you address any of our concerns apart from wrongly assigning the feature-request tag?

Apparently no-one who uses that functionality does so with Insiders.

Apparently, no-one at Microsoft cares about introducing breaking changes. Is there anybody who works on VS Code who is willing to address this issue?

This is infuriating. Thank you for the tip on rolling back to solve the issue now and I can get my work done. Going to look into other editor options for the future.

I've had my terminal on the right for years. This makes logical sense to me because all the languages I know are read left to right, I write my code on the left and I see the result of it in the terminal on the right.
I have also had my sidebar on the right for years because I work with it hidden until I need it, and when I toggle it, it only takes space from the terminal, and toggling the sidebar does not move one character of code on my screen, it only moves terminal output when I toggle it.
Now you broke all that and you are considering the fix a "feature request" on your backlog 😞

I've had my terminal on the right for years. This makes logical sense to me because all the languages I know are read left to right, I write my code on the left and I see the result of it in the terminal on the right.
I have also had my sidebar on the right for years because I work with it hidden until I need it, and when I toggle it, it only takes space from the terminal, and toggling the sidebar does not move one character of code on my screen, it only moves terminal output when I toggle it.

That's exactly how I'm using it as well, for exactly the same reasons.

Thanks everyone for being passionate users of VS Code and sharing your feedback. There is lots of goodness in the comments above and I hear you. When making this change, I reviewed the affected population, but I underestimated the impact on your workflows, and I am sorry about that. So, I will be pushing a fix which is simply to bring back the ability to move the, as some have called it, primary panel. The plan for this fix is to release it into the insiders build tomorrow and the recovery build for stable later this week. Going forward, we will continue to improve the new side panel while playing nicely with the primary panel in different locations. Future changes will always be in insiders first, and we hope you continue to share your ideas with us.

It took a lot of shrieking and complaining, but thanks for eventually listening to the users, @sbatten

Testing this in Insiders today.  Put the Side Bar on the right and use the command View: Move Panel Right.  In one workspace with the setting Workbench > Panel: Default Location : right it put the Panel to the right of the Side Bar (so far right) but triggering the command fixed that.   Editor | Terminal (Panel) | Side Bar.  And working if put on the left too.

I usually works on 2 screens.
Left Screen:

Explorer(git, etc)
Terminal

Right Screen:

Editor

So Terminal should be between Explorer and Editor
I'm here to upvote to consider to improve recent change.
Could be possible to move that SIDE panel where I want?
Semantic talking: SIDE is a position. I will refer to it without a positional word.
Thanks for the hard work.

Fix landed in release/1.64

@hediet can you give a perspective when the new version will be avaialable ?  I keep seeing 1.64.1  as the lastest version.

@fdiasr see #142605. My guess is we'll have it by next week.

@heartacker That isn't possible.  The Side Bar and Side Panel are always on opposite sides.  You would need to file another issue for that.

I guess I'm switching to Atom now. Thanks for breaking your whole editor.

What the fluff, man. They just told us that it gets fixed in the next patch.

I just received v1.64.2 which has this fix.

Unfortunately this fix only allows to move the bottom panel to the right, but I would also enjoy to move the new side panel to the same side like the explorer.

It simply broke my keybinds and the most used workflow in the middle of last 3 days of release.

@h3d0 maybe not a good time to have updated VS Code, particularly if you haven't also been using Insiders alongside Stable.

@h3d0 I can see how this caused some confusion in the first place. Please take a look at #26777 to see why this was added, so things start to make sense to you hopefully. Overall it was a good change and I hope you can see it the same way.
The new side-panel is purely optional and you are able to continue to use VSCode like you did before, due to some reverting changes of 1.62.2 as you just figured out. The new side panel was never meant to be a replacement for your bottom panel that you've put to the right previously.

I just wanted to share my expression and frustration of how bad the whole idea was. Have being using VSCdoe for 7+ years in my 12+ years developing experience. And this single change has been one of the most annoying in my whole IDE experience.

I totally agree with all your points, especially this one. I sat down one day to work on my project just to find that my workflow is totally broken. I've used dozens of editors throughout the years (Eclipse, Netbeans, Emacs, Idea, Vim, Notepad++, etc) and for a while I thought that VS Code was in the sweet spot. I no longer think that as none of those tools had a breaking change like that.
The dream is dead. And the worst part is not that when I start this I can expect this to happen but how it was handled. No one from the team acknowledged that this was a mistake, no one apologized and no one came here and said sorry guys, we messed up, not gonna happen again.
I thought that Microsoft had very high standards, but apparently, they don't.

No one from the team acknowledged that this was a mistake, no one apologized and no one came here and said sorry guys, we messed up, not gonna happen again.

Well, that's not true. @sbatten did that, and he provided a fix for the issue.
And while I can understand any anger about this and Microsoft in general (I was annoyed by the change as well): let's not forget that the developers are still humans. Repeatedly posting how annoyed you are probably won't increase anyone's motivation to address your thoughts.

No one from the team acknowledged that this was a mistake, no one apologized and no one came here and said sorry guys, we messed up, not gonna happen again.

That is simply not true: https://github.com/microsoft/vscode/issues/141349#issuecomment-1033046397

@adam-arold that's not fair. I think their response and actions were quite fast and everything is working as it was before now. And they actually did apologize to the users for this. To me, it looks like you have some generalized frustration towards Microsoft and their products. I actually thank every VSCode developer and contributor because they all made this amazing editor/IDE. And as stated above, we are humans and mistakes can happen and as long those mistakes get addressed and fixed it's fine; this is not a paid product, it's an open source project regardless if Microsoft may be having some of their developers to work on it.
Thank you @sbatten for working on this and fixing it.

Oh come on guys, it's true that @sbatten didn't cover himself in glory early on, but he learnt from his mistakes and the issue is now fixed (thanks!). Do we really need to keep going on about it? Maybe it's time to lock the thread....

@gotofritz agree.
And let's look forward:

https://github.com/microsoft/vscode/issues/142742

https://github.com/microsoft/vscode/issues/142832

To me, it looks like you have some generalized frustration towards Microsoft and their products.

You're right, this might be the case. I stand corrected.

I complained on here as loud as I felt appropriate. After the fix came in I just wanted to come back and say thank you, and now I see people still piling on.
Software lesson: After convincing the devs that it's a bug and they need to fix it RIGHT NOW, and then they fix it, you look like you don't understand software when you then steer the conversation toward the feature that caused the bug. That feature is a separate conversation, that you probably don't understand if you are still complaining in this thread.
Life lesson: When a human makes a mistake and (after some dialogue) apologizes and fixes their mistake, it is insensitive, emotionally-tone-deaf, and probably inhumane to keep going on about what a bad idea it was.

Life lesson: When a human makes a mistake and (after some dialogue) apologizes and fixes their mistake, it is insensitive, emotionally-tone-deaf, and probably inhumane to keep going on about what a bad idea it was.

Or maybe the person in question has autism and you haven't considered that as an alternative to being insensitive, emotionally tone-deaf and inhumane.

How exactly is it fixed?
I still can not get the terminal to the left side like I used to have it,
it insists on opening in the side panel on the right.
I thought I did manage somehow but then it just went back.

How exactly is it fixed? I still can not get the terminal to the left side like I used to have it for the life of me. It insists on opening in the side panel on the right. There are some 80 settings to do with the terminal and not one of them will do this simple thing.
P.S. Please do not tell me off for being insensitive for daring to complain about it.

I don't believe it is a setting. I would like it to be so I can default open the terminal in the same place across all environments. And you would be forgiven for spending your efforts looking in the settings because so many other things about the UI can be changed in settings.
Right-click toward the top of the terminal next to the tabs PROBLEMS, OUTPUT, etc, then you can choose Move Panel Right or Move Panel Left. If you don't see those options try Move Views to Panel and then those options should appear.

Thanks. I was stuck in catch 22. Those options were not showing because I did not activate them with "move views from side panel to panel". On the other hand, once I finally discovered this command, I now no longer need them.


fix: issue with navigation redirecting to /undefined/Task_1 when remo…

…ving pageKey and taskId from url
Description

Related Issue(s)

closes #{issue number}

Verification/QA

Manual functionality testing

[x] I have tested these changes manually
[ ] Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
[ ] No testing done/necessary

Automated tests

[ ] Unit test(s) have been added/updated
[x] Cypress E2E test(s) have been added/updated
[ ] No automatic tests are needed here (no functional changes/additions)
[ ] I want someone to help me make some tests

UU/WCAG (follow these guidelines until we have our own)

[ ] I have tested with a screen reader/keyboard navigation/automated wcag validator
[x] No testing done/necessary (no DOM/visual changes)
[ ] I want someone to help me perform accessibility testing

User documentation @ altinn-studio-docs

[ ] Has been added/updated

[x] No functionality has been changed/added, so no documentation is needed
[ ] I will do that later/have created an issue

Support in Altinn Studio

[ ] Issue(s) created for support in Studio

[x] This change/feature does not require any changes to Altinn Studio

Sprint board

[x] The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
[ ] I don't have permissions to do that, please help me out

Labels

[x] I have added a kind/* label to this PR for proper release notes grouping
[ ] I don't have permissions to add labels, please help me out

There seems to be no snapshots on the main branch in Percy for some reason 🤔

Reran the tests and everything was suddendly fine :shrug:


Fix typos in README

Found 2 type errors (lines 28  and 37) when copy-pasting animation examples. I wish READMEs were type-checked too :-)
The rest are just automatic formatting changes (removed spaces at the end of lines) and change case msgs of to more customary case msg of.

Looks like (just) a couple of the typos were fixed, causing the merge conflict: https://github.com/mdgriffith/elm-style-animation/commit/826238afd0c4ba8dc7070eab5a22cffab3351f51

Hey!  I just wanted to say I appreciate this type of pull request.  I had some of these typos fixed, I just hadn't pushed in a while.
I'm going to close this, but again, I appreciate you doing this:)


net/wireguard: Late Spring Cleaning

Those are generally minor changes:

Add interface name (wgX) as a column
Corrected/improved/explained a few help entries better and renamed them. Also using "Peers" instead of "Endpoints", as WireGuard also refers to "Peers" in their configuration and documentation.
Update configuration and handshakes once page loaded, instead waiting for the 5 secs refresh interval to start.

Thx for your efforts here but I'm not sure of changing all labels is a good idea in a minor release.
I know WireGuard calls it Interface and Peer but there are tons of guides and documentation out there referencing to instance and endpoint. Maybe this would be something for 23.1 and coordinating update to documentation and content creators updateing their stuff.

I just revert and changed the name back on the user-facing side. Fine this way?

As I don't have access to git-capable environment now, I've used the GitHub functionality to commit the changes - that's really handy. Thanks for the review!

@fichtner / @mimugmail

Thx for your efforts here but I'm not sure of changing all labels is a good idea in a minor release.

As 23.x seems to be around the corner, might it be a good time to finally change the wording as per WGs definition?

Shouldn’t be that hard. No screenshots fortunately in the docs I have worked on (road warrior and selective routing). :) Just need the list of proposed changes and the docs can be modified (at least, I can update the two I prepared, I won’t be able to do them all).

FYI, Created PR #3271 for this @fichtner @Greelan


Fixed recipes for 1.21.2+

Changed recipes according to work in 1.21.2+
Below is an exemple for a shaped craft but it's the same for all kinds of crafts, you just need to replace key by the appropriate keyword (i.e. ingredients for shapeless crafts).
Before
"key" : {
    "#": {
        "item": "minecraft:stick"
    },
    "P": [
        {
            "tag": "minecraft:planks"
        }
    ]
}

Now
"key" : {
    "#": "minecraft:stick",
    "P": "#minecraft:planks"
}

Thank you very much. I've been busy for so long that I didn't notice the changes


Is there support for Shell.Resources

Hello,
I had a quick question regarding Shell.Resources. It doesn't look the this is supported yet. Is there a work around for this? I'm trying to style my flyout menu and all my attempts have failed.

Hi @bryanp-ramosoil you are correct it isn't supported at this time. Do you know if it's possible to style the flyout in other ways, such as with regular properties or with CSS? Or is Resources the only way?

I've been trying to get it to work with style sheets but it's not working. The way Shell does it is within the ContentPage.Resources of the XAML.
<ContentPage.Resources>

</ContentPage.Resources>
I've also tried
using (var reader = new StringReader("^contentpage { background-color: lightgray; }"))
{
this.Resources.Add(StyleSheet.FromReader(reader));
}
Both attempts have failed.

Here's an example of how to use Stylesheet: https://github.com/xamarin/MobileBlazorBindings/blob/master/samples/MobileBlazorBindingsWeather/MobileBlazorBindingsWeather/WeatherApp.razor#L4

Perfect thanks. I don't know if this is an issue but it only seems to work if the css file is the root of the application. I've attempted to put the file in an Assets folder then reference it using it's name space and it fails. I've used a decompiler to verify the resource was there and it was.
Fails
Example: MyProject.Assets.styles.css
Folder: root/Assets/styles.css
Works
Example: styles.css
Folder: root/styles.css
It's not a deal breaker but I thought I would pass the information along.
Thank you for creating this project. This is perfect for us web developers who now need to start building mobile apps.

Ah very interesting, I've logged https://github.com/xamarin/MobileBlazorBindings/issues/103 to track investigating that.
Thanks for the details and kind words!


Add community meetings to README

What type of PR is this?
/kind documentation
What this PR does / why we need it:
Updates the README to add info on community meetings
Which issue(s) this PR fixes:
Fixes #151

lgtm

LGTM for now but let's make sure we change the Zoom link after tomorrow once it's stable.

@fabianbaier ya you're right, I missed the message earlier that we had a meeting-specific zoom link. :+1: lgtm


Teach goreleaser to use CHANGELOG.md instead of commit dump

As per the tagline  👀  👀  👀

Fixed in 0a470a5f407e43e8b3aa08bf352a7791c4e4e3ea and 90b2ada7ab0f3a7682bf39a1189526e65de25011


chore(deps): update terraform terraform-ibm-modules/landing-zone/ibm to v5.24.6

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/landing-zone/ibm (source)
module
patch
5.24.5 -> 5.24.6

Release Notes

terraform-ibm-modules/terraform-ibm-landing-zone (terraform-ibm-modules/landing-zone/ibm)
v5.24.6
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/landing-zone-vpc/ibm to v7.18.3 (#821) (4feb90e)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This issue has been resolved in version 5.3.0 :tada:
The release is available on:

GitHub release
v5.3.0

Your semantic-release bot :package::rocket:


Define milestones for steering committee

official timeline is in https://docs.google.com/spreadsheets/d/17SNeMHY3gpJe3AbcDKnXgSPy3yv8y_UnDgc9cUcJiyg/edit#gid=954079122  .

Looks like they don't use this repo, so closing for now.


update to the latest Version

Update to the latest commit of YDJSY, need to re-generate the docker image though.

docker pull gongzhang/ydkjs-epub:20200706


"Fălcoiu", "Cioroiașu", "Cioroiu" are listed in the drop-down menu

Description:
When user writes "Fălcoiu", "Cioroiașu" and "Cioroiu" the locations appear in the drop-down menu next to the comune and the county which is a part according to the law
Precondition:
The website is up an running.

Step 2
Press "x" button.
Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Cioroiașu"
Expected results
The location appears in the drop-down menu as "Sat Cioroiașu, OLT (Fălcoiu)"

Step 4
Press "x" button.
Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Cioroiu"
Expected results
The location appears in the drop-down menu as "Sat Cioroiu, OLT (Fălcoiu)"


The desktop application could not fetch the VPN connection

The problem about the VPN connection on Flutter Desktop Application
Hi there, I and my team wrote a small application with flutter. It works very well and quickly in mobile platforms. Recently, we would like to convert the mobile application into the Desktop version. By following the documents and resources here. The codes could run successfully. However, before using the application, we should check the VPN connection since the database is private and secured. The mobile application works well while the desktop platform will raise the exception

flutter: SocketException: Connection failed (OS Error: Operation not permitted, errno = 1), address = my.irb.ufl.edu, port = 443

And also, if we bypassed the checking process and try to connect with the server directly, it will also raise the SocketException.
The codes are shown below:

We just easily check the connection with the Http Package.
Other Information:

OS platform :  macOS
version : flutter upgraded and all of the packages are updated.
We only replaced the lib folder and pubspec.yaml to make sure the configuration is correct.
We used the Cisco Anyconnect Software to build the VPN connection.

We thought it might be the problem of the package that could not well-working in desktop application or there should be a bridge between the VPN connection and flutter desktop application.
Thanks for your time and if you have any suggestions please share with us.

Duplicate of https://github.com/flutter/flutter/issues/47606

@stuartmorgan  Hi, thanks for your information and it works now!
For others' information :100:
Add
<key>com.apple.security.network.client</key>
<true/>
to file DebugProfile.entitlements under directory macos/Runner/

If you only added it to that file, your release builds will have the same problem. Prior should follow the instructions linked from the other issue, which provide more complete information.

Yep I also add it to the release file. Thanks for your information and have a nice day! I will change my answer as well
Ziyuan Guan
Data Analyst From PrismaP Team
College of Medicine, University of Florida

发件人: stuartmorgan<EMAIL_ADDRESS>发送时间: Monday, December 23, 2019 11:52:56 AM
收件人: flutter/flutter<EMAIL_ADDRESS>抄送: Guan,Ziyuan<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>主题: Re: [flutter/flutter] The desktop application could not fetch the VPN connection (#47680)
[External Email]
If you only added it to that file, your release builds will have the same problem. Prior should follow the instructions linked from the other issue, which provide more complete information.
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_flutter_flutter_issues_47680-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAHPYPQNFG3M62O5OJ24GL2LQ2DUGRA5CNFSM4J6VTTC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHRP7JA-23issuecomment-2D568524708&d=DwMCaQ&c=sJ6xIWYx-zLMB3EPkvcnVg&r=USuxa2w-4iFZVU4XK5c-GRt5sD--LSrKsXkQuvtDnWU&m=9KDuyud3NYeyCyz5jpgXynqSz8iV0OSfp1DNDUOf2-c&s=s60FclEZwPmYeulCoUmaWn3_nV9W8SQUfA5tFD0EYTA&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AHPYPQN5YRXARQT6RKXE23DQ2DUGRANCNFSM4J6VTTCQ&d=DwMCaQ&c=sJ6xIWYx-zLMB3EPkvcnVg&r=USuxa2w-4iFZVU4XK5c-GRt5sD--LSrKsXkQuvtDnWU&m=9KDuyud3NYeyCyz5jpgXynqSz8iV0OSfp1DNDUOf2-c&s=VZPlpTyFft8fsHeCnxxnwOONg4HolQPHOj-gPHm0UAA&e=.


Use whitelists instead of blacklists for some ifdefs

This is the pattern used upstream and allows building on platforms such as OpenBSD and DragonFly, which don't get caught by the current blacklist and thus fail on unsupported features.

Bump @vtjnash

Bump @vtjnash

I'm sure it's fine. Could you make the same change to the upstream PR?

This actually gets our branch closer to what the current upstream is; there isn't really anything to change upstream.

https://github.com/libuv/libuv/pull/1654#discussion_r179312418?

Oh right 🙃

I can't push to the branch since it's on your fork of libuv. I can post a proposed diff against your branch though.

Needs a rebase too. If you put up the branch somewhere, I can push it to my PR.

https://github.com/vtjnash/libuv/pull/1

The current merge conflicts in your upstream PR should be quite simple to fix. I would have done them in my PR to your fork but then it wouldn't be mergeable because the histories differ. After the rebase you'll want to make sure the logic there isn't duplicated with https://github.com/libuv/libuv/commit/20cc969e5db3467bddaa35f48ba051a7ae3b3653#diff-993e2d1f75ebf418adfbe81df8050a95R48.

If you add me as a collaborator on your fork of libuv I can do the rebase for you.

I think I folded this into the current active branch, let me know if my memory is wrong.

Nope, these changes don't seem to be present on the default branch.

Not the default branch (I don't have permission to fix that), but I confirmed it's changed in julia-uv2-1.24.0

I mean our default branch, julia-uv2. I guess I don't understand how we're doing branch management for this repo.


etcdserver: fix wrong rev in header when nothing is actually got executed

Fix https://github.com/coreos/etcd/issues/6146

lgtm.


merge from original

Hi! I'm not really sure what this PR is adding to raml2html. Some VISION stuff? Sounds like a proprietary property?


Support for "equation" environment

It seems that multi-line auto rendering is not possible for the moment.
For example:
\begin{equation}
  x = a_0 + \cfrac{1}{a_1
          + \cfrac{1}{a_2
          + \cfrac{1}{a_3 + \cfrac{1}{a_4} } } }
\end{equation}

Here is the exception:
KaTeX auto-render: Failed to parse `
    \begin{equation}
    x = a_0 + \cfrac{1}{a_1
            + \cfrac{1}{a_2
            + \cfrac{1}{a_3 + \cfrac{1}{a_4} } } }
  \end{equation}\frac{1}{2}
    ` with  Error: KaTeX parse error: No such environment: equation at position 21: begin{equation}̲

Any ideas ?

The equation env has not been implemented yet...
But the aligned* is implemented according to the wiki page: https://github.com/Khan/KaTeX/wiki/Function-Support-in-KaTeX
It does not work neither.
\begin{aligned}
a&=b&c&=d\\
e&=f
\end{aligned}

It gives No such environment: aligned* exception

It seems that aligned is not recognized by the environment.
https://github.com/Khan/KaTeX/blob/master/src/Parser.js#L428

aligned is supported on master but not in the most recent release.  I can see how the wiki page is a little confusing.  The * after aligned is supposed indicate that there is a note at the bottom of the wiki page that states *Committed to master but not part of the most current release.

(I replaced * with † to make things less confusing maybe)

Thank you for the clarification. =)

@invkrh I also hope for the implementation of \begin {equation} for Katex. It would be fantastic.

It is possible to add very basic support for \begin{equation} ... \end{equation} by specifying a custom delimiter in auto-render. For example:
renderMathInElement(document.body, {
  delimiters: [
    {left: "$$", right: "$$", display: true},
    {left: "\\(", right: "\\)", display: false},
    {left: "\\[", right: "\\]", display: true},
    {left: "\\begin{equation}", right: "\\end{equation}", display: true}
  ]
});

See https://codepen.io/edemaine/pen/EpNamj for a demo.
However, equation numbering isn't supported yet; #350 tracks that.  Note that manual numbering via \tag is possible, though.

@edemaine And what about a dollar sign?

@edigleyalexandre You can add support for $ by adding another delimiter to the list.

@edigleyalexandre It matters where in the list things are placed. Be sure that "$" comes after "$$", as in:
renderMathInElement(document.body, {
  delimiters: [
    {left: "$$", right: "$$", display: true},
    {left: "$", right: "$", display: true},
    {left: "\\(", right: "\\)", display: false},
    {left: "\\[", right: "\\]", display: true},
    {left: "\\begin{equation}", right: "\\end{equation}", display: true}
  ]
});

I added as I said, but it does not render. Look here.

@edemaine Here's how to get with Mathjax. On here.

\begin {matrix} and \begin {cases} are supported on Katex. I tested the main page of the Katex website and rendered it, but the blog did not render. What happened? Page with \begin {cases} that did not render.

Well, you did omit a comma that should follow  {left: "\(", right: "\)", display: false}. I don't know if that by itself is enough to stop the script.

It worked. Forgive me for that.

This is still the problem. It is impossible to render equation-based environments such as
Environment `\begin{equation}...\end{equation}`
with auto-numbering:

\begin{equation}
h(z) = \sinh(z)
\end{equation}

---

Environment `\begin{equation}...(\#eq:label)\end{equation}`
with auto-numbering and label (for bookdown):

\begin{equation}
  f\left(k\right) = \binom{n}{k} p^k\left(1-p\right)^{n-k}
  (\#eq:binom)
\end{equation}

---

Environment `\begin{equation}...\label{label}\end{equation}`
with auto-numbering label for xaringan

\begin{equation}
  g\left(k\right) = \binom{n}{k} p^k\left(1-p\right)^{n-k}
\label{binom2}
\end{equation}

in several Markdown editors - see at least https://github.com/benweet/stackedit/issues/1424  and https://github.com/laurent22/joplin/issues/2212 .

omg. This is awesome!

Looks like it is not fixed, for example Joplin do not show \begin{equation}...\end{equation} blocks.

\begin{equation}...\end{equation} is so common in LaTex, why not consider to support this ?

Closed via PR#2369.

`Without equation, it is working as overflow: scroll
$Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)$
Without array it is working as expected (Breaking properly)
\begin{equation}
Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)
\end{equation}
With array and without equation (Not Breaking properly, overflow is scrolling)
$3Ta{n^{ - 1}}x$$=\left{\begin{array}{ccc}
Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)
\end{array}\right}$
With array and with equation it is not working as expected (Curly braces has problem) - THIS IS MY ISSUE
$3Ta{n^{ - 1}}x$$=\left{\begin{array}{ccc} \begin{equation}
Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right)Ta{n^{ - 1}}\left( {\cfrac{{3x - {x^3}}}{{1 - 3{x^2}}}} \right) \end{equation}
\end{array}\right}$
`
ISSUE: Why if I add an equation inside an array it's breaking?

@Varun-msd Soft line breaks occur after top-level relations and binary operators. If you wrap an equation environment or an array environment around some math, then the nested operators are no longer top-level.
Why was it programmed to work this way? Because KaTeX emulates TeX and that is the way TeX does soft line breaks. It is so specified in The TeXbook on page 173.

So @ronkok you say that we can't achieve the solution of my problem in Katex ? , my question is because it works in MathJax 2.0 but not in MathJax 3.0 (as they don't support line breaking till now)

The bug is not fully fixed. The following syntax is not rendered:
\begin{equation}
  g\left(k\right) = \binom{n}{k} p^k\left(1-p\right)^{n-k}
\label{binom2}
\end{equation}

See below:

Please: a - reopen, b - ask me to open new bug.

@N0rbert \label is different functionality, and already tracked in different issues, most recently #2798.

you can use align instead of flalifn https://katex.org/docs/supported.html#environments
\begin{align}
(a+b+c+..)^m&=\sum_{i}a^i(b+c+..)^{m-i} && \text{(nach No. 25)} \\
&=\sum_{i}a^i(\sum\limits_{j}b^j(c+..)^{m-i-j}) && \text{(nach No. 25)} \\
&=\sum_{i,j}a^ib^j(c+..)^{m-(i+j)} && \text{(nach No. 2)} \\
&=\sum_{i,j,k..}a^ib^jc^k+..)^{m-(i+j+k..)} \text{ wo, } i+j+k+..=m && \text{(nach No. 25)} \\
\end{align}


qDNAseq bin annotations

Description of feature
It might be worthwhile to integrate a flow to generate bin annotations for qDNAseq.
@nvnieuwk has already prepared a standalone workflow for this, but it might be a nice addition here.
https://github.com/CenterForMedicalGeneticsGhent/nf-cmgg-qdnaseq

Not 100% finished yet (still having some container issues), but yeah I can implement the flow of qDNAseq into this pipeline if it's wanted :)


ServiceCatalog floods brokers when provisioning is permanently not possible.

Hi all :)
This is a nutshell of our issue:
The flow of the ServiceInstance provisioning was changed after refactoring (https://github.com/kubernetes-incubator/service-catalog/pull/1886). Now the Service Catalog has infinite loop
start provisioning -> fail, requires orphan mitigation -> perform orphan mitigation
-> start provisioning -> …

it will do so until it finally succeeds.
Details
Scenario - Service Catalog version 0.1.3 - correct flow

The Service Catalog triggers provisioning of given ClusterServiceClass
We are responding with http code 202 (Accepted) and triggering asynchronous operation which fails because of some reason.
When Service Catalog calls last_operation endpoint we are returning http code 200 (OK) with body

{
  "state": "failed",
  "description": "Cannot provision instance. <reason>"
}

Service Catalog marks the ServiceInstance as failed, sets Deprovision Request as Required and does not perform any additional actions. When we call deprovision on such failed instance the Service Catalog sends deprovision request also to the broker.

Scenario - Service Catalog version 0.1.11 - broken flow

Steps 1-3 same as above.
Step 4: Service Catalog marks the ServiceInstance as failed, sets Deprovision Request as Not Required and does not perform any additional actions.

When we call deprovision on such failed instance the Service Catalog does not send deprovision request to the Service Broker, so you created a ticket to fix this https://github.com/kubernetes-incubator/service-catalog/issues/1879 but PR which should fix that https://github.com/kubernetes-incubator/service-catalog/pull/1886, caused something more. Now the Service Catalog in versions above the 0.1.11 has infinite loop
start provisioning -> fail, requires orphan mitigation -> perform orphan mitigation
-> start provisioning -> …

This loop "spams" our brokers because there are no delays and max retries. In some cases such approach breaks our flow.
We can also consider an example when someone has a Azure Service Broker and wants to provision a db service. Instance can failed e.g. because the quota in given namespace was exhausted. So repating describe action over and over does not make sense.
The question is, why are you performing the orphan mitigation if Service Broker responded with 200 (OK) status code?
In spec https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/spec.md#orphans, we can find that in such case you shouldn't do that.
Could you elaborate about your new approach for provisioning? Because I cannot find any documentation about it in the Service Catalog.
What's more in my opinion you should restore the previous behaviour (from version 0.1.3). When Service Broker respond with 200 status code on last_operation endpoint with body
{
  "state": "failed",
  "description": "Cannot provision instance. <reason>"
}

you should only mark this ServiceInstance as failed and stop pooling. Then when user sends deprovision request you should call the Service Broker. Thanks to that the given Service Broker will perform a deprovision action (same kind of garbage collector) for failed instance.
Thank you in advance

Also, to clarify the scope of the issue: by "when provisioning is permanently not possible" in the title it is implied that platform should either treat any async provisioning failure as a permanent one, or be able to determine whether a failure is temporary or permanent.
Unfortunately, with OSB API v2 it is impossible for the platform (Service Catalog) to know whether the failure is temporary or permanent. OSB broker just returns state: failed in the response to last_operation, there is no error categorization. This is definitely something we should address in v3 (or as a backward compatible optional field in v2), but currently we have to deal with what we have.
In 0.1.3 Service Catalog treated any failure as permanent. It was a general agreement that this was a flaw in the Service Catalog code that had been justified by our focus on beta release that only supported the "happy path" well. Since beta was released, we invested a lot of effort to improve coverage of "non-happy path", see issues filtered by non-happy-path label for example: https://github.com/kubernetes-incubator/service-catalog/issues?utf8=✓&q=label%3Anon-happy-path+
I hope that helps.
Please do report any bugs you might find.

@nilebox Thank you for you reply. It helps a lot!
Now we know that this behaviour is by design. Previous comment was based on version 0.1.12, but now I can see that v0.1.17 is the newest one, so we will validate the new flow one more time. If we find the same problems, we will look into the code and report issue with the details.
PS. Sorry for such late response but last week I was at conference and vacation.


python310Packages.xiaomi-ble: 0.11.0 -> 0.12.2

Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

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

1 package failed to build:

home-assistant-component-tests.xiaomi_ble

3 packages built:

home-assistant-component-tests.bthome
python310Packages.xiaomi-ble
python39Packages.xiaomi-ble


Wish: Check for throw in IO Monad

On page 150 of  Parallel and Concurrent Programming in Haskell by Simon Marlow is written
 It is always better to use throwIO rather than throw in the IO
 monad because throwIO guarantees strict ordering with respect to other
 IO operations, whereas throw does not.

Could hlint check for the usage of throw within the IO monad?
And even better could it be added to the default checks?

Unfortunately not - HLint has no idea whether the monad in question is IO or not, so thus no idea if throwIO would work. It's unfortunate, because I'm a big fan of this hint.

Unless of course you can think of a clever way...

In our case the signature was 'getCPOptsIO :: Maybe FilePath -> IO [Text]' so as a programmer I understood it was within the io monad. Your the expert so if you tell me hlint cannot draw the same conclusion I accept that as a fact.
A petty...

That would require finding the type signatures, matching arguments, and basically doing an approximate type inference pass in HLint. So far I've avoided that, because it's very hard to do right, impossible in the file-by-file module HLint operates. If I ever do extend HLint to do that, this will be a hint to add, but for now, unfortunately not possible.
I would however, suggest banning throw and having a throwImpure or similar so that "short" name people reach for is more likely to be correct.


Fix bug in "verbatim catalogNumber check" for DwC importer

I missed that the identifier value is stripped of its namespace prefix before the comparison with the cached catalogNumber is performed, so it never matched the cached value. Getting the original catalogNumber value with get_field_value is the correct way to do it, like I did with the verbatim tripCode check.
(Man, I should really write some unit tests for the occurrence importer...)

Codecov Report
Patch and project coverage have no change.

Comparison is base (69252c9) 85.79% compared to head (9342d51) 85.79%.

:exclamation: Current head 9342d51 differs from pull request most recent head 8172253. Consider uploading reports for the commit 8172253 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff              @@
##           development    #3500   +/-   ##
============================================
  Coverage        85.79%   85.79%
============================================
  Files             2005     2005
  Lines            72645    72644    -1
============================================
  Hits             62328    62328
+ Misses           10317    10316    -1

Files Changed
Coverage Δ

...pp/models/dataset_record/darwin_core/occurrence.rb
56.35% <0.00%> (+0.10%)
:arrow_up:

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


Is not grabbing any comments for any of my archives.

Im starting with the basic commands and all my csv files are 74bytes with just the post.  Cant get this to work.

If you're not downloading anything, then maybe pushshift is down or that data is unavailable. show your commands or try one of the examples.

I have the same problem with a whole subreddit. It seems to be a problem with pushshift and not with reddit-html-archiver. The example https://api.pushshift.io/reddit/submission/comment_ids/6uey5x given at https://github.com/pushshift/api gives a list of comments, but when I put a thread id of the subreddit I'm speaking about, there is never any comment in the answer.


What to do when homology arms don't match genome sequence?

This happens in the MYTK MoClo kit, where the sequence of the homology arms of 500bp does not exactly match that of the genome, having a few mistmaches. What to do in a case like this? Include Ns?

Causes something like this: https://github.com/manulera/ShareYourCloning_frontend/issues/241

To me, it would make sense to add the Ns (or any of the other IUPAC symbols. We could validate them later with sequencing results, like we would do for this issue.
Additionally, we could:

Add a feature named "unknown recombination site"
Label the construct as "unfinished" or "missing information" so the users pay attention


docker: backport transcational layer store fixes

This set of patches make sure that changes in the layer store are synced
to disk before updating the metadata of docker.
connects to docker/docker#25523
fixes resin-io/hq#274
Signed-off-by: Petros Angelatos<EMAIL_ADDRESS>

LGTM - but wait for build to finish first. Only to be merged when builds are green.

Eventually build succeeded: https://jenkins.dev.resin.io/view/Yocto/job/yocto-all/902/
Not sure why github won't pick it up

It also passed QEMU tests
On Tue, Sep 6, 2016 at 2:42 PM, Florin Sarbu<EMAIL_ADDRESS>wrote:

Eventually build succeeded: https://jenkins.dev.resin.io/
view/Yocto/job/yocto-all/902/
Not sure why github won't pick it up
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/resin-os/meta-resin/pull/277#issuecomment-244953603,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA5VnJqNLDr1oOOsukVUz00Iz0gKfgszks5qnW22gaJpZM4J1Nfy
.

--
Petros Angelatos
CTO & Founder, Resin.io
BA81 DC1C D900 9B24 2F88  6FDD 4404 DDEE 92BF 1079


post navigation floating issue on small screens

Hi Niklas,
the latest change has a bad effect on post navigation floating on small screens:
623840a

vs.
3edaa05

Best regards, Michi.

The main issue is here that the right-alignment only makes sense when the divs don't break and css seems to have no ability to set the alignment based on this condition, but I might be wrong here.
So I decided to let the divs always break on small screens and give them half width and alignment otherwise.
I hope this works for you, but I'm open for other solutions.

it could do the trick ;-) i'm not aware of other possible solutions...
thank you!


"Not a valid filter list" in ABP

When I click the magic links in README.md with AdBlock Plus installed, they autocreate invalid filters in ABP:

Hi!
In my opinion, one should not use AdBlock or AdBlock Plus. These projets are receiving money from advertisements companies to allow some ads.
Moreover, AdBlock doesn't support strict website blocking, and only blocks secondary resources. That's why this filter is not compatible with AdBlock.
I won't make this filter more compatible with Adblock. However cosmetic filters on search engine results might work with AdBlock, but I didn't checked.
You can install uBlock here : https://github.com/gorhill/uBlock and then use any filter from this projet.


Additional differential entropy estimators

@Datseris I have 4-5 additional differential EntropyEstimators, and some more ProbabilitiesEstimators as well, as part of my dev branch for CausalityTools. I'm on a tight deadline to finish all of this V2 stuff, so it would be nice to get these estimators in here right away.
Is it reasonable to just implement all of them in a large PR which is merged straight away, then we assess their code in detail when we do a complete codebase review ?
They are all documented with examples and tested experimentally for convergence to true values, so I don't think there should be much to review, except for code style.

I'm on a tight deadline to finish all of this V2 stuff, so it would be nice to get these estimators in here right away.

More estimators don't matter for v2. A stable API does. I would say to shift the focus from adding new stuff to polishing and checking everything here and making sure all tests are valid and all docs are valid, if the priority is to get v2 out.

Is it reasonable to just implement all of them in a large PR which is merged straight away, then we assess their code in detail when we do a complete codebase review ?

It is much better to do small focused PRs that add a single thing and therefore change at most 3 files: one for the thing, one for its docs, and one for its tests. These PRs are much easier to review in detail.

More estimators don't matter for v2. A stable API does. I would say to shift the focus from adding new stuff to polishing and checking everything here and making sure all tests are valid and all docs are valid, if the priority is to get v2 out.
It is much better to do small focused PRs that add a single thing and therefore change hopefully only 3 files: one for the thing, one for its docs, and one for its tests. These PRs are much easier to review in detail.

Ok sure, I'll just add them one by one then.

E.g., https://github.com/JuliaDynamics/Entropies.jl/pull/203 , which wasn't reviewd, changed 14 files. That's a lot for "one feature". The more files being changed, the harder and longer the review process will be. So I would definitely be against making more very ;arge PRs.


TabBarController stops working after dismissed

Hi,
I have a UITabBarController that goes to multiple navigation controllers. Once the TLPhotosPickerViewController is displayed and then dismissed, the tab controller doesn't load the contact when the selected index is changed. All works for presenting custom modals, but not when using this library. Code used to display the image picker below:
let viewController = TLPhotosPickerViewController()
        viewController.delegate = self
        viewController.didExceedMaximumNumberOfSelection = { [weak self] (picker) in
            (self?.navigationController as! MainNavigationViewController).showBanner(text: ApplicationText.OneProfilePicture, type: .error)
        }

        viewController.dismissCompletion = { [weak self] () in

            viewController.dismiss(animated: false, completion: nil)
            if viewController.selectedAssets.count > 0{
                let asset = viewController.selectedAssets.first?.phAsset
                let image = Utilities.getUIImage(asset: asset!)

                self?.uploadProfilePicture(image: image!)
            }
        }

        var configure = TLPhotosPickerConfigure()
        configure.numberOfColumn = 3
        configure.maxSelectedAssets = 1
        viewController.configure = configure

        self.present(viewController, animated: true, completion: nil)

Resolved - made it present over full screen by setting the modalPresentationStyle to OverFullScreen!


facebook-connect - Add support for return scopes

Adds a configuration option to facebook-connect provider to return the granted scopes back with the response data. This is useful when trying to determine if a user omitted any required scopes during the sign in process.
Defaults to off and is only added to the normalized response when configured.

@john-griffin this looks great- Can you add a test for it?

@mixonic good point, updated with a test.

:+1: Thanks!


Phylogibbs 1.2 python3.6.8

Add phylogibbs version 1.2 with python 3.6.9

@mkatsanto Can you please test whether it is working properly or not?


Lazy object instantiation via config file

Description & Motivation
As far as I can see, there is no way currently to do lazy instantiation.
Let say, we want to create an object of class path.to.B that we configure from the yaml file. However, its creation might depend on a property of another object, that we know only during runtime. So it would be great if, based on the config file, we get a constructor for an object of class path.to.B , where all parameters are already set from the config file. In the example below, the constructor would already set u=1, v=2, e.g. using functools.partial. So instead of getting the instantiated object I get a preconfigured constructor.
See the example below
Module:
class Model(pl.LightningModule):

     def __init__(self,model):
        super().__init__()
        obj_A = model.A
        obj_B_constructor = model.B
        obj_B = obj_B_constructor(extern_param=obj_A.param) # should correspond to path.to.B_class(u=1, v=2, extern_param=obj_A)

config file:
model:
    A:
      class_path: path.to.A_class
      init_args:
           a: 1
           b: 2
    B:
     class_path: path.to.B_class
     lazy_init: True
     init_args:
         u: 1
         v: 2

Pitch
By setting an additional key in the config file, we are not getting the instantiate object, but the constructor for the object, with all parameters already set.
Alternatives
No response
Additional context
No response
cc @borda @carmocca @mauvilsa

@rob-hen I assume you are talking about LightningCLI here? There is a lazy_instance method, explained here at the end of the section: https://lightning.ai/docs/pytorch/stable/cli/lightning_cli_expert.html#class-type-defaults
This is the closest to lazy instantiation we have, that I know of.

@awaelchli Yes, I am using the LightningCLI e.g. python train.py --config config.yaml. I would like to define lazy init with the config file, with the effect as described above.

If the number of "external" parameters is fixed, and they are the first positional parameters, then it is the same case as the optimizers and schedulers, see multiple-optimizers-and-schedulers. That is, you would define the parameter and type as model_b_constructor: Callable[[TypeExternalParam], BaseClassB]. And then in the __init__ body do obj_B = model_b_constructor(obj_A.param).
The proposed lazy_init: True pattern will not be done. It is a design decision that type hints are strictly followed. If someone did model_b: BaseClassB and then does lazy init, then the __init__ would not get an instance of BaseClassB. This is conceptually wrong. Also, in the code always an extra parameter needs to be given to create the instance. So it shouldn't be up to the CLI user to give in a config lazy_init: True. This should be part of the python code, not configuration.

@mauvilsa How would the corresponding config file look like? When I use Callable, it was already creating the object.

Not sure what you mean by "it was already creating the object".: My object model.constructor was not the __init__ function, but the instantiated object.
I created an MWE to show what I want: Lets say we have the following file test.py:
import pytorch_lightning as pl
from pytorch_lightning.cli import LightningCLI
from pytorch_lightning.demos.boring_classes import BoringDataModule
from test_classes import ModelParams

class Model(pl.LightningModule):

    def __init__(self, model_params: ModelParams):
        super().__init__()
        arg1 = 1
        arg2 = 2
        B_constructor = model_params.constructor
        obj = B_constructor(arg1, arg2)
        print(obj.arg1 == arg1)
        print(obj.arg2 == arg2)
        print(obj.paramA == 3)

if __name__ == "__main__":
    cli = LightningCLI(Model, BoringDataModule)

and test_classes.py:
from typing import Callable

class AbstractB:

    def __init__(self, arg1, arg2):
        self.arg1 = arg1
        self.arg2 = arg2

class B(AbstractB):

    def __init__(self, arg1, arg2, paramA):
        super().__init__(arg1, arg2)
        self.paramA = paramA

class ModelParams():
    def __init__(self, constructor: Callable[[int, int], B]):
        self.constructor = constructor

together with the config file test.yaml:
model:
  model_params:
    class_path: test_classes.ModelParams
    init_args:
      constructor:
        class_path: test_classes.AbstractB
        init_args:
          paramA: 3

Now python test.py fit --config test.yaml raise an error: Type typing.Callable[[int, int], test_classes.B] expects a function or a callable class: Expected 'test_classes.AbstractB' to be a class that instantiates into callable or a subclass of False. Got value: Namespace(class_path='test_classes.AbstractB', init_args=Namespace(paramA=3))
What do I need to do in order to use Callable?

The code and config above works as expected to me. Not sure what you have done differently. Do you have the latest version of jsonargparse installed?
I added print(f"constructor: {constructor}") to ModelParams and added print(f"B_constructor: {B_constructor}"), print(f"obj: {obj}") to Model. With these additions the output is
$ python3 test.py fit --config test.yaml
...
constructor: <function adapt_class_type.<locals>.partial_instance at 0x7fcbdb36f2e0>
B_constructor: <function adapt_class_type.<locals>.partial_instance at 0x7fcbdb36f2e0>
obj: <test_classes.B object at 0x7fcbdb7e3a60>
True
True
True
...

Exactly as expected.
I tried a few other modifications to make it fail, but I was unable to reproduce the exact same error. The only way I got an error was by redefining B as:
class B(AbstractB):
    def __init__(self, *args, paramA: int):
        super().__init__(*args)
        self.paramA = paramA

I would have hoped that this works also, but there seems to be an issue there. Anyway, the error is different.
By the way, please add type hints. Without type hints it doesn't fail for me. But the CLI is designed to work best when there are types.

Indeed, a had an old jsonargparse version (4.20.1). With the latest version it works correctly.
Now I am wondering, if the approach can still be improved?
The one direction is not to limit the number of positional arguments (with *args  as you were showing it). What would be the corresponding code for
class ModelParams():
    def __init__(self, constructor: Callable[[int, int], AbstractB]):
        self.constructor = constructor

?
Would it be
class ModelParams():
    def __init__(self, constructor: Callable[[List[Any]], AbstractB]):
        self.constructor = constructor

Can we get do something like bj = B_constructor(arg1=arg1, arg2=arg1)?

I have a similar issue, namely that to instantiate the model we need to know the shape of the data, which is only known after downloading and preparing the data. I am currently solving it this way:
def main():
    cli = LightningCLI(auto_configure_optimizers=False, run=False, ...)
    dm, mod = cli.datamodule, cli.model

    dm.prepare_data()
    dm.setup('fit')

    mod.initialize_modules(dm.input_shape, dm.output_shape)

    cli.trainer.fit(mod, dm)

class DataModule(LightningDataModule):
    # etc.

    def setup(self, stage):
        self.x, self.y = self.load_data()
        self.input_shape = self.x.shape[1]
        self.output_shape = self.y.shape[1]

class TrainingModule(LightningModule):
    # etc.

    def initialize_modules(self, input_shape, output_shape):
        self.predictor = nn.Sequential(
            nn.Linear(input_shape, self.hidden_shape), nn.ReLU(),
            nn.Linear(self.hidden_shape, output_shape)
        )

    def configure_optimizers(self):
        return ...

The disadvantage is that in this way I would need to implement all other commands (validate, test, predict).
Is there a more canonical/standard way to achieve the same result? If not, I think this is a valid use-case to support (in any case, this saves a lot of code compared to not using lightning, so thank you a lot already for this gem!)

Is there a more canonical/standard way to achieve the same result? If not, I think this is a valid use-case to support (in any case, this saves a lot of code compared to not using lightning, so thank you a lot already for this gem!)

This is a use case for links applied on instantiation, see cli docs or jsonargparse docs.
One possibility would be to implement in the LightningDataModule module two @property methods for the shapes. Accessing the property should automatically run whatever is needed to compute the shapes (i.e. setup). The LightningModule should receive in the__init__ the shapes. Finally create instantiation links from the data properties to the module parameters.
Having the shape dependent on the data is somewhat tricky. When you run fit it can make sense to compute the shapes from the training data. But if you later want to test, a checkpoint would be loaded and the shape be implied by that. It it is possible to compute the same shape from the test data, then it can work without issue, though it is unnecessary to compute it since the model comes from the checkpoint.


Show cost instead of infrastructure_cost, which omits markup cost

For Ocp cloud infrastructure, we should display cost instead of infrastructure_cost, which omits markup cost.
Fixes https://github.com/project-koku/koku-ui/issues/1206

Codecov Report

Merging #1208 into master will not change coverage.
The diff coverage is 50%.

@@          Coverage Diff           @@
##           master   #1208   +/-   ##
======================================
  Coverage    75.4%   75.4%
======================================
  Files         227     227
  Lines        4448    4448
  Branches      867     867
======================================
  Hits         3354    3354
  Misses        968     968
  Partials      126     126

Impacted Files
Coverage Δ

...ages/ocpCloudDashboard/ocpCloudDashboardWidget.tsx
71.42% <50%> (ø)
:arrow_up:

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 e7ef654...f82eb77. Read the comment docs.


Error installing on Ubuntu (II)

Bug report
__System info:  Ubuntu Xenial (16.04 LTS) (GNU/Linux 4.4.38-std-1 x86_64 )
Steps to reproduce:
curl -sL https://repos.influxdata.com/influxdb.key | sudo apt-key add -
source /etc/lsb-release
echo "deb https://repos.influxdata.com/${DISTRIB_ID,,} ${DISTRIB_CODENAME} stable" | sudo tee /etc/apt/sources.list.d/influxdb.list
sudo apt-get update && sudo apt-get install influxdb
Actual behavior:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'influxdb' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@ftr-app:~# sudo apt-get install influxdb
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
influxdb
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/17.3 MB of archives.
After this operation, 55.1 MB of additional disk space will be used.
Selecting previously unselected package influxdb.
(Reading database ... 32233 files and directories currently installed.)
Preparing to unpack .../influxdb_1.2.0-1_amd64.deb ...
Unpacking influxdb (1.2.0-1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up influxdb (1.2.0-1) ...
Failed to execute operation: Unit file is masked
dpkg: error processing package influxdb (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
influxdb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Fixed by doing
systemctl unmask influxdb.service


Mismatching between custom LabelSmoothing and and PyTorch's Label Smoothing

The current LabelSmooting in icefall (see below)
https://github.com/k2-fsa/icefall/blob/810b193dcc3ad3f7a65bc3def63493711c9a084e/egs/librispeech/ASR/conformer_ctc/transformer.py#L797
is based on ESPnet, which seems to be based on The Annotated Transformer.
As @janvainer  pointed out in #106, there is a built-in LabelSmooting loss in torch >=1.10, see https://pytorch.org/docs/master/generated/torch.nn.CrossEntropyLoss.html#torch.nn.CrossEntropyLoss
I just compared the implementation from PyTorch with the one in icefall and identified the following differences.
PyTorch's implementation follows the one described in the paper Attention Is All You Need
LabelSmoothing is proposed by the paper Rethinking the Inception Architecture for Computer Vision, which has the following formula:

First difference
icefall is using K - 1, not K. See the code below from icefall
https://github.com/k2-fsa/icefall/blob/810b193dcc3ad3f7a65bc3def63493711c9a084e/egs/librispeech/ASR/conformer_ctc/transformer.py#L853
Second difference
Rethinking the Inception Architecture for Computer Vision uses cross-entropy to compute the loss. See the formula from the paper, given below:

but icefall uses the following formula, i.e., KL-divergence

To match PyTorch's implementation (also the one used in the original transformer paper), we have to do the following changes:
(1) Change
https://github.com/k2-fsa/icefall/blob/810b193dcc3ad3f7a65bc3def63493711c9a084e/egs/librispeech/ASR/conformer_ctc/transformer.py#L853
to
true_dist.fill_(self.smoothing / self.size)

Also, we need to add self.smoothing / self.size to the target positions in true_dist.
That is, change
https://github.com/k2-fsa/icefall/blob/810b193dcc3ad3f7a65bc3def63493711c9a084e/egs/librispeech/ASR/conformer_ctc/transformer.py#L857
to use scatter_add_
            true_dist.scatter_add_(
                1,
                target.unsqueeze(1),
                torch.full(true_dist.size(), fill_value=self.confidence).to(true_dist),
            )

(2) Change
https://github.com/k2-fsa/icefall/blob/810b193dcc3ad3f7a65bc3def63493711c9a084e/egs/librispeech/ASR/conformer_ctc/transformer.py#L858
to
lable_smoothing_loss = -1 * (torch.log_softmax(x, dim=1) * true_dist).sum(dim=1)

@danpovey  Do you think we should make the above changes?

Yes I agree that it would be simpler and easier to understand.

Thanks for doing the comparison!


TimeVaryingDCMPlannerUnitTests segfaults on macOS

I noticed that TimeVaryingDCMPlannerUnitTests fails on macOS with a segmentation fault
https://github.com/dic-iit/bipedal-locomotion-framework/pull/346/checks?check_run_id=2884619713#step:20:62

I tried to replicate the error with https://github.com/GiulioRomualdi/blf-fastmac but I'm not able to replicate the error
@traversaro

Issue investigated in https://github.com/dic-iit/bipedal-locomotion-framework/pull/348

Since #348 is not failing. I think that this bug can be solved invalidating the cache and recompile the dependencies in macOS

Just to speculate on what happened, I think that the problem is that ABI changes in Homebrew-provided dependencies are not accounted for in the cache, so it is possible that the Homebrew dependencies ABI changed in a new build job, but the cache was not invalidated. To be honest, I am not sure what is the simple solution to account for that. In theory, we should include the versions of all homebrew packages used by the cached dependencies in the cache key, but that probably would result in many more rebuilt. Probably for now can just manually invalidate the cache whenever this happens.


#155519389 -  implement view single idea feature

What does this PR do?

Implement view single idea feature on the front-end

Description of Task to be completed?

create idea details page
create actions and reducers

How should this be manually tested?

clone and setup this repo locally
checkout to this branch feature/155519389/view-idea
run npm start:client to start the app.
click on idea title to navigate to idea details page.

Any background context you want to provide?

None

What are the relevant pivotal tracker stories?
https://www.pivotaltracker.com/story/show/155519389
Screenshots (if appropriate)

#### Questions:
N/A

Pull Request Test Coverage Report for Build 106

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

Totals

Change from base Build 92:
0.0%

Covered Lines:
301

Relevant Lines:
341

💛  - Coveralls


return FHIR exception details in endpoint requests

when an FHIR-side error occurs
BaseServerResponseException::getResponseBody contains more details regarding why the error occurred.
per discussion in #cohorting-backend

@jaigoradia because the change was simple enough, I ended up using main as the target branch.
let me know if you would prefer it to be as #79

changing target branch to WFFHCOHORT-278 per @jaigoradia's request.


SlotManager: releaseSlot needs to handle the case where particle's slot is pending

Done with: https://github.com/PolymerLabs/arcs/pull/109


feat: cancel spot requests

Description
Whenever a spot executor is created a spot request is created. Occasionally there might be open spot requests which have not been fulfilled.
Challenge: Make sure that spot requests are deleted only which belong to our module. Unfortunately the GitLab Runner does not tag them. We use the following logic for determinination:

state is open or active
they are associated to a SSH key which name starts with runner
they have the var.environment/var.overrides['name_docker_machine'] somewhere in the name

Solves part of #623
Closes #493
Migrations required
No.
Verification

[x] kill an agent manually and check the Cloudwatch logs. The function should log Removing open spot requests for environment and print either Spot requests deleted or No open spot requests found. There are no errors in the log.

merge conflicts fixed


block-grid.mobile-two-up

Expected Behavior

...
Current Behavior

...
Possible Solution

...
Test Case and/or Steps to Reproduce (for bugs)

Test Case:

How to reproduce:
1.
2.
3.
Context

...
Your Environment

Foundation version(s) used:
Browser(s) name and version(s):
Device, Operating System and version:
Link to your project:

Checklist

[ ] I have read and follow the CONTRIBUTING.md document.
[ ] This is a bug report or a feature request.
[ ] There are no other issues similar to this one.
[ ] The issue title and template are correctly filled.

Hi @IngridSexifuxsia,
Please fill out the issue template.


oneLink not work when app is open

Hello,
I am using react-native-AppsFlyer 6.4.0.
I am trying to trigger onelink (deeplink) when the user clicks on in-app-message.
when it's example://myRides it's works fine and Im route to the myRides screen , but when i am using
https://example.onelink.me/xxxx/xxxxx it's not working and nothing happens.
https://example.onelink.me/xxxx/xxxxx this link from push notification work fine.

sdfsdf

Hi @aharon-vish,
Thank you for reaching out to us.
To provide optimal support, we would kindly ask you to submit a support ticket to<EMAIL_ADDRESS>When submitting the ticket, please specify your AppsFlyer sign-up (account) email, app ID, reproduction steps, code snippets, logs, the links you used, and any additional relevant information.


docs(configuration): add resolve.restrictions

Document resolve.restrictions introduced in webpack v5.0.0-beta.18
Preview url: https://webpack-js-org-git-fork-chenxsan-feature-add-resolve-dot-8423d9.webpack-docs.vercel.app/configuration/resolve/#resolverestrictions

Thanks!


[Nuke] Not seeing any output

I've installed Cryptomatte following the instructions but I must be doing something wrong.  I'm using the supplied test images and don't see anything when I attach the gizmo.  I've tried deleting everything and starting over.  I've tried installing on Mac and Linux but they both act the same.  Troubleshooting says:
"Something went wrong. If you would like to report this, please the text in this window:
Error Traceback:
Traceback (most recent call last):
File "", line 4, in
File "/Users/brian/.nuke/cryptomatte_utilities.py", line 803, in troubleshoot_gizmo
issues = _troubleshoot_gizmo(node) + _troubleshoot_setup()
File "/Users/brian/.nuke/cryptomatte_utilities.py", line 797, in _troubleshoot_setup
issues.append(BAD_INSTALL)
NameError: global name 'BAD_INSTALL' is not defined"

Well, that's embarrassing. The issue is with your installation. I'll fix the message, in the next bug fix, but until you get that maybe try re-installing? The message would have said,

Installation is wrong, callbacks were not found. setup_cryptomatte() did not run, init.py may not be set up properly.

Please feel free to reopen this if following the installation instructions and setting up init.py does not fix the issue for you.


Create updated PRG file for the subset of genes found present (including genes found exactly, and those with denovo alleles to be included)

Please improve title.

Is this the cheap addition of new sequences to an existing index, to be used after discovery?

Can be renamed to be.

The title is fine, I was just wondering if I correctly understood it

Low priority for now (see #23 ).
If de novo pipeline requires, put this into high priority.


Add MaxNumParts

The number of participants, and therefore the number of off-chain signatures is currently not limited.
The implementer should also check for other cases of arbitrary long inputs.
To get some deterministic bench-marking results, all inputs should have defined maximum lengths.

Done in #7


nwg-panel: 0.7.8 -> 0.7.10

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for nwg-panel is: "GTK3-based panel for Sway window manager"
meta.homepage for nwg-panel is: "https://github.com/nwg-piotr/nwg-panel"
meta.changelog for nwg-panel is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.7.9 with grep in /nix/store/9imwnxjr1rawhwqjlyqqlc12wi9qbrhp-nwg-panel-0.7.9
found 0.7.9 in filename of file in /nix/store/9imwnxjr1rawhwqjlyqqlc12wi9qbrhp-nwg-panel-0.7.9

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
nwg-panel

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9imwnxjr1rawhwqjlyqqlc12wi9qbrhp-nwg-panel-0.7.9 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nwg-panel https://github.com/r-ryantm/nixpkgs/archive/66303456b3e292f7487d65f1832b5f7136b2a4f5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9imwnxjr1rawhwqjlyqqlc12wi9qbrhp-nwg-panel-0.7.9
ls -la /nix/store/9imwnxjr1rawhwqjlyqqlc12wi9qbrhp-nwg-panel-0.7.9/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

nwg-panel

Maintainer pings
cc @berbiche for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for nwg-panel is: "GTK3-based panel for Sway window manager"
meta.homepage for nwg-panel is: "https://github.com/nwg-piotr/nwg-panel"
meta.changelog for nwg-panel is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.7.10 with grep in /nix/store/32ivrsjggcy2h7g03h7rvkv7c54mbnpb-nwg-panel-0.7.10
found 0.7.10 in filename of file in /nix/store/32ivrsjggcy2h7g03h7rvkv7c54mbnpb-nwg-panel-0.7.10

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
nwg-panel

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/32ivrsjggcy2h7g03h7rvkv7c54mbnpb-nwg-panel-0.7.10 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nwg-panel https://github.com/r-ryantm/nixpkgs/archive/96449c156a28dba182073cc0220055dc81283aff.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/32ivrsjggcy2h7g03h7rvkv7c54mbnpb-nwg-panel-0.7.10
ls -la /nix/store/32ivrsjggcy2h7g03h7rvkv7c54mbnpb-nwg-panel-0.7.10/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

nwg-panel

Maintainer pings
cc @berbiche for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for nwg-panel is: "GTK3-based panel for Sway window manager"
meta.homepage for nwg-panel is: "https://github.com/nwg-piotr/nwg-panel"
meta.changelog for nwg-panel is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.7.11 with grep in /nix/store/l9mdz6840kwsdgpp81sjvsaif9qzs5sk-nwg-panel-0.7.11
found 0.7.11 in filename of file in /nix/store/l9mdz6840kwsdgpp81sjvsaif9qzs5sk-nwg-panel-0.7.11

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
nwg-panel

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/l9mdz6840kwsdgpp81sjvsaif9qzs5sk-nwg-panel-0.7.11 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nwg-panel https://github.com/r-ryantm/nixpkgs/archive/491d60d4d46f070062eb396ed4597e5ac6cc02ba.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l9mdz6840kwsdgpp81sjvsaif9qzs5sk-nwg-panel-0.7.11
ls -la /nix/store/l9mdz6840kwsdgpp81sjvsaif9qzs5sk-nwg-panel-0.7.11/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

nwg-panel

Maintainer pings
cc @berbiche for testing.


[Question] Neutrino and ZSO

Hello,I would like to know if there are any plans to add support for ZSO in Neutrino. I'm not sure if this has already been discussed or is planned.

There are no plans to add compression support in neutrino.
But I would like to see compression support in the server side of UDPFS, the successor to UDPBD.


refactor: deglobalization of bls_legacy_scheme 3/N

Issue being fixed or feature implemented
Many usages of CBLS{Signature,PrivateKey,PublicKey} assume using global variable, even if it can be specified explicitly in some situations.
These over-usages of bls::bls_legacy_scheme are blocker for changing buried height of activation of fork V19 on Regtest.
This PR helps unblock changing v19 height on RegTest, see: https://github.com/dashpay/dash/pull/6511
Prior improvements for BLS: https://github.com/dashpay/dash/pull/5443
What was done?
This PR does:

fixes Undefined Behavior in rpc protx register_legacy, protx register_fund_legacy, protx resiter_prepare_legacy, protx update_registrar_legacy
drop flag "is legacy" from secret key initialization and serialization (as it has no difference)
enforce specifying legacy flag to bls functions Sign, ToByteVector and in a helper SignSpecialTxPayloadByHash
removed unused methods from bls_ies.h and optimized headers usages
enforce p2p message mnauth to use Basic BLS scheme
enforce using flag legacy in RPC bls generate and bls fromsecret instead guessing which one user want based on v19 activation status.

How Has This Been Tested?
Run unit and functional tests; update testing framework test_framework.py to use _legacy RPCs which has been ignored before.
Reindex testnet src/qt/dash-qt -reindex -testnet -assumevalid=0 - SUCCEED
Reindex mainnet src/qt/dash-qt -reindex  -assumevalid=0 - SUCCEED
Breaking Changes
On RegTest RPC: bls generate, bls fromsecret should pass flag is_legacy for pre-v19 blocks
On RegTest RPC: protx register_legacy, protx register_fund_legacy, protx register_prepare_legacy, protx update_registrar_legacy should be used in pre-v19 blocks.
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation
[x] I have assigned this pull request to a milestone

Guix Automation has began to build this PR tagged as v22.1.0-devpr6508.f76f943c. A new comment will be made when the image is pushed.

Guix Automation has completed; a release should be present here: https://github.com/dashpay/dash-dev-branches/releases/tag/v22.1.0-devpr6508.f76f943c. The image should be on dockerhub soon.


Refactor tests

Codecov Report

Merging #160 (21586da) into develop (ba6c11b) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##           develop      #160   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           40        40
  Lines         1112      1112
=========================================
  Hits          1112      1112

Impacted Files
Coverage Δ

pfhedge/instruments/primary/brownian.py
100.00% <100.00%> (ø)

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 ba6c11b...21586da. Read the comment docs.


初始化项目出错

这块卡了好久了，也不知道为啥

`✔ Downloading template
✔ Copying template
✔ Processing template
ℹ Installing dependencies
✔ CocoaPods (https://cocoapods.org/) is not installed. CocoaPods is necessary for the iOS project to run correctly. Do you want to install it? › Yes, with Homebrew
✔ Installing CocoaPods
✔ Installing Bundler
✖ Installing CocoaPods dependencies (this may take a few minutes)
error warn Multiple Podfiles were found: ios/Podfile,vendor/bundle/ruby/2.7.0/gems/cocoapods-core-1.11.3/lib/cocoapods-core/Podfile. Choosing ios/Podfile automatically. If you would like to select a different one, you can configure it via "project.ios.sourceDir". You can learn more about it here: https://github.com/react-native-community/cli/blob/master/docs/configuration.md
✖ Installing CocoaPods dependencies (this may take a few minutes)
error Error: Looks like your iOS environment is not properly set. Please go to https://reactnative.dev/docs/next/environment-setup and follow the React Native CLI QuickStart guide for macOS and iOS.`

标准翻墙问题，文档里已经特别强调过了

刚玄学的解决了，似乎不是墙的问题，代理我这边是没问题的；
解决方法：到ios目录下pod install一下，然后用npx react-native run-ios运行，就是不知道下次还能不能这么玄学

因为墙的问题所以 pod install 没成功，所以需要你手动去重新pod install
如果代理没问题，那么初始化的时候就能自动 pod install 成功


where is the latency between the vehicle and the code  considered or can be considered?

which part of the code considers the lag or time gap between the vehicle model and the code ?

At the moment I do not consider lag. One easy way to fix the computation delay is to use the knowledge about the applied input at the moment, to simulate where the system will roughly be in one time step. This new state can then be used as the "current" state measurement.
This basically solves the issue that the MPC takes about 10ms to compute a solution but normally we assume that we apply the input immediately. If your robot has other delays, due to state estimation, you can try similar tricks to deal with these delays. Generally, delays should be as small as possible otherwise the performance will suffer a lot.


custom loss for many classes classification

Is it possible to define a custom loss function for many class classification?
I want to use lightgbm to construct a many class classification model for indoor bluetooth localization,I cut target area into many pieces with different id(hundreds of  class), Input is some signal strength values at each piece, output is the id of that piece, I want to make loss larger when distance error of predict id and target id is bigger than a specified value. current is multi-logloss, it does not work well when class number too big

refer to https://github.com/Microsoft/LightGBM/issues/1308