Domain/ComputerName -2016281112 (Remediation failed)

After applying this MDM policy to change the workstations name, the process is completed successfully (checked and the machine name is changed), but I get the "-2016281112 (Remediation failed)" error.
Using Windows 10 1803 and Windows 10 1809.

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

ID: 309bae29-c769-5051-6c3f-aebeb455cd34
Version Independent ID: bbdfad82-025e-8aee-b3fc-bcfb8b110674
Content: Accounts CSP
Content Source: windows/client-management/mdm/accounts-csp.md
Product: w10
GitHub Login: @MariciaAlforque
Microsoft Alias: maricia

Yep, i have this same issue. I'm using this to create new user account, set password and add to local admin groups.

@xonaecom and @dzejzipl Please show me the logs from Settings > Accounts > Work or school account > Export your management logs and the syncml you sent to the device. I can use that information to set up a bug report for the dev team so they can address this issue as soon as possible.

@xonaecom @dzejzipl I'm currently consulting the team regarding how best to address this, as this is the first time this issue has come up. I will let you know when they reply.

Hello @Heidilohr ,
Because both tickets were merged, I'm gonna put both settings in here.
How can I share with you the exported logs? The logs have client info that I don't want to put here in the wild. :)
Computer Name change settings:
OMA-URI used: ./Device/Vendor/MSFT/Accounts/Domain/ComputerName
Data Type: String
Value: OS-%SERIAL%
User as admin settings:
OMA-URI used: ./Device/Vendor/MSFT/Accounts/Users//Password
Data Type: String
Value:
OMA-URI used: ./Device/Vendor/MSFT/Accounts/Users/ITSD/LocalUserGroup
Data Type: Integer
Value: 2
Thank you.

Hi @xonaecom,
Please refrain from sending any log information for now. The team is still figuring out how to solve your problem. It may have something to do with Intune, but I will let you know once I get more information.
Thanks,
Heidi

Have the same problem with the username en password.

@Heidilohr I have a case where a customer reports this issue. Have you received any information from dev? How should we explain this issue to the customer? Thank you.

@kufang I'm still waiting to hear back from the dev team, but I'll be sure to let you know when they do.

Hi All, Do you have any update on this above thread. We are trying to configure the same in our environment and getting the same error code. It is causing Non-Compliant in the intune console for the devices. Please let me know is there anything to solve the problem.

I am sharing some updates from @Rob Lane, who discussed it with PG about the issue. The error here is due to the status check mechanism that is implemented within. In general, when Intune tries to determine if the policy takes effect on the target device, it calls Get Operation of the interested OMA-URI, which basically queries the registry key value from the client. And then compare the result with the policy value.
The problem is that this CSP only supports Add Operation, which means the Get Operation will always fail because it has not been implemented. That's why we get the error even if it successfully applied.
Even if we have the Get Operation implemented, we still need extra care for those Macros used since a simple strcmp would not be smart enough to identify if the results are expected. But that will be the dev's problem to solve.

Hi, I have similar issue - setting the local user account password sets the flag for "change password on next logon".

Any update on getting this fixed?

I solved this by using script, since Microsoft did not corrected this. Mail me if someone want the script.

Can you please post your script here? Very interested. Also interested in forcing the "change password on next logon" flag. Is there a CSP to set this option?

I solved this by using script, since Microsoft did not corrected this. Mail me if someone want the script.

I could no find your email on your profile.  Can you paste the script here?  Do you execute the script via powershell or intune32 app?  Thanks

cmd.exe /c 'net user | find /i "LocalAdmin" || Net user LocalAdmin StrongPasswordHere  /add /fullname:"LocalAdmin"'
cmd.exe /c 'net user | find /i "LocalAdmin" | Net user LocalAdmin StrongPasswordHere'
cmd.exe /c 'net localgroup administrators | find /i "LocalAdmin" || net localgroup Administrators LocalAdmin /add'
cmd.exe /c 'WMIC USERACCOUNT WHERE Name="LocalAdmin" SET PasswordExpires=FALSE'

cmd.exe /c 'net user | find /i "LocalAdmin" || Net user LocalAdmin StrongPasswordHere /add /fullname:"LocalAdmin"'
cmd.exe /c 'net user | find /i "LocalAdmin" | Net user LocalAdmin StrongPasswordHere'
cmd.exe /c 'net localgroup administrators | find /i "LocalAdmin" || net localgroup Administrators LocalAdmin /add'
cmd.exe /c 'WMIC USERACCOUNT WHERE Name="LocalAdmin" SET PasswordExpires=FALSE'

The script checks whether the account does exist so the error code is not reported wrongly. There are possibly more ways how to achieve this but for me, this worked.
Save it as a powershell script and run as a script within the Intune.

cmd.exe /c 'net user | find /i "LocalAdmin" || Net user LocalAdmin StrongPasswordHere /add /fullname:"LocalAdmin"'
cmd.exe /c 'net user | find /i "LocalAdmin" | Net user LocalAdmin StrongPasswordHere'
cmd.exe /c 'net localgroup administrators | find /i "LocalAdmin" || net localgroup Administrators LocalAdmin /add'
cmd.exe /c 'WMIC USERACCOUNT WHERE Name="LocalAdmin" SET PasswordExpires=FALSE'

The script checks whether the account does exist so the error code is not reported wrongly. There are possibly more ways how to achieve this but for me, this worked.
Save it as a powershell script and run as a script within the Intune.

Beware with this approach, the password is logged in plaintext (https://oliverkieselbach.com/2018/02/12/part-2-deep-dive-microsoft-intune-management-extension-powershell-scripts/#sensitive-data)
I would not use a script for this
Is there any update for this problem? Getting this error on all my devices

Have same error on multiple tenants/intune , on multiple windows 1803, 1809 , 1903 ...
it works (new users is deployed and added to local admin group), but the error in portal is visible as -2016281112 (Remediation failed)

@officedocsbot assign @jvsam

Hi @xonaecom @dzejzipl @aavdberg @SureshVijayaraghavan @dbdmora @LeThijs @hkusulja @bertrsh we appreciate your patience and thank you for bringing this to our attention. Thanks for sharing updates @kufang and for your workaround @Jakub-Urban.
Although we would love to help resolve this issue, however, this Github site is intended for product documentation. Our main goal here is to ensure users have the best Windows 10 experience by providing useful, accurate and up-to-date documentation. Hence, if there is anything in this documentation that you think should edited or new (and relevant) information that needs to be added, please let us know or you can also suggest changes via pull requests.
What we would recommend, if you are still experiencing the problem, is to utilize the proper channel by contacting support and opening a service ticket in your tenant to get this issue resolved ASAP. Thank you!
NOTE: Please keep us posted here on the resolution for it may be something we can incorporate to the docs.

@jvsam - please understand, that Microsoft support through service ticket is sometimes very slow etc.
Please update documentation what this number means about error so we can troubleshoot further and resolve issue by our self, since you are also documenting error codes, and this error code is unclear.

@jvsam I have to agree with @hkusulja. I already opened a ticket because of this problem using Premier, and the support has no idea what the problem is and how to respond to this. So your solution is not a solution.

Hi @hkusulja and @xonaecom, we do understand that this Github site is also another way/means of informing the community about this issue and in case someone is aware of a resolution, we hope it can be shared here. Although without the information coming from the right team, we will not be able to determine if this documentation needs to be updated or not. If yes, with what. But we do appreciate your patience on this matter.
Hello @lomayor, how are you? I hope you can help us with this issue. Can you please let us know if there has been any information from the Dev team related to the<PHONE_NUMBER> (Remediation failed) error since this has been reported? Thank you and we look forward to your feedback.

@jvsam there is a docs site with listed codes and what it means and how to troubleshoot further. (currently i am unable to find it), but this code was missing there. It would be great to provide information about details on error so we can proceed troubleshooting further. Also MS Support does not know how to proceed since lack of information...

Hi @xonaecom and @hkusulja I'm wondering if you had a chance to look at the Troubleshooting Windows 10 Intune Policy Failures blog article?
Excerpts:

One of our customers recently reached out with an issue where a policy for Windows 10 wasn’t applying correctly, and we were returning a very unhelpful error message “-2016281112 Remediation failed”.

Unfortunately, the Remediation failed error message is all that is returned by the client when we issue the SET command on the OMA-URI’s required to configure the target setting. We’re partnering with Windows to improve this experience, so watch this space. But for now, we have to settle for what we have.

@lomayor just following up. Do you have any update regarding the status of this issue and if it's something that can be called out in the docs? Tagging you here as well @ManikaDhiman, hoping you have information about this since you are updating the contents of CSPs? Thank you so much.

Hi @jvsam, thanks for tagging me here. I will get in touch with the product team to see if we should include the details about "-2016281112 (Remediation failed)" error message in Accounts CSP doc. Thanks!

Thank you so much @ManikaDhiman. We appreciate your help.

Hi @ManikaDhiman, just want to ask if you got the confirmation. Will the doc be updated? Thank you again.

Hi @jvsam, I am awaiting confirmation. I will update the status as soon as I hear from them. Thanks!

Hi @jvsam, Product team suggested not to add any note in the CSP doc for this error as it is specific to Intune, other MDM ISVs may have different results. Hope this helps. Thanks!

@ManikaDhiman then specify this error and details about it into Intune documentation...

Thank you for the update @ManikaDhiman. We appreciate all your effort.
@hkusulja there are different topic owners/authors. And with this new feedback system at docs.microsoft.com, it is easier to create an issue on the actual content page and provide feedback for better issue management. Please use the submit feedback option on the documentation where you think your suggestion is best applied since as per the Dev team and the author, this is not the right topic for that.
Also, there's already an existing Intune doc that lists all the common error codes and descriptions in Microsoft Intune. Although, please note that as per the author, the doc only lists the codes, and for troubleshooting, you can utilize the TechNet user forum or contact the dedicated Intune Support. You can also check the Intune Tech Community where you can ask questions and interact with other users, experts and also Microsoft engineers. Also looking into the different posts, it appears that the Remediation Failed error may vary based on different scenarios. So even the explanation from @kufang may not be a catch-all answer. But again, it is worth suggesting on the correct doc.

...The error here is due to the status check mechanism that is implemented within. In general, when Intune tries to determine if the policy takes effect on the target device, it calls Get Operation of the interested OMA-URI, which basically queries the registry key value from the client. And then compare the result with the policy value.
The problem is that this CSP only supports Add Operation, which means the Get Operation will always fail because it has not been implemented. That's why we get the error even if it successfully applied.
Even if we have the Get Operation implemented, we still need extra care for those Macros used since a simple strcmp would not be smart enough to identify if the results are expected. But that will be the dev's problem to solve.

I believe we can consider this as resolved and no changes to doc as of this time. We will now close this issue, however, feel free to re-open if you have other suggestions or ideas to improve the quality of this documentation.
Thank you for being part of the Microsoft Docs community!

@officedocsbot close

Ref: https://github.com/MicrosoftDocs/IntuneDocs/issues/2773


Solaris does not have bits/stat.h

The build on Solaris breaks because of the inclusion of <bits/stat.h> which does on exist. Just taking out the include works on Solaris.

I have no idea, how that made it into the source. Will check OpenBSD tomorrow, but I guess it was a mistake. Thanks for pointing out !

This seems to be the only issue left.

Fix pushed.
I built the latest stuff from branch 'develop' on the Solaris built farm (on unstable10x, unstable11x) without problems, the test suite succeeds.


Security Fix for Prototype Pollution - huntr.dev

https://huntr.dev/users/Asjidkalam has fixed the Prototype Pollution vulnerability 🔨. Think you could fix a vulnerability like this?
Get involved at https://huntr.dev/
Q | A
Version Affected | ALL
Bug Fix | YES
Original Pull Request | https://github.com/418sec/deeply-object-assign/pull/1
Vulnerability README | https://github.com/418sec/huntr/blob/master/bounties/npm/deeply-object-assign/1/README.md
User Comments:
📊 Metadata *
Prototype Pollution bug
Bounty URL: https://www.huntr.dev/bounties/1-npm-deeply-object-assign
⚙ Description *
deeply-object-assign is vulnerable to Prototype Pollution. This package allowing for modification of prototype behavior, which may result in Information Disclosure/DoS/RCE.
Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as _proto_, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
💻 Technical Description *
The bug is fixed by validating the input src to check for prototypes. It is implemented by a simple validation to check for prototype keywords (__proto__, constructor and prototype), where if it exists, the function returns the object without modifying it, thus fixing the Prototype Pollution Vulnerability.
🐛 Proof of Concept (PoC) *
Clone the project, install the required dependencies and on running the below snippet of code, it triggers prototype pollution and logs Yes! Its Polluted.
// poc.js
var deeplyObjectAssign = require("deeply-object-assign")
const payload = JSON.parse('{"__proto__":{"polluted":"Yes! Its Polluted"}}');
var obj = {}
console.log("Before : " + {}.polluted);
deeplyObjectAssign(obj, payload);
console.log("After : " + {}.polluted);

🔥 Proof of Fix (PoF) *
After the fix is applied, it returns undefined since the polluted referred in the PoC is no more accessible(which is intended). Hence fixing the issue.
👍 User Acceptance Testing (UAT)
Just prevented some keywords as key and no breaking changes are introduced. :)

