Regression the position of one of images in MenuFlyoutItem is incorrect

Describe the bug

Steps to reproduce the bug

Add flyout item more than 2
See the icon position is wrong

Expected behavior
The same position as before.
Screenshots
No response
NuGet package version
None
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

Fixed in the upcoming 1.5.1 servicing release.

This is not fixed at all.
Let me know how you fixed and verified to have fixed?

More specifically, this issue occurs when the menu item is hidden and then made visible later. The issue does not occur when the item is visible from the start.

The scenario @yaira2 mentioned is exactly what the fix was for, but it sounds like the fix wasn't complete.

There's an example app that can repro this issue. https://github.com/files-community/Files Upgrade the version in Files.App.csproj file to repro.

@0x5bfa Could you provide more specific repro steps using this app?  I've brought up the right-click menu in multiple places, but I haven't yet been able to see this repro with the latest version of the Microsoft.WindowsAppSDK NuGet package.

Try right clicking a photo

Select an item
Right click

In the latest commit, this icon is already hidden to publish a release to the public. Please check out to the Upgrading commit first.

I've added some extra checks to ensure that we're in the correct visual state at the right time.  The Files use case should be fixed in the next version of WinAppSDK.

@llongley thank you for the fix.


[DOC] Grammatical Error in Readme File

Is this issue related to an existing part of the documentation? If so, please provide a link
The section can be accessed from here
Describe the thing to improve
There were a few grammatical and punctuation errors in the document. (Improved in the PR)
Describe the solution (optional)
Wholesome documentation provides a better reading experience for a first-time product user. Hence, I have changed a few words and punctuation to provide a better reading experience.

@aliemir Please review the PR here. Thanks!

Hey @harshagrawal523 thank you for the issue and the quick PR 🚀 Leaving a quick review to the PR now.

@aliemir How can we claim the Refine Swag Tshirt?


Slight improvement of small_vector performance

adding benchmark

"Slight improvement": does that mean that Boost's implementation is still faster in the benchmark, or something else?

"Slight improvement": does that mean that Boost's implementation is still faster in the benchmark, or something else?

That means that for me (on WIndows) Boost is still faster. I have not tested gcc's or clangs' implementation of std::memory_resource. I have added a benchmark to this PR, would you be able to run it in your environment?
To explain what I changed: the PR essentially removes an explicit default construction for the std::aligned_storage_t<> that holds the pre-allocated memory. We've had a similar issue with our cache_line_data in the past, so I'm hoping that my fix will do the trick.

That means that for me (on Windows) Boost is still faster. I have not tested gcc's or clang's implementation of std::memory_resource. I have added a benchmark to this PR, would you be able to run it in your environment?

For the benchmark itself it unfortunately doesn't seem to make a big difference. This is with tcmalloc. I haven't tried on DLA-Future yet.
 Back to the drawing board, then.

@msimberg could you rerun the benchmark with --vector_size=1, please (also perhaps increase --test_count to 1e6/1e7)? That will push_back one element into each instance of the tested vectors. This is very close to what happens in hpx::future, I believe.
The benchmarks you ran add 10 elements, which guarantees allocation (except for the N==16 vectors). In those cases, both versions are very similar as the time is dominated by the allocations anyways.
From what I see from your timings above, the case without allocations has improved and has come closer to the boost vector.

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each-++++InfoPropertyBeforeAfterHPX Datetime2022-01-14T17:23:25+00:002022-02-08T22:49:30+00:00HPX Commit8f2c6614ec9aaeb3a0990bdc1f8cd6851a119c2aa9d806add9a57f6d80bd8d738d98f809d4efb437EnvfileCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ClusternamedaintdaintHostnamenid01559nid00025Datetime2022-01-14T18:39:05.441154+01:002022-02-09T00:02:04.509593+01:00ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPX Datetime2021-11-11T08:14:57+00:002022-02-08T22:49:30+00:00HPX Commit96a2e4bd1c76207dea8d5302784962c927882406a9d806add9a57f6d80bd8d738d98f809d4efb437EnvfileCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ClusternamedaintdaintHostnamenid00006nid00025Datetime2021-11-11T09:28:13.071121+01:002022-02-09T00:02:21.380945+01:00ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale-(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPX Datetime2021-11-10T19:14:21+00:002022-02-08T22:49:30+00:00HPX Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01aa9d806add9a57f6d80bd8d738d98f809d4efb437EnvfileCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ClusternamedaintdaintHostnamenid00120nid00025Datetime2021-11-10T20:28:18.266961+01:002022-02-09T00:02:36.624048+01:00Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

@msimberg FWIW, at least two of the performance tests report significant improvements.

@msimberg could you rerun the benchmark with --vector_size=1, please (also perhaps increase --test_count to 1e6/1e7)? That will push_back one element into each instance of the tested vectors. This is very close to what happens in hpx::future, I believe.

Good point! There's still a gap to Boost, but this is definitely an improvement. Thanks for looking into this!


Surrounding pairs missing backticks

I believe backticks should be surrounding, at least this how it works (and expected to work) in normal JS files. Volar disables this however, I believe must be added here:
https://github.com/johnsoncodehk/volar/blob/4963cd1350431e4bc3734486e56c6f6e877ce8f9/extensions/vscode-vue-language-features/languages/vue-language-configuration.json#L74

For <script> block, vscode use JS surroundingPairs config from https://github.com/microsoft/vscode/blob/b5a1bb34e9c6b77c2a8ccf54bcdbb4bac4d420cb/extensions/javascript/javascript-language-configuration.json#L72, so it do not need to define in vue language config.

Thanks for following up,
I apologize for not being more verbose in my initial issue description:
Whenever I select a string inside JS in a .vue  file and try to surround it with backticks by typing a backtick, the whole string gets replaced with a single backtick. This is not how it works with all other surrounding symbols ({} () '' ""  etc), hence my guess about the wrong surroundingPairs config.
This is still happening and would be nice to find out why.
https://user-images.githubusercontent.com/4336560/187037029-788d9b61-fa19-49be-b0ec-ab7d6cb0aba9.mov


Fix minor typos in docs/contributing.md

Codecov Report

Merging #1281 (c47ea26) into master (9696c73) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1281   +/-   ##
=======================================
  Coverage   82.26%   82.26%
=======================================
  Files          65       65
  Lines        5295     5295
=======================================
  Hits         4356     4356
  Misses        939      939

Continue to review full report at Codecov.

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

Thank you! 😃


Add progressbar for docker load

Signed-off-by: Lei Jitang<EMAIL_ADDRESS>Currently docker load just block until the docker load finish,
it's not friendly for user. This patch add progressbar for docker load.
$ docker load -i ubuntu.tar
Loading file to server [==================================================>] 225.5 MB/225.5 MB
Loading layer: 1c9383292a8f [==================================================>] 201.6 MB/201.6 MB
Loading layer: 9942dd43ff21 [==================================================>] 801.8 kB/801.8 kB
Loading layer: d92c3c92fa73 [==================================================>] 603.6 kB/603.6 kB
Loading layer: 0ea0d582fd90 [==================================================>] 601.6 kB/601.6 kB
Loading layer: cc58e55aa5a5 [==================================================>] 21.18 MB/21.18 MB
Loading layer: c4ff7513909d [==================================================>]   599 kB/599 kB
$

Oh, nice!!
Looks like there are go-lint failures though;
Errors from golint:
api/client/load.go:26:18: should omit type io.ReadCloser from declaration of var input; it will be inferred from the right-hand side

Please fix the above errors. You can test via "golint" and commit the result.

So do the docker save?

@HuKeping  The docker save progressbar is on working

but don't know if we really need this ..

The test failure seems related, please take a look: FAIL: docker_api_images_test.go:52: DockerSuite.TestApiImagesSaveAndLoad

Design seems ok for me
ping @docker/core-maintainers

@jimmyxian can you take care of this for the swarm side ?
Thanks

I like it, moving to code review

@vieux Thanks for ping me.
I will take care of this on swarm side. :)

@coolljt0725 Would you mind to address some comments?

@LK4D4, @coolljt0725 has been at DockerCon! :)

This will need a rebase after #17924, but I recommend waiting for #18353, which changes ProgressReader.

ping @coolljt0725, https://github.com/docker/docker/pull/18353 was just merged. can you rebase this and update this for the changes in https://github.com/docker/docker/pull/18353? Thanks!

@thaJeztah  Thank you for the ping, I'll update it later

ping @coolljt0725 :innocent:

@thaJeztah  Thank you for your ping. sorry for the delay to update this PR,  very very busy these day and maybe I can update this PR this weekend.

@coolljt0725 no worries! Let us know when you're done (or if you want someone to carry it for you)

ping @tonistiigi do you think somebody should carry this PR?

@thaJeztah  Sorry for the late, I start working on this...

@coolljt0725 thanks, thats great! And Happy New Year to you! (Well, "our" new year, I think your new year is in February :smile:)

@thaJeztah  Thank you, and Happy New Year to you(yes, Chinese New year is in Feb) -:)
I have finished the refactor and it works
$ docker load -i ubuntu1.tar
Loading layer: 17f5bb501870 [==================================================>] 201.6 MB/201.6 MB
Loading layer: 983647a7cf79 [==================================================>] 801.8 kB/801.8 kB
Loading layer: 6d8125b31a09 [==================================================>] 603.6 kB/603.6 kB
Loading layer: d351dc964d98 [==================================================>] 601.6 kB/601.6 kB
Loading layer: f146e528f86d [==================================================>] 21.18 MB/21.18 MB
Loading layer: d8b3f56cd852 [==================================================>]   599 kB/599 kB
But don't know why I can't push it to Github
$ git push -f origin add_load_progressbar
Username for 'https://github.com': coolljt0725
Password for<EMAIL_ADDRESS>Counting objects: 1233, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (259/259), done.
Writing objects: 100% (619/619), 143.65 KiB | 0 bytes/s, done.
Total 619 (delta 482), reused 477 (delta 356)

