Try again to bring Harbor-CLI into Homebrew

this is a nice software, but not notable enough for us to package in Homebrew for now. This is not a decision on the merits of the software, but we cannot distribute every single piece of software and have to draw a line on “notability” somewhere. Of course, we would be happy to reconsider in the future.

In https://github.com/Homebrew/homebrew-core/pull/165860 the PR to add harbor CLI to Homebrew was rejected, we should try this again, once we reach a certain maturity and recognition in the community.

@Vad1mo if nothing else, would it be worth setting up a tap for this in the goharbor org so folks can pull it from there via brew?

yes this is the goal, to have a tap set up. We need to make the first relese of that

@tylerauerbeck I have no preference, for now it has to be a tap. Whatever move us closer to a release pipeline is good enough


Bower install issue

Doing bower install results in:
ENOTFOUND Package benbarnett/jQuery-Animate-Enhanced=benbarnett/jQuery-Animate-Enhanced not found
You may need to update your bower.json with the recent build number and remove your repo name from the package name, so:
"name":"jQuery-Animate-Enhanced"

+1

Fixed


Broken link on FAQ page

on FAQ page
in section "13. How did NLTK start?"
link "this plan" leads to a google.code page that says:
"There was an error getting resource 'source':
401: Anonymous users does not have storage.objects.get access to object google-code-archive/v2/code.google.com/nltk/project.json."
screenshot:

Best regards.

This is showing on all resources of code.google.com right now. It will probably be rectified in a while.


HasInlineMorphToFields trait prevents other relationships fields to be displayed

Hello.
I'm facing a new issue, described as follows:
Imagine that there's another relationship field in the Article resource:
MorphMany::make('Collection')
The details page, when resource uses the HasInlineMorphToFields trait, is completely replaced by one that does not show this new relationship field.
Another issue I've found is that labels are not used to display the morph types. (singularLabel and pluralLabel). Instead, I'm seeing the actual Resource class.
See the following screens, before and after using this package.

Hi @fntneves ,

Another issue I've found is that labels are not used to display the morph types. (singularLabel and pluralLabel). Instead, I'm seeing the actual Resource class.

Based on this I assume you are using an old version where the label and the mentioned issues on the detail page were still a problem.
Can you double check that you are using version v0.1.6

I was using 0.1.4, actually.
This is now fixed. This package is getting better, you're doing a great job!
Additionally, is it possible to leverage "displayUsingLabels" function on Select fields?
Select option values are being displayed instead of labels.
Select::make('Unidade do valor de desconto', 'discount_unit')
    ->options([
        DiscountUnitType::FIXED => 'Fixo',
        DiscountUnitType::PERCENTAGE => 'Percentual',
     ])
    ->displayUsingLabels(),

I've attached two more screenshots:

@fntneves v0.1.7 fixes it, now you can use the ->displayUsingLabels() as well as ->displayUsing() on any field


LSTM layer with dropout does not use fast CuDNN implementation in Keras 3

I have a model that uses the keras LSTM layer with dropout not equal to zero. I am using TF backend.
I noticed a performance drop after updating to Keras 3 and after checking I found out that the requirements for using the fast CuDNN LSTM implementation.
With Keras 2.15, the requirements to use the cuDNN implementation are:

activation == tanh
recurrent_activation == sigmoid
recurrent_dropout == 0
unroll is False
use_bias is True
Inputs, if use masking, are strictly right-padded.
Eager execution is enabled in the outermost context.

With Keras 3, the requirements to use the cuDNN implementation are:

activation == tanh
recurrent_activation == sigmoid
dropout == 0 and recurrent_dropout == 0
unroll is False
use_bias is True
Inputs, if use masking, are strictly right-padded.
Eager execution is enabled in the outermost context.

This change has a significant impact on performance when using dropout. Can we expect a change or some alternative way to use dropout without performance degradation?

Thanks for the report -- this is now resolved at HEAD.


search bar was created successfully

Closes #
What new changes did you make? Tick all applicable boxes

[ ] Added new abbreviation
[ ] Fixed something in the source code
[ ] Added a new feature
[ ] Fixed the docs (README.md, CONTRIBTUING.md, etc)

Describe the new changes you added.

Share a screenshot of new changes

Sorry to ask, but which issue does this pull request fix? I see that there is now a search bar slapped unto the middle of the page. Although the search bar itself looks great, you also have to admit that it kind of breaks the site in a way. Unfortunately, I will have to close this pull request because we are not looking to add an extra search bar, or modify the already existing one just as yet. However, there is a similar conversation going on in #296. We can discuss the development of this feature there more, and then know how to proceed.


Bracket bevy feedback

Hey just wanted to share some feedback while poking around in the bevy branch!
First off, on exiting of the program, bracket-bevy seems to throw an error on unwrapping of the window in the mouse system

let (camera, camera_transform) = q_camera.single();
    let wnd = if let RenderTarget::Window(id) = camera.target {
        wnds.get(id).unwrap()
    } else {
        wnds.get_primary().unwrap()
    };

Which is odd since bracket-bevy is just a plug-in of systems running in bevy so I would think bevy wouldn't update the system on app exit. A quick google search didn't lead me down and successive results on why the system would still run.
Point 2: it seems that when importing bracket-bevy, and bevy as specific git branches, I am clashing when importing bracket-pathfinding. When implementing base map or alrogithm2D, the compiler is complaining that two different versions of bracket-geometry are being used. Pretty odd since they are locked at the same version.
I plan to continue to mess around with the plug-in but would love to help out if you could use it!
 I have to use the specific git branch for each bracket library. Silly me

One issue with the scaler, for non-resizing modes, the scaler can produce negative usize results resulting in a panic by rust. My debugs are not very helpful, but you can see that h (height) is 25, but the step_pos.1 is 26 resulting in a negative overflow.
Testing with TerminalScalingMode::ResizeTerminals works fine since it actually updates the height and width
https://user-images.githubusercontent.com/9278174/173469540-3e16fb00-c5b4-4e36-a028-be0bc35b0051.mp4

Went ahead and fixed the window issue! https://github.com/amethyst/bracket-lib/pull/270

There's a few overflow crashes right now. I goofed when I translated from Bevy and used a bunch of usize where i32 made sense (negatives can make sense when calculating UI positions, even if they aren't used) - as well as a few "print command parameters are in a different order than the main library" type things - so I'll be fixing those. Once that's done, I'll get some safety checks into the scaler.
Funny Bevy issue. I can't find a way to set window size from a plugin, because the window size resource is read before plugin instantiation. :-|

@thebracket that's effectively a known limitation. We either need to solve https://github.com/bevyengine/bevy/issues/5111 or https://github.com/bevyengine/bevy/issues/1255 to resolve that.