Thank you for fixing the bug.

Thank you for fixing the bug.


[BFCL] proprietary model handle

Describe the issue
The Privatized Model Deployment
When I copied yi.py to implement my proprietary model handle, I got errors:
Traceback (most recent call last):
  File "/gorilla/berkeley-function-call-leaderboard/openfunctions_evaluation.py", line 124, in multi_threaded_inference
    result, metadata = handler.inference(copy.deepcopy(test_case), include_debugging_log)
  File "/gorilla/berkeley-function-call-leaderboard/bfcl/model_handler/base_handler.py", line 41, in inference
    return self.inference_single_turn_FC(test_entry, include_debugging_log)
  File "/gorilla/berkeley-function-call-leaderboard/bfcl/model_handler/base_handler.py", line 415, in inference_single_turn_FC
    inference_data: dict = self._pre_query_processing_FC(test_entry)
TypeError: myHandler._pre_query_processing_FC() missing 1 required positional argument: 'test_entry'

ID datapoint

Datapoint / Model Handler permalink:
Issue:
Gorilla repo commit #:

What is the issue
Proposed Changes
{
'previous_datapoint':[],
'updated_datapoint':[]
}
Additional context
Add any other context about the problem here.

Hi @BeerTai,
Thanks for pointing this out. I will raise a quick patch for it.


incbin.c: Visual Studio 2017 missing MAX_PATH

Pretty simple.  If I compile incbin.c using Visual Studio 2017, it complains about a missing MAX_PATH.
The following invocation gives me what I need.  It's a little overkill, but it's probably the safest way to ensure MAX_PATH exists.
#ifdef _WIN32
#define WIN32_LEAN_AND_MEAN
#include <Windows.h>
#endif

This has been fixed


[WIP] Rename project to kubespray

Getting started with a PR to rename instances of kargo in our codebase to kubespray. This will take a bit of time, but it's here to show that we're actively working the problem. Beginning with a quick rename of the top-level yamls.
Will close #1352.

Alright, I've got most everything changed. I need to do a test to make sure a deploy works as expected. There were still several instances of "kargo", mainly because I wasn't comfortable making changes to contrib code without breaking something. That said, the biggest area is "kargo-cli". That github repo will need to renamed and then the docs updated (cc @Smana for that). There's also some GCE buckets and stuff, but those may not really need to change. Here's a list of the files that I'm showing still have kargo mentions:
./.gitlab-ci.yml
./contrib/inventory_builder/inventory.py
./contrib/inventory_builder/setup.cfg
./contrib/inventory_builder/tests/test_inventory.py
./contrib/kvm-setup/group_vars/all
./contrib/kvm-setup/README.md
./contrib/kvm-setup/roles/kvm-setup/tasks/sysctl.yml
./docs/cloud.md
./docs/coreos.md
./docs/getting-started.md
./docs/roadmap.md
./extra_playbooks/roles/download/defaults/main.yml
./extra_playbooks/roles/uploads/tasks/main.yml
./README.md
./roles/download/defaults/main.yml
./roles/uploads/tasks/main.yml
./scripts/premoderator.sh
./tests/cloud_playbooks/upload-logs-gcs.yml

How will this affect existing deployments?

This is, of course, a great question and deserves to be tested. But I'm hoping the answer is "it doesn't". The only thing that I believe is changed on the cluster itself is a simple label for kube-apiserver's template here.
I believe everything else is internal to the kargo playbooks or docs changes.

Almost all references have been removed. There are a few remaining that @ant31 should fix, as they are pointers to a quay image and a google cloud bucket. You can find them in these files:
./extra_playbooks/roles/download/defaults/main.yml
./extra_playbooks/roles/uploads/tasks/main.yml
./roles/download/defaults/main.yml
./roles/uploads/tasks/main.yml
./tests/cloud_playbooks/upload-logs-gcs.yml

Also, @Smana I renamed every "kargo-cli" reference to "kubespray-cli". If you could rename your project, that would be awesome. If we don't do it soon, we'll likely need to delete references to it altogether, since it will be incredibly confusing for new users.
Please follow up with these remaining changes ASAP.

ci check this


REQUEST: Make repeating messages fancier

Either every X hours or every Y day(s) at Z time
Wishful thinking: If the bot could see if its own last iteration was the most recent post in the channel, skip the new post* or replace the old post to update the timestamp**
*preferred
**fancier

This is doable.  It might get a little weird with DST, but we'll see
fancier is doable

This is doable.  It might get a little weird with DST, but we'll see
fancier is doable

Repeating messages have been implemented.  The next thing to do is make them fancier as described above

Repeating messages have been implemented.  The next thing to do is make them fancier as described above


added signal-handler for graceful shutdown

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 20 (40.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-3.1%) to 87.41%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pipecheck/main.py
8
20
40.0%

Totals

Change from base Build<PHONE_NUMBER>:
-3.1%

Covered Lines:
243

Relevant Lines:
278

💛  - Coveralls


[BUG]: The right pane for Terraform Live Graph has a single square white dot at the top.

Describe the bug
While using the extension, the graph view displays a small white box at the top of the view.
https://github.com/adamiBs/vscode-terraform-live-graph/issues/1#issuecomment-1472407101
To Reproduce
Steps to reproduce the behavior:

Open an empty folder in VS Code.
Activate the extension.

Expected behavior

Some kind of relevant message.

Screenshots
Example from @crc8109

Versions (please complete the following information):

OS: OSX 13.1
VSCode Version: 1.76.2
Terraform Live Graph Extension for VSCode Version 0.0.5
Terraform Version: 1.4.0

Hi @adamiBs , any update on this issue ?

Seeing the same. Can it have something to do with having a complex tf structure with external dependencies (other repos as modules)?

Kind of, we use AWS root modules to create tf resources in AWS, so we basically we copy the required files and keep it in folder and we use that folder as a module.


Export .hive on web

How would you export the .hive file from web, ie:
var boxBytes = await File(yourBox.path).readAsBytes();
as path is not supported on Web?

Please check browser support on hivedb docs. As it says, hivedb stores data on browser IndexedDB instead of a file since browser doesn't have file system.


Add actionable error messages when users hit the confusing error

Add actionable error messages when users hit the confusing error in sc install command.
Now the output is:

$ ./output/bin/sc install
generated service catalog deployment config in dir: /tmp/service-catalog895050393
WARNING: Please run kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account) before sc install.
Service Catalog could not be installed
Error: error deploying YAML files: deploy failed with output: exit status 1 :Error from server (Forbidden): error when creating "/tmp/service-catalog895050393/etcd-operator-rbac.yaml": clusterroles.rbac.authorization.k8s.io "etcd-operator" is forbidden: attempt to grant extra privileges: [PolicyRule{Resources:["etcdclusters"], APIGroups:["etcd.database.coreos.com"], Verbs:[""]} PolicyRule{Resources:["customresourcedefinitions"], APIGroups:["apiextensions.k8s.io"], Verbs:[""]} PolicyRule{Resources:["storageclasses"], APIGroups:["storage.k8s.io"], Verbs:[""]} PolicyRule{Resources:["pods"], APIGroups:[""], Verbs:[""]} PolicyRule{Resources:["services"], APIGroups:[""], Verbs:[""]} PolicyRule{Resources:["endpoints"], APIGroups:[""], Verbs:[""]} PolicyRule{Resources:["persistentvolumeclaims"], APIGroups:[""], Verbs:[""]} PolicyRule{Resources:["events"], APIGroups:[""], Verbs:[""]} PolicyRule{Resources:["deployments"], APIGroups:["apps"], Verbs:[""]}]<EMAIL_ADDRESS>[system:authenticated] map[]} ownerrules=[PolicyRule{Resources:["selfsubjectaccessreviews"], APIGroups:["authorization.k8s.io"], Verbs:["create"]} PolicyRule{NonResourceURLs:["/api" "/api/" "/apis" "/apis/" "/healthz" "/swaggerapi" "/swaggerapi/" "/version"], Verbs:["get"]}] ruleResolutionErrors=[]

Fixes #115, fixes #67, and fixes #35.

