Error:Failed to launch chaincode spec(Failed to init chaincode(handler not found for chaincode xxx))

Description
With pbft consensus, without membersrvc, using CORE_CHAINCODE_MODE=dev.
Deploy chaincode is successful, but invoke or query it will fail with error msg:
Error: Error querying chaincode: rpc error: code = 2 desc = "Error:Failed to launch chaincode spec(Failed to init chaincode(handler not found for chaincode xxx))"
Describe How to Reproduce

Start a hyperledger peer node or cluster with pbft as consensus following the documentation. No error msg if found at the peer nodes' output.
deploy chaincode example02 with

$ CORE_CHAINCODE_MODE=dev peer chaincode deploy -n "test" -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02 -c '{"Function":"init", "Args": ["a","100", "b", "200"]}'
07:36:35.690 [crypto] main -> INFO 001 Log level recognized 'info', set to INFO
07:36:35.691 [logging] LoggingInit -> DEBU 002 Setting default logging level to DEBUG for command 'chaincode'
07:36:35.692 [peer] func1 -> INFO 003 Auto detected peer address: <IP_ADDRESS>:30303
07:36:35.692 [peer] func1 -> INFO 004 Auto detected peer address: <IP_ADDRESS>:30303
07:36:35.693 [peer] func1 -> INFO 005 Auto detected peer address: <IP_ADDRESS>:30303
07:36:35.697 [main] chaincodeDeploy -> INFO 006 Deploy result: type:GOLANG chaincodeID:<path:"github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02" name:"test" > ctorMsg:<function:"init" args:"a" args:"100" args:"b" args:"200" >
test

query it:

$ peer chaincode query -n "test" -c '{"Function": "query", "Args": ["a"]}'
07:36:49.568 [crypto] main -> INFO 001 Log level recognized 'info', set to INFO
07:36:49.569 [logging] LoggingInit -> DEBU 002 Setting default logging level to DEBUG for command 'chaincode'
07:36:49.570 [peer] func1 -> INFO 003 Auto detected peer address: <IP_ADDRESS>:30303
07:36:49.570 [peer] func1 -> INFO 004 Auto detected peer address: <IP_ADDRESS>:30303
07:36:49.571 [peer] func1 -> INFO 005 Auto detected peer address: <IP_ADDRESS>:30303

Usage:
  peer chaincode query [flags]

Flags:
  -x, --hex[=false]: If true, output the query value byte array in hexadecimal. Incompatible with --raw
  -r, --raw[=false]: If true, output the query value as raw bytes, otherwise format as a printable string

Global Flags:
  -c, --ctor="{}": Constructor message for the chaincode in JSON format
  -l, --lang="golang": Language the chaincode is written in
      --logging-level="": Default logging level and overrides, see core.yaml for full syntax
  -n, --name="": Name of the chaincode returned by the deploy transaction
  -p, --path="": Path to chaincode
  -u, --username="": Username for chaincode operations when security is enabled

Error: Error querying chaincode: rpc error: code = 2 desc = "Error:Failed to launch chaincode spec(Failed to init chaincode(handler not found for chaincode test))"

@yeasy - when you use the CORE_CHAINCODE_MODE=dev flag, it will not actually build and deploy the chaincode in docker containers.   The purpose of "dev" mode is for you to be able to compile and run your chaincode without having to go through the full deploy cycle.
Now your situation is a little odd in that you are setting the flag while running the CLI to deploy, but this still results in the actual bytes of the chaincode not being physically deployed across the network
What are you hoping to accomplish with running in "dev" mode?

@mastersingh24
Thanks for the comments!
So in dev mode, we cannot deploy the chaincode. Then how can we run my own chaincode?
Could you help give the typical usage example with the dev mode?
Thanks a lot!

@yeasy : part of the confusion is the word "deploy".
In NON-dev mode, "deploy" does the following

compute the chaincode package for creating images
send the chaincode package to all peers
each peer creates the image
each peer starts the container
the init function is sent to each container

As @mastersingh24 points out dev mode is meant to be run with 1 local peer. It is for testing / dev only.
First of all, one runs the peer with "--peer-chaincodedev" mode.
In dev mode, "deploy" does the following

user starts the chaincode pointing to the peer
the deploy function sends "init" to the above chaincode

ie, the only purpose of "deploy" in dev mode is to send the "init".
Typical usage example for dev mode is in https://github.com/hyperledger/fabric/blob/master/docs/API/SandboxSetup.md

@muralisrini
Thanks for the comments.
So if I want to run the chaincode without container in the dev mode, is it possible to run the deploy, invoke, query steps?
Could you give some detailed steps?
Thanks!

@yeasy : Yes, that is possible. The steps for deploy, invoke and query in dev mode are in https://github.com/hyperledger/fabric/blob/master/docs/API/SandboxSetup.md. I would just be repeating them here. I'd go through "non-security" steps to get started.  But if you have more questions or need clarifications on the steps there, we could certainly talk further.

@muralisrini Thanks for the comments.
I will follow the steps first.

@muralisrini : I was trying to query transaction using the following command and see the following error
peer chaincode query -n   -c '{"Function": "query", "Args": ["a"]}' -u jim
23:52:59.542 [crypto] main -> INFO 001 Log level recognized 'info', set to INFO
Usage:
peer chaincode query [flags]
Flags:
-x, --hex[=false]: If true, output the query value byte array in hexadecimal. Incompatible with --raw
-r, --raw[=false]: If true, output the query value as raw bytes, otherwise format as a printable string
Global Flags:
-c, --ctor="{}": Constructor message for the chaincode in JSON format
-l, --lang="golang": Language the chaincode is written in
--logging-level="": Default logging level and overrides, see core.yaml for full syntax
-n, --name="": Name of the chaincode returned by the deploy transaction
-p, --path="": Path to chaincode
-u, --username="": Username for chaincode operations when security is enabled
Error: Error querying chaincode: rpc error: code = 2 desc = "Error:Failed to launch chaincode spec(Error starting container: cannot connect to Docker endpoint)"
I'm running peer in NON-DEV mode (mode: net). In net mode, validator will run chaincode in docker container.
Brief summary of peer node log
23:14:57.568 [devops] invokeOrQuery -> DEBU 03c Initializing secure devops using context jim
23:14:57.568 [crypto] invokeOrQuery -> INFO 03d Initializing client [jim]...
23:14:57.682 [crypto] invokeOrQuery -> INFO 03e Initializing client [jim]...done!
23:14:57.682 [devops] createExecTx -> DEBU 03f Creating secure invocation transaction 774fd330-ed1f-4a4d-b472-15386f3b5505
23:14:57.683 [devops] invokeOrQuery -> DEBU 040 Sending invocation transaction (774fd330-ed1f-4a4d-b472-15386f3b5505) to validator
23:14:57.683 [peer] sendTransactionsToLocalEngine -> DEBU 041 Marshalling transaction CHAINCODE_QUERY to send to local engine
23:14:57.683 [peer] sendTransactionsToLocalEngine -> DEBU 042 Sending message CHAIN_TRANSACTION with timestamp seconds:1463786097 nanos:683657855  to local engine
23:14:57.950 [chaincode] getArgsAndEnv -> DEBU 043 Executable is /opt/gopath/bin/7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568
23:14:57.950 [chaincode] launchAndWaitForRegister -> DEBU 044 start container: 7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568(networkid:dev,peerid:vp0)
23:14:57.950 [container] lockContainer -> DEBU 045 waiting for container(dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568) lock
23:14:57.950 [container] lockContainer -> DEBU 046 got container (dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568) lock
23:14:57.950 [dockercontroller] Start -> DEBU 047 Cleanup container dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568
23:14:57.950 [dockercontroller] stopInternal -> DEBU 048 Stop container dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568(cannot connect to Docker endpoint)
23:14:57.950 [dockercontroller] stopInternal -> DEBU 049 Kill container dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568 (cannot connect to Docker endpoint)
23:14:57.951 [dockercontroller] stopInternal -> DEBU 04a Remove container dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568 (cannot connect to Docker endpoint)
23:14:57.951 [dockercontroller] Start -> DEBU 04b Start container dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568
23:14:57.951 [dockercontroller] createContainer -> DEBU 04c Create container: dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568
23:14:57.951 [dockercontroller] Start -> ERRO 04d start-could not recreate container cannot connect to Docker endpoint
23:14:57.951 [container] unlockContainer -> DEBU 04e container lock deleted(dev-vp0-7849b0cdbc04a8498e3601188bf4ef87d25b5efda9d89cdb879914fcbbe544a429d379bdcb210e2ba7de131ee84b53b974e3afcbacbcf0e2db4ec408a4ddb568)
23:14:57.951 [chaincode] LaunchChaincode -> DEBU 04f launchAndWaitForRegister failed Error starting container: cannot connect to Docker endpoint
23:14:57.951 [crypto] CloseClient -> INFO 050 Closing client [jim]...
Question here being why is the container being taken offline aka terminated ?


