Enable changing the autoprune block space size in intro dialog

Moved from https://github.com/bitcoin/bitcoin/pull/18728

Concept ACK

Testing ACK 7e37329 on Windows 10.0.18363 Build 18363. Articulating how exactly the pruned storage works is a great UX move. Many users seem to think pruning only stores data relevant to them, not that its only storing a recent history of blocks. Can be quite a shock importing an old wallet that you believe has coins only to get a zero balance displayed.

Just some minor nits that could be fixed along with this PR:
"The wallet will also be stored in this directory" should be changed to "Wallets will also be stored in this directory" in the top dialogue. Users can / may have multiple wallets.
Blockchain size is around ~350GB now, may want to update the 320GB text in the second last paragraph.

Concept ACK

@Bosch-0 Does rescanning a wallet with a pruned node that misses relevant blocks result in an incorrect balance? That sounds like a bug - it should just abort with missing blocks or so.

@Bosch-0

Just some minor nits that could be fixed along with this PR:
"The wallet will also be stored in this directory" should be changed to "Wallets will also be stored in this directory" in the top dialogue. Users can / may have multiple wallets.

Usually, we are trying to keep PRs focused :)
A small pull with a label correction could be easy to review.

Blockchain size is around ~350GB now, may want to update the 320GB text in the second last paragraph.

This number update is a part of the release process, e.g., https://github.com/bitcoin/bitcoin/pull/20263.

Addressed @hebasto's comments.
Ping @promag @ryanofsky @Bosch-0 for re-ACKing

@Bosch-0 Does rescanning a wallet with a pruned node that misses relevant blocks result in an incorrect balance? That sounds like a bug - it should just abort with missing blocks or so.

I haven't actually tested this but I don't think it does - will test this today. The only time an incorrect balance may be shown is when importing a wallet post-prune that has tx history older than the block history stored as far as I'm concerned.

ACK ea7926527ce36c05cacb99602b2b59579ff646e8, looks good.

ACK ea79265, looks good.

Which commit did you mean?

@luke-jr

Addressed @hebasto's comments.

Sorry, but I don't think just that marking a comment as resolved means that it is addressed. If the current state of code is preferred  that could be stated explicitly, right?

Which commit did you mean?

I just re-tested the changes made since my first ACK, I did not review the code

Which commit did you mean?

I just re-tested the changes made since my first ACK, I did not review the code

I mean that ACK should be followed by the top commit of the pr branch, i.e. 7d40a4805229618a364dc53a84cd5af2ac273b7d for now, not the master branch (that ea7926527ce36c05cacb99602b2b59579ff646e8 is).

Is an update supposed to be pushed? My review was requested but there haven't been any changes since my last review https://github.com/bitcoin-core/gui/pull/125#pullrequestreview-528515367

QOverload doesn't work in Qt 5.5 ... reverted that change

master is bumped to Qt 5.9, so went back to QOverload...

@lucash-dev feeling dejavu - I see Intro::getPruneMiB() added here and int #149 :)

@luke-jr
Could you add release notes into https://github.com/bitcoin-core/bitcoin-devwiki/wiki/22.0-Release-Notes-draft#gui-changes?


What is the minimum Linux kernel version required for K3S?

What is the minimum Linux kernel version required for K3S? The kernel version 3.10 that we run on embedded devices does not support some of the necessary components, such as CONFIG_IP_NF_NAT, CONFIG_CGROUP_PIDS

I am not finding a specific note on the minimum kernel required for k3s or k8s.
However, from the container runtime side I do see a suggestion in containerd to use a 4.x kernel https://github.com/containerd/containerd/blob/main/README.md#runtime-requirements


creating source feedback

I am going through the process of adding a source and have a couple of suggestions that may help the user.
When I first went to add a video, the program crashed.

The cause was that I was missing opencv. It would be nice if you could prevent an ignorant user like myself from crashing the program by adding a try except clause such as:
try:
    import cv2
except:
    # show a dialog explaining that the user needs to install opencv using pip install pybehave[video] or link to the documentation

The docs do mention how to install the extra dependencies here. I suggest reiterating this information of how to add the dependency here where at the moment it only describes that opencv-python is required, not how to add it.
Another suggestion is to add labels/descriptions of the attributes or a link to documentation directly in this dialog (and other SourceParametersDialogs).

A link to included sources docs in this dialog may be useful as well:

This is a great suggestion and something I've been interested in adding for a little while now. Your suggestion to catch it at the import point made this really straightforward and clean to implement. Now, if you try to use a feature that requires an extra, a dialog like the below will pop up:

I've also made it so the '?' buttons in the two dialogs you sent link out to the corresponding documentation pages. I'll also work on adding the same feature for Widgets and EventLoggers.


Add authentication framework

Add the ability to place filters before the HTTP service, configurable
at the request level
Add the concept of an Authorizer, which is just a filter.
Add some initial Authorizers - Bearer (for pre-shared Bearer tokens)
and MAC (for pre-shared MAC tokens)

A future PR should contain a full OAuth2 flow implemented in an
Authorizer.

Current coverage is 54.48% (diff: 20.23%)

Merging #44 into master will decrease coverage by 8.87%

@@             master        #44   diff @@
==========================================
  Files             9         10     +1
  Lines           262        312    +50
  Methods         259        308    +49
  Messages          0          0
  Branches          3          4     +1
==========================================
+ Hits            166        170     +4
- Misses           96        142    +46
  Partials          0          0

Powered by Codecov. Last update bdecef0...e747ec5

@jeremyrsmith is it possible to write a test for Bearer and MAC authorizers?


Send Videos

I am a Gssoc24 Contributor. Can You Describe this issue? I think I can do it.

Registered users can send and receive video.

Please assign this issue to me.

Do I have to use the fixissue branch only? Because I am not able to create a new branch.

no, it's not necessary

Sure, thanks for assigning the issue to me,
However, I am not able to create a new branch or push my local branch in the repo. Can you please assign the required permissions to me?

here, from my side everything is good.

@shivam-sharma-2000 now everything is good, you can start contributing on this project

I agree to follow this project's Code of Conduct
I'm a GSSOC'24 contributor
I want to work on this issue.


allow to compile ROS packages on the target using the dev packages

One use case might be to compile ROS packages on the target, e.g. for debugging purposes.
With a image with
IMAGE_INSTALL += "
packagegroup-core-ssh-openssh
util-linux
catkin-dev
message-generation-dev
gencpp-dev
genmsg-dev
genlisp-dev
genpy-dev
std-msgs-dev
message-runtime-dev
cpp-common-dev
roscpp-serialization-dev
"
and downloading the example ros_chatter master and executing the following lines on the target (in this case, the qemu VM):

scp user@<IP_ADDRESS>:/download-location/ros_chatter-master.zip .
export CMAKE_PREFIX_PATH=/usr
mkdir -p catkin_ws/src
cd catkin_ws
catkin_init_workspace src
unzip ../ros_chatter-master.zip -d src
catkin_make

It breaks down with:

-- Using CATKIN_TEST_RESULTS_DIR: /home/root/catkin_ws/build/test_results
-- catkin 0.5.64
-- BUILD_SHARED_LIBS is on
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- ~~  traversing 3 packages in topological order:
-- ~~  - chatter_msgs
-- ~~  - chatter_receiver
-- ~~  - chatter_sender
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- +++ processing catkin package: 'chatter_msgs'
-- ==> add_subdirectory(ros_chatter-master/chatter_msgs)
CMake Error at /usr/share/rostime/cmake/rostimeConfig.cmake:95 (message):
Project 'rostime' specifies
'/home/lukas/oe-core/build/tmp-eglibc/sysroots/qemux86-64/usr/include' as
an include dir, which is not found.  It does neither exist as an absolute
directory nor in
'/usr//home/lukas/oe-core/build/tmp-eglibc/sysroots/qemux86-64/usr/include'.
Ask the maintainer 'Dirk Thomas<EMAIL_ADDRESS>to fix it.
Call Stack (most recent call first):
/usr/share/roscpp_serialization/cmake/roscpp_serializationConfig.cmake:151 (find_package)
/usr/share/message_runtime/cmake/message_runtimeConfig.cmake:151 (find_package)
/usr/share/std_msgs/cmake/std_msgsConfig.cmake:151 (find_package)
/usr/share/catkin/cmake/catkinConfig.cmake:72 (find_package)
ros_chatter-master/chatter_msgs/CMakeLists.txt:4 (find_package)
-- Configuring incomplete, errors occurred!
Invoking "cmake" failed

The dev packages still have some hard-coded pathes in the cmake files. This disallows to use the dev packages in any other environment than the build system.

This is not a supported use-case for OpenEmbeded. @bulwahn  < Can this issue be closed?