Can we make the error message less verbose? We can put "Info:", "Warning:", or "Error:" prefix if we need to print more than one messages in one command.
Something like:
Info: generated service catalog deployment config in dir: /tmp/service-catalog895050393
Warning: please run kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account) before sc install.
Error: error deploying YAML files: deploy failed with output: exit status 1 :Error from server (Forbidden): error when creating "/tmp/service-catalog895050393/etcd-operator-rbac.yaml": clusterroles.rbac.authorization.k8s.io "etcd-operator" is forbidden: attempt to grant extra privileges: [PolicyRule{Resources:["etcdclusters"], APIGroups:["etcd.database.coreos.com"], Verbs:[""]} PolicyRule{Resources:["customresourcedefinitions"], APIGroups:["apiextensions.k8s.io"], Verbs:[""]} PolicyRule{Resources:["storageclasses"], APIGroups:["storage.k8s.io"], Verbs:[""]} PolicyRule{Resources:["pods"], APIGroups:[""], Verbs:[""]} PolicyRule{Resources:["services"], APIGroups:[""], Verbs:[""]} PolicyRule{Resources:["endpoints"], APIGroups:[""], Verbs:[""]} PolicyRule{Resources:["persistentvolumeclaims"], APIGroups:[""], Verbs:[""]} PolicyRule{Resources:["events"], APIGroups:[""], Verbs:[""]} PolicyRule{Resources:["deployments"], APIGroups:["apps"], Verbs:[""]}]<EMAIL_ADDRESS>[system:authenticated] map[]} ownerrules=[PolicyRule{Resources:["selfsubjectaccessreviews"], APIGroups:["authorization.k8s.io"], Verbs:["create"]} PolicyRule{NonResourceURLs:["/api" "/api/" "/apis" "/apis/" "/healthz" "/swaggerapi" "/swaggerapi/" "/version"], Verbs:["get"]}] ruleResolutionErrors=[]

service catalog could not be installed

The last message can be the consequence of the command.

The last message can be the consequence of the command.

Currently, we rely on Cobra to print the error message for all the failed commands. So the "Error:" section will always printed at last. I can make a change to print the error details before printing out the consequence. But I think there will always be an "Error:" section after our last message if we return an error.
One alternative is to never return any error after failures, but instead, print the error before "return nil". To create consistent behavior, we may need to refactor all the commands.


[Enhancement] Method appears to call the same method on the same object redundantly [ReplyMessageProcessor]

Search before asking

[X] I had searched in the issues and found no similar issues.

Enhancement Request

located at:
eventmesh-runtime/src/main/java/org/apache/eventmesh/runtime/core/protocol/http/processor/ReplyMessageProcessor.java line 81,92
analysis and explanation:
This method makes two consecutive calls to the same method, using the same constant parameters, on the same instance, without any intervening changes to the objects. If this method does not make changes to the object, which it appears it doesn't, then making two calls is just a waste.
Describe the solution you'd like
These method calls could be combined by assigning the result into a temporary variable, and using the variable the second time.
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

i try to fix this problem by this pr https://github.com/apache/incubator-eventmesh/pull/2838


Getting the code to work on wordpress

When I attempted to upload the files to Wordpress to see if it would work, this is what happened.
https://favoriteservant.com/11-2/

I'm not very familiar with Wordpress myself, but Googling for how to upload custom HTML content to Wordpress, I get stuff like this: https://blog.hubspot.com/website/upload-html-file-to-wordpress

So I consulted the wordpress support and apparently I couldn't make the site work without upgrading my plan, so I decided to just cancel my subscription. Do you have any suggestions for a service I could use instead?

https://neocities.org/ provides free hosting for simple webpages, which should work fine for the picker! Of course, it depends what else you might want to put on the site.


[Worker] Allow interrups to exit the process even after the threads are disposed

This means that SIGINT during, say, dependency resolution will still cleanly exit the process.

good catch! @bundlerbot r+


Merge deploy-changehc to main

Update main with this new deployment branch.
NOTE: In addition to the standard additions for a deployment branch, we've also added:

Jenkins staging deployments

After this branch is integrated with main (and then propagated to the other deployment branches), we'll start deploying an indicator package as part of the Jenkins pipeline that runs for the PR submission/update against the corresponding deployment branch. The Jenkins PR phase now looks like build -> test -> package -> deploy to staging. The subsequent merge deploys to production.

@krivard It may or may not be useful to merge this yet because of our possible upcoming rework of this repo's workflow, but here it is.

It may or may not be useful to merge this yet because of our possible upcoming rework of this repo's workflow,

Good thought, but without knowing how long it will take to implement workflow changes, I'd rather keep the CHC indicator moving forward


LRU cache optimization

A cache is added to reduce the number of system calls that copy the remote process's memory. The cache is a LRU cache with a specified capacity.

I'm not sure if any of the bugs I noticed were the cause, but the coverage stage of CI failed with:
INFO     /home/runner/work/pystack/pystack/src/pystack/_pystack.cpython-310-x86_64-linux-gnu.so:test_gather_stacks.py:119 Fetching Python threads
double free or corruption (out)
Fatal Python error: Aborted

We'll have to see if the bugs I noticed account for that, or if that's an unrelated issue...

Lastly, the "Commits Check" check is ensuring that you've provided a DCO sign-off in your commit message. You could add that to your current commit by doing a git commit --amend -s and then force-pushing your changed commit up to GitHub with git push -f

Codecov Report
Patch coverage: 88.00% and project coverage change: +0.06 :tada:

Comparison is base (8473602) 90.34% compared to head (d94dab7) 90.40%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #124      +/-   ##
==========================================
+ Coverage   90.34%   90.40%   +0.06%
==========================================
  Files          47       48       +1
  Lines        5480     5526      +46
  Branches      863      863
==========================================
+ Hits         4951     4996      +45
- Misses        529      530       +1

Flag
Coverage Δ

cpp
75.80% <88.00%> (+0.61%)
:arrow_up:

python_and_cython
99.94% <ø> (-0.03%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/pystack/_pystack/mem.h
55.55% <ø> (ø)

src/pystack/_pystack/mem.cpp
89.60% <87.67%> (+2.79%)
:arrow_up:

src/pystack/_pystack/process.cpp
78.92% <100.00%> (+0.14%)
:arrow_up:

... and 6 files with indirect coverage changes

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

This all looks good to me at this point. I don't see any more bugs. I've got some nitpicks, but rather than force you to go through another round of reviews, I'm just going to push a fixup commit that improves those little things.
@ivonastojanovic Please check my work and make sure I didn't get anything wrong or make anything worse in my fixup commit.
@pablogsal Would you like to review this as well before we land it?

@godlygeek Everything looks great!


[WIP] [Do Not Merge] support for NodePort

Support for NodePort, call for review. Still need to test it completely.
Also TODO: add support for externalIPs.
Signed-off-by: Rajat Chopra<EMAIL_ADDRESS>

A little bit of code move (load balancer functions to their own file loadbalancer.go, gateway related functions in gateway.go).
@shettyg PTAL, still need to extensively test this though
@dcbw Glance over?

@shettyg All the feedback is taken care of. Still keeping it as WIP. Will remove the tag once I have tested it thoroughly.
Thanks.

@shettyg Tested this out. Its working piece of code now.

This PR will take care of issue #128 in the golang based controller.

LGTM


Remove compatibility plural api

In order to ease the transition, Prisma Client right now ships with a note with the old plural api, that it's deprecated.
We should by now remove the note, as it gets in the way with the autocompletion.

Any reason why this is removed? It reads weirdly
// This reads weird
🤮  const blogs = await prisma.blog.findMany()

// This reads greatly
😍  const blogs = await prisma.blogs.findMany()

You refer to the old "pluralized API", not the "compatibility plural api" we had for a few versions that @timsuchanek mentioned above.
About the pluralized API:
The problem is if people already have pluralized table names like posts it created something like postes - which is really awkward to use and non intuitive. Same problem in other, non English languages. Also if the table names for example use both way mixed at the same time. So for now we removed the feature. If you want to, you can use @map in your schema.prisma to rename the model (blog => blogs) which will also be reflects in Prisma Client.
We will think about how we can improve this experience in the future - we agree with your initial statement, but have to find a better way to offer that.


How to create virtualenv without setuptools installed?

Is it possible to use pyenv-virtualenv to create a virtualenv without setuptools installed?  I tried the following, but it doesn't seem to work:
$ pyenv virtualenv --no-setuptools 2.7.10 test-no-setuptools
New python executable in /Users/chris/.anyenv/envs/pyenv/versions/2.7.10/envs/test-no-setuptools/bin/python2.7
Also creating executable in /Users/chris/.anyenv/envs/pyenv/versions/2.7.10/envs/test-no-setuptools/bin/python
Ignoring indexes: https://pypi.python.org/simple
Collecting setuptools
Collecting pip
Installing collected packages: setuptools, pip
Successfully installed pip-6.1.1 setuptools-15.2

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/28766215-how-to-create-virtualenv-without-setuptools-installed?utm_campaign=plugin&utm_content=tracker%2F335155&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F335155&utm_medium=issues&utm_source=github).

It is not possible at least for now since it tries to run ensurepip after the creation. What is your purpose to skip the installation of setuptools?
https://github.com/yyuu/pyenv-virtualenv/blob/cf7dea411dca932e8a0dc6930eb608863da91502/bin/pyenv-virtualenv#L500-L501

I need to test the installation of setuptools & pip in a virtualenv which does not have these installed already.  Would it be possible to add a way to disable ensurepip as an option?


attempt to index field 'enriched_ctx' (a nil value)

Describe the bug
I encounters this error recently very often:
attempt to index field 'enriched_ctx' (a nil value)

Steps to reproduce
using code acitons
Expected behavior
auto fix problems
Neovim version (nvim -v)
NVIM v0.9.0 Build type: Release LuaJIT 2.1.0-beta3
lspsaga commit
latest
Terminal name/version
alacritty

I also get this error when trying to select an action, just started yesterday...
Neovim git latest
lspsaga latest
Alacritty

and another one: 🤔
 .../share/nvim/lazy/lspsaga.nvim/lua/lspsaga/codeaction.lua:203: attempt to call field 'deepcopty' (a nil value)

update . a typo sry

update . a typo sry

the same error of attempt to index field 'enriched_ctx' (a nil value)  occurs at line 265 just now .. 🫠

hmm I am on phone to edit these code .. can you update and test.

hmm I am on phone to edit these code .. can you update and test.

no worries, take your time on this fix. 🫠

Yup, I can confirm that after updating it's fixed

true, confirmed fixed. 💋

I confirmed above error has been fixed, however, the code action window does not auto-close after i've chosen a action.
Can i suppose that window was closed in history releases?

hmm you mean after you type 1 the window not close ?

yes, exactly.

can you update then test .. i try to add some patch. not sure can fix this i don' try to reproduce it.

can you update then test .. i try to add some patch. not sure can fix this i don' try to reproduce it.

can you update then test .. i try to add some patch. not sure can fix this i don' try to reproduce it.

No it doesn't. But it works fine while using :Lspsaga code_action command : (

i just disabled the code action on diagnostics:
diagnostic = {
	show_code_action = false
}

fixed.


where is crop function to crop roi of image?

where is crop function to crop roi of image?
I'm going crazy. I'm really going crazy.

Did you solve it? My quick check shows that there is no such function in OpenCV API. But you should be able to use https://docs.rs/opencv/latest/opencv/core/struct.Mat.html#method.roi to achieve the same functionality.

Yes, Mat::rowscols and Mat::roi are what I want. I missed them because of description: "download data from GpuMat".
Mat::rowscols is equivalent to img[a:b, c:d] in python or img(Range(a,b),Range(c,d)) in c++.

description: "download data from GpuMat".