Problem with encoding

Good day!
 I installed your bot on my discord server. Works. And thanks for that. But since the coding on my site cp1251_general_ci I get the import of news in stacc characters.
��������� ������ � ��������� ceh9 �� ���� �������� �������
I already changed the encoding from utf-8 to cp1251 in files FlattenedJSON.js and Article.js, but it did not help. Ready to pay for help.

Think issue can be resolved?


mouseOver Events

Is 'mouseOver' event supported? I'm trying to render an SVG image and I want to do something on mouse over. Please suggest me some related links.

This package is used to output html content overtop of a map so anything you can do with html you can do with this package

Thank you. That helped.


[BP-1.18][FLINK-36421] [fs] [checkpoint] Sync outputStream before returning handle in FsCheckpointStreamFactory

Backport of FLINK-36421 for 1.18
Cherry-pick of commit dfb9bfeabac8d3ac289e46a3017ed68c50ba3777 from original PR #25468

@flinkbot run azure

/home/vsts/work/1/s/flink-end-to-end-tests/test-scripts/test_docker_embedded_job.sh: line 65: docker-compose: command not found

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure

I guess there is something wrong with CI infra for 1.18. Any thoughts? @JingGe
I'd propose merge this since this is a small one.

I would vote on merging since it's trivial change and all other branches tests are passing.

Will merge this without CI green ....


Add TOC to README

I do not want to click on each and every folder to see what the SPECs are about, so would be nice to have a TOC like https://github.com/astropy/astropy-APEs . 😅
I am not sure if these are the columns you want, so I am happy to modify the columns. Would be nice for outsider to see the statuses of the SPECs at a glance too. And once SPEC is accepted, would be nice to have a permanent DOI people can cite.

This is auto-generated: https://scientific-python.org/specs/ and has all the information in the README table, but will also automatically include additional information that may be hard to include in the README (for example which projects have endorsed the SPEC and what its status is).
I would rather not have too much additional manual work needed. I also don't like having to manually format tables. Is the website not sufficient? If not, maybe we should consider improving the quickstart.py script to also update the README using tabulate or something.

Okay, fair point. I will close this.


How to contol RWM  implementations of the target image?

I could not find any information in the wiki, how to control whitch rwm implementations are included in the final image.
I am missing something like: Only depend on "fastrtps" or  only include "cyclone" in the image.
I dont want to have multiple rwm implementations in the image, as it only would waste space and never is used.
Is it possible?

See https://github.com/ros/meta-ros/pull/854 with that both fastrtps and cyclonedds are installed in every rolling and galactic image built with meta-ros.
If you want to remove one of them, then you would need to add a bbappend for rmw-implementation and remove the one you don't want from ROS_EXEC_DEPENDS.
Similarly like "rmw-connext-cpp rmw-connextdds" is removed from ROS_BUILD_DEPENDS when connext is in ROS_WORLD_SKIP_GROUPS.
You can also send a patch to support fastrtps and cyclonedds as ROS_WORLD_SKIP_GROUPS to remove this more automatically based on ROS_WORLD_SKIP_GROUPS (especially if there are more recipes ending with runtime dependency on the implementation you want to remove)

This appears to have been answered already.  Please reopen the issue if you have any follow-up questions.


Fix invalid json

Commas missing after string array elements

Fixed in v1.2.0 - sorry for the long wait and thanks for the PR!!!


No Subscriptions found

Hi,
I just installed Storage Explorer and wanted to connect to my subscription through my Microsofot Azure account.
I connect succesfully but now it says that there are "No subscriptions found" while I do have 1 subscription.
Connecting directly to one of my storage accounts is on the other hand possible..

@DR93EHV can you please try checking the checkbox for the "Default Directory" tenant?

@DR93EHV can you please try checking the checkbox for the "Default Directory" tenant?

Thanks @MRayermannMSFT ! Works for me.

@MRayermannMSFT
You suggestion did the job, but I wonder why I have wrong (expired) subscription even visible?

I'm also getting "No subscriptions found".

I'm interested in the hotmail account, not the Buzzhorn one.
There's no "Default directory" checkbox.


[WIP] Adding sensor delay setting for android

Adding a new project setting to be used on Android with which you can set the sensor update frequency. This defaults to the setting "Game" which is good for games (whats in a name), it is a faster update frequency then normal but still retains some accuracy taking out jitter from the accelerometer, gyrometer and magnetometer readings.
For VR however this update frequency is not high enough resulting in a lot of jitter and you need to use the "Fastest" option.
The new setting allows you to set all 4 presets available in Android. The higher/faster the update frequency, the more noise there will be in the readings but the more up to date your reading is.
Fixes #19645

I lack a good phone to test this on, if anyone could verify my work that be cool

Needs a rebase, and I guess some changes after your recent refactor?

Needs a rebase, and I guess some changes after your recent refactor?

Yeah I just need to find time to actually do it...

Moving to 4.0 milestone as it's not mergeable for now. If it can be fixed in coming days though, I'm happy to include it in 3.2.

@BastiaanOlij Another reminder that this needs to be rebased on the latest master branch.
Otherwise, abandoned pull requests will be closed in the future as announced here.

I need to get back into doing stuff with Android, too many other things going on at the moment

This PR has not received any new commits for over a year, closing. It can be re-opened or re-created if the feature is rebased on the latest master.


runTests opens three windows

I was trying to test a filesystem provider and now runTests() opens three windows.
I since stripped everything down to
const { runTests } = require("@vscode/test-electron");
runTests({})

and I still get three opened windows on each run.

Hi @connor4312 . Thanks for the follow up. I solved it by deleting the the .vscode-test folder.

