On-demand policy wildcarding

Replace the current model of mass L7 wildcarding with on-demand wildcarding to allow for redirecting some but not all selectors for a given L4 filter.
L4 filters without L7 rules are now wildcarded either when merged with L4/L7 rules, or when used by the L7 proxies.
Some context for reviewing:

The functionality of L4Filter.CachedSelectors has been merged into the L4Filter.L7RulesPerEp (which has been renamed as L7RulesPerSelector). This is needed to efficiently keep track of which selectors have L7 rules and which not. The latter case is represented by a nil value in the map.
L7 proxy code dealing with L7RulesPerEp has been modified to threat nil values as L7 wildcards (DNS, Kafka, Envoy)
L7 wildcarding rules are generated on-demand when merging a non-L7 L4 rule with a L4/L7 rule.
The above lead to sometimes surprising unit test changes, which requires careful validation.
L4Filter.ToKeys() has been renamed as L4Filter.ToMapState as it now returns a map (MapState) instead of just the keys. Map entries tell if the entry needs L7 redirection or not. This makes it possible for a single L4 filter to create redirects for some of the allowed security IDs, but not necessarily all of them.
Tracking of MapState entries now relies on each CachedSelector tracked by an L4Filter to be in the L7RulesPerSelector map. nil vs. non-nil value in the map is used to determine if the new map entry needs redirection or not. This is then used to test if the proxy port value needs to be set, so that even if the L7Proxy type of the L4 filter is set, selectors without L7 rules do not generate proxy redirection in the bpf policy map.
These changes mean that L3-dependent L7 processing in the proxy now relies on L3/L4 entries in addition to L3/L4/L7 entries in the NetworkPolicy. This required removal of some sidecar-specific code from cilium-envoy that was never exercised earlier due to the "mass wildcarding" model.
policy/selectorcache.go required an interesting fix relating to use of interfaces as map keys (like in L4Filter.L7RulesPerSelector :-)

Fixes: #9996

This change is

test-me-please

Coverage decreased (-0.1%) to 44.574% when pulling 0d58d44d5603e4eadfc0ea121d6b05ba5475ea9c on pr/jrajahalme/tls-policy-merge-fix into 20c39223f6a070a3f428adbde81646545e040e6a on master.

test-me-please

test-me-please

test-me-please

test-me-please

@jrajahalme  some jenkins happened and the GKE tests triggered for this PR. You should ignore them (as they will fail). Sorry!

@raybejjani @joestringer Sorry for the rebase if you happened to be in a middle of a review. However, the unit test changes should be less confusing now, as I reverted the changes I had made to the test input. Also added the fix @raybejjani sent me offline.

test-me-please

@raybejjani Yes, the intent was to add the wildcard rule to an L3/L4 rule when merging with an L7 rule. Functionally, master should behave the same, but I'm not 100% sure it does (if not, then this would also be a bug fix). For the example you gave, are you saying that master redirects port 53 to the dns proxy, which then only allows requests for google.com? If so, I'd say master is behaving badly.

test-me-please

test-me-please

@jrajahalme Changes (still) look good to me.

For the example you gave, are you saying that master redirects port 53 to the dns proxy, which then only allows requests for google.com? If so, I'd say master is behaving badly.

Yup! master is behaving badly. For that example, talking to kube-dns only allows google.com lookups despite the implicit wildcard. Talking to <IP_ADDRESS> only allows cloudhmar.com (which is correct). So, +1 bugfix!

test-me-please

test-me-please

@joestringer Added a note to the description about the bpf changes added in a new commit.

test-me-please

Changed bpf datapath policy lookup order from:
L3/L4 -> L3/* -> */L4 -> /
to:
L3/L4 -> /L4 -> L3/ -> /
This helps redirecting to the proxies in visibility cases without playing with L3-only map entries.
Additionally, generation of L3/L4 keys is suppressed if L4-only key already does what L3/L4 would need to be doing (considering also that L3/L4 would need to redirect if */L4 redirects).

Changed bpf datapath policy lookup order from:
L3/L4 -> L3/* -> */L4 -> /
to:
L3/L4 -> /L4 -> L3/ -> /
This helps redirecting to the proxies in visibility cases without playing with L3-only map entries.
Additionally, generation of L3/L4 keys is suppressed if L4-only key already does what L3/L4 would need to be doing (considering also that L3/L4 would need to redirect if */L4 redirects).

test-me-please

Another VM provisioning fail due to timeout.

Have to rebase again for bpf bindata conflict.

Adding a commit that bumps Jenkins timeouts.

test-me-please

No change, but had to rebase due to daemon/bpf.sha (aka bindata).

test-me-please

Great work in preparing this in time for the release @jrajahalme


Latest version 1.5.4 breaks Rails 4.1 compatibility

See<PHONE_NUMBER>d66bfad9cef8e25e0f6aa4d49acdb3
In Rails 3.0 -> 4.1 there is no way to call model_name on an ActiveRecord instance. This is only possible in Rails 4.2
The solution is to add ".class" before ".model_name" this should work in all cases since from Rails 4.2 the call to ".model_name" is delegated to the instance class.
https://github.com/rails/rails/blob/4-2-stable/activemodel/lib/active_model/naming.rb#L220

Can you try if the solutions you proposed works? I don't use it anymore, so I would have to setup new app with this gem which could have take some time..

Yes it work. Both in Rails 4.1 and in Rails 4.2

Fixed by @laserlemon in #58


Bug: The generated Xcode project does not include the source files from cmake

Description
I want to compile a cmake project using Bazel and manage its source code dependencies. However, I've noticed that while the generated project runs correctly, it does not include the source files contained in cmake, preventing me from setting breakpoints.
Reproduction steps
The file directory is as follows:

The BUILD file under 'vendor' contains the following code,

The BUILD file in the outer layer contains the following

The generated Xcode project, as  following, can run normally. However, the project does not display the files 'hello.c' and 'hello.h'. This prevents setting breakpoints.

Expected behavior
The generated project includes the relevant source code from CMake, that is, it contains the files 'hello.c' and 'hello.h’
rules_xcodeproj version
f5c1f4bea9f00732ef9d54d333d9819d574de7020dbd9d081074232b93c10b2c
Xcode version
Version 15.0 (15A240d)
Bazel version
bazel 6.4.0-homebrew
rules_apple version
No response
rules_swift version
No response
Additional information
No response

Can you attach a self-contained repro that we can debug?

https://github.com/yyl1989726/bazel_cmake_xcodeproj_demo/tree/main

I can't generate the project, I get this error:
Download from https://pkgconfig.freedesktop.org/releases/pkg-config-0.29.2.tar.gz failed: class java.net.ConnectException Connection refused

I assume it's my network for some reason. I'll try again later.

@brentleyjones freedesktop.org has been down for the best part of the day. It's not you.

You can use temporarily:
rules_foreign_cc_dependencies(register_built_pkgconfig_toolchain = False)

#2847 fixes this:


IE 11 issue - still get "Access Denied" in getOwnPropertyNames

I'm submitting a bug report

Library Version:
<EMAIL_ADDRESS>

Browser:
IE 11 - 11.672.10586.0

Language:
TypeScript 2.1

Current behavior:
After adding Power Bi which creates an iframe underneath, I can still see following errors in console multiple times:
SCRIPT5: Access is denied.
aurelia-polyfills.js (131,7)

This is simple repro project using power bi client library. First install dependencies npm i and then run app i.e. gulp watch. PowerBi token can expire, so please obtain new one -> more info in src/powerbi.ts file.
Polyfills-Repro.zip

@jdanyow Any chance you can look into this?

https://github.com/zloirock/core-js/issues/76

@EisenbergEffect do you think we should update our polyfills to fix this issue?
https://github.com/zloirock/core-js/issues/76
https://github.com/paulmillr/es6-shim/commit/cee098d1cb451540e1e8f5341180964bbb66c66d

Seems like it. Any idea if it's a small fix?

+1
Same as @mikeesouth noted on #22, we're not seeing this in current releases of Chrome or Firefox. Only on IE 11 (we're using 11.0.9600.18617) 100% of the time as well.
Any updates on this?

I just noticed @doubleaa93 made the PR, I will skip my PR. Sorry for the delay.

Thanks a lot @doubleaa93! Any chance to get this PR merged soon?

We'll get it out this week :)

@EisenbergEffect Thans a lot!

Merged fix. Releasing in a few minutes.


Compiled m5o should be generated in .meltano folder

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/301
Originally created by @mbergeron on 2019-01-18 14:25:36

We currently generate the compiled version alongside the definitions, which to me pollutes the directory.
Also, we already have an ephemeral storage in .meltano and everything that is created/managed by Meltano should go in there.
This would prevent mistakes like committing your database config or a compiled model upstream.
I propose .meltano/collections/carbon.collection.m5oc and meltano/index.m5oc
In MR for !400 so will be done when that MR is finished.
/cc @jschatz1

View 6 previous comments from the original issue on GitLab


Gardening

This does some cleanup:

Fix Swift 3.1 deprecations in tests
Remove usage of fatalError by assigning last in the same if let where first is also assigned.

It also adds some more convenience:

Allow passing an Evaluator to the convenience function for evaluating a String
Add convenience function on Expression to rewrite the given expression (incl. tests).

These changes look great! :)


added JS Maze Game

Added Maze Game made in JS using Canvas API

Thanks for contributing @GujGeek ✨


Duplicate "bit-txt-disabled-fluent" CSS class insertion in BitTextFiled component

this issue was fixed in pull request #691


[Question] How does speedy mode actually work?

I am extremely curious how Glamor's speedy mode actually work, I hope this wasn't asked before, I tried looking for it to no avail here or on Google.
<style type="text/css" data-glamor=""></style>

This harmless looking style tag actually holds all the styles inside of it, somehow... magically? How? What technique is being used here? Nothing on Mozilla's documentation of Style tag says anything about this as well

