optional senses

I'm using VSCode in Windows 10 with extension Visual Studio IntelliCode v1.2.10 for Python, with Python 3.9 installed.
I would like to see to see option's too:
A- resize the inteli window that pop's up with suggestions
B- cancel the inteli window via .json settings, on certain parameters
such as the print function, as I do not need a window the size of
half my screen popping up telling me all the options I have using
the print function.
Thank you!
You all rock!

Product and Version [VS/VSCode]:
OS Version [macOS/Windows]:
IntelliCode Extension Version:
Target Platform or Language [e.g. Node.js]:
Steps to Reproduce / Scenario:

Hi @TGauthier2011, the above screenshot is of IntelliSense in Visual Studio Code not IntelliCode, the stars on items you get at the top of your IntelliSense completions list. As you mentioned the settings.json file is the right location for customizing IntelliSense, however, you are not currently able to customize WHEN to show/not show the IntelliSense window on certain parameters.
For more information, you should check out IntelliSense in VS Code.
Please let me know if the IntelliCode team can help you further?
Cheers,
Caty, Program Manager


Create e7.custom_error_types.md

The main points are fantastic, and these wording changes would help me more easily read and consume the contents.

Duplicate PR https://github.com/learning-rust/site/pull/56


Add Dockerfile for job-server

This change adds a new Dockerfile.job-server for the job-server image. This image is built within Cloud Build and does not need to be publicly accessible.

This change is

Pull Request Test Coverage Report for Build 121

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

Totals

Change from base Build 119:
0.0%

Covered Lines:
390

Relevant Lines:
406

💛  - Coveralls

Part of:

https://github.com/m-lab/uuid-annotator/issues/48


Align broadcast

Removed partial_align()
Added exclude and indexes optional parameters to align() public API
Added exclude optional parameter to broadcast() public API
Added various unit tests to check that align() and broadcast() do not perform needless data copies
broadcast() to automatically align inputs

Note: there is a failed unit test, TestDataset.test_broadcast_nocopy, which shows broadcast on dataset doing a data copy whereas it shouldn't. Could you look into it?

can you add a brief note to "what's new"?
I'm going to issue another bug fix release shortly, would be nice to get this in :)

Updated what's new, fixed unit test bug, and added auto-align to concat().
I plan to add auto-broadcast to it as well eventually, but I realised it's not trivial as when doing it on datasets you must perform it pairwise. I'll leave it for later.

OK, this looks great to me! I especially appreciate all the extra test coverage.
I will merge once the CI tests are green.

Actually, tests were passing on the previous commit (pre doc fixes) so I decided to go ahead.
Thanks Guido!


reamde: add cachix instructions to CONTRIBUTING.md

You have a typo in the commit name ("reamde").

You have a typo in the commit name ("reamde").

whoops


feat: auth | logout on session expire

Fixes Issue

Changes proposed

Screenshots

Note to reviewers

Code of Conduct

[ ] By submitting this pull request, I confirm I've read and complied with the CoC 🖖

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

You can also join our Discord community.
Feel free to check out other cool repositories of the Thecyberworld.
Join the Thecyberworld GitHub Organisation by raising an issue (you will be sent an invitation).

https://github.com/thecyberworld/TheCyberHUB/assets/76536506/8d1e6f0d-1460-46e1-814b-0fd05793e988
https://github.com/thecyberworld/TheCyberHUB/assets/76536506/2e75b9f4-bddd-4092-8674-7b5f83a139bc
@kabir0x23


Add new Purview API version 2024-04-01-preview with assignIdentity API.

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

[!NOTE]
As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Click here to see the details of Step 1, Breaking Changes review
If you are in purview of Step 1 of the diagram, follow the Breaking Changes review process.
IMPORTANT! This applies even if you believe your PR was mislabeled, for any reason, including tool failure.

Click here to see the details of Step 2, ARM review
See https://aka.ms/azsdk/pr-arm-review.

 Click here to see the diagram footnotes
Diagram footnotes
[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[x] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with PR workflow diagram Step 2 (ARM review), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

/azp run

    "responses": {

Delete should not really be accepting query params like this. The platform will not support it.
If you do it this way for example you will not be able to use policy to soft delete the resource.
A better way to model this is to have a property on the object: "DeleteMode" : ""SoftDelete" and always honor that property during delete

Refers to: specification/purview/resource-manager/Microsoft.Purview/preview/2024-04-01-preview/purview.json:253 in e9db665. [](commit_id = e9db66567521a132734b96ac531dfcef2c38310d, deletion_comment = False)

      "readOnly": true

could you use the definitiosn from commontypes instead : https://github.com/Azure/azure-rest-api-specs/blob/main/specification/common-types/resource-management/v5/privatelinks.json

Refers to: specification/purview/resource-manager/Microsoft.Purview/preview/2024-04-01-preview/purview.json:2796 in e9db665. [](commit_id = e9db66567521a132734b96ac531dfcef2c38310d, deletion_comment = False)

"version": "2024-04-01-preview"

Your fist commit does not have the previous version as a base commit. Was this PR created using openapi hub ?

Refers to: specification/purview/resource-manager/Microsoft.Purview/preview/2024-04-01-preview/purview.json:6 in e9db665. [](commit_id = e9db66567521a132734b96ac531dfcef2c38310d, deletion_comment = False)

We're starting a new GitHub PR for the API Version 2024-04-01-preview as there have been certain revisions to the feature set intended for this release now. Closing this PR.


[Docs] GKE Workload Identity has changed

Describe the bug
About a week ago, google cloud changed how workload identity works on GKE, so we no longer need to create a service account, attach roles and permissions to it.
https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity
Users can now assign permissions to the secret or project to the below, which is the kubernetes service account of the secretStore:
principal://iam.googleapis.com/projects/PROJECT_NUMBER/locations/global/workloadIdentityPools/PROJECT_ID.svc.id.goog/subject/ns/NAMESPACE/sa/KSA_NAME

Does this work for ClusterSecretStore?
I have no idea, which is why I am opening this issue, as I know it works for SecretStore and before I open a PR to update the docs I thought I would check and see if other GCP users have come across this
Additional context
Page: https://external-secrets.io/latest/provider/google-secrets-manager/#creating-workload-identity-service-accounts
Add any other context about the problem here.

Just waiting to see if others have this issue then I'll contribute docs


Record event when image GC fails.

All tests are green :)

/cc @dchen1107 @yujuhong

Rebase please :-)

Rebased and green, PTAL @dchen1107 :)

Travis failing...? :)

Suuuuper weird, it was an infrastructure failure on code that didn't exist :-\ kicking off again.

LGTM.


(ios) fixes background thread problem in pickContact method

This fixes  #228

Can we have the new version with this fix?

Can we have the new version with this fix?

Before we can merge or make a release, the plugin needs to have it's testing tools updated. The tests are failing because it's still using versions that are no longer supported. To get this PR merged, I'd also like at least one other PMC member to vote green.
For the record, I don't believe anything in this change is causing the test to fail, just travis and appveyor configs needs to be updated. I have some time, I'll make those changes now. Once the test changes are merged in, I'll restart the checks here, and if they turn green I'll start nudging people to take a look.

@breautek Ok sure. Thanks!

Actually there won't be any releases (and I'll probably won't convince anybody else for a green check) as this plugin is deprecated. My apologies, I didn't realise this plugin was deprecated initially.
See https://github.com/apache/cordova-plugin-contacts#deprecation-notice and https://cordova.apache.org/news/2017/11/27/Deprecation-of-cordova-contacts-plugin.html for more details.
I personally don't know of any migration strategy or alternate solution, feel free to use your own fork of this plugin.

@breautek Yes, I have manually applied this fix https://github.com/apache/cordova-plugin-contacts/pull/229/commits/868cfba60d2328306e3bb13bf98643c08c501622 on this plugin and it works. I use 2.3.1 Thanks!

@breautek Yes, I have manually applied this fix 868cfba on this plugin and it works. I use 2.3.1 Thanks!

Hi, I'm experiencing this issue as well. How do I apply the fix to my project? Thanks.

@zimejin You need to add this fix https://github.com/apache/cordova-plugin-contacts/pull/229/commits/868cfba60d2328306e3bb13bf98643c08c501622 to here src/ios/CDVContacts.m

We are archiving this repository following Apache Cordova's Deprecation Policy. We will not continue to work on this repository. Therefore all issues and pull requests are being closed. Thanks for your contribution.


Linux build environment

What is the recommended build environment for compiling this on linux? A small guide would be appreciated

You need to install msbuild and gcc. Then you can just use the make file to build the whole project if I remember correctly.