Speaking of. How would you write a test for a custom filesystem provider, like your memfs example? Is it possible?


Download parquet files with huggingface_hub instead of duckdb in split-descriptive-statistics

will fix https://github.com/huggingface/datasets-server/issues/1712#issuecomment-1690029285

Codecov Report
Patch coverage: 100.00% and project coverage change: +6.21% :tada:

Comparison is base (07a290a) 86.13% compared to head (aab7fcf) 92.34%.

:exclamation: Current head aab7fcf differs from pull request most recent head 78340db. Consider uploading reports for the commit 78340db to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1719      +/-   ##
==========================================
+ Coverage   86.13%   92.34%   +6.21%
==========================================
  Files          52       81      +29
  Lines        2763     5673    +2910
==========================================
+ Hits         2380     5239    +2859
- Misses        383      434      +51

Flag
Coverage Δ

libs_libapi
?

services_admin
?

services_api
?

services_rows
?

services_search
?

services_worker
92.34% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

services/worker/src/worker/config.py
100.00% <100.00%> (ø)

...worker/job_runners/split/descriptive_statistics.py
93.95% <100.00%> (ø)

... and 131 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Breaking changes in minor version release 1.13.2 to 1.14.0

The 1.14.0 release appears to contain breaking changes. and the CHANGELOG entry includes a note on the breaking changes. If this project is following semver  as the Jazzband contribution guidelines state, I believe this release should be 2.0.0.
Expected Behavior

Breaking changes result in a major version release.
Current Behavior

Breaking changes released as a minor version release.
Possible Solution

Re-release 1.14.0 as 2.0.0.
Context

Since I override the built in templates, the changes between 1.13.2 and 1.14.0 broke my login pages. Specifically because it cannot load the two_factor templatetags anymore.

Re-release 1.14.0 as 2.0.0.

Oh, and far more important:
Release 1.14.1, reverting the breaking changes! That should happen immediately, even if a 2.0.0 release needs longer.

Sorry this won't happen. Please pin your dependency if it is an issue for you.

Sorry this won't happen. Please pin your dependency if it is an issue for you.

Eh? What kind of behaviour do you think that is?
You are explicitly using semantic versioning, yet you tell downstreams to not rely on it and instead ditch reasonable handling of security updates?

Oh, and just so you know what this means in reality:
Downstreams that provide reasonable security support might have several supported versions out. In our case, we have AlekSIS-Core 2.4, 2.7 and 2.9 out as supported versions. All of them depend on django-two-factor-auth ^1.x.0, which is correct because we want users to get the most recent, compatible versions of dependencies.
Now, by telling us we have to work around your semver-disrespecting release ourselves, you are telling us that we have to publish maintenance releases of all these supported versions, pinning the dependency to a fixed version – and after that start monitoring django-two-factor-auth manually and backport all future fixes manually because security updates are disabled for it.
With that attitude, you are deliberately fostering maintainer burnout in free software products.
So, please fix the havoc you caused – it is a really trivial thing to do, while working around it is a major catastrophe for downstreams!

That's exactly true.


Breaks a ROCm venv

Beware, installing this will break a ROCm pytorch environment. After you install this you'll need to reinstall the ROCm torch:
pip uninstall torch torchvision && pip install torch torchvision --index-url https://download.pytorch.org/whl/rocm5.7
Once you do this, the node will fail to load, but at least you can still use ComfyUI, and hopefully MrForExample can fix the node.

They will never understand not to play with people's environments. At least this one only has torch and xformers. I've seen others enforcing xformers in their code with 'xformers=true' and the only way to turn it off is to find the 3 lines of code in 500 files that use it and turn it off.
"The current goal of this project is to achieve desired pose2video result with 1+FPS on GPUs that are equal to or better than RTX 3080!"
Well the 7900XTX is better than RTX3080. Why break it? Torch and Xformers should be the job of the user and the UI to install. They should never be required by custom nodes as users already have them, otherwise they wouldn't be able to use Comfy in the first place.

Your requirements file has xformers. Which forces reinstall of nvidia torch and torchvision. Can you remove it from requirements.


Doesn't work if wifi already connected on plugin start

This affects primarily people not using enso but h-encore on 3.67.
sceNetCtlInetGetState needs to be called once at the time when setting the net callback in order to check if the network is already connected.

It should be fixed, here is the fixed version:
vitacompanion-debug.zip


Re-initiate on ajax-load

I'm loading content dynamically using a XHR-request, containing some picture-elements. How can I re-initiate picturefill to handle these?

Can we re-open this? I too am dynamically loading in images and have found that on IE10 if there is more than 40 images the browser crashes!!


Fix not changing tab after editing successfully

Codecov Report
Base: 61.48% // Head: 61.48% // No change to project coverage :thumbsup:

Coverage data is based on head (fb13b48) compared to base (8489a0f).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #273   +/-   ##
=========================================
  Coverage     61.48%   61.48%
  Complexity      822      822
=========================================
  Files           155      155
  Lines          3204     3204
  Branches        408      408
=========================================
  Hits           1970     1970
  Misses         1064     1064
  Partials        170      170

Impacted Files
Coverage Δ

...commands/consultation/EditConsultationCommand.java
91.78% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Element state / cache key handling

See original issue on GitLab
In GitLab by [Gitlab user @juergbi] on Dec 19, 2017, 10:30
Cache keys are currently calculated on demand as they cannot always be calculated early on. E.g., tracking affects cache keys and calculating strong cache keys with a non-strict build plan requires extraction of metadata from possibly downloaded dependencies.
There is a caching mechanism for the calculated cache keys, however, there are still situations where the same cache key is calculated multiple times. This can incur a performance overhead.
Related issues #149 and #167.

In GitLab by [Gitlab user @juergbi] on Jan 8, 2018, 18:41
mentioned in commit 5513634d176dfe83fee7ea84a88cb1fc3f987101

In GitLab by [Gitlab user @juergbi] on Jan 10, 2018, 15:50
mentioned in commit eb0e18e751edff3ab8cca75494b08ed3ec90d61f

In GitLab by [Gitlab user @juergbi] on Jan 10, 2018, 16:00
mentioned in commit 6172fb9cad085b6e531cb222c5e5f0e912afea38

In GitLab by [Gitlab user @juergbi] on Jan 11, 2018, 09:40
mentioned in commit c05e85bfb86634361d9c606f731ac0e977651229

In GitLab by [Gitlab user @juergbi] on Jan 11, 2018, 09:41
mentioned in commit 93099418ebec58ddeeacb5bc3bc40a584831d9c4

In GitLab by [Gitlab user @juergbi] on Jan 12, 2018, 05:07
mentioned in commit 64c9803e4364d9b5be341e5e70868d5ee525c22f

In GitLab by [Gitlab user @juergbi] on Jan 12, 2018, 10:24
mentioned in commit bc492fa8f3973367c3817c84064629f3975b22bd

In GitLab by [Gitlab user @juergbi] on Jan 12, 2018, 11:52
closed via commit bc492fa8f3973367c3817c84064629f3975b22bd

In GitLab by [Gitlab user @juergbi] on Jan 12, 2018, 11:52
closed via merge request !215

In GitLab by [Gitlab user @juergbi] on Jan 25, 2018, 14:11
mentioned in commit 6446a5912336c2bfa5dc254cbb24666d0b5af543