Don't know why it blocked. Maybe something wrong with the proxy....

@coolljt0725 that's weird. If it doesn't work, feel free to open a new PR to replace this one

@thaJeztah  It should be something wrong with our enterprise firewall, I'll take a look at that tomorrow, if it doesn't work, I'll try to open a new PR

Thanks @coolljt0725

updated. I wonder if we should add a flag to the load api to disable the progress bar

updated. I wonder if we should add a flag to the load api to disable the progress bar

Perhaps a -q / --quiet flag? Didn't we have detection to check if a TTY is present? I can imagine this not needed if ran from a script :)

@aaronlehmann  thanks you for your suggestion
@thaJeztah  Added a -q/--quite flag

@thaJeztah  Oh, my poor english..., thank you, updated

@coolljt0725 don't forget to update the docs and man-pages as well :innocent:

@thaJeztah  I'll update the docs when it go to docs review

@coolljt0725 you need to make a PR to https://github.com/docker/engine-api to put the API changes in (to be able to rebase there and proceed forward) :sweat_smile:

ping @vieux because they do this in swarm. Maybe they can remove their implementation if we add this one.

oh he's already in this thread XD

@calavera yes! as soon as it's merged we are going to switch to this one

SGTM

/ping @coolljt0725 :angel:

@vdemeester  will rebase later :)

rebased

good so far, just needs tests and doc updates.

LGTM

ping @coolljt0725 don't forget to update the documentation for the new flag/option

@thaJeztah Thank you for reminding :)

@coolljt0725 this is good but you can't update the files in vendor/ without vendoring them first.

@tiborvass  I'll update this once https://github.com/docker/engine-api/pull/65 merged

@coolljt0725 docker/engine-api#65 was already merged and vendored, go for it!

@calavera  rebased.
Chinese New Year is coming, Happy Chinese New Year  :-).
And I start a 9-day vacation tomorrow, so I don't know if I have time to update the tests
and docs during the vacation, if not, I'll update docs and test when the vacation end.

@coolljt0725 happy new year, and enjoy your vacation!

Here comes the  "Year of Monkey" LOL

:fireworks: :monkey_face: :fireworks:
we can carry it.

@coolljt0725 happy new year!!! and thanks

LGTM

Carried here: #20078


Output from console.log during SSR is not reset between requests

Thanks for filing a bug! To save time, if you're having trouble using the library, please check off the items you have tried. If you are just asking a question, skip right to the bottom.
Please verify these steps before filing an issue, and check them off as you go

[x] The relevant native JavascriptEngineSwitcher library packages are installed (such as JavaScriptEngineSwitcher.V8.Native.win-x64)
[x] The VC++ 2017 runtime is installed
[x] The value of SetUseReact and SetUseBabel is correct in ReactConfig.cs or Startup.cs
[x] I've looked at the sample projects in this repo to verify that my app is configured correctly

I'm using these library versions:

ReactJS.NET: 5.0.0

Steps to reproduce / description
make sure to enable reuse of javascript engines.
SetReuseJavaScriptEngines(true)
render a simple component that logs something.
function Comp(){
     console.log("test");
     return
Hello World!
;
}

and refresh the page a few times.
You'll notice you get one more console.log for each page refresh. (Until the javascript engine is reset)
Suggested fix: Either expose a method that resets the console calls array or you could just make console.getCalls empty the array of calls, since I don't see a situation where you'd want to get the same calls more than once.

Happened to me as well... even when the component called console.log is not rendered in the next requests, the console.log message still appears.

Hmmm... It's likely that this has been a problem ever since engine pooling was added to the library. The data stored in the log shim needs to be cleared after the request.


quantitative   immunoblotting

I was looking for a term for
quantitative   immunoblotting
and found
protein expression level evidence based on western blot used in manual assertion
Go to external page http://purl.obolibrary.org/obo/ECO_0007183  Copy
Search ECO
Search
A type of protein expression level evidence based on western blot that is used in a manual assertion. [ http://www.evidenceontology.org/browse/#ECO_RCT ]
is this the term I need, and if so would
quantitative   immunoblotting be a better name? The name and definition sound almost identical

Hi Val,
I think that ECO:0007183 could work for you. Although, I'm thinking that 'quantitative immunoblot'  might actually be a more specific child of ECO:0007183 since not all western blotting is quantitative.
I agree that the names of these terms are a little cumbersome. And could possibly be revised.
What are your thoughts on whether you want a new more specific child for the quantitative term?
Michelle

Oh yes of course it is more specific,  I think a descendant.

Hi Val,
In looking at the terms around the above term a bit more, I realize that there is more work to be done in this region of the tree for this all to make sense. How quickly do you need this term?
Michelle

Not quickly. Nothing is ever needed quickly... In your own time ;)

Thank you!  :)

Hi Val - sorry it took so long to get back to this. There are a lot of things that disturb me about the terms in this node, but I don't have to address all of those to get you the term you want.
Here is my proposal:
We are thinking of merging 'protein expression level evidence based on western blot' into its parent 'western blot evidence'. (As currently I don't see how they are different.) This would result in a term that is for 'qualitative western blot' which would encompass all types of western blot.
For your term, we were then thinking we'd make a child of 'qualitative western blot' that would be 'quantitative western blot'.
Does this sound ok?

Yes,  that sounds good. I  can't remember which paper I needed it for  (why didn't I include the PMID?!)
but I'm sure it will come back to me!

Ok good - (sorry again for the huge delay making you forget what annotation this was for)
I've actually decided to merge three terms together.
Plan:
-merge ECO:0005602 'protein expression level evidence based on western blot'
and ECO:0000112 'western blot evidence'
into ECO:0000333 'sodium dodecyl sulfate polyacrylamide gel electrophoresis evidence'
change name of merged term to: 'qualitative western immunoblotting evidence'
with synonyms of all three old names.
New definition: "A type of protein expression evidence where proteins are separated using gel electrophoresis, blotted onto a membrane, and probed with an antibody that can be detected via light or radioactive emission."
reference: https://pubmed.ncbi.nlm.nih.gov/23050259/
Add parent 'protein expression level evidence' to the merged term.
Likewise merge the automatic/manual assertion children of each of these into each other:
merge ECO:0000112 and ECO:0007287 into ECO:0007770
merge ECO:0000279 and ECO:0007183 into ECO:0007689
New term: 'quantitative western blot'
child of ECO:0000333 (the newly merged term from above)
def: "A type of qualitative western blot evidence where detection of the signal is carried out through digital imaging and the signal is normalized with methods such as standard curves built from reference housekeeping proteins or total transferred protein measurements."
reference: https://pubmed.ncbi.nlm.nih.gov/25852189/
child terms: make automatic and manual assertion children for this.
@ValWood  - do these definitions look ok?

This sounds good to me. I'm not  great with  evidence codes so also copying in @mah11 who may need to know about the proposed  for historical  HTP curation reasons.
No worries about the timeframe, I know how it is. I sometimes return to tickets on my todo list after years 👍
totally my fault for not recording my PMID here!

Note to self PMID:26527280 courtesy of Midori

Revised plan: we are going to leave ECO:0000333 'sodium dodecyl sulfate polyacrylamide gel electrophoresis evidence' alone for now and just do the merge of the two western terms. Everything else stays as planned.

Hi @ValWood
As per the revised plan, the following changes have been made.

Changed the label of ECO:0000112 'western blot evidence' to "qualitative western immunoblotting evidence".
Merged ECO:0005602 'protein expression level evidence based on western blot' into "qualitative western immunoblotting evidence" (ECO:0000112).
Merged the automatic/manual assertion children of 'protein expression level evidence based on western blot' into
automatic/manual assertion children of "qualitative western immunoblotting evidence".
Merged ECO:0007183 into ECO:0000279
Merged ECO:0007287 into ECO:0007306
Created a new child term "quantitative western immunoblotting evidence" (ECO:0006169) under "qualitative western immunoblotting evidence".
Children under this:
quantitative western immunoblotting evidence used in automatic assertion (ECO:0006171)
quantitative western immunoblotting evidence used in manual evidence (ECO:0006170)
Added one more parent 'protein expression evidence' (ECO:0000010) to "qualitative western immunoblotting evidence".

Closing the ticket now but reopen if needed.
Thanks,
Suvvi


Creating new room

Added a plus icon and the search icon.

Merged! Thanks for completing this @Deepshikha99  :rocket:


Need a mechanism to determine build's state (based on the build ID) (…

…enhancement #1254)

Description
This issues implements a new feature described in #1254, The idea is that users can check the status of the requested build.
New feature added to track the requested build state, from the user perspective the following CLI commands were added:
pyrsia build status --id <BUILD ID>
Few examples of returned messages:
Build status for 'b024a136-9021-42a1-b8de-c665c94470f4' is 'RUNNING'
Build status for 'b024a136-9021-42a1-b8de-c665c94470f4' is 'SUCCESS'
Build status for 'f1548c9a-f2ee-46b9-8993-eed0a8e5c239' is 'FAILED'
When the build ID is not found or expired:
Build status for 'b024a136-9021-42a1-b8de-c665c94470f4' was not found. Additional info related to the build might be available via 'pyrsia inspect-log' command.
The code follows patterns and style of other similar features including the "build request/start". It reuses the already existing API but also adds functionality to the CLI, build service, network and node API. New unit tests added also there is a pending integration test PR: pyrsia/pyrsia-integration-tests#18
Fixes pyrsia/pyrsia#
The new feature is described here: #1254
This PR is a first step towards a more useful "build status" feature. Eventually, we should be able to add functionality which fetches the build logs and more. It should be relatively easy to add it based on this PR as long as the pipeline/build service supports it (provides API to get the build logs, etc).
PR Checklist