Closing this in favor of 0.8 coming out. Alot of changes will happen. I created a seperate issue (#281 )to track more things I have noticed.


chore: remove ts-lib from dev deps

:tada: This PR is included in version 2.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Create cellPartOfAnatomicalEntity.yaml

addresses #696 https://github.com/obophenotype/cell-ontology/issues/450

is this redundant with #718?

yes it is, closing.


bug: Make only the search bar sticky, allowing "Near Me" and "Trending" buttons to scroll

Describe the bug
Currently, the entire top bar (including the search bar, "Near Me," and "Trending" buttons) stays sticky while users scroll, essentially hiding the main content aka the pandal cards.
To reproduce
Make only the search bar sticky, and allow the "Near Me" and "Trending" buttons to scroll off the screen as users move down the page. This will make the interface cleaner and provide more visible space for viewing pandals.
Additional information

Please see screenshot for reference

you can assign this issue to me


Trigger feature flag for new link styles on govuk-link

What
Set the feature flag for applying the new govuk-link styles ($govuk-new-link-styles) to true, thus setting the new link styles on our components by default.
Why
This change has come from the latest release of GOV.UK frontend. This change has been extensively researched and will have a positive impact on link visibility across govuk.
Visual Changes
coming soon...

Closing this as it's out of date


DeprecationWarning: Invalid 'main' field ...

Upon fresh git clone I get the following error.

Project still runs fine.
Just wanted to bring that to your attention 👍🏽

Upon further testing amigo, I discovered errors on /posts and /authors.
Also on mobile, the drop menu is not centered.
Attached is a short
https://github.com/zeon-studio/astroplate/assets/1428292/d545edaa-c4ba-49f3-b986-06796c11be08
In case the video came out blurry or illegible, here are a few screenshots.

I filed to mention my versions:
node --version = v18.12.0
npm --version = 8.19.2
yarn --version = 1.22.19

👍🏽

hey @jjaimealeman
Thanks for pointing out this issue, I have added a fix for the issue. please check it now.

Excellent amigo.
Thanks!
Have a good weekend.


terra-clinical-header border lowlight is incorrect

Bug Report
When the fix was made in PR #649, it set the variable --terra-clinical-header-border-bottom to a color in lowlight.  But in the source code and the fusion theme, it is a border, for example: 1px solid #d3d4d5
I think the fact that the variable is not a proper border is keeping the border a light color when it needs to be dark.
Description
Bottom border on terra-clinical-header is still not dark for a lowlight theme.
Additional Context / Screenshots

Expected Behavior
Border should be darker in lowlight.
Possible Solution
Update the lowlight variable to be a valid border value, like 1px solid #08090a
Environment

Component Name and Version:terra-clinical-header  3.17.0
Browser Name and Version: Chrome
Node/npm Version: [e.g. Node 8/npm 5] node 11
Webpack Version:
Operating System and version (desktop or mobile):

I'm finding some other issues with our lowlight app, so the fact the border variable is defined inconsistently may not be the cause of the image attached.  However, it probably would still be good to get it consistent.

I'm sorry, i really thought i fixed it :(

I did some more testing in the Chrome browser tools.  If I change the variable to something that is defined as a border, then the color is updated.  So the fact it is not a valid border seems like it might be causing our issue.
Is there any chance to get a correction this week?


Icons Request

Firstly, GREAT WORK.
By far the best implementation of svg / font icons.
Please consider adding these:

Globe (Very useful specially for internationalization | Language Menu)
Shopping Cart
Houzz, Etsy, StoreEnvy, SquareMarketplace icons  (you already have ebay / amazon)
HTML5 / CSS3

THANK YOU!!!!

Sorry for the late reply. I will be adding all of these to a new SVG icon system implementation coming soon.

Thanks!


Memory leak?

I've deploed the vault-init based on the howto from https://github.com/kelseyhightower/vault-on-google-kubernetes-engine.
But the memory consuption of the vault-init scripts seem to be ever growing, untill the k8s memory limit kicks in and kills the container. Than all starts over again.

name: vault-init
resources:
    limits:
        cpu: 100m
        memory: 512M
    requests:
        cpu: 10m
        memory: 128M

The issue is resolved by pull-request #4


Filter value with leading space gets trimmed resulting in no match

Version
2.14.2
Details
When I give Gridify a filter value with a leading space the resulting query trims the filter criteria resulting in no matches being found.
Granted I should sanitize my data, but I still believe this to be a bug.
Steps to reproduce
When I give Gridify the filter value: "tags= with leading space", it generates the following query statement:
SELECT VALUE root FROM root JOIN (SELECT VALUE EXISTS(SELECT VALUE m0 FROM root JOIN m0 IN root["tags"] WHERE (m0["name"] = "leading space"))) AS v0 WHERE ((root["tags"] != null) AND v0)
Note that the filter criteria no longer contains the leading space, resulting in no matches returned from my store.

For what it's worth, I worked around the issue by modifying my filter mapper:
new GridifyMapper<MyModel>()
	.GenerateMappings()
	.AddMap(nameof(Filter.Tags), t => t.Tags.Select(tag =>  tag.Name.TrimStart()))

Hi @DonavanPrinsTrimble,
just FYI another workaround is escaping the leading space
tags=\ with leading space

also would be nice if I get some feedback about a potential configuration to disable the AutoTrim feature. do you think would be useful in your case?


(maint) Add arm64 to Debian architecture fact

Prior to this commit, the Debian architecture fact had special cases for amd64 and i386, but otherwise returned the output of uname.
This commit updates the fact to use arm64 instead of what aarch64, which is what uname returns. We prefer arm64 here because that's what Debian's naming convention uses.

Hi @jcharaoui , we're in the process of adding official Debian aarch64/arm64 support in Puppet and since I know that you're a Debian maintainer, we were hoping you might be able to confirm that this is the desired behavior.
It seemed like from the Supported Architectures doc that Debian generally prefers "arm64" over "aarch64," but I know architecture names can vary depending on the context.
Thank you!

I think the appropriate thing would be for facter to report the architecture as arm64 but I'll consult with my Debian colleagues and let you know!

For what it's worth, running facter architecture now, using facter from Debian's own archive on an arm64 installation will report aarch64.

One suggestion that's been made, if the goal is to report the Debian architecture, would be for facter to simply supply the output of dpkg --print-architecture.

Thanks for the feedback @jcharaoui ! We're going to discuss this a bit internally. Do you feel the benefits of having this fact be consistent with Debian's convention and the amd64/i386 fact would outweigh the potentially breaking change of going from aarch64 to arm64?

Hey, module author here. In puppet modules we often need to check the architecture. Our live is much much easier when the usage of aarch64 vs arm64 is consistent for every operating system. I don't care which value is used, but it's easier to develop modules when it's the same. Otherwise we always need to check the architecture and the operating system.

Thanks for the feedback @jcharaoui ! We're going to discuss this a bit internally. Do you feel the benefits of having this fact be consistent with Debian's convention and the amd64/i386 fact would outweigh the potentially breaking change of going from aarch64 to arm64?

I think a breaking change here is probably fine as long as it's properly documented. Since aarch64 is only used by Debian (and derivatives) we can make sure the change enters the next release and comes with a user-facing announcement (NEWS file, in Debian packaging terms).

Hey, module author here. In puppet modules we often need to check the architecture. Our live is much much easier when the usage of aarch64 vs arm64 is consistent for every operating system. I don't care which value is used, but it's easier to develop modules when it's the same. Otherwise we always need to check the architecture and the operating system.

Right, there's consistency within Debian, but also consistency with other operating systems. I'm not sure how other facter reports the architecture for operating systems . The schema seems to suggest there is a conversion to amd64 already happening on several operating systems when uname reports x86_64.

Another perspective on a breaking change: normalize the architecture on what uname outputs, meaning getting rid of amd64 in favor of x64_64. Today in Foreman we already normalize that back:
https://github.com/theforeman/foreman/blob/d8200eeae33ff730cf85fcae9c47e92466c64a6a/app/services/puppet_fact_parser.rb#L58-L60
Because if you have a homogeneous fleet of servers you don't want those differences.

Perhaps you want os.architecture for the OS specific architecture code while architecture is what uname returns.

We also already massage uname output for the generic Linux fact: https://github.com/puppetlabs/facter/blob/a866afe3c4eccc74d1ae519aeecd8dc51b686820/lib/facter/facts/linux/os/architecture.rb#L13
While os.hardware seems to be the output of uname -m without any modification, at least for all Linux platforms, macOS, and FreeBSD.
It seems like using the latter could be the more uniform option across many nodes/platforms (as @bastelfreak described in his comment)

That looks like a useful fact.

I've updated this PR with @jcharaoui 's suggestion of using dpkg to determine architecture.
This should address inconsistencies between architectures on Debian and will prevent us from having to periodically update mappings between uname -m and what Debian uses.
os.hardware should be able to address the issue of this type of fact varying between distros.

@mhashizume could you rebase to pick up the Thor fix?

This had further reaching implications than we'd realized and we will be reverting this change before it's part of a Facter release. While official Puppet support for Debian on ARM is forthcoming, Ubuntu on ARM has been supported since 2021 and this change has the potential to break a lot of integration that's already been built for those platforms.
I would still encourage users looking for an architecture scheme that's consistent between OSes to use os.hardware since os.architecture has historically been different for Debian-based OSes and will report i386 and amd64 (as opposed to x86 and x86_64) even after this change is reverted.


Fixes License.txt link in README.md.

I signed it

This was fixed by another commit already.  https://github.com/Polymer/polymer/commit/3d8fd0f5e02dad48f7994168b15ce466021152fe
Thanks for helping out!


Fix unit tests on Windows

(Re-do of https://github.com/sourcegraph/cody/pull/1150 because all the bots won't run on forks)
I don't know how sound all of these changes are, but they fix the failing tests I have on Windows.

Use platform-correct paths (drive letters + backslashes on Windows) in tests and debug printing
Previously lots of code assumed posix-style paths then had mismatches on windows because of slash direction
Replace fake Uri class with vscode-uri
As part of doing (1), I found that vscode.Uri was missing. While adding it, I realised there was a mock Uri implementation (presumably to avoid importing vscode where it won't be available), however the vscode-uri package (which does not depend on VS Code) was also already imported, so I removed the fake Uri class and just used this. This required updating a bunch of places (Uri => URI) and I don't know if there are other implications of doing this, but I think it's better.
Add launch config to run current test file under debugger
Makes it easy to debug tests (or run without debugging for the current file) without having to use the terminal
Use prettier when editing JSON files like .vscode/settings.json and .vscode/launch.json (these already seemed to be formatted using Prettier, but it wasn't set explicitly so the formatting gets messed up if you didn't have Prettier as default formatter)

Test plan
Tested using pnpm test:unit.

Related question: should the bots be running these tests on Windows too?

Quick comment on vscode-uri, the custom Uri implementation is intentional because vscode-uri is not a comprehensive implementation of vscode.Uri. I'm on the phone right now so can't share concrete details but replacing Uri with URI will break the JetBrains plugin. We have tests to reproduce the cases but they don't run in CI yet because they depend on a Sourcegraph instance.

replacing Uri with URI will break the JetBrains plugin

Ah, thanks for the note! If you have more info on this, it'd be good to add a comment to the class about this for reference.
I reverted that part of the change and hit some issues because the graph tests end up with a mix of shim and real URIs, and there are various comparisons on fsPath. The shimmed fsPath is incorrect on Windows because it just returns the URI path:
https://github.com/sourcegraph/cody/blob/57dd0b0c5d971ceeee12963a9a6f50ad73357a37/vscode/src/testutils/mocks.ts#L53
I was able to work around this for now by tweaking comparing URI.toString() in the failing test (I did first try changing the whole test to use the shim URIs, but that causes other failures because some other code is using vscode-uri and their paths are compared in expectations).
It would probably be good to:

Fix fsPath to work correctly in the shim
I'm not sure if the implications of changing this - if the shim is used in production code, it's currently giving incorrect fsPaths on Windows. This should be fixed, but will it change/break anything that may have had existing assumptions about that wrong format?
Make it clearer where real/mock URIs should be used
It's not clear to me whether we should use the shim URI everywhere and never use vscode-uri, or if there are reasons to use vscode-uri in some places (there are a fair few files using vscode-uri).

I guess an ideal solution would be to remove the shim and find a solution to for the JetBrains plugin - but I don't know how feasible that is (because I'm not familiar with specifics of the problem). If it's not feasible (I suspect if it was easy you would have done it!), I wonder if we could reproduce those issues in tests so the bots can ensure that doesn't get broken by this kind of change 🙃

I'm not sure if the implications of changing this - if the shim is used in production code, it's currently giving incorrect fsPaths on Windows

This is very insightful, thank you for sharing! We are using the shim for the JetBrains plugin and this could be the root caused behind why autocomplete is not working on Windows.

Make it clearer where real/mock URIs should be used

Great point! The shim should never be used directly. It's fine to replace all usages of vscode_shim.Uri with vscode.Uri. In lib/shared, it's fine to use vscode-uri. I'll follow up with a PR to improve documentation.
The only reason we need the shim to be 100% compatible with vscode.Uri is because we replace all imports on the vscode module with the shim when running the agent (which we use from JetBrains and Neovim). Originally, I tried using vscode-uri URI in the shim but it crashed at runtime because vscode-uri URI is not a drop-in replacement of vscode.Uri.

Regarding tests on windows: All you need is to add windows here #1315 🙂

I pushed some changes, though the changes to each set of tests is a little different:

debugPrint() now always uses posix paths, that way it can easily compare strings written in that form (and my assumption is that this is just a debug string and using / on Windows will cause no issues)
graph-section-observer tests have the results of sectionObserver.getContextAtPosition run through a new function withPosixPaths which rewrites the paths so that they can be compared to inline snapshots using posix paths
graph tests use file URIs built with the native path format rather than hard-coded posix string paths. This is the ideal case because on Windows it's testing everything like-for-like. It works here because there aren't inline snapshots/strings that make it difficult to use the native path format.

Seems like there are some other issues running the bots on Windows (and macOS with node 16). Mac looks like connectivity issues downloading wasm libraries, and Windows looks like maybe timeouts and being terminated.
I've reverted that change from this PR to focus on just having the tests pass locally, and will dig into that in another PR (to avoid keeping this open and potentially causing conflicts as people work on other tests).
I also discovered that on the bots Git was using autocrlf which breaks snapshot tests (which combine a mix of a file from disk and some string-build code) which differed from my machine, so I've made this explicitly use lf to make this consistent. I think ideally auto should be used (so on Windows the tests are using crlf), but that'll need some changes to the snapshot annotation code (it's also not clear to me whether this difference would affect anything outside of tests so it might not be worthwhile).

The Windows issue was a timeout. I increased the timeout to 10 mins (from 5), and they went green in a little over 5 mins.
Slowest steps are:
pnpm install - 2:43
pnpm build - 0:35
pnpm run test:unit --run - 1:12
pnpm store - 0:42
It's possible that part of the issue is that a lack of cache (because it's never succeeded before) is slowing it down a little, but since it's never guaranteed the cache is available, the timeout should probably allow for this. So I've included the change to increase from 5->10 mins here and re-enabled on Windows.
For macOS, the issue is a bit weirder.. on the Node 16 bot, it fails with what seems like a connectivity issue downloading wasm files (and this seems to be 100% consistent):
vscode postinstall$ pnpm download-wasm
vscode postinstall: ><EMAIL_ADDRESS>download-wasm /Users/runner/work/cody/cody/vscode
vscode postinstall: > ts-node-transpile-only ./scripts/download-wasm-modules.ts
vscode postinstall: We are missing 12 files.
vscode postinstall: Error: read ECONNRESET
vscode postinstall:     at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
vscode postinstall:   errno: -54,
vscode postinstall:   code: 'ECONNRESET',
vscode postinstall:   syscall: 'read'
vscode postinstall: }
vscode postinstall:  ELIFECYCLE  Command failed with exit code 1.
vscode postinstall: Failed
 ELIFECYCLE  Command failed with exit code 1.

However I can't understand why this would only affect Node 16 (the Node 20 bot is always green). Maybe there's some difference in Node 16/20 that affects networking on a Mac? Seems odd though. I guess my first questions would be:

Why was Node 16 picked?
Would it be reasonable to skip the Node 16 both only for Mac?

Why was Node 16 picked?

That was added because VS Code as of (I think) ~ 1month ago used Node 16 in the runtime and since some of the remote desktop setups for VS Code often lag a few versions behind, we got a lot of bug reports after adding code that did not work on Node 16.

Would it be reasonable to skip the Node 16 both only for Mac?

Yeah I think so! The main intention with Node 16 is to find unavailable APIs, We only need to run one test for this on one platform 👍
Excellent work here, thank you 🙇

I've tweaked this so only Linux runs on Node 16, and the others on 20. I also rebased on latest because some tests were changed and moved around so there were conflicts, so I resolved those and updated the tests accordingly.
Please take a look :-)