Add --blob-type for az storage copy command

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Add --blob-type for az storage copy command
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

For traige.

Fixed in PR #10535


use debug version of C runtime with MSVC

https://docs.microsoft.com/en-us/cpp/build/reference/md-mt-ld-use-run-time-library
I encountered a link error when linking a Rust library with some C++ built by cc with other C++ code built by CMake because cc wasn't using the debug version of the C runtime.

On a tangential note, there is a case to be made that when it comes to a library, /MT /Zl flags would be most appropriate. Why is that? Well, what's the difference between /MT and /MD when it comes to the .obj file? Let's say you make a call to a CRT subroutine, for example malloc. If compiled with /MD, the resulting .obj file will have a reference to __imp_malloc, and if compiled with /MT to malloc. Another difference would be a link directive that reflects the chosen option, but you can omit it with /Zl. Now the fun fact. You can link maloc with either CRT, be it static or dynamic, but you can link __imp_malloc only with dynamic. Hence an object file, or collection thereof, compiled with /MT /Zl effectively allows you to leave the decision about which specific CRT library, be it static, dynamic, debug or not, the final application will be linked with to somebody else. To summarize, consider cc.static_crt(true).flag("/Zl");.
Since cc-rs produces specifically libraries for Rust to link with, one can even argue that cc-rs should use /MT /Zl unconditionally. Though I'm not sure how it would play out if you use ATL or MFC... Well, /Zl omits CRT-related link directives, but not others, so it should work...

leave the decision about which specific CRT library, be it static, dynamic, debug or not, the final application executable object will be linked with to somebody else

That would be nice if that works. If you want to experiment with that, go for it. In the meantime this simple change solves my problem.

It does work for me. And if it doesn't for you, I'd like to hear about it. Would you care to provide more details about the failure? At least who does the final linking, Rust or cl?

I'm not clear what you're asking. I have not tested using /MT Zl as you proposed. The problem that led to me making this PR is that I ran a debug build with CMake in a project using Corrosion to invoke Cargo to build a Rust staticlib and link it with a C++ executable. That failed to link on Windows.

I have not tested using /MT /Zl as you proposed.

Then why did you write "That would be nice if that works"? I mean it sounded like it didn't work for you. So I had to ask. It's ok if you don't want to entertain the idea, but then don't make it sound like it didn't work :-)

Ping. I stumbled over this bug again trying to setup a Windows development environment.

Hm, while this is certainly the easiest way to fix your specific issue, I'm not sure that this is a good general solution.
This PR may be incorrect for many other use cases. Currently rustc (via libc) hard codes non-debug CRT for all Rust compiled code so it may cause conflicts depending on how it's used.
While I absolutely want to see a solution to the problems with linking the right CRT, I think there is perhaps some design work that needs to be done first.

Since #723 has been closed can this straightforward bug fix be merged?

Just in case for reference. So that there is understanding of the scope. Since rustc effectively overrides references to C RT left by /M* flag, in cases when C++ is involved, the suggested modification will [currently] result in linking the debug version of C++ RT and non-debug version of C RT. More specifically, when rustc is linking the final executable. Question is if it's a sustainable configuration. One needs to weigh the impact on an average user to figure out if it would qualify as a non-breaking change. In the context one can recognize that a staticlib crate-type provider can solve the problem in the crate's build.rs, by [conditionally] invoking .define( _DEBUG, None) method. In other words, it's not like it's impossible to solve the problem(*) as it stands now. (One can even wonder if crate's build.rs would be a better spot...)
(*) The C++ problem more specifically. As for C-only, I [for one] would still recommend the -MT -Zl approach ;-)

straightforward bug fix

I don't think this is a "straight forward bug fix". To be honest, I'm even more nervous about this now than I used to be. Changing the implicit behaviour of cc-rs has been causing issues with various build systems in recent releases.
I do think there should be a way to use debug CRT versions, etc. But this should not be tied to an existing option. Solving one use case does not necessarily justify breaking others. If we can have a solution that doesn't break others then we should do that instead.

The issue is not vague, it's specific. rustc hardcodes non-debug CRT libraries. cc-rs is primarily used to compile static libraries for use in applications compiled by rustc. There are various potential fixes to this.

rustc could be changed so that it does not hard code its CRT library (or provides an option to override it).
cc-rs could provide a way to force overriding of the CRT library used (rather than doing so implicitly).

cc-rs could provide a way to force overriding of the CRT library used (rather than doing so implicitly).

It's actually possible to override rustc's choice with println!("cargo:rustc-link-lib=msvcrtd");. Well, it's not like it makes rustc give up the attempt to link with non-debug version, it's simply so that rustc-link-lib-s are passed first on the command line to the vendor linker, and that's how they take precedence. Just in case, I would not advocate for having cc-rs playing this game.

Hi I'm experimenting rust integration with c++ on windows with msvc, and I find it annoying that the out of the box experience doesn't work to build code in Debug that is built by CMake when some code is also build by cc using the wrong crt library.
From my limited knownledge this PR would be the best to fix the issue implictly for everyone. It only affect the code in Debug mode, so it shouldn't break any behavior in production code.
Another idea would be to add a feature crt-debug to control if -MTd or -MDd is used.

See https://github.com/rust-lang/rust/issues/39016. I have just written a comment outlining a possible way forward and asking rustc compiler if this would be the approach they want.


df-288: This pr converts double types to Double types

This PR aims to ease the conversion issues by making all doubles Doubles. The reason is that a lot of the types in 1x11 are Double but the values in 20 were double which did not allow for null and therefore threw null pointer exceptions.

Thar she blows!
I saw that you uppercased the word "double" in many test XML files. Are you concerned that this will cause issues with incoming WITSML requests that won't have a capitalized "Double"?

You are correct sir…I will fix that.

On Feb 26, 2019, at 9:06 AM, Randy<EMAIL_ADDRESS>wrote:
Thar she blows!
I saw that you uppercased the word "double" in many test XML files. Are you concerned that this will cause issues with incoming WITSML requests that won't have a capitalized "Double"?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/hashmapinc/WitsmlObjectsLibrary/pull/21#issuecomment-467473723, or mute the thread https://github.com/notifications/unsubscribe-auth/AFphD5IaF7gdz2alxi8Y-iitCeDtosgAks5vRU1fgaJpZM4bRLqD.

Just to check, I did a source check for any instances of == comparisons, and luckily they are all involved in null checks (weird that == works with null).
so, great news!


initial drop

@coreydaley FYI

@adambkaplan fyi

@gabemontero OWNERS file is in, looks like we need to set up prow, in the same fashion that we do for source-to-image.

@gabemontero OWNERS file is in, looks like we need to set up prow, in the same fashion that we do for source-to-image.

ah yeah makes sense @adambkaplan
@coreydaley can you include that as part of your BUILD-55 activities?

@gabemontero OWNERS file is in, looks like we need to set up prow, in the same fashion that we do for source-to-image.

ah yeah makes sense @adambkaplan
@coreydaley can you include that as part of your BUILD-55 activities?

Yes, I plan on working on the prow job today

@gabemontero Could you split out the vendor directory /go.mod/go.sum into it's own commit also?

Can we get a make verify also? maybe just throw in something from another repo

Please amend the "initial drop" commit message to contain a descriptive body message that provides context for this initial code base (ex - based on CSI example, link the PoC in your github account, etc.)