"Silence implies consent" (see http://wiki.c2.com/?SilenceImpliesConsent).


Initial draft for thanos migration

What this PR does / why we need it:
Which issue this PR fixes (use the format fixes #<issue number>(, fixes #<issue_number>, ...) to automatically close the issue when PR gets merged): fixes #
Public facing documentation PR (if applicable)

Special notes for reviewer:
Checklist:

[ ] Added relevant notes to WIP-CHANGELOG.md
[ ] Proper commit message prefix on all commits
[ ] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[ ] is completely transparent, will not impact the workload in any way.
[ ] requires running a migration script.
[ ] will create noticeable cluster degradation.
E.g. logs or metrics are not being collected or Kubernetes API server
will not be responding while upgrading.
[ ] requires draining and/or replacing nodes.
[ ] will change any APIs.
E.g. removes or changes any CK8S config options or Kubernetes APIs.
[ ] will break the cluster.
I.e. full cluster migration is required.

Chart checklist (pick exactly one):

[ ] I upgraded no Chart.
[ ] I upgraded a Chart and determined that no migration steps are needed.
[ ] I upgraded a Chart and added migration steps.

Pipeline config (if applicable)
If you change some config options (e.g. add/rename variable or change the default value) you may need to update the config used by the pipeline in pipeline/config.

does it make sense to add
prometheus:
  prometheusSpec:
    externalLabels:
      cluster: {{ .Values.global.clusterName }}

in helmfile/values/kube-prometheus-stack-sc.yaml.gotmpl
this will help use remove all the serviceMonitor relabelings and with alerts grouping

does it make sense to add, as part of this PR, the externalLabels for sc prometheus in helmfile/values/kube-prometheus-stack-sc.yaml.gotmpl?
prometheus:
  prometheusSpec:
    externalLabels:
      cluster: {{ .Values.global.clusterName }}

this will help use remove all the serviceMonitor relabelings and with alerts grouping

As someone stated, this breaks some backup/restore functionality with influx. So I think that we start with this in a release (depricate influx) and for the release where we remove influx completely we add the externalLabel and remove the relabeling.

does it make sense to add, as part of this PR, the externalLabels for sc prometheus in helmfile/values/kube-prometheus-stack-sc.yaml.gotmpl?
prometheus:
  prometheusSpec:
    externalLabels:
      cluster: {{ .Values.global.clusterName }}

this will help use remove all the serviceMonitor relabelings and with alerts grouping

As someone stated, this breaks some backup/restore functionality with influx. So I think that we start with this in a release (depricate influx) and for the release where we remove influx completely we add the externalLabel and remove the relabeling.

can we try using a relabel_action under the remote_write for thanos?
I would like to have the correct cluster label value in thanos from the beginning.

Could you update the tests and the pipeline as well?

Would you like to enable thanos only? I'm a little bit split about this. Because right now thanos is an opt in thing. But since we are sure that it's going to be replacing influx it might be a smart idea to make it the default here right now.

Could you update the tests and the pipeline as well?

Would you like to enable thanos only? I'm a little bit split about this. Because right now thanos is an opt in thing. But since we are sure that it's going to be replacing influx it might be a smart idea to make it the default here right now.

I'm also not sure about enabling only thanos. I could see having both (the same way we will use it while migrating away from influxdb), then removing influx from the pipeline after a while.

Should we add the thanos receiver endpoint (and other ops.endpoints) to blackbox

Yes, good idea


[Feature request] Disable non active or  unnecessary entities

I just installed this integration and it seems to work quite well. But it burdens the recorder with many unnecessary entities.
The total in my setup is more than 200 entities.
I can identify possible ways to cut the number down:

When I have a Single phase setup all L2 and L3 entities are not necessary, not active.
The Victron modbus protocol has many doublettes, which means several identical values can be received from different devices. Could be tricky to identify those, I guess you are creating those values by scanning modbus, so to identify doublettes must be done after the scan. Ev. you can make it possible to mark them as doublettes afterwards. Plus a list of known doublettes can be managed by the community and integrated into the scan process.
Another method to decrease the impact on the recorder, could be to have a built-in switch for the recorder. By default, only the entities which are essential would have the recorder switched on. Dissable them switches the recorded off too I guess.

To make it easier, I select all of my entities and hide them, through the bulk select feature in home assistant.
I then manually select the 10 or so I want to see… I may make helpers and hide all of the native ones so when I have to change the ip address and delete and re-add the hub, I don’t have to do it all again.

https://community.home-assistant.io/t/bulk-edit-for-entities/289593/9
Didn't know about so far.


Enhancements and bugfixes to BV reader

I've made the following changes to the BV reader:

Greater support for older BVA files:

fallback to Latin-1 if UTF-8 doesn't work
more regex-based / efficient parsing of fields in the channels section to accommodate old-style columns with units in column names and not in fields

Fixes for reading in filter information

convert from seconds to Hz right away so that max/min comparisons actually make sense for high/low pass filters
fixed high-pass filters to actually take the highest filter setting (looks like a copy-paste error from the low-pass filter code)
fixed the code to detect that all channelwise filter settings are equal
read in software filter information when present and use that instead of amplifier settings

default to µV  (scale=1e-6) in the API -- this is both in line with the original BV format (before units were explicitly specified) and in line with the existing behavior for "truncated" files (albeit not for non-truncated files). In other words, this is more consistent, both internally and with the BV format.

Looks useful. Do you have a (preferably small) test file that has some of these problems that we could add to mne-testing-data so that you can then write unit tests that fail on master but pass on this PR? We try to follow test-driven development (TDD) so inclusion of unit tests is important.

Lemme talk to the owner of the dataset that led to the issues with older files.
The comparison of channel filter settings was something that I noticed when I was modifying that bit to work with software filter settings. I definitely don't have a dataset with different filters for different channels.

All of these refer to header files, right? So one solution might be to just write header files with various now-solved problems. We do something similar with the EEGLAB reader.
Also, hey Phillip :)

Speaking of copy-paste errors ...

And I thought about modifying header files but (1) I'm lazy and (2) 'real' files from the wild are always better.
The dataset in question is under embargo for a few more days, but I can upload a sample maybe beginning of next week? Just need to know where ....

How big is it? Files added to the test repo should be as small as possible, something like 1MB or less would be ideal. If you can get the recording people to do a 1-sec recording that would be best.

It's small (1 minute) and I'll see if I can trim it down without BV automatically updating the format. If nothing else, I can contribute the header file as an example for simulating header files with existing data.

From: Eric Larson<EMAIL_ADDRESS>Sent: Aug 25, 2016 18:23
To: mne-tools/mne-python
Cc: Phillip Alday; Author
Subject: Re: [mne-tools/mne-python] Enhancements and bugfixes to BV reader (#3532)
How big is it? Files added to the test repo should be as small as possible, something like 1MB or less would be ideal. If you can get the recording people to do a 1-sec recording that would be best.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/mne-tools/mne-python/pull/3532#issuecomment-242450274, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABmZ19TtAPVPbRB3P9hmXqJ5eXDviHX6ks5qjcGDgaJpZM4JtNk_.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/mne-tools/mne-python","title":"mne-tools/mne-python","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/mne-tools/mne-python"}},"updates":{"snippets":[{"icon":"PERSON","message":"@Eric89GXL in #3532: How big is it? Files added to the test repo should be as small as possible, something like 1MB or less would be ideal. If you can get the recording people to do a 1-sec recording that would be best."}],"action":{"name":"View Pull Request","url":"https://github.com/mne-tools/mne-python/pull/3532#issuecomment-242450274"}}}

And now with tests .... the test data does include a CRLF file which the full MNE test suite complains about but it is necessary to fully test compatibility with older BV files.

We can add it to a list of files to ignore. But how big is it? If it's more
than about 10kB it should go in mne-testing-data instead of this repo to
avoid history bloat.

Hmm 28 kB (I looked) is right on the threshold for me. We'll have to see what @agramfort thinks but for now it can stay in this PR to simplify things.
In any case, add the file to this list of _tab_ignores:
https://github.com/mne-tools/mne-python/blob/master/mne/tests/test_docstring_parameters.py#L64

Looks reasonable to me. Don't forget to update doc/whats_new.rst. I guess this should go in BUG section, since we 1) couldn't read some files and 2) didn't properly populate the Info filter settings in others.

Should the change to the scale parameter be separated off and put into the API section?

Good question. Is it actually an API change, or is it a change in terminology? I'm not quite clear on how the behavior has changed.

I would count it as an API change -- scale now actually defaults to microvolts, but used to default to volts with one codepath (truncated files) silently using microvolts. This wasn't obvious previously because newer BV files have the scale explicitly set via their internal configuration and so the test sets didn't pick up this mismatch.

@Eric89GXL @agramfort @dengemann Anybody have a few to review ?

Can this break existing code?
Is API change a bug fix?
@jaeilepp any thoughts?

This could in theory break existing code, but shouldn't because:

Newer BV files have their scaling set in the vhdr file and older files didn't work anyway (hence all the changes)
This was already silently done for the "truncated" BV files (e.g. those exported by EEGLAB).

So I don't know whether the API change is really a bugfix: it's definitely in line with some previous implicit behavior.

The API change was done in c56895002027c492d64dfe9a603ffc8859e8882d but the actual assumption of microvolt raw data scaling for no units listed in done in 229b25418336a00f76c32eec8fad548a8bf9cdb0, without any reference to the scale parameter.
The scaling with the scale parameter is actually performed later:
https://github.com/palday/mne-python/blob/5ee27296b933fd0ff6969a842cc5f46ed19ddd29/mne/io/brainvision/brainvision.py#L376
So the API change doesn't quite do what it's supposed, but then again the scale parameter also doesn't do what the previous documentation claimed. It doesn't assume any type of unit, but rather scales the raw data.
Maybe the better change would be to note that scaling simply scales the raw data by a constant in addition to the scaling implied by the units in the file. If there are no units in the channel infos section of the header file, then µV are assumed?

More concretely, revert the API change and instead change the documentation:
scale : float
    The scaling factor for EEG data. Unless specified otherwise by
    header file, units are in microvolts. Default scale factor is 1.

Sounds good to me

API change reverted and scale documentation fixed. Commits done in such a way that you can cherry-pick and squash to rid the history of the undone changes.

travis is not happy and errors are related.
besides diff LGTM

@agramfort The issue with the line-endings -- I would add that to the exceptions list because part of reading the older BV files is reading with alternate line-endings (even though the standard library functions should handle this distinction automatically) instead of changing the line endings.

ok please fix/update the test in test_line_endings.py so CIs are happy and we can merge this.
thx @palday

@palday you need to rebase

And fix a string issue in Python3 ...

let us know when CIs are happy

Current coverage is 87.30% (diff: 79.03%)

Merging #3532 into master will increase coverage by <.01%

@@             master      #3532   diff @@
==========================================
  Files           341        341
  Lines         59702      59744    +42
  Methods           0          0
  Messages          0          0
  Branches       9084       9092     +8
==========================================
+ Hits          52117      52157    +40
- Misses         4862       4865     +3
+ Partials       2723       2722     -1

Powered by Codecov. Last update 71b15a7...50fed8c

green merging !
thx @palday


LWT routing optimisation

This enables optimisation of LWT queries routing. If the cluster supports the LWT mark protocol extension, then it will be negotiated and henceforth prepared statements which contain an LWT will be routed to the replicas only.
Partly fixes: #100
Pre-review checklist

[x] I have split my patch into logically separate commits.
[x] All commit messages clearly explain what they change and why.
[ ] I added relevant tests for new features and bug fixes. [TODO]
[x] All commits compile, pass static checks and pass test.
[x] PR description sums up the changes and reasons why they should be introduced.
[ ] I added appropriate Fixes: annotations to PR description.

Tests are yet to be done, but first I'd love a review to make sure the approach is right. @piodul @cvybhu

v2:

moved towards gocql solution (optimisation only present in TokenAwarePolicy, in other cases leaving default behaviour),
addressed naming and docstrings comments
@piodul Could you take a look now?

Apart from small comments, looks good.
@wprzytula what about automatic tests? Could it be done using the proxy? If not, did you do any manual tests? If you are not going to include automatic tests then please describe your manual tests and put them in the PR's description.

I've rebased on current main and adjusted for changed CachingSession (by extending RawPreparedStatementData with is_confirmed_lwt value).

---- speculative_execution_is_fired stdout ----
Unique name: test_rust_1669812108_0
thread 'speculative_execution_is_fired' panicked at 'timeout: the function call took 5008 ms. Max time 5000 ms', scylla/tests/retries.rs:19:1
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Looks like the speculative_execution_is_fired test took too long and failed :/ This is unrelated to the PR, but it shows that our timeouts in tests are definitely too short (this one got 5 seconds). I saw during local tests that Scylla spends a lot of time processing schema updates - here, it was Cassandra that failed, but I would suspect that it was too slow due to similar reasons.

---- speculative_execution_is_fired stdout ----
Unique name: test_rust_1669812108_0
thread 'speculative_execution_is_fired' panicked at 'timeout: the function call took 5008 ms. Max time 5000 ms', scylla/tests/retries.rs:19:1
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Looks like the speculative_execution_is_fired test took too long and failed :/ This is unrelated to the PR, but it shows that our timeouts in tests are definitely too short (this one got 5 seconds). I saw during local tests that Scylla spends a lot of time processing schema updates - here, it was Cassandra that failed, but I would suspect that it was too slow due to similar reasons.

As a quick mitigation, I'll just increase timeout in the integration tests to 30 seconds each. It will additionally trigger CI check again, so that should suffice to pass CI and merge this.


removing Bad imgs - correlation

Examples look great, thanks for doing this!

Change the path in the 10,000 image stack to be
img_stack = np.load("100_500_NIPA_GEL.npy")

Instead of the full path on your laptop

Great, thanks!  Looks good!


Share FUNSD trained model weights

Hi,
It is a great help that you have shared a SPADE model trained on CORD dataset - makes setting up and sanity-checks with this codebase much easier.
Any chance you could also share the weights of a trained FUNSD model?
thanks,
Aruni

Hi @AruniRC
Unfortunately, as I have moved to a new position, I'm no longer able to access the trained model.
Please use  funsd.1.5layers.train.yaml(https://github.com/clovaai/spade/blob/master/configs/funsd.1.5layers.train.yaml) to train the model.
Wonseok


feat: adds verification for zksync block explorer

Motivation

Previously using --verify targeting ZKsync block explorer verification service it would fail

Closes #566

Solution

Fixes verification by implementing ZkVerificationProvider formatted to adhere to ZKsync verification service while maintaining the Etherscan verification
Adds zksync verifier, should be used alongside --verifier-url

Example usage
Using forge create
forge create --zksync --rpc-url https://sepolia.era.zksync.dev --constructor-args "ForgeUSD" "FUSD" 18<PHONE_NUMBER>000000000000 --private-key <PRIVATE-KEY> --verifier zksync  --verifier-url https://explorer.sepolia.era.zksync.dev/contract_verification  --verify src/MyToken.sol:MyToken

Using forge verify-check

Passing verification ID, and specifying verifier and  verifier-url

forge verify-check 27487 --verifier zksync --verifier-url https://explorer.sepolia.era.zksync.dev/contract_verification --chain zksync-testnet

Using forge verify-contract
forge verify-contract 0x21d6dffe4B406c59E80CD62b4cB1763363c8a040 src/Counter.sol:Counter --verifier zksync --verifier-url https://explorer.sepolia.era.zksync.dev/contract_verification --zksync

Foundry-zksync-book

https://github.com/matter-labs/foundry-zksync-book/pull/28

TODO

[x] Test with standardJSON
[ ] Test using scripts (FAILS)
[x] Test with more contracts (with libraries)
[x] Test with additional compiler settings
[x] Update foundry book
[x] Test with forge verify-check
[x] Test with forge verify-contract

Fails when using scripts right now. Let me know if I should introduce those changes in a subsequent PR.

Thanks for the contribution @Jrigada !!! It seems to work with basic examples (e.g. Counter.solscript) but fails for others. Specifically trying to--verify` upgradeable contracts from these scripts fails with:
    ├─ [0] VM::getCode("ProxyableCrowdfundingCampaign.sol") [staticcall]
    │   └─ ← [Revert] Multiple matching artifacts found
    └─ ← [Revert] Multiple matching artifacts found

Has this feature been included in a release yet? Keen to test it out!

Hey @jarrodwatts, I believe this feature made it into our nighlty release for a few days at the very least :)
For sure if you get the latest nightly release you'll have the feature available to use :)


Latest portal-version broke HttpTriggered functions

From @dersia on April 14, 2017 18:15
Since the last update (new "next"-portal) there seems to an issue with Http-Triggered Functions.
I came across this issue when I added a second Http-Triggred function to my function app.
The Problem is with the Route-Template:
FunctionA - RouteTemplate: "{id]/"
FunctionB - RouteTemplate: ""
this causes the runtime to add the name of the function to the route for FunctionB but not for FunctionA.
So when you call FunctionB (postman or testing-tab in portal) FunctionA and FunctionB is called where for the FunctionA call the {id} is set to the name of FunctionB.
I understand why this is happening, but I think this is not attended and I'm almost sure it wasn't that way before.
The weirdest thing, though, is that there are no logs shown for the FunctionB call in the Portal.
I'm certain that this issue is not a WebJobsSDK issue and more a Azure Functions Portal issue.
Copied from original issue: Azure/Azure-Functions#251

@alrod could you take a look?

no repro


Depricated?

I'm a bit confused about the Wave 1 2020 and this article. Does this article describes the new module, that improves the existing change tracking based functionality?
Regards,
Alexander

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

ID: 3d51ad6f-b7a7-7abd-f1d1-1d7963dd3d49
Version Independent ID: 4612ff88-8457-2f49-8222-4fd110fd72f6
Content: Replicate data to Azure SQL Database - Power Platform Admin center
Content Source: power-platform/admin/replicate-data-microsoft-azure-sql-database.md
Service: power-platform
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

@soutchilin
Please provide the Release Plan topic you're referring to above. Thanks.

@soutchilin
Perhaps you're looking for  ‘Export to data lake’ - https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/export-to-data-lake which is a similar service that instead of going from Common Data Service to Azure SQL, it exports to Azure data lake.


Sample rule to restrict transfers of sum of all BTs to allowed limit.

It contains sample contract to restrict the sum of all the transfers of BTs to allowed limit in a single transaction.
Fixes #101

We are providing an implemenation of global constrainta and not mocking anything.
So,it cannot be a mock contract.


I18N: add Hindi translation file

Describe what problem your feature request solves
It would be good to have the Hindi translation for Threat Dragon
Describe the solution you'd like
Modify translation file
Additional context

Hello @professorabhay , the translation file is in place so this is now all yours. Thank you for offering to do this translation

Hello @jgadsden, Thanks for the help. I'll raise PR soon !!


Bot Doesn't Respond to Tagged Tweets When Running in Docker

When I run the bot using npm start, everything works perfectly: it tweets and responds to tagged tweets as expected. However, when I run the bot inside Docker, I encounter the following issues:
Environment Variable: The OPENAI_API_KEY  is required when running the bot in Docker (docker compose up) , but it's not needed when running it directly (without Docker).
Tweeting: The bot tweets without any issues when running in Docker.
Response to Tagged Tweets: The problem arises when the bot is supposed to respond to tweets it's tagged in. While it tweets fine, it doesn't respond to any tagged tweets.
I’ve checked the logs, and everything seems normal—there are no visible errors.
Could anyone help identify what might be causing this issue when running the bot inside Docker?

Can you provide logs from your docker container ?


Port to federated extensions (with eager loading of shared extensions)

Fixes #288, closes #49 and fixes #264. Does not solve #269, i.e. the extension manager remains disabled as we do not offer support for source extensions but currently the extension manager assumes that both prebuild (federated) and source extension are supported.
Code changes

uses webpack module federation, in line with upstream and retrolab to deliver the core packages to the frontend

differently than upstream, the core packages are loaded eagerly which reduces the extent of changes needed; this might be suboptimal for web deployments but it should not matter for a desktop app that much

properly re-uses the PageConfig provided by the server; this also means that we get the URL for the licenses endpoint
the lab app will now be loaded asynchronously after the prebuilt extensions are fetched; I kept the changes in the App to the minimum (i.e. I kept the old synchronous methods) to avoid conflicts with other work you may have and used then instead.
updated target to es2020 since we now ship Electron 12 (2019 would probably do fine too)
we now copy the resolutions from upstream as those define the version of shared packages we offer; we could create our own resolutions, but I believe it is better to stick to the upstream algorithm and ensure we are in sync

Please note that our custom extensions (electron-extension, desktop-extension) are not shared, i.e. third-party extensions cannot depend nor use them.
User-facing changes
Prebuilt extensions, such as MIME renderers and other output-related extensions work if installed into the correct environment:
plotly:

jupyterlab-git:

jupyterlab-lsp + pylsp server:

The licences component is now available:

This pull request has been mentioned on Jupyter Community Forum. There might be relevant details there:
https://discourse.jupyter.org/t/how-to-run-jupyter-lab-without-the-terminal-on-windows-10/11419/12

New user-facing change with the latest commit, this is the appName in PageConfig is now set to JupyterLab Desktop:

I am not fully convinced about the name change; the longer name might help in user awareness and support, but is well, longer. Either would work fine for me - please let me know what you think.

Really nice!


Can you update metronome operation while AudioKit is running?

Is is possible to update the metronome operation while audiokit is running?
Trying to create a click track in the background while running a sequence. Using the metronome operation but can't seem to be able to update the metronome frequency without making AudioKit stop working.
I want to call an update method whenever the tempo is updated in the UI text field, but after updating the AudioKit output stops.
//AudioKit has already by started, trying to update the metronome operation generator with new frequency
func update(tempo: Double){
if clickGenerator != nil{
print("Stopping click generator")
clickGenerator.stop()
return;
    }

    clickOperation = AKOperation.metronome(tempo) // metronome needs frequency
    clickGenerator = AKOperationGenerator(operation: clickOperation)
    avAudioNode = clickGenerator.avAudioNode
    clickGenerator.start()
}

Yes you can, let me whip up an example.

Ok, thank you Aure!

So, basically you need to replace the tempo constant with an AKOperation.parameters(parameterNumber) call.  Here is the code from a playground that increases the tempo over time:
import AudioKit
import XCPlayground

var currentFrequency = 1.0
let beep = AKOperation.sineWave(frequency: 480)

let trig = AKOperation.metronome(AKOperation.parameters(0))

let beeps = beep.triggeredWithEnvelope(
    trig,
    attack: 0.01, hold: 0, release: 0.01)

let generator = AKOperationGenerator(operation: beeps)
generator.parameters = [currentFrequency]

AudioKit.output = generator
AudioKit.start()
generator.start()

AKPlaygroundLoop(frequency: 5) {
    currentFrequency *= 1.1
    generator.parameters = [currentFrequency]
}

XCPlaygroundPage.currentPage.needsIndefiniteExecution = true

If this wasn't sufficient, please feel free to reopen the issue, but I think for now this is resolved.

Great, this is exactly what I needed. Thank you for your help.


Automatic host discovery/multiple routes

Some kind of automatic discovery of other hosts on the bus would be nice. Maybe even with gateway announcements from the radio(s)...

Or implement source routing by caching discovered routes in every hop.

Host discovery has not been made possible with CSP 2.0 L2 broadcast.
Redundant radio links is possible with PROMISC mode on CAN bus.
I'm closing this now.


className feature not working in child components

Versions

vee-validate: 2.0.9
vue: 2.5.16

Describe the bug
VeeValidate ignores the classes and classNames attributes when working on child components: the child components won't be decorated with the classNames classes.
To Reproduce

Add the veeValidate plugin to Vue with the aforementioned attributes, for instance:

Vue.use(VeeValidate, {
  classes: true,
  classNames: {
  valid: 'ok',
  invalid: 'wrong',
},
});

Setup a vue component that renders an <input> tag within its template.
Add the v-validate attribute to the component with some validation rule.
When validation applies, the vue component -nor the <input> within- won't be decorated with the valid or invalid classes.

Expected behavior
I'm not sure what would be the expected behavior here: either the component will get the classes added, or the <input> tag inside.
Demo Link
https://jsfiddle.net/zacxggy9/92/
Desktop (please complete the following information):

OS: Mac Os 10.13.4
Browser: Chrome 66.0

Additional context
In the fiddle, you will find also that the inputs get the aria-required and aria-valid... attributes, even if the aria option is passed as false. I think we should add another issue regarding this, just commenting this out in case it is somehow related, since I guess the classes and aria attributes addition may share the same mechanism internally.
(Btw, the bug is not related with the aria option: it will show up also if the aria option is omitted).

they do share the same mechanism but classes are not applied if the input is a custom component. as it introduces issues like element pollution and SSR issues in rare cases, also there are the third party components disabling inheritAttrs option which makes the behavior inconsistent. So I opted to disable it for custom components at the moment.
Currently, you can bind the flags object and pass it to the component so it controls its own UI state rather than vee-validate which is much better in my opinion. I haven't yet thought of a good solution for this issue so feel free to suggest one, but it can't be automatic in the same way as the HTML5 inputs.

Thanks for your response @logaretm. Sorry for open a duplicated issue, didn't found the same issue.
I believe I sort of understood what you mean. The idea is to bind the fields object to be able to use the flags inside the child component computed properties, isn't it?.
I set up a fiddle which I believe illustrates the mechanism:
https://jsfiddle.net/zacxggy9/141/
I would appreciate if you could check it and point out any problems with such approach, or possible improvements.
Some extra tweaks apart from bind the field are needed, like setting touched flag explicitly, like says the flags documentation page.
However, it seems that you forgot to copy a fiddle link at the end of the page :cry:.

I wasn't able to locate the fiddle but it was pretty much like yours, a slightly better version would be to map the custom class names to those flags since a css framework would be used in most cases.
this example maps the custom class names to the flags and opts out of any additional classes that you did not specify.
https://jsfiddle.net/zacxggy9/147/
I'm leaning towards removing the auto classes since it is not consistent and you reporting this issue shows it. Maybe replace it with a utility class mapper and let the user specify the classes themselves. Not sure yet but won't be introduced until the next major version 3.x


webapp create resulted in "'NoneType' object has no attribute 'lower'"

This is autogenerated. Please review and update as needed.
Describe the bug
Could create a webapp using cli. Upgraded to the latest version
Command Name
az webapp create
Errors:
'NoneType' object has no attribute 'lower'
Traceback (most recent call last):
Local\Temp\pip-unpacked-wheel-49qlvzn7\knack\cli.py, ln 215, in invoke
azure\cli\core\commands\__init__.py, ln 654, in execute
azure\cli\core\commands\__init__.py, ln 718, in _run_jobs_serially
azure\cli\core\commands\__init__.py, ln 709, in _run_job
azure\cli\command_modules\appservice\commands.py, ln 55, in _polish_bad_errors
azure\cli\core\commands\__init__.py, ln 688, in _run_job
azure\cli\core\commands\__init__.py, ln 325, in __call__
pip-unpacked-wheel-03qxfwck\azure\cli\core\__init__.py, ln 784, in default_command_handler
azure\cli\command_modules\appservice\custom.py, ln 154, in create_webapp
azure\cli\command_modules\appservice\custom.py, ln 1040, in _format_fx_version
AttributeError: 'NoneType' object has no attribute 'lower'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp create -g {} -p {} -n {}

Expected Behavior
webapp created
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.14.0

Extensions:
azure-devops 0.18.0
db-up 0.2.0
interactive 0.4.4

Additional Context

webapp


KML parsing fails as of DuckDB v1.1.2

Not sure whether this is a GDAL issue or duckdb_spatial issue, but KML parsing sometimes fails in DuckDB v1.1.2, worked in v1.1.1
v1.1.2:
copy (SELECT
            'hello-'||generate_series AS name,
            'world-'||generate_series AS desc,
            format('POINT(52.{} 4.{})', generate_series, generate_series)::geometry AS geom
          FROM generate_series(1,100)) to 'test.kml' with (format 'GDAL', driver 'KML');

select count(*) from st_read('test.kml');
IO Error: GDAL Error (1): XML parsing of KML file failed : unclosed token at line 278, column 2

select count(*) from st_read('test.kml');
IO Error: GDAL Error (1): GDALOpen() called on test.kml recursively

v1.1.1:
select count(*) from st_read('test.kml');
┌──────────────┐
│ count_star() │
│    int64     │
├──────────────┤
│          100 │
└──────────────┘

Hi! Thanks for opening this issue!
Im unable to reproduce the error using the code you provided, both when building duckdb from source and when using the one provided by brew. What platform are you on?
maxxen@Maxs-MacBook-Pro-2 duckdb_spatial % duckdb
v1.1.2 f680b7d08f
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
D load spatial;
D copy (SELECT
              'hello-'||generate_series AS name,
              'world-'||generate_series AS desc,
              format('POINT(52.{} 4.{})', generate_series, generate_series)::geometry AS geom
            FROM generate_series(1,100)) to 'test.kml' with (format 'GDAL', driver 'KML');
D
D select count(*) from st_read('test.kml');
┌──────────────┐
│ count_star() │
│    int64     │
├──────────────┤
│          100 │
└──────────────┘

I'm using Ubuntu 22.04 on x86_64 using DuckDB CLI v1.1.2
$ rm ~/.duckdb/extensions/v1.1.2/linux_amd64/*
$ duckdb
v1.1.2 f680b7d08f
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
D install spatial; load spatial;
D copy (SELECT
              'hello-'||generate_series AS name,
              'world-'||generate_series AS desc,
              format('POINT(52.{} 4.{})', generate_series, generate_series)::geometry AS geom
            FROM generate_series(1,100)) to 'test.kml' with (format 'GDAL', driver 'KML');
D select count(*) from st_read('test.kml');
IO Error: GDAL Error (1): XML parsing of KML file failed : no element found at line 279, column 0
D

The behaviour appears to be size related:
D copy (SELECT
              'hello-'||generate_series AS name,
              'world-'||generate_series AS desc,
              format('POINT(52.{} 4.{})', generate_series, generate_series)::geometry AS geom
            FROM generate_series(1,53)) to 'test.kml' with (format 'GDAL', driver 'KML');
D select count(*) from st_read('test.kml');
┌──────────────┐
│ count_star() │
│    int64     │
├──────────────┤
│           53 │
└──────────────┘
D copy (SELECT
              'hello-'||generate_series AS name,
              'world-'||generate_series AS desc,
              format('POINT(52.{} 4.{})', generate_series, generate_series)::geometry AS geom
            FROM generate_series(1,54)) to 'test.kml' with (format 'GDAL', driver 'KML');
D select count(*) from st_read('test.kml');
IO Error: GDAL Error (1): XML parsing of KML file failed : unclosed token at line 279, column 0

With 53 rows the file is 8058 bytes, and with 54 rows it is 8206 bytes. Presumably ~8192 is the boundary.
I tried building DuckDB from source and downloading from https://github.com/duckdb/duckdb/releases/download/v1.1.2/duckdb_cli-linux-amd64.zip and both give the same error.


Use GalleryCardList in Gallery

What happened?
Currently we have duplicated implementation for the same stuff on GalleryCard.vue
Please reproduce in steps
Moreover, the hover effect does not work on screens like profile or collection detail.
Expected Behavior
[BLOCKED] By first basilisk impl
What browsers are you seeing the problem on?
No response
Are you logged in?
No response
At which address did you encounter bug?
No response
Screenshots
~
Relevant log output
~

Payment link for reward
https://kodadot.xyz/transfer/?target=<My_Kusama_Address_check_https://github.com/kodadot/nft-gallery/blob/main/CONTRIBUTING.md#creating-your-ksm-address>
Code of Conduct

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

I'll take this

@petersopko is this some edge case ?

Alright, issues labelled "blocked" won't be up for grabs by the bot, I'll think of some message tomorrow and add this to the mix.

is this some edge case ?

I meant that: Why are issues without a bounty label are locked for 36hrs?

is this some edge case ?

I meant that: Why are issues without a bounty label are locked for 36hrs?

Ah, @yangwao was asking about the blocked label at the same time. I thought you meant that.
Issues without bounty labels are locked for 24hrs by default. Frequent contributors to the repository (10+ merged PRs) get a 50% time boost for assignments, therefore, 36hrs for unlabeled ones -> #2932

Nice bot


Remove allowInputShuffle_ flag in AggregationTestBase::testReadFromFiles

Simplify the AggregationTestBase by automatically determining if the
aggregate function is order-sensitive, which would disallow input shuffling.
If the orderSensitive flag is set to true for any of the test aggregates,
disable the test from files.
Fixes #9274

@mbasmanova Hi Masha, could you please help review this PR? Thanks.

Hi @mbasmanova I've updated the PR to address comments and remove allowInputShuffle_ flag. Could you please have another look? Thanks.


docs: update doc for edgex2.2 upgrade

Signed-off-by: Valina Li<EMAIL_ADDRESS>

doc on-hold for now, need to update after few refactoring is done


Twitter :large fix

fixes #3

By the way, i do not know if it is customary to create issues on github for problems you are planning to fix straight away, as it is my first time doing a PR, but I did it anyway.


Qualification tool: Add filtering based on configuration parameters

This fixes https://github.com/NVIDIA/spark-rapids/issues/3043.
Filtering for configuration parameters is done for specific values of configuration or keys of configs if values are not provided.
Added tests for all cases and updated Readme.
If multiple configs are given where some have specific values and some have just the keys, then specific values takes precedence and filtering is done based on that.

build

build


fix: add support for pluginDownloadURL from schema.json

Description
This PR will fix the issue described in #1109.
updated build.gradle code with info.metaClass.server

generated plugin.json:

Fixes #1109
Checklist

[ ] I have added tests that prove my fix is effective or that my feature works

[ ] I have updated the CHANGELOG-PENDING file with my change

[ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version

@EronWright Too bad I was a little to late for 0.12.0 #1364
@t0yv0


New features (default params, MultiplyOp, NeqOp)

Closes #39, #42, #43

Thanks @edi9999! I've released these changes (with some minor additions of my own) in v1.22.0.


[BUG]: Stratify notebook does not produce non-directed stratification when asked

Scenario:
Step:
Link to the project:

Describe the issue
A clear and concise description of what the bug is.
When asking the notebook to "Stratify my model by the ages young and old where young and old can become old, but old cannot become young" the resulting code block produces
model = stratify(
template_model=model,
key= "Age",
strata=['young', 'old'],
structure= [['young', 'old']],
directed=True,
cartesian_control=False,
modify_names=True,
concepts_to_stratify=None, #If none given, will stratify all concepts.
params_to_stratify= None, #If none given, will stratify all parameters.
param_renaming_uses_strata_names = True
)
directed should be False

A similar problem occurs in this issue:
https://github.com/DARPA-ASKEM/terarium/issues/5286
I think this only requires a tweak to the code generation instructions. TBD.


feat(flow): flow node addr key

I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
#4094
What's changed and what's your intention?
add a key to store mapping from flownode id to addr
Please explain IN DETAIL what the changes are in this PR and why they are needed:

Summarize your change (mandatory)
added a mapping from flownode id to flownode addr, so that in distributed mode can flownode be registered and discover(which will be in a subsequent PR)

Checklist

[ ] I have written the necessary rustdoc comments.
[ ] I have added the necessary unit tests and integration tests.
[ ] This PR requires documentation updates.

I'm working on this in #4166.

Close for #4166


Closes: #3927

Closes: #3927

I'm sorry, but I am unable to test this pr, as:

error: could not find system library 'glib-2.0' required by the 'glib-sys' crate
error: could not find system library 'gobject-2.0' required by the 'gobject-sys' crate
and idk how to resolve this on nixos. I already tried bringing those modules into my current environment.

Please give this PR a proper title and description


Documentation

Currently, Tarmac is pretty unstable.
Once it's more stable, we should build a documentation site for it to help users adopt it.

Documentation is available in README.md for now.


Cherry-pick PR #6506 into release-0.23: [writeset-generator] Implement a primitive tooling for generating genesis writeset

This cherry-pick was triggerd by a request on #6506
Please review the diff to ensure there are not any unexpected changes.

Motivation
This implements an offchain binary tool that would be used by node operators to generate genesis writeset in case of some catestropic scenarios. In case of a majority of validator lossed, this tools, together with the db bootstrapper will be used to remove bad validators to kick validators out from the network.
The flow should be following: when we lost 1/3 of the node in the network, each node operator would:

Pause their own network
Sync their node to the latest committed state.
Use this tool to generate waypoint transaction. e.g:
run cargo run --bin libra-writeset-generator -- --output <path-to-genesis-transaction> remove-validators <addresses to be removed>
Spawn up the db bootstrapper with the genesis transaction generated in step 4 provided.

Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Added e2e test for the generated transaction.

cc @sherry-x

/land

@sherry-x :exclamation: This PR is still missing approvals, unable to queue for landing

/land


netlify.toml: use partial paths for redirects

Removing the domain part of the URL in the from fields ensures that
netlify will trigger the redirect on any domain. Going forward we should
be able to check redirects on preview deploys before merging.
Signed-off-by: Cedric Charly<EMAIL_ADDRESS>

URLs to check:
/cl/538063
/issue/123
/issues/123
/discussion/1818
/releases/v0.4.3


Using the converter renders less informative Java var names

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

This feels like a regression in the quality of the generated programs when introducing the converter into the pipeline.
Original PR where this is discovered: https://github.com/pulumi/pulumi-azuread/pull/484
All variables are held equal during the comparison, the change is just introducing the pulumi convert plus the converter at 1.0.11 version into the pipeline.
Example HCL:
data "azuread_client_config" "current" {}

resource "azuread_user" "example" {
  display_name        = "J Doe"
  owners              = [data.azuread_client_config.current.object_id]
  password            = "notSecure123"
  user_principal_name =<EMAIL_ADDRESS>}

resource "azuread_group" "example" {
  display_name     = "MyGroup"
  owners           = [data.azuread_client_config.current.object_id]
  security_enabled = true

  members = [
    azuread_user.example.object_id,
    /* more users */
  ]
}

Java rendering without the converter:
package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.azuread.AzureadFunctions;
import com.pulumi.azuread.User;
import com.pulumi.azuread.UserArgs;
import com.pulumi.azuread.Group;
import com.pulumi.azuread.GroupArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        final var current = AzureadFunctions.getClientConfig();

        var exampleUser = new User("exampleUser", UserArgs.builder()
            .displayName("J Doe")
            .owners(current.applyValue(getClientConfigResult -> getClientConfigResult.objectId()))
            .password("notSecure123")
<EMAIL_ADDRESS>            .build());

        var exampleGroup = new Group("exampleGroup", GroupArgs.builder()
            .displayName("MyGroup")
            .owners(current.applyValue(getClientConfigResult -> getClientConfigResult.objectId()))
            .securityEnabled(true)
            .members(exampleUser.objectId())
            .build());

    }
}

Java rendering with the converter:
package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.azuread.AzureadFunctions;
import com.pulumi.azuread.User;
import com.pulumi.azuread.UserArgs;
import com.pulumi.azuread.Group;
import com.pulumi.azuread.GroupArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        final var current = AzureadFunctions.getClientConfig();

        var example = new User("example", UserArgs.builder()
            .displayName("J Doe")
            .owners(current.applyValue(getClientConfigResult -> getClientConfigResult.objectId()))
            .password("notSecure123")
<EMAIL_ADDRESS>            .build());

        var exampleResource = new Group("exampleResource", GroupArgs.builder()
            .displayName("MyGroup")
            .owners(current.applyValue(getClientConfigResult -> getClientConfigResult.objectId()))
            .securityEnabled(true)
            .members(example.objectId())
            .build());

    }
}

Affected area/feature

Yeh we need to make use of __logicalName to not change resource names in conversion.

Looks like the same problem is affecting not just Java, but python, node and Go. I had a build problem that was masking that. But now it's uncovered.

This is because the converter is using "Resource" as a suffix to make the resource names unique rather than using the type of the resource. Should be a fairly easy fix.

I think this looks done as of this morning!

@Frassle, what's involved to fix this? Is this a quick fix that you or @Zaid-Ajaj could pick up?

https://github.com/pulumi/pulumi-azure/pull/1377 specifically does not have this problem anymore. After it picked up 1.0.13 in https://github.com/pulumi/pulumi-azure/pull/1377/commits/f9d3f3bb38fa9bce17064ecd8e0d2be6167d1ba5 so I think 1.0.13 must contain a fix.

https://github.com/pulumi/pulumi-converter-terraform/pull/107 would have fixed this. There's a couple of outstanding questions from that implementation though.
Firstly, if variables conflict (i.e. two terraform blocks both called "example" but with different type) should we use the type name on all of them, or should the first be allowed to claim just "example"?
Secondly, should we be suffixing with the type always, not just when there's name conflicts?
Obviously if we answer yes to the second question the first question is redundant.


Update meta.yaml for latest PyPI released version

Checklist

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

@conda-forge-admin, please rerender

@conda-forge-admin, please restart ci

can I get an approval/merge @yehoshuadimarsky or @stefan-jansen? Getting an annoying downgrade of this package when updating to pandas 2 because the pd 2 compatible version of this isn't on conda-forge


[server-wallet] Remove dependency on devtools

The server-wallet currently depends on @statechannels/devtools. It could be a dev dependency, but it shouldn't be a dependency.

This is already in master.


Update dependencies

Description
Fixes #14
Blocked by https://github.com/Mankeli-Software/mankeli_core/pull/2
Conventional Type

[ ] ✨ feat
[ ] 🛠 fix
[x] ✅ chore
[ ] 📝 doc
[ ] 🧪 test
[ ] ❌ BREAKING CHANGE

I can see that Flutter version is set to 3.10.5:
https://github.com/Mankeli-Software/dart_define/blob/2d84cf86872fb38ab8d0de16d1e9eacb429f7fc9/.github/workflows/flutter_ci.yaml#L16
Is there a reason to keep it at 3.10.5, or can it be updated to the latest version?
The CI has failed because pub_updater 0.5.0 requires dart sdk 3.5.0+, while CI has dart 3.0.0
However, pub_updater 0.4.0 has no such requirement - if preserving compatibility with 3.10.5 is a priority, I can roll back pub_updater to 0.4.0, which would still solve the issue #14


Integer "feature names" can raise exception

If a user submits a file that has integer and non-integer (i.e. valid) names for rows, an exception is raised due to numbers being passed to an str.join method.
Two issues:

cast the integers to strings
allow integers as row names if there are other non-integer present? Need to evaluate this requirement and resolve any unit tests.

Addressed the first part of this in 83cd163d3626c9bd03398f80e22674f099661e81


fix: get_color should not throw error when name is not string

AFAIK, this is a private function, not even exposed outside utils.lua, so I think it safe to assume that the function will always used correctly

@fitrh yeah, you are right, but it will read the color from outside. And actually after I upgrade the plugin this morning, I met the error like it's not a lua string, blabla 😢

@Miloas can you provide a minimum reproduction steps of your issue ? I use the latest version and works without any problem

I am curious if you are you using any custom colours & what theme - we derive from the theme highlights which could provide something wonky

curious if you are you using any custom colours & what theme - we derive from the theme highlights which could provide something wonky
edit: maybe update and see if this issue persists as we reverted 4e69c2a

cool, it works!
I use gruvbox theme, and it's CursorLineNr highlight is weird, so I set it to none.


Publish 7.4-20211223172113+0000

Publish 7.4-20211223172113+0000

@bot-gradle test and merge

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

Pre-tested commit build failed.


DebugMode uses .NET Framework 4.8 instead of .NET Core 6.0

Mod version: v1.0.5
Game version: v1.4.101 - Release
Melon loader version: v0.6.1
Issue: Using .net Framework 4.8
Screenshot
N/A
Log file
N/A
Additional Info
DebugMode is using .Net Framework 4.8:
https://github.com/LeCloutPanda/DebugMode/blob/main/DebugMode.csproj#L12C1-L12C58
Vampire Survivors is a Il2Cpp game and based on the following link:
https://melonwiki.xyz/#/modders/quickstart

Basic mod setup
First, you will need to create a new project. Unity versions require different project templates:
Any Il2Cpp game:
    Template: Class Library
    Framework: .NET 6.0

It should be using .NET Core 6.0.
Using .NET 6.0 make debugging on visual studio significantly easier. I haven't been able to setup debugging correctly with a .NET 4.8 mod yet.
Debugging on 4.8 gives me the following error due to a mixture of .NET Framework and .NET Core.

If there's a reason why you're using an older version .NET, I'd love to know why for my own mods 😊
Thanks,
Nick

Hi Nick.
No there is no particular reason I wrote my mods in .Net  4.8, I was the first person to push mods for the new engine so I didn't have much knowledge on the subject and just wanted to push a product out without thinking which version of .Net 4.8 instead of .Net 6. In saying that I will be updating it to .Net 6 now along side my other mods.
Thanks,
Panda


Build stops, looking for httpclient

The current build goes looking for http://maven.repository.redhat.com/techpreview/all/org/apache/httpcomponents/httpclient/4.2.6/httpclient-4.2.6.jar, but this jar is not to be found.  (The build hangs.)
It looks like every jar in that vicinity has 'redhat' in it's name.
Thanks!

Hi,
I've tested running the build in a clean environment without any problems. The repository link that you mention does not feature in our build so maybe it's something in your ~/.m2/settings.xml that's causing Maven to go looking for artifacts elsewhere.
What Maven version are you using? Also, when you refer to 'current build'. Is that the community or productized version of wildfly-camel?

Hi James.
Thanks for that response.  Your suspicion was correct, I removed a few extra entries from my settings.xml and cleaned my local repo, Wildfly-Camel built after that.
I'm working with the community build, BTW.  Trying to get a handle on the project, it's components and quickstarts, etc.
Thanks again.  This Issue can be marked 'closed'.
Rick


fix: pick query params with empty values

Issue Reference(s):
Fixes #2467
/claim #2467

This doesn't fix the issue for me 🤔  It's still calling the endpoint without the query param for a null value

This doesn't fix the issue for me 🤔 It's still calling the endpoint without the query param for a null value

can you give a working config pls

@angristan can you join the discord server for faster communication
https://discord.gg/tn2Gtg7s

@angristan can you try the new changes

This fixes it ✅


Can't recieve Calender

msg : string[45]
"Nextcloud:CalDAV -> get calendars went wrong."
Actual nextcloud and credentials are set and right.
Can't get any calender. "Müllabfuhr" "Personal" etc are not working.

same issue with webdav in node :
"Nextcloud:WebDAV -> send file went wrong."

i modify the node to get the error and  i got : self signed certificate in certificate chain
it may be possible that you had the same @masterdot

Same here.
Checkmarked "Accept self signed certificates" to use self-signed certificate.
in the server properties
Some doku with examples might be helpful. Had to look up in the code....

I am having this same issue. I am not using self-signed certificates though and I can not find the option to allow self signed.

Same here.
Checked "Accept self signed certificates" but still "Nextcloud:CalDAV -> get calendars went wrong."
any ideas


settings contains illegal dictionary path

On MacOS I found this file inside my Eclipse installation:
Eclipse.app/Contents/MacOS/D:\\devonws\\TempIde\\workspaces\\main\\development\\settings\\eclipse\\project.dictionary
This obviously looks like a hardcoded path that accidentally went into our settings.

I can not find that this comes from our settings:
https://github.com/devonfw/devon-ide-settings/blob/2109a1010a31cfb767c9cb6e44defc918d2f50f0/eclipse/workspace/update/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.jdt.ui.prefs#L148
However, it is for sure that "devonws\TempIde\workspaces\main\development\settings" is 100% from our devon-ide and can not come from the original eclipse release distribution.

I have to try a new installation from scratch.
For the record: D:\\devonws\\TempIde\\workspaces\\main\\development\\settings\\eclipse is a single folder inside MacOS folder that contains project.dictionary file.

This error cannot be reproduced anymore. It came from a very old settings repo with some odd settings.


python312Packages.mkdocs-material: 9.5.17 -> 9.5.18

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.mkdocs-material is: Material for mkdocs
meta.homepage for python312Packages.mkdocs-material is: https://squidfunk.github.io/mkdocs-material/
meta.changelog for python312Packages.mkdocs-material is: https://github.com/squidfunk/mkdocs-material/blob/refs/tags/9.5.18/CHANGELOG
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.5.18 with grep in /nix/store/06rnf3zrknasi7086z8hq74gy38zi0q5-python3.12-mkdocs-material-9.5.18
found 9.5.18 in filename of file in /nix/store/06rnf3zrknasi7086z8hq74gy38zi0q5-python3.12-mkdocs-material-9.5.18

Rebuild report (if merged into master) (click to expand)

18 total rebuild path(s)

18 package rebuild(s)

First fifty rebuilds by attrpath
copier
hydrus
netbox
netbox_3_6
netbox_3_7
ntfy-sh
python311Packages.canals
python311Packages.mkdocs-jupyter
python311Packages.mkdocs-material
python311Packages.mkdocs-mermaid2-plugin
python311Packages.mkdocs-redoc-tag
python311Packages.mkdocstrings-python
python312Packages.canals
python312Packages.mkdocs-jupyter
python312Packages.mkdocs-material
python312Packages.mkdocs-mermaid2-plugin
python312Packages.mkdocs-redoc-tag
python312Packages.mkdocstrings-python

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/06rnf3zrknasi7086z8hq74gy38zi0q5-python3.12-mkdocs-material-9.5.18 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.mkdocs-material https://github.com/r-ryantm/nixpkgs/archive/3cc77d62e11af3a6ed0829d3e26c59e917bf7d94.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/3cc77d62e11af3a6ed0829d3e26c59e917bf7d94#python312Packages.mkdocs-material

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/06rnf3zrknasi7086z8hq74gy38zi0q5-python3.12-mkdocs-material-9.5.18
ls -la /nix/store/06rnf3zrknasi7086z8hq74gy38zi0q5-python3.12-mkdocs-material-9.5.18/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

31 packages built:

copier
copier.dist
hydrus
hydrus.doc
netbox (netbox_3_7)
netbox_3_6
ntfy-sh
python311Packages.canals
python311Packages.canals.dist
python311Packages.mkdocs-jupyter
python311Packages.mkdocs-jupyter.dist
python311Packages.mkdocs-material
python311Packages.mkdocs-material.dist
python311Packages.mkdocs-mermaid2-plugin
python311Packages.mkdocs-mermaid2-plugin.dist
python311Packages.mkdocs-redoc-tag
python311Packages.mkdocs-redoc-tag.dist
python311Packages.mkdocstrings-python
python311Packages.mkdocstrings-python.dist
python312Packages.canals
python312Packages.canals.dist
python312Packages.mkdocs-jupyter
python312Packages.mkdocs-jupyter.dist
python312Packages.mkdocs-material
python312Packages.mkdocs-material.dist
python312Packages.mkdocs-mermaid2-plugin
python312Packages.mkdocs-mermaid2-plugin.dist
python312Packages.mkdocs-redoc-tag
python312Packages.mkdocs-redoc-tag.dist
python312Packages.mkdocstrings-python
python312Packages.mkdocstrings-python.dist

Maintainer pings
cc @dali99 for testing.

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

42 packages built:

copier
copier.dist
hydrus
hydrus.doc
netbox (netbox_3_7)
ntfy-sh
python311Packages.canals
python311Packages.canals.dist
python311Packages.jsonfeed
python311Packages.jsonfeed.dist
python311Packages.mkdocs-jupyter
python311Packages.mkdocs-jupyter.dist
python311Packages.mkdocs-material
python311Packages.mkdocs-material.dist
python311Packages.mkdocs-mermaid2-plugin
python311Packages.mkdocs-mermaid2-plugin.dist
python311Packages.mkdocs-redoc-tag
python311Packages.mkdocs-redoc-tag.dist
python311Packages.mkdocs-rss-plugin
python311Packages.mkdocs-rss-plugin.dist
python311Packages.mkdocstrings-python
python311Packages.mkdocstrings-python.dist
python311Packages.validator-collection
python311Packages.validator-collection.dist
python312Packages.canals
python312Packages.canals.dist
python312Packages.jsonfeed
python312Packages.jsonfeed.dist
python312Packages.mkdocs-jupyter
python312Packages.mkdocs-jupyter.dist
python312Packages.mkdocs-material
python312Packages.mkdocs-material.dist
python312Packages.mkdocs-mermaid2-plugin
python312Packages.mkdocs-mermaid2-plugin.dist
python312Packages.mkdocs-redoc-tag
python312Packages.mkdocs-redoc-tag.dist
python312Packages.mkdocs-rss-plugin
python312Packages.mkdocs-rss-plugin.dist
python312Packages.mkdocstrings-python
python312Packages.mkdocstrings-python.dist
python312Packages.validator-collection
python312Packages.validator-collection.dist


docs issue?

Hi Konstantin,
Could the docs for react-routing be outdated? The README file shows examples of router.use(...) and router.route(...), but those don't seem to work or exist in the source code.
Thanks!
Bruno

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27157912-docs-issue?utm_campaign=plugin&utm_content=tracker%2F18115217&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F18115217&utm_medium=issues&utm_source=github).

Yep, the docs are outdated. Here is a usage sample:
https://github.com/kriasoft/react-starter-kit/blob/master/src/routes.js

+1

Yes. react-starter-kit has switched to use @koistya's universal-router. There's a great overview of it at http://slides.com/koistya/universal-router and you can check out the repo at https://github.com/kriasoft/universal-router

Docs had been updated to reflect the latest API changes.


js: migrated webhook deliveries to vue components

This patch also includes a small fix that was preventing the request of
the webhook to happen when no authentication were provided.
Signed-off-by: Vítor Avelino<EMAIL_ADDRESS>

Only merge this after #1824.


fix/feat: ability to use asyncio.run with Snake.start and Snake.start_gateway

What type of pull request is this?

[ ] Non-breaking code change
[x] Breaking code change
[ ] Documentation change/addition
[ ] Tests change

Description
Converted Snake.start and Snake.start_gateway to async methods inorder to enforce to use if asyncio.run.
Additionally this PR removes the use of a loop attribute.
Changes
Removed the loop attribute from the following classes:

Snake
HTTPClient
WebsocketClient

Changed the following methods from non-async to async:

Snake.start
Snake.start_gateway

Removed the loop and asyncio_debug keyword arg from Snake
Also removed start_gateway keyword arg from Snake.login
Checklist

[x] I've formatted my code with Black
[x] I've ensured my code works on Python 3.10.x
[x] I've tested my code

If youre removing asyncio debug, you'll need to remove it from debug scale too. By default it enables the asyncio's debug logging


how to solve react-navigation-stack error react native ios

i am new in react native but when i trying to build my application in IOS its show me this Error
i am using below command
react-native bundle --entry-file index.js --platform ios --dev false --bundle-output ios/main.jsbundle --assets-dest ios

but its show me below Error, anyone know how to solve this Error. because spend 5 hours to solve this error but not success
ABCs-Mac-mini-6:ServiceProviderApp ABCEDFC$ react-native bundle --entry-file index.js --platform ios --dev false --bundle-output ios/main.jsbundle --assets-dest ios

Loading dependency graph, done.

Loading dependency graph...

While trying to resolve module `react-navigation-stack` from file `/Users/ABCEDFC/Desktop/react-native/New folder/ServiceProviderApp/node_modules/react-navigation/src/react-navigation.js`, the package `/Users/ABCEDFC/Desktop/react-native/New folder/ServiceProviderApp/node_modules/react-navigation/node_modules/react-navigation-stack/package.json` was successfully found. However, this package itself specifies a `main` module field that could not be resolved (`/Users/ABCEDFC/Desktop/react-native/New folder/ServiceProviderApp/node_modules/react-navigation/node_modules/react-navigation-stack/dist/index.js`. Indeed, none of these files exist:

  * `/Users/ABCEDFC/Desktop/react-native/New folder/ServiceProviderApp/node_modules/react-navigation/node_modules/react-navigation-stack/dist/index.js(.native||.ios.js|.native.js|.js|.ios.json|.native.json|.json|.ios.ts|.native.ts|.ts|.ios.tsx|.native.tsx|.tsx)`

  * `/Users/ABCEDFC/Desktop/react-native/New folder/ServiceProviderApp/node_modules/react-navigation/node_modules/react-navigation-stack/dist/index.js/index(.native||.ios.js|.native.js|.js|.ios.json|.native.json|.json|.ios.ts|.native.ts|.ts|.ios.tsx|.native.tsx|.tsx)`

@addikhann could you please provide some extra information about what versions of RN, react-navigation and babel are you using? Also will be great to see you .babelrc/babel.config.js
Thanks!

closing because we can't do much without more info. @addikhann - you can try clearing your local packager / babel cache


[Mounts on images] add_local_file/add_local_dir

Since we create new methods we have the opportunity to introduce otherwise breaking logic changes for where to put/how to names files that have been somewhat inconsistent or poorly documented so far.
Here is my attempt at an overview of the state of various edge case handling of directories and files copying:
Directories
shell
If you have a file source_dir/foo
cp -r source_dir /dest in shell creates a /dest/source_dir/foo
whereas adding a trailing slash on the source:
cp -r source_dir/ /dest in shell creates a /dest/foo
docker
In docker COPY source_dir /dest you always copy the content of the dir and never the dir itself (as if you always had a trailing slash in shell cp source dir).
If you want an output directory with the same name you specify that in the destination path explicitly.
current Modal Mount.from_local_dir
The current way this works in Modal mounts today and in add_local_dir in this PR is how it works in Docker (always copy contents, never the directory itself).
current Modal image.copy_local_dir
Same as modal.mounts/docker - always copies content into the destination dir
Individual files
shell
cp some_file dest  # this creates dest as a file
cp some_file dest/  # this creates dest/some_file and fails if dest doesn't exist
docker
COPY some_file dest  # this creates dest as a file
COPY some_file dest/  # this creates dest/some_file and creates the dest dir if it doesn't exist
current Modal Mount.from_local_file
Mount.from_local_file("some_file")  # this creates a file named "some_file"
Mount.from_local_file("some_file", remote_path="dest")  # this creates a file named /dest
Mount.from_local_file("some_file", remote_path="dest/")  # this creates a file named /dest 🤡 🤯
current Modal image.copy_local_file
Image.copy_local_file("some_file")  # this creates a file named some_file in workdir
Image.copy_local_file("some_file", remote_path="dest")  # this creates a file named dest in workdir
Image.copy_local_file("some_file", remote_path="dest/")  # this creates the dest/ dir in workdir and creates a file dest/some_file 👍
Current differences compared to existing copy_ commands:

Trailing slash on the remote_path of add_local_file works the same regardless if we're using mounts or images
The current copy_local_ commands support relative destination paths, but add doesn't. This is fixable, but a bit messy, so I'm leaving it out for now and adding an exception when using relative paths so we can fix it later and people don't rely on the "broken" implementation.

Changelog

Adds Image.add_local_file(..., copy=False) and Image.add_local_dir(..., copy=False) as a unified replacement for the old Image.copy_local_*() and Mount.add_local_* methods.

@prbot approve


bad handshake - requests.exceptions.SSLError

Hi,
I read and tried what's in other threads without success. This is the error:
 python -c "import requests;  requests.get('https://acciseonline.agenziadogane.it')"

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/filippo/src/venvs/test_ssl_sito_dogana/local/lib/python2.7/site-packages/requests/api.py", line 70, in get
    return request('get', url, params=params, **kwargs)
  File "/home/filippo/src/venvs/test_ssl_sito_dogana/local/lib/python2.7/site-packages/requests/api.py", line 56, in request
    return session.request(method=method, url=url, **kwargs)
  File "/home/filippo/src/venvs/test_ssl_sito_dogana/local/lib/python2.7/site-packages/requests/sessions.py", line 488, in request
    resp = self.send(prep, **send_kwargs)
  File "/home/filippo/src/venvs/test_ssl_sito_dogana/local/lib/python2.7/site-packages/requests/sessions.py", line 609, in send
    r = adapter.send(request, **kwargs)
  File "/home/filippo/src/venvs/test_ssl_sito_dogana/local/lib/python2.7/site-packages/requests/adapters.py", line 497, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: ("bad handshake: Error([('SSL routines', 'SSL23_GET_SERVER_HELLO', 'sslv3 alert handshake failure')],)",)

it runs inside a virtualenv
(test_ssl_sito_dogana) filippo@savage:~/src/venvs/test_ssl_sito_dogana$ which python
/home/filippo/src/venvs/test_ssl_sito_dogana/bin/python
(test_ssl_sito_dogana) filippo@savage:~/src/venvs/test_ssl_sito_dogana$ pip --version
pip 9.0.1 from /home/filippo/src/venvs/test_ssl_sito_dogana/local/lib/python2.7/site-packages (python 2.7)

here the pip freeze output
(test_ssl_sito_dogana) filippo@savage:~/src/venvs/test_ssl_sito_dogana$ pip freeze | sort
appdirs==1.4.0
backports.shutil-get-terminal-size==1.0.0
cffi==1.9.1
configparser==3.5.0
cryptography==1.7.1
decorator==4.0.11
elpy==1.13.0
enum34==1.1.6
flake8==3.2.1
idna==2.2
importmagic==0.1.7
ipaddress==1.0.18
ipdb==0.10.2
ipython==5.1.0
ipython-genutils==0.1.0
jedi==0.9.0
mccabe==0.5.3
ndg-httpsclient==0.4.2
nose==1.3.7
packaging==16.8
pathlib2==2.2.1
pep8==1.7.0
pexpect==4.2.1
pickleshare==0.7.4
pkg-resources==0.0.0
prompt-toolkit==1.0.9
ptyprocess==0.5.1
pyasn1==0.1.9
pycodestyle==2.2.0
pycparser==2.17
pyflakes==1.5.0
Pygments==2.2.0
pyOpenSSL==16.2.0
pyparsing==2.1.10
requests==2.13.0
scandir==1.4
simplegeneric==0.8.1
six==1.10.0
traitlets==4.3.1
wcwidth==0.1.7

and here some openssl info:
(test_ssl_sito_dogana) filippo@savage:~/src/venvs/test_ssl_sito_dogana$ python -c "import ssl; print ssl.OPENSSL_VERSION"
OpenSSL 1.0.2g  1 Mar 2016

(test_ssl_sito_dogana) filippo@savage:~/src/venvs/test_ssl_sito_dogana$ openssl s_client -connect acciseonline.agenziadogane.it:443
CONNECTED(00000003)
depth=3 C = SE, O = AddTrust AB, OU = AddTrust External TTP Network, CN = AddTrust External CA Root
verify return:1
depth=2 C = GB, ST = Greater Manchester, L = Salford, O = COMODO CA Limited, CN = COMODO RSA Certification Authority
verify return:1
depth=1 C = GB, ST = Greater Manchester, L = Salford, O = COMODO CA Limited, CN = COMODO RSA Domain Validation Secure Server CA
verify return:1
depth=0 OU = Domain Control Validated, OU = SSL, CN = acciseonline.agenziadogane.it
verify return:1
---
Certificate chain
 0 s:/OU=Domain Control Validated/OU=SSL/CN=acciseonline.agenziadogane.it
   i:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
 1 s:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
   i:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Certification Authority
 2 s:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Certification Authority
   i:/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root
 3 s:/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root
   i:/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIFczCCBFugAwIBAgIQc2nmdmmY4REjS+9DUxt9NjANBgkqhkiG9w0BAQsFADCB
kDELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4G
[...]
BFDOspLDTFNZ4/WmvfSS/VGZhbqewlpyD+GCYvdiiOrrhxX7cOXkQrBR0ckEypX2
qWl7dMhwlA==
-----END CERTIFICATE-----
subject=/OU=Domain Control Validated/OU=SSL/CN=acciseonline.agenziadogane.it
issuer=/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
---
No client certificate CA names sent
---
SSL handshake has read 5585 bytes and written 619 bytes
---
New, TLSv1/SSLv3, Cipher is RC4-SHA
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1
    Cipher    : RC4-SHA
    Session-ID: FE200000E6B4995A513CC8625648B6F13F32666D5858585812C08958DF770000
    Session-ID-ctx:
    Master-Key: 35260147D2EEB4B465892E426BBD8504190DDC895FFA894DE0079A40C50247AF1080C1FF792D8E255AF2CD6F2A04087E
    Key-Arg   : None
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time:<PHONE_NUMBER>
    Timeout   : 300 (sec)
    Verify return code: 0 (ok)
---

Hi there!
This is not the first time this website has been reported to us as a problem. However, I should note for the future that this website has quite possibly the worst TLS configuration I have ever seen.
Requests refuses to talk to this server in the default configuration because it cannot establish a secure connection: we don't support any of the ciphers that this server does, because all of them are weak. You can get this to work by enabling support for 3DES as shown in this answer, but I strongly recommend you don't do that, and that instead you put pressure on your governmental representatives to fix this terrible TLS configuration.

thank you for your response. I'll try to enable 3DES.

but I strongly recommend you don't do that, and that instead you put pressure on your governmental representatives to fix this terrible TLS configuration.

have you noticed the '.it' at the end of the url? Our government/parliament isn't able to produce a electoral law:  it's impossible to 'put pressure' on anyone.... Right now no one cares about IT services... To be honest no one cares about the people, too... it's a sad story....

I have, but it's not really my place to make judgements about the Italian electoral system. The best I can really do is point out which organisation needs to take action. =(

the following code works. Thank you for your support.
import requests
from requests.adapters import HTTPAdapter
from requests.packages.urllib3.util.ssl_ import create_urllib3_context

# This is the 2.11 Requests cipher string.
CIPHERS = (
    'ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:'
    'DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:'
    '!eNULL:!MD5'
)

class DESAdapter(HTTPAdapter):
    def init_poolmanager(self, *args, **kwargs):
        context = create_urllib3_context(ciphers=CIPHERS)
        kwargs['ssl_context'] = context
        return super(DESAdapter, self).init_poolmanager(*args, **kwargs)

if __name__ == '__main__':
    s = requests.Session()
    s.mount('https://acciseonline.agenziadogane.it', DESAdapter())
    print s.get('https://acciseonline.agenziadogane.it')

anyway how did you spot that 3des was missing and necessary? I'm asking just to understand the topic and avoid to re-ask for similar problems.

So, I have a moderate advantage in that I do maintenance of the TLS configuration in Requests.
However, the Requests cipher string lives at requests.packages.urllib3.util.ssl_.DEFAULT_CIPHERS. You can check what that turns out to be on your system in most cases by running
openssl ciphers `python -c "import requests; print(requests.packages.urllib3.util.ssl_.DEFAULT_CIPHERS)"`

Of course, that produces a lot of output, so the compressed form used in Requests may be more helpful, which is:
'ECDH+AESGCM:ECDH+CHACHA20:DH+AESGCM:DH+CHACHA20:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:RSA+AESGCM:RSA+AES:!aNULL:!eNULL:!MD5'

This translates to, in order of preference:

(ECDH+AESGCM) Any cipher suite using Elliptic-Curve Diffie-Hellman key exchange and AES in GCM mode; or
(ECDH+CHACHA20) Any cipher suite using Elliptic-Curve Diffie-Hellman key exchange and ChaCha20 (not widely available in OpenSSL yet); or
(DH+AESGCM) Any cipher suite using regular Diffie-Hellman key exchange and AES in GCM mode; or
(DH+CHACHA20) Any cipher suite using regular Diffie-Hellman key exchange and ChaCha20 (same caveat as before); or
(ECDH+AES256) Any cipher suite using Elliptic-Curve Diffie-Hellman key exchange and 256-bit AES in any mode; or
(DH+AES256) Any cipher suite using regular Diffie-Hellman key exchange and 256-bit AES in any mode; or
(ECDH+AES128) Any cipher suite using Elliptic-Curve Diffie-Hellman key exchange and 128-bit AES in any mode; or
(DH+AES) Any cipher suite using regular Diffie-Hellman key exchange and any-strength AES in any mode (this basically covers the same as DH+AES128, it's just set this way for completion); or
(RSA+AESGCM) Any cipher suite using RSA key exchange and AES in GCM mode; or
(RSA+AES) Any cipher suite using RSA key exchange and AES in any mode;
(!aNULL) Also remove any cipher suites that may have made it into that list that have no authentication (there shouldn't be any, but just to be safe)
(!eNULL) Also remove any cipher suites that may have made it into that list that have no encryption (there shouldn't be any, but just to be safe)
(!MD5) Also remove any cipher suites that may have made it into that list that use MD5 for their MAC.

What's noticeable about this list? Well, it contains only two stream ciphers: AES in its appropriate stream modes, and ChaCha20. That's because we removed 3DES in the wake of the news that it's insecure for bulk transfer, as we do not control whether or not our users perform bulk transfer so it should be removed. Additionally, 3DES is very slow compared to AES and ChaCha20, so it was usually a sub-optimal choice.

clear. But let me elaborate on the theme.
From https://www.ssllabs.com/ssltest/analyze.html?d=acciseonline.agenziadogane.it&hideResults=on you got TLS_RSA_WITH_3DES_EDE_CBC_SHA is a valid cipher for the site. Now it's obvious that we need to instruct requests/openssl to use that cipher.
The way is to add to the ciphers string the following:

ECDH+3DES
DH+3DES
RSA+3DES

where are these strings listed and documented? I've found a partial answer here: https://wiki.openssl.org/index.php/Manual:Ciphers(1)
looking for TLS_RSA_WITH_3DES_EDE_CBC_SHA in that page you get:

TLS_RSA_WITH_3DES_EDE_CBC_SHA           DES-CBC3-SHA

under TLS v1.0 cipher suites.
but how do you know that ECDH+3DES or DH+3DES or RSA+3DES is the correct string to add in order to solve my problem?

You don't need to add all three of those: that's just what used to be the Requests cipher string. To add literally just that cipher suite you could add just DES-CBC3-SHA.
However, the others are groups of cipher suites. Again, they use the weird OpenSSL grouping language. "ECDH+3DES" means any cipher suite that uses Elliptic-Curve Diffie-Hellman key exchange and 3DES as the stream cipher. "DH+3DES", same deal: regular Diffie-Hellman and 3DES. Finally, "RSA+3DES" is RSA key exchange and 3DES.
In this case, you can just add the specific string you need (DES-CBC3-SHA). The string you added is a bit more liberal, because it includes forward-secret versions of 3DES that this server doesn't use. That's probably ok, and it's written that way to be a bit more defensive in case other users hit 3DES issues: it basically reverts to the Requests behaviour of 2.11, before we removed 3DES from our supported cipher list.
Unfortunately, the only way to understand what cipher strings do is to understand how a TLS cipher suite is constructed, and to understand the way OpenSSL thinks about them. That's a somewhat complex issue, but let me break it down a bit. BTW, some of this has changed in the upcoming TLSv1.3, so bear that in mind.
In TLSv1.2 and earlier, all cipher suites have got formal IANA-registered names like TLS_RSA_WITH_3DES_EDE_CBC_SHA. These names uniquely identify all the constituent parts of a cipher suite.
An authentication/signing mechanism to validate the certificate. This is not actually a free-choice: the server has to use one that matches the type of private key it has. For example, GitHub.com's certificate has an RSA private key, so it must always use a cipher suite with an RSA signature part.
A stream cipher
A key size
A MAC

The name encodes all of this. For example, consider the following names and their breakdowns:

TLS_RSA_WITH_3DES_EDE_CBC_SHA:

Key Exchange: RSA
Signing: RSA (this means this must be an RSA certificate). Note that RSA is a unique case in that if it is used as a key exchange mechanism it is also used as the signing mechanism, so only needs to be specified once)
Stream Cipher: 3DES in EDE-CBC mode
Key Size: Not specified, so it's the default for 3DES, which is 168 bits (3x56)
MAC: SHA1

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

Key Exchange: Ephemeral Elliptic-Curve Diffie-Hellman

Signing: Elliptic-Curve DSA (not common at the moment)

Stream Cipher: AES in GCM mode (the best currently-deployed AES mode)

Key Size: 256-bits

MAC: Actually, doesn't have one.
You see, I lied a little bit. Starting in TLSv1.2 we got stream ciphers with AEAD modes. These modes don't require a MAC (or, more properly, the MAC functionality is integrated with the cipher mode). However, these modes do change the way the pseudo-random numbers are generated in TLS, so the part of the name that would normally have the MAC instead have the PRF algorithm. So...

PRF: SHA384  (For non-AEAD cipher suites, the PRF is always SHA1 and MD5).

TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

Key Exchange: Ephemeral Elliptic-Curve Diffie-Hellman
Signing: RSA
Stream Cipher: ChaCha20 using Poly1305 authentication
Key Size: 256-bits
MAC: None, again, ChaCha20/Poly1305 is an AEAD cipher.
PRF: SHA256.

As you can see, this is not a totally simple idea. However, the argument goes that you can construct "groups" of cipher suites based on their common functionality. For example, if you like ChaCha20 you could construct a group of cipher suites all based on ChaCha20. This would be any suite that uses ChaCha20 as its stream cipher. In this case, as of TLSv1.2, that list is:

TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256
TLS_PSK_WITH_CHACHA20_POLY1305_SHA256
TLS_ECDHE_PSK_WITH_CHACHA20_POLY1305_SHA256
TLS_DHE_PSK_WITH_CHACHA20_POLY1305_SHA256
TLS_RSA_PSK_WITH_CHACHA20_POLY1305_SHA256

OpenSSL lets you specify these either one-by-one using their full OpenSSL name (e.g. the first one is ECDHE-ECDSA-CHACHA20-POLY1305), or as a group by just using "CHACHA20". If you wanted only the ones that use ECDHE for key exchange, you can join that requirement with a +: "ECDH+CHACHA20". Maybe you want to exclude the PSK ones (often a good idea): in that case, you can say "CHACHA20:!PSK".
The final wrinkle in here is that some of OpenSSL's full names seem a lot shorter than the IANA name, and are missing parts. Consider again our friend TLS_RSA_WITH_3DES_EDE_CBC_SHA. As you noted, OpenSSL's name for this is DES-CBC3-SHA. This only specified the stream cipher, the mode, and the MAC. Why is it missing this other stuff?
The answer is that OpenSSL has defaults: stuff that is assumed. If you don't name the key exchange mechanism, OpenSSL assumes RSA. That means that if you tried to see what OpenSSL uses for "ECDH+3DES", you'll find that DES-CBC3-SHA isn't in there. It's only present for "RSA+3DES".
Essentially the OpenSSL cipher string language is an extremely complex query system. It is moderately difficult to understand, and I recommend playing about with the openssl ciphers command to get a feel for what's going on.

wow. things are a lot clearer now. I think this answer should live on requests' main site.
thank you very much!

Thanks!
While I'm glad you liked the answer, however, I don't think Requests should document it. Touching this area of the code is very much like opening the emergency exit on an aircraft in flight. Sure, there might be a good reason to do it, and it should be possible, but the average passenger should never even realise that it can be done, let alone know how.
As much as possible we don't want users to have to touch this code at all. That's why changing this code is tricky (and undocumented). The term I like to use is "attractive nuisance": people who encounter errors when running their code will often start flicking random switches in an attempt to get it to work. verify=False is our one concession to this case in the public API. But we very much don't want the cipher suite list to be a part of this because there are too many bad cipher suites, and the list gets longer over time.
The Requests and urllib3 cipher suite list is maintained by a small number of people who keep a very careful eye on the crypto research and keep it up-to-date. We expand to use new believed-safe ciphers, and we proactively remove ones that are discovered to be bad. That is generally less-likely to happen if users are overriding our choices, so we don't want to make it too easy for users to do that unless they really, really need to.


vector_api VectorEnv incorrect

Part of the VectorEnv subsection in the API Reference section is incorrect. See everything between ### VectorEnv and ### Reset

Resolved by https://github.com/Farama-Foundation/gym-docs/pull/60#issue-1125064407


Setting IMDB Watchlist Items not working properly

Is there already an issue for your problem?

[X] I have checked older issues, open and closed

Bug Description
Even if the movies are already present in IMDB watchlist, the script adds them again.
Environment
WSL (Ubuntu 22)
Screenshots
No response

This may have been caused by a change in the IMDB CSV export data as mentioned in https://github.com/RileyXX/IMDB-Trakt-Syncer/issues/93. There is a new patch available now (v1.9.1) which should fix this problem.
Try updating to the latest version (v1.9.1) using python -m pip install IMDBTraktSyncer --upgrade and let me know whether or not it fixes this problem for you. Thanks!