How to determine a windows machines is 64bit or 32bit ?

When I run  wmic OS get OSArchitecture in powershell, I can get the right result.
PS C:\Users\Administrator> wmic OS get OSArchitecture
>>
OSArchitecture
64-bit

Which api in windows-rs can get the same result?  thanks.

This isn't really a question specific to the Windows crate. Such questions are more suitable for https://stackoverflow.com/.
Anyway, it depends on what problem you're trying to solve. I would probably just query the following environment variable:
fn main() {
    println!("{:?}", std::env::var("PROCESSOR_ARCHITECTURE"))
}


VSCode Extension ?

Is there any chance that this project will be a VSCode Extension?
Appreciate.

Anyone's welcome to do that, but I don't have the time for it.

I am interested in doing an extension for json-to-go

It is live at https://marketplace.visualstudio.com/items?itemName=maracko.json-to-go
Any feedback is welcome!

That's cool! I will have to try this out.

Interesting! It's actually good. 👍

We can probably close this, then.
Feel free to submit a PR to add a link to it on the web page!


Images Uploaded

Acceptance Criteria:

All images to be used uploaded to an img folder with descriptive names

I've created a folder for "images" The following images are sized to work with Mobile and Desktop. Upon initial design all images were sized the same for compatibility purposes. Please let me know if this works or doesn't.


ENH: Speed up CircleCI

Fix the numpydoc build error about plot_gallery being a str
Speed up CircleCI by using a machine image
Get rid of a warning (hopefully) that we see at the start of the doc build

Amazing! I've been hating those errors and warnings!

@rob-luke it looks like CircleCI has been running for >35 minutes. We're going to start paying for CircleCI time soon, so it would be good to cut this down if possible. It looks like PRs are currently doing all builds using sphinx-multiversion (right?), would it be an option for PRs to just build the current PR version of the docs rather than all versions? You could adopt a syntax like we have for MNE-Python that could even cause it to build all versions rather than just the current dev one for example.

would it be an option for PRs to just build the current PR version of the docs rather than all versions?

Yes. This is how the github doc building works, it only builds the PR branch. This was handled in the github doc building using...
https://github.com/mne-tools/mne-nirs/blob/8b9e7b854b6308ed4067e778c2fad6a277fa1f8b/.github/workflows/SphinxBuild_PR.yml#L23
and maybe...
https://github.com/mne-tools/mne-nirs/blob/8b9e7b854b6308ed4067e778c2fad6a277fa1f8b/.github/workflows/SphinxBuild_PR.yml#L59-L63

Feel free to merge this if you're happy @rob-luke , we can deal with CircleCI speed in https://github.com/mne-tools/mne-nirs/pull/418

Thanks @larsoner


invalidateSessionForAppLostFocus not working when screen is closed - Android 13

Using android 13 (I didnt test in others), when you close your device (click in the power button), and after the expected time (75 seconds in my case) return to the app, it doesnt fire the event.
I hope you can solve it.
Thanks for your contribution! This package is very important for me.

I solve mine by adding a pakcge called wakelock, In this case we know that the app is still in foreground even the though it's on screen.
I hope this finds you helpful.

Hi @guperini , Android kills background processes for power saving ref.
Thanks for the input @Erchil66 , I'll go through the package and see if same can be used here

Hi, In my case when app in minimize (background -> foreground) invalidateSessionForAppLostFocus is work in first time but next time when minimize again it not work.

Hi @klaokamol I'll check this

@klaokamol Its working fine for me, can you check if the same issue is occurring in the example app? You can disable invalidateSessionForUserInactivity so that it won't interrupt.

Thank you for reply, I'm testing by use same code like exmaple: Sample Usage and rollback to old version is work fine.
my invalidateSessionForUserInactivity duration set to 1 second
test step:

run app first minimize app and open app again
(invalidateSessionForAppLostFocus is work in first time and timeoutEvent == SessionTimeoutState.appFocusTimeout)

minimize app (foreground -> background)

flutter: state AppLifecycleState.inactive -> lib stamp time 00:01:30.00
flutter: state AppLifecycleState.hidden
flutter: state AppLifecycleState.paused

open app again (background -> foreground)

flutter: state AppLifecycleState.hidden
flutter: state AppLifecycleState.inactive -> lib stamp time 00:01:31.00
flutter: state AppLifecycleState.resumed -> check dif time ( 00:01:31.00 and 00:01:30.02) < 1s

difference time in SessionTimeoutManager function didChangeAppLifecycleState  is always false because it's double stamp time. and sessionConfig.stream.listen((SessionTimeoutState timeoutEvent) not call back.

Hi, I think the issue is because when you re-open the app inactive state is emitted which overwrites the previous value of _appLostFocusTimestamp. I have raised a fix, can you checkout to this branch and try once. If it works I'll merge the PR and create a new release

@SankethBK I tested it and it worked. Thanks for your help. :bow:

Great! I'll create a new release with this fix


B-21686: Allow Prime Sim User to update estimated weight and actual weight independently