Install Mono >= 5 (http://www.mono-project.com/download/stable/)
sudo apt-get install gcc
git clone https://github.com/ReClassNET/ReClass.NET.git
cd ReClass.NET
make update
make debug

Copy NativeCore.so from
/ReClass.NET/NativeCore/Unix/build/debug
to
/ReClass.NET/ReClass.NET/bin/Debug/x64
Maybe someone with more knowlegde about make files could add the copy?
Then start ReClass.NET and get the error System.IO.FileNotFoundException: /ReClass.NET/ReClass.NET/bin/Debug/x64/NativeCore.so :confused:
Currently don't know what's the problem here.


React to changes in produced corefx packages

Corefx removed these from the package list
@natemcmaster @Eilon Need this for the 2.1.7 build.

@Eilon Yeah, a couple packages were incorrectly added.


Fixed #192. Mobile nav menu height too tall.

Moved nav menu height setting to media at-rule to ensure it is only
applied when viewport is at least medium (when standard nav menu is
displayed: >991px).

You also updated Font Awesome from 4.5.0 -> 4.6.2, was that intentional?


Feat/Bug: Set the value of _ (underscore) to the value of the last ruby expression

Your proposal
Pry and IRB have a feature in which _ is always set the the value of the last expression. While I realize it may not make sense to do this with debug commands, it would be nice if the feature was there at least for Ruby expressions. The current behavior seems to be setting _ to the last error, but seemingly only for debug commands like ls. This is kind of a bug in the irb_console since IRB has this feature normally but it stops working after entering debug mode.
Additional context
Shell session:

irb(#<Foobar:0x000000011efeb9f0>):001> 3+3
=> 6

irb(#<Foobar:0x000000011efeb9f0>):002> puts _
6
=> nil

irb(#<Foobar:0x000000011efeb9f0>):003> 4+4
=> 8

irb(#<Foobar:0x000000011efeb9f0>):004> info
(rdbg:irb) info
%self = #<Foobar:0x000000011efeb9f0 @foo="bar">
@foo = "bar"

irb:rdbg(#<Foobar:0x000000011efeb9f0>):002> puts _

nil

irb:rdbg(#<Foobar:0x000000011efeb9f0>):003> 4+4
8

irb:rdbg(#<Foobar:0x000000011efeb9f0>):004> puts _

nil
irb:rdbg(#<Foobar:0x000000011efeb9f0>):005> 4+4
8

irb:rdbg(#<Foobar:0x000000011efeb9f0>):006> info
%self = #<Foobar:0x000000011efeb9f0 @foo="bar">
_ = nil
@foo = "bar"

irb:rdbg(#<Foobar:0x000000011efeb9f0>):007> ls Bar
Traceback (most recent call last):
	24: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:212:in `block in activate'
	23: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:254:in `session_server_main'
	22: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:365:in `process_event'
	21: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:403:in `wait_command_loop'
	20: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:403:in `loop'
	19: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:404:in `block in wait_command_loop'
	18: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:444:in `wait_command'
	15: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:1981:in `intercept_trap_sigint'
	 4: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/irb_integration.rb:9:in `evaluate'
(irb):7:in `set_foo': uninitialized constant Foobar::Bar (NameError)`

irb:rdbg(#<Foobar:0x000000011efeb9f0>):008> puts _
uninitialized constant Foobar::Bar
nil

irb:rdbg(#<Foobar:0x000000011efeb9f0>):009> ls Bar
Traceback (most recent call last):
	24: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:212:in `block in activate'
	23: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:254:in `session_server_main'
	22: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:365:in `process_event'
	21: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:403:in `wait_command_loop'
	20: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:403:in `loop'
	19: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:404:in `block in wait_command_loop'
	18: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:444:in `wait_command'
	15: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/session.rb:1981:in `intercept_trap_sigint'
	 4: from /Users/joesharp/.asdf/installs/ruby/2.7.8/lib/ruby/gems/2.7.0/gems/debug-1.9.1/lib/debug/irb_integration.rb:9:in `evaluate'
(irb):9:in `set_foo': uninitialized constant Foobar::Bar (NameError)`

irb:rdbg(#<Foobar:0x000000011efeb9f0>):010> info
%self = #<Foobar:0x000000011efeb9f0 @foo="bar">
_ = #<NameError: uninitialized constant Foobar::Bar>
@foo = "bar"

irb:rdbg(#<Foobar:0x000000011efeb9f0>):011> Bar.methods
eval error: uninitialized constant Foobar::Bar
  (rdbg)/scratch.rb:1:in `set_foo'`
nil

irb:rdbg(#<Foobar:0x000000011efeb9f0>):012> info
%self = #<Foobar:0x000000011efeb9f0 @foo="bar">
_ = nil
@foo = "bar"

irb:rdbg(#<Foobar:0x000000011efeb9f0>):013> Bar.methods
eval error: uninitialized constant Foobar::Bar
  (rdbg)/scratch.rb:1:in `set_foo'`
nil

irb:rdbg(#<Foobar:0x000000011efeb9f0>):014> puts _

nil

Please let me know if the bug portion of this (_ stops working in IRB when entering debug mode) should be filed as a separate issue. Thanks!

Additionally, please note in the "Session Variables" section of https://docs.ruby-lang.org/en/2.2.0/IRB.html#module-IRB-label-Commands that IRB also supports __ (double underscore) and __[line_no] when configured to do so. It always supports the single underscore for the last value though.

Please let me know if the bug portion of this (_ stops working in IRB when entering debug mode) should be filed as a separate issue. Thanks!

Yes please open a separate issue in IRB, thank you!


python311Packages.pydrawise: 2023.12.0 -> 2023.12.1

Diff: https://github.com/dknowles2/pydrawise/compare/refs/tags/2023.12.0...2023.12.1
Changelog: https://github.com/dknowles2/pydrawise/releases/tag/2023.12.1
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

1 package marked as broken and skipped:

home-assistant-component-tests.hydrawise

4 packages built:

python310Packages.pydrawise
python310Packages.pydrawise.dist
python311Packages.pydrawise
python311Packages.pydrawise.dist


flocker-node should be easily installable on modern Ubuntu

We originally considered packaging Flocker for Ubuntu in #86, but at the time we decided that it was easier to document the installation via pip and virtualenv instead. Those instructions were then reproduced in a simple linux-install.sh script.
But it would eventually be nice if flocker-node could be easily installed on an existing Ubuntu / Debian server and the easiest mechanism is probably by creating a deb file.
But we'll create a sumo style deb file which includes all the dependencies in a virtualenv. That's the strategy proposed for our flocker-node RPM package in #508
This is probably going to require some sub-issues. For example:

Create Debian compatible version numbers
Run fpm to build the deb package
Create a Debian package repo.
Automate or document:

uploading the deb to our repo
regenerate the deb repo metadata

A followup ticket will be to package flocker-deploy in the same way.

We are moving our development planning to JIRA. This issue is now being tracked at https://clusterhq.atlassian.net/browse/FLOC-864. You are welcome to file additional issues in GitHub if that's easier for you.


this code do not display the last page I opened

https://github.com/barteksc/AndroidPdfViewer/blob/d243b39377f19c3eae41e227067da254ebbf731b/sample/src/main/java/com/github/barteksc/sample/PDFViewActivity.java#L118

Right, I tried this but not working...
Please help us

Store the current page number with shared preference or simple SQLite database.
Then pass the stored page number as the default page. Will drop code soon


[draft] dont add a partition if it already exists but the getPartition fails …

…with TException, dont alter a partition if a partition does not exist but the add_partition fails with TException
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-XXX

Description

[ ] Here are some details about my PR, including screenshots (if applicable):

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3344 (25e019d) into master (1367614) will decrease coverage by 3.54%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3344      +/-   ##
============================================
- Coverage     46.54%   42.99%   -3.55%
+ Complexity    10137     1940    -8197
============================================
  Files          2052      394    -1658
  Lines         79563    16877   -62686
  Branches       8882     2076    -6806
============================================
- Hits          37032     7257   -29775
+ Misses        39098     8821   -30277
+ Partials       3433      799    -2634

Impacted Files
Coverage Δ

...in/java/org/apache/gobblin/cluster/HelixUtils.java
32.23% <0.00%> (-2.48%)
:arrow_down:

...n/service/modules/dataset/FSDatasetDescriptor.java

...gobblin/source/DatePartitionedNestedRetriever.java

...in/runtime/cli/PublicMethodsGobblinCliFactory.java

...untime/troubleshooter/TroubleshooterException.java

.../org/apache/gobblin/writer/AsyncWriterManager.java

...org/apache/gobblin/stream/FlushControlMessage.java

...nt/retention/version/FileStatusDatasetVersion.java

...nt/copy/UnixTimestampRecursiveCopyableDataset.java

...copy/predicates/RegistrationTimeSkipPredicate.java

... and 1651 more

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 1367614...25e019d. Read the comment docs.

@sv2000 please review/merge

@autumnust please review/merge

Just want to confirm that have you verified when there is partition, add_partition will throw AlreadyExistsException but not other exception? Same for get_partition and NoSuchObjectException. Asking because I barely remember I do see some other TException been throw when there is no partition exist. If that's not the case, the PR LGTM

@arjun4084346 Just want to confirm that have you verified when there is partition, add_partition will throw AlreadyExistsException but not other exception? Same for get_partition and NoSuchObjectException. Asking because I barely remember I do see some other TException been throw when there is no partition exist. If that's not the case, the PR LGTM

Yes, I verified. Also added a unit test to confirm what exact exception hive client returns in case a) partition already exists, b) partition does not exist.


Expand mensa menu coverage

[ ] Coverage of CK1
[ ] Coverage of Ulf

Users have also mentioned a potential interest in the film-mensa


RFC (DRAFT) - less magical API

current sketch
but:

only one syntax for CoLists, more regular:

class Chat extends CoList {
  item = Message
}

what about avoiding the "instance" syntax in favor of partial application (effect.ts-style)? this way we can have compile time validations for field names, and avoid generic static methods when they're not really generic but bound to the declaration (like .create): https://tsplay.dev/wQQ6jw
class Message extends CoMap.Of<Message>()({
  text: co.string,
}) {}

I agree that it's not the prettiest thing (the example of class Chat extends CoList { item = Message } is much nicer) but it's practical and very powerful

what about avoiding the "instance" syntax in favor of partial application

Which use cases are you imagining for the partial application in lists?

Explainer
The major difference with the current APIs is how the CoValues are consumed and represented as "values".
Now the load functions are returning CoValues as instances of the schema class, requiring us to use Proxies and do magic in order to make Typescript types to work correctly.
We are going to change this in order to have more flexibility on what to return when a user reads a CoValue.
So APIs like useCoState are going to never return undefined but the return type will be a uninon like this one:
type Unloaded<T> = {$state: "unloaded", $jazz: { id: string }}
type Loaded<T, D> = {
    $state: "loaded",
    $kind: T[Kind]
    $jazz: {id: string, other: "magic", update: UpdateFn<T>}
} & ValueOf<T> & DepthResolution<D>

Example:
const [value] = useCoState(Message, messageId, {})

if (value.$state === "loaded") return null

return <MessageContent content={message.text} author={message.$jazz.createdBy} />

Another important difference will be on the update API.
Instead of using seamless mutations we will move toward an update function.
The update function will work with an API similar to Immeer's produce:
const [item, updateItem] = useCoState(TodoItem, id, {})

function handleChange(evt) {
  updateValue(item => {
    item.value = evt.target.value
  })
}

Like the Loaded type suggests it will also be possible to call the update function via $jazz.update for which the callback returned by useCoState is just a shortcut.
This new iteration of the API is more friendly with the frontend frameworks because:

the React Compiler was flagging our update system as a violation of the Rules of React. It wasn't because the updates were immutable but on the compiler perspective there is no way to tell the difference between a mutation and a "proxied" mutation like ours.
returning proxied values was making harder for us to integrate with the rest of the main frameworks (Vue, Svelte and Solid). Returing plain objects should make it way easier.

@aeplay
We might add an API that triggers suspense and always return the loaded/fresh value:
const [item, updateItem] = useCoState(TodoItem, id, {})

const data = item.$use(); // always Loaded

This would make the code much more cleaner because there would be:

No type guards to add to check if the value is unloaded
No load state to manage internally the component
The rejection would be handled with an ErrorBoundary

We should also have a dedicated state for the CoValues that can't be accessed for a lack of permissions.
e.g. by returning $state = 'access-not-allowed'

Another important point is that we are going to remove the auto-subscription that currently works by accessing to CoValues refs that aren't declared in the deep loading object.
We found that it creates confusion and relies on Proxy which makes our integration with non-react frameworks less efficient.
But, as suggested by one of our main adopters, we should still keep the ability of downloading part of the data in background and not making it render-blocking.
This is the greatest perk of the auto-subscription, but since it's too magical most of the time devs don't realize that they are using it.
We can keep this feature by adding an API that achieves the same result but in a more explicit manner:
Example
const [issue] = useCoState(Issue, id, {})

return <>
<h1>{issue.title}</h1> {/* This is rendered before we start loading the comments */}
{issue.comments.map((comment) => {
  const data = comment.$subscribe({ author: { profile: {} } }); // This subscribes to the comment content and returns `Unloaded` until everything declared in the resolve is fully loaded

This way the data flow will become more clear, Typescript more friendly, and the refactoring in multiple components can be easier.


isValidTag check is not correct for regexp

Hello,
I'm trying to apply a custom regexp on a field, something like:
type ParamsHook struct {
	Name string `json:"name" valid:"required,matches(^\\$[A-Za-z]$)"`
}

But because of the isValidTag check, my regexp appears as invalid.
The code of the function in validator.go is:
switch {
case strings.ContainsRune("!#$%&()*+-./:<=>?@[]^_{|}~ ", c):
	// Backslash and quote chars are reserved, but
	// otherwise any punctuation chars are allowed
	// in a tag name.
default:
	if !unicode.IsLetter(c) && !unicode.IsDigit(c) {
		return false
	}
}

Why backslash are not allowed in tags ?
How to achieve what I want to do?
Thank you

This fix has since disappeared from the code (overwritten by a later merge). Can you please put it back?

https://github.com/asaskevich/govalidator/pull/205


Wrong sign in Focal length parameter?

I see ray-optics simulator is using image focal length as parameter for ideal lens and ideal mirrors, but the name of the parameter is "focal length", not "image focal length".
This is confusing especially in ideal mirrors, since mirrors do not have "image focal points", just "focal points":

a concave mirror has a negative focal length
a convex mirror has a positive focal length
see this example for a convex mirror: focal length should be +100, not -100: https://screenrec.com/share/yxwoefucJ9

Could you change the parameter sign for ideal lens and ideal mirrors?

I followed the sign convention of the General Physics textbook I used. I think it is also the sign convention used in most high schools and universities. For example:
https://www.physics.louisville.edu/cldavis/phys299/notes/lo_spmirror.html

I see your text book is using the right sign convention: https://screenrec.com/share/aWCF4QjkrJ
that is, a convex mirror has a positive focal length, but in simulator we see this negative: https://screenrec.com/share/yxwoefucJ9

In my text book, if rays come from left to right, distances are measured positive to the right of vertex, negative to the left (Spanish):
https://screenrec.com/share/J3bX4RSMGD
See this reference in English:
https://www.excellup.com/classten/scienceten/lightreflection4.aspx
And tthis video:
https://www.khanacademy.org/science/in-in-class10th-physics/in-in-10th-physics-light-reflection-refraction/in-in-sign-conventions/v/sign-conventions-for-mirror-lenses

In my text book, if rays come from left to right, distances are measured positive to the right of vertex, negative to the left (Spanish):
https://screenrec.com/share/J3bX4RSMGD
See this reference in English:
https://www.excellup.com/classten/scienceten/lightreflection4.aspx
And this video:
https://www.khanacademy.org/science/in-in-class10th-physics/in-in-10th-physics-light-reflection-refraction/in-in-sign-conventions/v/sign-conventions-for-mirror-lenses
Check video transcript ("negative focal length automatically implies concave mirror, positive focal length implies convex..."):
https://screenrec.com/share/iMSL9ebwIK

I added a checkbox for ideal curved mirror for the convention you mentioned (the Cartesian Sign Convention). For ideal lens, I think the Cartesian Sign Convention gives the same sign as the original convention, so no change is made.
This option is off by default, since most of the General Physics textbooks in use still follow the old convention (as far as I know). And at least in Taiwan, the high school education also uses the old convention (see the sentence below equation 4-2 on page 10 of https://moodle.fg.tp.edu.tw/~tfgcoocs/blog/wp-content/uploads/2015/10/高三物理4-2球面鏡課本_空白.pdf).
If the new convention is the default in some country/region and the locale for that country/region is added, this option can be on by default for that locale.

I understand now, thanks for the explanation. I think this solution is perfect, thank you!
Have you considered the same solution for ideal lens?
I've studied that a convergent lens has a negative focal length (or a positive image focal leght), whereas a divergent lens has a positive focal length (or a negative image focal leght)
https://screenrec.com/share/dRqZjfUxtl

I use Google Lens to translate the link, but I only see "image focal length", not "focal length". Is there a reference that defines the "focal length" as you mentioned?

you can find the definition of "focal length" and "image focal length" here:
https://www.fisicalab.com/apartado/lentes-delgadas
again sorry for the Spanish, go to section "Focos"
https://screenrec.com/share/2UO8QRmade

I checked this at Wikipedia:
https://en.wikipedia.org/wiki/Focal_length#General_optical_systems
"Back focal length or back focal distance is the distance from the vertex of the last optical surface of the system to the rear focal point (F′)."
They use the term "back focal length", but I prefer "image focal length" because in divergent lens F' is at the front.
I think we can avoid sign convention misunderstanding just with your solution above?

Note that in the "thin lens approximation" section of that wiki article, it only uses "focal length", and the sign convention is the same as the simulator. I think the distinction you mentioned is only for thick lens, where the optical system is regarded at two separate surfaces having their own focal lengths.
Therefore, in this simulator, only the "Spherical lens" tool may have this concern, not the ideal (thin) lens. Currently, the only number-parameter for that tool is the refraction index, so nothing need to be changed for now.
On the other hand, if the Spanish education system always uses that term, even for thin lens, then the Spanish for "image focal length" should be used for the Spanish locale of the simulator (which does not exist yet. It would be a great idea to contribute a new locale by translating index.html and simulator/locale/en.js, then open a pull request.)

ok, understood
thank you!


[cors] Use JDK'S URI class for origin parsing

As suggested by @zugazagoitia in #2104, we should consider rewriting the custom host scheme port logic in the CORS plugin to use the JDK's URI class.
I plan to look into this next weekend.

Yes, it is. An IPv6 or a domain name (any string of characters) are valid origins.
The Origin header contains a scheme, host and optionally a port. The host, defined by the URI spec is not limited to TLDs, localhost or any internal DNS names are also valid, as well as IP literals.

I'm not sure how we can match using the URI class, it'll end up relying upon some manual parsing or regular expression, but we can use the URI class to normalize/validate non-wildcard URIs since they have already implemented the standard for us.


Implemented Animal in C#

Stayed true to the original's behavior and intent.
Added methods to clean up the code and a poor-man's tree structure instead of a list of magic strings.
Implemented with C# 9's new top level statements to reduce boiler plate.
Hopefully this aligns with the project's goals.  Feedback is welcome.

Hey thanks!! 🤗


Member & Origin systems missing features

Make UI popups on first login
On this popup suggest user to enter his Origin name.

Add popups with status when ncickname changed
Tell user if he is accepted into BoB or suggest joining BoB platoon. Also show any error if happens.

Add tracking of applications on Members admin panel. Also, add "if representing" column.

Update user object when new Origin name provided.

I will make Frontend changes, @zefanjajobse Is API ready for that? Also, looks like "if representing" working not on every platoon or player.


feat: write secrets as export commands

The type of this PR is: Feat
This PR supports PHIRE-1097
Related to https://github.com/artsy/hokusai-sandbox/pull/74
Description
Currently, the secrets file is written in this format:
FOO=bar
BAR=foo

A client that wants to export the vars into Shell environment must do something like this:
export $(cat /secrets/secrets | xargs)

This PR changes the output format to:
export FOO='bar'
export BAR='foo'

The changes are:

The content becomes export commands.
Values are single quoted.

This allows the client to simply do:
source /secrets/secrets

This looks fine assuming values cannot contain single quotes, since they will not be escaped... how true is that?

Great question. I assumed that secret values don't contain single quotes, as I didn't recall seeing one that does. But I am not sure. Let me survey the main apps (Gravity, MP, Force, Gemini, Volt).

Surveyed, in Staging. None of those apps have single quotes in their vars.

In Zenith we just use the dotenv parser (see here) since ENV file parsing is tricky.

Oh, I did not know about python-dotenv. It looks like exactly what we want for app container to load vars from file to env. But I wonder how we can integrate it with k8s apps, instead of the current shell sourcing.

@artsyjian Yes it could be tricky to integrate dotenv with all the apps unless you have some kind of init hook where you can install packages onto the image... I'm not sure how initContainers work but could it just be another one of those?

@artsyjian Yes it could be tricky to integrate dotenv with all the apps unless you have some kind of init hook where you can install packages onto the image... I'm not sure how initContainers work but could it just be another one of those?

There can be multiple init containers. So if we can get Python and all required libs and dotenv script stored under  one directory that is then mounted to the app container via a volume, similar to how /secrets/secrets is mounted, then the script can be run in app container. Seems it'd be brittle, though. And the init container's image or Python/libs/script-installation would still have to vary with the different types of project base images (e.g. alpine, debian, ubuntu, ...).


PreserveCompilationContext breaking change

Addresses https://github.com/aspnet/Announcements/issues/460.
Internal preview

Thanks Rick! Could you label all except the first announcement (# 461) as documented? https://github.com/aspnet/Announcements/issues

All as in 458-460? If so, done.

Thank you! Can you also label 454 and 457?

Done.


feat: Support querying nested fields

Codecov Report

Merging #329 (6da02c8) into main (7ba6e98) will increase coverage by 0.53%.
The diff coverage is 68.93%.

@@            Coverage Diff             @@
##             main     #329      +/-   ##
==========================================
+ Coverage   28.63%   29.16%   +0.53%
==========================================
  Files          60       60
  Lines        6446     6500      +54
==========================================
+ Hits         1846     1896      +50
- Misses       4384     4388       +4
  Partials      216      216

Impacted Files
Coverage Δ

server/metadata/tenant.go
34.21% <0.00%> (ø)

server/services/v1/query_runner.go
0.00% <0.00%> (ø)

server/services/v1/search_reader.go
0.00% <0.00%> (ø)

server/services/v1/search_indexer.go
15.29% <60.46%> (+15.29%)
:arrow_up:

schema/collection.go
65.81% <63.33%> (+0.23%)
:arrow_up:

query/filter/selector.go
30.23% <66.66%> (ø)

query/filter/filter.go
58.33% <75.00%> (ø)

schema/fields.go
76.58% <89.13%> (+1.87%)
: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 7ba6e98...6da02c8. Read the comment docs.

LGTM. Left minor remarks, nits only.

Where is the function PackSearchField used? Should it be ported to use FieldType or if not used, removed?

Some cleanup remaining, good catch. Let me remove it and fix all the comments :)


Add quick action to ignore line

Currently to ignore a line one has to manually add a # noqa  comment. This could be added as a quick action in the pop-up message.
For example this is what SublimeLinter-flake8 looks like:

clicking on the blue arrow triggers:
import scienceplots  # noqa: F401

This is already supported through code action.
https://github.com/user-attachments/assets/655993d2-bcda-40e7-95e5-f5ede5361c4c
You can trigger code actions in multiple ways - from the popup, through right click, menus or keyboard shortcut (needs to be manually assigned).

You are correct, don't know how I missed that. Thank you


Initial install of kvm, kpm and k breaks

I just did a fresh Ubutnu 14.10 and followed the Home section to install Mono and then KVM using
curl -sSL https://raw.githubusercontent.com/aspnet/Home/master/kvminstall.sh | sh && source ~/.kre/kvm/kvm.sh
I did a kvm upgrade and it came back saying I need unzip - So I installed unzip via apt but then the next time I ran kvm upgrade it came back saying
root@vnext:~# kvm upgrade
Determining latest version
Latest version is 1.0.0-beta2
KRE-Mono.1.0.0-beta2 already installed.
Cannot find KRE-Mono.1.0.0-beta2, do you need to run 'kvm install 1.0.0-beta2'?

I cannot use k or kpm
I had to fix this manually, I just took a lucky shot and deleted the directory KRE-Mono... under ~/.kre/packages rerun kvm upgrade and this time it installed properly.
Now I have k and kpm

I had the same issue on a linux machine (Ubuntu 14.04 x64 vmlinuz-3.13.0-36-generic).
Your workaround worked!

Thanks this helped me out, would never have thought of that


Test with Angular 8 and update if all good

carbon-components-angular now supports Angular 8, let's update!

@youda97, assign yourself if you have time.

Closed by #15


dependency_overrides not working through Path Operation decorator?

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
from fastapi import FastAPI, Depends

from project.config import Settings

def get_settings():
    return Settings()

app = FastAPI()

@app.get("/info")
async def info(settings: Settings = Depends(get_settings)):
    print(settings)
    return {
        "app_name": settings.app_name,
        "admin_email": settings.admin_email,
        "items_per_user": settings.items_per_user,
    }

@app.post("/things", status_code=201, dependencies=[Depends(get_settings)])
async def update(email):
    print(get_settings())
    returned_thing = put_decision(email, get_settings())
    return {"thing": returned_thing}

def put_decision(email, settings):
    s = email
    s += " " + str(settings.items_per_user)
    return s

Description
I am trying to run some tests with pytest against FastAPI. I am having an issue overriding a dependency that I've specified using depends and dependency_overrides. The settings get overridden fine in the GET endpoint but not in the POST endpoint.
Here is my main.py file:
from fastapi import FastAPI, Depends

from project.config import Settings

def get_settings():
    return Settings()

app = FastAPI()

@app.get("/info")
async def info(settings: Settings = Depends(get_settings)):
    print(settings)
    return {
        "app_name": settings.app_name,
        "admin_email": settings.admin_email,
        "items_per_user": settings.items_per_user,
    }

@app.post("/things", status_code=201, dependencies=[Depends(get_settings)])
async def update(email):
    print(get_settings())
    returned_thing = put_decision(email, get_settings())
    return {"thing": returned_thing}

def put_decision(email, settings):
    s = email
    s += " " + str(settings.items_per_user)
    return s

Here is my test_ping.py file
from starlette.testclient import TestClient

from project.main import app, get_settings
from project.config import Settings

def get_settings_override():
    print("overriding!")

    return Settings(
        app_name="My cool API"<EMAIL_ADDRESS>items_per_user=30
    )

app.dependency_overrides[get_settings] = get_settings_override
client = TestClient(app)

def test_info():
    response = client.get("info")
    assert response.status_code == 200
    assert response.json() == {
        "admin_email"<EMAIL_ADDRESS>        "app_name": "My cool API",
        "items_per_user": 30,
    }

def test_update():
    response = client.post("things", params={"email": "mything"})
    assert response.status_code == 201
    assert response.json() == {"thing": "mything 30"}

Here is my config.py file where the Settings class is first defined:
from pydantic import BaseSettings

class Settings(BaseSettings):
    app_name: str = "My cool API"
    admin_email: str =<EMAIL_ADDRESS>    items_per_user: int = 50

What am I missing here? I've tried overriding the function directly by doing the below but doesn't seem like it makes a difference.
app.get_settings = get_settings_override

I've looked at the solutions provided here and here but I am still observing the same behavior (i.e. my Settings stay the default for the POST call) but
Operating System
macOS
Operating System Details
No response
FastAPI Version
0.70.0
Python Version
Python 3.9.8
Additional Context
No response

@nessadc I don't think that you could override a dependency in the path operation decorator. You could simply patch the get_settings object directly.
from unittest.mock import patch

from project import main

@patch.object(main, "get_settings", get_settings_override)
def test_update():
    response = client.post("things", params={"email": "mything"})
    assert response.status_code == 201
    assert response.json() == {"thing": "mything 30"}

I hope that it passes.

@harunyasar I realized this as well after reading through some other issues related to Depends. Thank you for looking into this! This works for me now.
import pytest
from starlette.testclient import TestClient

from . import main
from project.config import Settings

def get_settings_override():
    return Settings(
        app_name="My cool API"<EMAIL_ADDRESS>items_per_user=30
    )

@pytest.fixture(scope="module")
def test_app():
    main.app.dependency_overrides[main.get_settings] = get_settings_override
    with TestClient(main.app) as test_client:
        yield test_client

def test_info(test_app):
    response = test_app.get("info")
    assert response.status_code == 200
    assert response.json() == {
        "admin_email"<EMAIL_ADDRESS>        "app_name": "My cool API",
        "items_per_user": 30,
    }

def test_update(test_app, monkeypatch):
    monkeypatch.setattr(main, "get_settings", get_settings_override)
    response = test_app.post("things", params={"email": "mything"})
    assert response.status_code == 201
    assert response.json() == {"thing": "mything 30"}


Not a issue, but a question?

Hi, I'm wondering if I can make a theme that's a combination of Comfy and Blackhole I know you don't own Blackhole but I'm wondering if I can use comfy in it?
I've already been working on it if you wanna see it I can show you.
Thanks -Minoa

I've already been working on it if you wanna see it I can show you.

Surely, my themes are usable in every way you want

On Sun, May 22, 2022 at 2:27 PM NYRIA @.***> wrote:

Closed #64 https://github.com/Comfy-Themes/Discord/issues/64 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/Comfy-Themes/Discord/issues/64#event-6656548882, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANZKIZPQXWHVC2AH5YXKIVTVLKDCBANCNFSM5WNG4KYQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok, thanks!


feat: Initial version of an extension to list contract method names

Creating extension for #70

@Buckram123

I recommend using interactive-clap to build the extensions with interactivity (see #93)
We should not merge extensions into this repo, instead:
2.1. setup a separate repo
2.2. configure CI (copy .github/workflows)
2.3. add the reference and a short description to near-cli-rs README

Building it here, working on:

[ ] README
[ ] Configure CI

@Buckram123 Ouch, I somehow missed your last message. Since that time devtools team developed NEAR ABI and cargo near extension.
I feel cargo near should remain dedicated to NEAR development on Rust, so we can start thinking about near-cli-dev which would be a generic extension for developers and yet agnostic to the language. It will include this feature with ABI support (using it to not only list the functions but also their signatures), and more (the commands layout still needs to be properly designed).

This is now implemented as near contract inspect command in #293


Overhaul device IP numbering system using mutex

Allocating IP addresses for device creation is not a trivial endeavor.
Before, we were using a window function and full-table lock in order
to select a candidate device IP to use when creating a new device. This
behavior was designed to mimic DHCP.
Consider the following example.
Say you currently have a list of devices in the database with the following IPs:
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
Assuming WIREGUARD_IPV4_NETWORK is set to <IP_ADDRESS>/24, the IP address
for the next device generated should be <IP_ADDRESS>. Before, this IP
would have been found with a large SELECT query that tried to find the
first non-sequential IP address in the devices table. This required
wrapping the SELECT and following INSERT in a single transaction to
ensure the IP address "reserved" would be insertable.
As you may imagine, this resulted in deadlocks, and prevented us from
running much of the device tests with async: true enabled.
@conectado came up with a simple but elegant solution to this problem
using a Mutex to guard an IP allocation cache. It works as follows:

Maintain an allocation cache: a list of all of the available IP
addresses represented as a list of {gap_start, gap_end} tuples.
Using the example data above, this would be:[
  {<IP_ADDRESS>, <IP_ADDRESS>},
  {<IP_ADDRESS>, <IP_ADDRESS>},
  {<IP_ADDRESS>, <IP_ADDRESS>}
]

When creating a new device, lock the mutex, then select the first
available IP address from the allocation cache. Increment the IP
address and save this new state as the new allocation cache.
If allocation fails (i.e. the cache is empty), rebuild the cache from
the DB. This has the nice effect that a stale cache just skips a few
IPs and causes a premature cache rebuild, but doesn't otherwise halt
creation like a SEQUENCE field would.
If the rebuilt cache is also empty, the IP address pool actually
has been exhausted, so return nil for the IP. The Device schema
interprets this as an error and adds an appropriate error to the changeset.

cc @wiresock for visibility

Pull Request Test Coverage Report for Build 9f74fe4b6cf5c4ab0cc5f9a97f710cc000795064-PR-1200

115 of 138 (83.33%)  changed or added relevant lines in 21 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 67.527%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

apps/fz_http/lib/fz_http/application.ex
0
1
0.0%

apps/fz_http/lib/fz_http/conf/cache.ex
0
1
0.0%

apps/fz_http/lib/fz_http/config.ex
22
23
95.65%

apps/fz_http/lib/fz_http/devices/stats_updater.ex
0
1
0.0%

apps/fz_http/lib/fz_http/oidc/start_proxy.ex
0
1
0.0%

apps/fz_common/lib/fz_integer.ex
18
23
78.26%

apps/fz_http/lib/fz_http/saml/start_proxy.ex
0
5
0.0%

apps/fz_http/lib/fz_http/ip_allocator.ex
36
44
81.82%

Totals

Change from base Build a8174e60b22a2e3fd29cfd165dec90e743eb85f6-PR-1155:
0.3%

Covered Lines:
1308

Relevant Lines:
1937

💛  - Coveralls

TODO:

write more tests for a changeset (especially when IP range is exhausted)

@jamilbk we have a ton of conflicts 😢. I also spotted two things:

https://github.com/firezone/firezone/blob/refactor/overhaul-device-ip-numbering/apps/fz_http/test/support/fixtures/devices_fixtures.ex#L24 hides some errors and makes tests flaky. We should just rely on the number generator in the changeset from now on. I will remove it.
I had multiple deadlocks during allow rule creation, I'll take care of it in a bit.

Eek sorry about all the conflicts! I’m getting deadlock on rules too.

@jamilbk this should be ready to merge into your branch. There is a rollback test failing but since you removed rollbacks in master it will go away once you rebase the bigger PR with REST API.


chore: fix typos

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

@luizstacio Thanks for your review. I had to update changeset to pass the ci "Validate PR Changeset" just now.


Add docker image

Closes #
Changes proposed in this pull request:

...

This looks fine to me (as someone who doesn't understand docker). Are you OK with these 7 commits being merge-squashed?


Digraphs

Add digraph support
Add user macro support to test runner for command line args specified via //aro-args

When using the -E flag with gcc and clang, digraphs are not converted into the corresponding token.  I don't think we can support this unless we add new tokens for each digraph (.l_brace_digraph etc). Would you want me to do that?

When using the -E flag with gcc and clang, digraphs are not converted into the corresponding token. I don't think we can support this unless we add new tokens for each digraph (.l_brace_digraph etc). Would you want me to do that?

This should be doable without adding any new tags by just adding a little more logic in Preprocessor.prettyPrintTokens to always find the slice in source for these tokens when digraphs are enabled.


Vercel adapter error in vercel app

Describe the bug

Start to get this error in vercel build immediately after this recent update that is not more than 1 hour now @sveltejs/adapter-vercel

Reproduction
https://github.com/arinzejustin/cryptflix/dashboard
Logs
TypeError: builder.routes is not iterable
--
18:35:57.663 | at Object.adapt (file:///vercel/path0/dashboard/node_modules/@sveltejs/adapter-vercel/index.js:155:32)
18:35:57.664 | at Object.adapt (file:///vercel/path0/dashboard/node_modules/@sveltejs/adapter-auto/index.js:103:19)
18:35:57.664 | at adapt (file:///vercel/path0/dashboard/node_modules/@sveltejs/adapter-auto/index.js:114:31)
18:35:57.664 | at async adapt (file:///vercel/path0/dashboard/node_modules/@sveltejs/kit/src/core/adapt/index.js:28:2)
18:35:57.664 | at async Object.handler (file:///vercel/path0/dashboard/node_modules/@sveltejs/kit/src/exports/vite/index.js:694:6)
18:35:57.664 | at async PluginDriver.hookParallel (file:///vercel/path0/dashboard/node_modules/rollup/dist/es/shared/rollup.js:23626:17)
18:35:57.664 | at async Object.close (file:///vercel/path0/dashboard/node_modules/rollup/dist/es/shared/rollup.js:24931:13)
18:35:57.664 | at async Promise.all (index 0)
18:35:57.664 | at async build (file:///vercel/path0/dashboard/node_modules/vite/dist/node/chunks/dep-5e7f419b.js:44352:13)
18:35:57.664 | at async CAC.<anonymous> (file:///vercel/path0/dashboard/node_modules/vite/dist/node/cli.js:808:9)
18:35:57.693 | Error: Command "npm run build" exited with 1

System Info
Vercel app

Severity
blocking an upgrade
Additional Information
No response

I can confirm I am also getting the same error on Vercel and locally via yarn build as well. I guessing this is due to the fact that adapter-auto does not enforce the same semver on the adapter-vercel package. (So my adapter-auto is at 1.0.0, while it tries to use adapter-vercel of 2.0.0).
I will try to post a minimal repro tomorrow.

see https://github.com/sveltejs/kit/issues/8907 ?

For anybody coming to this thread, you need to update to the following.
    "@sveltejs/adapter-auto": "^2.0.0",
    "@sveltejs/kit": "^1.5.0",

closed via #8915


[Bug] Calculation of IV 15/15/15

Something is wrong, I have a Taurus with IV 15/15/15  and average of 0.78. Picture attached.

my mistake


Jamroot?

The repository contains a file Jamroot which seems to be unused. Can this be removed?
/cc @artemp @springmeyer

yes

@springmeyer - pls, not ! :) . I'm currently using and planning to use bjam, it doesn't hurt anything does it ?


merge checkinday dimension fix

Docs Build status updates of commit 9ee0b61:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Advertising/hotel-service/reporting.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Automate the LCE AAR release

We release the LCE AAR on Bintray. Currently there is no automatic release mechanism in place in CI for LCE AAR.

We updated the docs to use the AAR prebuilt published with the release, so this issue can be closed now.


Page reload UI jitter

This is what I see now when refreshing the page when using the compact/inline mode.
Would it be possible to wait until everything is loaded/computed before rendering the items?
https://user-images.githubusercontent.com/996134/219873173-304f2836-ab76-493a-b219-30164e5b7038.mp4

Seems there is jitter too when reacting to something as well.
https://user-images.githubusercontent.com/996134/221369237-86db2cb8-8391-49c0-ac84-f295f6d59fd4.mp4

It's my plan to refactor it to use react - that should fix this issue. I just need to find the time to do it.


BufNMF has no padding argument.

This was noticed by @tremblap and myself this morning. We were wondering if it is supposed to or not? And if so, if there's a plan for adding it.

I've only just noticed this. It's by design, and I'm afraid PA must have forgotten the very long conversation about what did and didn't get a padding parameter when they got added. The only things with padding are the standard wrapped descriptors. Other FFT objects are all locked at a standard win / 2. I can see how a case for NMF being as much a descriptor as an audio object can be made, but the effort to reward ratio isn't good in this instance.


AL2023 AMI: "invalid capacity 0 on image filesystem" kubelet warning

I'm not sure if this is a bug so I'm filing this as a general question.
During node startup I can see the event "invalid capacity 0 on image filesystem" as a warning from kubelet.
Using journalctl -u kubelet I can see additional information for this warning:
kubelet.go:1440] "Image garbage collection failed once. Stats initialization may not have completed yet" err="invalid capacity 0 on image filesystem"
Afterwards, the node starts normally, pods are assigned to the node and I cannot observe any abnormal behaviour.
I'm wondering if anyone else encountered this and if I can safely ignore this warning? (because Stats initialization may not have completed yet as the message already suggests 😄)
Environment:

AWS Region: eu-central-1
Instance Type(s): r5a.xlarge
EKS Platform version (use aws eks describe-cluster --name <name> --query cluster.platformVersion): eks.17
Kubernetes version (use aws eks describe-cluster --name <name> --query cluster.version): 1.28
AMI Version: AL2023 1.28.11-20240828 and 1.28.11-20240817
Kernel (e.g. uname -a): Linux ip-10-156-75-203.eu-central-1.compute.internal 6.1.102-111.182.amzn2023.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Aug 13 22:23:09 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Release information (run cat /etc/eks/release on a node):

BASE_AMI_ID="ami-0ba8fabdb90841bee"
BUILD_TIME="Wed Aug 28 01:53:55 UTC 2024"
BUILD_KERNEL="6.1.102-111.182.amzn2023.x86_64"
ARCH="x86_64"

You can ignore it.


[3.x] Tweak editor icons for navigation nodes and SkeletonIK

Backport of #62201

A nitpick, but I think the colors are off and need to be less saturated for this version of Godot. You can clearly see the pink and the blue are different from their base node counterparts.

TIL the tint colors are different between 4.0 and 3.x :) Adjusted the colors to be the same as their base icons:

For reference, this change was initially made in https://github.com/godotengine/godot/pull/48644.

Thanks!


Add android instructions on including the apt plugin

Add android instructions on including the apt plugin

:thumbsup: sure useful, thanks


Scenario.read_excel() fails on sheets containing 'phantom' cells

The error occurs when executing read_excel().
When reading an excel file, some rows of data can be added which actually do not contain any data. These extra rows will contain "NaN"s, therefore resulting in two errors.
The first error which occurs, if the argument add_unit=True is passed:
TypeError: No matching overloads found for at.ac.iiasa.ixmp.Platform.addUnitToDB(float,str), options are: 	public int at.ac.iiasa.ixmp.Platform.addUnitToDB(java.lang.String,java.lang.String) throws at.ac.iiasa.ixmp.exceptions.IxException
The error message results from the fact that a unit "nan" is trying to be added.
The second error occurs when reading data and determining the column type. Should "phantom" data be included in the dataframe, then columns which should be integers are read as floats. The following error is given:
RuntimeError: unhandled Java exception: The key '2001.0' must not contain a '.'!
The current workaround requires cleaning of the xlsx which is being read-in. In the various sheets, columns can be filtered for "Blanks" in excel. The resulting selection will show the respective rows, indicated by having blue row numbers. Deleting these and saving the xlsx file should resolve the issue.
In order to see which parameter sheet contains the phantom data, add print(name) in line 274 of the file ixmp/backend/io.py. The parameter sheet currently being processed will be printed on screen. The last parameter printed before the error message will guide the user to the sheet containing the phantom-data.

pandas has problems with:

rows which can be cleaned used df.dropna(how="all")

columns that have “left-over” empty columns, naming them Unnamed: {v} where v is a counter…
This is how this is caught and treated in pyam: https://github.com/IAMconsortium/pyam/blob/c62ee8c368a9ee48447fce8a838410112298a3b2/pyam/utils.py#L178


Connection Error docker-compose up ML backend with localhost

I launch label studio server with label-studio start.
Then I lauch my ML backend server with docker-compose up.
I get this error from ner.py (configuration for training the model) :
requests.exceptions.ConnectionError: HTTPConnectionPool(host='<IP_ADDRESS>', port=8080): Max retries exceeded with url: /api/projects/3/export?exportType=JSON (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fb95a9f1050>: Failed to establish a new connection: [Errno 111] Connection refused'))
I changed ner.py like this :
ner.py, l. 478 and following :
def fit(
        self, event, data, model_type='bert', pretrained_model='bert-base-uncased',
        batch_size=32, learning_rate=5e-5, adam_epsilon=1e-8, num_train_epochs=100, weight_decay=0.0, logging_steps=1,
        warmup_steps=0, save_steps=50, dump_dataset=True, cache_dir='~/.heartex/cache', train_logs=None,
        **kwargs
    ):
        workdir = os.environ['WORK_DIR'] = '<my-work-dir>'
        # URL en dur
        download_url = "http://localhost:8080/api/projects/3/export?exportType=JSON"
        token = "<my_token>"

        # Requête API
        response = requests.get(download_url, headers={'Authorization': f'Token {token}'})
        if response.status_code != 200:
            raise Exception(f"Can't load task data using {download_url}, "
                f"response status_code = {response.status_code}")

        if workdir is None:
            raise ValueError('Specify "WORK_DIR" environmental variable to store model checkpoints.')
        train_logs = train_logs or os.path.join(workdir, 'train_logs')
        os.makedirs(train_logs, exist_ok=True)
        logger.debug('Prepare models')
        cache_dir = os.path.expanduser(cache_dir)
        os.makedirs(cache_dir, exist_ok=True)

        model_type = model_type.lower()
        # assert model_type in MODEL_CLASSES.keys(), f'Input model type {model_type} not in {MODEL_CLASSES.keys()}'
        # assert pretrained_model in ALL_MODELS, f'Pretrained model {pretrained_model} not in {ALL_MODELS}'

        tokenizer = AutoTokenizer.from_pretrained(pretrained_model, cache_dir=cache_dir)

        logger.debug('Read data')
        # read input data stream
        completions = response.json()
        texts, list_of_spans = [], []

It has previously worked with label-studio start ner_adapted --init --ml-backend http://localhost:9090.

Solved it byr replacing localhost by host.docker.internal :
download_url = "http://host.docker.internal:8080/api/projects/3/export?exportType=JSON"

Closed as a non-active issue, and it seems like it has been resolved.


[FR] Add SageMaker notebook support

Like Databricks (#1339), supporting SageMaker's notebook environment needs attention.
Currently the DatabseService fails to start.

I installed like this:
%pip install albumentations --upgrade
%pip install opencv-contrib-python --upgrade
%pip install opencv-python --upgrade
%pip install opencv-python-headless --upgrade
%pip install datascience --upgrade
%pip install flask --upgrade
%pip install fiftyone
!sudo yum install -y openssl-devel openssl11-libs

And then importing works, but I can't get it to display.

use a sagemaker notebook with base python version 2.0 rather than datascience


Unable to target CoreCLR from Visual Studio Code

From @TheBlueSky on February 26, 2016 13:3
Hellp everyone,
I created a totally empty project and specified only CoreCLR as targetted framework; i.e., in project.json I have:
"frameworks": {
    "dnxcore50": {}
}

On my PC, the dnvm confirugration is the following:
Active Version           Runtime Architecture OperatingSystem Alias
------ -------           ------- ------------ --------------- -----
       1.0.0-rc1-update1 clr     x64          win
       1.0.0-rc1-update1 clr     x86          win
  *    1.0.0-rc1-update1 coreclr x64          win             default
       1.0.0-rc1-update1 coreclr x86          win

Still, when I run the application I receive:
System.InvalidOperationException: The current runtime target framework is not compatible with 'SomeProject'.
Current runtime target framework: 'DNX,Version=v4.5.1 (dnx451)'
 Version:      1.0.0-rc1-16231
 Type:         Clr
 Architecture: x86
 OS Name:      Windows
 OS Version:   10.0
 Runtime Id:   win10-x86

Please make sure the runtime matches a framework specified in project.json

Visual Studio Code is still "thinking" that it should run x86 CLR DNX and not the x64 CoreCLR one.
I'm not sure if this is a Visual Studio Code issue, or ASP.Net Core tooling issue; and appreciate any hint and help.
Copied from original issue: Microsoft/vscode#3489

From @TranscendOfSypherus on March 4, 2016 1:56
I too am seeing this issue, if I launch a command window from the command pallet and invoke dnx web then kestrel launches fine against coreclr.

Hi @TheBlueSky and @TranscendOfSypherus, with DNX replaced with .NET Core, is this still an issue. It seems to be pretty stale. Let me know if you're still experiencing this problem.

@DustinCampbell, it isn't relevant anyway now, after moving to dotnet. I'm going to test this later, and if there is an issue, I believe we should open a new "Issue".

yes, that'd be best.


Use googleapis/release-please for deployments

Release Please has better support for mono repos, squash commits, and overall results in a cleaner commit history.
Refs: googleapis/release-please, google-github-actions/release-please-action

Use gradle/gradle-build-action


Remove deprecated RetryableStatusCodeException

Fixes #2003

Codecov Report

Merging #2427 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2427      +/-   ##
==========================================
- Coverage   68.44%   68.43%   -0.01%
==========================================
  Files         235      234       -1
  Lines        8220     8218       -2
  Branches     1020     1020
==========================================
- Hits         5626     5624       -2
  Misses       2210     2210
  Partials      384      384

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 ba24811...157038c. Read the comment docs.


Unable to edit

I just upgraded Joplin to 2.14.2 and found your mind mapper tool. Looks great, but once I have created a mindmap and saved it I cannot edit it again.

Cannot to edit mindmap with other plugin that JoplinEnhancement.


Healthz overhaul

Currently, the healthz endpoint on Dapr services do not represent the actual health of the service as they are mostly only spinning up a HTTP server and immediately returning a 200 OK. This results in services receiving traffic before they are ready to actually serve requests. This issue manifests in integration tests where, for example, no metrics are available on the metrics endpoint even though the service reports as healthy and therefore fails the test.
This PR overhauls the healthz package to allow registering health targets during the service New process chain. Each module marks their target as healthy and the healthz server reports the overall health of the service. Although not perfect, service healthz endpoints should now be more representative of the actual health of the program.

@JoshVanL please resolve conflicts

@yaron2 fixed

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

This will need a doc PR.


Publish 7.2-20210811230220+0000

Publish 7.2-20210811230220+0000

@bot-gradle test and merge

OK, I've already triggered a build for you.


[azservicebus] amqp-common's link.RetryableRPC() retries an entity does not exist

This can lead to a series of retries that will not work. It'd be nice to be able to pass in an error handling strategy per RPC call so we can provide better error handling when we know what the context of the call is and just fail early.
The underlying error is:
Code: 404
Description: "The messaging entity 'sb://.servicebus.windows.net/samples' could not be found. To know more visit https://aka.ms/sbResourceMgrExceptions.  TrackingId:888b355f-038e-42e1-ab5d-cf1d0bfa20d1_G53, SystemTracker:riparkdev2.servicebus.windows.net:samples, Timestamp:2021-11-04T17:42:29"

Another example - when attempting to complete a message it will retry on 410 (message lock lost) which should be considered terminal and non-retryable.

@mikekistler noted that our retry policies just plain don't match the azcore retry numbers (and need to). This can cause some pretty bad retry behavior.

I'm in the process of trying to upgrade from the old "azure-service-bus-go" package, and I think this is also a change in behavior.
In the old package, when I try to send a message to a nonexistent topic, I would get an error back (not a great one, but at least it said "404" somewhere in it). Now, it just hangs until the context expires (if ever).
Same deal for trying to receive messages from a subscription that doesn't exist.
SendMessage and ReceiveMessages should return usable error messages for fatal errors, not just hang.

@vangent, I'll be working on this, this is definitely unintentional and is just us misclassifying errors error types.

Which module + version contains this fix?

Hi @vangent,
You can install the latest release v0.3.6 and get this fix and several others that impacted reliability and recoverability.

Thanks!
I can't find any documentation about error handling in the new library. The old one had constants like servicebus.ErrorNotImplemented, servicebus.ErrorNotFound, etc., but all I can find in the new one is
https://github.com/Azure/azure-sdk-for-go/blob/sdk/messaging/azservicebus/v0.1.0/sdk/messaging/azservicebus/errors.go
Given that I made a call, and I got an error back, is there any structured way to determine what kind of error it is (other than parsing the message string, which fragile)?

BTW, I confirmed that I now do get an error back when sending to a nonexistent topic, although it takes > 60s to return. Maybe it's retrying internally for some time? Nonexistent topic seems like it should be non-retryable.
unhandled error link 4d9ac674-xxx: status code 404 and description: The messaging entity 'sb:/
/xxx.servicebus.windows.net/nonexistent-topic' could not be found. To know more visit https://aka.ms/sbResourceMgrException

Thanks! Any response to my question in https://github.com/Azure/azure-sdk-for-go/issues/16088#issuecomment-1062454958 ?

Thanks! I can't find any documentation about error handling in the new library. The old one had constants like servicebus.ErrorNotImplemented, servicebus.ErrorNotFound, etc., but all I can find in the new one is https://github.com/Azure/azure-sdk-for-go/blob/sdk/messaging/azservicebus/v0.1.0/sdk/messaging/azservicebus/errors.go
Given that I made a call, and I got an error back, is there any structured way to determine what kind of error it is (other than parsing the message string, which fragile)?

We've tried to not redefine/recreate error types that exist, so for the most part the errors you'll see will be actual Go network related errors, or errors returned from go-amqp, which is our AMQP layer. It's not something we anticipate customers having to do, as most of the time an error returned from the library is a fatal one and there's no actual programmatic intervention possible.
We also allow you to configure the # and nature of the retries, so these can be adjusted if you find that the library is giving up too early or is taking too long between tries. You can configure this using the ClientOptions when you create your client. This would let you still lean on the library for categorization of errors while still being more resilient. This could hopefully eliminate any need to manually categorize errors.
If you're still interested in dissecting the errors you can see how we categorization today using errors.As() our implementation is here:
https://github.com/Azure/azure-sdk-for-go/blob/3349b7f7ed8c0af215b628b7734ebb2a7afdf876/sdk/messaging/azservicebus/internal/errors.go#L166
(looks like you've already looked at the older version of that file, it's seen some work since then)
It's totally possible to do the same in external code. We don't lock these errors down (behaviors in go-amqp could change) but you'll always see adjustments to azservicebus's error code to handle it.
All of this is a bit side to the original issue which is actually that the previous code doesn't use the error categorization code. I'm still fixing that one :)

OK, thanks. By the way, as I mentioned above I do get an error sending to a non-existent topic now (after 1m), but I still don't get anything but "context deadline exceeded" when trying to receive from a non-existent subscription (servicebus.Receiver.ReceiveMessages).

Yes, I'm definitely looking at that. I've got the test brewing and trying to see what I missed.

as most of the time an error returned from the library is a fatal one and there's no actual programmatic intervention possible.

@richardpark-msft we should make this a strong guarantee (i.e. not "most" but "always") and document this behavior.

@richardpark-msft  I still don't see this fixed. I'm using v0.3.6.

Sending to a nonexistent topic fails, but it takes a long time still.
Receiving (ReceiveMessages) from a nonexistent topic doesn't fail, it just waits for the context to timeout.

Can we keep the issue open until there's a confirmed fix in a tagged version?

Reopened. I even added a test for this so I must be missing some circumstance here. I'll look and see on Monday.

Oh, I see what you mean, yes, it'll be out in 0.3.7. I'll update this when it goes out.

@richardpark-msft I'm curious if this issue also explains some behavior we're seeing.
We've been seeing that a receiver of a topic that has a long period of inactivity will stop receiving new messages. It's extremely hard to reproduce on demand, but what we've seen is that a topic that receives no messages for a few days (2+) will not pickup new messages when they are added and the call will hang forever.
This comes up a lot with topics used for test environments where we may have a long period of inactivity.
We've worked around the issue by checking for messages in a loop with a 10 minute context timeout, but perhaps this a workaround we can back out once 0.3.7 is available?

hi @tkent, do you mind filing a separate issue for this? What you're mentioning is different than the original issue filed, and it's simpler to track yours separately.

@vangent , 0.4.0 has been released with this fix. Sorry about the earlyclose on that.

Works, thanks!

@richardpark-msft, we're going to let v1.0.1 run for a few weeks without the work around we've had in place. If it shows up again, I'll file a separate issue. I'm hesitant to file an issue otherwise because we'll just get asked to try again with another version.

@richardpark-msft - I went through the exercise of running a small golang app usingv1.0.1 against a dedicated test service bus queue for about 13 days. When I put messages into the bus this evening, just as before, the app failed to receive new messages. I had to restart the app and then the messages showed up as expected.
I'll file an issue separately for this, but I'm going to put my workaround back in and call it day after that. I have to move onto other things.


How to use build in Unity mask with the shader (Rect Mask etc).

I was playing around with the shader in Unity, and I am wondering how could I apply mask to it (I do understand that shader would probably need to be edited for that to work but I couldn't find out how to do it).
My test scenario (2d Scene) :
I have UI object 1080x1080, and inside another object thath ave camera feed casted on the rawImage on it (1080x1920), I wish for that object to be masked, and only have 1080x1080 visible on the screen while still having the green screen efect working. Would it be possible to get your help with it?

I managed to work around this with one of the ugliest code you might have seen, but it satisify my needs (this is just a fragment of the code) :
`            float4 frag(v2f IN) : SV_Target
{
             if (_UseClipRect && UnityGet2DClipping(IN.worldPosition.xy, _ClipRect) == 0){
            half4 color = (tex2D(_MainTex, IN.uv) + _TextureSampleAdd);
            color.a *= UnityGet2DClipping(IN.worldPosition.xy, _ClipRect);

            #ifdef UNITY_UI_ALPHACLIP
                clip (color.a - 0.001);
            #endif

            return color;
                 }

[rest of frag() code below]
`
Basically I added if to detect if this pixel should be visible and make it invisible, if it should be visible I let your code do all other calculations.

Glad that this approach worked for you!


wrapping bug on repo link

noticed a lil wrapping bug on the repo link
not sure why the icon is getting pushed down, but its be great to stop doing that
e.g., https://www.pulumi.com/registry/packages/azure-quickstart-acr-geo-replication/

cc/ @sean1588


Feature Request: Please Update Library to include The New Arduino Portenta Vision Shield LoRa version

Please Update the LongFi Library to include The New Arduino PortentaH7 Vision Shield LoRa version.
https://store.arduino.cc/usa/portenta-vision-shield-lora
Clips onto the https://store.arduino.cc/usa/portenta-h7 dual core 160 pin $100 USD board.
Makes machine learning possible on an edge device, perfect for the Helium network. I would test code for you but presently 40 km away from a Gateway, and new Gateways are not shipping very fast.

https://store.arduino.cc/usa/portenta-vision-shield-lora


Buffer Overflow?

I have been experiencing random crashes some of which seem to involve random memory corruption.  I have since found a probable cause, but did run across this while I was searching for issues.
I ran address sanitizer on my code and it spit out the following. There is a warning of potential false positives...
==47182==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x70000f1bb000; bottom 0x00010a1da000; size: 0x6fff04fe1000<PHONE_NUMBER>02720)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
==47182==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x00010a1db9e1 at pc 0x000100136a7a bp 0x70000f1b9bb0 sp 0x70000f1b9370
READ of size 5664 at 0x00010a1db9e1 thread T2
#0 0x100136a79 in wrap_memmove+0x169 (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x1da79)
#1 0x109ce5d60 in SharedCoroutine.saveStack()+0x830 (goSwiftlyTests:x86_64+0xdad60)
#2 0x109cedc9d in SharedCoroutineQueue.start(dispatcher:scheduler:task:)+0x47d (goSwiftlyTests:x86_64+0xe2c9d)
#3 0x109ceac4a in closure #1 in SharedCoroutineDispatcher.execute(on:task:)+0x22a (goSwiftlyTests:x86_64+0xdfc4a)
#4 0x109cbd932 in thunk for @escaping @callee_guaranteed () -> ()+0x92 (goSwiftlyTests:x86_64+0xb2932)
#5 0x1001613ba in __wrap_dispatch_async_block_invoke+0xca (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x483ba)
#6 0x7fff72cb56c3 in _dispatch_call_block_and_release+0xb (libdispatch.dylib:x86_64+0x16c3)
#7 0x7fff72cb6657 in _dispatch_client_callout+0x7 (libdispatch.dylib:x86_64+0x2657)
#8 0x7fff72cbbc43 in _dispatch_lane_serial_drain+0x254 (libdispatch.dylib:x86_64+0x7c43)
#9 0x7fff72cbc5d5 in _dispatch_lane_invoke+0x16a (libdispatch.dylib:x86_64+0x85d5)
#10 0x7fff72cc5c08 in _dispatch_workloop_worker_thread+0x253 (libdispatch.dylib:x86_64+0x11c08)
#11 0x7fff72f10a3c in _pthread_wqthread+0x121 (libsystem_pthread.dylib:x86_64+0x2a3c)
#12 0x7fff72f0fb76 in start_wqthread+0xe (libsystem_pthread.dylib:x86_64+0x1b76)
0x00010a1db9e1 is located 190945 bytes inside of 200704-byte region [0x00010a1ad000,0x00010a1de000)
allocated by thread T2 here:
#0 0x100162870 in wrap_posix_memalign+0xb0 (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x49870)
#1 0x7fff7262bcd1 in swift_slowAlloc+0x41 (libswiftCore.dylib:x86_64+0x2f2cd1)
#2 0x109cd817b in CoroutineContext.init(stackSize:guardPage:)+0x4fb (goSwiftlyTests:x86_64+0xcd17b)
#3 0x109cd7c68 in CoroutineContext.__allocating_init(stackSize:guardPage:)+0x38 (goSwiftlyTests:x86_64+0xccc68)
#4 0x109ced426 in SharedCoroutineQueue.init(stackSize:)+0x5b6 (goSwiftlyTests:x86_64+0xe2426)
#5 0x109cece58 in SharedCoroutineQueue.__allocating_init(stackSize:)+0x28 (goSwiftlyTests:x86_64+0xe1e58)
#6 0x109ceb158 in SharedCoroutineDispatcher.getFreeQueue()+0x438 (goSwiftlyTests:x86_64+0xe0158)
#7 0x109ceac2f in closure #1 in SharedCoroutineDispatcher.execute(on:task:)+0x20f (goSwiftlyTests:x86_64+0xdfc2f)
#8 0x109cbd932 in thunk for @escaping @callee_guaranteed () -> ()+0x92 (goSwiftlyTests:x86_64+0xb2932)
#9 0x1001613ba in __wrap_dispatch_async_block_invoke+0xca (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x483ba)
#10 0x7fff72cb56c3 in _dispatch_call_block_and_release+0xb (libdispatch.dylib:x86_64+0x16c3)
#11 0x7fff72cb6657 in _dispatch_client_callout+0x7 (libdispatch.dylib:x86_64+0x2657)
#12 0x7fff72cbbc43 in _dispatch_lane_serial_drain+0x254 (libdispatch.dylib:x86_64+0x7c43)
#13 0x7fff72cbc5d5 in _dispatch_lane_invoke+0x16a (libdispatch.dylib:x86_64+0x85d5)
#14 0x7fff72cc5c08 in _dispatch_workloop_worker_thread+0x253 (libdispatch.dylib:x86_64+0x11c08)
#15 0x7fff72f10a3c in _pthread_wqthread+0x121 (libsystem_pthread.dylib:x86_64+0x2a3c)
#16 0x7fff72f0fb76 in start_wqthread+0xe (libsystem_pthread.dylib:x86_64+0x1b76)
Thread T2 created by T1 here:

Thread T1 created by T0 here:

SUMMARY: AddressSanitizer: stack-buffer-overflow (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x1da79) in wrap_memmove+0x169
Shadow bytes around the buggy address:
0x10002143b6e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10002143b6f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10002143b700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10002143b710: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10002143b720: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x10002143b730: 00 00 00 00 00 00 00 00 f1 f1 f1 f1[01]f3 f3 f3
0x10002143b740: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10002143b750: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10002143b760: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10002143b770: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10002143b780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable:           00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone:       fa
Freed heap region:       fd
Stack left redzone:      f1
Stack mid redzone:       f2
Stack right redzone:     f3
Stack after return:      f5
Stack use after scope:   f8
Global redzone:          f9
Global init order:       f6
Poisoned by user:        f7
Container overflow:      fc
Array cookie:            ac
Intra object redzone:    bb
ASan internal:           fe
Left alloca redzone:     ca
Right alloca redzone:    cb
Shadow gap:              cc
2020-11-06 15:47:39.270045-0700 xctest[47182:2741407] ==47182==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x70000f1bb000; bottom 0x00010a1da000; size: 0x6fff04fe1000<PHONE_NUMBER>02720)
2020-11-06 15:47:39.270161-0700 xctest[47182:2741407] False positive error reports may follow
2020-11-06 15:47:39.270244-0700 xctest[47182:2741407] For details see https://github.com/google/sanitizers/issues/189
2020-11-06 15:47:39.270366-0700 xctest[47182:2741407] =================================================================
2020-11-06 15:47:39.270476-0700 xctest[47182:2741407] ==47182==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x00010a1db9e1 at pc 0x000100136a7a bp 0x70000f1b9bb0 sp 0x70000f1b9370
2020-11-06 15:47:39.270527-0700 xctest[47182:2741407] READ of size 5664 at 0x00010a1db9e1 thread T2
2020-11-06 15:47:39.270648-0700 xctest[47182:2741407]     #0 0x100136a79 in wrap_memmove+0x169 (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x1da79)
2020-11-06 15:47:39.270708-0700 xctest[47182:2741407]     #1 0x109ce5d60 in SharedCoroutine.saveStack()+0x830 (goSwiftlyTests:x86_64+0xdad60)
2020-11-06 15:47:39.270798-0700 xctest[47182:2741407]     #2 0x109cedc9d in SharedCoroutineQueue.start(dispatcher:scheduler:task:)+0x47d (goSwiftlyTests:x86_64+0xe2c9d)
2020-11-06 15:47:39.270892-0700 xctest[47182:2741407]     #3 0x109ceac4a in closure #1 in SharedCoroutineDispatcher.execute(on:task:)+0x22a (goSwiftlyTests:x86_64+0xdfc4a)
2020-11-06 15:47:39.270955-0700 xctest[47182:2741407]     #4 0x109cbd932 in thunk for @escaping @callee_guaranteed () -> ()+0x92 (goSwiftlyTests:x86_64+0xb2932)
2020-11-06 15:47:39.271008-0700 xctest[47182:2741407]     #5 0x1001613ba in __wrap_dispatch_async_block_invoke+0xca (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x483ba)
2020-11-06 15:47:39.271119-0700 xctest[47182:2741407]     #6 0x7fff72cb56c3 in _dispatch_call_block_and_release+0xb (libdispatch.dylib:x86_64+0x16c3)
2020-11-06 15:47:39.271189-0700 xctest[47182:2741407]     #7 0x7fff72cb6657 in _dispatch_client_callout+0x7 (libdispatch.dylib:x86_64+0x2657)
2020-11-06 15:47:39.271266-0700 xctest[47182:2741407]     #8 0x7fff72cbbc43 in _dispatch_lane_serial_drain+0x254 (libdispatch.dylib:x86_64+0x7c43)
2020-11-06 15:47:39.271346-0700 xctest[47182:2741407]     #9 0x7fff72cbc5d5 in _dispatch_lane_invoke+0x16a (libdispatch.dylib:x86_64+0x85d5)
2020-11-06 15:47:39.271396-0700 xctest[47182:2741407]     #10 0x7fff72cc5c08 in _dispatch_workloop_worker_thread+0x253 (libdispatch.dylib:x86_64+0x11c08)
2020-11-06 15:47:39.271445-0700 xctest[47182:2741407]     #11 0x7fff72f10a3c in _pthread_wqthread+0x121 (libsystem_pthread.dylib:x86_64+0x2a3c)
2020-11-06 15:47:39.271534-0700 xctest[47182:2741407]     #12 0x7fff72f0fb76 in start_wqthread+0xe (libsystem_pthread.dylib:x86_64+0x1b76)
2020-11-06 15:47:39.271578-0700 xctest[47182:2741407]
2020-11-06 15:47:39.271621-0700 xctest[47182:2741407] 0x00010a1db9e1 is located 190945 bytes inside of 200704-byte region [0x00010a1ad000,0x00010a1de000)
2020-11-06 15:47:39.271667-0700 xctest[47182:2741407] allocated by thread T2 here:
2020-11-06 15:47:39.271708-0700 xctest[47182:2741407]     #0 0x100162870 in wrap_posix_memalign+0xb0 (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x49870)
2020-11-06 15:47:39.271749-0700 xctest[47182:2741407]     #1 0x7fff7262bcd1 in swift_slowAlloc+0x41 (libswiftCore.dylib:x86_64+0x2f2cd1)
2020-11-06 15:47:39.271861-0700 xctest[47182:2741407]     #2 0x109cd817b in CoroutineContext.init(stackSize:guardPage:)+0x4fb (goSwiftlyTests:x86_64+0xcd17b)
2020-11-06 15:47:39.271926-0700 xctest[47182:2741407]     #3 0x109cd7c68 in CoroutineContext.__allocating_init(stackSize:guardPage:)+0x38 (goSwiftlyTests:x86_64+0xccc68)
2020-11-06 15:47:39.272024-0700 xctest[47182:2741407]     #4 0x109ced426 in SharedCoroutineQueue.init(stackSize:)+0x5b6 (goSwiftlyTests:x86_64+0xe2426)
2020-11-06 15:47:39.272134-0700 xctest[47182:2741407]     #5 0x109cece58 in SharedCoroutineQueue.__allocating_init(stackSize:)+0x28 (goSwiftlyTests:x86_64+0xe1e58)
2020-11-06 15:47:39.272253-0700 xctest[47182:2741407]     #6 0x109ceb158 in SharedCoroutineDispatcher.getFreeQueue()+0x438 (goSwiftlyTests:x86_64+0xe0158)
2020-11-06 15:47:39.272323-0700 xctest[47182:2741407]     #7 0x109ceac2f in closure #1 in SharedCoroutineDispatcher.execute(on:task:)+0x20f (goSwiftlyTests:x86_64+0xdfc2f)
2020-11-06 15:47:39.272388-0700 xctest[47182:2741407]     #8 0x109cbd932 in thunk for @escaping @callee_guaranteed () -> ()+0x92 (goSwiftlyTests:x86_64+0xb2932)
2020-11-06 15:47:39.272434-0700 xctest[47182:2741407]     #9 0x1001613ba in __wrap_dispatch_async_block_invoke+0xca (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x483ba)
2020-11-06 15:47:39.272518-0700 xctest[47182:2741407]     #10 0x7fff72cb56c3 in _dispatch_call_block_and_release+0xb (libdispatch.dylib:x86_64+0x16c3)
2020-11-06 15:47:39.272628-0700 xctest[47182:2741407]     #11 0x7fff72cb6657 in _dispatch_client_callout+0x7 (libdispatch.dylib:x86_64+0x2657)
2020-11-06 15:47:39.272735-0700 xctest[47182:2741407]     #12 0x7fff72cbbc43 in _dispatch_lane_serial_drain+0x254 (libdispatch.dylib:x86_64+0x7c43)
2020-11-06 15:47:39.272836-0700 xctest[47182:2741407]     #13 0x7fff72cbc5d5 in _dispatch_lane_invoke+0x16a (libdispatch.dylib:x86_64+0x85d5)
2020-11-06 15:47:39.272911-0700 xctest[47182:2741407]     #14 0x7fff72cc5c08 in _dispatch_workloop_worker_thread+0x253 (libdispatch.dylib:x86_64+0x11c08)
2020-11-06 15:47:39.273034-0700 xctest[47182:2741407]     #15 0x7fff72f10a3c in _pthread_wqthread+0x121 (libsystem_pthread.dylib:x86_64+0x2a3c)
2020-11-06 15:47:39.273105-0700 xctest[47182:2741407]     #16 0x7fff72f0fb76 in start_wqthread+0xe (libsystem_pthread.dylib:x86_64+0x1b76)
2020-11-06 15:47:39.273255-0700 xctest[47182:2741407]
2020-11-06 15:47:39.273320-0700 xctest[47182:2741407] Thread T2 created by T1 here:
2020-11-06 15:47:39.273371-0700 xctest[47182:2741407]
2020-11-06 15:47:39.273523-0700 xctest[47182:2741407]
2020-11-06 15:47:39.273596-0700 xctest[47182:2741407] Thread T1 created by T0 here:
2020-11-06 15:47:39.273647-0700 xctest[47182:2741407]
2020-11-06 15:47:39.273745-0700 xctest[47182:2741407]
2020-11-06 15:47:39.273816-0700 xctest[47182:2741407] SUMMARY: AddressSanitizer: stack-buffer-overflow (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x1da79) in wrap_memmove+0x169
2020-11-06 15:47:39.273872-0700 xctest[47182:2741407] Shadow bytes around the buggy address:
2020-11-06 15:47:39.273990-0700 xctest[47182:2741407]   0x10002143b6e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2020-11-06 15:47:39.274067-0700 xctest[47182:2741407]   0x10002143b6f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2020-11-06 15:47:39.274157-0700 xctest[47182:2741407]   0x10002143b700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2020-11-06 15:47:39.274265-0700 xctest[47182:2741407]   0x10002143b710: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2020-11-06 15:47:39.274326-0700 xctest[47182:2741407]   0x10002143b720: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2020-11-06 15:47:39.274419-0700 xctest[47182:2741407] =>0x10002143b730: 00 00 00 00 00 00 00 00 f1 f1 f1 f1[01]f3 f3 f3
2020-11-06 15:47:39.274529-0700 xctest[47182:2741407]   0x10002143b740: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2020-11-06 15:47:39.274609-0700 xctest[47182:2741407]   0x10002143b750: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2020-11-06 15:47:39.274754-0700 xctest[47182:2741407]   0x10002143b760: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2020-11-06 15:47:39.274823-0700 xctest[47182:2741407]   0x10002143b770: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2020-11-06 15:47:39.274904-0700 xctest[47182:2741407]   0x10002143b780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2020-11-06 15:47:39.274969-0700 xctest[47182:2741407] Shadow byte legend (one shadow byte represents 8 application bytes):
2020-11-06 15:47:39.275105-0700 xctest[47182:2741407]   Addressable:           00
2020-11-06 15:47:39.275183-0700 xctest[47182:2741407]   Partially addressable: 01 02 03 04 05 06 07
2020-11-06 15:47:39.275238-0700 xctest[47182:2741407]   Heap left redzone:       fa
2020-11-06 15:47:39.275349-0700 xctest[47182:2741407]   Freed heap region:       fd
2020-11-06 15:47:39.275440-0700 xctest[47182:2741407]   Stack left redzone:      f1
2020-11-06 15:47:39.275499-0700 xctest[47182:2741407]   Stack mid redzone:       f2
2020-11-06 15:47:39.275594-0700 xctest[47182:2741407]   Stack right redzone:     f3
2020-11-06 15:47:39.275647-0700 xctest[47182:2741407]   Stack after return:      f5
2020-11-06 15:47:39.275709-0700 xctest[47182:2741407]   Stack use after scope:   f8
2020-11-06 15:47:39.275749-0700 xctest[47182:2741407]   Global redzone:          f9
2020-11-06 15:47:39.275838-0700 xctest[47182:2741407]   Global init order:       f6
2020-11-06 15:47:39.275905-0700 xctest[47182:2741407]   Poisoned by user:        f7
2020-11-06 15:47:39.275996-0700 xctest[47182:2741407]   Container overflow:      fc
2020-11-06 15:47:39.276094-0700 xctest[47182:2741407]   Array cookie:            ac
2020-11-06 15:47:39.276177-0700 xctest[47182:2741407]   Intra object redzone:    bb
2020-11-06 15:47:39.276229-0700 xctest[47182:2741407]   ASan internal:           fe
2020-11-06 15:47:39.276335-0700 xctest[47182:2741407]   Left alloca redzone:     ca
2020-11-06 15:47:39.276429-0700 xctest[47182:2741407]   Right alloca redzone:    cb
2020-11-06 15:47:39.276583-0700 xctest[47182:2741407]   Shadow gap:              cc
==47182==ABORTING
Warning: hit breakpoint while running function, skipping commands and conditions to prevent recursion.
AddressSanitizer report breakpoint hit. Use 'thread info -s' to get extended information about the report.
(lldb) thread info -s
thread #3: tid = 0x29d49f, 0x000000010016ab20 libclang_rt.asan_osx_dynamic.dylib`__asan::AsanDie(), queue = 'GoSwiftly[1]', stop reason = Stack buffer overflow
{
"access_size": 5664,
"access_type": 0,
"address":<PHONE_NUMBER>,
"description": "stack-buffer-overflow",
"instrumentation_class": "AddressSanitizer",
"pc":<PHONE_NUMBER>,
"stop_type": "fatal_error"
}
(lldb)

@ckornher Hi, AddressSanitizer can show stack buffer overflow warning because it can't detect the change of stack location (google/sanitizers#189).
If possible, could you please provide real crash reports?
Also please pay attention to this issue which has already been discussed  - https://github.com/belozierov/SwiftCoroutine/issues/22

@belozierov Thanks for the reply. It looks like it was probably a race condition in my code. I am going to close the one.


IOS : RangeError: Maximum call stack size exceeded.

version:
"@walletconnect/web3wallet": "^1.5.1" @walletconnect/sign-client": "^2.6.2"
source code:
core.pairing.pair({ uri: wcuri })
error message:
ERROR  {"context": "core"} {"context": "core/relayer"} [RangeError: Maximum call stack size exceeded.]

It seems that if the [walletconnect/core] package is v2.7.1, this error will be reported.