Yep, unfortunately it's a known issue, the function annotation is reported this way by libclang for some reason. I'm yet to find a workaround for that issue.


ByteBuffer is not released when compression is enabled, causing pool leakage

Hey Mongo team.
My team experienced an increased number of failures caused by latency recently. Further investigation showed that InternalStreamConnection doesn't close buffers returned by PowerOfTwoBufferPool when compression is enabled. It leads to permits leakage. After INTEGER_MAX buffer retrievals buffer pool is fully exhausted and all following requests would be blocked indefinitely unless the thread gets interrupted.
JAVA-4510

An alternative way to address the issue can be buffer release as part of Compressor.ByteBufInputStream.close() method. For example, SocketInputStream works this way and closes the underlying socket as part of close call. But I think it's better to be explicit and close it within the same section that used it.

Hi @kulabun,
Thank you for the PR. I looked through the class InternalStreamConnection trying to see whether there are other places where we may not release buffers, and pushed a new commit.
Using your code in JAVA-4510 I confirmed that after the changes threads are not blocked due to ConcurrentPool.maxSize being exhausted. This can be done quickly by changing the ConcurrentPool.INFINITE_SIZE constant from Integer.MAX_VALUE to something small.


Enhacing kiali to be compatible with csi drivers/providers

Since the addition of OIDC to Kiali - the insertion of the oidc-secret into the Kubernetes namespace has been a challenge. In scenarios where secrets cannot be inserted directly through kubectl but only through independent secret providers the secret store CSI driver would solve this.
Since not everyone would be using this - I have also made it optional(or enabled) through values.yaml
The modifications include :
-Addition in values.yaml to specify values of csiVolume and Volume mounts

Addtion of volume and volume mounts in deployment.yaml and their logic
Secretstorage agnostic (works with every seceret management tool)

https://secrets-store-csi-driver.sigs.k8s.io/introduction

Please review the Kiali contributors page for the process.
https://github.com/kiali/kiali/blob/master/CONTRIBUTING.md#making-a-change
Before submitting your first PR, please submit an issue where it can be discussed among the community.

handled by this: https://github.com/kiali/kiali/issues/6942


Respect json_name option in go json tags

message Foo {
    int64 Bar = 1 [json_name="b"];
}

Fixes a bug when the .proto file above doesn't respect "json_name" option and generates:
type Foo struct {
    Bar int64 `protobuf:"varint,1,opt,name=Bar,json=b,proto3" json:"Bar,omitempty"`
}

instead of:
type Foo struct {
    Bar int64 `protobuf:"varint,1,opt,name=Bar,json=b,proto3" json:"b,omitempty"`
}

Thanks for the PR, but unfortunately we cannot accept this pull request even if the change is entirely reasonable.
The generation of the json tags preceded the creation of the jsonpb package with the intention of always using the standard library encoding/json package for serializing protobufs as JSON. However, it became clear over time that the stdlib version of json was not sufficient, which eventually led to the creation of jsonpb. At some point, the json_name option was added to control the JSON name, but it only affects the name used in jsonpb.
We cannot have json_name option also affect the json tag since it would break compatibility for users still using the stdlib json package and rely on the current behavior. Fiixing this is probably not worth the breakages it may cause.


[CI] Updated setup-msbuild tasks

On October 1, GitHub deprecated commands used by setup-msbuild to set the PATH environment variable. As a result, all of our CI is currently broken at the setup-msbuild step.
As a workaround, I've updated all of the tasks that use setup-msbuild to include the ACTIONS_ALLOW_UNSECURE_COMMANDS environment variable, which will override the command deprecation.
At some point, this same fix will need to be applied to all of the dependant projects for CI to work properly.

Seems like they're going to need an alternative to keep setup-msbuild working. Any idea if there is one that's better than this workaround for long term? I'm fine with this for now, but I'd assume that switch'll break at some point.

Seems like they're going to need an alternative to keep setup-msbuild working. Any idea if there is one that's better than this workaround for long term? I'm fine with this for now, but I'd assume that switch'll break at some point.

It looks like setup-msbuild needs to update its implementation to use Github's preferred method of setting environment variables. I think our best bet for long-term maintainability is to use this workaround and hope that setup-msbuild will update to a new implementation in a v2. Unfortunately, there's nothing I could find on how long Github plans to support the ACTIONS_ALLOW_UNSECURE_COMMANDS workaround.
Another option is for us to hard-code the msbuild.exe path everywhere we use it. This is pretty ugly, and breaks as soon as that path changes.
Another option is for us to set the path environment variable ourselves, but at that point we're just re-implementing setup-msbuild.


Dynamic Firebase ref url with React router params instead of url matching

Hello,
in the TodoMVC example, the actual Firebase url is fetched by matching the session key from window.location so that every time the page loads Firedux only gets access to the current session data in Firebase.
I have a React router param groupId accessible within the App as this.props.params.groupId and want to use that in the url e.g. url: FIREBASEURL + this.props.params.groupId. It just won't work.
The problem seems to be that Firedux is created first within the Redux store when calling firedux.dispatch = store.dispatch so way before the router params are even accessible and therefore no reference to the props.
The React App is Rendered as:
<Provider store={store}>
    <Router history={history}>
    <Route path="/" component={App}>
        <IndexRoute component={Home}/>
        <Route path="group/:groupId" component={Tool}/>
        <Route path="*" component={NotFound}/>
    </Route>
    </Router>
</Provider>

Any ideas how to solve this?

@uneart Can you just initialize Firedux with the top-level Firebase URL, then interact with it in components on paths that include the appropriate parameters?

@adjohnson916 That is what I ended up doing now as a workaround. I was just wondering if there is any way to achieve this. Fetching it from window.location doesn't work well with React router.

@uneart Maybe someday I'll change the TodoMVC example to use React Router.


swagger-ui.html inaccessible in version 2.8.0 with spring boot 1.5.8 and spring security web 4.1.3

When I try to access https://localhost:8443/context-root/swagger-ui.html, I get the "Unable to infer base url" popup that is often reported, but when I delve into the logs, I see some information that I haven't seen in the other reports.
Our application is a Spring Boot application (1.5.8) secured with Spring Security Web (4.1.3) and we are using our browser certs in order to authenticate, along with a directory server that determines our authorization.
I am able to access https://localhost:8443/context-root/swagger-resources/* just fine, and I can see that these have been mapped during the spring boot application startup.  So, I try to navigate to https://localhost:8443/context-root/swagger-ui.html, and the logs indicate that authentication is successful for various resources in the /context-root/webjars/springfox-swagger-ui/ location.  After several of these, I am getting "org.apache.juli.logging.DirectJDKLog - Servlet.service() for servlet [dispatcherServlet] in context with path [/context-root] thre exception java.lang.RuntimeException: Authentication was null.  Likely a configuration problem where an X509 or request-header filter was not properly placed in the filter chain.
I have everything working, including swagger-ui, with springfox 2.7.0.  When I upgrade to 2.8.0, I observe this problem.  It seems like swagger can find the resources well enough, but the authentication may be the problem.  I have seen examples for oauth, but how can I determine if it is the x509 certificate issue?  If anyone has any suggestions, it would be greatly appreciated.  Thanks in advance.

Additional detail: spring boot startup does not indicate that swagger-ui.html is mapped.

Just a guess, but does it work if you navigate to https://localhost:8443/swagger-ui.html

I tried that, but it does not work for me.  It doesn't throw an error, but
there is no content.
On Sat, Mar 24, 2018 at 9:15 AM, Dilip Krishnan<EMAIL_ADDRESS>wrote:

Just a guess, but does it work if you navigate to https://localhost:8443/
swagger-ui.html
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/springfox/springfox/issues/2319#issuecomment-375888585,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APqR25uygzjbGEcfNp2Wsxz-97Zy_Ipoks5thkb-gaJpZM4S4n5o
.

Same problem here.
The html get fetched but can't access the endpoints because of the missing permission.
I was in the need to copy the swagger files into the resources folder,
add ResourceHandlers
 @Override
    public void addResourceHandlers(ResourceHandlerRegistry registry) {
        registry.addResourceHandler("/swagger-ui.html").addResourceLocations("classpath:/");
        registry.addResourceHandler("/webjars/**").addResourceLocations("classpath:/");
    }

and modify the springfox.js fetch api usage to send an auth header.
const configUIResponse = await fetch(baseUrl + "/swagger-resources/configuration/ui",
            {
                headers: {
                    'Authorization': 'Basic ' + b64EncodeUnicode('user' + ':' + 'pass'),
                },
            },
        );
      const configUI = await configUIResponse.json();

      const configSecurityResponse = await fetch(baseUrl + "/swagger-resources/configuration/security",
            {
                headers: {
                    'Authorization': 'Basic ' + b64EncodeUnicode('user' + ':' + 'pass'),
                },
            },
        );
      const configSecurity = await configSecurityResponse.json();

      const resourcesResponse = await fetch(baseUrl + "/swagger-resources",
            {
                headers: {
                    'Authorization': 'Basic ' + b64EncodeUnicode('user' + ':' + 'pass'),
                },
            },
        );
      const resources = await resourcesResponse.json();
      resources.forEach(resource => {
        resource.url = baseUrl + resource.url;
      });

What's your concrete conclusion after thinking about it? :)

I've been playing a toy application, havent had time recently with the 2.9.0 release, but i'll report back once I make progress


Query result: column aliases ignored when copied as CSV

Description
Trying to copy the result of a query with more than 1 result column alias, those aliases are ignored and the original column names are pasted instead
DBeaver Version
Community Edition 22.3.3
Operating System
Windows 11
Database and driver
MariaDB 10.5.16
Steps to reproduce
execute query "SELECT t.ID AS Alias1, t.Description AS Alias2 FROM mytable t"
select all the results clicking the top-left cell in the results section (note that the aliases are correctly displayed there)
right-click "Advanced Copy"->Copy as CSV
Paste in Excel/LibreOffice Calc/NotePad: the first row will be "ID" - "Description" instead of "Alias1" - "Alias2"
Additional context
No response

Can you please provide footage showing your issue? Thank you.

"Copy as JSON" too.
Just make a query with aliases in columns names (I do it with MySQL connection), select all results in the Grid View, then select "Copy as JSON" in "Advanced Copy" in the context menu when right click over results selected. Paste in a text editor and you will see original column names, no the alias wrote in the SELECT query
I some version we lose this feature.

@arhayka the "steps to reproduce" are detailed above, do you really need a footage?

Does it still reproducible on the latest DBeaver version (23.0.0)?

It's been a long time since no update here. Please let me know if the issue still actual and can be reproduced on the latest DBeaver version.

I'm able to reproduce this issue with Version <IP_ADDRESS>304240630  .  Can this be reopened or do you need a fresh issue created?

Thanks.
No need to create another one issue.

@kcbaltz could you provide an example please?

Is it the same as in the issue description or some other?