Great question, I've been meaning to write this up for the longest time. Tldr- it uses this api https://developer.mozilla.org/en-US/docs/Web/API/CSSStyleSheet/insertRule which bypasses the DOM and injects rules straight into the cssom. You can see how we use this in this file https://github.com/threepointone/glamor/blob/master/src/sheet.js . There are tradeoffs around it, which is why it's enabled only in production. I'll drop a line here when I finally do publish the doc, but I hope this clears things up.

Closing this issue, but feel free to carry on the conversation if you need more info

Thank you! That's an extremely interesting API that I have never seen before, it's amazing how it's also nothing new, in fact exists in IE9, I believe your doc will explain the tradeoffs which will probably be partially why it's not used more often
Can't wait to read your doc once you have time to finish it!


Add v1.22.3 and v1.23.1 release of grpc-go to interop matrix.

v1.23.0 seems to have missed out since the
PR to add that had a merge
conflict and was never merged.

@karthikravis

Known failures:
https://github.com/grpc/grpc/issues/20095


Add remote-control-with-oculusvr for Clover

Is this a CopterHack article? What is the team?

Да, статья для CopterHack, команда - ProCleVeR18.03.2021, 20:34, "Oleg Kalachev" @.***>:
Is this a CopterHack article? What is the team?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

What is the team name? And, please, give some contact (e-mail, Telegram, ...) you want to put into the article.

Please, give some contact (e-mail, Telegram, ...) you want to put into the arti

I don't need to close the PR to change something, you just need to push new changes to your branch.

Please, give some contact (e-mail, Telegram, ...) you want to put into the article.

<EMAIL_ADDRESS>

I pushed the latest article changes to my fork according to recommendations

I don't need to close the PR in order change something, you just need to push new changes to your branch.

I pushed the latest article changes to my fork according to recommendations


Replace non-alphanumeric characters with dash in id attributes.

Although it is allowed to use just about any character for id attributes there are some that will create problems when using them from css or javascript/jquery. For shins it can be seen by adding f.ex. a "." to one of the ids in source/index.html.md. This PR cleans up the id attributes and replaces all non-alpanumeric character with a dash.
See discussion here: https://stackoverflow.com/a/79022

Many thanks!


python3Packages.awslambdaric: fix build following simplejson upgrade

Motivation for this change
awslambdaric fails to build following the upgrade to simplejson 3.17.5 in nixpkgs. See https://github.com/aws/aws-lambda-python-runtime-interface-client/pull/58.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

2 packages built:

python38Packages.awslambdaric
python39Packages.awslambdaric

Result of nixpkgs-review pr 139694 run on x86_64-darwin 1


Support for nodenv installed via Homebrew

Description of changes
This updates the react-native-xcode.sh build script to check for versions of nodenv installed by Homebrew. These were added to React native by https://github.com/facebook/react-native/pull/19509, this PR simply applies those same changes to react-native-schemes-manager's version of the script.

I assume this has now been merged in as part of the v60 work in #74, so I'll close this one. If I'm wrong please let me know.


Improve scalability of ProtocolAdapterPollingServiceImpl

Previously, every job run attempted to grab the locks of
executingJobs and semaphore multiple times, concurrently
to other jobs and the watchdog.
In scenarios of high contention due to many connections
and/or a high polling rate, this could lead to high lock
contention and subsequent, costly context switches.
Therefore, this commit removes replaces said locks with:

A per-job AtomicBoolean to mark it as (not) running.
This removes the need to check the previous, synchronized
executingJobs, completely removing multiple lock attempts.
An AtomicInteger counter of jobs currently running.
Any job which is the "first" running one will synchronize
on it to notify the potentially waiting watchdog.
This significantly reduces the number of job threads which
might attempt to do this concurrently.

Additionally, replace calls to System.currentTimeMillis with .nanoTime because the former

is not guaranteed to be strictly monotonically increasing, and
tends to have a significantly higher overhead

@cla-bot check


switch to tests to wast

What kind of change does this PR introduce?
The issue is that currently we test against opaque wasm binary and doesn't help when debugging.
I only converted two tests for the demo. I'll continue if you agree.

Did you add tests for your changes?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

btw I have the wast-loader package now. I'm waiting for your review @sokra to continue.

I kept the LEB128 padded one to ensure we are parsing them, everything else has been changed to wast.

As a side note, wabt's WASM to WAT adds a bit of latency, the test is probably failing because of that. Should we increase the timeout?

Thanks


Search - Tax field for the expense does not auto update after changing distance rate

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v9.0.25-2
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:
Precondition:

Track tax is enabled
Workspace has at least two distance rates that have tax rate and tax reclaimable on.

Submit a distance expense, with a distance rate that has tax rate and tax reclaimable on.
Go to Search.
Click on the submitted expense in Step 3.
Click Rate.
Select a different distance rate that has tax rate and tax reclaimable on.
Close the RHP.

Expected Result:
The Tax field for the expense will update.
Actual Result:
The Tax field for the expense does not update, unless user switches to another tab and back to Expenses tab.
Workaround:
Unknown
Platforms:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/3ff338c0-f658-481d-a751-2247ae3f9451

View all open jobs on GitHub

We think that this bug might be related to #wave-control

@strepanier03  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

This is a BE issue as we don't support optimistic data for Search.

Hmmm, I'm not able to reproduce this as described. During my testing the tax field was updating after making a change and closing the RHP, I didn't need to toggle to another tab to get it to update.
I'm also receiving some inconsistent behavior as sometimes I'm unable to change the tax rate on the expense. I'm going to test this some more.

Okay, got past the inconsistent behavior I was running into and was able to reproduce this successfully.

No update yet. Tied to a project and labeled.

Help wanted still. Gonna set to weekly until this is picked up.

Issue not reproducible during KI retests. (First week)

Thank you @mvtglobally - If it's not reproducible next week I'll retest as well.

Waiting on testing, but I'll test and close if still unrepro.

Issue not reproducible during KI retests. (Second week)

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989


Adds craftable ducky slippers

About the PR

Allows you to craft ducky slippers out of two rubber duckies.
Why / Balance

Quack
Technical details

All yml requirements to add a construction graph, tags for it, and the end result.


Build CI CD for gpu.

Currently, we only test cpu version for every commit. We may need to add for gpu version (maybe running test on local machine.)

There is a way to do GPU testing for CI but I don't think we have bandwidth to do that

We are bringing in some help.

Hi, I would like to contribute this part.
The related PR will use nvidia/cuda docker image.
What's the CUDA version we intent to use in CI?

I think we are using ubuntu 20 or 22, right?

22 would be nice. Also some DevOps help on setting up GitHub CI actions of
that would be great.
On Mon, Dec 16, 2024, 08:44 Alex Chiang @.***> wrote:

I think we are using ubuntu 20 or 22, right?
—
Reply to this email directly, view it on GitHub
https://github.com/Cytnx-dev/Cytnx/issues/538#issuecomment-2545669352,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFCX3SNFHNE73EBYCEKWJW32F3KKTAVCNFSM6AAAAABTTIAKWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBVGY3DSMZVGI
.
You are receiving this because you commented.Message ID:
@.***>

@kaihsin
I try to build and test in the nvidia container (nvidia/cuda:11.8.0-devel-ubuntu22.04).
 It's a expected?
Can the tests pass with only USE_CUDA enabled?
95% tests passed, 43 tests failed out of 891

Total Test time (real) = 413.69 sec

The following tests FAILED:
        640 - NetworkTest.gpu_Network_dense_no_order (Failed)
        641 - NetworkTest.gpu_Network_dense_find_optimal (Failed)
        642 - NetworkTest.gpu_Network_dense_order_line (Failed)
        643 - NetworkTest.gpu_Network_dense_specified_order (Failed)
        644 - NetworkTest.gpu_Network_dense_reuse (Failed)
        646 - NconTest.gpu_ncon_default_order (Failed)
        647 - NconTest.gpu_ncon_specified_order (Failed)
        648 - NconTest.gpu_ncon_optimal_order (Failed)
        649 - ContractTest.gpu_Contract_denseUt_optimal_order (Failed)
        650 - ContractTest.gpu_Contract_denseUt_default_order (Failed)
        651 - ContractTest.gpu_Contract_denseUt_specified_order (Failed)
        652 - ContractTest.gpu_Contract_denseUt_optimal_specified_order (Failed)
        653 - ContractTest.gpu_Contracts_denseUt_optimal_order (Failed)
        654 - ContractTest.gpu_Contracts_denseUt_default_order (Failed)
        655 - ContractTest.gpu_Contracts_denseUt_specified_order (Failed)
        656 - ContractTest.gpu_Contracts_denseUt_optimal_specified_order (Failed)
        657 - BlockUniTensorTest.gpu_Trace (Failed)
        706 - BlockUniTensorTest.gpu_group_basis (SEGFAULT)
        710 - DenseUniTensorTest.gpu_Trace (Failed)
        775 - Directsum.gpu_one_elem_tens (SEGFAULT)
        779 - Directsum.gpu_shared_axis_contains_all_tens_one_elem (SEGFAULT)
        789 - ExpM.gpu_ExpM_test (Failed)
        791 - Lanczos_Gnd.gpu_Bk_Lanczos_Gnd_test (Failed)
        792 - Arnoldi.gpu_which_LM_test (Failed)
        793 - Arnoldi.gpu_which_LR_test (Failed)
        794 - Arnoldi.gpu_which_LI_test (Failed)
        795 - Arnoldi.gpu_which_SM_test (Failed)
        796 - Arnoldi.gpu_which_SR_test (Failed)
        797 - Arnoldi.gpu_which_SI_test (Failed)
        798 - Arnoldi.gpu_mat_type_real_test (Failed)
        799 - Arnoldi.gpu_k1_test (Failed)
        800 - Arnoldi.gpu_k_max (Failed)
        801 - Arnoldi.gpu_smallest_dim (Failed)
        807 - Svd.gpu_dense_one_elem (Failed)
        808 - Svd.gpu_dense_nondiag_test (Failed)
        813 - Svd.gpu_U1_zeros_test (Failed)
        820 - Gesvd.gpu_dense_one_elem (Failed)
        821 - Gesvd.gpu_dense_nondiag_test (Failed)
        835 - linalg_Test.gpu_BkUt_Svd_truncate3 (Failed)
        836 - linalg_Test.gpu_BkUt_Qr1 (Failed)
        838 - linalg_Test.gpu_BkUt_expM (Failed)
        839 - linalg_Test.gpu_DenseUt_Gesvd_truncate (Failed)
        840 - linalg_Test.gpu_DenseUt_Svd_truncate (Failed)