Agility ticket
Summary
Issue was that the Prime Sim User could not update Estimated Weight and Actual Weight Independently. This was happening because there is a default 0 in both text fields so if it is not removed then it would get submitted as 0, which would violate the validation rule of a value of 1 or greater. Prime API already supports updating both fields independently. The issue was the prime sim was submitting the payload with default value of 0.
Is there anything you would like reviewers to give additional scrutiny?
this article explains more about the approach used.
Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[ ] Have the BL acceptance criteria been met for this change?
[ ] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Access the Prime Sim
Start with a shipment that has no estimated weight nor an actual weight
Try updating actual weight with a value greater than 0. Save the changes. Should be successful.
To speed up testing so you do not have to create a new shipment null out the actual weight , then update the estimated weight on the shipment as the prime.
Try adding a 0 in the field and you will get the validation error.

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
[ ] This change meets the standards for Section 508 compliance.

Backend

[ ] Code follows the guidelines for Logging.
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys.
[ ] Have been communicated to #g-database.
[ ] Secure migrations have been tested following the instructions in our docs.

Screenshots

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against c49e2ce5518c7961491a9ee00e146e5edc22a936

Test coverage on server failed.
Last run: Thu 12 Dec 2024 01:25:29 AM UTC
Refer to this report to see coverage details for the server app.
Documentation for test coverage can be found at this link.

Able to update the estimated weight independently from the actual weight, and vice versa without error.
Only thing missing is a test to validate in PrimeUIShipmentUpdate.test.jsx

@danieljordan-caci Tests added.

Test coverage on server failed.
Last run: Fri 13 Dec 2024 03:11:25 PM UTC
Refer to this report to see coverage details for the server app.
Documentation for test coverage can be found at this link.


Moves SolutionContainerManagerComponent to Shared.

About the PR

So far, mostly just namespace changes.
Why / Balance

I was attempting to refactor chemical reactions and wound up requiring this. The other option is unpredicted chemical reactions.
Technical details
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

SolutionContainerManagerComponent, SolutionContainerSystem, SolutionChangedEvent, and associated components have been moved to shared.

Changelog

<!--
Make sure to take this Changelog template out of the comment block in order for it to show up.

Could you please check your linter failure?

Will when I get back to my house.


Add rocBLAS backend

Description
As discussed in #99 with the newly added hipSYCL support oneMKL is able to target AMD GPUs. This PR adds the rocBLAS backend to the BLAS domain. The changes were based on the Cuda backend, and the set of supported BLAS functions matches the functionality of the Cuda backend.
Testing was carried out using rocm 4.5 and rocBLAS 4.5, and hipSYCL built from develop cc794e3, on a system with AMD MI Instinct 100 GPUs.
rocm_tests_out.log

[x] Do all unit tests pass locally? Attach a log.
[x] Have you formatted the code using clang-format?
[ ] Update Readme

Hi, thank you for the quick feedback @mmeterel and @andrewtbarker !

Please make sure all files are formatted properly with clang-format and use the check mark.
Have you formatted the code using clang-format?

Formatted, and checked.

Can we add the device info in the gtest/ctest report? You can look at other backends as an example.
Start 9: BLAS/RT/Nrm2TestSuite/Nrm2Tests.ComplexSinglePrecision/Column_Major_
9/3336 Test : BLAS/RT/Nrm2TestSuite/Nrm2Tests.ComplexSinglePrecision/Column_Major_ ......................................................... Passed 1.61 sec

This seems to be a rocm issue I opened https://github.com/RadeonOpenCompute/ROCm/issues/1625 , hipSYCL just uses the rocm interface that does not seem to work on the test system.

AFAIK, rocBLAS backend will be supported by only hipSYCL implementation. (Please correct me if I am wrong).

Yes I agree

This information needs to be added into README along with how to download rocBLAS, hipSYCL, their supported version numbers, build directions, etc.

I'll look into this I will ping you in the next 1-2 days when I am finished with the changes to the README.

@sbalint98 Could you please comment on the minimum ROCm version and the hardware support needed for ROCm support in general with hipSYCL? For example, do we need ROCm 4.5? Can we use Vega RX, or do we absolutely need MI100?

do we need ROCm 4.5?

I tested this PR with rocm 4.5 exclusively but in my opinion, it should work with rocm+rocblas 4.2 and above. In terms of the version of rocBLAS the presence of the rocblas_status_check_numerics_fail type is necessary, which should be present since rocBLAS 4.2. In the case of building hipSYCL against rocm 4.2+, hipSYCL needs to be built against the LLVM compiler shipped with rocm.

Could you please comment on the minimum ROCm version and the hardware support needed for ROCm support in general with hipSYCL?

In terms of hipSYCL rocm backend hardware support, all cards supported by rocm are available under hipSYCL as well. see here . Pinging @illuhad for more details if needed.

Can we use Vega RX, or do we absolutely need MI100?

I think Vega cards are sufficient for hipSYCL. We are also using a FirePro card for some of our testings. Pinging @illuhad for more details

FWIW: hipSYCL/hipSYCL-rocm 0.9.0 (can't remember which version of ROCm was included) worked for me back in April.

In terms of hipSYCL rocm backend hardware support, all cards supported by rocm are available under hipSYCL as well. see here . Pinging @illuhad for more details if needed.

That's right, there's nothing special in hipSYCL that would restrict hardware support - it should "just work" on all devices supported by ROCm. Naturally, we can only test on a selection of GPUs due to not having all conceivable ROCm GPUs available. We mainly test on Radeon VII, Radeon Pro VII workstation cards and MI50 and MI100 data center cards.
The main limiting factor for oneMKL is the availability of some functionality in earlier rocBLAS versions as @sbalint98 points out.

In the case of building hipSYCL against rocm 4.2+, hipSYCL needs to be built against the LLVM compiler shipped with rocm.

This is the case with some clang versions (I think clang 12), because not all changes required for ROCm 4.2+ support had reached upstream by that point. When building hipSYCL against newer clang versions, those might work without coming from the ROCm release.

@sbalint98 @illuhad Thank you for your responses. One more question :) Is there a specific linux kernel we need?

I think the answer is similar to the hardware support one. We are supposed to be supporting everything that rocm supports as well :https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html#prerequisites

@illuhad Can you have a look at the changes to the README?

@mmeterel test_helper.hpp includes oneapi/mkl.hpp that in turn includes types.hpp. However, let me update this solution. Defining half conflicts with rocrand.h since half is also defined there. I also noticed that in the rocblas backend I use half instead of sycl::half after fixing that there is no need for aliasing half.

@mmeterel, I added the fix

Results of the mklCPU and netlib backend tests:
mklcpu_rocblas_hipsycl.txt
netlib_rocblas_hipsycl.txt

@mkrainiuk  Could you please review this PR? Especially for the changes in Copyright banner, build process and README? I provided feedback on README as much as possible (it is WIP)

Results of the mklCPU and netlib backend tests:
mklcpu_rocblas_hipsycl.txt netlib_rocblas_hipsycl.txt

Thanks for confirming.

@sbalint98 Could you please resolve conflicts?

Sure, rebased onto develop

Thanks for your time, helpful comments and contributions @mmeterel @mkrainiuk


Default withtypeprovider to true

What do you think about making the withtypeprovider parameter default to true?

Let's implement it then!

Hey @petrsvihlik is this a large change?  I've began looking through some of the other issues just to get an idea of what is going on exactly.

hi @kzisme , not really. it should be a matter of adjusting this line: https://github.com/Kentico/cloud-generators-net/blob/master/src/CloudModelGenerator/Program.cs#L20
The expected output is that when you launch the program without explicitly specifying withtypeprovider it should generate the class even so.

implemented as a part of https://github.com/Kentico/cloud-generators-net/pull/33


[WIP] First draft of plugins

This PR is implementing an external plugin system using GRPC. Admins will be able to set external plugins extending capabilities of Broadway.
With the current implementation an external service will be able to receive event notifications about instances. This way we can move Slack notifications to an external Plugin. I'm also planning to add a plugin for the new LED board.

If we moved k8s deployment to a plugin then we could build and test broadway an order of magnitude faster

@therealplato so true! I'll draft  a protofile for showing  how that could look  like.

#92


Ignore TLS verification for containerd insecure registries

Signed-off-by: Waleed Malik<EMAIL_ADDRESS>
What this PR does / why we need it:
When using an insecure registry TLS verification should be ignored by default. This behaviour was missing when the user was using an insecure registry for containerd. This PR fixes that isue.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1547
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Skip TLS verification when using containerd for insecure registries

Aren't we set http prefix to the endpoint, so there there is no TLS involved in insecureRegistry? How this helps then?

Closing this pull request because it doesn't solve the actual issue. This requires an API change and will be resolved with https://github.com/kubermatic/kubeone/issues/1611


Scheduled Post function always runs three times

Every time the cron job runs the scheduled-post function, the function executes three times.

Expected Behavior

The function should run exactly once.
Current Behavior

When the server automatically runs the function, it does so three times, wasting server resources and posting the same thing three times.

The issue is that the function will keep running until it gets a 200/OK response.


Health check of all the pods on one node are failing after a period of time until cilium pod is manually restarted

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
After a random period of time, all health check on a node are failing.
If I delete the cilium pod on the node, the health check are now working.
Sometimes it concerns all the nodes of the cluster and I need to restart all cilium pods.
Cilium Version
v1.11.13
Kernel Version
Linux dc1-k8s-dev-02 5.13.0-39-generic #44~20.04.1-Ubuntu SMP Thu Mar 24 16:43:35 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Linux dc1-k8s-dev-03 5.13.0-39-generic #44~20.04.1-Ubuntu SMP Thu Mar 24 16:43:35 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Linux dc1-k8s-dev-04 5.13.0-39-generic #44~20.04.1-Ubuntu SMP Thu Mar 24 16:43:35 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Linux dc1-8gpudev-01 5.4.0-131-generic #147~18.04.1-Ubuntu SMP Sat Oct 15 13:10:18 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Linux dc3-4gpudev-01 5.4.0-131-generic #147~18.04.1-Ubuntu SMP Sat Oct 15 13:10:18 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Kubernetes Version
v1.24.4
Sysdump
The file is compress as .tar.xz. Github blocks xz extension, so I append a fake .zip.
cilium-sysdump-dev-20230131-114412.tar.xz.zip
Relevant log output
Example of failing health check on the node dc3-4gpudev-01:

