Fix incorrect webpage title on back button press (chrome bug)

cc @iwiznia since this bug is really bothering you 😄
Details
This is a workaround for a very annoying bug in the Chrome browser. It is a hack but I am not able to find and alternative and people will not stop complaining about this so it must be done???
Fixed Issues
$ https://github.com/Expensify/App/issues/8005
Tests (Web & Mobile Web Only)

Start a chat between User A and User B
Send a message from User B to User A while User A has the chat OUT OF VIEW
Verify the (1) appears in the document title
Navigate to the chat
Verify there is no count in the document title
Navigate back using the browser back button
Verify the count does not persist in the document title (note: there will be a brief flash of the count - but then it will stay hidden)

[ ] Verify that no errors appear in the JS console

PR Review Checklist

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] Any functional components have the displayName property
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

PR Reviewer Checklist
The reviewer will copy/paste it into a new comment and complete it after the author checklist is completed

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] iOS / native
[ ] Android / native
[ ] iOS / Safari
[ ] Android / Chrome
[ ] MacOS / Chrome
[ ] MacOS / Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] Any functional components have the displayName property
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

QA Steps

[ ] Verify that no errors appear in the JS console

Screenshots

Web
https://user-images.githubusercontent.com/32969087/193941594-ee48fe0b-2be2-4b2e-8aa7-abcf78c737f5.mp4
Mobile Web - Chrome
https://user-images.githubusercontent.com/32969087/193941632-b14d9f8f-af4b-450e-b0b3-b5060c784c8a.mp4
Mobile Web - Safari
https://user-images.githubusercontent.com/32969087/193943093-0bdbf050-5aaa-4d7a-a0ba-1b71f08df83e.mp4
Desktop
N/A since there is no document.title on this platform
iOS
N/A since there is no document.title on this platform
Android
N/A since there is no document.title on this platform

I think we'll need someone to post the completed checklist before we can merge.

Tested on Web & Desktop 👍

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] Any functional components have the displayName property
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

🤷♂  everything is checked and was good to merge before I clicked the merge button. Can see there are like 4 checklist jobs. Not really sure what is up with that.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @marcaaron in version: 1.2.13-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @yuwenmemon in version: 1.2.13-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Improve package usage validation for internal builds: filter out source-built nupkgs from smoke-test-prereqs