If you built on the master branch, it's expected. If you build on the dev-master branch there are fewer falling tests but still a few.

I got it. I think we should list all the failed tests and plan to fix them in the future. The list will be included in the PR.
Does that make sense?

Which branch should I submit my pr to? master or dev-master?
BTW, I cannot build dev-master successfully. Is It expected?
We can discuss this issues on another thread.

I think dev-master is fine. Could you try to use cuda:12.2 to build?

These tests are expected to fail on the develop branch.
linalg_Test.gpu_BkUt_Svd_truncate3
linalg_Test.gpu_BkUt_expM
Svd.gpu_U1_zeros_test
Lanczos_Gnd.gpu_Bk_Lanczos_Gnd_test

I can't copy the whole environment. However, you may try these changes to suppress the segmentation fault error.
To build in the debug mode, the compiler flag -D USE_DEBUG=ON should be set even if CMAKE_BUILD_TYPE is set to Debug. The env value ASAN_OPTIONS="protect_shadow_gap=0:replace_intrin=0:detect_leaks=0" should be set while running tests. Refer to:
https://github.com/google/sanitizers/issues/629#issuecomment-161755902
https://stackoverflow.com/a/68027496

I still encountered some errors:
The following tests FAILED:
        174 - SearchTreeTest.BasicSearchOrder2 (Failed)
        972 - Directsum.gpu_one_elem_tens (Failed)
        976 - Directsum.gpu_shared_axis_contains_all_tens_one_elem (Failed)
        1100 - BlockUniTensorTest.gpu_group_basis (Failed)

I will try to fix them later.
My commit:
https://github.com/jysh1214/Cytnx/commit/58d1473060c8587d6866f0cfca755d35faf029a2

I still encountered some errors:
The following tests FAILED:
        174 - SearchTreeTest.BasicSearchOrder2 (Failed)
        972 - Directsum.gpu_one_elem_tens (Failed)
        976 - Directsum.gpu_shared_axis_contains_all_tens_one_elem (Failed)
        1100 - BlockUniTensorTest.gpu_group_basis (Failed)

I will try to fix them later.
My commit: jysh1214@58d1473

Could you provide the log file in build/Testing/Temporary/LastTest.log when you run these Failed test?

Could you provide the log file in build/Testing/Temporary/LastTest.log when you run these Failed test?

Sure. Please chech this:
https://drive.google.com/drive/folders/1FenrFwgLBsqv25icR_U7alEkVcpRe3Mt


Allow running up with no input

I like to run up to just run grep searches interactively (using ripgrep on the current directory).

I saw this sentiment expressed also in #33; can you please help me understand if there are reasons why e.g. something like echo | up is not working for you? What holds me back on this feature is basically that I'm having concerns about discoverability of the app's core feature being impacted...

@akavel Because up passes the dummy input to the command, and a lot of commands (including grep) will change their behavior if stdin is present. I don't think discoverability will be affected; If anything, the current marketing seems confusing to me. up is essentially a new mode of using a REPL. I think the best summary of what up is, is up makes your commands sticky in any REPL. Anyhow, adding an option for running with no input, if not advertised upfront, definitely won't change people's first impression of the tool.

Would this not be the exact usecase for FZF?


Support for sqlite3_create_function

Would it be possible to support custom functions in sqlite on iOS and Android. It would be desirable to be able to define custom functions and have them implemented by javascript functions.
This is definitely a wishlist item, I'm just curious if anyone would benefit from this (and even if it's technically feasible - I'm not familiar with the limitations of the sqlite implementations on mobile platforms).

http://www.sqlite.org/c3ref/create_function.html
Android helps out a little here -  https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/database/sqlite/SQLiteCustomFunction.java#37

This is possible to do by creating a custom native wrapper (like what Android did) in ObjC; however this is not a feature I will be adding myself as I honestly have no use for it, and this would require a bit of work.  ;-)
I am willing to accept any pull requests; or you can hire me (or someone else) to add this feature.


Setup new integration-HomeKit Accessory fails

The problem

Environment

Home Assistant release with the issue: 0.106.0
Last working Home Assistant release (if known):  not known
Operating environment (Hass.io/Docker/Windows/etc.):
Integration causing this issue: Adding HomeKit accessory
Link to integration documentation on our website:  https://www.home-assistant.io/integrations/homekit_controller/

Problem-relevant configuration.yaml

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
zeroconf:

# Need this even though I have default_config:
frontend:
  themes: !include_dir_merge_named themes

# Add customization information:
homeassistant:
  customize: !include customize.yaml

# Needed to assess health of system
system_health:

# Config for mobile phone app
mobile_app:
cloud:
ios:
stream:

# Required for some configurations
#homeassistant:
#    customize: !include customize.yaml

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Text to speech
tts:
  - platform: google_translate

# Control and limit size of database
recorder:
  purge_keep_days: 5
  exclude:
    domains:
      - camera
      - fan
      - light
      - media_player
      - sun
      - weather
      - device_tracker
      - switch
      - cover
      - zone
    entities:
     - sensor.last_boot
     - sensor.date

# Lutron Caseta Control
lutron_caseta:
  host: <IP_ADDRESS>
  keyfile: /ssl/lutron/caseta.key
  certfile: /ssl/lutron/caseta.crt
  ca_certs: /ssl/lutron/caseta-bridge.crt

# Chamberlain Garage Doors
cover:
  - platform: myq
    username: !secret who
    password: !secret id

# Local IP sensor
local_ip:

# HACs add-on to identify potential problems on upgrades
breaking_changes:

# WeMo devices with automatic discovery
wemo:
  discovery: true
  static:
    - <IP_ADDRESS>
    - <IP_ADDRESS>
    - <IP_ADDRESS>
    - <IP_ADDRESS>
    - <IP_ADDRESS>
    - <IP_ADDRESS>
    - <IP_ADDRESS>
    - <IP_ADDRESS>

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
garbage_collection: !include trash.yaml
sensor: !include sensor.yaml
camera: !include video.yaml
weather: !include weather.yaml
homekit: !include homekit.yaml

Traceback/Error logs