[x] I've read the contributing guidelines.
[x] I've read "What is a Good PR?"
[x] I've included a good title and brief description along with how to review them.
[x] I've linked any associated an issue.

Code Contributions

[x] I've built the code cargo build --all-targets successfully.
[x] I've run the unit tests cargo test --workspace and everything passes.

@karolh2000 did you notice the clippy error on GhA? https://github.com/pyrsia/pyrsia/actions/runs/3605219431/jobs/6075385186#step:6:1213

@erwin1 I think clippy 1.65 is broken and it "panics" and fails when it builds the sources (logs below). It works fine with clippy nightly (1.67, rustup default nightly) so I'm assuming this is clippy related problem and we might have to turn off clippy until 1.67? BTW I created a new clippy issue for the problem (https://github.com/rust-lang/rust-clippy/issues/10034)
CLIPPY 1.67 (FAILS)
karolh@karolh-mac pyrsia % cargo clippy
    Checking pyrsia v0.2.1 (/Users/karolh/trunk/karolh2000/pyrsia)
error: internal compiler error: compiler/rustc_middle/src/ty/subst.rs:626:9: type parameter `Self/#0` (Self/0) out of range when substituting, substs=[]

thread 'rustc' panicked at 'Box<dyn Any>', /rustc/897e37553bba8b42751c67658967889d11ecd120/compiler/rustc_errors/src/lib.rs:1462:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust-clippy/issues/new

note: Clippy version: clippy 0.1.65 (897e3755 2022-11-02)

query stack during panic:
#0 [analysis] running analysis passes on this crate
end of query stack
error: could not compile `pyrsia`

CLIPPY 1.67 nightly (SUCCESSFUL, the warnings are not related to the PR/changes)
   Compiling pyrsia v0.2.1 (/Users/karolh/trunk/karolh2000/pyrsia)
error[E0277]: the type `UnsafeCell<backtrace::Capture>` may contain interior mutability and a reference may not be safely transferrable across a catch_unwind boundary
  --> src/artifact_service/storage.rs:51:50
   |
51 |       let panic_wrapper = std::panic::catch_unwind(|| match result {
   |  _________________________------------------------_^
   | |                         |
   | |                         required by a bound introduced by this call
52 | |         Ok(unwrapped) => unwrapped,
53 | |         Err(error) => {
54 | |             let msg = format!("Error initializing {}, error is: {}", label, error);
...  |
57 | |         }
58 | |     });
   | |_____^ `UnsafeCell<backtrace::Capture>` may contain interior mutability and a reference may not be safely transferrable across a catch_unwind boundary
   |
   = help: within `anyhow::error::ErrorImpl`, the trait `RefUnwindSafe` is not implemented for `UnsafeCell<backtrace::Capture>`
   = note: required because it appears within the type `backtrace::LazilyResolvedCapture`
   = note: required because it appears within the type `backtrace::Inner`
   = note: required because it appears within the type `Backtrace`
   = note: required because it appears within the type `std::option::Option<Backtrace>`
   = note: required because it appears within the type `anyhow::error::ErrorImpl`
   = note: required for `NonNull<anyhow::error::ErrorImpl>` to implement `UnwindSafe`
   = note: required because it appears within the type `anyhow::ptr::Own<anyhow::error::ErrorImpl>`
   = note: required because it appears within the type `anyhow::Error`
   = note: required because it appears within the type `Result<T, anyhow::Error>`
note: required because it's used within this closure
  --> src/artifact_service/storage.rs:51:50
   |