No free pass even with the initial seeding ...... ahhhhhh .... ok/jk, will do ;-)

I can green-button merge this if necessary.

yeah per @coreydaley 's comment in his openshift/release PR we have a bit of a chicken and egg thing going.  It would be good to see rehearsal jobs passing there.  So when I've addressed everyone's comments let's green button it.

@gabemontero Could you split out the vendor directory /go.mod/go.sum into it's own commit also?

No free pass even with the initial seeding ...... ahhhhhh .... ok/jk, will do ;-)

Can we get a make verify also? maybe just throw in something from another repo

I'll move the go vet into a make verify directive for now.  We can evolve it, pulling in stuff done in other repos, over time.  Certainly feel to tinker with it more as part of BUILD-55

Can we get a make verify also? maybe just throw in something from another repo

I'll move the go vet into a make verify directive for now. We can evolve it, pulling in stuff done in other repos, over time. Certainly feel to tinker with it more as part of BUILD-55

I'll add a gofmt as well

ok @coreydaley @adambkaplan updates stemming from review comments pushed

/lgtm

No free pass even with the initial seeding ...... ahhhhhh .... ok/jk, will do ;-)

Obligatory xkcd: https://xkcd.com/1296/

No free pass even with the initial seeding ...... ahhhhhh .... ok/jk, will do ;-)

Obligatory xkcd: https://xkcd.com/1296/

LOL ... very well done

Can we green button merge this so that we can test the new jobs?

Let's see
/approve


scanner: provide device name

This PR uses the http interface at 8008:setup/eureka_info to pick out the device name, if a device has been found via scanning.
$ go run .  scan --cidr <IP_ADDRESS>/24
Scanning...  scanned 0, current <IP_ADDRESS>
  - 'Office speaker' at <IP_ADDRESS>:8009
Scanned 256 uris in 1.609840334s

Also removes some leftovers from a previous PR.

Thanks for this @holiman!


fix(clion): Add Xcode information to Cpp compiler wrapper

Checklist