Wed Feb 26 2020 10:59:09 GMT-0700 (Mountain Standard Time)
Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start
    resp = await task
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/real_ip.py", line 39, in real_ip_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 72, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 135, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 123, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 130, in post
    return await super().post(request)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 50, in wrapper
    result = await method(view, request, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 62, in post
    handler, context={"source": config_entries.SOURCE_USER}
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 109, in async_init
    result = await self._async_handle_step(flow, flow.init_step, data)
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 172, in _async_handle_step
    result: Dict = await getattr(flow, method)(user_input)
  File "/usr/src/homeassistant/homeassistant/components/homekit_controller/config_flow.py", line 107, in async_step_user
    all_hosts = await self.hass.async_add_executor_job(self.controller.discover, 5)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/homekit/controller/controller.py", line 90, in discover
    return discover_homekit_devices(max_seconds)
  File "/usr/local/lib/python3.7/site-packages/homekit/zeroconf_impl/__init__.py", line 102, in discover_homekit_devices
    info.properties
  File "/usr/local/lib/python3.7/site-packages/homekit/zeroconf_impl/__init__.py", line 180, in parse_discovery_properties
    d['category'] = Categories[int(category)]
  File "/usr/local/lib/python3.7/site-packages/homekit/model/categories.py", line 94, in __getitem__
    raise KeyError('Item {item} not found'.format(item=item))
KeyError: 'Item 33 not found'
Connection lost. Reconnecting…

Additional information
This worked on my Raspberry Pi 3B+ 105.5

Cheers @JamesDenby.
For context, https://community.home-assistant.io/t/homekit-accessory-integration-fails/174636/2.
As i said on the forums, the underlying library has never supported category 33 so this is not a regression in the traditional sense.
But given you said this worked before there are 2 main scenarios I see:

You previously paired your device from the "Discoveries" list. This ignores the category and so worked. This time you did a manual add. This uses the discovery from the upstream library. This is more thorough and strict and didn't recognise category 33.

You bought some new equipment (or upgraded some firmware on existing equipment). You know have a HomeKit device that you didn't last time you paired. This new accessory is category 33 and is breaking home-assistant from discovery any HomeKit device.

Interestingly you use eero networking gear, and eero is one of the few providers that do (or plan to) support HomeKit routers. Looking at the JS HomeKit library, category 33 is a HomeKit router. This is a feature that lets HomeKit push firewall rules into your networking gear, and was only released very very recently - see here.
For now i would edit line 180 of /usr/local/lib/python3.7/site-packages/homekit/zeroconf_impl/__init__.py and change:
    d['category'] = Categories[int(category)]

to just
    d['category'] = "unknown"

Home Assistant doesn't use this field so its a safe change and should allow discovery to complete.
We are migrating to a different homekit library, so in parallel to this I will make sure it knows about routers but also make sure it doesn't fail the entire discovery process if its an unknown category.

Jc2k,
Thank you for the rapid response. Outstanding!
But, I cannot seem to get to the file to edit it. I tried through Terminal and get a bash error when I try to go past /usr/local/lib/
Any chance you could guide me to that file so that I may change it?

I'll try but theres a limit to how much i can intuit about other peoples environments 😺
The traceback you posted shows that the package is under /usr/local/lib/python3.7/site-packages/ so the fact that you can't get to it really indicates to me:

it's a permissions thing
it's a container or vm thing

Really need to know what OS you are using, what commands you are typing and what errors you are seeing.
In your original post you mentioned Home Assistant Core. But you don't say whether its Home Assistant OS, Raspbian or something else. But looking at the fact that your home assistant code seems to be in /usr/src/homeassistant i'm going to go out on a limb and say you are using Docker and the official container and given its a Pi - potentially via Home Assistant OS?
I have never used Home Assistant OS myself so don't know if these are valid instructions but i use the official Docker container on Ubuntu and can do:
docker ps
To see a list of containers running. I find the id for the home assistant container and then do
docker exec -it abcdef123 /bin/sh
And i've now got a shell inside the container. At that point the commands you were using before might now work.

I'll try but theres a limit to how much i can intuit about other peoples environments 😺
The traceback you posted shows that the package is under /usr/local/lib/python3.7/site-packages/ so the fact that you can't get to it really indicates to me:

it's a permissions thing
it's a container or vm thing

Really need to know what OS you are using, what commands you are typing and what errors you are seeing.
In your original post you mentioned Home Assistant Core. But you don't say whether its Home Assistant OS, Raspbian or something else. But looking at the fact that your home assistant code seems to be in /usr/src/homeassistant i'm going to go out on a limb and say you are using Docker and the official container and given its a Pi - potentially via Home Assistant OS?
I have never used Home Assistant OS myself so don't know if these are valid instructions but i use the official Docker container on Ubuntu and can do:
docker ps
To see a list of containers running. I find the id for the home assistant container and then do
docker exec -it abcdef123 /bin/sh
And i've now got a shell inside the container. At that point the commands you were using before might now work.

Thank you. I am using Home Assistant OS on a Pi (I believe it is docker). The problem is since it is Home Assistant OS I do not have permission to change the file. Even though I have "root" access through terminal, the OS does not allow any modifications outside of the config directory.
I guess I am stuck until the newer version is finished.

That's weird - i'm sure i've helped people with HA OS before. Are you definitely root inside the container and not just outside it? I.e. what is the output of id inside the container? If you aren't root inside the container you can do something like:
docker exec -u root -it 38aeedf833d5 sh

Yeah, I think I am not really root, and the Home Assistant OS doesn't allow anyone but the chosen developers access.  At that prompt, type login. Then you should have a real shell and docker ps should work.

It works! ... except it won't take 'root' as the login

Not really sure what isn't taking root as the login - do you mean the docker exec? If so try it without, what happens.

Actually, it is root not being taken when I enter Login.

Our command line:
$ ha help

~ $ login
core-ssh login: root
Login incorrect
core-ssh login:

Hi @JamesDenby - sorry for the delay in getting back to you. I'm at a loss on how to help with SSH in your environment, but this should be fixed in 0.107.0 when its released (the first beta was just tagged so hopefully not far away). I'm going to close this now, but please do open another issue or ping me if it doesn't resolve it for you.

Thank you for letting me know. I am looking forward to 0.107.0. I will certainly let you know if I still have a problem once that is released

Actually, it is root not being taken when I enter Login.

Our command line:
$ ha help

~ $ login
core-ssh login: root
Login incorrect
core-ssh login:

Did you find a solution to this?
I could become root with "login", but now I get "Login incorrect" as well.

Hi! This is a closed ticket for a homekit_controller bug that was fixed 8 months ago, and your issue seems seperate to the homekit_controller bug that the issue is for. The community advice is not to comment on closed tickets, especially if its not to say something about the original problem. I don't use HA OS so have no idea how to help you. For something like this you are better asking on Discord or the forums. Thanks.


POL-435 Lambda Functions with High Error Rate

Description
[Describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves]
Contribution Check List

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ ] New functionality has been documented in CHANGELOG.MD

Danger has errored
[!] Invalid Dangerfile file: no implicit conversion of nil into String. Updating the Danger gem might fix the issue. Your Danger version: 8.0.5, latest Danger version: 8.2.3
 #  from Dangerfile:99
 #  -------------------------------------------
 #  has_app_changes.each do |file|
 >    pp.parse(file)
 #    category = pp.parsed_category
 #  -------------------------------------------

  Generated by :no_entry_sign: Danger


Legacy Salesforce API Use with User Provisioning

The Summer '22 Release for Salesforce is approaching, but the legacy Salesforce Platform API version still hasn't been updated for user provisioning. When is this going to be addressed?

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

ID: 624be0a5-9ab6-ec59-e7a2-74585cb0571e
Version Independent ID: a00a09c8-f0c5-2bfe-75aa-6183346af405
Content: Tutorial: Configure Salesforce for automatic user provisioning with Azure Active Directory - Microsoft Entra
Content Source: articles/active-directory/saas-apps/salesforce-provisioning-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@DevinLown-Tanger
Thanks for your feedback! We will investigate and update as appropriate.

@DevinLown-Tanger
Thank you for your time and patience!
Unfortunately, we don't provide product release updates through our GitHub channels. For this, I'd recommend referring to our Azure Updates or Microsoft 365 Roadmap pages for this info.


Look at type libraries for truffle

https://medium.com/ethereum-ts/typesafe-truffle-with-typescript-and-typechain-1773e5b733b4

Migrated to trello


improve syntax error

@yamatoya : Thanks for your contribution to the Azure documentation! The author, @bonova, has been notified to review your proposed change.

@yamatoya thanks - already fixed
#please-close


[FEATURE] Store Bookmarks and notes to supabase

⭐ Suggestion
We'll need to store user specific data to supabase
this would include

Bookmarks
Notes
user Preferences

💻 Use Cases
No response
❌ Related Problems
No response

I am ready to contribute

@akshitarora921, hello, sir, I created 2 issues, #423 and #422, on the Bhagavad Gita page. please have a look, my setup is ready to contribute


release/version info is missing

I'm looking at what you recommend to use in web app, linked in your read me:
https://raw.githubusercontent.com/aws/aws-amplify/master/packages/amazon-cognito-identity-js/dist/amazon-cognito-identity.min.js
There is no version of release info in the file or url or on the git hub repo!
That is a bug.
For example this CDN offers version 2.0.1:
<EMAIL_ADDRESS>But ... is 2.0.1 the latest? I'd like a bit of confidence on what I would be using. What is your release/tag process for us the users of your libs?

Hi @uptimestar, on every release we update github releases: https://github.com/aws/aws-amplify/releases
currently amazon-cognito-identity-js is on version 2.0.2

So I have to look at your notes to know there was a release. But the regular way of looking at a file or the location of file or name of the file, one can't tell.

@uptimestar github doesn't currently have support for creating releases with a mono repo. We tend to just follow the same way most do it for example react. I imagine better support for package releases should be coming soon given the popularity of the mono repos. Until then please let us know what might help that we could do differently with the releases / changelog.

In the mean time, for the users, can you just put inside the .js file name the release version # like is common. You have license, etc. in there.


linking the library ?

Hi, will the library need to be linked somehow? doesn't say anything in the readme ?
Thanks.

oh it dose it automatically, nice. Closed.


Sync develop & master

Automerge master in develop

CDS Report auto-merge#62.0 ✘

Stage 1

automerge ✘

Automerge master in develop has failed due to an error from our CI/CD system. I close this pull request and fix conflict manually.
Thanks!


subscribing to models requires update operation