Events:
  Type     Reason     Age                     From     Message
  ----     ------     ----                    ----     -------
  Normal   Pulled     32m (x305 over 20h)     kubelet  Container image "registry.console.toolkit.com/system.component.eaid/eaid:20230126162559.bb8d8c3327" already present on machine
  Warning  Unhealthy  23m (x3232 over 20h)    kubelet  Readiness probe failed: Get "http://<IP_ADDRESS>:8080/health/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  Warning  Unhealthy  8m13s (x1228 over 20h)  kubelet  Liveness probe failed: Get "http://<IP_ADDRESS>:8080/health/live": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  Warning  BackOff    2m54s (x1644 over 20h)  kubelet  Back-off restarting failed container

The cilium cilium-9l8cn on this node is still running, so I can do any test if you need.

### Anything else?

_No response_

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

I'm seeing a lot of packet drops due to missed tail calls between the CoreDNS pods and some of the pods (always eai-toolkit/registry-images-docker-import-xxx):
Jan 31 10:44:09.088: kube-system/coredns-64897985d-fqtm2:53 (ID:21214) <> eai-toolkit/registry-images-docker-import-27916800-fzkrm:54855 (ID:20554) Missed tail call DROPPED (UDP)

That is clearly not expected from Cilium.
I also see all of those registry pods are stuck on Init:0/1, maybe because of these packet drops. The CoreDNS pods are on different nodes, but the registry pods are all on dc1-8gpudev-01.
Questions:

What exact command(s) did you use to install Cilium?
Is there anything different about the dc1-8gpudev-01 node?
Is there anything special about the registry pods?

Hi @pchaigno
Thank you for your help!

What exact command(s) did you use to install Cilium?

I have a etcd cluster with 3 instances installed for cilium on the 3 control-planes like it is done for the kubernetes etcd and I have a HAproxy/keepalived to get virtual IP for the 3 control-planes. I am using this virtual IP in the cilium configuration (see values.yml)
To install cilium, I am using the helm chart with this helm-charts-values.yaml.txt file.
I just noticed I still have an extra config to increase rate limiting from my previous issue (https://github.com/cilium/cilium/issues/19648). Maybe I should delete this part.

Is there anything different about the dc1-8gpudev-01 node?

Others has Taint to avoid pods like registry-images-docker-import to run on them. So, dc1-8gpudev-01 remains as a main runner for these pods.

Is there anything special about the registry pods?

It is a kubernetes CronJob and the Pod/Job are mainly doing a docker pull & docker push to another registry using https://github.com/containers/skopeo. I think I will need to review the CronJob configuration because there are too much Fail:
spec:
  failedJobsHistoryLimit: 1
  schedule: 0 */1 * * *
  successfulJobsHistoryLimit: 3
  suspend: false

All pod were blocked in Init0/1 because there is a initContainer to wait for the availability of the docker registry to push (registry installed locally in Kubernetes):
          initContainers:
          - command:
            - sh
            - -c
            - while true; do wget -T 15 -c https://registry.console-dev.toolkit.com
              && break; sleep 5; done
            image: busybox
            imagePullPolicy: IfNotPresent
            name: wait

And the log for this initContainer are:
wget: bad address 'registry.console-dev.toolkit.com'
wget: bad address 'registry.console-dev.toolkit.com'
wget: bad address 'registry.console-dev.toolkit.com'
wget: bad address 'registry.console-dev.toolkit.com'
wget: bad address 'registry.console-dev.toolkit.com'
wget: bad address 'registry.console-dev.toolkit.com'
wget: bad address 'registry.console-dev.toolkit.com'
wget: bad address 'registry.console-dev.toolkit.com'
...

I didn't notice that there are so many Miss tail call DROP. Could it be linked to a NetworkPolicy which blocked the traffic between registry-images-docker-import to coredns ? I don't have any network policy on registry-images-docker-import but I have for few deployments.
I was too much focus on the node dc3-8gpu-01 (cilium pod cilium-9l8cn) because of that in file cilium-bugtool-cilium-9l8cn-20230131-114412/cmd/cilium-health-status---verbose.md:
All other nodes can connect to <IP_ADDRESS> but the host cannot connect to itself:
  dc3-4gpudev-01 (localhost):
    Host connectivity to <IP_ADDRESS>:
      ICMP to stack:   OK, RTT=415.49µs
      HTTP to agent:   OK, RTT=436.589µs
    Endpoint connectivity to <IP_ADDRESS>:
      ICMP to stack:   OK, RTT=485.721µs
      HTTP to agent:   Get "http://<IP_ADDRESS>:4240/hello": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

I updated to 1.11.14 and waiting to see if I can reproduce the issue

I finally found the origin of my issue and I was able to reproduce it.
There was also another bug linked to that which was new pod on the node didn't have any network. dig/curl to internal service or outside website didn't work at all.
When we were using cilium 1.6, there no automatically mount of bpffs, so there was a remaining entry in /etc/fstab:
bpffs         /sys/fs/bpf     bpf     defaults 0 0

I was looking to a buggy node, I noticed that:

almost all cilium bpf * list (bandwidth, endpoint, lb, ct, nat, ipcache, tunnel) were empty.
ip route on the host is good
cilium status is marked as OK
cilium identity list seems good
cilium endpoint list seems good
tcpdump is able to show the DNS request from a new pod on the host sudo tcpdump -i any -n udp and port 53 and host <IP_ADDRESS> -vvv:

[Interface: any] 23:37:59.801832 IP (tos 0x0, ttl 64, id 36002, offset 0, flags [DF], proto UDP (17), length 55)
[Interface: any]     <IP_ADDRESS>.39696 > <IP_ADDRESS>.53: [bad udp cksum 0x5f76 -> 0xde31!] 31542+ A? google.com. (27)

but cilium monitor -vv didn't show any request from this new pod
I noticed that cilium bpf metrics list only contains 2 metrics:

cilium bpf metrics list
REASON                    DIRECTION   PACKETS   BYTES
Policy denied             EGRESS      50907     4455409
Unsupported L3 protocol   EGRESS      440       31944

Policy denied is increasing for each dig I tried to run on the new pod
cilium bpf policy get --all is returning only 4 files /sys/fs/bpf/tc/globals/cilium_policy_xxx whereas a good node has 20 files

And I noticed that bpffs was mount multiple times. I think something called at some point sudo mount -a which add another mount point:
mount|grep bpf
none on /sys/fs/bpf type bpf (rw,relatime,mode=700)
none on /sys/fs/bpf type bpf (rw,relatime)

I made a reproduction of the issue on a node just rebooted:

start a new pod named S with http server and health check
start a new pod named A
run curl in the pod A: Working
call sudo mount -a to duplicate mount point for none on /sys/fs/bpf type bpf (rw,relatime)
start a new pod named B
run curl in the pod A: Working
run curl in the pod B: Fail
after 2 hours, health check on pod S are failing

Thank @pchaigno for the help :)


Update titles and headings

Changed titles and headings to sentence case.

Changed title and heading verbs to gerunds.

closed, and created new PR: https://github.com/lensapp/lens/pull/1321


fix(DataDoc): Use Previous Query Engine

We noticed there's a default query engine set that's used when creating a new query cell on a DataDoc, but we wanted to have the option of defaulting to a query cell's previous selected query engine since it's easier in the case of having multiple query engines and when users are creating query cells for the same previously used query engine.
This is the new option on the User Settings page:

Functionality when Use Previous Query Engine is enabled:

@LulaV14 before merge, can you fix the lint error? just for future reference, you can use pre-commit https://www.querybook.org/docs/developer_guide/developer_setup to do it automatically

@LulaV14 before merge, can you fix the lint error? just for future reference, you can use pre-commit https://www.querybook.org/docs/developer_guide/developer_setup to do it automatically

Thanks for pointing that out, I was using Github Codespaces and forgot to install the pre-commit hook 😅


Modules renaming proposal

With the addition of multiplatform support, I encountered a name clash and, as a result, confusion in understanding.
As an example, there is a multik-native module, its artifacts will be as follows:

multik-native-jvm
multik-native-native

multik-native-macosX64
multik-native-macosArm64
multik-native-iosArm64
multik-native-linuxX64
multik-native-mingwX64

This naming makes confusion.
Therefore, it is necessary to rename the modules in accordance with their purpose and multiplatform.
Since renaming modules breaks compatibility and makes publishing difficult, I'm posting this as a proposal.
multik-api
multik-api doesn't have problems with multiplatform naming conventions, but the name doesn't reflect the essence of the module. The module itself consists of a data structure (ndarray), simple and iterative operations on ndarrays, and interfaces for mathematics, linear algebra, and statistics. In that case, I think it's correct to call this module multik-core, since this describes the essence well.
multik-jvm
There is confusion in the names multik-jvm-jvm and multik-jvm-native here. This module implements interfaces from multik-api (multik-core) in pure Kotlin without native code. Then it can be called as multik-pure-kotlin. But in this case, this name is not well in my opinion. I would be glad if you suggest other variants.
multik-native
Obviously there is confusion with native for jvm. This module implements interfaces from multik-api (multik-core) using the OpenBLAS library and partially cpp code. One obvious option was to name this module as multik-openblas, but other native libraries may be added in the future and then this name will not be correct.
multik-default
This module combines multik-jvm and multik-native implementations. This name works well for users who do not want to understand the intricacies of the library. Nevertheless, in terms of Kotlin, it is more correct to name this module as multik-common, but you can leave the old name as well.
I will be glad if you share your vision and experience of using the library in order to clearly understand how to name different modules.