Currently, in internal builds, we disable this package filtering:
https://github.com/dotnet/source-build/blob/ea2042c6a31b4a83e136505e6cb3010b461da631/eng/SourceBuild.Tarball.targets#L236-L241
We should actually apply the filtering all the time, and fix tarball smoke-test to work with the internal feeds. This simulates how the packages will go public on release day. The filtering is actually valuable for a specific form of validation (https://github.com/dotnet/source-build/issues/1677#issuecomment-666607299):

There is value in eliminating these in public builds to ensure that it works with the public nuget packages.  The way packages are captured for internal builds assumes that if they're downloaded by smoke-tests, then they are from the official build, but they may be from source-build.

Triage notes:
I think I was wrong again with this issue, we actually need a third style of test for testing "online" but with smoke-test-prereqs saved in case the internal feeds can't be authenticated against. @dagood to open new issue.


Remove cmdrunner package; comment fixes

Went through the claimhelper package and made sure the func comments matched the actual func names.
Removed the cmdrunner package and corresponding tests because it appears unused.
Removed cmdJoin function and corresponding test.

Fixing the CI in #319


Add Integration Test

This adds integration tests for the multiboot2 crate and the multiboot2-header crate.

I'm very thankful for your contribution, @YtvwlD - now, I can write a much better integration test by constructing a real MBI :)

Oh cool. The chainloader is an interesting idea.


System.Drawing is missing

While working on https://github.com/dotnet/corefx/pull/21707 I realised that System.Drawing seems to be missing from this repository.
It does seem to be available in http://referencesource.microsoft.com though.

It's been three years. Is there any progress on this?


Installation instructions outdated

I tried installing rustfmt, but the installation instructions in the README.md seem outdated and I couldn't figure out how to install rustfmt correctly.
I tried:
$ cargo install rustfmt
error: binary `cargo-fmt` already exists in destination
binary `rustfmt` already exists in destination
Add --force to overwrite

This is the first time I tried using rustfmt. Is is normally preinstalled?
(I also tried installing with --force)
$ cargo fmt
error: 'cargo-fmt' is not installed for the toolchain 'stable-x86_64-unknown-linux-gnu'
To install, run `rustup component add rustfmt`
$ rustup component add rustfmt
error: toolchain 'stable-x86_64-unknown-linux-gnu' does not contain component 'rustfmt' for target 'x86_64-unknown-linux-gnu'

At least the error message tried ^^
$ rustup install nightly
$ cargo +nightly install --force rustfmt
$ cargo +nightly fmt
This version of rustfmt is deprecated. Use rustfmt-nightly. Use --force to run deprecated rustfmt.

Aparrently, I installed the wrong version. But:
$ rustup component add rustfmt --toolchain nightly
info: component 'rustfmt' for target 'x86_64-unknown-linux-gnu' is up to date

My setup:
Linux (Ubuntu 18.04)
rustup 1.16.0 (beab5ac2b 2018-12-06)
rustc 1.31.1 (b6c32da9b 2018-12-18)
cargo 1.31.0 (339d9f9c8 2018-11-16)

Can someone correct the installation instructions in the README.md? Thank you ^^

Aparrently the right command was
cargo +nightly install --force rustfmt-nightly

And it can be used with cargo fmt, the +nightly isn't necessary.


Add utility for concatenating null flags

Adds a class managing concatenation of bits.  There is a special case
for all ones, where the bitmap comes out as nullptr. This corresponds
to the all non-null case in readers.
Used for Parquet and Alpha, where a read may span multiple encoded
runs, each with its own nulls.

Thank you. Edited the files. Note ‘//’ for non-documentation comments, e.g. class private.

Thank you. Could you accept the diff?
reset() is needed because this is an inline member of a bigger thing that keeps reusing the same buffer where can. Reset is better than placement new.


安装 kubeadm

CentOS、RHEL 或 Fedora 没有安装命令?

please try the support channels:
https://github.com/kubernetes/kubernetes/blob/master/SUPPORT.md
/close

please try the support channels:
https://github.com/kubernetes/kubernetes/blob/master/SUPPORT.md
/close


Question about Iterative Modified Gram-Schimidt

Thank you for open-sourcing this wonderful repo!
I am currently trying the evaluation script, and I've noticed something I'd like to understand better. When evaluating new poses, the predicted axes are processed by Iterative Modified Gram-Schimidtt to get a legal rotation matrix:
https://github.com/HeegerGao/RiEMann/blob/95a3dfa6c3bd80945032118fa7c344fbe232aa44/scripts/testing/infer.py#L59
I noticed that you transposed the matrix before input to modified_gram_schmidt() but the output is not transposed back. Could you provide some insight into the reasoning behind not transposing the output?

Hello Zhengbang,
Thanks for your interest in RiEMann.
The variable output_direction in line 59 is in the shape of [1, 9], which can also be seen as [$v_1^T$, $v_2^T$, $v_3^T$], where a legal rotation matrix is $R=[v_1, v_2, v_3]$. Thus, in line 59, we first reshape it from [1, 9] to the shape [3, 3], then we transpose it to get a legal rotation matrix, and finally, we send it through the modified_gram_schmidt function.
The output of modified_gram_schmidt is already a legal rotation matrix, so we do not need to transpose it again.

Thank you for your reply!


Plugin
device_info_plus
Use case
hope get Serial
Proposal
Serial

Can I work on this issue?

Hi! Can I work on this issue?

can I work on this issue?

On iOS Apple forbids to get unique device identifiers like serial number. Google goes the same way, so it makes no sense in adding this functionality, even if it is planned to be used on old versions of iOS or Android.


dataconverter does not correctly pick up --generate template flag

The --generate-template flag of pynxtools/dataconverter seems to not be working for me at the moment. If I pass that flag, the template is not printed to the console.
Probably comes from changes to the logger in https://github.com/FAIRmat-NFDI/pynxtools/pull/191. This seems to be related to the setting of the logger level, see here.
Quick fix: Change to logger.error(template) in https://github.com/FAIRmat-NFDI/pynxtools/blob/c4d1b9cf8fdabe1a9d49ec54b09a78e5b773e28b/pynxtools/dataconverter/convert.py#L248
We should check that all other flags (like --fair, --undocumented) are still picked up correctly.
@domna @sherjeelshabih @RubelMozumder

I had a quick look. It seems some other code is setting the logging level back to warning.

See the linked PR, there's some explanation why this might happen. I am not an expert on logging though, so would be nice if you could have a look.


WIP: Breakpoint UI

While this implementation basically works, there's still a lot to figure out:

[x] julia-client shouldn't need to maintain a stack of set breakpoints; it'd probably be best to only have that in julia so there's less potential for both sets of breakpoints to diverge
[x] Breakpoints should probably be unset when their marker changes (i.e. line inserted above the breakpoint or soemthing like that). Maybe re-set them at the new location afterwards?
[x] Only saved files should have their breakpoints actually applied, because that is the state Gallium sees. Maybe we should save files automatically when setting a breakpoint or something like that (which would require separate stacks, now that I think about it...)?
[ ] Conditional breakpoints.
[ ] Breakpoint pane.
[ ] Other stuff I didn't yet think about, but this will be kinda tricky to get right I think.

Just for reference (need to get those if you want to try this branch):

https://github.com/JunoLab/Atom.jl/tree/sp/breakpoints
https://github.com/JunoLab/atom-ink/tree/sp/breakpoints

Any idea, why the Travis CI check fails?

Because it isn't configured correctly -- see #236 for progress on that.

I think you make some good points, and at the same time this will take some thought and iteration to work out in detail, so just getting something that does the job can be the priority.

julia-client shouldn't need to maintain a stack of set breakpoints; it'd probably be best to only have that in julia so there's less potential for both sets of breakpoints to diverge

I don't necessarily agree with this. For example, you can imagine a use case where we run a one-shot script with a new julia instance each time – I think setting the breakpoints on boot makes sense there. Though in future we'll probably have the debugger itself in its own process which will achieve the same effect.

Yeah, this is definitely not easy to get right. Also, I haven't really used debuggers yet, so I'd appreciate any input regarding expected behaviour and such.

julia-client shouldn't need to maintain a stack of set breakpoints; it'd probably be best to only have that in julia so there's less potential for both sets of breakpoints to diverge

I don't necessarily agree with this. For example, you can imagine a use case where we run a one-shot script with a new julia instance each time – I think setting the breakpoints on boot makes sense there. Though in future we'll probably have the debugger itself in its own process which will achieve the same effect.

Yup, I don't agree with that either now that I've been thinking about it for a bit :D

Active breakpoint:

Inactive breakpoint:

It'd be great if someone could play around with this for a bit -- I think this should work well as is, but am not totally sure. Also, I'd rather implement the remaining two items (debugger pane item and conditional breakpoints) in a separate PR, mostly because I'm not sure yet how to best implement that.

The code here is looking good, with the minor downside that I can't get it to work :)
I have a separate set of branches (omm/breakpoints) where I'm going to strip this down a bit to get the minimal thing working and fairly robust. There are some good ideas in the synchronisation code and stuff which I definitely don't want to throw out, but also some hard questions to answer. It's ok if in our first pass we simply ask users to be careful, and apply the extras later on.
To outline the issue, the sync problem is particularly tricky because (a) the code in the buffer, (b) the code on disk and (c) the loaded code in Julia can all get out of sync. The current approaches address a!=b well but not so much a!=c. I think we need to see more of how Gallium behaves with no sync handling in order to figure out the tradeoffs involved here.

Are you on gallium master? If not, it's not possible to remove source breakpoints, which kinda hampers the toggleability a bit :D
Apart from that: a!=b isn't actually a problem, only a!=c -- and I apparently thought b==c was true, so I wrote code that handled that case. If were talking about source breakpoints only, then Gallium's behaviour for unsynched breakpoints is straightforward -- it halts execution at the wrong line. Imho it's reasonable to say "if Gallium doesn't place you at your breakpoint, make sure to save the file and reload your code", but maybe we could find some way to check for a==c (maybe something like setting breakpoints on the method definition nearest the breakpoint and then stepping down ourselves?). Will have to think about that a bit...
All that said: For the little bit I used this implementation, it works pretty well for Base code and mostly well for actively developed code, but YMMV.

Ah, I better grab Gallium master then – that's at least part of the issue. I think that was exposing a bug in breakpoint removal as well.
I mention a because I know that ASTInterpreter loads code from disk at times; but I'm not sure if that's only for display in the repl, in which case it doesn't affect us. I agree we can probably do something smarter about this (perhaps keeping track of where BPs originated?), but we'll have to be really careful not to play whack-a-mole with confusing cases – being consistently wrong might end up being the lesser evil. (But I also agree we can tell people to be wary and figure that out later – as this is working well we should use it ASAP.)
I also want to fix the loading indicator; if it's always on while in debug mode, it's not particularly useful.

The UI parts of this PR are first class – I really like the way the breakpoint registry is set up, among other things.
For now, I've simplified the backend parts quite a lot, in particular the approach to syncing breakpoints. I've no doubt that we'll want to do smarter things eventually, but with the debugger itself in a very beta stage I think it's important to keep things simple. For now, setting a breakpoint is exactly like calling Gallium.breakpoint(file, line), which will make it easier to track down the first wave of issues.

Awesome, thanks for fixing this up -- I'll have a look at the new logic as soon as I can.


Mark --jax_xla_backend as deprecated.

cc @jakevdp

+1 to warnings. I'm hoping to get a few "alpha testers" to confirm this is a reasonable API, and then I can add warnings once we're more confident we won't need to make further changes.


[Analytics] Make ‘sign-up/connect with email/facebook/twitter’ -> ‘created account’ consistent.

Fixes https://github.com/artsy/eigen/issues/1123#issuecomment-198306933.

Makes perfect sense, thank you!

Should these provide a context dictionary?

Ideally we would want to have a single tapped sign up event that has properties around how the sign up was created (email, facebook, twitter). This works, too, for now -- it is on my team's radar to revisit all major flows (eg account creation, inquiry etc.) and make sure eventing is instrumented with a clear pattern that translates between apps, so we can do that pass later, too. If not too much trouble, we could do this at this pass.
Additionally, we could add context_type: [sign up splash, follow, bell etc.] but I think this might require more work on our end to sketch out all possible contexts.

Also not sure if more thorough event revamp is necessary for this round if we are moving through with obligatory sign ups.

Good point, in which case I'd opt for deferring more elaborate changes until the new onboarding is in place.

:+1:


Cannot build dependency by rebar

After I add cqerl in rebar.config in my project I am not able to build dependency.
I have following error:
../deps/cqerl/include/cqerl.hrl:61: type map() undefined
I have same result for master branch and v1.0 tag.
Regards,
Szymon

I am using E16B03

Probably you meant maps:map() there?

Actually the correct type is map(). The problem you're hitting is that maps don't exist in R16. There's code to work around this in most places, but evidently that bit was missed. Probably the simplest workaround for your case is just to define map() to be something innocuous. Unfortunately Erlang lacks version macros or something similar that might make this easy to ifdef our way around.

Yes, you are right here.
I will do as you suggest.


MongoDB 3.x

Hey,
Is Mongoskin ready for MongoDB 3.x?
I've seen that it requires the 1.4.18 native module.
Thanks,
Philmod

So mongoskin 1.4.13 should be compatible with any ~1.4 version of the mongodb npm module. Let me know if you run into any issues with that.

From what I can tell Mongoskin isn't compatible with MongoDB Native Driver V2 and hence MongoDB V3. For a start it fails in admin.js var Admin = require('mongodb').Admin;. I haven't looked beyond this.
IMHO it is easier and better to develop directly for the Native driver, especially seeing the number of pending issues with MongoSkin.

Nope, latest mongodb driver ~1.4 also supports mongodb server 3.0.

To use Authentication with MongoDB V3 you need to use MongoDB Native Driver V2. ie. You can't access a Mongo V3 DB which uses authentication with the ~1.4 driver. My app uses authentication and therefore Mongoskin is a non-starter. FYI I am using agenda.js which uses Mongoskin and because of this issue agenda.js breaks. I'm currently refactoring agenda.js so it works directly with the MongoDB V2 driver.

What authentication mechanism are you using and what sort of error are you getting? Node driver >= 1.4.13 supports SCRAM-SHA-1, so there should be no issue using auth with mongodb 3.0

When I passed authentication details in the url to agenda, which just passes them on to Mongoskin I got an error saying authentication failed and then agenda or mongoshell (not sure which) crashed with an exception. I am using the default SCRAM-SHA1 authentication and the new Wiredtiger DB engine.

I am also having issues ("auth failed") with the current mongoskin (through monq) when connecting to MongoDB 3.0 with SCRAM-SHA-1 authentication.

@dhritzkiv I think that mongoskin does auth against the db you are using with it. If instead you have the auth user specified in the admin db vs. the db you are using with mongoskin, then auth will fail. HTH.

@nevf Thanks for the tip. I'll check this out.

any updates on supporting the 2.1.x driver?

I need to use MongoDB 3.X apis like insertMany, bulk operations etc. Are there any plan to support these features in mongoskin? if yes, by when can we expect it?

Did anyone look into @thucnc 's fix?  That would be super cool if this worked and got merged.


Command system error with quotes

Factorio version
Version number: 0.17.46
Scenario version
Version number: 5.6.0
Bug description
Command argmuent parse does not handle quotes correcly all the time; example given is using the role assign function with /interface
Reproduction method
Steps to reproduce the behavior:

/interface Roles.assign_player("Cooldude2606",{"Senior Administrator","Moderator","Donator"})
Result in log: Roles.assign_player(\"Cooldude2606\",{\"Senior_Administrator\",\"Moderator\",\"Donator\"})

Expected behavior
The command parse needs to be able to haddle quotes corectly and insert spaces back where they are required.

A small fix has been made to allow this instance of the bug to work; other cases may still be broken.
See v5.7.0

No new errors have shown up so this bug is assumed to be fixed.

This issue has resurfaced with the following commands:
/interface game.print(serpent.line( game.json_to_table('{"foo": [1,2,3], "bar": [1,2,3]}') ))
becomes
{
  "player_name": "Cooldude2606",
  "command_name": "interface",
  "comment": "Success",
  "params": ["game.print(serpent.line( game.json_to_table('{\"foo\": [1,2,3],_\"bar\": [1,2,3]}') ))"],
  "raw": "game.print(serpent.line( game.json_to_table('{\"foo\": [1,2,3],_\"bar\": [1,2,3]}') ))"
}

error is with the _ being added between [1,2,3], and \"bar\"

PR which fixed this issue has been merged. Closing this issue.


Resolving SubmitHashes Defect

Defect:
Failed hash submissions to Chainpoint Network
Discovered Reason:
Request body in call to submit hashes to Chainpoint Network consisted of an array with empty values alongside 32byte hashes.
Fix:
Improperly initializing array of hashes to submit to the length of hashes provided to the SubmitHashes() method, and later appending additional items to this array.
Steps to Test:
Run Goldmine using latest version of this Package and observe that Chainpoint Proofs are being generated and retrieved with Goldmine.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


did you tried float16 in tensor2tensor?

hi guys,
did you tried float16 in tensor2tensor ? as [https://arxiv.org/abs/1806.00187](the new paper) said , it will speed up the training .
but I think tensor2tensor now does not support float16 in NVIDIA gpu, is that right ?
or did you guys try some work like this ?Thx.

Currently, float16 is only supported on tpus: https://github.com/tensorflow/tensor2tensor/blob/6969fab42200a7da11bc40c9537b76b0a204b46a/tensor2tensor/layers/common_hparams.py#L233

But, it may be worth a test on Volta gpus, which have tensor cores supporting multiplication in FP16 and accumulation in FP32 precision.


iOS Foreground Notifications stop working after app restart

Hi,
I set up APNS and background + foreground notifications started to work both :)
After a while, when the app is in background or the app is killed from task manager manually in iOS, if I restart the app I don't get any foreground notifications anymore. I have to deinstall and install the app from scratch again to receive foreground notifications again.
Background notifications are still working. But foreground is not. This happens only in the iOS variant. :(
Does anybody have any ideas?
Best,
Stefan

If I revoke the permission in iOS Settings, my app tries to grant permission again and the foreground notifications are received again. But the next time I kill the app, the game starts again.

[inc.together.social] Received remote notification request D33B-F206 [ hasAlertContent: 1, hasSound: 0 hasBadge: 0 hasContentAvailable: 0 hasMutableContent: 0 ]
Seems taht the notification is received, but it is not shown anymore.

Can you confirm you are specifying "notification_foreground": "true" in the FCM message payload's data section as outlined in the the documentation?
If so, please can you test using the example project and its built-in FCM client and confirm whether you can reproduce the issue in this known codebase.
For example:
npm run-script send -- --token="<your_device_token>" --message=notification.json

Since notification.json contains the required key for foreground notifications.

Closed due to no response

I found the solution. The firebasex plugin clashes with the local-notifications plugin from ionic. If you enable both of this cordova plugins in an Ionic project, you have the explained buggy behaviour. I solved it by removing the local Notificafions plugin. I tried this with ionic 4 and 5. @dpa99c


Screen based panel width is inconvenient when using differen monitors

Describe the bug
When using different monitors (e.g. laptop used alone and with external monitor) the panel width changes if the monitors don't use the same resolution. Depending on resolution difference and settings this can make the panel unusable.
How To Reproduce

Configure the panel width on a bigger/smaller external monitor.
Unplug the external monitor thus Gnome switching the main screen.
The panel is now to small or to wide

Versions
aveau.dev/schemas list-recursively org.gnome.shell.extensions.clipboard-history
GNOME Shell 41.4
GCH   Version: 9
org.gnome.shell.extensions.clipboard-history next-entry @as []
org.gnome.shell.extensions.clipboard-history disable-down-arrow true
org.gnome.shell.extensions.clipboard-history history-size 1000
org.gnome.shell.extensions.clipboard-history cache-size 100
org.gnome.shell.extensions.clipboard-history confirm-clear true
org.gnome.shell.extensions.clipboard-history strip-text true
org.gnome.shell.extensions.clipboard-history display-mode 0
org.gnome.shell.extensions.clipboard-history topbar-preview-size 10
org.gnome.shell.extensions.clipboard-history clear-history @as []
org.gnome.shell.extensions.clipboard-history private-mode false
org.gnome.shell.extensions.clipboard-history cache-only-favorites false
org.gnome.shell.extensions.clipboard-history process-primary-selection false
org.gnome.shell.extensions.clipboard-history paste-on-selection true
org.gnome.shell.extensions.clipboard-history notify-on-copy false
org.gnome.shell.extensions.clipboard-history toggle-menu ['<Super><Shift>V']
org.gnome.shell.extensions.clipboard-history move-item-first true
org.gnome.shell.extensions.clipboard-history window-width-percentage 20
org.gnome.shell.extensions.clipboard-history enable-keybindings true
org.gnome.shell.extensions.clipboard-history toggle-private-mode ['<Super><Shift>P']
org.gnome.shell.extensions.clipboard-history prev-entry @as []

Steps to repro
Panel with 10% width on external monitor (2560x1440

Panel after unplugging external monitor, now in internal one (full HD)

Additional context
The issue seems only occur when unplugging the monitor and thus Gnome Shell auto-switching. If I change manually the main screen in Gnome settings the panel keeps somehow a sane width.

If you reopen the panel, does it fix itself?

No, I can open and close it and it stays the same.
Also I didn't have the panel open when unplugging the cable and auto-switching monitors.

Ok, thanks. I'm probably using the wrong monitor.

Turns out the API I was using returned a composite width of all the monitors stitched together (so waaaay too many pixels).

Just released, should be fixed.

Turns out the API I was using returned a composite width of all the monitors stitched together (so waaaay too many pixels).

Ah this also explains why setting the primary screen didn't triggered the issue.

Just released, should be fixed.

Works perfectly for me. Thanks for the quick fix!


Why the seed is 14159265?

This seed seems pretty weird to me. Why setting the seed to this specific number?

Digits of pi after the decimal place.
I remember reading somewhere that it is better to set a large seed so I set it to that instead of 0.
It also follows from my previous work MiVOS: https://github.com/hkchengrex/Mask-Propagation/blob/ec9309f04ae3c98edb2eb5675c937a699d80006f/train.py#L26

I see.

The "large seed" claim is from here: https://pytorch.org/docs/1.10/generated/torch.Generator.html#torch.Generator.manual_seed
I don't know why though.

FYI, https://discuss.pytorch.org/t/torch-generator-manual-seed-it-is-recommended-to-set-a-large-seed-why/120819


Username and platform not available for some users

Hi, I am opening this issue by request from @LuiggiTenorioK. In some cases (such as all of my DestinE experiments), the user and platform are not shown in the corresponding fields in the card, but dashes are displayed instead (see below example of experiment a20i)

Many thanks!

Thanks for reporting this issue @ialsina. The API/GUI has a background process that gets the user and platform information and stores them in the DB to make it searchable on the home page. It seems that this process has been failing since December 15th more or less.
Possible causes could be related to a lack of file system permissions or exceeding memory limits. Unfortunately, I cannot debug it since I don't have access to the logs of that API instances but I think @Nortamo can help us track it down.
From my side, I'll try to fix it by running only the background process on our shared VM.

@Nortamo is leaving the project, @LuiggiTenorioK . Maybe @tiggi or @JuhaTonttila can help (Juha is replacing Henrik, Luiggi).

I'll take a look... but do we have any kind of hint what this background system is named?


Updates to Javagen

Adds a new configuration include-read-only-in-constructor-args to support cases where read-only properties were previously included in constructors when the property was also required.
Changes a few code patterns when generating stream style serialization.

I assume this is mostly for backward compatible? User likely does not need read-only property in ctor, if the model class is used as input?
I am not sure why CI fails.

Yeah, the new configuration is for backwards compatibility when a library was generating with
required-fields-as-ctor-args: true
and the Swagger defined required, read-only properties. Without this new configuration regenerating would lose a constructor argument and if that was exposed as public API it would be breaking.
I'll follow-up with the CI failures shortly.


item_order feature

to #38
use keep_item_order to save struc field order and the serialize will pick it up.
@larshp ready for test, though I will add some docs and maybe refactor some stuff. But the feature is ready and covered with UTs.
P.S. I hope 2 extra table keys are ok for older system. 731 seems to support it ...

@larshp abaplint false negative ?
Not the most canonical implementation ... but sap compiles it without warnings ...

@larshp abaplint false negative ?
Not the most canonical implementation ... but sap compiles it without warnings ...

yea, its probably a bug, will have a look, might be similar/identical to https://github.com/abaplint/abaplint/issues/1561

yea, its probably a bug, will have a look, might be similar/identical to https://github.com/abaplint/abaplint/issues/1561

https://github.com/abaplint/abaplint/issues/1661 opened

https://github.com/abaplint/abaplint/issues/1661 opened

try again, 2.63.16 published

try again, 2.63.16 published

:+1: works now!

:+1: works now!

i'm lazy to do refactoring ... just added docs and merging, it works

i'm lazy to do refactoring ... just added docs and merging, it works


Contact section html code with css code

fixes #5 email of our website is included as well as the form suggested by @jeanne-strg our social media are also linked

Putting icons to link our socials is mindful for easy access

Its also good that making the color of icons still related to our website.

Should i merge it now?

Yes, you can. No problem.


cold mail | resume tailoring tools | cover letter | fixed chatbot related errors

…ated errors
What does this PR do?

Fixes #42
Fixes #43
Fixes #40
Fixes #41
Fixed chatbot errors

Type of change

Bug fix (non-breaking change which fixes an issue)
Chore (refactoring code, technical debt, workflow improvements)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

How should this be tested?

[ ] Test A
[ ] Test B

Mandatory Tasks

[ ] Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

Can you the picture and video @sezallagwal

@iamkanhaiyakumar

@sezallagwal  Please resolve the conflict in below specified file
app/(data)/Template.tsx

@sezallagwal great!!


The presets tabs export as the name "Preset 1" instead of the name of the input

Current Behavior

The presets tabs export files as the name "Preset 1" instead of the name of the input
Expected Behavior
A correct naming of the exported files
Steps To Reproduce

create a cube
add a preset and name it "toto"
export it via the export button at the botton

It seems that the files are exported with the name "Preset 1" instead of "toto"
Environment
- OS: win10
- Blender: 3.1
- glTF-Blender-IO-MSFS: 1.1.6

Anything else?
No response

That is a workaround, but the file naming should match the name specified by the user. Will fix this soon

well, the name here is actually pretty useless.
The base idea was to use a name to identify a group of presets like it is done in 3dsmax

You can see that even in this plane, made by the internal Asobo team the name of the preset is useless
We could consider removing it in favour of a name for a group of presets


Allow use of secret files.

This PR will add the ability to use secrets instead of having environment variables contain secret information.
For example get_config("consumer_key") will first lookup to see if consumer_key is in the environment if so then return it.
Otherwise if key consumer_key_file exists we will read the files content and return it.
Otherwise we will search /run/secrets/consumer_key and /var/openfaas/secrets/consumer_key and if any of them exist we will return the files content.
If all these fail then the second argument to get_config is returned and by default that is None
p.s I'm not a Python developer so this may be way off.
fixes #3

Hi @bweston92 please can you sign off this commit?
How have you tested the change?
Alex

Sorry I can write tests if you want but I don't know OpenFaas to test it.

Thanks for signing-off the commit. FYI this project is licensed MIT and follows the OpenFaaS contribution process.

Should be relatively straight-forward to test. It will help your PR get merged as I don't have time to do this any time soon (and I can't put untested code onto the server, how do we know it works?).
Alex

Please ask on Slack if you need help getting a Twitter API token etc.

Testing:

Deploy OpenFaaS

Setup a testing Patreon page

Setup a Twitter account and get your access key / secret

Create your secrets

Build and deploy the code from your fork

Now trigger a test event from Patreon and check that the Tweet appears on the test account.

closing until I can find time to test


chore: first pass at cypress e2e tests

Some of these files were stubbed out by cypress, thinking of maybe adding some more tests as well, wanted to see how it runs in travis :D

@benjchristensen it does not, but the pre-push hook took care of this. There are a bunch of linting/prettier fixes that need to be added in a seperate PR it looks like.


New lines with matching fields will fail

Take the case of two CSVS:
A
organization_name,website,location,phone_number,email
"Foo's Bar", example.com, "Detroit, MI", ,

B
organization_name,website,location,phone_number,email
"Foo's Bar", example.com<EMAIL_ADDRESS>
Both imports A and B are equally important. Unfortunately, B will fail because the row's import is saved in a transaction and Foo's Bar is invalid, since it already exists.
See https://github.com/artsy/bearden/pull/117 for a failing test.

Is this being closed because it was fixed?

Looks like this was mistakenly closed - reopening!

@gnilekaw Is work on this still ongoing?

We talked about this briefly in the planning meeting. We're not currently working on it. We'd like to hold off fixing it unless there's a distinct problem from users.

Yes I'm fine with the stopgap we discussed at the planning meeting—there will be an error row in the errors CSV, and then we can just delete the offending duplicate field.

I would like to hijack this issue and transform it to the following:
During Import, ignore uniqueness validation errors on Organization Name
When we import a list and that list has a row with a matching website, we will fail the whole row if the Organization Name matches an existing name for the Organization. We do that because there is a uniqueness constraint on OrganizationName. What I propose is that we ignore that specific error during import - we simply throw out the organization name info and do not fail the whole row.
Given the scenario in the original post above, we pretend that this:
organization_name,website,location,phone_number,email
"Foo's Bar", example.com<EMAIL_ADDRESS>
Is really this:
organization_name,website,location,phone_number,email
, example.com<EMAIL_ADDRESS>
With that exception in place, I think we'll deal with the majority of errors around two lists having the same organization. It would satisfy the original case for this issue but wouldn't go too far and let junk data in.
I looked through the rest of the Rankables and only Website also had the uniquness constraint, so I think this is as far as we have to take this exception.
Thoughts?

Sounds good. Looks like there aren't really other uniqueness validators that will fail. https://github.com/artsy/bearden/search?utf8=✓&q=uniqueness&type= So we won't be in a situation where organization_name is just one of several fields that could fail in the same way.  I can imagine validators for email failing when there's no @ but in that case the whole row should fail!

@gnilekaw cool, we're on the same page then! 👍
@madeleineb if you're good with this, then I'll get started on it.

After a couple conversations with @madeleineb and @gnilekaw, we have decided to just remove the uniqueness constraint on OrganizationName. None of the other Rankables have it - we just use the rank of the source of the data to determine a winner.
I'll get a commit in that does this.


Consolidate blob upload, submit methods

Fixes https://github.com/microsoft/qdk-python/issues/83.
Refactored Job and added generic blob upload/submit methods.
@anpaz Solver.submit can optionally be refactored further if we are OK with deprecating Problem.upload(), it would look something like this:
if isinstance (problem, Problem):
    # Upload problem to container storage
    blob = problem.to_blob(compress=compress)
    job = Job.from_blob(
        workspace=self.workspace,
        name=problem.name,
        target=self.target,
        blob=blob,
        blob_name="inputData",
        encoding="gzip" if compress else ""
    )
    job.submit()

CC @vxfield @frtibble
we can do that in this PR or a follow up PR later. LMK what you think.

@anpaz, as mentioned in https://github.com/microsoft/qdk-python/issues/83 I wanted to propose to move the submit() logic to Workspace, we can do that in a follow up PR.

Updated base to feature branch which we can merge to main once we align on design details.

            self.workspace,

Instead of calling upload, I would call the from_input_data

Refers to: azure-quantum/azure/quantum/optimization/solvers.py:108 in e883fe4. [](commit_id = e883fe4d62ad1589d972d659a430daef0440ca7f, deletion_comment = False)


Update PULL_REQEST_TEMPLATE.md

[X] I have read the contributing guidelines, and I agree with the Code of Conduct.
[X] Have you checked that there aren't other open pull requests for the same changes?
[X] Have you tested that the committed code can be executed without errors?
[X] This PR is not composed of garbage changes used to farm GitHub activity to enter potential Crypto AirDrops.
Any user suspected of farming GitHub activity with crypto purposes will get banned. Submitting broken code wastes the contributors' time, who have to spend their free time reviewing, fixing, and testing code that does not even compile breaks other features, or does not introduce any useful changes. Thank you for your understanding.

Change the text provided by the user in the "optionally, explain here about the committed code" sentence font size from heading to normal.

Closes #XXXX

Relates to #XXXX

But you are editing a comment. I have tested the changes and they change nothing

Also, Why is there so many commit history?

But you are editing a comment. I have tested the changes and they change nothing

I meant in PULL_REQUEST_TEMPLATE.md

Also, Why is there so much commit history?

Since I reverted a PR, actually I don't know.

Also, Why is there so much commit history?

Since I reverted a PR, actually I don't know.

I will try to change that.

Please open a new PR with the changes

PR moved from #2605 to #2607.


conda mambabuild does not forward arguments to conda build

As the title says, e.g. --no-test is not forwarded to conda build, and thus tests are still executed although they shouldn't.

I think this is fixed, again, with 0.4.2. sorry about that!

@wolfv implemented like this it will still only handle one recipe, in contrast to what the help text suggests and conda build can do

Sorry

No problem! A quick workaround would be passing whole config.recipe not just config.recipe[0] to api.build(…) (not api.test(…) tho). But still I wonder if the 're-implementing parsing/handling logic' is even needed on the mambabuild-side, when apparently monkeypatching the solver is enough to get the desired result (fast solves with otherwise conda-build)…


Consider adding a license

I know we already spoke about this but I wanted to make another issue to remind you and because I'm not using Github enough.

Fine!

I don't like that one. Can you please choose a different one? Yeah thanks in advance.

This is why we can't have nice things...


Develop login fix

Compare to my closed PR #135

Looks almost the same. Have I just wasted my time?


Make sure djangosaml2 works in csp-enabled applications too (fix #391)

See #391: Iff Django-applications use Content-Security-Policy to increase security (or just to tick boxes of automated code checkers), SAML2 with POST-Bindings tend to have a hard time: POST-Bindings typically render a simple HTML-Page, consisting of a form with hidden fields, a submit-button and an onload to trigger submitting.
Currently, users can either bend their application-wide Policies to allow unsafe-inline code and form actions to any https-url, but for security reasons this should be avoided. This PR detects if django-csp is installed and uses its decorators to add specific allowances for the POST-Bindings.
Note that this requires the IdP to use https, but imho this should not break any legitimate use cases.

Good catch
we need other three things in this PR:

requirements update here: https://github.com/IdentityPython/djangosaml2/blob/master/setup.py#L66
version set to 1.9.0 here: https://github.com/IdentityPython/djangosaml2/blob/master/setup.py#L30
security considerations in the docs, decide to resuse a preexisting section or create a new one for this scope, here: https://github.com/IdentityPython/djangosaml2/tree/master/docs/source/contents

I drafted a security considerations page, but more help is greatly appreciated regarding format and content. I also bumped to Version 1.9.0 as instructed, but did not add the requirement: In my opinion, django-csp is no requirement, as we will simply ignore if it is not found (hence the try-block).
Imho it is more an extension, but adding it as an optional dependency would not be good either: People could be tricked into installing djangosaml2[csp] and believing we would send Content-Security-Policy Headers, but django-csp requires configuration in the application first, so all we do is being compliant with django-csp if it is found.

@prauscher I made suggestion to help this PR to get merged soon
please accept my suggestion with the github UI, then request to me again the review.
Can I ask you to include a setup instruction in the documentation about django-csp?
I want to guide the users in the best setup

@peppelinux Sorry, only now realized that I forgot to push my latest changes, which include the warning.
This also introduced links to the django-csp install and config page - I do not feel confident enough to provide own explanations, but I think that should work :)


more explicit handling of keys

Mostly cosmetic changes to be more explicit in the logic.
Also cast keys as strings to check if they match
Add some asserts before tryOpen to make sure we got it correct.

nicee
On Sat, Feb 4, 2017 at 11:21 AM Joe Hand<EMAIL_ADDRESS>wrote:

Merged #94 https://github.com/datproject/dat-node/pull/94.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/datproject/dat-node/pull/94#event-949213228, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACWlegszZch6XVq4Z7nj89fS5We9DfATks5rZM-4gaJpZM4L3NkU
.


[docs] Add notebooks as tutorials to the docsite

Issue and/or context:
https://github.com/single-cell-data/TileDB-SOMA/issues/1017
Changes:
Add notebooks as tutorials
Notes for Reviewer:

Codecov Report
Patch coverage has no change and project coverage change: +28.64 :tada:

Comparison is base (b0b91f6) 62.55% compared to head (a0427ab) 91.20%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1140       +/-   ##
===========================================
+ Coverage   62.55%   91.20%   +28.64%
===========================================
  Files          88       30       -58
  Lines        6198     2296     -3902
===========================================
- Hits         3877     2094     -1783
+ Misses       2321      202     -2119

Flag
Coverage Δ

python
91.20% <ø> (ø)

r
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 58 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[Discussion] Incorporating external layout extensions with the official cytoscape release

Many layouts are shown as example in the gallery, but a lot of those layouts are not included by default in Cytoscape.js. Adding them to Dash might be an issue.
The following quote describes layout in cytoscape.js:

The function of a layout is to set the positions on the nodes in the graph. Layouts are extensions of Cytoscape.js such that it is possible for anyone to write a layout without modifying the library itself.

To accomplish this, we need to yarn add the external layouts extension, then write something like this in react:
import Cytoscape from 'cytoscape';
import COSEBilkent from 'cytoscape-cose-bilkent';
import React from 'react';
import CytoscapeComponent from 'cytoscape-reactjs';

Cytoscape.use(COSEBilkent);

class MyApp extends React.Component {
  render() {
    const elements = [
      { data: { id: 'one', label: 'Node 1' }, position: { x: 0, y: 0 } },
      { data: { id: 'two', label: 'Node 2' }, position: { x: 100, y: 0 } },
      { data: { source: 'one', target: 'two', label: 'Edge from Node1 to Node2' } }
    ];

    const layout = { name: 'cose-bilkent' };

    return <CytoscapeComponent elements={elements} layout={layout}>;
  }
}

However, including the packages at run time in Dash is impossible since Dash runs a bundle.js version of the Cytoscape.react.js, which means that all the packages have to be added beforehand, and included inside the bundle.js.
Including the layouts risks increasing the size of bundle.js, create more dependencies. Not including the layouts will severely limit the possibility of Dash-cytoscape.
This issue will serve as a discussion around how we should approach this layout problem.

Conversation moved to https://github.com/plotly/dash-cytoscape/issues/32


ToolTipModel Opacity 0 on mouseover

Expected Behavior
TooltipModel.opacity == 1 and the toopltip shows
Current Behavior
TooltipModel.opacity == 0 on mouseover, jumps to 1 on mouseout and then rapidly decreases to 0.
(Its actually TooltipModel[0].opacity due to https://github.com/chartjs/Chart.js/issues/7541)
Steps to Reproduce
https://codepen.io/tomlee86/pen/PoZOPrQ
Context

Environment

Chart.js version: https://www.chartjs.org/dist/master/chart.js
Browser name and version: Chrome 83.0.4103.116 (

Possibly a duplicate of https://github.com/chartjs/Chart.js/issues/7239

I'm not sure what's updating the opacity. Maybe it's an animation thing? Do you have any ideas @kurkle ?

opacity is animate by default. If you disable the animation, it is still changed to 0/1, directly. I don't think it is designed to be manually altered.

The point is opacity is the wrong value. On mouseover a bar/scatter point, it’s value is 0 and on mouseout it’s 1.  It should be the other way round I think.

I see. The example custom tooltip (https://www.chartjs.org/docs/master/configuration/tooltip) may need updating then. If the value is 0 at the event then the example tooltip returns before populating and positioning the tooltip
if (tooltipModel.opacity === 0) {
tooltipEl.style.opacity = 0;
return;
}

Hi! I'm seeing the same issue in v2.9.3, using a Scatter chart. When the mousenter event happens over a point, the tooltip's model opacity is 1, but immediately if you keep moving the cursor (without leaving the point), it goes to 0. The only way of keeping it as 0 is to stop moving at the exact moment you enter the point hit radius.
(Google Chrome 83.0.4103.116)


Front Face Detection lack of information

Hey there,
I'm integrating Front Face Detection (https://google.github.io/mediapipe/solutions/face_detection) (https://drive.google.com/file/d/1f39lSzU5Oq-j_OXgS67KfN5wNsoeAZ4V/view) model within my app.
I'm trying to understand what is the input that the model is expecting. Looking at the docs, it says that it's expecting a 128x128 square input image. But my camera ratio is 9:16 (vertical), and I need to detect faces inside each frame.
What am I expected to do? Should I crop the center-square of the image? If so, I can't detect faces properly as the face could be in the upper/lower bounds of the box. Usually, for face detection, you use the whole image as input, then you get faces. What is the recommend approach for source image which is not square?
Sample input from the camera:

You need to pad the image to make it a square input.

We are closing this issue now as we did not find any relevant update from the reporter.


api-docs: Update register API link, deprecate register-component

Hey, I just made a Pull Request!

The register-component isn't used in the project currently anywhere except in the API Docs register API link. This wires that link  instead back to the newer catalog-import.
This PR replaces PR #3782 to simply not use the register-component plugin, before some future pure decommission activity.
Tried to figure out how to do something smart with Winston to try warning if the register component is used (e.g., by an outside plugin, a la logger.warn('This component is deprecated')), but couldn't figure out how to inject it since this plugin lacks business logic (it's mostly entirely a React component). Welcome suggestion/advice!
Also figured a real npm deprecate wasn't appropriate here.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)

Ya!  Roger that...


Discrepancies 9.0.0 <-> 10.0.1

I have discovered some oddities between v9 and v10 so I thought a report could help.
Running from fresh (resynced from start) c334c12.

active_epoch_no in a tx with pool update certificate has changed.

SELECT
  pu.id,
  pu.cert_index,
  ph.view,
  pu.active_epoch_no
FROM tx
  JOIN pool_update pu ON (pu.registered_tx_id = tx.id)
  JOIN stake_address sa ON (sa.hash_raw = pu.reward_addr)
  JOIN pool_hash ph ON (ph.id = pu.hash_id)
WHERE encode(tx.hash, 'hex') = '28bd5e8c342ab89d6642e446cb299058ea36256af1718e4af9326898ce4192d7';

9:
  id   | cert_index |                           view                           | active_epoch_no
-------+------------+----------------------------------------------------------+-----------------
 10714 |          0 | pool1kchver88u3kygsak8wgll7htr8uxn5v35lfrsyy842nkscrzyvj |             250
 10715 |          1 | pool1s7t7mfc89syw93h07aammaccnua66yn6d4l0mqt7zqurz2mczvq |             250

10:
  id   | cert_index |                           view                           | active_epoch_no
-------+------------+----------------------------------------------------------+-----------------
 10963 |          0 | pool1kchver88u3kygsak8wgll7htr8uxn5v35lfrsyy842nkscrzyvj |             249
 10964 |          1 | pool1s7t7mfc89syw93h07aammaccnua66yn6d4l0mqt7zqurz2mczvq |             249

rewards have changed.

SELECT es.epoch_no AS "epoch",
  COALESCE(
    (
      SELECT COALESCE(SUM(amount), 0)
      FROM reward r
        JOIN pool_hash ph ON (ph.id = r.pool_id)
      WHERE epoch_no = es.epoch_no
        AND ph.view = 'pool1pu5jlj4q9w9jlxeu370a3c9myx47md5j5m2str0naunn2q3lkdy'
    ),
    0
  ) AS "rewards"
FROM epoch_stake es
  JOIN epoch e ON (e.no = es.epoch_no)
  JOIN pool_hash ph ON (es.pool_id = ph.id)
WHERE ph.view = 'pool1pu5jlj4q9w9jlxeu370a3c9myx47md5j5m2str0naunn2q3lkdy'
AND epoch_no = 219
GROUP BY es.epoch_no;

9:
 epoch |   rewards
-------+-------------+------------
   219 |<PHONE_NUMBER>3 |

10:
 epoch |   rewards
-------+-------------+------------
   219 |<PHONE_NUMBER>1

Rewards have been incorrect. There have been a number of changes that have either already been applied or in the process of being worked on.

Thanks for the information! And what about the first issue - different active_epoch_no?

In an earlier version active_epoch_no was incorrect. It has since been fixed (commit c226c4bbfd3ff0816723f44bf534e36eb8da1b44).

In an earlier version active_epoch_no was incorrect. It has since been fixed (commit c226c4b).

Thank you very much!


Moved to own library

I have moved to interconnect module to its own library, is that fine with you @zacharee?
Because that makes it was easier to version the library, which i usually do by tagging it, then building via JitPack

Good idea. Much easier for organizing

Great, added you as a contributor.


Add the implementation of CreateReport in ReportsService.

This adds the implementation of CreateReport based on the API design of ReportsService. Note that updating report and associated measurements is deferred till ListReports and GetReport are requested.

This change is

src/main/kotlin/org/wfanet/measurement/reporting/service/api/v1alpha/ReportsService.kt line 614 at r9 (raw file):
Previously, SanjayVas (Sanjay Vasandani) wrote…
This is a case where a Sequence would probably make things easier to read.
val seenDisplayNames = // init your map

metricList.asSequence().flatMap { metric ->
  metric.setOperationsList.asSequence().map {
    // Code that results in a pair of metric type to display name
  }
}.forEach { (metricType, displayName) ->
  // if display name has been seen for metric type, throw error
  // else add to seenDisplayNames
}

I just realized I can just use metric.metricTypeCase as the key... Would this be better? Or the Sequence one is still preferred?
for (metric in metricsList) {
    for (setOperation in metric.setOperationsList) {
      grpcRequire(
        !seenDisplayNames.getValue(metric.metricTypeCase).contains(setOperation.displayName)
      ) { "The display names of the set operations within the same metric type should be unique." }
      seenDisplayNames.getOrPut(metric.metricTypeCase, ::mutableSetOf) += setOperation.displayName
    }
  }


[EDIT]

Entry

https://web3isgoinggreat.com/?id=silvergate-crypto-focused-bank-faces-crisis
Changes

Old:  They acknowledged that the bank's "ability to continue" was a "going concern".
New: They are still "evaluating ... their ability to continue as a going concern".
Alternatively: They are still "evaluating" their ability to survive.
Background: "To continue as a going concern" is actually something positive, in the language of finance. It is what every copmany hopes to achieve. "Concern" here is not used as in something "concerning", something troublesome, but as in "venture", "living entity", or "to survive".
Agreement
By submitting this issue, I irrevocably agree to release my contribution under the CC-BY 3.0 License. I agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Agreed. No attribution required. I transfer all my rights in this little snippet to you.
Daniel Sokolov
Please attribute this contribution to:

You can leave this blank if this is a change so small as to not be copyrightable.

Appreciate it!


Clearing .openbazaar2.0 folder while preserving identity

We've had to clear the blocks/ folder on our bootstrap node as it was taking 17G of space. Now openbazaar-go is crashing. Is there an easy way to extract and reimport the identity into a fresh .openbazaar2.0 folder? Maybe this could be a command line option to pass in a specific identity.

init -m "your mnemonic"

Oh cool. What's an easy way to get mnemonic (in human readable format) out of a database?

Either the sqlite viewer or the wallet/mnemonic/ api call


Nav bar: Color change to denote current page is confusing with only two pages

Consider

underline current page, keep both nav links darker color
have a box around the link for the current page with a "highlight" (lighter) green color, since I think a box says "selected" more than a color change

One idea for the box:

to jazz up the box, when you mouse over on the other nav links, you can box without highlight (Kellen's suggestion, in case you want to chat with him about it later)

Decided to underline for now (perfection being the enemy of good and all), and consider the box in the future.


Are there any gzip options?

Are there any gzip options?
Is adding the gzip option possible?

@b6pzeusbc54tvhw5jgpyw8pwz2x6gs Sorry, not yet. But it's worth to add the future :)
I'm going to implement it in few days. Please wait a while.

@b6pzeusbc54tvhw5jgpyw8pwz2x6gs Sorry for being late. I've just added an environment variable CONTENT_ENCODING for compressing response body. Please try it :)

Awesome! You're not late at all, thanks!


RFE: Improve molecule scenarios in new collection

Add a README to the current which explains that it is there to demonstrate running exisiting integration tests with molecule.
Add an additional scenario which is 100% molecule w/o an integration test.

+1 on this.
Following a guide like Introducing Ansible Molecule with Ansible Automation Platform is pretty close, but will error out when actually kicking off molecule test.
➜  lab git:(main) $ cd extensions
➜  extensions git:(main) $ molecule test
CRITICAL 'molecule/default/molecule.yml' glob failed.  Exiting.

There is an implied task that you need to create a directory with at least a molecule.yml that can be referenced as the scenario.
➜  extensions git:(main) $ ls molecule
my_role  utils
➜  extensions git:(main) $ molecule test -s my_role


Rethrow OpenSearch exception in concurrent search

Description
CircuitBreaker tests are breaking because of the difference in the Exceptions being thrown at the shard failure. The exceptions can be found below:
Shard failure exception with Concurrent Search
shard[[wkVu-9P-R1ylmYdjXkGw4w][cb-test][6]], reason [RemoteTransportException[[node_t0][<IP_ADDRESS>:62392][indices:data/read/search[phase/query/id]]]; nested: QueryPhaseExecutionException[Query Failed [Failed to execute main query]]; nested: CircuitBreakingException[[fielddata] Data too large, data for [test] would be [1689/1.6kb], which is larger than the limit of [100/100b]]; ], cause [CircuitBreakingException[[fielddata] Data too large, data for [test] would be [1689/1.6kb], which is larger than the limit of [100/100b]]
	at org.opensearch.common.breaker.ChildMemoryCircuitBreaker.circuitBreak(ChildMemoryCircuitBreaker.java:104)
	at org.opensearch.common.breaker.ChildMemoryCircuitBreaker.limit(ChildMemoryCircuitBreaker.java:196)
	at ...

Shard failure exception without Concurrent Search
shard [[cbO2S4OXRHOvPGDErQe2lg][cb-test][0]], reason [RemoteTransportException[[node_t0][<IP_ADDRESS>:64587][indices:data/read/search[phase/query]]]; nested: QueryPhaseExecutionException[Query Failed [Failed to execute main query]]; nested: OpenSearchException[java.util.concurrent.ExecutionException: CircuitBreakingException[[fielddata] Data too large, data for [test] would be [3529/3.4kb], which is larger than the limit of [100/100b]]]; nested: ExecutionException[CircuitBreakingException[[fielddata] Data too large, data for [test] would be [3529/3.4kb], which is larger than the limit of [100/100b]]]; nested: CircuitBreakingException[[fielddata] Data too large, data for [test] would be [3529/3.4kb], which is larger than the limit of [100/100b]]; ], cause [OpenSearchException[java.util.concurrent.ExecutionException: CircuitBreakingException[[fielddata] Data too large, data for [test] would be [3529/3.4kb], which is larger than the limit of [100/100b]]]; nested: ExecutionException[CircuitBreakingException[[fielddata] Data too large, data for [test] would be [3529/3.4kb], which is larger than the limit of [100/100b]]]; nested: CircuitBreakingException[[fielddata] Data too large, data for [test] would be [3529/3.4kb], which is larger than the limit of [100/100b]];
	at org.opensearch.index.fielddata.plain.AbstractIndexOrdinalsFieldData.load(AbstractIndexOrdinalsFieldData.java:116)
	at org.opensearch.index.fielddata.plain.AbstractIndexOrdinalsFieldData.load(AbstractIndexOrdinalsFieldData.java:62)
	at ...

This PR attempts to fix this.
All tests report after this change(making sure that the other tests don't break with this change): link
Related Issues
Resolves #9124

Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@sohami @jed326 please review the changes.


feat(tailorviews): Anonymized Data #213

In reference to #213
Please Review:
@skhtet
@akonsowski
@rkenyon1969

:+1:

:+1:


Validate the latest cert-manager in Rancher server helm chart to latest

Cert-manager 1.5.1 is EOL; requesting eng validation for cert-manager in Rancher to see if it can be updated to 1.6.x (or higher). This will require an update to docs as well. Please see https://cert-manager.io/docs/installation/supported-releases/, as it appears 1.6.x is almost EOL as well.
See also #34299 as a reference to the previous validation testing done on 1.5.1.
cc @sowmyav27

Short Summary:

Both 1.6.2 and 1.7.1 work in upgrade and fresh install scenarios
There's a few versions which customers should avoid because they cause upgrade issues
You need to follow a specific upgrade path for this to work (you can't do two helm upgrade calls - you need to remove rancher and cert-manager and re-install). This won't cause data loss, and is one of the upgrade paths we mention in our docs.
I only tested this with Let's encrypt, need to also test with the rancher created certs.

The following validation steps were done for 1.5.1 -> 1.6.2 (success) and 1.5.1 -> 1.7.1 (success):

Create a rke1 cluster (k8s version 1.20.12).
Install cert-manager following the rancher docs (besides CRD install - used chart option for that):

kubectl create namespace cattle-system
helm install cert-manager jetstack/cert-manager --namespace cert-manager --create-namespace --version v1.5.1 --set installCRDs=true

Install rancher using let's encrypt as the cert source:

helm install rancher rancher-latest/rancher --namespace cattle-system --set hostname=$HOSTNAME --set bootstrapPassword=$BOOTSTRAP --set ingress.tls.source=letsEncrypt --set letsEncrypt.email=$EMAIL --set letsEncrypt.ingress.class=nginx

Through the rancher UI, create a downstream RKE cluster in digital ocean.
Create a new user with the standard user global role.
Through the rancher UI, create a project in the downstream RKE cluster. Add the new user as a project member. Create a namespace in the project (one as admin, one as standard user).
Uninstall Rancher using the following command:

helm delete rancher -n cattle-system

Uninstall cert-manager using the following command:

helm delete cert-manager -n cert-manager

Install the new cert-manager version using the following command:

helm install cert-manager jetstack/cert-manager --namespace cert-manager --create-namespace --version $CERT_MANAGER_VERSION --set installCRDs=true

Install the new version of rancher using the following command:

helm install rancher rancher-latest/rancher --namespace cattle-system --set hostname=$HOSTNAME --set bootstrapPassword=$BOOTSTRAP --set ingress.tls.source=letsEncrypt --set letsEncrypt.email=$EMAIL --set letsEncrypt.ingress.class=nginx --version 2.6.4-rc4

Confirm that the cert remains valid, by going to the rancher UI. Create a third namespace in the downstream cluster's project using the created user. Confirm that the cluster/project/user data was not lost during the upgrade.

I also did the following fresh install validation for 1.6.2 (success) and 1.7.1 (success):

Create a rke1 cluster (k8s version 1.20.12).
Install cert-manager following the rancher docs (besides CRD install - used chart option for that):

kubectl create namespace cattle-system
helm install cert-manager jetstack/cert-manager --namespace cert-manager --create-namespace --version $CERT_MANAGER_VERSION --set installCRDs=true

Install rancher using let's encrypt as the cert source:

helm install rancher rancher-latest/rancher --namespace cattle-system --set hostname=$HOSTNAME --set bootstrapPassword=$BOOTSTRAP --set ingress.tls.source=letsEncrypt --set letsEncrypt.email=$EMAIL --set letsEncrypt.ingress.class=nginx --version 2.6.4-rc4

Through the rancher UI, create a downstream RKE cluster in digital ocean.
Create a new user with the standard user global role.
Through the rancher UI, create a project in the downstream RKE cluster. Add the new user as a project member. Create a namespace in the project (one as admin, one as standard user).
Through the rancher UI, delete the created cluster.

Notes:

There was a breaking change implemented in cert-manager 1.5.4. This was later reverted. Customers will need to follow the recommended upgrade path (i.e. don't upgrade to or use versions 1.5.4, 1.6.0, or 1.6.1)
It should be noted that customers who are using an unsupported version of cert-manager will need to refer to the above docs on completing the upgrade process
You can't upgrade rancher/cert-manager using helm upgrade. The api version used for the issuer will result in the following error:

Error: UPGRADE FAILED: current release manifest contains removed kubernetes api(s) for this kubernetes version and it is therefore unable to build the kubernetes objects for performing the diff. error from kubernetes: unable to recognize "": no matches for kind "Issuer" in version "cert-manager.io/v1beta1"

To prevent this error, you need to follow Option B as stated in the rancher docs. This option was adapted and used above in the testing steps.

It should be noted that both upgrades had various issues with removing the cluster, including:

Resulted in the downstream cluster being briefly unavailable (error was webhook related). The issue eventually resolved itself.
Caused issues when the downstream cluster was deleted (500 errors)
Downstream cluster was never fully deleted, had to be processed outside of rancher

Since these issues did not happen with the RKE clusters, I don't believe that these errors should affect the validity of using cert-manager versions 1.6.2 and 1.7.1.
I will also re-run the above tests using the other cert method (rancher generated), as the above only represents let's encrypt certs. Will update the issue when that is done.

I re-ran the following tests from the previous comment with rancher generated certs:

Upgrade from cert-manager 1.5.1 -> 1.6.2 (with rancher upgrade from 2.6.3 -> 2.6.4-rc4) (pass)
Upgrade from cert-manager 1.5.1 -> 1.7.1 (with rancher upgrade from 2.6.3 -> 2.6.4-rc4) (pass)
Fresh install of cert-manager 1.6.2 with rancher version 2.6.4-rc4 (pass)
Fresh install of cert-manager 1.7.1 with rancher version 2.6.4-rc4 (pass)

Notes:

For installing rancher with self-signed certs (i.e. rancher generated), the following command was used:

helm install rancher rancher-latest/rancher --namespace cattle-system --set hostname=$HOSTNAME --set bootstrapPassword=$BOOTSTRAP

Firefox was used instead of chrome (chrome didn't play well with the self-signed certs)
For upgrading rancher with self-signed certs (i.e. rancher generated), the following command was used:

helm install rancher rancher-latest/rancher --namespace cattle-system --set hostname=$HOSTNAME --set bootstrapPassword=$BOOTSTRAP --version 2.6.4-rc4

Summary:

The current latest versions of cert-manager (1.6.2 and 1.7.1) appear to work in upgrade cases (when rancher is also upgraded from 2.6.3 to 2.6.4) and in fresh install cases (with 2.6.4), with some caveats.
Rancher has to be upgraded with option b from the rancher docs. It also should be noted that if cert-manager is upgraded alone (i.e. rancher is not upgraded), users will be likely to experience issues. We should update our docs with specific instructions to ensure that users do not run into issues.
Certain versions of cert-manager may cause issues. See the cert-manager docs for more information. We should note this in our docs and link to the cert-manager documentation in case users have started to use unsupported versions of the applications.

If there are any other test cases you would like me to run to confirm functionality, please let me know.

@jtravee do you have an opinion on how we should proceed based on Michael's summary?

@jtravee do you have an opinion on how we should proceed based on Michael's summary?

I think we're good to proceed in documenting for the new versions of cert-manager, and we'll make sure to add the caveats that were described above.

@jtravee One thing to note here - I'm not 100% sure that the issues caused when using an RKE2 cluster (i.e. created on version 2.6.3 with cert-manager 1.5.1) are completely unrelated to cert-manager - when I didn't upgrade cert manager (but do upgrade rancher) I don't see the issue and can consistently reproduce with an upgrade (but it's only with RKE2 - so I'm not 100% sure). I'll let you know if I manage to isolate the issue - that's one area that I'm still a bit nervous on.

@jtravee One thing to note here - I'm not 100% sure that the issues caused when using an RKE2 cluster (i.e. created on version 2.6.3 with cert-manager 1.5.1) are completely unrelated to cert-manager - when I didn't upgrade cert manager (but do upgrade rancher) I don't see the issue and can consistently reproduce with an upgrade (but it's only with RKE2 - so I'm not 100% sure). I'll let you know if I manage to isolate the issue - that's one area that I'm still a bit nervous on.

Thanks! I can just hold off on documenting until the RKE2 piece is fully tested, no problem!

Pending validations:

Cert manager update - 1.5 --> 1.6 --> 1.7 update
Rancher upgrade rollback using backup-restore app after cert manager has been upgraded to 1.7 version


Possibility to handle focus from outside

Is your feature request related to a problem? Please describe.
Hi,
I already opened an A11y issue ticket for this library before and I was really impressed by the speed you delivered a fix.
Thank you very much again for this.

We have tried to adapt the Datepicker from outside, to align it as much as possible with the W3C suggestion regarding datepickers.
We came across an issue, which we currently are not able to solve without forking the library.
That's why I first want to ask, if it is maybe an improvement for everybody and therefore can go into your original library.
W3C suggests following points, which we could not implement without a fork:

while navigating inside the calendar, one should be able to jump to the first/last day of the current week, by pressing HOME or END key on your keyboard
while navigating inside the calendar, one should be able to jump to the previous/next month, by pressing PAGE UP or PAGE DOWN key
while navigating inside the calendar, one should be able to jump to the previous/next year, by pressing SHIFT + PAGE UP or SHIFT + PAGE DOWN

I was only able to visually shift the focus via javascript, but could not actually set the index of the focus inside the datepicker.
That means e.g., after pressing END key, the focus visually moves to the last day of the current week, but as soon as I press some arrow-key, let's say RIGHT-ARROW for this example, the focus will jump back to the day I was before pressing END and then go to the next day.
Describe the solution you'd like
I see two possible solutions for this:

You try to implement the W3C suggestions into the datepicker by default
You implement some feature (prop or something?) which provides a possibility to modify the current focus from outside of the element.

Describe alternatives you've considered
I will have to fork the library then I guess, I did not find any other solution yet.
Additional context

Pressing END key

Pressing RIGHT-ARROW

Hi,
any update on this?
Thx & BR

I missed it completely, will re-open as bug

Hi,
unfortunately I still have found two last issues.

The Focus is still lost when switching month or year with the keyboard (at least the visible focus ring is lost) (PAGE UP/PAGE DOWN or SHIFT + PAGE UP/SHIFT + PAGE DOWN
When having auto-apply enabled, HOME and END key both select and close the datepicker, which should not be the case I think, because it's just a navigation action like using the arrow keys or PAGE UP/PAGE DOWN which both do not select and close the datepicker
Thanks & BR

Sorry for bumping, just scared you missed my update.


VSC-like recent used command in command plate (search result)

Description of the new feature/enhancement
A VSCode-like recently used (history) command in the command plate is very helpful by doing repeated jobs.
Scenarios:

executing a command that does not have a shortcut, like "rename tab title" or "toggle always on top mode". With this feature on, you can save time to type at least two keywords to do so. You can switch tab than re-do it with "ctrl + shift + p" + enter.

skip unwanted alike command. You want to new a tab that you can not tell it is profile 7 or 8. Without a mouse, you will be willing to use the nested command "new tab... with >", but, as image, you may need too press tons of down arrow to reach that command instead of the one without nested command.

Maybe you will later find out: you can do this by ⌨"ctrl + shift + space" or adding "..." in search.
But, I think the command plate's purpose is to ease the pain/gives hint before you learnt the shortcut.

Proposed technical implementation details (optional)

In general, I think you're looking for the same thing as #6647.
FWIW, the command palette does do "fuzzy" matching, so typing nt. will probably automatically filter to New Tab... for you.
Thanks!
/dup #6647


Question not issue: How config devise modules dynamically

I want to allow admin user to set the devise module from user interface and store it in db.
In model like this:
devise `:database_authenticatable , :trackable , current_user.options_from_db`

How can I do it ?

Please use the mailing list or StackOverflow for questions/help, where a wider community will be able to help you. We reserve the issues tracker for issues only.


TEST PR - Ignore this.

Please ignore this test PR, only for debugging circleci behavior.

It behaved OK, closing.


[BUG] - Squashing Migrations is not taking updated Auto Increment Value

Laravel Version: v9.28.0
PHP Version: 8.1
Database Driver & Version: 8.0.30

Description:
When we reset the auto-increment value of the new table by using ->from(100) Laravel schema:dump --prune it's not taking the auto-increment value inside the dump file. Ideally, we need to add AUTO_INCREMENT=100 at the end of the table creation SQL query.
Steps To Reproduce:
Migration looks like
Schema::create('test_table', function (Blueprint $table) {
    $table->increments('id')->from(100);
    $table->string('name');
});

And the generated schema should be like this:
CREATE TABLE `test_table` (
  `id` int unsigned NOT NULL AUTO_INCREMENT,
  `name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci AUTO_INCREMENT=100;

It is not adding AUTO_INCREMENT=100 on the dump File.
Thanks, Let me know if I was missing something.

Hi @hirenkeraliya. Thanks for reporting this. At first glance this seems like a bug with mysqldump and not Laravel. I found https://bugs.mysql.com/bug.php?id=14515 which notes something similar got fixed in MySQL 5.1 however when I browse the manual of 8.0 I cannot find anything about this. I have no idea how to manipulate mysqldump to also include the auto incrementing value. I think it's best that you file a bug report with MySQL itself as this isn't Laravel specific it would seem.


Add Rīgas Tehniskā Koledža

@cliquant Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


WIP: [DO NOT MERGE]: K8s: Define k8s template for master and worker

This assumes the existence of Ciao compatible k8s VM images
for worker and master.
Scripts for generating these images will be published later.
Signed-off-by: Manohar Castelino<EMAIL_ADDRESS>

Coverage decreased (-0.04%) to 66.596% when pulling 015d50c1d4e99ee2599fbe8a7bd3068ed756a32b on mcastelino:k8s into 0333062c1d7f9615b50bdbbe1441a2835a63733b on 01org:master.

Coverage remained the same at 66.56% when pulling 9d74a1bf1572314475fb80531a012a840d6a6941 on mcastelino:k8s into 3bb33ad64383f0712d0f68e7e25379a7be636254 on 01org:master.

Coverage increased (+0.01%) to 66.574% when pulling 1704dfbcafb18c57365fccf98e08e9190547ca6c on mcastelino:k8s into 74c1e8d41bc4fceefa5b785513691a67d6544a54 on 01org:master.

Coverage remained the same at 66.617% when pulling ca7830ef62ffdd313327c2202ba4f14b5f853624 on mcastelino:k8s into cf9780c55fd828022bb479a5b39ebce068bbea7d on 01org:master.


keep getting crash when opening the video settings (in my modpack) (CLIENT-SIDE-MODPACK) (not on curseforge as a modpack yet ): )

here is the crash report https://bytebin.lucko.me/QFZ15mq8DU

url supported by (not enough crashes)

Try removing betteruiscale mod to see if it still occurs, also I don't think I'm at fault here looking at the crash report.


AE2WTLIB-0.3.1-1.16.5 Bugs?

Bug 1. Creative Inventory Tab Is Called itemGroup.ae2wtlib.
Bug 2. The ToolTips Of The Wireless Terminals when they are unlinked Are Called AppEng.GuiITooltip.Unlinked.
Bug 3. When Opening The Wireless Crafting Terminal Your Player Is In The Terminal Slots.
Here Are Some Photos.

Hello. I know how to fix these. If you want me to rebuild the mod without the bugs (not all) dm me. Lacsaysy#0001

Hello. I know how to fix these. If you want me to rebuild the mod without the bugs (not all) dm me. Lacsaysy#1

On what Discord?

Hello. I know how to fix these. If you want me to rebuild the mod without the bugs (not all) dm me. Lacsaysy#1

On what Discord?

Yes

Hello. I know how to fix these. If you want me to rebuild the mod without the bugs (not all) dm me. Lacsaysy#1

On what Discord?

Yes

Doesn't work did you forget to include all numbers #1?


Additional Icons

Describe the solution you'd like
Looking for additional icons

UAV /drone
technician
badge /swipe card
grip (drag & drop reorder)
Sign
approve
wind farm (no suggestions yet)

Describe alternatives you've considered
The majority are from material design I believe.
The sign icon is custom.
Additional context

Thanks for this request :)
We have newly implemented 3 types of drone (land, shore and air) that have been released.
The Technician icon can be found under the name engineering in our library.
We will implement the other suggested in our next release.

Ready for review @BirteThornquist @benteljones

Wind farm: latest in Energy Category
Badge: latest in People Category
Approve and Signature: latest in UI Action

@mimarz ready to deploy if review is approved :)

@lucasveil I first wondered if the lower line on the body could be increased to a whole px (badge) but then you get some new challenges. Never mind! 😉 LGTM! 👍🏻

LGTM @lucasveil  👍🏻

There is some issue with the wind farm icon that we didn't manage to solve. I need to have a deeper look into it so that design and dev is aligned and that the icon exports correctly.