Describe the bug
Our model contains Projects, that unauthenticated users of a mobile app should be able to read, and also to subscribe to updates to these objects. Hence our graphql schema contains:
type Project
  @model(subscriptions: { level: public })
  @auth(
    rules: [
      {
        allow: private
        provider: userPools
        operations: [read, create, update, delete]
      }
      { allow: public, provider: iam, operations: [read] }
    ]
  ) {

But when the client tries to subscribe to updates (verifiable also in the AppSync console), an error for unauthorised access is thrown, despite only read access is required, and also subscriptions for the model is set to public. There should be a way for unauthenticated clients to subscribe to public models.
  "errors": [
    {
      "path": [
        "onUpdateProject"
      ],
      "data": null,
      "errorType": "Unauthorized",
      "errorInfo": null,
      "locations": [
        {
          "line": 2,
          "column": 3,
          "sourceName": null
        }
      ],
      "message": "Not Authorized to access onUpdateProject on type Subscription"
    }

The only way to have the proper resource statements generated in the cloudformation scripts for the unauthRole is to include update in the list of operations.
Amplify CLI Version
3.15.0
To Reproduce
see above
Expected behavior
if read access is allowed for public, it should be possible to subscribe to updates

What is the default Authorization mode for your API? Could you try subscribing to API using the default authorization mode and see if the subscription succeeds

This the backend-config.json
	"api": {
		"fooBarApi": {
			"service": "AppSync",
			"providerPlugin": "awscloudformation",
			"output": {
				"authConfig": {
					"additionalAuthenticationProviders": [
						{
							"authenticationType": "AWS_IAM"
						}
					],
					"defaultAuthentication": {
						"authenticationType": "AMAZON_COGNITO_USER_POOLS",
						"userPoolConfig": {
							"userPoolId": "authidowebec08169c"
						}
					}
				}
			}
		},

AFAIK there's no unauth access with userpools, is there? so I don't know how to subscribe to the api with the default auth mode.

as far as I can tell, the transformer doesn't generate the required resources in the unauth role to grant access to the subscriptions.

When multi auth is enabled, the subscriptions support only the default auth type even if its declared as public. The transformer is not generating the required multi auth directives to support all the auth types enabled in your API. I am marking this as bug.
the workaround for this issue is to extend subscription in your schema and adding the auth directives manually as shown below
type Subscription {
    onCreateProjectPublic: Project
        @aws_subscribe(mutations: ["createProject"])
        @aws_iam
        @aws_cognito_user_pools
    onUpdateProjectPublic: Project
        @aws_subscribe(mutations: ["updateProject"])
        @aws_iam
        @aws_cognito_user_pools
    onDeleteProjectPublic: Project
        @aws_subscribe(mutations: ["deleteProject"])
        @aws_iam
        @aws_cognito_user_pools
}

The workaround suggested by @yuth didn't work for me.
For now, I manually added the permission to the UnauthRole policy
arn:aws:appsync:us-east-1:[...]:apis/[...]/types/Subscription/fields/onUpdateProject
I made this change directly in the IAM console as I couldn't find a way to do it by editing the Amplify files

Hi @AndreasEK
PR: https://github.com/aws-amplify/amplify-cli/pull/4340 address this by adding read on the permissions the GraphQL Transformer will add the necessary permissions to allow the unauthRole to listen to subscriptions.

The workaround suggested by @yuth worked for me but only after I also added the permission to the UnauthRole policy:
arn:aws:appsync:us-east-1:[...]:apis/[...]/types/Subscription/fields/onUpdateProjectPublic
I made this change directly in the IAM console as I couldn't find a way to do it by editing the Amplify files

You can do it in CustomResources.json file:
  ...

  "Resources": {
    "UnauthRolePolicy": {
      "Type": "AWS::IAM::Policy",
      "Properties": {
        "PolicyName": "appsync-unauthrole-policy-custom",
        "Roles": [
          {
            "Ref": "unauthRoleName"
          }
        ],
        "PolicyDocument": {
          "Version": "2012-10-17",
          "Statement": [
            {
              "Effect": "Allow",
              "Action": ["appsync:GraphQL"],
              "Resource": [
                {
                  "Fn::Sub": [
                    "arn:aws:appsync:${AWS::Region}:${AWS::AccountId}:apis/${apiId}/types/${typeName}/fields/${fieldName}",
                    {
                      "apiId": {
                        "Ref": "AppSyncApiId"
                      },
                      "typeName": "Subscription",
                      "fieldName": "onUpdateProjectPublic"
                    }
                  ]
                }
              ]
            }
          ]
        }
      }
    }
  },
  ...

Closing this issue as the PR for this has been merged and and released into version 4.21.1. By adding the read operation this will generate the IAM policies to allow access to subscriptions.

Hi @SwaySway, the fix didn't work for my model (amplify CLI version 4.21.3)
type Project @model(subscriptions: { level: public })
 @auth(
    rules: [
      { allow: public, provider: iam, operations: [read] }
      { allow: owner, operations: [create, read, update ] }
    ]
  ) {

No subscription permissions are added to the IAM policies
I also tested changing the model to this:
type Project @model
 @auth(
    rules: [
      { allow: public, provider: iam, operations: [read] }
      { allow: owner, operations: [create, read, update ] }
    ]
  ) {

The permissions are added, but now only the owner of a project can subscribe to its updates.
Is there something else I should do?
Thank you

@andriworld Were you able to resovle?
I'm facing the same issue on version 4.26.0 This is my model
type Book
  @model
  @auth(
    rules: [
      { allow: groups, groups: ["Admins"] }
      { allow: groups, groupsField: "level1", operations: [update, read] }
      { allow: groups, groupsField: "level2", operations: [read] }
    ]

In this case admins can subscribe. but level1 can't.

I am still seeing this same behavior on version 4.29.2 with this model:
type Account @model
    @auth(rules: [
        {
            allow: owner, ownerField: "id", identityField: "custom:accountNumber",
            operations: [read]
        }
        { allow: groups, groups: ["admin"] }
    ])
    {
        id: ID!
        name: String
        description: String
    }

owner can read, but on trying to subscribe to update, get unauthorized error.
@SwaySway Is this expected behavior after the PR merge or have I hit a new case?
Seems like read permission should allow for subscribing to updates.

I'm on 4.29.4.. And am also seeing the same behaviour. I guess I should create a new Issue though

@SwaySway  I'm on 4.29.5
type Post
  @model(subscriptions: { level: public })
  @aws_iam
  @aws_cognito_user_pools
  @auth(
    rules: [
      { allow: owner, operations: [create, read, update, delete] }
      { allow: public, provider: iam, operations: [read, update] }
      { allow: groups, groups: ["user"], operations: [create, read, update] }
    ]
  )
  @key(name: "byUser", fields: ["userID"]) {
  id: ID!
  title: String!
  userID: ID!
  content: String
  user: User @connection(fields: ["userID"])
  comments: [Comment] @connection(keyName: "byPost", fields: ["id"])
}

Owner can read, but when it is aws_iam, "no current user"

I've been getting flaky experiences with this.  I at one point was only getting my primary and gsi back and now I'm back to getting nulls again but I get an event which I just hacked into refreshing my UI.
I've tried adding the subscription level public, I tried adding the Subscription extension and its all null.

I've been getting flaky experiences with this.  I at one point was only getting my primary and gsi back and now I'm back to getting nulls again but I get an event which I just hacked into refreshing my UI.
I've tried adding the subscription level public, I tried adding the Subscription extension and its all null.

I am also experiencing a similar issue. Subscriptions are not allowing public access. I am getting the following error when trying to load a subscription:
Uncaught (in promise) No current user
Here is my schema. I am using multi-authorization modes i.e., main cognito user pools + secondary iam.
type Note @model (subscriptions: { level: public })
@auth (rules: [
  { allow: owner, operations: [create, read, update, delete] },
  { allow: private, operations: [read] },
  { allow: public, operations: [read], provider: iam }
])
{
  id: ID!
  body: String!
  owner: String
}


OIDC RequireHttpsMetadata

#485
Something like this @PinpointTownes?
@muratg @Eilon @brentschmaltz @tushargupta51 @blowdart
(I'll do Bearer once we agree on the fix).

Hi @Tratcher, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

:shipit: it looks fine.
3 remarks/questions though:

I think it would be appropriate to update the OIDC middleware to throw an exception when a non-HTTPS authority/metadata endpoint is used without RequireHttpsMetadata being set to false directly at the startup time (the document retriever will only throw an exception during the challenge, it's too late IMHO).

Should we automatically set it to false on production/testing environments, similarly to what you've done in Hosting to make the development stage smoother?

Should we generalize this property to related things like the token request or the callback stage to make sure the OIDC middleware doesn't send insecure requests and doesn't listen on non-HTTPS endpoints?

Is this still an option we want to add?

Yes, I'll get back to it this week.

Rebased and updated.
@PinpointTownes I think there's a big difference between requiring metadata retrieval to use https vs requiring your site to run on https. I have almost never needed to get my metadata from an http source, but I always develop my sites using http because https is harder to set up locally.

@PinpointTownes I think there's a big difference between requiring metadata retrieval to use https vs requiring your site to run on https.

Not from a security perspective. @brentschmaltz claimed that this change was to make the OIDC stuff "secure by default". If only the initial stage requires HTTPS, then it's not really "secure by default", as the whole authentication flow (authorization response, token request/response) would need to use HTTPS to avoid disclosing critical data like client credentials or access/identity/refresh tokens.

I have almost never needed to get my metadata from an http source, but I always develop my sites using http because https is harder to set up locally.

I guess that's because you're not using your own authorization/identity server, but I bet that most IdentityServer3/ASOS users will develop their authorization server using HTTP.

Thanks for adding the early check :+1:

:shipit:


making screenshots stopped working on windows

Making a screenshot using a background renderer is not working on windows 10.
vedo version: 2021.0.2
vtk version: 9.0.1
import vedo

c = vedo.Cone()

camera = dict()
camera['pos'] = (10,0,0)
camera['focalPoint'] = (0,0,0)

# display on screen: works
p = vedo.Plotter(bg=(0.5,0.5,0.9))
p.add(c)
p.show(camera=camera)

# render offscreen: actor is not displayed
b = vedo.Plotter(offscreen=True, bg=(0.5,0.5,0.9))
b.add(c)
b.show(camera=camera)

# render and display using PIL image, saving to disk gives same result
npdata = b.screenshot(returnNumpy=True)

from PIL import Image
image = Image.fromarray(npdata)
image.show()

Expecting:

but getting:

With vedo 2020.4.2:

My mistake, solved in 2021.0.3


I want to improve paciFy

Hi,
I have seen in this website navigation bar is overlapping each other and images are not loading. Here's the screenshot of the problem

Hi, @geetanjali2001 this bug has been removed. You can now work on some other issues.


How to get the correct 'transparency' value in the DecodeImage API?

Hello, I need get the correct 'transparency' value when using DecodeImage, correct means the source format does has alpha channel, but now for BMP files I always get PIXEL_FORMAT__BGRA_NONPREMUL even for 24bpp non-alpha files.
My example code can be found here: https://github.com/iyzsong/onscripter-libretro/blob/main/sdl-libretro/SDL_image.cpp
In SelectPixfmt, I use ic.pixcfg.pixel_format().transparency(), which comment as "the image file's natural pixel format", does this pixel_format mean to have the correct transparency value or is there another way to get what I want?
Thanks.

Thanks for the bug report. Let me know if release/c/wuffs-unsupported-snapshot.c doesn't fix it for you.

It works now, thank you!


Incremental skewness and other moments when provided equal values do not yield expected results

Checklist

Please ensure the following tasks are completed before filing a bug report.

[x] Read and understood the Code of Conduct.
[x] Searched for existing issues and pull requests.

Description

Description of the issue.

Encountered a potential bug when using the incremental accumulators for skewness and kurtosis. Notably, when providing all equal values, the accumulators return NaN. However, for uniformly distributed values, the skewness is 0.
Related Issues

Does this issue have any related issues?

No related issues in this repository. However, Pandas seems to have encountered a similar issue: https://github.com/pandas-dev/pandas/issues/18044.
Questions

Any questions for reviewers?

No.
Other

Any other information relevant to this issue? This may include screenshots, references, stack traces, sample output, and/or implementation notes.

No.
Demo

If relevant, provide a link to a live demo.

N/A
Reproduction

What steps are required to reproduce the unexpected output?

In order to reproduce this bug, do the following:
var incrskewness = require( '@stdlib/stats/incr/skewness' );

var acc = incrskewnesss();

for ( var i = 0; i < 100; i++ ) {
    acc( 10.0 );
}
console.log( acc() );
// => NaN

Expected Results

What are the expected results?

The following results are expected:
0

Actual Results

What are the actual results?

The following are the actual results:
NaN

Environments

What environments are affected (e.g., Node v0.4.x, Chrome, IE 11)? If Node.js, include the npm version, operating system, and any other potentially relevant platform information.

All environments are affected.

The fix may be as simple as checking whether M2 is 0.0, before performing division. See here.


Add documentation on using the vscode yaml editor to edit devfiles

/area documentation
Which area this documentation change is related to?
/area api
Issue details
What mistake did you find / what is missing in the documentation?
With https://github.com/devfile/api/issues/456, the user can now use the vscode yaml editor to edit devfile 2.1. We can add a section to describe how to edit devfile yaml files using that editor (including installing the extension and a short video to show it in action).

Background info: https://drive.google.com/file/d/13t5Vy0D8r_1sshK6aWdiSJ01zU_tm2LE/view


[REQUEST] Add more versions of OB2 on docker.hub

Describe the solution you'd like
Could be useful, for people who have issues with new versions, to roll back to the previous version or to another version they would like to install. Right now it's only possible to install the latest version of OB2 via docker.hub

Ok, i changed the build script here https://github.com/openbullet/OpenBullet2/commit/c4648fc862978efe4848eba97ef26f8d0888847
i think/hope starting with 0.1.22 it should also be uploaded with an extra tag which is the version number.


Tidy should ignore

Working with an angular example, tidy is munging my angular in page templates, placing spaces between most things.
<script type="text/ng-template" id="tempTest">
  <input type="date" data-ng-model="TestDate" / >
</script>

becomes
<script type="text/ng-template" id="tempTest">
  < input type = "date"
  data - ng - model = "TestDate" / >
</script>

Same concern here. The beautifier should ignore ng-template script tag content (in the sense that it shouldn't push it through js_beautify, but it should still apply HTML beautification).
The tag_complete local in Parser.get_tag seems to be clean enough after building to simply split and check for 'type' and its value. Then this line
} else if (tag_check === 'script') { //for later script handling

could become something like
} else if (tag_check === 'script' &&
           ignored_script_types.indexOf(tag_attribute_type) === -1) { //for later script handling

where ignored_script_types is an array of strings defined somewhere (maybe even on the options parameter of style_html), and would include at least 'text/ng-template'.
I think that's all that's necessary, but I haven't finished reading the beautification logic. @ggoodman (or another experienced contributor), is this a reasonable approach?

@ggoodman I missed the fact that js-beautify is external to plunker, sorry. The latest js-beautify takes care of this issue:
} else if (tag_check === 'script' &&
    (tag_complete.search('type') === -1 ||
    (tag_complete.search('type') > -1 &&
    tag_complete.search(/\b(text|application)\/(x-)?(javascript|ecmascript|jscript|livescript)/) > -1))) {

Unless there's some reason not to, plunker should probably use the latest version of js-beautify or another stable version with this script-type handling.

Fixed with 9db18e8efb91b17c11da735bfa4be6144feede2f. Thanks for this!


Error While Uploading manifest folder

Sample
msgext-dalle
Author(s)
@lee_ford
What happened?
Error while extracting package: Please ensure there are no folders in your app package and that your app package contains only the manifest.json and the two required icon files at its root level. For an easier experience creating your app package, install Developer Portal from the Teams Store.
manifest.zip
Steps to reproduce

I tried to upload the package in Teams
Face the same error

Expected behavior
the same error

Teams Client

[ ] Teams desktop client
[x] Web browser
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Developer environment
macOS
Browsers

[ ] Internet Explorer
[ ] Microsoft Edge
[X] Google Chrome
[ ] FireFox
[ ] Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Node.js version
v18.17.1
Additional environment details
No response

The uploading of "Manifest.zip" file has been fixed.
the solution is by compressing the file by another compressing mechanism not by mac (online zip or windows)

There are another issue occured. After writing the text-to-image prompt and the image appeared.
I want to press the "send" button to post the image in MS Teams, unfortunatly I got an error message.


Increasing the concurrent test execution count

Current limit of 4 parallel test per invocation is too less for validation tests which have 15min timeout. For example Dataflow validation test has ~16 tests. Each takes 5+ min to execute. With 4 parallel tests, it will take roughly 4 batches of jobs to do the testing taking 4*5+ = 20+ min easily exceeding the 15min timeout.
Please add a meaningful description for your change here

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

R: @pabloem

Hi Ankur. How did you choose 20? I'm checking with Mark on how to deal with this.

@pabloem The only rational behind it is its greater than 16 which is the number of jobs launched in dataflow but other wise its very arbitrary.

I think in this case it makes sense to 1) increase the timeout (15 minutes is still quite low), 2) increase the number of processes by a smaller margin, 3) both.
@jasonkuster what do you suggest?

We don't want to blow through our quota; we have this, Java / Python ValidatesRunner, and Java PostCommit competing for quota in the project. How do you feel about 8? Halves runtime but still keeps quota under control.

Run Python PostCommit


python311Packages.ring-doorbell: 0.7.3 -> 0.7.4

Changelog: https://github.com/tchellomello/python-ring-doorbell/releases/tag/0.7.4
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

5 packages built:

home-assistant-component-tests.ring
python310Packages.ring-doorbell
python310Packages.ring-doorbell.dist
python311Packages.ring-doorbell
python311Packages.ring-doorbell.dist


AWS Discovery

Thanks for open-sourcing shardcake, @ghostdogpr and Devsisters!
I'd like to port a running akka cluster to shardcake, and the largest blocker is the service discovery.
We have an Akka cluster that is running on ECS Fargate instead of Kubernetes so that we're using ECS discovery module provided by Akka Management:
https://doc.akka.io/docs/akka-management/current/discovery/aws.html

This can be done easily by providing an implementation of PodsHealth using ECS API, see https://devsisters.github.io/shardcake/docs/customization.html#health
The Kubernetes one is only a few lines long: https://github.com/devsisters/shardcake/blob/series/2.x/health-k8s/src/main/scala/com/devsisters/shardcake/K8sPodsHealth.scala

Btw if someone implements it, we'll happily accept the contribution!

Conceptual question about this: Are these infra-specific health-checks in any way superior the built-in "ping" health check? That one is also very reliable (right?), works out of the box and does not require to set up access permissions to infra API for your application.

In case of network issue, the ping might fail. However the infra (like Kubernetes) knows if the pod is alive or not because it's in charge of its lifecycle. Basically we rely on the built-in logic of the infrastructure to handle things like cluster split, etc.

Hmm. I guess that can cut both ways. If the ping fails because of network issues, payload messages might fail for the same reason, even though Kubernetes knows that the pod is alive. In that scenario the ping healthcheck is closer to "proof in the pudding". 🤔

We don't want to rebalance as as we're not sure the pod is gone. Otherwise you might end up with the same shard on 2 different pods.

Hello! I'm wondering how to test it during development, considering that localstack's EKS module is available in the Pro version only.

Hello! I'm wondering how to test it during development, considering that localstack's EKS module is available in the Pro version only.

I don't have a great solution for that, we tested the k8s in a real environment...


Feature/email then call

Nice work, this looks great and works well!
On Nov 22, 2017 6:19 PM, "shu.chen"<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/fightforthefuture/battleforthenet/pull/131
Commit Summary

Add petition back to flow, refactor template back out
Readd header
Text updates to headline, button, subheadline
small text change to subheadline
Fix styles of form flow, fix call modal behavior
Fix header sizes
Fix petition form layout
Change default letter text
Change petition id
Track events in ga

File Changes

M dist/bundle.js
https://github.com/fightforthefuture/battleforthenet/pull/131/files#diff-0
(45788)
M dist/index.css
https://github.com/fightforthefuture/battleforthenet/pull/131/files#diff-1
(29)
M scss/index.scss
https://github.com/fightforthefuture/battleforthenet/pull/131/files#diff-2
(21)
M ts/bftn-form-flow.tsx
https://github.com/fightforthefuture/battleforthenet/pull/131/files#diff-3
(20)
D ts/call-action-copy.tsx
https://github.com/fightforthefuture/battleforthenet/pull/131/files#diff-4
(26)
M ts/call-action-form.tsx
https://github.com/fightforthefuture/battleforthenet/pull/131/files#diff-5
(3)
D ts/petition-copy.tsx
https://github.com/fightforthefuture/battleforthenet/pull/131/files#diff-6
(40)
M ts/petition-form.tsx
https://github.com/fightforthefuture/battleforthenet/pull/131/files#diff-7
(71)
M ts/r.tsx
https://github.com/fightforthefuture/battleforthenet/pull/131/files#diff-8
(21)
M ts/templates.tsx
https://github.com/fightforthefuture/battleforthenet/pull/131/files#diff-9
(62)
M ts/utils.tsx
https://github.com/fightforthefuture/battleforthenet/pull/131/files#diff-10
(11)

Patch Links:

https://github.com/fightforthefuture/battleforthenet/pull/131.patch
https://github.com/fightforthefuture/battleforthenet/pull/131.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fightforthefuture/battleforthenet/pull/131, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AC6GjJwKh5EMkooO0nRjfO1nUiR0IDHdks5s5Ln_gaJpZM4QoJi4
.


improve coverage

Codecov Report

Merging #25 (1a586fc) into master (7673809) will increase coverage by 0.68%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #25      +/-   ##
============================================
+ Coverage     84.74%   85.43%   +0.68%
- Complexity      325      327       +2
============================================
  Files            41       41
  Lines          1016     1016
  Branches         62       62
============================================
+ Hits            861      868       +7
+ Misses          128      121       -7
  Partials         27       27

Impacted Files
Coverage Δ

...ithub/md2conf/converter/ConfluencePageFactory.java
100.00% <0.00%> (+100.00%)
:arrow_up:

Continue to review full report at Codecov.

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


Only consider files in expected path (not under) for cmd provides.

Anything with +x in usr/bin/.../node_modules/... was getting marked as a command provided by the apk.
Instead, of considering any path under usr/bin, only consider usr/bin/.
Melange Pull Request Template

Functional Changes

[ ] This change can build all of Wolfi without errors (describe results in notes)

Notes:
SCA Changes

[ ] Examining several representative APKs show no regression / the desired effect (details in notes)

Notes:
Linter

[ ] The new check is clean across Wolfi
[ ] The new check is opt-in or a warning

Notes:

closing this, i guess i oepned it twice.
prefer https://github.com/chainguard-dev/melange/pull/1164/files


Added custom scroll bar

Resolves issue #72
Description -> Added a custom scroll bar of white colour with hidden background
Image ->

Resolves issue #72


deployment on windows is failing in the postprovision phase

The deployment on windows is failing in the postprovision phase. Steps to reproduction :

follow the intructions on the README.md and launch provisioning
On a windows machine the execution of postprovision stage launches a pwsh and runs .\scripts\setup_postgres_database.ps1;.\scripts\setup_postgres_azurerole.ps1;.\scripts\setup_postgres_seeddata.ps1 - setup_postgres_database.ps1
setup_postgres_database.ps1 fails with error ModuleNotFoundError: No module named 'fastapi_app'
The setup_postgres_database.ps1 is not correctly inizialized

Expected result is provisioning and postprovisionin  completes successfully
Please note the postprovision fails on posix as well

So this was happening to me too, I had to create a new setup script and then modify the current scripts to use a relative path instead of the absolute path

Try this fork, I have successfully deployed this about 4 times
https://github.com/mazer-rakham/graphrag-legalcases-postgres/tree/thomas-flock-suggestions


⚠ Adacta-fintech.com has degraded performance

In 63d41b3, Adacta-fintech.com (https://www.adacta-fintech.com) experienced degraded performance:

HTTP code: 200
Response time: 1439 ms

Resolved: Adacta-fintech.com performance has improved in 79087bf after 7 minutes.

Resolved: Adacta-fintech.com performance has improved in 79087bf after 7 minutes.


Time ago

A directive or component to display time since the timestamp.
Features:

Refresh as time goes by
Support Internationalization
Support common time formats (unix seconds, unix milliseconds, ISO 8601)
Support custom formatting

References:

nmn/react-timeago
urish/angular-moment (am-time-ago directive)
yaru22/angular-timeago
moment (i18n)

It would be great to support a level of precision. By default moment.js is limited to 1 level.
1: 2 hours
2: 2 hours, 25 minutes
3: 2 hours, 24 minutes, 44 seconds

Closed with vue-timeago.


adding data to DIKSHA and NISHTHA

@ramya-k-murthy I am seeing grammer rather than grammar. Can you please update that. Thanks.


Compute falling snow levels below sea level

As a downstream user of IMPROVER data I want to be confident that the snowfall levels produced are as realistic as possible.
Pre-requisite: #194, #195
Associated: #318
The falling snow level is the altitude level at which it is predicted that snow will reach prior to being turned into rain. If the snow has not converted into rain upon reaching sea level, then the falling snow level may be set equal to zero, however, a falling snow level of zero may result in a positive bias when different models are merged with varying values for the falling snow level. A solution to this is to extrapolate the falling snow level below sea level.
Acceptance criteria:

Create a plugin for extrapolating the falling snow level below sea level.
Modify the falling snow level plugin and CLI as appropriate.
Include a test for output from falling snow levels when different models are blended and a test for a very cold day when the falling snow level is far below sea level.
Plot the output, preferably within a shareable jupyter notebook.

Closed.


Remove round prop

I was thinking not have too sense mix style props with the component API

Removed some code non related with the original purpose of the PR 🙂


get_mbid() Returns Error On Some (Newer?) Songs

What did you do?
Tried to get my 20 most recent scrobbles.
What did you expect to happen?
Expected to get my recent scrobbles & display the mbid for each track.
What actually happened?
I got a 'pylast.WSError: Track not found', when it got to the 15th scrobble.
Traceback (most recent call last):
  File "test.py", line 13, in <module>
    print('M:',s.track.get_mbid())
  File "/home/devon/.local/lib/python3.8/site-packages/pylast/__init__.py", line 1595, in get_mbid
    doc = self._request(self.ws_prefix + ".getInfo", cacheable=True)
  File "/home/devon/.local/lib/python3.8/site-packages/pylast/__init__.py", line 1126, in _request
    return _Request(self.network, method_name, params).execute(cacheable)
  File "/home/devon/.local/lib/python3.8/site-packages/pylast/__init__.py", line 959, in execute
    response = self._download_response()
  File "/home/devon/.local/lib/python3.8/site-packages/pylast/__init__.py", line 948, in _download_response
    self._check_response_for_errors(response_text)
  File "/home/devon/.local/lib/python3.8/site-packages/pylast/__init__.py", line 978, in _check_response_for_errors
    raise WSError(self.network, status, details)
pylast.WSError: Track not found

Before that track, it would do as expected (either displaying the mbid or saying None). That 15th scrobbled song was a little known song that was just released yesterday. I'm guessing that's related to why it's not being detected correctly & therefore not returned correctly, 'cause other songs before it had no issue. Seems like a problem on last.fm's end, that would need to be worked around?
What versions are you using?

OS: Ubuntu 20.04
Python: 3.8.5
pylast: 3.3

Please include code that reproduces the issue.
The best reproductions are self-contained scripts with minimal dependencies.
import pylast

lfm_key = [insert your own string]
lfm_secret = [insert your own string]
lfm_user = 'AvecPaix'
limit = 20

network = pylast.LastFMNetwork(api_key=lfm_key,api_secret=lfm_secret,)
u = network.get_user(lfm_user)
recent = u.get_recent_tracks(limit=limit)

for s in recent:
    print('M:',s.track.get_mbid())

@April29th Hi! Please could you check #341?

Closing due to lack of response, can re-open if needed.


Localization for copilot webview strings

Added localization for copilot and notification panel.

Dismissed as false positive, they are  constant string not user inputs.


modernized examples

Are there modernized examples for the old examples in
https://github.com/neuraloperator/neuraloperator/tree/master
Thanks,
Nachiket

Can you be more specific? The example scripts in scripts are up to date.

Sorry, my mistake. I didn't look in scripts , just looked in examples.


How open .stats file created by -outlier flag

Hi,
I am using the following code to find the outliers of free surfer segmentation:
python3 qatools.py --subjects_dir /my/subjects --output_dir /my/output --outlier --screenshots-html
This code gives me a folder in my output called outliers. The outlier folder contains the following files:
all.aseg.stats
all.outliers.norms.stats
all.outliers.sample.nonpar.stats
all.outliers.sample.param.stats
all.regions.stats
However, I don't know how to read them in a table.
I already used the following code to read this:
asegstats2table -i /outliers/all.aseg.stats --tablefile /outliers/aseg_stats.txt
but I get the following error:
Parsing the .stats files
Traceback (most recent call last):
File "/Applications/freesurfer/7.4.0/python/scripts/asegstats2table", line 567, in
id_name_map, measurelist = parsed.parse(options.meas)
File "/Applications/freesurfer/7.4.0/python/packages/fsbindings/legacy.py", line 509, in parse
seg = strlst[1] # segmentation id is in the 2nd field
IndexError: list index out of range
I appreciate your help,
Parinaz.

The issue has been solved. I added ".csv" to the file's name, and then I could read it in a table.


Improve PTO packet emission

At the moment, when PTO fires and if handshake is incomplete or there is nothing pending to be sent, quicly marks the oldest two inflight packets as lost, hoping that doing so would add something to the pending list. Then, it emits packets in all possible epochs.
This design is bad. Consider the case of a server.
When it receives the first Initial, it sends two datagrams, one containing Initial+Handshake, the other containing Handshake+1RTT.
Then, when the first PTO fires, the server marks first two QUIC packets (i.e. Initial+Handshake) as lost, and transmits three QUIC packets (i.e. Initial, Handshake, 1RTT ping).
When second PTO fires, the server marks the latter two packets of the first flight (Handshake+1RTT) as lost, and transmits three QUIC packets (i.e. Initial ping,Handshake,1RTT).
When third PTO fires, the server marks the the first two packets of the second flight (Initial,Handshake) are deemed lost. These Initial and Handshake gets retransmitted.
When fourth PTO fires, the server marks the last packet of the second flight (1RTT ping) and the first packet of the third flight (Initial ping), and sends Initial PING + Handshake PING + 1RTT ping.
As can be seen, there are two issues:

quicly does not prioritize CRYPTO data of smaller epochs, therefore there's less chance of making process. The issue would be worse than the above example if the certificate chain is large.
As PTO repeats, amount of PING-only packets in the sentmap increases relative to packets with CRYPTO frames. That makes the situation worse.

I think it's time to start doing the optimal thing when PTO fires.
IMO, when the PTO timer fires, quicly should, mark sentmap entries that are older than one PTO as lost, so that the stream scheduler can pick the stream to be sent based on the priorities.
The downside of doing that naively, sentmap entries older than 4 PTO will be discarded. But in case of severe loss, we might want to make progress when we receive an ACK for packets sent at earlier than 4 PTO from now. Therefore, we'd better retain certain number of sentmap entries beyond 4 PTO. To paraphrase, quicly would evict sentmap entries older than 4PTO only if the number of packets contained in sentmap is above certain threshold (maybe 64 packets?).


Poland 100m

Poland at least 100m mesh for every voivodeship provided as points. There are quite accurate so maybe it will be useful to complement other data sources.  Downloadable as 16 zip files (text format) for each province with 1st and 2nd columns descripting location and 3rd elevation.
http://www.codgik.gov.pl/index.php/darmowe-dane/nmt-100.html

http://www.gugik.gov.pl/pzgik/dane-bez-oplat/dane-dotyczace-numerycznego-modelu-terenu-o-interwale-siatki-co-najmniej-100-m-nmt_100

@slachiewicz and @kamilkonowalik thanks for the links to sources! We'd like to do a new build in 2020 and plan to incorporate this then.


[Unity] Fix ForceNarrowI32 with pod arguments

This PR fixes ForceNarrowI32 for functions that comes with pod arguments.
Test cases are added

will send a separate PR to main and cover the force narrow code.

We might want to send this PR to mainline as well

agree, forcenarrow function is not yet in main, and we should send it later


Editable Draggable Table component

depends on #37

Pull Request Test Coverage Report for Build 121

191 of 275 (69.45%)  changed or added relevant lines in 14 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-11.6%) to 59.619%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/Forms/FormFactory.js
13
14
92.86%

tools/validations/componentFriends.js
0
1
0.0%

src/components/Wizards/CreateVmWizard/BasicSettingsTab.js
44
47
93.62%

src/components/Wizards/CreateVmWizard/CreateVmWizard.js
19
22
86.36%

src/components/Forms/Integer.js
35
53
66.04%

src/components/Table/EditableDraggableTable.js
41
99
41.41%

Totals

Change from base Build 153:
-11.6%

Covered Lines:
233

Relevant Lines:
363

💛  - Coveralls


HDFS-16379. Reset fullBlockReportLeaseId after any exceptions

JIRA: HDFS-16379.
Recently we encountered FBR-related problems in the production environment, which were solved by introducing HDFS-12914 and HDFS-14314.
But there may be situations like this:
1 DN got fullBlockReportLeaseId via heartbeat.
2 DN trigger a blockReport, but some exception occurs (this may be rare, but it may exist), and then DN does multiple retries without resetting fullBlockReportLeaseId. Because fullBlockReportLeaseId is reset only if it succeeds currently.
3 After a while, the exception is cleared, but the fullBlockReportLeaseId has expired. Since NN did not throw an exception after the lease expired, the DN considered that the blockReport was successful. So the blockReport was not actually executed this time and needs to wait until the next time.
Therefore, should we consider resetting the fullBlockReportLeaseId in the finally block? The advantage of this is that lease expiration can be avoided. The downside is that each heartbeat will apply for a new fullBlockReportLeaseId during the exception, but I think this cost is negligible.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 46s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 36s

trunk passed

+1 :green_heart:
compile
1m 26s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
1m 18s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  1s

trunk passed

+1 :green_heart:
mvnsite
1m 26s

trunk passed

+1 :green_heart:
javadoc
1m  2s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 29s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 12s

trunk passed

+1 :green_heart:
shadedclient
22m 29s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 14s

the patch passed

+1 :green_heart:
compile
1m 17s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
1m 17s

the patch passed

+1 :green_heart:
compile
1m 12s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
1m 12s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 51s

the patch passed

+1 :green_heart:
mvnsite
1m 19s

the patch passed

+1 :green_heart:
javadoc
0m 50s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 22s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 12s

the patch passed

+1 :green_heart:
shadedclient
21m 59s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
227m 42s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 47s

The patch does not generate ASF License warnings.

326m 25s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3787/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3787

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux f267ccbfdd60 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 89bb4ae73bd9293008a9d77e52be626958babeef

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3787/1/testReport/

Max. process+thread count
3569 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3787/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Project URLs naming?

There are a few syntaxes for project URLs in Grayskull atm. Looks like Setuptools goes with project_urls. Should we go with that here?
https://github.com/conda-incubator/grayskull/blob/0e51e0205586acf61b10c06370d3f222cd724bf8/grayskull/strategy/py_base.py#L714
https://github.com/conda-incubator/grayskull/blob/0e51e0205586acf61b10c06370d3f222cd724bf8/grayskull/strategy/pypi.py#L280
https://github.com/conda-incubator/grayskull/blob/0e51e0205586acf61b10c06370d3f222cd724bf8/setup.py#L69

Should add this seems to result in the about/home URL being missed for the pyproject.toml case

indeed, I missed that, gonna fix it, thanks


Feature/fetch async

@vitaliy-artyukh not all the commits are signed. Since I squash them - fine for me at the moment.


Add HIP-514 example

Problem
HIP-514 introduces new token precompiles that Hedera supports. Add examples using the new precompiles are supported.
HIP: https://hips.hedera.com/hip/hip-514
The following are not yet support from the list:

getTokenExpiryInfo(address)
updateTokenExpiryInfo(address, Expiry),
updateTokenInfo(address, HederaToken),
isToken(address token)
getTokenType(address token)

Solution
Add example
Alternatives
No response

After poking around a bit, I do not believe that this is ready for examples yet.

@Sean-Tedrow-LB can you please expand what you mean?

The wrappers around the new precompiles have not been pushed to the hedera-smart-contracts repo.  Someone directed me to another repo where there seem to be wrappers around the new precompiles, and there appear to be new helper functions, and they've said that these will eventually be pushed to the hedera-smart-contracts repo, but it all looks unfinished to me.

The hedera-smart-contracts is expected to be updated with the new precompiles by this Friday. I believe @Nana-EC can point you to what they've been using for reference.

Yes, that's what I'm referring to.
Nana directed me to this: https://github.com/hashgraph/hedera-json-rpc-relay/tree/main/packages/server/tests/contracts
Is this interface, including the helper functions, the finalized interface?  Do we know that for certain?  I don't want to write these examples and documentation for them and then have to go back and rewrite them because this isn't the actual interface that is released.

@Sean-Tedrow-LB will remove this issue from this sprint and add it to the next one. By then the hedera-smart-contracts repo should be up to date. thanks!

Depends on:

[ ] https://github.com/hashgraph/hedera-smart-contracts/pull/53
[ ] https://github.com/hashgraph/hedera-smart-contracts/pull/54


Capture request / response body (for POSTs, especially for JSON content type)

https://github.com/glowroot/glowroot/issues/579

Sorry, I wanted to open this PR on my own fork. Closing it.


Would the maintainers be interested in having a cloud-scheduler action?

TL;DR
I did not know where to open this issue and thought maybe here :)
I would like to ask if the maintainers are interested to have a cloud scheduler action?
if yes i can help to setup that.
thanks
cc @sethvargo
Detailed design
No response
Additional information
No response

Hi @cpanato
What would be the use case over gcloud scheduler jobs runs?

more to hook up with the cloud run or functions to trigger, I was setting up a pipeline to deploy a cloud run and needed a cloud scheduler as well, but maybe we can just use the gcloud command and not over complicated 😅

I see - so you mean creating a Cloud Scheduler job instead of invoking it? I'm not sure that's a good use case since IaC would probably be a better fit there.

not a problem :) will close
thanks for the quick reply


Why I always get a 401 unauthorized when uploading fragments of resumable item upload in OneDrive API?

I'm developing a web app with the OneDrive API for OneDrive for Business, but I meet a problem that I always get a 401 unauthorized when uploading fragments of resumable item upload. I'm sure that I have sent a access_token key and even I still get a 401 using a new access_token key from refresh access_token codes.

Hi @imkk - in the headers for the response that returned the 401 there should be a request-id value... can you give that to us? It'll help us see what's going on.

Hello @ificator , I'm sorry to reply to you for a long time. In fact, on the next day after I asked this question I found it's alright for most of files to upload except a file with a name: "《鸟哥的Linux私房菜-基础篇》.pdf", and this is the header info you need: request-id: 914ba59d-a084-3000-b1bf-992f6a196057.

I'll close this issue since we have a new one tracking the same thing.


IS this code reachable?

https://github.com/Ousret/charset_normalizer/blob/58f69f76983fc2042b4f47037c02d2d74ecec2cc/charset_normalizer/models.py#L58C16-L58C78
The outer if would mean that coherence_difference > 0.02
The inner if would require that self.coherence == other.coherence, in other words coherence_difference == 0.0
Am I misunderstanding the code? or was there a mistake here?

Good catch.
This piece of code was intended for some edge cases. And could not have possibly run.
I issued a fix.


[Feature Suggestion] Option to filter by "updatability"

As the title suggests, this would add a filtering option to only display mods that have an available update.
An alternate implementation could be done with another Sorting option, one that would bump mods with updates available to the top of the mod list.
The use case is for someone like me, whose eyes tend to skip over the small icon that indicates a mod can be updated.

Just type update into the search box.  :)

Just type update into the search box. :)

Ahhh thank you!!! However, as nice as this is to know now, I still think a button to magically show them would be nice. :3

There probably will not be a dedicated button for an update filter, but some other change such as pinning updatable mods is likely to come in the future. Syntax highlighting in #498 will make the updates search term more discoverable as well.

Fair enough... that PR looks VERY promising. :D


[Refactor] add default_cluster in LocalMetaData and Database

Signed-off-by: zombee0<EMAIL_ADDRESS>What type of PR is this：

[ ] bug
[ ] feature
[ ] enhancement
[x] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

add default_cluster in LocalMetaData and Database so that can remove it from stmt safely.

[FE PR Coverage Check]
:disappointed: fail : 5 / 9 (55.56%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/server/LocalMetastore.java
4
8
50.00%
[502, 614, 630, 631]

:large_blue_circle:
com/starrocks/catalog/Database.java
1
1
100.00%
[]

run starrocks_admit_test


python connector added

The Python Connector is a web service that securely executes Python scripts and functions. It offers two routes for script execution and function invocation, providing features like secure code execution, detection of dangerous operations, module installation with pip, and support for code execution or script file upload. The service is designed to parse and check code using the ast module to prevent harmful operations. Users can make HTTP requests to execute Python code securely and obtain the results as JSON responses. The service is built with Python, Flask, and RestrictedPython, and it ensures secure execution of code in a restricted environment. Users are advised to review and validate code executed in the service to ensure security.

This code is not a part of workflow engine. It is independently deployable.
Rejecting the PR.
Expected: Add only a code snippet in workflow engine which can call the python connector


polymer/test/property_observe_test sometimes times out in Dartium/windows

See:
http://chromegw.corp.google.com/i/client.dart/builders/dartium-win-inc-ninja-be/builds/3289/steps/dartium_core_unchecked_tests/logs/stdio
Marking it as Pass, Timeout.

This issue has been moved to dart-lang/polymer-dart#209.