Modules renamed as follows:

multik-api -> multik-core
multik-jvm -> multik-kotlin
multik-native -> multik-openblas
multik-default -> multik-default (remained the same)


Make all relevant variables parameters and set defaults

This will allow for a better CLI/API with more customization.

@dosu-bot


Any way to upload video?

Would love to know!

Another vote for video upload support

same here, I really need this feature, does anyone figure it out ?

Unfortunately, I do not think uploading videos is allowed on the web version. Therefore, it will probably not be added.

Unfortunately, I do not think uploading videos is allowed on the web version. Therefore, it will probably not be added.


Fix DataTree.coords.__setitem__ by adding DataTreeCoordinates class

Doesn't work yet - pushing to get feedback on the approach.

[x] Closes #9204
[x] Tests added
[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst
[ ] New functions/methods are listed in api.rst

cc @shoyer

This now builds on top of #9453, so that should be merged first.

I think this is basically ready now @shoyer


提示为安装Python

Your os

The version of electron-ssr

What's the problem

App log here

0.2.6

if your os is Ubuntu18 ,you can common line write
sudo cp /usr/local/python3  /usr/local/python


model.extendedGrant cannot verify client_id

The other grant types make sure that the client id from the authorization header matches the provided client_id parameter. However, if the extendedGrant handler wants to base its actions off of the actually verifed clientId, there's no clear way for it to do so — it can only access the supposed client_id passed in the body, which may be spoofed!
Either the authorized client id should be passed to the helper, although that would be an incompatible change. Perhaps if the user object returned from the extendedGrant delegate method includes a clientId field, it would be compared to self.client.clientId as done in the useAuthCodeGrant logic? So at least extendedGrant could opt-in to a followup check.

Ah, I understand, makes sense - we recently fixed a similar issue by adding the verified client credentials into the req object (https://github.com/thomseddon/node-oauth2-server/blob/master/lib/grant.js#L354-L357), perhaps if we just moved this assignment further up, inside the checkClientCredentials function?

Comments welcome on #143

This should work nicely, thanks for the quick improvement!


Build llvmdev 9.x for ppc64le

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [109].

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [111].

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

:tada:


Use "this" keywords in attrs constructor and styled template strings.

To avoid unnecessary wrappers. I want to write the following code.
const Input33 = styled.input.attrs<{}>({
  placeholder:"Hover here...",
  innerRef:(x:HTMLInputElement) => { this.input = x },
  onMouseEnter:() => this.input.focus()
})`
  padding: 0.5em 2em;
  margin: 0.5em;
  color: palevioletred;
  background: papayawhip;
  border: none;
  border-radius: 30px;
  ${console.log(this)||``}
`;

However, all of "this" value is undefined. Can I get the expected value from there?

You're using arrow functions that bind lexically to the outer scope.


Azure Subnet Get Error: Failure preparing request: StatusCode=0 -- Original Error: autorest: No scheme detected in URL

Bug Report

What happened?
Get subnet api is throwing error while preparing the request.
What did you expect or want to happen?
Execute the request.
How can we reproduce it?
Using mentioned code.
Anything we should know about your environment.
go version go1.14 darwin/amd64

package main
import (
"fmt"
"context"
"github.com/Azure/azure-sdk-for-go/services/network/mgmt/2018-10-01/network"
"github.com/Azure/go-autorest/autorest/azure/auth"
)
func main() {
azureServicePrinciple:= auth.NewClientCredentialsConfig("APPID", "TOKEN", "TENANT")
subnet_client := network.NewSubnetsClient(raz.subscriptionID)
a, err := azureServicePrinciple.Authorizer()
if err!=nil{
fmt.Println(err)
}
subnet_client.Authorizer = a
ctx:=context.Background()
subnet_info,err := client.subnet_client.Get(ctx, "RG",
"VNET",
"SUBNET", "")
if err!=nil{
fmt.Println(err)
}else{
fmt.Println(subnet_info)
}
}
Error is Failure preparing request: StatusCode=0 -- Original Error: autorest: No scheme detected in URL

Hi @rahulroshan96 thanks for this issue!
The error is complaining the host URL in the request is missing the scheme, for instance http or https.
In your program, you are assigning the authorizer to the variable subnet_client, which should be fine, but when you invoke the get function, you use client.subnet_client. Are you sure this is the same client as the client you are assigning the authorizer?
If you decide to create the client struct by using native initialization rather than calling the funtion NewSubnetsClient you will have to give it a BaseURI, otherwise the BaseURI would be empty and then the error in your description will show up.


Another related package

https://github.com/3stack-software/meteor-embox-value
I've used it in Blaze Components multiple times, but it's nice to see a Mitar approach!

You should do a pull request that adds it to the README file.

Thanks.


Unable to cut Moes WS-B-US

I've been battling with this a bit and eventually got it to a point where it tries to update the firmware but then get this error...
Oct 23 21:30:50 dnsmasq[16]: query[A] a3.tuyaus.com from <IP_ADDRESS>
Oct 23 21:30:50 dnsmasq[16]: config a3.tuyaus.com is <IP_ADDRESS>
Using PSK v1 - Received PSK ID version 01

[21:30:50.403682 Log (Client)] Request: HTTPServerRequest(protocol='https', host='a3.tuyaus.com', method='POST', uri='/d.json?a=tuya.device.uuid.pskkey.get&et=1&t=6&uuid=aEMVRiO3C29d&v=1.0&sign=db6107e682f60d21a780ab3733031e61', version='HTTP/1.1', remote_ip='<IP_ADDRESS>')
[21:30:50.403891 LOG (Client)] ==== Request body ===
{"t":6}
[21:30:50.404666 LOG (Client)] ==== End request body ===
[21:30:50.406416 LOG (Server)] Response:  {'result': {'pskKey': ''}, 't':<PHONE_NUMBER>, 'success': True}
[21:30:50.409805 MQTT Sending] Sending firmware update message {"data":{"firmwareType":0},"protocol":15,"t":1698096650} using protocol 2.2
[21:30:50.415129 MQTT Sending] Triggering firmware update message.
[21:30:50.415432 MQTT Received] Topic: smart/device/in/4wZ9YVmw4oO0Mxqabik5 - Message: {"data":{"firmwareType":0},"protocol":15,"t":1698096650}
Oct 23 21:31:10 dnsmasq[16]: query[A] m2.tuyaus.com from <IP_ADDRESS>
Oct 23 21:31:10 dnsmasq[16]: config m2.tuyaus.com is <IP_ADDRESS>
Oct 23 21:31:10 dnsmasq[16]: query[A] m2.tuyaus.com from <IP_ADDRESS>
Oct 23 21:31:10 dnsmasq[16]: config m2.tuyaus.com is <IP_ADDRESS>
Oct 23 21:31:30 dnsmasq[16]: query[A] m2.tuyaus.com from <IP_ADDRESS>
Oct 23 21:31:30 dnsmasq[16]: config m2.tuyaus.com is <IP_ADDRESS>
Oct 23 21:31:33 dnsmasq[16]: query[A] m2.tuyaus.com from <IP_ADDRESS>
Oct 23 21:31:33 dnsmasq[16]: config m2.tuyaus.com is <IP_ADDRESS>
Oct 23 21:31:59 dnsmasq[16]: query[A] m2.tuyaus.com from <IP_ADDRESS>
Oct 23 21:31:59 dnsmasq[16]: config m2.tuyaus.com is <IP_ADDRESS>
Oct 23 21:32:04 dnsmasq[16]: query[A] m2.tuyaus.com from <IP_ADDRESS>
Oct 23 21:32:04 dnsmasq[16]: config m2.tuyaus.com is <IP_ADDRESS>
Oct 23 21:32:26 dnsmasq[16]: query[A] m2.tuyaus.com from <IP_ADDRESS>
Oct 23 21:32:26 dnsmasq[16]: config m2.tuyaus.com is <IP_ADDRESS>
Oct 23 21:32:32 dnsmasq[16]: query[A] m2.tuyaus.com from <IP_ADDRESS>
Oct 23 21:32:32 dnsmasq[16]: config m2.tuyaus.com is <IP_ADDRESS>
Oct 23 21:32:33 dnsmasq[16]: query[A] a3.tuyaus.com from <IP_ADDRESS>
Oct 23 21:32:33 dnsmasq[16]: config a3.tuyaus.com is <IP_ADDRESS>
Using PSK v1 - Received PSK ID version 01
Decryption failed due to padding error with key choice TuyaCipherKeyChoice.SECKEY. Retrying with other key choice
Decryption failed due to padding error with key choice TuyaCipherKeyChoice.AUTHKEY. Retrying is false - bailing out
[!] Unable to decrypt device reponse.  PSKKEY/AUTHKEY do not match device.
Oh no, something went wrong with updating firmware! Try again I guess...

PSKKEY/AUTHKEY do not match device. means you are using an incorrect profile.  Because the device already has an A- prefix, we can't protect against you using the wrong profile.
You will not get PSKKEY/AUTHKEY errors using the correct profile.  You need to go back to the profile that caused the device to change to A- in the first place.

Thanks, in amongst all my trial and error it does seem to have become mixed up. I have tried all the profiles and none work. I also have a second switch so I'll now be trying with that one to see if I can make some progress starting entirely from scratch agin.

Argh, the other switches a bought all seem to have the v1.3.5 tuya firmware. There is only one profile for this version and it doesn't work :-(

The 1.3.5 firmware for plugs is for BK7231T, if that profile didn't work, then it means you probably have BK7231N, and 1.3.5 for that one is on the known patched list.  https://github.com/tuya-cloudcutter/tuya-cloudcutter/wiki/Known-Patched-Firmware  Serial flashing will probably be your only option there.

Thanks, they are pretty easy to open up so will investigate serial flashing.

Sorry, mixing up issues.  Yeah, 1.3.5 on the Moes switches is for sure patched and BK7231N.  Serial flashing is for sure the only option.

Closing, as your specific case requires serial flashing, there is nothing we can do on the CloudCutter side.


RecyclerView and Clickable buttons

Hi,
is any way to use AndroidSwpieLayout with clcikable bottom_wrapper children and clickable surface view?

try this PR: https://github.com/daimajia/AndroidSwipeLayout/pull/106


CreateVmWizard - skip close wizard dialog confirmation after VM creation

Fixes: #1277 .
Close confirmation modal appears when closing the CreateVMWizard modal even if the VM already created and there are no data which will lose.
I fixed that and now if the VM is already created the CreateVMWizard will close without confirmation and will skip the confirmation dialog.
WDYT?

Hello contributor, thanks for submitting a PR for this project!
I am the bot who triggers "standard-CI" builds for this project.
As a security measure, I will not run automated tests on PRs that are not from white-listed contributors.
In order to allow automated tests to run, please ask one of the project maintainers to review the code and then do one of the following:

Type ci test please on this PR to trigger automated tests for it.
Type ci add to whitelist on this PR to trigger automated tests for it and also add you to the contributor white-list so that your future PRs will be tested automatically. ( keep in mind this list might be overwritten if the job XML is refreshed, for permanent whitelisting, please follow #3 option )
If you are planning to contribute to more than one project, maybe it's better to ask them to add you to the project organization, so you'll be able to run tests for all the organization's projects.

ci add to whitelist

LGTM


Feature | 新增setnx命令

We're currently processing your upload.  This comment will be updated when the results are available.


Calling get on an NVS variable before it's set causes a crash

I made function to get status and it tries to retrieve a couple of strings from NVS but if they haven't been set it causes a reboot.
If they've been set then it's all good, but if they haven't been set yet and I run this bit of code:
NVS myNamespace(WIFI_STORAGE_NAMESPACE, NVS_READONLY);
myNamespace.get(KEY_SETTINGS_SSID, &ssid, false);
myNamespace.get(KEY_SETTINGS_PASSWORD, &password, false);
then I get:
abort() was called at PC 0x400fc6f3 on core 1
And the esp reboots. There doesn't seem to be a "check" function to see if the namespace has been used or the variables have been set. Is there a workaround for this?
Sorry, once I get my head around the esp-idf API a bit more I'll probably be able to fix it myself and send a patch but for now I'm a bit stuck. Any help appreciated!

Looks like you implemented an elegant resolution.  Thank you kind sir.  Is this issue now ready for closure?

Thanks! Im really happy I can contribute.


It's extremely difficult to install the library

Current Behavior
We had an attempt to add tamagui library to both: react native and next js projects.
Both unfortunately unsuccessful.
We followed the documentation. Also tried different things, e.g.:
https://github.com/tamagui/tamagui/issues/524#issuecomment-1398576145
https://github.com/tamagui/tamagui/issues/303#issuecomment-1319008879
Still no luck with getting the library up and running.
Similar issues were already raised - and closed with no conclusion. So I'm raising a new one wondering if anything can be done to make tamagui installation process smoother.
Expected Behavior
Better installation experience. I'm sure this great library can get more attention if this will be improved.
Tamagui Version
1.23.0

Reproduction
Follow the steps from documentation.

System Info
No response

This morning I released a new starter template that shows off a complete configuration from scratch, plus sets up webpack and vite.
I'll leave this open and in the future will run through the entire docs again and see.
It would be super helpful for you to do that and push it to a repo somewhere for me to debug. This is OSS and we have tons of resources out there, many starter templates, etc. If you are stuck following docs you should grab any of the starters and go from there. But it's valid if there is some missing step.


yarn/npm start no longer prints listen port

I noticed that when I start a new razzle project in development mode it now only outputs:
✅  Server-side HMR Enabled!
🚀 started

Where the screenshot in the main README shows a message of 'started on port 3000'? Especially for newbies starting the server for the first time (or when you configure an alternative port in a project) it is very useful to output the port on development startup.

Getting this issue also, also nothing runs on port 3000 when this message is sent.

I'm no expert, but I might have inadvertently resolved this when looking and Typescript linting problems.
In index I moved the error callback to .on instead of passing it as a function into the listen method, so express now looks like:
export default express()
  .use((req, res) => app.handle(req, res))
  .listen(port, () => {
    console.log(`> Started on port ${port}`);
  })
  .on("error", e => {
    console.error(e.message);
    throw e;
  });

Now the port is displayed.  HTH


TypeError: test.describe is not a function when using nodejs, selenium and mocha

I am getting TypeError: test.describe is not a function when using 'test' with describe, it, before etc.
Using node, selenium and mocha to run tests.
Please find the code below:
Test that I am executing:
    var LoginObj = require('../pages/Login.js');
    var HomeObj = require('../pages/Home.js');
   var LoginData = require('../testdata/LoginData.json');
   var using = require('jasmine-data-provider');
   var basetest = require('../pages/BaseTest.js');
   var test = require('selenium-webdriver/testing')
   var driver = basetest.getDriver();

     test.describe('Checking  Login Functionality', function() {

        test.beforeEach(function(){
            driver.get('https://applicationurl.com');
           driver.manage().window().maximize();
         //driver.manage().timeouts().implicitlyWait(30000);

            });

       LoginData.forEach(function(data, username, password) {
       test.it('Login with: '+data.username+" and "+data.password, function() {

         //LoginObj.get();

          LoginObj.login(data.username, data.password, data.answer);

         assert.isTrue(HomeObj.isLogoutDisplays(),'Login successful, Passing
         Test!')
         console.log('Login flag is: '+HomeObj.isLogoutDisplays()+', Failing
      Test!');

               })

      });

           test.afterEach(function() {

               HomeObj.logout();

                  })

   });

Is that anything I am lacking somewhere? or it's an issue., I have installed mocha using npm install mocha --save and running my test using npm test.

I am sorry but I am not following where is the usage mocha in the code you provided?

@Bamieh @plroebuck , describe is already used  and 'test' is basically comes from var test = require('selenium-webdriver/testing'), which is actually used when executing tests with selenium and mocha .
I have used this implementation after referring so many articles on the web.
some of them are:
https://blog.testproject.io/2017/06/07/javascript-testing-with-selenium-webdriver-mocha/
https://simpleprogrammer.com/selenium-with-node-js/
https://dzone.com/articles/selenium-nodejs-and-mocha
May be  I am lacking somewhere. However If I remove 'test' and run using npm test, tests execute but all of them faililng. Might be mocha runner execution completes before invoking my test flow in browser.
I am getting this in console:
D:\Day_User\Rohit\Eclipse\Workspace\Mochatest>npm test

<EMAIL_ADDRESS>test D:\Day_User\Rohit\Eclipse\Workspace\Mochatest
mocha tests/AllevaLoginTest2.js

Checking Alleva Login Functionality
1) Login with: rohitnegi and Test@12345
2) Login with: testuser and Test@12345
0 passing (28ms)
2 failing

Checking Alleva Login Functionality
Login with: rohitnegi and Test@12345:
ReferenceError: assert is not defined
at Context. (tests\AllevaLoginTest2.js:25:3)

Checking Alleva Login Functionality
Login with: testuser and Test@12345:
ReferenceError: assert is not defined
at Context. (tests\AllevaLoginTest2.js:25:3)

DevTools listening on ws://<IP_ADDRESS>:12555/devtools/browser/694d41b2-857e-4664-9d3c-6be7904a4d06
(node:2592) UnhandledPromiseRejectionWarning: NoSuchElementError: no such element: Unable to locate element: {"method":"xpath","selector":"//input[contains(@ng-model,'UserName')]"}
(Session info: chrome=66.0.3359.181)
(Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.2.9200 x86_64)
at Object.checkLegacyResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\error.js:585:15)
at parseHttpResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:533:13)
at Executor.execute (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:468:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:2592) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:2592) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate
the Node.js process with a non-zero exit code.
(node:2592) UnhandledPromiseRejectionWarning: NoSuchElementError: no such element: Unable to locate element: {"method":"xpath","selector":"//input[contains(@ng-model,'UserName')]"}
(Session info: chrome=66.0.3359.181)
(Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.2.9200 x86_64)
at Object.checkLegacyResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\error.js:585:15)
at parseHttpResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:533:13)
at Executor.execute (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:468:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:2592) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:2592) UnhandledPromiseRejectionWarning: NoSuchElementError: no such element: Unable to locate element: {"method":"xpath","selector":"//input[contains(@ng-model,'Password')]"}
(Session info: chrome=66.0.3359.181)
(Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.2.9200 x86_64)
at Object.checkLegacyResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\error.js:585:15)
at parseHttpResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:533:13)
at Executor.execute (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:468:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:2592) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)
(node:2592) UnhandledPromiseRejectionWarning: NoSuchElementError: no such element: Unable to locate element: {"method":"xpath","selector":"//input[contains(@ng-model,'Password')]"}
(Session info: chrome=66.0.3359.181)
(Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.2.9200 x86_64)
at Object.checkLegacyResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\error.js:585:15)
at parseHttpResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:533:13)
at Executor.execute (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:468:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:2592) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4)
(node:2592) UnhandledPromiseRejectionWarning: NoSuchElementError: no such element: Unable to locate element: {"method":"xpath","selector":"//input[@type='submit' and @value='Log In']"}
(Session info: chrome=66.0.3359.181)
(Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.2.9200 x86_64)
at Object.checkLegacyResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\error.js:585:15)
at parseHttpResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:533:13)
at Executor.execute (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:468:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:2592) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 5)
(node:2592) UnhandledPromiseRejectionWarning: NoSuchElementError: no such element: Unable to locate element: {"method":"xpath","selector":"//input[@type='submit' and @value='Log In']"}
(Session info: chrome=66.0.3359.181)
(Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.2.9200 x86_64)
at Object.checkLegacyResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\error.js:585:15)
at parseHttpResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:533:13)
at Executor.execute (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:468:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:2592) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)
(node:2592) UnhandledPromiseRejectionWarning: NoSuchElementError: no such element: Unable to locate element: {"method":"xpath","selector":"//input[contains(@ng-model,'twoFactorModel.answer')]"}
(Session info: chrome=66.0.3359.181)
(Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.2.9200 x86_64)
at Object.checkLegacyResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\error.js:585:15)
at parseHttpResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:533:13)
at Executor.execute (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:468:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:2592) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 7)
(node:2592) UnhandledPromiseRejectionWarning: NoSuchElementError: no such element: Unable to locate element: {"method":"xpath","selector":"//input[contains(@ng-model,'twoFactorModel.answer')]"}
(Session info: chrome=66.0.3359.181)
(Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.2.9200 x86_64)
at Object.checkLegacyResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\error.js:585:15)
at parseHttpResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:533:13)
at Executor.execute (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:468:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:2592) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 8)
(node:2592) UnhandledPromiseRejectionWarning: NoSuchElementError: no such element: Unable to locate element: {"method":"xpath","selector":"//input[@type='submit' and @value='Proceed']"}
(Session info: chrome=66.0.3359.181)
(Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.2.9200 x86_64)
at Object.checkLegacyResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\error.js:585:15)
at parseHttpResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:533:13)
at Executor.execute (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:468:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:2592) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 9)
(node:2592) UnhandledPromiseRejectionWarning: NoSuchElementError: no such element: Unable to locate element: {"method":"xpath","selector":"//input[@type='submit' and @value='Proceed']"}
(Session info: chrome=66.0.3359.181)
(Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.2.9200 x86_64)
at Object.checkLegacyResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\error.js:585:15)
at parseHttpResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:533:13)
at Executor.execute (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:468:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:2592) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 10)
(node:2592) UnhandledPromiseRejectionWarning: NoSuchElementError: no such element: Unable to locate element: {"method":"xpath","selector":"//a[text()='Logout' and @class='logoutbtn']"}
(Session info: chrome=66.0.3359.181)
(Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.2.9200 x86_64)
at Object.checkLegacyResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\error.js:585:15)
at parseHttpResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:533:13)
at Executor.execute (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:468:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:2592) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 11)
(node:2592) UnhandledPromiseRejectionWarning: NoSuchElementError: no such element: Unable to locate element: {"method":"xpath","selector":"//a[text()='Logout' and @class='logoutbtn']"}
(Session info: chrome=66.0.3359.181)
(Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.2.9200 x86_64)
at Object.checkLegacyResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\error.js:585:15)
at parseHttpResponse (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:533:13)
at Executor.execute (D:\Day_User\Rohit\Eclipse\Workspace\Mochatest\node_modules\selenium-webdriver\lib\http.js:468:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:2592) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 12)
npm ERR! Test failed.  See above for more details.
Let me know if anything is needed from my end.