My steps are this:
Query:
SELECT cntry_a3_cd AS code3, cntry_a2_cd AS code2, cntry_nm AS country_name
FROM countries
Advanced Copy as HTML result pasted here (Note
cntry_a3_cd	cntry_a2_cd	 instead of
code3	code2
<!DOCTYPE html>

<meta charset="UTF-8"/>

SELECT cntry_a3_cd AS code3, cntry_a2_cd AS code2, cntry_nm AS country_name
FROM countries

cntry_a3_cd	cntry_a2_cd	cntry_nm

ABW	AW	Aruba

AFG	AF	Afghanistan

AGO	AO	Angola

AIA	AI	Anguilla

ALB	AL	Albania

AND	AD	Andorra

ARE	AE	United Arab Emirates

ARG	AR	Argentina

ARM	AM	Armenia

ATG	AG	Antigua and Barbuda

I believe this is the same issue, only I was using HTML instead of CSV, but I believe all the Advance Copies are affected

Results with JSON:
{
"SELECT cntry_a3_cd AS code3, cntry_a2_cd AS code2, cntry_nm AS country_name \nFROM countries\n": [
	{
		"cntry_a3_cd" : "ABW",
		"cntry_a2_cd" : "AW",
		"cntry_nm" : "Aruba"
	},
	{
		"cntry_a3_cd" : "AFG",
		"cntry_a2_cd" : "AF",
		"cntry_nm" : "Afghanistan"
	},
	{
		"cntry_a3_cd" : "AGO",
		"cntry_a2_cd" : "AO",
		"cntry_nm" : "Angola"
	},
	{
		"cntry_a3_cd" : "AIA",
		"cntry_a2_cd" : "AI",
		"cntry_nm" : "Anguilla"
	},
	{
		"cntry_a3_cd" : "ALB",
		"cntry_a2_cd" : "AL",
		"cntry_nm" : "Albania"
	},
	{
		"cntry_a3_cd" : "AND",
		"cntry_a2_cd" : "AD",
		"cntry_nm" : "Andorra"
	},
	{
		"cntry_a3_cd" : "ARE",
		"cntry_a2_cd" : "AE",
		"cntry_nm" : "United Arab Emirates"
	},
	{
		"cntry_a3_cd" : "ARG",
		"cntry_a2_cd" : "AR",
		"cntry_nm" : "Argentina"
	},
	{
		"cntry_a3_cd" : "ARM",
		"cntry_a2_cd" : "AM",
		"cntry_nm" : "Armenia"
	},
	{
		"cntry_a3_cd" : "ATG",
		"cntry_a2_cd" : "AG",
		"cntry_nm" : "Antigua and Barbuda"
	}
]}

If it is of help, I can also provide details for recreating the problem, which remains in DBeaver 23.2.2:

Run query

SELECT resources.name AS resource_title
FROM resources;

Result window in DBeaver shows column name is "resource_title" as expected

Right-click the top-left corner of the result window and click Advanced Copy -> Copy as TXT, then paste in a text editor. The the column is called "name" instead of the alias "resource_title":

name

Resource 1

Resource 2

Resource 3

The same occurs with Copy as CSV, which I also use often.

Thanks

Getting the same thing here too.
select
col1,
col2 as NEW_COL_NAME_FOR_COL2,
col3
from table1
In DBeaver results panel this displays this accurately: col1, NEW_COL_NAME_FOR_COL2, col3
Advanced copy commands return the following however: col1, col2, col3

Has there been an development with a fix for this? Getting the same still

We haven't fixed it yet.
You can vote for the issue with 👍 under the issue description to promote it to a higher priority.

I face the same for the "Copy as TXT" in Dbeaver with the recent version of the repo, i.e. commit 0d326aa112032931ec134156d89caa757fa64c13 .
I set up the development environment on my machine and run the debug mode of Dbeaver and even manage to find a bit more context:

When the transfer is finished in StreamTransferConsumer#finishTransfer the outputBuffer does not have the aliases present;
On the other side, when using the Dbeaver Sample Database (SQLite) that comes out of the box with the debug - the aliases are there.

I am planning to continue investigating this issue as I am now able to reproduce and debug it and will post my progress here.

Cheers with an MR that I have tested and works like a charm. It took some time debugging, but I am pleased with the results. I hope it will get to production soon, because I use this functionality on a daily basis in JIRA. There the TXT tables (exported with Advanced Copy -> Copy as TXT) are displayed directly in the JIRA comments as tables. Evidence from the DB, as always.

@MashaKorax Possible duplicates of this issue are:

https://github.com/dbeaver/dbeaver/issues/34963
https://github.com/dbeaver/dbeaver/issues/34050

I commented in them with a cc to the authors and I strongly recommend to ask them to retest as soon as this one is fixed with https://github.com/dbeaver/dbeaver/pull/35007
What do you think ?

Hi, @dstivanov! Thank you for your effort. Indeed the issues you mention looks very similar. I'll ask our QA to check those issues too and close, if they're solved.
At the moment, we have passed your pull request to our quality assurance team for testing. While we are waiting for them to complete the testing, the fix will not be included in the product.


Emojis missing?

are theses emojis missing?
1F9B0                                      ; fully-qualified     # 🦰 red-haired
1F9B1                                      ; fully-qualified     # 🦱 curly-haired
1F9B2                                      ; fully-qualified     # 🦲 bald
1F9B3                                      ; fully-qualified     # 🦳 white-haired
They are included in Unicode 11.0 as standalone emojis but seem to be missing from twemoji.

Added the missing hair component assets in the latest release.
https://github.com/twitter/twemoji/commit/6f3545b9649bba68ead0660328f318777c8a9416


this result is worse

The result from the paper for Wide-Resnet-32 on cifar100 is 78.74% for initial lr=0.1 and  78.44% for initial lr=0.2. However, this implementation (71.78%) is far worse than the result of the paper. Are there any other tricks?


Self-hosted fonts

Closes https://github.com/oasisprotocol/oasis-wallet-web/issues/526

Tested using Chrome/FF/Safari
I've removed  Inter web font completely, because we are not using it in our app. This also deprecates usage of fontfaceobserver dependency in the app

I forgot about CSP rules

e2e test is failing due to missing governance.SubmitProposal. That is covered in https://github.com/oasisprotocol/oasis-wallet-web/pull/776


Instance BLE with compose

how to use BLE with compose?

The README.md has been updated with instructions

How do I get ComponentActivity in a Composable?

It's not super-clear what to do here.
I've tried:
tailrec fun Context.getActivity(): AppCompatActivity? = when (this) {
  is AppCompatActivity -> this
  is Activity -> getActivity()
  is ContextWrapper -> baseContext.getActivity()
  else -> null
}

BLE(LocalContext.current.getActivity())

but that just results in:
E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.myapp, PID: 14836
    java.lang.IllegalStateException: LifecycleOwner com.myapp.MainActivity@183df6e is attempting to register while current state is RESUMED. LifecycleOwners must call register before they are STARTED.
        at androidx.activity.result.ActivityResultRegistry.register(ActivityResultRegistry.java:123)
        at androidx.activity.ComponentActivity.registerForActivityResult(ComponentActivity.java:833)
        at androidx.activity.ComponentActivity.registerForActivityResult(ComponentActivity.java:842)
        at quevedo.soares.leandro.blemadeeasy.ContractHandler.<init>(ContractHandler.kt:21)
        at quevedo.soares.leandro.blemadeeasy.BLE.registerContracts(BLE.kt:159)
        at quevedo.soares.leandro.blemadeeasy.BLE.setup(BLE.kt:150)
        at quevedo.soares.leandro.blemadeeasy.BLE.<init>(BLE.kt:133)


Revert "GEODE-9632: Allow INDEX_THRESHOLD_SIZE System property to ove…

…rride CompiledValue.RESULT_LIMIT (#7010)"
This reverts commit 67359dcd

For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

@mkevo as mentioned in the dev mail, we are planning to put the commit in develop again after fixing the problem that was brought up by you in dev list.
We are planning to release 1.15 (which is planned for this month) and then try to fix the issue and put it back into develop.
We need to revert the commit in develop to back port the revert to 1.15 ( its the release protocol). After 1.15.0 is released, we can put the complete solution back in


CPU out of control

On Ark Client 1.4.2, two of my CPU cores are monopolized by the ArkClient Helper process, even
with the wallet application not running.
OSX 10.12.6

Is it mining Vertcoin? ;)

do you use ledger nano s?

This was supposed to be solved in #357  (which is already merged in 1.4.2) :thinking:

I can give it a whirl! Could they be leftover processes from the previous version of the client? When did you last restart your machine?

I was thinking that as well, that they might have been rogue processes from 1.4.1.
@ehrlichja can you restart your computer and try to reproduce this?

I restarted and am running the wallet again, so far I don't see it.


Tray icon doesn't change colour when entering private mode in Gnome 44 Wayland

Describe the bug
Before Gnome 44, the tray icon would change to a dim colour if you switched to private mode. This is no longer the case since upgrading to Gnome 44, as the tray icon doesn't change colour at all when entering private mode. This bug happened on Wayland only, whihle on X11 I didn't encounter the same issue.
Versions

GNOME Shell 44.0
GCH bash: gnome-extensions: command not found
org.gnome.shell.extensions.clipboard-history cache-only-favorites false
org.gnome.shell.extensions.clipboard-history cache-size 100
org.gnome.shell.extensions.clipboard-history clear-history @as []
org.gnome.shell.extensions.clipboard-history confirm-clear true
org.gnome.shell.extensions.clipboard-history disable-down-arrow true
org.gnome.shell.extensions.clipboard-history display-mode 0
org.gnome.shell.extensions.clipboard-history enable-keybindings true
org.gnome.shell.extensions.clipboard-history history-size 1000
org.gnome.shell.extensions.clipboard-history move-item-first true
org.gnome.shell.extensions.clipboard-history next-entry @as []
org.gnome.shell.extensions.clipboard-history notify-on-copy false
org.gnome.shell.extensions.clipboard-history paste-on-selection false
org.gnome.shell.extensions.clipboard-history prev-entry @as []
org.gnome.shell.extensions.clipboard-history private-mode false
org.gnome.shell.extensions.clipboard-history process-primary-selection false
org.gnome.shell.extensions.clipboard-history strip-text false
org.gnome.shell.extensions.clipboard-history toggle-menu ['<Super><Shift>V']
org.gnome.shell.extensions.clipboard-history toggle-private-mode ['<Super><Shift>P']
org.gnome.shell.extensions.clipboard-history topbar-preview-size 10
org.gnome.shell.extensions.clipboard-history window-width-percentage 33

For me it works (GNOME 44.0 Wayland)
Запись экрана от 2023-04-08 20-32-07.webm


No "enable_ipv6" In Version 3

File: compose/compose-file/index.md, CC @gbarr01
From https://docs.docker.com/compose/compose-file/#enable_ipv6 it says enabling IPv6 is "Not supported in Compose File version 3" but in https://docs.docker.com/compose/compose-file/#ipv4_address-ipv6_address there is still reference to that flag. Also, there is still mention of compose version "2.1".
Is that note/caveat correct in version 3?

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!


chore(main): release 0.6.48

:robot: I have created a release beep boop
0.6.48 (2023-07-04)
Documentation

update BLC to SLC (#176) (327b475)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/rickstaa/stable-gym/releases/tag/v0.6.48 :sunflower:


Made sample type agnostic and GPU compatible

Fixed the issue of sample mentioned in #92.
Closes #92.

@mtfishman I can look around other code in ITensorMPS to see if there is more implicit Float64 typing and open another PR if there is. Thank you @tipfom for your PR!

Thanks @kmp5VT. Also it would be great to start switching some tests over to being able to test on GPU, looping over device backends the same way we do in the NDTensors/ITensors tests. For now it could just test using JLArrays, but ultimately we should also set things up with Jenkins to run the tests on GPUs.

@mtfishman I've replaced all occurances of promote_itensor_eltype by scalartype. Hope that's okay; sorry for the delay.

@mtfishman I've replaced all occurances of promote_itensor_eltype by scalartype. Hope that's okay; sorry for the delay.

Thanks!


Feature Request: Add spelling suggestions to completion menu

When you press z= on a wrong spelling then an entire buffer is opened and you need to enter a number. It would be great if instead you got the selection menu from nvim-compe instead.

z= is a normal command... compe is insert-mode plugin, I think.


intermittent unit/functional test failures in at_client

Describe the bug
1.unit test failure in full_stack_test.dart
https://github.com/atsign-foundation/at_client_sdk/actions/runs/4531205164/jobs/7981075022?pr=978

functional test failure in commit_log_compaction_test.dart
https://github.com/atsign-foundation/at_client_sdk/actions/runs/4534311709/jobs/7988326981

Steps to reproduce
n/a
Expected behavior

unit and functional tests should consistently pass

Screenshots
No response
Smartphones

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Were you using an atApplication when the bug was found?
No response
Additional context
No response

unit test failure fixed by @gkc
in PR https://github.com/atsign-foundation/at_client_sdk/pull/980/files

Another occasional unit test failure (e.g. in this action run) is the following
test/sync_new_test.dart: A group of test to verify sync conflict resolution A test to verify when sync conflict info when key present in uncommitted entries and in server response of sync (failed)
  INFO|2023-05-05 09:53:39.964249|HiveBase|commit_log_38229722d63f456a35120d98f43873a0b9e5bbb2182def930834332b30c118cb initialized successfully

  INFO|2023-05-05 09:53:39.965729|HiveBase|38229722d63f456a35120d98f43873a0b9e5bbb2182def930834332b30c118cb initialized successfully

  INFO|2023-05-05 09:53:40.006089|SyncService (@hiro)|984319571|Returning serverCommitId 3

  INFO|2023-05-05 09:53:40.007212|SyncService (@hiro)|187671533|Returning serverCommitId 3

  INFO|2023-05-05 09:53:40.023724|SyncService (@hiro)|709749291|Inside syncComplete. syncRequest.requestSource : SyncRequestSource.app; syncRequest.onDone : null

  INFO|2023-05-05 09:53:40.024165|SyncService (@hiro)|1014060890|Returning serverCommitId 3

  Expected: SyncStatus:<SyncStatus.success>
    Actual: SyncStatus:<SyncStatus.started>

  package:matcher                 expect
  test/sync_new_test.dart 2874:9  main.<fn>.<fn>.<fn>
  Callback called more times than expected (1).

With the latest changes to the functional_tests, This test isn't failing. Added syncOptions to wait till the key is synced. Changes are in the branch issue#981. Will raise a PR and close the ticket.


Add Metafield Resource

Adds the general Metafield resource (e.g. client.Metafield.List(...))
Adds metafields to Product resource (e.g. client.Product.ListMetafields(...))

Codecov Report

Merging #89 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #89   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          17     18    +1
  Lines         513    577   +64
=====================================
+ Hits          513    577   +64

Impacted Files
Coverage Δ

oauth.go
100% <ø> (ø)
:arrow_up:

metafield.go
100% <100%> (ø)

product.go
100% <100%> (ø)
:arrow_up:

goshopify.go
100% <100%> (ø)
:arrow_up:

util.go
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Sorry, we'll point the PR at another branch and open another PR for the order-related changes as well.

Closing in favor of https://github.com/getconversio/go-shopify/pull/90. This PR inadvertently pointed to our master branch.


feat: add performance metrics commands

Description
This PR does the following changes:

Restore the query_context param in charts to query data from charts programmatically.
Fixes the datasets's Jinja template so that the data is only filtered on the dashboard context where the filters are defined.
Adds a performance-metrics command that queries the data on all the SUPERSET_EMBEDDABLE_DASHBOARDS charts and gets the data needed for performance measurements. Every query performed (by clickhouse-connect) is attached a custom http_user_agent following this format aspects-{ASPECTS_VERSION}-{UUID[0:6]}  so that those can the queries can be retrieved and matched later.

An example output is here for reference:
Superset Reports: aspects-0.86.1-b327bf
    1. Course Grade Distribution
    Superset time: 0.906486 s.
    Query duration: 0.464 s.
    Result rows: 1
    Memory Usage (MB):<PHONE_NUMBER>772705
    Row count Clickhouse 1
    Filters: [{'column': 'emission_time'}]

    2. Distribution Of Hints Per Correct Answer
    Superset time: 2.238558 s.
    Query duration: 1.469 s.
    Result rows: 0
    Memory Usage (MB):<PHONE_NUMBER>8896484
    Row count Clickhouse 0
    Filters: []

    3. Posts per user
    Superset time: 0.131786 s.
    Query duration: 0.007 s.
    Result rows: 0
    Memory Usage (MB): 0.351043701171875
    Row count Clickhouse 0
    Filters: []
...

The following chart and its dataset are created to query the queries performance:

Thanks for the pull request, @Ian2012! Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@Ian2012 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


Sublime doesn't show up in the search bar

Currently the only way to find sublime is to right click a file and then go through the list of programs that can open it. Is there a way to lock it to the launcher beforehand or at least make it show up in the search bar?

This is probably an issue on first statup, probably if you reboot the machine it fixes things.
Not sure what I can do about this but make people wait for a bit (although this may be a way to trigger this manually).

I definitely had rebooted at least 3 times before trying that, I'm wondering if it doesn't recognize it as a program to display in the search bar until you actually launch it for the first time or something weird like that.

I'll take a look at it

I seem to be able to find it on first login (even on the first start). Are you sure you're having this issue?

It definitely didn't show up the first time I searched for it, maybe I just didn't give it enough time to display the results. It shows up every time now.


Fix Max Compression Level in zstd.1

This is also wrong in master.
The file seems outdated, the "--ultra" parameter is also not listed.
Is this man-page still used?

Fair enough.
It's always a problem to manually keep updated multiple separated documentation.
man page format (troff) is also pretty poor. It's far from the simplicity of markdown.
At least, within zstd -h, it's possible to use program constants to have automatic update of parameters such as max compression level.
Thanks for the update Tobias.


[SPARK-30162][SQL] Add PushedFilters to metadata in Parquet DSv2 implementation

What changes were proposed in this pull request?
This PR proposes to add PushedFilters into metadata to show the pushed filters in Parquet DSv2 implementation. In case of ORC, it is already added at https://github.com/apache/spark/pull/24719/files#diff-0fc82694b20da3cd2cbb07206920eef7R62-R64
Why are the changes needed?
In order for users to be able to debug, and to match with ORC.
Does this PR introduce any user-facing change?
spark.range(10).write.mode("overwrite").parquet("/tmp/foo")
spark.read.parquet("/tmp/foo").filter("5 > id").explain()

Before:
== Physical Plan ==
*(1) Project [id#20L]
+- *(1) Filter (isnotnull(id#20L) AND (5 > id#20L))
   +- *(1) ColumnarToRow
      +- BatchScan[id#20L] ParquetScan Location: InMemoryFileIndex[file:/tmp/foo], ReadSchema: struct<id:bigint>

After:
== Physical Plan ==
*(1) Project [id#13L]
+- *(1) Filter (isnotnull(id#13L) AND (5 > id#13L))
   +- *(1) ColumnarToRow
      +- BatchScan[id#13L] ParquetScan Location: InMemoryFileIndex[file:/tmp/foo], ReadSchema: struct<id:bigint>, PushedFilters: [IsNotNull(id), LessThan(id,5)]

How was this patch tested?
Unittest were added and manually tested.

Test build #115211 has started for PR 26857 at commit 72fd2bf.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/20021/
Test PASSed.

Thank you for pinging me. I'll take a look now.

Test build #115211 has finished for PR 26857 at commit 72fd2bf.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/115211/
Test FAILed.

retest this please

Thank you guys!

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/20027/
Test PASSed.

Test build #115225 has started for PR 26857 at commit 72fd2bf.

Test build #115225 has finished for PR 26857 at commit 72fd2bf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/115225/
Test PASSed.

Merged to master. Thank you, @HyukjinKwon and @gengliangwang .


feat!: Upgrade to libbinaryen v110

This upgrades libbinaryen to v110 and adapts the bindings for the changes upstream.
I separated each thing into their own commits so it will be easier for @ospencer to review.

Updated, but waiting on https://github.com/ocaml/opam-repository/pull/22863 to be merged so we can release these breaking updates


Embedded demo install

Goal
Improve adoption by simplifying the getting-started procedure.
Motivation
An example project is critical to getting started with Avalon. The current installation guide works well, except for when you get to uploading the "Batman" example project to Mongo.
Because it's a database and not your typical file hierarchy it requires dedicated tools that you typically don't have on your system unless you follow the guide to the letter and install a temporary MongoDB instance on your machine. To make matter worse. you can't leverage Docker for your Mongo instance, because the guide requires access to one of Mongo's command-line utilities for uploading the project.
Implementation
So I had a thought; why not wrap that process in a Python script that ships with the Avalon install?
# Example
$ pip install avalon
$ avalon --upload batman.json

Bam, all done. Furthermore, with this process within our control, we could easily fetch demo projects straight from GitHub, and download things on-demand as opposed to having everything pre-downloaded as it is at the moment.
$ avalon --demo batman
# Downloading Batman example project..
# Installing Batman..
# Success

Is the entry to Avalon not what https://github.com/getavalon/docker is trying to solve?

Hey @tokejepsen, this would apply there too I think; as you'd still need some way of uploading the example project.
I also realised the above example wasn't clear enough. In the current guide, you call avalon --import batman which in turn calls on the mongodump executable for its upload into the database. What this issue would do instead is use the pymongo Python library to do that, such that you don't need the MongoDB executables.
I'd also like to get rid of Mongo for the initial learning curve; @davidlatwe wrote a mongo emulator I'd like to try here. If we can get to the point where you can just pip install avalon that would be great for adoption. Then there can be advanced options for installing and maintaining a Mongo instance for performance and scale etc.

In the current guide, you call avalon --import batman which in turn calls on the mongodump executable for its upload into the database.

I thought the batman example was using pymongo: https://github.com/getavalon/examples/blob/cb733dbbf7c7adc96c8d7a898a6973c25b3a8da3/import.py#L38 ?

If we can get to the point where you can just pip install avalon that would be great for adoption.

Totally agree. The entry to Avalon is too steep atm.

Oh no, yes it is! The guide is referencing the setup repo, which references an older version of this.

https://github.com/getavalon/examples/blob/764ad2f3308e1123874b3211f489fefc3b0bd77a/import.py#L29

Maybe it's only a matter of updating setup?

Maybe it's only a matter of updating setup?

Quite possibly. I personally would like to see avalon-docker being used, as I see it as an easier environment to manage. We are currently using avalon-docker in production for the database. Have even got a scheduled backup of the avalon database through avalon --backup.


#25361 bip324-cipher-suite

This PR supersedes #20962 and introduces a two-layered cipher suite used in the latest draft of BIP324 (pending public release). The first commit is from #25354 and should be reviewed there.

Inner layer uses RFC8439 which comes with a formal security analysis so any novelty introduced by our cipher suite still offers a baseline confidence in confidentiality and authenticity. The RFC8439 instance is re-keyed every 256 messages for forward secrecy.
Outer layer uses a forward secure version of ChaCha20, FSChaCha20 which re-keys itself every 256 messages for forward secrecy. It is used to encrypt the message length resulting in a pseudorandom byte stream.

rebased -- not making rekey changes

88fa767ccd has new rekeying mechanism


Add docker-build workflow (#942)

Checklist

[x] All new and existing tests are passing
[x] (If docs changes needed:) I have updated the documentation accordingly.
[x] I have added an entry to CHANGES.rst because this is a user-facing change or an important bugfix
[x] I have written proper commit message(s)

What changes does this Pull Request introduce?

This PR adds an automated docker build using GH actions.
Images are build automatically for the following patterns:

PR is opened/updated: builds and tags the image but does not push it to the registry (this is done to verify a successful build; example build)
Push to master (i.e. merge a PR): build and tag image with :latest (example build)
Push a new tag (i.e. release new version): build and tag with

major version only (i.e. :0), and major+minor version (i.e. :0.14) (example build)
full version (i.e. :0.14.1-post.0) (example build)

Furthermore this includes a multi-arch docker build: the image will be build for linux/amd64, and linux/arm64/v8, arguably the most common platforms for both large production environments and small-scale self-hosted applications.
Example image are available via my fork: https://github.com/janw/isso/pkgs/container/isso
Why is this necessary?

Removes necessity to manually build container images, and resolves #942 in the process.

We probably need to work out where exactly we want the docker images to live, GitHub doesn't make it very easy to publish docker images cross-repo.
@ix5 do we want to move the main repo to the isso-comments org at some point

What other repo is there, why not just publish the images to here?

This PR uses the ghcr.io/isso-comments namespace, and I think the plan is also to move this repo to GitHub.com/isso-comments/isso eventually

I talked to @posativ about moving the repo over to the org, but can't quite remember what prevented us from doing that.
PR itself LGTM.

Just to make it clear, this is blocked until we have a decision about moving the repo over to the org.

Just to make it clear, this is blocked until we have a decision about moving the repo over to the org.

could we just publish to posativ/isso in the mean time?

Just to make it clear, this is blocked until we have a decision about moving the repo over to the org.

could we just publish to posativ/isso in the mean time?

That would be fine by me, but I don't have access to the Settings repo tab (for posativ/isso) to add a deploy key as a secret.
I do have access to the isso-comments org and could add the deploy key as an accepted one, just as I have done for the GitHub pages repo (see sso-comments/isso-comments.github.io).
So either way, we're blocked until Martin finds time to act on this.

Just checking in, is there anything you need from me to help move this forward? I'd be happy to assist in any way necessary.

Thanks; I think we're basically just waiting from a response from @posativ

The repo has now been migrated, and references are being updated in #996 so let's land this!

I think it's pretty common in docker that latest just refers to whatever the latest thing that was built and pushed was; the way the latest tag works in docker this is pretty common hard to avoid.
I think that if we want to have a docker tag for the latest release, we should just create a new ":release" tag and update that accordingly.
That said, I think it's good practice for people to specify an explicit version (v1.0) as a tag so that their service don't get silently upgraded whenever they restart their services, including any regressions that may cause.


Prepare azure-monitor-ingestion for beta 2

API change check
API changes are not detected in this pull request.


Please provide more info on modules used and wiring

Hello!
Thank you very much for such a great project! This is exactly what I was looking for since my first drive on my Peugeot iOn. I also really liked you way of connecting it directly to CAN bus without additional OBD adapter.
I would like to reproduce your device as is (first) and I'm also really interested in a ESP32 or Raspberry PI Zero version to be able to upload the odometer and battery data to my smarthome on a regular basis.
Would you please be so kind to share more wiring info and photos, especially on how did you connect and power it?..
The complete BOM and wiring diagram would be just great, but at least some links to exact MCP2515 and an OLED screen modules used, please!
Thank you in advance!

Hi dmit2k !
I was just going to take this free time rainy Sunday to catch up on some projects. I published this one a bit in a hurry, and it is time to complete it. At least, as you said, the wiring. I'll let you know in this github issue by tonight.
Thanks for your nice words, I hope you will iterate on this project. The arduino I used is quite limited, the CAN bus has a high data rate and data are skipped during display refresh...

Thank you for the prompt reply, now impatiently waiting for the wiring! ))
Yes I agree, this arduino is pretty limited in resource, but it is just perfect as a PoC! I was looking for a solution to upload my battery telemetry to my smarthome either by wifi when arriving to my garage or in some realtime manner using my mobile phone wifi hotspot while driving. The idea is to continuously monitor battery health in relation to weather conditions and kilometres driven, as well as individual cells misbalance. Some other useful options could be:

catching DTC errors and alerting them immediately;
triggering on the heater in winter or AC in summer 10 minutes before leaving my office.

But I didn't like the idea of having an OBD adapter always plugged in to the socket (it is easy to break the socket while driving) and I found those adapters very unreliable. Earlier I have had some positive experience with ESP modules and especially modular ESPHome framework. It has everything ready to maintain wifi access or hotspot, provides a web ui and misc displays support, has MQTT client built-in and even has a CAN bus integration:
https://esphome.io/components/canbus.html
I was just looking around on how to put everything together and connect to CAN bus of the car directly when explored your project! ))
So once you will feel ready to rebuild the thing on ESP32 you can evaluate the ESPhome platform )

I've put a schematics/wiring diagram here : https://github.com/pierre-muth/c-zero_dashboard/tree/main/picture_shematics.
Plus some pictures. I've updated the blog post as well.
To summaries.

I wired the two CAN bus lines from the ODB2 plug.
I took the 12V from the radio to not drain the battery.

You can easily find the MCP2515 + transceiver CAN module on ebay, but I struggle to find the exact same OLED screen. Actually you can find the same 2.42" OLED 128x64 I2C module, but with a larger PCB.
It should be even easier with an ESP32, as you said there is a CAN bus interface. Only the transceiver is needed.
Turning on the heater during winter is, to me as well, the start of these procrastination. It is not easy as far as I understood. Cars equipped with the Remote option has 2 additional modules, a RF receiver and a CAN module. On the imiev forum some people are trying to record the full message on the CAN bus when commands from the remote are send. No luck so far.

Forum : https://myimiev.com/forum/viewtopic.php?t=763&sid=0d867ea4a08a17a7b57c030ba32bd9b3&start=170
iMiev workshop manual : http://mmc-manuals.ru/manuals/i-miev/online/Service_Manual/2017/index_M1.htm

I'll have a look on ESPhome, looks promising!
Thanks again, and of course don't hesitate for any question, I'll try to help.

@pierre-muth JFYI:
while waiting for the purchased components to arrive found this note regarding the possible performance issues:
combination with software SPI and the old MCP2515 a high busload will give you a high loss on receiving data packages
...
It would be best to support the CAN Interface inside the ESP32 which has a huge input queue and with hat even on high load a software filter would ne no issue.
https://github.com/esphome/issues/issues/2642
So probably the performance issues you have experienced are not related to Arduino board and it is not the main bottleneck... Rebuilding the project on esp32 looks more and more promising then )

@pierre-muth JFYI:
Found one more project similar to what I'd like to achieve:
https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3
The project is pretty mature but still being actively developed. It is also based on ESP32 chip with custom hardware board (opensourced) and additional interfaces (3G/4G modem, GPS, three (!) CAN buses, etc) + iPhone / Android apps.
What is interesting, it is able to get lots of additional info from i-Miev / C-Zero / iOn cars, it refers some interesting CAN bus IDs that I've not seen elsewhere:
https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/tree/master/vehicle/OVMS.V3/components/vehicle_mitsubishi/src
Maybe this can be useful for you too as I was able to reuse those IDs and calculation methods in my PoC ESPHome/ESP32 project I'm testing right now. Unfortunately, I'm not so good in CPP syntax and can't understand the logic of getting some values of my interest:
static const OvmsVehicle::poll_pid_t vehicle_mitsubishi_polls[] =   {     { 0x761, 0x762, VEHICLE_POLL_TYPE_OBDIIGROUP,  0x01, 		{       0,  10,   10 }, 0, ISOTP_STD }, 	// cac     { 0x765, 0x766, VEHICLE_POLL_TYPE_OBDIIGROUP,  0x01, 		{       0,  10,    0 }, 0, ISOTP_STD },   // OBC     { 0x771, 0x772, VEHICLE_POLL_TYPE_OBDIIGROUP,  0x13, 		{       0,  10,   10 }, 0, ISOTP_STD },   //external/internal temp     { 0x782, 0x783, VEHICLE_POLL_TYPE_OBDIIGROUP,  0xCE, 		{       0,   5,    0 }, 0, ISOTP_STD },   //Trip A/B     POLL_LIST_END   };
As far as I get (and if I'm not wrong), those values require polling them by sending some specific CAN bus frames which is happening within the mi_can_poll.cpp file. But I still can't get the full picture on how to interpret this OvmsVehicle::poll_pid_t syntax to reproduce it in my project...


wip: Install with fsverity

The goal of this PR is to enable in an install config:
[install]
root-fs-type = "ext4"
fsverity = "enabled"

to hard require fsverity for bootc install, and chain it to the ostree config. We're trying to hide the ostree configuration here though.

Needs a rebase, conflicts should be relatively straightforward to fix

Can you explain some scenarios where we might want to have fs-verity disabled?  Is it just on filesystems that can't support it?  Because even without checking the verity data or anything, I find the "this inode is now immutable" thing to be extremely compelling, particularly in the presence of multiple hardlinks....


Feat: Add MyAnimeList support

Describe the feature
Hi there! I would like to add support for MyAnimeList, a popular anime and manga database. I've previously contributed to a similar repository, but it's no longer maintained and I need it for one of my projects.
I will add appropriate tests too.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'24 contributor
[X] I want to work on this issue

i would like to work on this with u.

@A-Ashh, I suggest you look for any other issue or module you want to add. Because I'll not be able to give points to both of you corresponding to a single PR.

Go ahead @shravanasati
Note

Please create a separate module for this, as in the folder and project structure (if it is not already created).
Do not use the `selenium web driver as it is incompatible with all devices and cloud platforms.
Before making any changes, please check whether the module you want to add exists. If yes, then you can add your functionality as a method only make a separate module and class for it.

All the best 👨💻

Thank you @nikhil25803, I might be able to deliver this feature by the next weekend.


Issue with running Calico with libnetwork and coreos

hi
I followed the procedure here to install calico with libnetwork in coreos.
https://github.com/projectcalico/calico-docker/blob/master/docs/getting-started/VagrantCoreOS.md
Iam using coreos alpha 815.0.0 image with Vagrant and Virtualbox. I created 2 node cluster.
I was able to start calico with libnetwork.
When I start the container, I get the following error:
core@calico-01 ~ $ /opt/bin/docker run --publish-service srvA.net1.calico --name workload-A -tid busybox
d9bb4f52ba24e30066de38713419eeab96370f58e33734e4b5dbe478cd417857
Error response from daemon: Cannot start container d9bb4f52ba24e30066de38713419eeab96370f58e33734e4b5dbe478cd417857: failed to set s
tatic route: &{<IP_ADDRESS>/32 1  0}; rolled back
This is the docker version running:
core@calico-01 ~ $ /opt/bin/docker --version
Docker version 1.8.0-dev, build 3ee15ac, experimental
Any ideas?
Thanks
Sreenivas

@smakam Thanks for the bug report.
This is a bug in our code. The problem is with line 110 in https://github.com/projectcalico/calico-docker/blob/master/docs/getting-started/libnetwork/cloud-config/user-data-first
The line needs to be replaced with
wget https://experimental.docker.com/builds/Linux/x86_64/docker-latest

I'm not going to have a chance to test it myself today, but you're welcome to try :smile:

@tomdee
Thanks for your response.
i assume that we also need "mv docker-latest docker" since the next line does "chmod +x docker".
Now, I see that docker service does not get started and i get the following error for docker.service:
Oct 02 17:12:11 calico-01 systemd[1]: Starting Docker Application Container Engine...
Oct 02 17:12:11 calico-01 docker[2151]: flag provided but not defined: --kv-store
Oct 02 17:12:11 calico-01 docker[2151]: See '/opt/bin/docker --help'.
Oct 02 17:12:11 calico-01 systemd[1]: docker.service: Main process exited, code=exited, status=2/INVA
LIDARGUMENT
Oct 02 17:13:12 calico-01 calicoctl[2152]: Traceback (most recent call last):
Oct 02 17:13:12 calico-01 calicoctl[2152]: File "", line 102, in
Oct 02 17:13:12 calico-01 calicoctl[2152]: File "/code/build/calicoctl/out00-PYZ.pyz/calico_ctl.check
system", line 46, in checksystem
Oct 02 17:13:12 calico-01 calicoctl[2152]: File "/code/build/calicoctl/out00-PYZ.pyz/calico_ctl.check
system", line 69, in check_system
Oct 02 17:13:12 calico-01 calicoctl[2152]: File "/code/build/calicoctl/out00-PYZ.pyz/calico_ctl.check
system", line 175, in _check_docker_version
Oct 02 17:13:12 calico-01 calicoctl[2152]: File "/code/build/calicoctl/out00-PYZ.pyz/docker.client",
line 1110, in version
Oct 02 17:13:12 calico-01 calicoctl[2152]: File "/code/build/calicoctl/out00-PYZ.pyz/docker.client",
line 106, in _get
Oct 02 17:13:12 calico-01 calicoctl[2152]: File "/code/build/calicoctl/out00-PYZ.pyz/requests.session
s", line 477, in get
Oct 02 17:13:12 calico-01 calicoctl[2152]: File "/code/build/calicoctl/out00-PYZ.pyz/requests.session
s", line 465, in request
Oct 02 17:13:12 calico-01 calicoctl[2152]: File "/code/build/calicoctl/out00-PYZ.pyz/requests.session
s", line 573, in send
Oct 02 17:13:12 calico-01 calicoctl[2152]: File "/code/build/calicoctl/out00-PYZ.pyz/requests.adapter
s", line 433, in send
Oct 02 17:13:12 calico-01 calicoctl[2152]: ReadTimeout: UnixHTTPConnectionPool(host='localhost', port
=None): Read timed out. (read timeout=60)
Oct 02 17:13:12 calico-01 calicoctl[2152]: Unexpected error executing command.
Oct 02 17:13:12 calico-01 systemd[1]: docker.service: Control process exited, code=exited status=1
Oct 02 17:13:12 calico-01 systemd[1]: Failed to start Docker Application Container Engine.
Oct 02 17:13:12 calico-01 systemd[1]: docker.service: Unit entered failed state.
Oct 02 17:13:12 calico-01 systemd[1]: docker.service: Failed with result 'exit-code'.
Also, I assume that the change you mentioned is also needed for user-data-others.
Thanks
Sreenivas

Good spot on the mv command.
They've renamed that parameter to --cluster-store=. I think the format has also changed to require a // too
So, I think line 70 needs changing now (https://github.com/projectcalico/calico-docker/blob/master/docs/getting-started/libnetwork/cloud-config/user-data-first#L70) to
ExecStart=/opt/bin/docker --cluster-store=consul://$private_ipv4:8500 --daemon --host=fd:// $DOCKER_OPTS $DOCKER_OPT_BIP $DOCKER_OP

And yes to changing user-data-others

hi @tomdee
I made the following change in line 70:
/opt/bin/docker --cluster-store=consul://$private_ipv4:8500 --daemon --host=fd:// $DOCKE
R_OPTS $DOCKER_OPT_BIP $DOCKER_OPT_MTU $DOCKER_OPT_IPMASQ
Now I get this error while starting calicoctl:
core@calico-01 ~ $ sudo calicoctl node --libnetwork
No IP provided. Using detected IP: <IP_ADDRESS>
Unexpected error executing command.
Traceback (most recent call last):
File "", line 102, in
File "/code/build/calicoctl/out00-PYZ.pyz/calico_ctl.node", line 182, in node
File "/code/build/calicoctl/out00-PYZ.pyz/calico_ctl.node", line 326, in node_start
File "/code/build/calicoctl/out00-PYZ.pyz/docker.utils.decorators", line 15, in wrapped
File "/code/build/calicoctl/out00-PYZ.pyz/docker.client", line 1065, in start
File "/code/build/calicoctl/out00-PYZ.pyz/docker.client", line 122, in _raise_for_status
APIError: 500 Server Error: Internal Server Error ("Cannot start container bcf5d4b275cbc8017839c86c3a
64e2277838f9f628e4a81e714539bae08cb706: [8] System error: stat /var/lib/docker/containers/bcf5d4b275c
bc8017839c86c3a64e2277838f9f628e4a81e714539bae08cb706/hosts: no such file or directory")
Looks like there are some incompatibilities with latest docker experimental version?
thanks
Sreenivas

Yes, looks like a docker problem. They're going to be merging a new libnetwork UX soon into docker and exiting experimental. It might be worth holding off a few days until things settle down.

@robbrockbank Did you have a branch that fixes this?

hi folks
Any progress on this? Would this get fixed as part of official Docker release? Any idea when this is expected?
Thanks
Sreenivas

Yes, it will be fixed as part of the docker 1.9 release (which is due on Oct 27 I believe).
If you want to try it out sooner, we'll be releasing a v0.8.0 version of Calico docker shortly - current work in progress is on this branch https://github.com/projectcalico/calico-docker/tree/v0.8.0-candidate
However, we only have it working on Ubuntu and not CoreOS.

I've raised an upstream bug to track this https://github.com/docker/docker/issues/16948

The v0.8.0 release was tested with CoreOS.  This should be working now.  Closing issue.


Prioritize matching build metadata for '=' requirements

This PR makes lz4-sys = "=1.0.1+1.7.3" resolve to https://crates.io/crates/lz4-sys/1.0.1+1.7.3 while lz4-sys = "=1.0.1+1.7.5" resolves to https://crates.io/crates/lz4-sys/1.0.1+1.7.5. Previously, build metadata in a requirement was irrelevant.
This is not in opposition to the semver ranges proto-spec, which has this to say:

Implementations MAY reject Ranges with SemVer strings that include build metadata, but if they do not, then they MUST ignore any build metadata when evaluating versions for inclusion.

Build metadata continues to be ignored when evaluation versions for inclusion (i.e. whether a version is considered matching the version requirement). Build metadata only comes into play once there is a set of multiple matching versions that Cargo needs to choose among, which is not a behavior that is governed by the spec. Versions with a different build metadata are still considered matching, and one may use cargo update --precise to update among them.
  I think everyone is leaning towards not allowing multiple packages that differ only in the metadata string. I think it is fine for this PR to match more tightly, but the intent is to not allow this to happen in the first place.

Could you expand a bit more on the motivation for this as well?

Closing up loose ends from https://github.com/dtolnay/semver/issues/107#issuecomment-848241681. The approach here is based on @sgrif advocating that metadata in = requirements be relevant in https://github.com/dtolnay/semver/issues/107#issuecomment-521760730.

I think it may actually make the most sense for Cargo to print a warning about a version requirement with build metadata, since it's explicitly ignored. I think we could support the cargo update --precise case explicitly to match a very specific build metadata, but otherwise I'd ideally like to follow the semver spec here and simply ignore build metadata.
I sort of wish we didn't even parse it if it's ignored, but that ship is probably sailed so all we can do now is print a warning.

Makes sense. I'll go ahead and close since your description is already how Cargo works. There is a warning for dependency reqs in Cargo.toml containing build metadata, but cargo update --precise still respects the metadata.
https://github.com/rust-lang/cargo/blob/66686fd9951d14019b75e47b3ae0f647c744cb07/src/cargo/util/toml/mod.rs#L1721-L1728

Thanks for following up on that @dtolnay ❤


add task::blocking docs

Adds better docs for #251. Thanks!

Going to merge these changes when CI passes; final touches to docs before we put out #292.


Decrease Dht log level from warning to info or debug

Every 5 minutes (our session/epoch time), our validators logged warnings like this:
WARN sub-authority-discovery Value for hash 'Key(b"\x12 \xde2\x91\x8aVZv\xa7b\x80\xd1ye\x11z)\xbf2\x1aC&*\x83eK\xf0uC\xa5\x03K\xcc")' not found on Dht.
It seems that these log statements do not have any signifcance – can we decrease the log level for them?
Here's a screenshot from our datadog (last 24 hours, validator was started about 14 hours ago):

They use Substrate c6fc2e6240edeb31233b07748c6bf968c7c15553.
CC @mxinden

It seems that these log statements do not have any signifcance – can we decrease the log level for them?

They report that the given authority is not putting their addresses on the Kademlia DHT, or that we have data availability issues within the DHT. The former sounds more realistic, given that this feature is still behind a feature flag.
Both debug as well as warn level sound good to me. Once we have more authorities use the authority discovery feature we can probably go back to warn level.