51 |     let panic_wrapper = std::panic::catch_unwind(|| match result {
   |                                                  ^^
note: required by a bound in `std::panic::catch_unwind`

error[E0277]: the type `UnsafeCell<backtrace::Capture>` may contain interior mutability and a reference may not be safely transferrable across a catch_unwind boundary
  --> src/util/keypair_util.rs:53:50
   |
53 |       let panic_wrapper = std::panic::catch_unwind(|| match result {
   |  _________________________------------------------_^
   | |                         |
   | |                         required by a bound introduced by this call
54 | |         Ok(unwrapped) => unwrapped,
55 | |         Err(error) => {
56 | |             let msg = format!("Error initializing {}, error is: {}", label, error);
...  |
59 | |         }
60 | |     });
   | |_____^ `UnsafeCell<backtrace::Capture>` may contain interior mutability and a reference may not be safely transferrable across a catch_unwind boundary
   |
   = help: within `anyhow::error::ErrorImpl`, the trait `RefUnwindSafe` is not implemented for `UnsafeCell<backtrace::Capture>`
   = note: required because it appears within the type `backtrace::LazilyResolvedCapture`
   = note: required because it appears within the type `backtrace::Inner`
   = note: required because it appears within the type `Backtrace`
   = note: required because it appears within the type `std::option::Option<Backtrace>`
   = note: required because it appears within the type `anyhow::error::ErrorImpl`
   = note: required for `NonNull<anyhow::error::ErrorImpl>` to implement `UnwindSafe`
   = note: required because it appears within the type `anyhow::ptr::Own<anyhow::error::ErrorImpl>`
   = note: required because it appears within the type `anyhow::Error`
   = note: required because it appears within the type `Result<T, anyhow::Error>`
note: required because it's used within this closure
  --> src/util/keypair_util.rs:53:50
   |
53 |     let panic_wrapper = std::panic::catch_unwind(|| match result {
   |                                                  ^^
note: required by a bound in `std::panic::catch_unwind`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `pyrsia` due to 2 previous errors
warning: build failed, waiting for other jobs to finish...

PR to disable the clippy warnings: https://github.com/pyrsia/pyrsia/pull/1378

All issues and conflicts resolved, please take a look @tiainen @jperedadnr, thanks!

I've tested the functionality and it all seems to work fine. I got the correct response both when asking the build status from an authorized node and a regular node.
I only have one remark: wouldn't it be nice to also propagate the error message back to the client in case of a failure? Currently, the actual error is ignored: https://github.com/pyrsia/pyrsia/pull/1360/files#diff-459f5dc9cbc7765c794b21667a5ccea2a16aa313e7f99a0ed035756d62a6086fR267

I've tested the functionality and it all seems to work fine. I got the correct response both when asking the build status from an authorized node and a regular node.
I only have one remark: wouldn't it be nice to also propagate the error message back to the client in case of a failure? Currently, the actual error is ignored: https://github.com/pyrsia/pyrsia/pull/1360/files#diff-459f5dc9cbc7765c794b21667a5ccea2a16aa313e7f99a0ed035756d62a6086fR267

@tiainen Makes sense, will take a look and improve the failure error handling, thanks.

I've tested the functionality and it all seems to work fine. I got the correct response both when asking the build status from an authorized node and a regular node.
I only have one remark: wouldn't it be nice to also propagate the error message back to the client in case of a failure? Currently, the actual error is ignored: https://github.com/pyrsia/pyrsia/pull/1360/files#diff-459f5dc9cbc7765c794b21667a5ccea2a16aa313e7f99a0ed035756d62a6086fR267

@tiainen Makes sense, will take a look and improve the failure error handling, thanks.

The suggested changes implemented, the string contains the BuildStatus::Failure message.

tested and works nicely. one additional improvement (for a new issue) could be the option to chose for processing friendly output from the CLI, so one can more easily get the build ID.
As a side note: I had a bug in the config edit that is now fixed on main. Maybe you should update and let the tests run again before merging.


feat: add updated kzg file to bellatrix genesis

wrong URL!
its https://raw.githubusercontent.com/ethereum/consensus-specs/dev/presets/mainnet/trusted_setups/trusted_setup_4096.json


chore(test): Add unit test and integration test

Description
We need set up the test process and add more unit/integration test cases. There are many interfaces in the code, thus it should be easy to mock them and test the main logic.
Acceptance Criteria

[ ] test for IR and frontend
[x] test for cache
[ ] test for docker client

Closed in #804


New v15 entries

ARK: Survival Envolved (Thanks for the cache https://github.com/Hebarch)
Assassin's Creed Brotherhood
Assassin's Creed Revelations
Grand Theft Auto: San Andreas (2004)
Resident Evil 4
Rise of the Tomb Raider
Tomb Raider

I also noticed now that you added files to v15 folders (except ARK).
Could you instead edit Readme.md files without the new folders and move x.dxvk-cache.md files?
Example: dxvk-caches/Tomb Raider/Tomb Raider/ v15/ Readme.md and
dxvk-caches/Tomb Raider/Tomb Raider/ v15/ TombRaider.dxvk-cache.md


MIOpen using wrong ISA for certain convolution operations

I've just updated MIOpen to the latest version (package version <IP_ADDRESS>05), which now apparently uses the wrong ISA for my GPU. I normally work with PyTorch for all my projects, however, this issue occurs while MIOpen is tuning the Perf. Db before even running my python code. As soon as it tries to do so, it repeatedly runs into errors similar to this:
<instantiation>:4:3: error: instruction not supported on this GPU                 s_mul_hi_u32 s[tiles_w], div_const_1_4, s[tiles_w]                 ^ <instantiation>:2:2: note: while in macro instantiation         _s_div_const_u32_u16 s[tiles_w], s[tiles_w], 4         ^ <stdin>:796:2: note: while in macro instantiation         _s_ceil_u32 s[tiles_w], s[S], %xformx_f_size         ^ <instantiation>:4:3: error: instruction not supported on this GPU                 s_mul_hi_u32 s[tiles_h], div_const_1_4, s[tiles_h]                 ^ <instantiation>:2:2: note: while in macro instantiation         _s_div_const_u32_u16 s[tiles_h], s[tiles_h], 4         ^ <stdin>:797:2: note: while in macro instantiation         _s_ceil_u32 s[tiles_h], s[R], %xformy_f_size         ^ <instantiation>:8:2: error: instruction not supported on this GPU         v_sub_u32         v[vtmp+1+3],   0,            v[vtmp+1+1]         ^ <stdin>:857:2: note: while in macro instantiation         ceil_2_32_div_u16 v[vtmp], v[vtmp], vtmp+1, stmp
This goes on for several pages, full log is here: https://pastebin.com/dughVHes
I'm running an RX 470, though the error also occurs on a RX 560.
The only way I've found to replicate this is to try to run a convolution with exactly 3 output channels and 128 input channels, otherwise, this error occurs seemingly at random, as most operations complete successfully and only some trigger the error (as seen in the full log).

@zjing14 Please take a look.

@daniellowell The Conv3x3AsmWrW is not supported on RX4/560 (i.e., Fiji/Polaris Arch). We need to disable the kernel on Fiji platform. Will create a PR.

@89Mods We will fix this in the next release. In the mean time can you see if setting the environment variable:
MIOPEN_DEBUG_GCN_ASM_KERNELS=0
unblocks you.

@daniellowell I tried setting the environment variable as you suggested, but while it does hide the errors, nothing works correctly anymore. I also tried downgrading back to MIOpen 2.0.0, but doing that now causes a Segfault in PyTorch, so I'm pretty much stuck with the broken 2.0.1 release.

Resolved in 2.1.0

@89Mods please try the latest release. If your issue is not resolved please feel free to reopen this issue.


Improve error messages to include action name

Currently (as of v0.2.0), when an action fails, the resulting error message does not include the action name. Consequently, if the application runs many actions and one fails, then it's not immediately clear which action failed.

As part of resolving this issue, Chill's Error enum should become an opaque type and applications should instead use a new ErrorKind enum for distinguishing between different CouchDB errors such as, e.g., “not found” vs “document conflict.” This change would free the Error type to become a struct that would contain common fields for all error kinds, including something like an Option<&'static str> for describing the action that failed.


⚠ Bofrost.be has degraded performance

In 02a3d96, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1400 ms

Resolved: Bofrost.be performance has improved in 90fc18b.


chore: Update visualstudio.com non-redirected links

Closes #1884

@nschonni Thank you for for fixing these. I am merging this PR and it should be live soon.


iOS 13 SegmentedControl support

Library version: 1.0.2
iOS 13 introduced a new version of SegmentedControl with changes in API, and library does not support customizing it now. Every SegmentedControl made with it now looks like this:

tintColor property makes no effect on it's appearance anymore.

same prob with ios13 what to do now? any idea?

segmentedControl.selectedSegmentTintColor = .clear for iOS 13

segmentedControl.selectedSegmentTintColor = .clear
Only works on iOS 13.

What's the status on this! Nothing is working!

It looks like this component needs a re-work with all the new properties that iOS 13 brings to SegmentedControl. As you said, you are right, tintColor won't work anymore.

@ferrannp is it possible that these were fixed in the version on react native master since we haven't actually removed that component from RN yet (we were waiting for stable releases).

@cpojer I don't see tintColor fixed on RN 0.61.2 on iOS 13.

Here is a fix by @sammy-SC:
- (void)setTintColor:(UIColor *)tintColor
{
  [super setTintColor:tintColor];
  if (@available(iOS 13.0, *)) {
    [self setSelectedSegmentTintColor:tintColor];
    [self setTitleTextAttributes:@{NSForegroundColorAttributeName: [UIColor whiteColor]}
                        forState:UIControlStateSelected];
    [self setTitleTextAttributes:@{NSForegroundColorAttributeName: tintColor}
                        forState:UIControlStateNormal];
  }
}

It has to go into the module here as a PR: https://github.com/react-native-community/react-native-segmented-control/blob/master/ios/RCTSegmentedControl.m

There are more stuff we can do to UISegmentedControl  right now with iOS 13 @cpojer. I think it would be good to update it here and remove it from core (now core is fixed, here is not). @harisbaig100 are you around?

@ferrannp We'll remove it from RN soon!

@cpojer thank you but we would probably need a new maintainer here :)

ff

@cpojer @ferrannp
If it's not a problem, I'd like to help maintain this package.
Is there anything I can do to help?


put_object_stream reads stream to determine it's size

Describe the bug
When using async put_object_stream I assume that the stream will be readed part by part as in async mode, but in reality it reads the whole stream to determine the size first. For large files it leads to OOM errors.
To Reproduce
let (mut rx, mut tx) = tokio::io::duplex(65535); // tokio duplex
tokio::spawn(async move { loop  { tx.write_all(&[1,3,4,5,6]).await; } });
Bucket::put_object_stream(b, &mut rx, "/123.txt").await;

Expected behavior
Memory is not overflowing, data is written as you go.
Environment

Rust version: 1.69
lib version 0.33.0

Additional context

This seems to be covered by #346


calico/node is not ready: felix is not ready: Get http://localhost:9099/readiness: dial tcp <IP_ADDRESS>:9099: connect: connection refused

1.Basic environment
1.1 The internet
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp9s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 0c:c4:7a:4b:65:20 brd ff:ff:ff:ff:ff:ff
3: enp5s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 68:91:d0:60:cc:3a brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/22 brd <IP_ADDRESS> scope global enp5s0f0
       valid_lft forever preferred_lft forever
    inet6 fe80::6a91:d0ff:fe60:cc3a/64 scope link
       valid_lft forever preferred_lft forever
4: enp10s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 0c:c4:7a:4b:65:21 brd ff:ff:ff:ff:ff:ff
5: enp5s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 68:91:d0:60:cc:3b brd ff:ff:ff:ff:ff:ff
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:a2:4a:a9:a5 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global docker0
       valid_lft forever preferred_lft forever
7: kube-ipvs0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
...

1.2 DNS
nameserver <IP_ADDRESS>

1.3 /etc/hosts Mapping configuration
# cat /etc/hosts
<IP_ADDRESS> localhost
<IP_ADDRESS> k8s01

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
xxx.xx.x.xx1 apiserver.cluster.local
xxx.xx.x.xx1 k8s01
xxx.xx.x.xx2 k8s02
xxx.xx.x.xx3 k8s03
xxx.xx.x.xx4 k8s04
xxx.xx.x.xx5 k8s05

2.Abnormal
2.1 source
# kubectl get pods -n kube-system
NAME                                       READY   STATUS             RESTARTS   AGE
calico-kube-controllers-6b4c6ff56f-5lgpb   1/1     Running            0          14h
calico-node-25jm4                          0/1     CrashLoopBackOff   203        14h
calico-node-2kcfw                          0/1     CrashLoopBackOff   204        14h
calico-node-fwd88                          0/1     Running            213        14h
calico-node-kr24t                          0/1     CrashLoopBackOff   215        14h
calico-node-msqdn                          0/1     CrashLoopBackOff   204        14h
...

2.2 logs
# kubectl describe pod calico-node-25jm4 -n kube-system
...
Events:
  Type     Reason     Age                     From            Message
  ----     ------     ----                    ----            -------
  Warning  Unhealthy  14m (x1952 over 14h)    kubelet, k8s04  Readiness probe failed: calico/node is not ready: felix is not ready: Get http://localhost:9099/readiness: dial tcp <IP_ADDRESS>:9099: connect: connection refused
  Warning  BackOff    3m57s (x2392 over 14h)  kubelet, k8s04  Back-off restarting failed container

3.Ways that have been tried (but still not successfully resolved)
3.1 Regular expression specifies calico network card
# kubectl delete -f calico.yaml
# vim calico.yaml
...
            - name: IP_AUTODETECTION_METHOD
              value: "interface=enp.*|eth.*|en.*"
...
# kubectl apply -f calico.yaml

I configured through the above methods, but still can't solve this problem, I hope to get your help.thank you very much!

I think it is readiness issue

What calico version is this? Where did you get the calico manifest from?

Readiness won't cause the pods to crashloop. Though the liveness probes would.
I think we need logs from the failing calico/node pods in order to diagnose this. @tscswcn can you provide those?

 k get events -n calico-system -w
LAST SEEN   TYPE      REASON                   OBJECT                                          MESSAGE
3m14s       Normal    Scheduled                pod/calico-kube-controllers-55b67d5544-kncnd    Successfully assigned calico-system/calico-kube-controllers-55b67d5544-kncnd to ip-10-60-66-177.eu-central-1.compute.internal
3m14s       Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "5dbe288d04afa894c52d62a317c1a1a1389cb532b16c1505893894fe256526c6": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
3m3s        Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "d5d9be67f3611a6e2c4982b5de56f5034e072242168da71e63e54bc49c80aa7d": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
2m49s       Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "14e0dfa9f207d51d87607b331dfc49c0b4c3ebd4fdf0456edea5bd50fb4ee35c": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
2m37s       Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "f7e3bbb8db43435d70f53ac1e6de1f73db2edcd51fdfe372ef68e148872b624c": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
2m26s       Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "36744c19c1a0fa8bbb3c2a6d22998e8dd641c1ded6584476a1dd852ac289ae68": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
2m14s       Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "137c9abd3ec8b7b2d4d0332b54f1865489646b367d2236e82a1aae0f11f4f84f": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
2m1s        Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "7a7c4004bbabe480dd0e8d55008a7717b4559864970da895316b657ab012816c": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
106s        Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "e276e7eeebd323995f2c31bed240179be59665981f239c9e93a1c4daf4fce162": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
92s         Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "ea6baf7d056bf1820b5b0f1d66878e0381e950fad0bf737a6cac59903fbfc0ae": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
4s          Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "11bfee8532ecf9586f435b29acc86586cf819f0b1a8c0fb96a579c550ba1296e": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
3m14s       Normal    SuccessfulCreate         replicaset/calico-kube-controllers-55b67d5544   Created pod: calico-kube-controllers-55b67d5544-kncnd
3m14s       Normal    ScalingReplicaSet        deployment/calico-kube-controllers              Scaled up replica set calico-kube-controllers-55b67d5544 to 1
3m14s       Normal    Scheduled                pod/calico-node-cp8hh                           Successfully assigned calico-system/calico-node-cp8hh to ip-10-60-66-177.eu-central-1.compute.internal
3m14s       Normal    Pulled                   pod/calico-node-cp8hh                           Container image "docker.io/calico/pod2daemon-flexvol:v3.22.0" already present on machine
3m14s       Normal    Created                  pod/calico-node-cp8hh                           Created container flexvol-driver
3m14s       Normal    Started                  pod/calico-node-cp8hh                           Started container flexvol-driver
3m13s       Normal    Pulled                   pod/calico-node-cp8hh                           Container image "docker.io/calico/node:v3.22.0" already present on machine
3m13s       Normal    Created                  pod/calico-node-cp8hh                           Created container calico-node
3m13s       Normal    Started                  pod/calico-node-cp8hh                           Started container calico-node
3m12s       Warning   Unhealthy                pod/calico-node-cp8hh                           Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp <IP_ADDRESS>:9099: connect: connection refused
3m14s       Normal    Scheduled                pod/calico-node-f944f                           Successfully assigned calico-system/calico-node-f944f to ip-10-60-20-88.eu-central-1.compute.internal
3m14s       Normal    Pulled                   pod/calico-node-f944f                           Container image "docker.io/calico/pod2daemon-flexvol:v3.22.0" already present on machine
3m14s       Normal    Created                  pod/calico-node-f944f                           Created container flexvol-driver
3m14s       Normal    Started                  pod/calico-node-f944f                           Started container flexvol-driver
3m13s       Normal    Pulled                   pod/calico-node-f944f                           Container image "docker.io/calico/node:v3.22.0" already present on machine
3m13s       Normal    Created                  pod/calico-node-f944f                           Created container calico-node
3m13s       Normal    Started                  pod/calico-node-f944f                           Started container calico-node
3m12s       Warning   Unhealthy                pod/calico-node-f944f                           Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp <IP_ADDRESS>:9099: connect: connection refused
3m14s       Normal    Scheduled                pod/calico-node-kztsh                           Successfully assigned calico-system/calico-node-kztsh to ip-10-60-53-225.eu-central-1.compute.internal
3m14s       Normal    Pulled                   pod/calico-node-kztsh                           Container image "docker.io/calico/pod2daemon-flexvol:v3.22.0" already present on machine
3m14s       Normal    Created                  pod/calico-node-kztsh                           Created container flexvol-driver
3m14s       Normal    Started                  pod/calico-node-kztsh                           Started container flexvol-driver
3m13s       Normal    Pulled                   pod/calico-node-kztsh                           Container image "docker.io/calico/node:v3.22.0" already present on machine
3m13s       Normal    Created                  pod/calico-node-kztsh                           Created container calico-node
3m13s       Normal    Started                  pod/calico-node-kztsh                           Started container calico-node
3m12s       Warning   Unhealthy                pod/calico-node-kztsh                           Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp <IP_ADDRESS>:9099: connect: connection refused
3m14s       Normal    SuccessfulCreate         daemonset/calico-node                           Created pod: calico-node-kztsh
3m14s       Normal    SuccessfulCreate         daemonset/calico-node                           Created pod: calico-node-f944f
3m14s       Normal    SuccessfulCreate         daemonset/calico-node                           Created pod: calico-node-cp8hh
3m6s        Normal    Scheduled                pod/calico-typha-6cbdfd7b58-psf4w               Successfully assigned calico-system/calico-typha-6cbdfd7b58-psf4w to ip-10-60-53-225.eu-central-1.compute.internal
3m5s        Normal    Pulling                  pod/calico-typha-6cbdfd7b58-psf4w               Pulling image "docker.io/calico/typha:v3.22.0"
3m1s        Normal    Pulled                   pod/calico-typha-6cbdfd7b58-psf4w               Successfully pulled image "docker.io/calico/typha:v3.22.0" in 4.478576474s
3m          Normal    Created                  pod/calico-typha-6cbdfd7b58-psf4w               Created container calico-typha
3m          Normal    Started                  pod/calico-typha-6cbdfd7b58-psf4w               Started container calico-typha
3m14s       Normal    Scheduled                pod/calico-typha-6cbdfd7b58-xmmqs               Successfully assigned calico-system/calico-typha-6cbdfd7b58-xmmqs to ip-10-60-20-88.eu-central-1.compute.internal
3m14s       Normal    Pulling                  pod/calico-typha-6cbdfd7b58-xmmqs               Pulling image "docker.io/calico/typha:v3.22.0"
3m9s        Normal    Pulled                   pod/calico-typha-6cbdfd7b58-xmmqs               Successfully pulled image "docker.io/calico/typha:v3.22.0" in 4.144873054s
3m9s        Normal    Created                  pod/calico-typha-6cbdfd7b58-xmmqs               Created container calico-typha
3m9s        Normal    Started                  pod/calico-typha-6cbdfd7b58-xmmqs               Started container calico-typha
3m14s       Normal    SuccessfulCreate         replicaset/calico-typha-6cbdfd7b58              Created pod: calico-typha-6cbdfd7b58-xmmqs
3m6s        Normal    SuccessfulCreate         replicaset/calico-typha-6cbdfd7b58              Created pod: calico-typha-6cbdfd7b58-psf4w
3m15s       Normal    NoPods                   poddisruptionbudget/calico-typha                No matching pods found
3m14s       Normal    ScalingReplicaSet        deployment/calico-typha                         Scaled up replica set calico-typha-6cbdfd7b58 to 1
3m6s        Normal    ScalingReplicaSet        deployment/calico-typha                         Scaled up replica set calico-typha-6cbdfd7b58 to 2
0s          Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "eade90ec78643927bfa771a7da9a2ca7eec55e7d6c080c32456828b868656c6d": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
0s          Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "a1306d5cdc7c887ad11be590ac5ff072a339511193c08b3daac6526b7ed8e794": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
0s          Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "20a447d3635dacba3b1b88cefd2c4c20f66ccd7df0a8fb6b8c7d5f1fac93396c": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
0s          Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "59cfa0a0a402a69a4f5ff3cc8bc735eb50e20cf7edd5926c73a28e60a6882ebf": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
0s          Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "b10d27b4cf92b5d792133a7d4b8a02d1a9f80bcdc8249fb375026369a1fd7142": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
0s          Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "6494c197d9923de231c42052d8ce6e86f2595dbf58dcb318f3c243e63b40c46a": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
0s          Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "d4bfad5460b4f86e2eace88c141c67613b40aab8e8ed3e9fe462461043755454": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
0s          Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "8dd30cba050045bc1581d4eef98f867054b89738aad52caa23cad47eb70d4bec": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
0s          Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "e87a19a93c5d2dc91d06d11a5c092caee51b44be797a937d1acce1aa7f11dd65": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
0s          Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "11249ba03a564ecf82c055917a951e9dcc4f3dc11ce1a468d1753e29931f2972": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"
0s          Warning   FailedCreatePodSandBox   pod/calico-kube-controllers-55b67d5544-kncnd    (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "07eba007cfd52e203ca1cf41e5b1557662e2dadfed2be2bbd2f3b6b46e6df17c": add cmd: Error received from AddNetwork gRPC call: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"


feat: refactor xyk config

Related Issue
Fixes: #130  -->

This is a good start - but still requires additional effort.
And to be done properly - it requires changes in math package too - see issue comment
Closing for now. Can be resurrected later.


feat(example): adding auto-unseal example

Added a Terraform blueprints example for creating EKS cluster with Vault Add-On configured with Dynamo backend and KMS for auto-unseal.
Adding a test ALB ingress for accessing the Vault UI.
Moved .gitignore a level up to ignore for all subdirectories.

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.

@ksatirli Could you please take look?

I closed my PR for auto-unseal because this one is better.

+1 for this feature! When can we get this merged?


Debuff

how to increase the size of the enemy debuffs ?
Thank you!

You cant in game, heres how to do it in the layout lua file: https://github.com/Sticklord/oUF_Abu/blob/master/Layout.lua#L723

Thank you!  everything is working!


Refact GPU imfilter padding

This PR aims to optimize the imfilter_gpu function.
The idea is to remove the padding applied to the img and pad only the krn to have the same size of img.

Ok, so we can just return this last statement instead of assigning it back
to the result variable.
Em sex., 5 de ago. de 2022 11:19, ClaroHenrique @.***>
escreveu:

@.**** commented on this pull request.
In src/imfilter.jl
https://github.com/JuliaEarth/ImageQuilting.jl/pull/43#discussion_r938866639
:

recover result

finalsize = size(img) .- (size(krn) .- 1)
result = real.(result[CartesianIndices(finalsize)]) |> Array

The image is not padded, but the final result is smaller than the original
image.
For example, if one have a 20x10 image and a 5x4 kernel, the expected
result must be 16x7.
—
Reply to this email directly, view it on GitHub
https://github.com/JuliaEarth/ImageQuilting.jl/pull/43#discussion_r938866639,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZQW3JSBTQXMG2KWUPSM5LVXUPI5ANCNFSM55V7MXZA
.
You are receiving this because you commented.Message ID:
@.***>

Ok, so we can just return this last statement instead of assigning it back to the result variable. Em sex., 5 de ago. de 2022 11:19, ClaroHenrique @.> escreveu:
…
@.* commented on this pull request. ------------------------------ In src/imfilter.jl <#43 (comment)> : > + # recover result + finalsize = size(img) .- (size(krn) .- 1) + result = real.(result[CartesianIndices(finalsize)]) |> Array The image is not padded, but the final result is smaller than the original image. For example, if one have a 20x10 image and a 5x4 kernel, the expected result must be 16x7. — Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZQW3JSBTQXMG2KWUPSM5LVXUPI5ANCNFSM55V7MXZA . You are receiving this because you commented.Message ID: @.***>

done!

Awesome, will just wait for the tests to pass to merge 💯

Codecov Report

Merging #43 (58a75cf) into master (9d67727) will increase coverage by 0.23%.
The diff coverage is 0.00%.

:exclamation: Current head 58a75cf differs from pull request most recent head fc2af3e.  Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I will squash and merge given that the errors are unrelated to the changes in this PR.
The next PR can work on the preprocessing kernel to load once in GPU memory as we discussed.


Reloading the page after routing isn't working

When I reload a page after performing a routing action, for example, going to the About section and then hitting the reload button, it will display this error message:

I think I found a fix, but I haven't tried it yet. Here it is:

just found out that using Vite automatically fixed it


chore: update browserlists lock & update security package updates

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #538 (45392fa) into main (be36527) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #538   +/-   ##
=======================================
  Coverage   88.68%   88.68%
=======================================
  Files          68       68
  Lines        2527     2527
  Branches      731      731
=======================================
  Hits         2241     2241
  Misses        277      277
  Partials        9        9

Continue to review full report at Codecov.

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

moving this into another pr with datastore dependency update


add A.B. Paterson College

add A.B. Paterson College
https://www.abpat.qld.edu.au/

@WilliamDGH First stage of verification passed, official domain is abpat.qld.edu.au as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@WilliamDGH Thank you for your patience while waiting for a review and processing your request. Pull request merged.


[Feature Request] echo-message

A client-side implementation of the IRCv3 echo-message extension would facilitate the ability to log messages sent by the client/bot in conjunction with other chat messages.

See above for the implementation. Thanks :+1:


Can't add repositories as GitHub account prompt doesn't appear

Dev Home version
<IP_ADDRESS>
Windows build number
10.0.22621.1776
Other software
OS Build Version: 10.0.22621.1776.amd64fre.ni_release.220506-1250
.NET Version: .NET 6.0.16
Steps to reproduce the bug
I've installed Dev Home previously, and have skipped past a few of the important setup steps. But now, when I go to End-to-End setup of my dev device I choose to add a repository and then select Accounts.  Here I'm not prompted for a login to GitHub, and instead am left with no repositories...
Expected result
Prompt for GitHub authentication
Actual result
Empty list.
Included System Information
CPU: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
Physical Memory: 15.92GB (2.44GB free)
Processor Architecture: x64
Included Extensions Information
Extensions:
Microsoft.Windows.DevHome_<IP_ADDRESS>_x64__8wekyb3d8bbwe
Microsoft.Windows.DevHomeGitHubExtension_<IP_ADDRESS>_x64__8wekyb3d8bbwe

I've installed Dev Home previously
This makes me wonder if you encountered an issue with how the extension handled credentials.

Can you still repro this with the version from the store?


[Bug] Table has a vertical scrollbar even if content fits

Description
A table always has a vertical scrollbar, whether or not the content of the table fits within the page.
Expected Behavior
The table should never need a vertical scrollbar, because it should load just as many rows as it can display on a single page.
Steps to reproduce the behaviour:

Open any table
Try scrolling in the table

Here's a loom recording showing what I mean:

Important Details

Version: Self-Hosted v1.3.3
OS: MacOSX (client), Ubuntu (server)
Browser: Chrome, Firefox (probably others too)

@anthony-zhou thanks for the loom video and reporting this, we'll fix it.

Mentioned in #3248

#3966 is related?

https://user-images.githubusercontent.com/19254107/220286538-820db046-500d-4cd5-afe5-80926a2d5fb3.mov
Hi there, was there a fix for this ?
@Nikhil-Nandagopal @areyabhishek 🙏🏼

Thanks for reporting @rfenaux there is another bug which i am not able to find, but it's the same issue. We will prioritise this.

Tracking in #20831, @rfenaux please follow that issue

Following up on this update ...

@chriscupas please follow #20831 for updates


upgrade VenusOS 2.89 to 2.90 -> ERROR: no service template for dbus-serialbattery

You have a working dbus-serialbattery installation and upgrade your VenusOS on Cerbo from 2.89 to 2.9, dbus-serialbattery stops working:
root@einstein:~# tail -f /data/log/serial-starter/current
@4000000063303b520f814e94 ERROR: no service template for dbus-serialbattery

Device type: Cerbo

Firmware Version 2.89 to 2.9

BMS/Battery type: JKBMS

Cells: 2 x 16

Interface: usb-rs485

When you reboot in 2.89 all is working again. How to fix this?

On 2.9 the mount point / is read only:
root@einstein:/opt/victronenergy# touch test
touch: test: Read-only file system
root@einstein:/opt/victronenergy# mount
/dev/mmcblk1p2 on / type ext4 (ro,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=465376k,nr_inodes=116344,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /var/volatile type tmpfs (rw,relatime)
/dev/mmcblk1p5 on /data type ext4 (rw,noatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /service type tmpfs (rw,nosuid,nodev,mode=755)
overlay on /var/lib type overlay (rw,relatime,lowerdir=/var/lib,upperdir=/var/volatile/lib,workdir=/var/volatile/.lib-work)
root@einstein:/opt/victronenergy#
So the install script cannot reinstall it in /opt/victronenergy:
oot@einstein:~# sh /data/etc/dbus-serialbattery/reinstalllocal.sh
mkdir: can't create directory '/opt/victronenergy/dbus-serialbattery': Read-only file system
mkdir: can't create directory '/opt/victronenergy/service-templates/dbus-serialbattery': Read-only file system
cp: can't create '/opt/victronenergy/dbus-serialbattery/LICENSE': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/README.md': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/ant.py': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/battery.py': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/daly.py': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/dbushelper.py': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/disabledriver.sh': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/ecs.py': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/installlocal.sh': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/installqml.sh': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/installrelease.sh': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/jkbms.py': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/lifepower.py': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/lltjbd.py': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/minimalmodbus.py': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/mnb.py': No such file or directory
cp: omitting directory '/data/etc/dbus-serialbattery/qml'
cp: can't create '/opt/victronenergy/dbus-serialbattery/reinstalllocal.sh': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/renogy.py': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/revov.py': No such file or directory
cp: omitting directory '/data/etc/dbus-serialbattery/service'
cp: can't create '/opt/victronenergy/dbus-serialbattery/sinowealth.py': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/start-serialbattery.sh': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/util_max17853.py': No such file or directory
cp: can't create '/opt/victronenergy/dbus-serialbattery/utils.py': No such file or directory
cp: can't create directory '/opt/victronenergy/service-templates/dbus-serialbattery/log': No such file or directory
cp: can't create '/opt/victronenergy/service-templates/dbus-serialbattery/run': No such file or directory

on 2.89 the mount / is read write:
/dev/mmcblk1p3 on / type ext4 (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=465376k,nr_inodes=116344,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /var/volatile type tmpfs (rw,relatime)
/dev/mmcblk1p5 on /data type ext4 (rw,noatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
overlay on /service type overlay (rw,relatime,lowerdir=/opt/victronenergy/service,upperdir=/run/overlays/service,workdir=/run/overlays/work/service)
root@einstein:~#

Ok, with the following command you can change to read/write FS:
/opt/victronenergy/swupdate-scripts/remount-rw.sh

Thanks for the feedback. I'll do some test with upgrades to 2.90 this week and adjust the script to include the remound


Run Multiple Website Scopes From Sub Folders

Hi - Is it possible to run multiple website scopes from sub folders using warden? For example:
https://app.example.test/uk -> Points to UK website
https://app.example.test/us -> Points to US website
With this setup all category and product pages return 404s and the US website seems to redirect to the UK website e.g. https://app.example.test/us/product-url -> https://app.example.test/uk/us/product-url.
I have the subfolders created correctly as I have this working on a live environment. When debugging it seems that all requests are routed to pub/index.php rather than the subfolders index.php which I think is what is causing the issue.
Does anyone know how to get this kind of setup to work using Warden?

@ryan-copeland The config used here for M2 on Nginx is very close to the sample one in the Magento 2 application repo (see here: https://github.com/davidalger/warden/blob/develop/images/nginx/context/etc/nginx/available.d/magento2.conf) and it's this bit you're interested in:
location / {
    try_files $uri $uri/ /index.php$is_args$args;
}

A long while back, I setup an M2 production system to do country code specific stores like you mentioned, and I'm pretty sure the only thing I needed to do was load something like the following prior to the rest of the Magento 2 config for Nginx (so it took precedence over wildcards later in the magento2.conf file); something like this…
location /au/ {
    try_files $uri $uri/ /au/index.php$is_args$args;
}

location /ca/ {
    try_files $uri $uri/ /ca/index.php$is_args$args;
}

You should be able to use docker-compose configuration in .warden/warden-env.yml to mount a custom Nginx configuration into the nginx container which included the appropriate country code configurations alongside that main / location block.

@ryan-copeland , I just configured such a setup for a Magento1 shop.
Maybe that helps you.
So first you need to add a custom nginx config file to your setup. To do that, add .warden/warden-env-yml to you project root with the following content:
version: "3.5"
services:
  nginx:
    volumes:
      - ./.warden/nginx/custom.conf:/etc/nginx/default.d/custom.conf

Now you add a file .warden/nginx/custom.confin your project root with the following content:
location /uk {
    alias /var/www/html/;
    try_files $uri $uri/ @uk;

   location ~ \.php$ {
       try_files $uri =404;
       expires off;

       fastcgi_pass $fastcgi_backend;

       fastcgi_buffers 1024 4k;
       fastcgi_buffer_size 128k;
       fastcgi_busy_buffers_size 256k;
       fastcgi_read_timeout 3600s;

       include fastcgi_params;

       fastcgi_param HTTPS on;

       # Prevents these headers being used to exploit Zend_Controller_Request_Http
       fastcgi_param HTTP_X_REWRITE_URL "";
       fastcgi_param HTTP_X_ORIGINAL_URL "";

       fastcgi_param MAGE_RUN_CODE {{STORE_CODE_OF_YOUR_UK_STORE}};

       fastcgi_param SCRIPT_FILENAME  $realpath_root$fastcgi_script_name;
       fastcgi_param DOCUMENT_ROOT    $realpath_root;
       fastcgi_param SERVER_PORT      $http_x_forwarded_port;
   }

}

location @uk {
        rewrite /uk/(.*)$ /uk/index.php?/$1 last;
}

location /us {
    alias /var/www/html/;
    try_files $uri $uri/ @us;

   location ~ \.php$ {
       try_files $uri =404;
       expires off;

       fastcgi_pass $fastcgi_backend;

       fastcgi_buffers 1024 4k;
       fastcgi_buffer_size 128k;
       fastcgi_busy_buffers_size 256k;
       fastcgi_read_timeout 3600s;

       include fastcgi_params;

       fastcgi_param HTTPS on;

       # Prevents these headers being used to exploit Zend_Controller_Request_Http
       fastcgi_param HTTP_X_REWRITE_URL "";
       fastcgi_param HTTP_X_ORIGINAL_URL "";

       fastcgi_param MAGE_RUN_CODE {{STORE_CODE_OF_YOUR_US_STORE}};

       fastcgi_param SCRIPT_FILENAME  $realpath_root$fastcgi_script_name;
       fastcgi_param DOCUMENT_ROOT    $realpath_root;
       fastcgi_param SERVER_PORT      $http_x_forwarded_port;
   }

}

location @us {
        rewrite /us/(.*)$ /us/index.php?/$1 last;
}

See https://serversforhackers.com/c/nginx-php-in-subdirectory for further information about this approach.
At least in my case it worked fine. Please let me know if you find any issues.

Really useful! Thanks very much for this. Works well for M2 also.

I just ran into the need to set this up. I used David's snippet and followed @norgeindian's specific recommendations of where to put the configuration. Thanks for the help guys!


Deprecated defaultProps warning

When I try to use your lib in my React app a have some warnings in console:
"Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead."
I find solution here, you can use it: https://stackoverflow.com/questions/47774695/react-functional-component-default-props-vs-default-parameters
Please, fix it, because without solution I cannot use Lib for long-term projects

And also I found this warning:

The fixes for these warnings are minor, but they allow you to use your great and easy-to-use library in new projects

+1

+1


Fixed autocomplete on Japanese keyboards

Toggling autocorrect on Japanese keyboards breaks autocompletion.
If you try typing "@" on a Japanese keyboard toggling the autocomplete causes iOS to set the textView's text to an empty string.
My thought is that this is caused by the same mechanism that forces autocorrection to be committed when refreshing the first responder.
This fixes the issue.  Only ja-JP was affected.

Nope, didn't happen on Chinese, Russian, Arabic, etc. Only Japanese.


What are the plugin version requirements for docker versions?

Description
I can't figure out which version of the plugin will work with my docker service.
It would be helpful to mention which version can work with each release.
How to reproduce
I'm running the plugin on docker version 1.7 and it builds the image fine, but running on 1.10 causes unexpected exception.
What do you expect
A docker image to be built
What happened instead
Exception in the build phase
Software:

docker version: 1.10
docker-maven-plugin version: 0.4.0
maven version: 3.0.5

What are the errors you are getting on 1.10?

If I had to guess, I would speculate that the issues with 1.10 are related to https://github.com/spotify/docker-maven-plugin/issues/271#issuecomment-245276445.
I am going to close this issue on that theory but please re-open if the unexpected exception happens to have another cause.


dev/ic3: v3 writer

issue #3

reader_legacy is now able to read long int variable sections (node or cell indexed)
v3 writer is able to write them

new connectivity in v3 involves long int arrays which are saved as variables

NODE_GB_INDEX(node indexed)
CV_NODE_ROOT_0 and CV_NODE_ROOT_1 (cell indexed)
reading and writing long int sections was necessary

v2 to v3 transfer is not yet available since it needs the creation of these arrays

one very small box (generated from cfdtools from a v3 file) has restarted. v3 to v3 should be considered working


make compatible for usb boot

restore_root: change handling of device. Actually sd card is hard coded

This has no longer priority.


Add support for an escape hatch when properties fail

Right now you can't easily handle property get/sets that fail. The current design would require the developer to do something like this:
let foo = try obj._default.get_Foo()
While not the worse, you then would need to know which internal interface to invoke the property on Also, the internals aren't exposed (mainly due to export limit issues). While we could fix that issue for cmake, export limits are always going to be an issue for SPM, so I think it makes sense to not require the solution to expose all of those.
Solution
Provide a withFailingCall method that developers can use if they need to gracefully handle an error. What this does is it allocates a LastErrorHolder object, which is checked whenever a WinRT method fails. If there is a LastErrorHolder, it is given the error of the winrt method call. withFailingCall then checks for the error and throws the exception. Here is the implementation of the method:
public func withFailingCall<Result>(_ call: @autoclosure () -> Result) throws -> Result {
  let error = getLastError()
  defer { clearLastError() }
  let result = call()
  if let error = error.error {
    throw error
  }
  return result
}

Usage
Property get: let foo = try withFailingCall(obj.foo)
Property set: try withFailingCall(obj.foo = "invalid")
Changes

_tryWinRT methods were added for generated code to invoke. These methods capture the file and line of the caller and add that to the exception information so you know which line failed.
an error message is provided when one of these errors is unhandled, telling the developer of the possible workaround:

An example of the message:
test_component/ERROR.swift:263: Fatal error: Unhandled WinRT Error @ test_component/test_component.swift: 1098 - 0x80004001 - Not implemented

  Note: If this error is expected and needs to be handled, use `withFailingCall`

This is a very clever way to go about the problem but I am concerned about the overhead of this solution. I think the original let foo = try obj._default.get_Foo() was an okay solution (if non-default interfaces are also exposed). There is also an alternative way to solve this: generate get_Foo() (or _get_Foo) on the object directly and have the var foo accessors call it with try!.

what overhead are you referring to?


Looking for the right way to provide Static IPs for masters and workers.

I was not sure in which category this fit and hence the blank template.
Use case: I would like to have 1 master and 2 workers in my cluster. I want to create bond interfaces in the baremetalhosts and set static IPs for these workers.
Your documentation here: https://github.com/metal3-io/cluster-api-provider-metal3/blob/master/docs/getting-started.md is quite useful!
However in my case I would probably need to provide separate env variables for separate workers, right(As the kubeadmconfigtemplate is going to look different for both the hosts)? Is it possible to get the cluster configuration for such a use case, through clusterctl? Or would I need to manually edit the output from clusterctl to include two kubeadmconfig and reference them in two separate machine CRs.

Hi! You can unfortunately use static IP address allocations and MachineDeployment / KubeadmControlPlane only if your hardware is homogeneous. i.e. the same configuration can be applied on both hosts. So if your hardware is exactly the same with the same interface order and connectivity, then you can use a machine deployment with a KubeadmConfigTemplate and Metal3DataTemplate for the two workers. If it is not the case, then you cannot use MachineDeployment.
However, you can still create individual machines and their static configuration, that is supported. so you might not need to do any changes in you KubeadmConfig if you use a Metal3DataTemplate or directly give the networkdata secret in your Metal3Machine.
Bonds are supported in Metal3DataTemplates and networkdata secrets (unfortunately still untested though).

Got it. Will provide and test bond network interface information through Metal3DataTemplate and create separate machines which have same kubeadmconfig.


Add model name in generator.yaml

Description of changes:
This PR is to add the model name, states, in generator.yaml of the sfn-controller.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@JamesJHPark , can you also execute the make build-controller for this controller after updating the generator.yaml ?

/lgtm


add gorm or sqlx datasource support

What would you like to be added:
Why is this needed:
add go orm support as plugin

add go orm support as plugin

这个给我吧

pls assign me

z在sample项目提交


There is no directive with "exportAs" set to "matHorizontalStepper

please help me
    "@angular/animations": "^5.2.7",
    "@angular/cdk": "^5.2.4",
    "@angular/common": "^5.2.7",
    "@angular/core": "^5.2.7",
    "@angular/flex-layout": "^5.0.0-beta.13",
    "@angular/forms": "^5.2.7",
    "@angular/http": "^5.2.7",
    "@angular/material": "^5.2.4",

There is no directive with "exportAs" set to "matHorizontalStepper" ("
				<mat-horizontal-stepper [linear]="isLinear" [ERROR ->]#stepper="matHorizontalStepper">
				  <mat-step [stepControl]="firstFormGroup">
				    <form [formG"): ng:///AppModule/DatasourcesUploadComponent.html@11:48

Closing this issue as it does not follow the issue template. Please file a new issue that follows the template, which gives the team the information needed to investigate

Check it once whether you missed it to import {MatStepperModule} from '@angular/material/stepper'  in your app.module.ts (root module or you submodule)


Support Pixi 7

Is there a plan to support Pixi 7?

The line that is giving me problems right now for pixiv7 is https://github.com/pixijs/graphics-smooth/blob/7b5d86559c86c5534645fca45d01f125b49854b1/src/SmoothGraphics.ts#L711
It seems renderer no longer stores/exposes the options used to create it so we can't read the antialias setting :(

move it to the setting and set to FALSE. This plugin is made to evade antialias webgl setting.


Add showcase Sake Pool

Name: Wallet Analytics
Description: Helpful tool that displays number of wallets that hold specific amount of ada.
Link:   SakePool
Tags:

analytics

@rdlrt @os11k Thank you for the feedback. I've made a mistake by uploading a completely wrong information, I've made some new changes now.

Closing this because of too few approvals.


Difference numberH with just number on UI at screen

Hi.
ScreenUtil().setWidth(540)  (sdk>=2.6 : 540.w) //Adapted to screen width
540.w means 540 px? as you mentioned on document . Right?
 Right?
Now if i want to use your library, How could i do that ?Because I am using like this:
              child: Container(
                height: 34.h, // returns 9.147619047619047

The height of container 34.h is different with 34.0!!
This is height: 34.0:
https://pasteboard.co/JxKBmlt.png
height: 34.h:
https://pasteboard.co/JxKBBCN.png
I initialized like this:
 ScreenUtil.init(context,
        designSize: Size(1440, 2880), allowFontScaling: false);

Designer ask us that container's height at  Size(1440, 2880) device size must be 34, but 34.h is not right.
https://pasteboard.co/JxKSLln.png
34 pixel converted in to 9.1

34 is a dp !
child: Container(
                  height: 34.0,

xx.h
xx.w
The unit of xx is px on the design draft.
The input unit is px, and the returned result unit is dp

Thank. I think i got it.
The designer give us design draft with adobe xd that units is px but flutter unit is dp.
When we add height: 34.0, means I added 34 dp not px.
If i want to achieve px must 34 dp multiplied with pixelRatio .Right?

Yes, it returns dp.
And, if there is no additional description, generally dp is returned


dependency injection

Please describe the purpose of this pull request.
This is related to spreadsheet id #1
The goal here is to move a version-managed router with dependency injection for all the deps.
Why is dependency injection good here?
pragmatically, it makes the code testable. Without injection points testing the code is extremely complex and brittle, and in turn adding new features is super slow and difficult. Injecting the db, actor etc makes those things trivial at test time.
What is going on here?!?!
1. Dependency injection
for elements like the sync server and the current user that should be injected at runtime, we are using callables that return the assets from utilities. (note: at the moment utilities are scattered, they should live in a single module soon). This means that in testing these deps can easily be swapped out for a mocked server or a seeded user, so the test code only tests the mechanics under test (and not all the setup boilerplate).
2. API Versioning
You'll see a pattern in app.py that is aliasing the v1 version folder. The idea is whichever the latest version of the API is, that will respond to:

the bare route
the route by name (ie /v2/users)
the route with latest (ie /latest/users)
this means breaking changes to the API are not breaking, as long as the consumers pinned their routes. It also makes parallel route versions extremely clear in the code, with routes/v1/users.py as the v1 route, and routes/v2/users.py as the v2.

3. No User Auth
this needs to get done and finished next, but isn't happening in this PR. bits of semi-auth are scattered all over and they need to be centralized and refined and then applied as one correct auth scheme, so this PR will go only so far as to cut them out when they are in the way.

OOPS -there's already a PR for this #1537


Window only dismisses when another window gains focus

Problem:
When I click on another window, the EB window closes, but if for example I click on the desktop background, or my panel, it stays put.
Suggested Change:
Maybe it can watch for any click outside its window space and then close?

Fixed in #6 v0.0.11


feat: Added in log analytics integration to cluster

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign chrismellard
You can assign the PR to them by writing /assign @chrismellard in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@chrismellard: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr
a742f78612c4e5de4375e86394db77332f2495af
link
/retest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@chrismellard: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr
8cfa7154fbeb244c793496765a94125bf1a611fd
link
/retest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Add a "fall damage" cost or let us decide up to which health we want him to fall

Or please tell me where to find the corresponding code where I could implement this!
I am not new to programming at all but I totally am to NodeJS, hence I don't quite understand where some of the code originates... :)

There is already the option maxDropDown in movements that you can edit. It defaults to 4 blocks, but you can increase it.

There is already the option maxDropDown in movements that you can edit. It defaults to 4 blocks, but you can increase it.


Can you please provide any syntax or snippet for selecting dates by range

There is no way to select dates by range, but you can try to manage it with the dayClick function.
When user select 2 dates, you change your ng-model to add all dates between.
Not tested but you could try :)


To people who care about this project. Recommend use ts-whammy.

First, say thanks to @antimatter15 write this magic project whammy.
But this project is old school and event without maintain.
So i rewrite a new version of whammy call ts-whammy.
ts-whammy only include the core function of whammy then with modern frontend technology stack.
Welcome issue and PR or any other contribution.
Thanks, Love everybody.

ts-whammy has many online demos and fix current issue.
https://akimyou.github.io/ts-whammy/demo1/
https://akimyou.github.io/ts-whammy/demo2/
Thanks, Love everybody.


Error rendering report: instance has been daemonized

Hello,
Im trying  to fallow the example that you have in the demos with dotnet core and im executing this code on my controller:
var rs = new LocalReporting()
                .Configure(cfg => cfg.FileSystemStore())
                .UseBinary(JsReportBinary.GetBinary())
                .AsUtility()
                .Create();

            var report = await rs.RenderByNameAsync("Invoice", new
            {
                number="123",
                seller =new{name="Mayko Estevez",road="La nunnez",country="Dominican Republic" }

            });

I referenced the studio project to my webproject, and when i call the controller i get this error:
An unhandled exception occurred while processing the request.
JsReportBinaryException: Error rendering report: instance has been daemonized and initialized successfully (pid: 9280)rendering has finished with errors:Error: An error occurred while trying to execute the command: at onCriticalError ([eval]:36106:25) at [eval]:36061:13 at tryCatcher ([eval]:9718:23) at Promise._settlePromiseFromHandler ([eval]:38241:31) at Promise._settlePromise ([eval]:38298:18) at Promise._settlePromise0 ([eval]:38343:10) at Promise._settlePromises ([eval]:38418:18) at Async._drainQueue ([eval]:4650:16) at Async._drainQueues ([eval]:4660:10) at Immediate.Async.drainQueues [as _onImmediate] ([eval]:4534:14) at processImmediate [as _immediateCallback] (timers.js:396:17) {"originalError":{"remoteStack":"Error: Asset Invoice styles.css not found\n at jsreportRuntime.js:123990:15\n at tryCatcher (jsreportRuntime.js:47185:23)\n at Promise._settlePromiseFromHandler (jsreportRuntime.js:129736:31)\n at Promise._settlePromise (jsreportRuntime.js:129793:18)\n at Promise._settlePromise0 (jsreportRuntime.js:129838:10)\n at Promise._settlePromises (jsreportRuntime.js:129917:18)\n at Async._drainQueue (jsreportRuntime.js:42117:16)\n at Async._drainQueues (jsreportRuntime.js:42127:10)\n at Immediate.Async.drainQueues [as _onImmediate] (jsreportRuntime.js:42001:14)\n at processImmediate [as _immediateCallback] (timers.js:396:17)"}}(Original) Error: Error during rendering report: Asset Invoice styles.css not found at [eval]:39138:23 at ConcatStream. ([eval]:44860:43) at emitNone (events.js:72:20) at ConcatStream.emit (events.js:166:7) at finishMaybe ([eval]:4229:14) at afterWrite ([eval]:4115:3) at nextTickCallbackWithManyArgs (node.js:486:18) at process._tickCallback (node.js:384:17) {"remoteStack":"Error: Asset Invoice styles.css not found\n at jsreportRuntime.js:123990:15\n at tryCatcher (jsreportRuntime.js:47185:23)\n at Promise._settlePromiseFromHandler (jsreportRuntime.js:129736:31)\n at Promise._settlePromise (jsreportRuntime.js:129793:18)\n at Promise._settlePromise0 (jsreportRuntime.js:129838:10)\n at Promise._settlePromises (jsreportRuntime.js:129917:18)\n at Async._drainQueue (jsreportRuntime.js:42117:16)\n at Async._drainQueues (jsreportRuntime.js:42127:10)\n at Immediate.Async.drainQueues [as _onImmediate] (jsreportRuntime.js:42001:14)\n at processImmediate [as _immediateCallback] (timers.js:396:17)"}
Any help would be appreciate, thanks

test


0.20.21

The results of load testing for the test network.
test.1.pocketnet.app
2 VCPU
4 GB RAM
SSD

threads=10
workqueue=100

duration 1 hour

Test #
Threads /  TX per sec
Count
Time AVG (ms)
Time MAX (ms)
Time MIN (ms)
RPC Pool  exceeded

1
4 / 2
6680
134.7
19353
88
0

2
8 / 1
23903
182
7364
87
0

3
16 / 0.5
64191
375
20349
86
0

4
32 / 0.25
102505
748
66390
87
0

The method of generating a transaction in the test network - pocketdb/web/PocketTransactionRpc.h::GenerateTransaction
The following types of transactions were used in equal proportions:
Comment
Post
Rating
Subscription


Re-use big.Int in DecomposePQ

Pull Request Test Coverage Report for Build 418957671

30 of 30 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 32.736%

Totals

Change from base Build 418797360:
0.3%

Covered Lines:
1663

Relevant Lines:
5080

💛  - Coveralls


datacube: application infrastructure improvements

@akphi  as mentioned, lets split bump dependencies into its own PR so the team is aware of what has changed. makes it hard if it is buried under 146 changes of repl. those changes affect the rest of the application and not just repl.


internal: Record attribute calls on assoc items in TraitData and ImplData

Fixes https://github.com/rust-analyzer/rust-analyzer/issues/11228

bors r+


⚠ CodePush has degraded performance

In 4a0c363, CodePush (https://codepush.appcenter.ms/v0.1/public/codepush/update_check?deployment_key=Fzqu71x4FXhOaKcAiwpqXkFQddjgYl2dIUW2K&app_version=4.4.1) experienced degraded performance:

HTTP code: 200
Response time: 11956 ms

Resolved: CodePush performance has improved in 1cee9a8.


Feature/ledger error reporting

Please ignore this, I accidentally sent a PR to the official romeo repo rather than the Ledger one!


Create ability to embed bins elsewhere

Allow users to embed their bins on other sites easily by copying and pasting an embed code

done