I believe that selenium-webdriver/testing v4.0.0-alpha.1 removed these API.

Changes to testing/index
Since the promise manager has been removed, it is no longer necessary to wrap the Mocha test hooks;  instead, users can simply use async functions. The following have all been removed:
describe
before
beforeEach
after
afterEach
it

It's not a mocha issue.
I have no experience with selenium-webdriver/testing, but it may work if you use selenium-webdriver/testing 3.x.


Document {name} and {$root}

{name} is name of the resource
{$root} is the root path of the module
Both are evaluated in %IPM.ResourceProcessor.Abstract:%Evaluate()

Added the documentation in wiki page.


No good tutorial

There is no good starter tutorial on the net about Snap.
Things like template context variables, acid-state (database) usage, urls, etc.. are not clear how to use or where to stick them. The default/init site generated by Snap is confusing with three files: Application.hs, Main.hs, Site.hs - with no explanation of what file does what, and a bunch of weird looking code that does 'magic' (and uses symbols like [| ).
For a person just getting started with haskell I think it would be really useful to have a "for dummies" tutorial. And yes - it's possible, just look at Django docs.
Snap can have an advantage here, as no other framework (yesod or happstack) has a good beginner tutorial.

I'm quite interested in building such a thing. There actually are a few pretty good resources around, but they require a reasonable amount of google-fu to discover..
http://learnsnap.chromaticleaves.com
http://snapforbeginners.com
Then there's my own personal quite-wrong-in-places snap_notes for "let's get started with the basics of SNAP", which is a broken-down version of Ryan Trinkle's "webcast" about a URL-shortener. As @mightybyte points out, Haskell itself takes quite a while to get fully to grips with, and Snap assumes intermediate Haskell. This is quite a good reason that most of the people in IRC don't recommend you start with a web app - there's a huge learning curve.
http://www.genericoverlords.com/snap_notes
I'm actually quite interested in starting to build some resources for getting going with Snap from nothing (but done better than those notes there).


Feature Charts: Add Longhorn 1.2.7 Chart in 2.6.x

Longhorn has an upcoming release 1.2.7 so we need to add this new release in the feature charts along with the upcoming Rancher 2.6.x.
Probably need to make it OOB if need to release it earlier.
Add 1.2.7 LH chart in feature chart 2.6.x - Cluster Manager/Rancher Marketplace
cc @khushboo-rancher @yasker @MKlimuszka @deniseschannon @cchien816 @yangchiu @prachidamle @innobead
Related issue for 2.7.x: https://github.com/rancher/rancher/issues/39527

done.
verified new version live; installed on rancher prime for additional verification.


Name Manager

Hi @aloifran , could you add a description? You can link to the Figma and include a couple of piuctures.
Also mention the things that are not yet done.

I can't add a name if the list needs scrolling:

When you update a name, add a name or delete one the changes should be applied immediately to the workbook.
You just need to "emit" a "onChange" event and run a redraw request in the workbook. You can see how the borderPicker does it.


Non-Interactive Staking

A major re-work of the gilts pallet to now become NIS (non-interactive staking) pallet.

Allow partial thawing.
Enforce throttling for thawing.
Allow manual deficit funding.
Replace AdminOrigin for a target getter.
Introduce FundOrigin for automatic deficit funding.
Allow receipts to be transferred through nonfungibles trait API.
Introduce optional counterpart receipts via fungibles trait impl.
Replace some confusing terms.
Refactoring.
Additions to defensive traits.
Additions to per-things.

TODO

[x] Instead of MaxIntakeBids it should take MaxIntakeWeight.
[x] Benchmarks.
[x] Check if upgrade would need some initialisation.

Future

Consider using Scheduler instead of on_initialize.

@xlc @ggwpez grumbles should be addressed. Approvals appreciated :)

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2075942

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2077814

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2078278

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2078623