[ ] I have filed an issue about this change and discussed potential changes with the maintainers.
[X] I have received the approval from the maintainers to make this change.
[X] This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.
Discussion thread for this change
Issue number: N/A (sorry, I didn't open one).
Description of this change
In CLion, the Bazel plugin has to pass a C compiler to the rest of the CLion machinery.
Currently, on macOS, if using the standard cc toolchains, it does so by wrapping the clang_wrapper.sh we get from each toolchain implementation. On macOS, that wrapper expects the environment variables DEVELOPER_DIR and SDKROOT to be set. In Bazel, they are set on every action. Currently, in CLion, they are not, which makes a lot of the smarts of CLion inaccessible to macOS users.
This PR sets those variables by mirroring Bazel's logic:

When resolving Compiler Settings, cquery for the xcode version in @bazel_tools//tools/osx:current_xcode_config.
Then, use the xcode locator that Bazel uses to translate the DEVELOPER_DIR that corresponds with that version. (This is where Bazel does it).
The rest is just piping those values so that they end up as environment variables in the compiler wrapper.

Note that we could have gotten the xcode version from the aspect, and saved ourselves a potentially expensive cquery. But, due to this issue, we cannot forward those values to the rest of the build.

ECD 27 April 2023 to be merged as per @tpasternak


Microsoft.Automation automationAccounts/schedules  mistake in documentation

I was trying to find repo for runbook schedules but could not find it but I definitely found a mistake in your official documentation
Microsoft.Automation automationAccounts/schedules
https://docs.microsoft.com/en-us/azure/templates/microsoft.automation/automationaccounts/schedules?tabs=json
{
"name": "string",
"type": "Microsoft.Automation/automationAccounts/schedules",
"apiVersion": "2020-01-13-preview",
"properties": {
"description": "string",
"startTime": "string",
"expiryTime": "string",
"interval": {},
"frequency": "string",
"timeZone": "string",
"advancedSchedule": {
"weekDays": [
"string"
],
"monthDays": [
"integer"
],
"monthlyOccurrences": [
{
"occurrence": "integer",
"day": "string"
}
]
}
}
}
property interval is defined as an object but it is not. It is an integer.

interval
object
No
Gets or sets the interval of the schedule.

Also this property is required if you specify frequency of the job as recurring which is another mistake. This is very confusing and needs to be changed.

Hello @VladimirtheGreatest Thanks for the feedback!
I have assigned the issue to the content author for further review and update the doc as appropriate.

This reference content has been updated and now shows the correct type.
#please-close


add support for \item and {itemize}

Is your feature request related to a problem? Please describe.
AFAIK there is no way to render LaTeX with {itemize}, e.g.
\begin{itemize}
\item List entries start with the \verb|\item| command.
\item Individual entries are indicated with a black dot, a so-called bullet.
\item The text in the entries may be of any length.
\end{itemize}
Describe the solution you'd like:
A simple way to do this
Link to or name of a (La)TeX package that provides the same feature:
Overleaf does this, not sure what you meant here
Describe alternatives you've considered:
A clear and concise description of any alternative solutions or features you've considered.
Additional context:
Add any other context or screenshots about the feature request here.

Katex is math typesetting. It provides a Math-Environment using $...$ and $$...$$ like LaTeX, or at least major functionalities of it. It is not meant for parsing LaTeX.


Fix actions, default estimatefee rpc call to return 1, .com domain

Noting that we also have a review by s15a. Proceeding with the merge.


[SPARK-40727][INFRA] Add merge_spark_docker_pr.py

What changes were proposed in this pull request?
This patch add the merge_spark_docker_pr.py to help to merge commits.
The script is from https://github.com/apache/spark/blob/ef837ca71020950b841f9891c70dc4b29d968bf1/dev/merge_spark_pr.py
And change spark to spark-docker: https://github.com/apache/spark-docker/commit/e4107a74d348656041612ff68a647c6051894240
Why are the changes needed?
Help to merge spark-docker commits.
Does this PR introduce any user-facing change?
No, dev only
How was this patch tested?
will merge it by using itself

cc @HyukjinKwon @zhengruifeng

This patch is merged by it self
$ ./merge_spark_docker_pr.py
git rev-parse --abbrev-ref HEAD
Which pull request would you like to merge? (e.g. 34): 1

=== Pull Request #1 ===
title	[SPARK-40727][INFRA] Add merge_spark_docker_pr.py
source	Yikun/merge_script
target	master
url	https://api.github.com/repos/apache/spark-docker/pulls/1

Proceed with merging pull request #1? (y/n): y
git fetch apache-github pull/1/head:PR_TOOL_MERGE_PR_1
From github.com:apache/spark-docker
 * [new ref]         refs/pull/1/head -> PR_TOOL_MERGE_PR_1
git fetch apache master:PR_TOOL_MERGE_PR_1_MASTER
From github.com:apache/spark-docker
 * [new branch]      master     -> PR_TOOL_MERGE_PR_1_MASTER
 * [new branch]      master     -> apache/master
git checkout PR_TOOL_MERGE_PR_1_MASTER
Switched to branch 'PR_TOOL_MERGE_PR_1_MASTER'
['git', 'merge', 'PR_TOOL_MERGE_PR_1', '--squash']
['git', 'log', 'HEAD..PR_TOOL_MERGE_PR_1', '--pretty=format:%an <%ae>', '--reverse']
Enter primary author in the format of "name <email>" [Yikun Jiang<EMAIL_ADDRESS>git config --get user.name
git config --get user.email
['git', 'commit', '--author="Yikun Jiang<EMAIL_ADDRESS>'-m', '[SPARK-40727][INFRA] Add merge_spark_docker_pr.py', '-m', '### What changes were proposed in this pull request?\r\nThis patch add the merge_spark_docker_pr.py to help to merge `spark-docker` commits and resolve spark JIRA issue.\r\n\r\nThe script is from https://github.com/apache/spark/blob/ef837ca71020950b841f9891c70dc4b29d968bf1/dev/merge_spark_pr.py\r\n\r\nAnd change `spark` to `spark-docker`: https://github.com/apache/spark-docker/commit/e4107a74d348656041612ff68a647c6051894240\r\n\r\n### Why are the changes needed?\r\nHelp to merge spark-docker commits.\r\n\r\n\r\n### Does this PR introduce _any_ user-facing change?\r\nNo, dev only\r\n\r\n\r\n### How was this patch tested?\r\nwill merge it by using itself', '-m', 'Closes #1 from Yikun/merge_script.', '-m', 'Authored-by: Yikun Jiang<EMAIL_ADDRESS>Yikun Jiang<EMAIL_ADDRESS>
Merge complete (local ref PR_TOOL_MERGE_PR_1_MASTER). Push to apache? (y/n): y
git push apache PR_TOOL_MERGE_PR_1_MASTER:master
Enumerating objects: 4, done.
Counting objects: 100% (4/4), done.
Delta compression using up to 8 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 7.63 KiB | 3.82 MiB/s, done.
Total 3 (delta 0), reused 0 (delta 0), pack-reused 0
To github.com:apache/spark-docker.git
   c5b015a..fa2d1a5  PR_TOOL_MERGE_PR_1_MASTER -> master
git rev-parse PR_TOOL_MERGE_PR_1_MASTER
Restoring head pointer to merge_script
git checkout merge_script
Switched to branch 'merge_script'
git branch
Deleting local branch PR_TOOL_MERGE_PR_1
git branch -D PR_TOOL_MERGE_PR_1
Deleting local branch PR_TOOL_MERGE_PR_1_MASTER
git branch -D PR_TOOL_MERGE_PR_1_MASTER
Pull request #1 merged!
Merge hash: fa2d1a59

Would you like to update an associated JIRA? (y/n): y
Enter a JIRA id [SPARK-40727]:
=== JIRA SPARK-40727 ===
summary		Add merge_spark_docker_pr.py to help merge commit
assignee	Yikun Jiang
status		Reopened
url		https://issues.apache.org/jira/browse/SPARK-40727

Enter comma-separated fix version(s) [3.4.0]:
Successfully resolved SPARK-40727 with fixVersions=['3.4.0']!

JIRA https://issues.apache.org/jira/browse/SPARK-40727 are be closed as expected.


Force skip validation option

Added -f / --force option

In some case the jwt token may not have typ specified, so the validator prevent the script from starting

Added Missing token error message when token is not provided
Changed the Unsupported typ error message to display the acual token typ instead of alg

Hey sorry for the very long delay in getting back to you. I had missed this PR somehow!
I like this feature and I'd be more than happy to get it integrated. Would you have some time to resolve the conflicts?
thanks

Thank you so much for this contribution ❤

Hi ! No problem :)


Exception: Cannot set property 'data' of undefined

Just got bug report from production server:
TypeError: Cannot set property 'data' of undefined at https://github.com/pqina/filepond-plugin-file-encode/blob/36b9cfb8705dacfc5f7b7100593c0b43c714d783/src/js/index.js#L50
So I would suggest to add a check that base64Cache[item.id] is not empty before trying to assign value to base64Cache[item.id].data.

Looks like the item was removed while the file was being encoded. PR is welcome.

Just got bug report from production server:
TypeError: Cannot set property 'data' of undefined at
https://github.com/pqina/filepond-plugin-file-encode/blob/36b9cfb8705dacfc5f7b7100593c0b43c714d783/src/js/index.js#L50
So I would suggest to add a check that base64Cache[item.id] is not empty before trying to assign value to base64Cache[item.id].data.

How did you resolve this issue. I am unable to get over it


5.2: BingMapTileSource displays Australian tiles for UK lat/long

In the current (5.2) release of osmdroid, I can display maps as expected using the default tile source, or others such as the USGS Topo source. However, if I switch to the thirdparty/BingMapTileSource, it displays maps centered in New South Wales, Australia for lat/long coordinates in the UK.
Edited to add: this appears to be a race condition, in that if the map location and overlays are set before initMetaData is called, they are incorrectly positioned. Unfortunately there is no way to invoke it directly, so Activities that build up a map view before the map is displayed will show the wrong location?
In addition, the maximum zoom level returned for BingMaps seems to exceed the available tile sources for aerial maps by quite a way - ie. if you zoom to maximum, you get 'no tile' images for the three most detailed levels at my current location.
I'm creating the BinMapTileSource as indicated in the Wiki:
            BingMapTileSource.retrieveBingKey(context);
            BingMapTileSource bing = new BingMapTileSource(null);
            bing.setStyle(BingMapTileSource.IMAGERYSET_AERIALWITHLABELS);

Horrible work around to invoke initMetaData:
            BingMapTileSource bing = new BingMapTileSource(null) {
                @Override
                public String toString() {
                    getBaseUrl();
                    return super.toString();
                }
            };
            bing.setStyle(BingMapTileSource.IMAGERYSET_AERIALWITHLABELS);
            bing.toString();

Does this also imply that BingMaps will not work in offline mode, as it won't be able to run the initMetaData request when displaying tiles from an offline cache?

Ok I'll take a look at it
On Aug 25, 2016 8:02 AM, "atoone"<EMAIL_ADDRESS>wrote:

In the current (5.2) release of osmdroid, I can display maps as expected
using the default tile source, or others such as the USGS Topo source.
However, if I switch to the thirdparty/BingMapTileSource, it displays maps
centered in New South Wales, Australia for lat/long coordinates in the UK.
In addition, the maximum zoom level returned for BingMaps seems to exceed
the available tile sources for aerial maps by quite a way - ie. if you zoom
to maximum, you get 'no tile' images for the three most detailed levels at
my current location.
I'm creating the BinMapTileSource as indicated in the Wiki:
        BingMapTileSource.retrieveBingKey(context);
        BingMapTileSource bing = new BingMapTileSource(null);
        bing.setStyle(BingMapTileSource.IMAGERYSET_AERIALWITHLABELS);

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/383, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB4kGQyMUD949mqYb8uJgfaJzVfdExohks5qjYQpgaJpZM4Js_fW
.

I can make  initMetaData public if that will help you. I've also set the max zoom is 19, which does exist in certain areas.
Is your issue with mismatched tiles at a specific zoom level?

Also do you have a lat/lon and zoom level to recreate the problem? it's looking ok over here

@atoone can you give me more specifics? What coordinates was the issue at? what zoom level? If it was greater than zoom 19, the issue is probably the overflow issue #329. In which case, the only solution is to reduce the max zoom level to 19.

Ah, that may well be the problem.
I've heavily refactored the code I was using, which means I don't have a
convenient test case - but on the other hand I'm not experiencing odd
results any more. I believe it was zooming in to maximum during map loading
(I'm loading a flight path progressively, so the initial data covers a very
small distance, which would result in maximum zoom). Now however I load the
data asynchronously and leave the map zoom at 'global', zoomed out at
default. Once the data is loaded, things are zoomed to the extent of the
flight path, which is typically within the maximum zoom of the various
providers.
The location I'm testing with is Cambridge, UK, so 0 degrees long, 52 lat
more or less. It was coming out as New South Wales under the original code.
I'm not totally clear what the metadata load is needed for - what happens
if you're looking at offline, cached tiles?
Andy
On 28 August 2016 at 15:15, spyhunter99<EMAIL_ADDRESS>wrote:

@atoone https://github.com/atoone can you give me more specifics? What
coordinates was the issue at? what zoom level? If it was greater than zoom
19, the issue is probably the overflow issue #329
https://github.com/osmdroid/osmdroid/issues/329. In which case, the
only solution is to reduce the max zoom level to 19.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/383#issuecomment-242977187,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFH3TEl1zOW4YDNddM5KSOTZ8AVtLshzks5qkZgSgaJpZM4Js_fW
.

Once the tile is downloaded, it's stored (cached) in osmdroid's format, metadata isn't needed in that case.  Looks like the metadata thing is some kind of authentication mechanism, min/max zooms, pixel sizes, etc

reopen if you run into any more issues with this

Many thanks for your help, sorry for pointing in the wrong direction
initially.
Andy
On 28 August 2016 at 19:51, spyhunter99<EMAIL_ADDRESS>wrote:

reopen if you run into any more issues with this
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/383#issuecomment-242992100,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFH3TL4VgpBP9T9JaIxWEzVkhrN3fDphks5qkdi9gaJpZM4Js_fW
.


Error while generating bindings for bellsoft-liberia jdk

Command : bt dependency-mapping -b paketo-buildpacks/bellsoft-liberica
Env: WSL2 ubuntu 20.04.03 LTS
Error:
thread '<unnamed>' panicked at 'Download of https://download.bell-sw.com/vm/22.1.0/bellsoft-liberica-vm-core-openjdk17.0.3+7-22.1.0+1-linux-amd64.tar.gz failed with error copy failed', src/deps.rs:109:33
stack backtrace:
   0: rust_begin_unwind
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/std/src/panicking.rs:498:5
   1: core::panicking::panic_fmt
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/core/src/panicking.rs:107:14
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread '<unnamed>' panicked at 'unable to get lock: PoisonError { .. }', src/deps.rs:106:45
stack backtrace:
   0: rust_begin_unwind
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/std/src/panicking.rs:498:5
   1: core::panicking::panic_fmt
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/core/src/panicking.rs:107:14
   2: core::result::unwrap_failed
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/core/src/result.rs:1613:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread '<unnamed>' panicked at 'unable to get lock: PoisonError { .. }', src/deps.rs:106:45
stack backtrace:
   0: rust_begin_unwind
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/std/src/panicking.rs:498:5
   1: core::panicking::panic_fmt
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/core/src/panicking.rs:107:14
   2: core::result::unwrap_failed
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/core/src/result.rs:1613:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I have had this happen once or twice. It has been intermittent though and re-running the command has resolved the issue for me.
The with error copy failed happens when reading from the response from the server, so it could be networking related to an issue with downloading that particular file. I know that the file referenced in your failure message is the largest file in one of the paketo buildpacks, weighing in around 500M.
At any rate:

Try again a few times
Try downloading with curl or your browser, make sure that works & see what kind of download speeds you're getting
I'll keep this open as I can try to improve the error messages being generated here, perhaps get something more meaningful to show up.

I have a similar issue, it sort of looks like something is timing out when downloading a big binary
bt dependency-mapping -b paketo-buildpacks/bellsoft-liberica
thread '<unnamed>' panicked at 'Download of https://github.com/bell-sw/Liberica/releases/download/19.0.1+11/bellsoft-jdk19.0.1+11-linux-amd64.tar.gz failed with error copy failed', src/deps.rs:123:33
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' panicked at 'unable to get lock: PoisonError { .. }', src/deps.rs:120:45
thread '<unnamed>' panicked at 'unable to get lock: PoisonError { .. }', src/deps.rs:120:45
Error: thread 'thread panic: Download of https://github.com/bell-sw/Liberica/releases/download/19.0.1+11/bellsoft-jdk19.0.1+11-linux-amd64.tar.gz failed with error copy failed<unnamed>
' panicked at 'unable to get lock: PoisonError { .. }', src/deps.rs:120:45

bt manages to download about 170M of the 205M file before error
-rw-rw-r-- 1 user user 170926080 tammi   5 14:09 bellsoft-jdk19.0.1+11-linux-amd64.tar.gz
If I download the file with curl, it works fine
curl -L https://github.com/bell-sw/Liberica/releases/download/19.0.1+11/bellsoft-jdk19.0.1+11-linux-amd64.tar.gz --output testfile
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  205M  100  205M    0     0  5804k      0  0:00:36  0:00:36 --:--:-- 5973k

@jansu76 is this consistently happening for you? You can try adjusting BT_CONN_TIMEOUT and BT_REQ_TIMEOUT.
These are environment variables that the app will read and use to adjust the client's TCP connection timeout and request timeout. I suspect it is the latter that's causing issues.
Please try a large value there and see if that helps. If so, I can adjust the client settings (probably should set timeout_read and timeout_write instead).

Thanks, I will try that and report findings, was not aware of those timeout variables.

Setting BT_REQ_TIMEOUT fixed the issue, super!

Thanks for the feedback. That's my fault I should have documented those :) I'll get that fixed too.


Make kubelet & docker service restart automatically when it crashes on Windows

Is this a request for help?:
FEATURE REQUEST
Is this an ISSUE or FEATURE REQUEST? (choose one):

What version of acs-engine?:
v0.21.2

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes
What happened:
I found kubelet on Windows crashes due to OOM, while after that kubelet won't restart automatcially even there is memory later (while on Linux node, it does). Could we configure kubelet and docker service restart if there is failure like what it does on Linux node. Below are the manual step to restart kubelet:
start-service docker
start-service kubeproxy
start-service kubelet

What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
@PatrickLang @feiskyer

+1

kubelet and kubeproxy are registered via nssm.exe and as far as I can see are already configured to restart automatically.

Hmm, I logged into a node and didn't see a FailureActions registry value on the kubelet service:
get-itemproperty hklm:\system\currentcontrolset\services\kubelet

Type                             : 16
Start                            : 2
ErrorControl                     : 1
ImagePath                        : c:\k\nssm.exe
DisplayName                      : Kubelet
ObjectName                       : LocalSystem
DelayedAutostart                 : 0
FailureActionsOnNonCrashFailures : 1
Description                      : Kubelet
PSPath                           : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\system\currentcontrolset\serv
                                   ices\kubelet
PSParentPath                     : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\system\currentcontrolset\serv
                                   ices
PSChildName                      : kubelet
PSDrive                          : HKLM
PSProvider                       : Microsoft.PowerShell.Core\Registry

I ran sc.exe failure "kubelet" actions= restart/60000/restart/60000/restart/60000 reset= 86400 to set it, and now I see that in the registry.
get-itemproperty hklm:\system\currentcontrolset\services\kubelet

Type                             : 16
Start                            : 2
ErrorControl                     : 1
ImagePath                        : c:\k\nssm.exe
DisplayName                      : Kubelet
ObjectName                       : LocalSystem
DelayedAutostart                 : 0
FailureActionsOnNonCrashFailures : 1
Description                      : Kubelet
FailureActions                   : {128, 81, 1, 0...}
PSPath                           : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\system\currentcontrolset\serv
                                   ices\kubelet
PSParentPath                     : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\system\currentcontrolset\serv
                                   ices
PSChildName                      : kubelet
PSDrive                          : HKLM
PSProvider                       : Microsoft.PowerShell.Core\Registry

sc.exe failure "kubelet" actions= restart/60000/restart/60000/restart/60000 reset= 86400 means
restart after 60000ms (1 minute) for the first, second, and third failures. Reset the counter after 86400 seconds (1 day)

@PatrickLang set FailureActions is not enough, I also found kubeproxy and docker is not running after OOM happens, shall we set same FailureActions for kubeproxy and docker? And how could I get original FailureActions of docker, it's already set while I found docker is not started when it hit OOM, see below info:
PS C:\k> get-itemproperty hklm:\system\currentcontrolset\services\kubeproxy
Type                             : 16
Start                            : 2
ErrorControl                     : 1
ImagePath                        : c:\k\nssm.exe
DisplayName                      : Kubeproxy
ObjectName                       : LocalSystem
DelayedAutostart                 : 0
FailureActionsOnNonCrashFailures : 1
DependOnService                  : {Kubelet}
Description                      : Kubeproxy
PSPath                           : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\system\currentcontrolset\serv
                                   ices\kubeproxy
PSParentPath                     : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\system\currentcontrolset\serv
                                   ices
PSChildName                      : kubeproxy
PSDrive                          : HKLM
PSProvider                       : Microsoft.PowerShell.Core\Registry

PS C:\k> get-itemproperty hklm:\system\currentcontrolset\services\docker
Type           : 16
Start          : 2
ErrorControl   : 1
ImagePath      : "C:\Program Files\Docker\dockerd.exe" --run-service
ObjectName     : LocalSystem
FailureActions : {10, 0, 0, 0...}
PSPath         : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\system\currentcontrolset\services\docker
PSParentPath   : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\system\currentcontrolset\services
PSChildName    : docker
PSDrive        : HKLM
PSProvider     : Microsoft.PowerShell.Core\Registry


Remove copied SINR code from the respository

As a developer, I need our application to be easy to maintain, so that I have time to work on new features and not just repository maintenance. Having copied code from a different repository makes a project much more difficult to maintain for these reasons:

It makes reviewing code and comparing code difficult, because it is difficult to tell which changes are from which repository.
It creates additional maintenance overhead. Every time the code in the copied repo is changed on git, I need to first find out about it, then recopy the code to my repository.

There are two options here:
Option 1) Add the SINR code as a git submodule (see https://www.freecodecamp.org/news/how-to-use-git-submodules/)
Option 2) Convert the SINR code to a proper python package that can be installed via the requirements.txt file (note that it doesn't need to be pushed to pypi, see https://pip.pypa.io/en/stable/topics/vcs-support/)

linked to prototype pr: https://github.com/UMassCDS/ds4cg2024-inaturalist/pull/25/files#diff-d1bfd7459bf41ce7af92b21f4e8981dcea885fec67097986ba7aaf58d1b49916


Request for Enhancing Cropping Usability

I am a loyal user of this app, but I have just one complaint: the cropping operation is difficult to use. Therefore, I would like to request improvements to make cropping more user-friendly.
Request:

Set the initial position of the cropping window to match the original size of the image. Currently, the initial position of the cropping window is slightly enlarged from the original image, so it needs to be adjusted.

Fix the image by preventing it from moving unintentionally. When the image moves, it becomes difficult to specify the cropping position accurately.

Limit the cropping window to the image boundaries to prevent it from extending beyond the image area. When the cropping window is extended beyond the image boundaries, the image automatically enlarges based on the cropping window, causing the cropping position to shift.

If I were to provide an example, something like LLCrop would be ideal.
Also, I'm aware that the existing cropping feature relies on external libraries. Therefore, I would like to request the addition of a new feature focused solely on pure cropping. How about something like "Quick Crop"? The name is up to you. I would like the new feature to prioritize ease of use, leaving aspects like aspect ratio and crop mask changes to the existing cropping tool. I understand that this request may seem ambitious, but I genuinely appreciate your consideration.

I think this could be acieved using this lib
https://github.com/Yalantis/uCrop
it also have native llcrop, but only for png and jpg
i will add this as second option in crop

this implemented somewhat, now cropper much more useable


Support for mapping update for the replication store system index

Description
Support for mapping update for the replication store system index
Issues Resolved
N/A
Testing
./gradlew clean release

Check List

[x] Commits are signed per the DCO using --signoff

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

It would be great to include tests to confirm schema version can be safely updated. Can you assess if it is introduce able now or requires significant plumbing work?

Added issue to track UTs: https://github.com/opensearch-project/cross-cluster-replication/issues/113


[Feature]: Does it now support Nuxt3?

Describe the feature
Nuxt3 module is provided.
Additional information

[ ] I intend to submit a PR for this feature.
[ ] I have already implemented and/or tested this feature.

This still is super early dev... and the way it will works doesn't required Nuxt3 module. 😁

Then how do I use shacn-vue in Nuxt3?

I can't wait to use it 🤗

@evanlong0926 check out how to use vue plugins in nuxt: https://nuxt.com/docs/guide/directory-structure/plugins#vue-plugins

@evanlong0926 check out how to use vue plugins in nuxt: https://nuxt.com/docs/guide/directory-structure/plugins#vue-plugins

shaCN-vue Is a Vue plugin for Nuxt3?

@evanlong0926  please have a look on the concept of shadcn.
Essentially shadcn-vue is just a collections of reusable components, which you can copy and paste into Nuxt, which is support by default thanks to radix-vue Nuxt modules.

@zernonia is Right, sorry for my false response. Thought you meant something else.

@evanlong0926 please have a look on the concept of shadcn.
Essentially shadcn-vue is just a collections of reusable components, which you can copy and paste into Nuxt, which is support by default thanks to radix-vue Nuxt modules.

Maybe this needs a documentation lol.

Please be patience @evanlong0926 . We are working hard on it.. and will announce it when it is ready ya

what is currently the preferred way to make it work with nuxt ? just running the cli ?

Please be patient @evanlong0926 . We are working hard on it.. and will announce it when it is ready ya

its ready?

its ready? its ready? its ready? its ready?


onthespot: Fix build issue; python3Packages.pyogg: 0.6.9a1 > 0.6.14a1

Description of changes
Fixes https://github.com/NixOS/nixpkgs/issues/299640
Supersede https://github.com/NixOS/nixpkgs/pull/299731
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

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

10 packages built:

onthespot
onthespot.dist
python311Packages.librespot
python311Packages.librespot.dist
python311Packages.pyogg
python311Packages.pyogg.dist
python312Packages.librespot
python312Packages.librespot.dist
python312Packages.pyogg
python312Packages.pyogg.dist