Just companions are missing, the other CI failures are unrelated.

Have some questions still regarding https://github.com/paritytech/substrate/pull/12610#discussion_r1026610306, also posted in the parity forum.

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2091715


Cannot contact discovery URL as string is not passed correctly.

Running this inside Kubernetes with KeyCloak. Have keycloak as an externally available service and pointing keycloak-proxy to that URL, however when supplying the URL with suffix ".well-known/openid-configuration" the service cannot reach the URL:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: keycloak-proxy
  namespace: proxy
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: keycloak-proxy
      annotations:
        repository: https://github.com/gambol99/keycloak-proxy
    spec:
      containers:
        - name: keycloak-proxy
          image: quay.io/gambol99/keycloak-proxy:v2.3.0
          imagePullPolicy: IfNotPresent
          ports:
          - containerPort: 8000
          args:
            - --client-id=test
            - --discovery-url=http://test.example.com/auth/realms/freeipa/.well-known/openid-configuration
            - --enable-default-deny=false
            - --enable-json-logging=true
            - --enable-logging=true
            # - --enable-request-id=true
            - --enable-security-filter=true
            - --http-only-cookie=true
            - --listen=:8000
            # - --preserve-host=true
            - --redirection-url=http://automatix-1-f4.ngci.lab.vce.com
            - --resources=uri=/*|roles=admin
            - --skip-client-id=true
            - --upstream-url=http://httpbin.http1:8000
            - --secure-cookie=false
            - --verbose=true

Like this the suffix ".well-known/openid-configuration" is ignored:
{"level":"info","ts":1536165905.8208709,"caller":"keycloak-proxy/server.go:682","msg":"attempting to retrieve configuration discovery url","url":"http://test.example.com/auth/realms/freeipa","timeout":"30s"}
{"level":"warn","ts":1536165905.8221016,"caller":"keycloak-proxy/server.go:688","msg":"failed to get provider configuration from discovery","error":"EOF"}

If I attempt to quote the string in single-quotes ('http://test.example.com/auth/realms/freeipa/.well-known/openid-configuration') then I get another error:
{"level":"warn","ts":1536165349.6460118,"caller":"keycloak-proxy/server.go:659","msg":"failed to get provider configuration from discovery","error":"parse \\'http://test.example.com/auth/realms/freeipa/.well-known/openid-configuration\\'/.well-known/openid-configuration: first path segment in URL cannot contain colon"}

Issue appears to be that keycloak-proxy wanted to add the suffix itself. Now issue is that keycloak-proxy is not reaching keycloak but everything else can. Closing this issue.