Fix mimic joint for effort command

Tested with the gripper example.

This PR should close this issue https://github.com/ros-simulation/gazebo_ros2_control/issues/108, isn't it ?

Thank you for your contribution @christophfroehlich

No, I think they are not related to each other.
This one just fixes a typo with the mimic joint, but setting initial positions with the effort interface has still no effect.


somthing wrong with guide/testing/marble-testing#time-progression-syntax

Bug Report
Current Behavior
'a 9ms b 9s c|': on frame 0 emit a, on frame 10 emit b, on frame 10,012 emit c, then on on frame 10,013 complete.
Expected behavior
'a 9ms b 9s c|': on frame 0 emit a, on frame 10 emit b, on frame 9,012 emit c, then on on frame 9,013 complete.

Closing as fixed in #5988.


Bump Rails to 5.2.1

This should be backwards compatible - it has a pretty good compatibility score on Dependabot.

Sorry to ask, do you run Postal to know its backwards compatible?

I haven't run locally because I didn't have mysql installed when creating this. I'll add it now and take a look, but I'm pretty confident.

Also did you mean to also change config/initializers/new_framework_defaults.rb?

Yep - that setting was removed in 5.2. Postal was already setting it to the value that is now the default.

Have spent the last two hours trying to get a mysql install and get the test running, but something's wrong with my setup and I'm getting nowhere. 😢
If you can easily test this then that would be amazing.

I will get this tested myself and get the update out as soon as I can.

I've done this upgrade. Sorry I didn't use this pull request :slightly_smiling_face:

No worries!
Would it be a horrible pain to get Travis/CircleCI set up for this repo? I had a horrible time trying to get the tests to run and it would have made my life way easier. Unfortunately my inability to run the tests locally makes me a bad candidate to submit a PR!


OpenDataCam on Android : Call for beta tester

Hi all 🙌
Some great news to share with you for the start of this 2021, we got a grant a few months ago to start working on a OpenDataCam version running on Android.
This does not mean that the IoT version is deprecated... it just means that we are trying to expand the list of hardware you can run and play with OpenDataCam. As part of the funding we got we are also gonna update the OpenDataCam for Jetsons later this month.
We are ready to start sharing a broader beta test to detect and fix more bugs.. The goal of the beta test will also be to define the minimum CPU requirements in order to run the object detection at a decent speed.
We set-up a mailing list for the beta test, please register below and this week we will be in touch with the link to download the app beta on the google play along with a feedback form.
Link to Register for the beta test
Feel free to ask anything, some more detailed info:

The app code will be Open Source under MIT license after the release
It currently runs Tiny YOLOv4 using NCNN inference framework from Tencent, on CPU .. but can run on mobile GPU too.. just right now NCNN is faster on CPUs

OpenDataCam beta (android version)

Thanks for the help 🙏
Thibault

Super news ! My S8 with a broken screen has been waiting for this in the dust :)

Super news ! My S8 with a broken screen has been waiting for this in the dust :)

I just added a few emails to the beta and sent some instruction on how to get the app, but I noticed lots of email weren't valid google play accounts so if you can't download the app please reach out at<EMAIL_ADDRESS>

I just added a few emails to the beta and sent some instruction on how to get the app, but I noticed lots of email weren't valid google play accounts so if you can't download the app please reach out at<EMAIL_ADDRESS>

@tdurand  Can you point to the source of this particular development.. I am interested in contributing to it.
Is it the mobile branch or the source is not committed yet ?

Hi , thanks for the message. It is not published yet.. working on cleaning things up but should go public in the next weeks.. in the meantime I add you to the beta

@tdurand any updates on source branch being published ?

working on it, should be done this week 😁

just published the OpenDataCam mobile repo & app on google play, thanks for all testers.. Would be nice if you can put some good rating ⭐⭐⭐⭐⭐ on the google play 😉 .
https://github.com/opendatacam/opendatacam-mobile
next step is to update the IoT version and the website.


added github workflows

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6cb4f20). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             master        #1   +/-   ##
==========================================
  Coverage          ?   100.00%
==========================================
  Files             ?         7
  Lines             ?       131
  Branches          ?         0
==========================================
  Hits              ?       131
  Misses            ?         0
  Partials          ?         0

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 6cb4f20...642731d. Read the comment docs.


Need to customize keys.

What have I done before I ask here?
Need to customize keys.

file-browser-keybinds.json > script-opts folder
custom_keybinds=yes > file_browser.conf
s script-binding scroll_down > input.conf
s script-binding scroll-down > input.conf

Unfortunately, nothing changed.

You need to use the file-browser-keybinds.json file to modify the key binds. See the documentation.

I'd like to use two different keys like WHEEL_UP and w just for scroll_up. Is it possible? If yes, how?


[Doc] Branch 2.2, merge all the docs from docs.zh-cn into this repo

Why I'm doing:
merge all the docs from docs.zh-cn into this repo, and keep all the commits
What I'm doing:
merge all the docs from docs.zh-cn into this repo
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[x] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.6 out of 7 committers have signed the CLA.:white_check_mark: amber-create:white_check_mark: evelynzhaojie:white_check_mark: hellolilyliuyi:white_check_mark: DanRoscigno:white_check_mark: EsoragotoSpirit:white_check_mark: jaogoy:x: mergify[bot]You have signed the CLA already but the status is still pending? Let us recheck it.


Feature/xamarin forms navigation unit testing and api adjustments

API adjustments, refactorings and modal navigation support.
Closes #81

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 3
- Added 22

Complexity increasing per file
==============================
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.close.cs  4
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cs  5
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.show.cs  6
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  6
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/NavigationServiceExtensions.cs  2
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cache.cs  4

Clones added
============
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 3
- Added 8

Complexity increasing per file
==============================
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  6
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cs  5
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/NavigationServiceExtensions.cs  2
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.close.cs  3
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cache.cs  4
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.show.cs  6

Clones added
============
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 3

Complexity increasing per file
==============================
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.show.cs  6
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  6
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cache.cs  4
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/NavigationServiceExtensions.cs  2
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cs  5
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.close.cs  3

Clones added
============
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 3
- Added 2

Complexity increasing per file
==============================
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cache.cs  4
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cs  5
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.close.cs  3
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/NavigationServiceExtensions.cs  2
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.show.cs  6
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  6

Clones added
============
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 3
- Added 2

Complexity increasing per file
==============================
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.show.cs  6
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/NavigationServiceExtensions.cs  2
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cache.cs  4
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cs  5
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.close.cs  3
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  6

Clones added
============
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 3

Complexity increasing per file
==============================
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.show.cs  6
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/NavigationServiceExtensions.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cs  5
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cache.cs  4
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  6
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.close.cs  3

Clones added
============
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 3

Complexity increasing per file
==============================
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/NavigationServiceExtensions.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.show.cs  6
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.close.cs  3
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cs  5
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.cache.cs  4
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  6
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1

Clones added
============
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Service/NavigationService.registration.cs  1
- src/Navigation/Xamarin.Forms/Navigation.Xamarin.Forms/Models/NavigationServiceOptions.cs  1

See the complete overview on Codacy


Not working well with Android

Dartpad does not work on Android based mobile.

I'm going to close this in favor of https://github.com/dart-lang/dart-pad/issues/2751 which discusses adding a responsive layout for mobile. There have been recent improvements in https://github.com/dart-lang/dart-pad/commit/7375a5442e854bc20965930271e488fa643634f5 and more are planned. If you experiences issue or have suggestion relative to the current state, please let us know with a new issue and we're happy to accept PRs too. Thanks! <3


Update documentation to reflect new fn signature

https://github.com/onyx-platform/onyx-template/blob/31f05ca5fed17cb1dcab3f307214bdeaaa1e866f/src/leiningen/new/onyx_app/README.md#production claims:

Running onyx in production just requires building an uberjar and running the {{app-name}}.launcher.launch_prod_peers function with an onyx_id and a npeers argument.

... but that function no longer takes onyx_id.

Some other portions in that section looks like they could use updates as well.

Thanks @lvh


The SubscriptionId:"" of the request must match the SubscriptionId "" contained in the Key Vault Id.

If VM is hosted on a different subscription ID than the Key vault following error is encountered:
"The SubscriptionId:"" of the request must match the SubscriptionId "" contained in the Key Vault Id."
Can we add a prerequisite for this doc to have the Windows VM in the same subscription  as the Key vault?
similar to this doc https://docs.microsoft.com/en-us/azure/frontdoor/front-door-custom-domain-https ?
Thank you!

@ElenaMST Thank you for your query . Could you please let me know which document you are referring to and we will have it reviewed.

This is the doc: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/tutorial-secure-web-server
From: ShashiShailaj-MSFT @.>
Sent: Friday, January 28, 2022 2:34 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Elena Stefan @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] The SubscriptionId:"" of the request must match the SubscriptionId "" contained in the Key Vault Id. (Issue #87105)
@ElenaMSThttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FElenaMST&data=04|01|Elena.Stefan%40microsoft.com|3a5c3fcc030e40ef39f408d9e25a6c76|72f988bf86f141af91ab2d7cd011db47|1|0|637789700342451963|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=2%2FvCFO1TFfBfv3LmRiRpevSkUpPuLVVo03LYXS2bVCs%3D&reserved=0 Thank you for your query . Could you please let me know which document you are referring to and we will have it reviewed.

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F87105%23issuecomment-1024172745&data=04|01|Elena.Stefan%40microsoft.com|3a5c3fcc030e40ef39f408d9e25a6c76|72f988bf86f141af91ab2d7cd011db47|1|0|637789700342451963|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=edrEB1vXkd1zibnaCIGKCZ7LV2qdPHEvHqebDa94uog%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXOVDCJ6LWFSNOEGYYFDBK3UYKEKPANCNFSM5NAJI7DA&data=04|01|Elena.Stefan%40microsoft.com|3a5c3fcc030e40ef39f408d9e25a6c76|72f988bf86f141af91ab2d7cd011db47|1|0|637789700342451963|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=gFDlULt2Kw9x7x6dB1ec%2FNr81iKvFdGhJRNnh1QoGVE%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|Elena.Stefan%40microsoft.com|3a5c3fcc030e40ef39f408d9e25a6c76|72f988bf86f141af91ab2d7cd011db47|1|0|637789700342451963|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=6JsbRlzTzs%2BoC3sKPaIgkzbPe5aZ9grtixB2LTlkf7k%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|Elena.Stefan%40microsoft.com|3a5c3fcc030e40ef39f408d9e25a6c76|72f988bf86f141af91ab2d7cd011db47|1|0|637789700342451963|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=2051F29x0b8xq%2F1RyMD3ciP5eLRQ8er0U1Hdu6B5JUo%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

@ElenaMST We have initiated the change request for this issue and the content team will approve or make changes as necessary after their review. Once it is approved , we will see the changes live in the documentation .


could not train VOC2012 datasets by using fcn_train.py

hi, i installed the VOC2012 datasets in "fcn/data/pascal/VOC2012", and put the "vgg16.chainermodel" on "fcn/data", all i want to do is train the VOC2012 datasets, but it failed, what's the problem?

Thank you for the report.
@jinhang #45 will fix it.

i have read the closed problem #20, you succeed in training datasets.  where is the difference, environment or code, thank you!

I merged #45 right now. Please try the training script again.

i will try, thank you!

it works, thank you!


HDDS-11285. cli to trigger quota repair and status

What changes were proposed in this pull request?
CLI option to trigger repair and also check status:
ozone repair quota status [--service-host=<omHost> ] [--service-id, --om-service-id=<omServiceId>]

ozone repair quota trigger [--buckets=<buckets>] [--service-host=<omHost>] [--service-id=<omServiceId>]

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-11285
How was this patch tested?

Unit test case is added

./ozone repair quota trigger --service-host=localhost
ATTENTION: Running as user sumitagrawal. Make sure this is the same user used to run the Ozone process. Are you sure you want to continue (y/N)? y
Run as user: <supressed>
{"bucketCountDiffMap":{},"lastRunFinishedTime":0,"lastRunStartTime":1724236779363,"taskId":1,"errorMsg":""}

./ozone repair quota status --service-host=localhost
ATTENTION: Running as user sumitagrawal. Make sure this is the same user used to run the Ozone process. Are you sure you want to continue (y/N)? y
Run as user: <supressed>
{"bucketCountDiffMap":{},"lastRunFinishedTime":1724236779748,"lastRunStartTime":1724236779363,"taskId":1,"errorMsg":"BUCKET_NOT_FOUND org.apache.hadoop.ozone.om.exceptions.OMException: no matching buckets"}

./ozone repair quota status --service-host=localhost
ATTENTION: Running as user sumitagrawal. Make sure this is the same user used to run the Ozone process. Are you sure you want to continue (y/N)? y
Run as user: <supressed>
{"bucketCountDiffMap":{},"lastRunFinishedTime":1724236894205,"lastRunStartTime":1724236893883,"taskId":1,"errorMsg":""}

@sumitagrawl , is it allowed to submit multiple quota repair commands in the same time?

@sumitagrawl , is it allowed to submit multiple quota repair commands in the same time for different buckets?

No, its not allowed. As this operation is resource intensive, so allowed one quota repair task at a point of time.

The last patch LGTM.  Thanks @sumitagrawl.  One further suggestion is can we display the lastRunFinishedTime and lastRunStartTime in a human readable format?

The last patch LGTM. Thanks @sumitagrawl. One further suggestion is can we display the lastRunFinishedTime and lastRunStartTime in a human readable format?

Handled, now output sample,
{"bucketCountDiffMap":{},"lastRunFinishedTime":"","lastRunStartTime":"Thu Sep 05 10:28:59 IST 2024","taskId":1,"errorMsg":""}
{"bucketCountDiffMap":{},"lastRunFinishedTime":"Thu Sep 05 10:29:00 IST 2024","lastRunStartTime":"Thu Sep 05 10:28:59 IST 2024","taskId":1,"errorMsg":"BUCKET_NOT_FOUND org.apache.hadoop.ozone.om.exceptions.OMException: no matching buckets"}


Support KNIGHT (Echo Show) devices

Problem
Right now, the plug-in only allows ECHO-family devices and they're created as SPEAKER accessories with a SmartSpeaker service. KNIGHT-family (Echo Show) devices are filtered out.
Solution
KNIGHT-family devices should be supported, but since they have a screen, I'd like to create the accessory as a TELEVISION and Television + TelevisionSpeaker services instead.
Alternatives
Alternatively, the could be registered as speakers like the rest.

what is the advantage of TV-Service? I think the Shows are only Music-Player with screen, there is no real "Video-Service", only special Video-Skills, so the show won't act like a tv (channel up/down, EPG and so on..) I don't believe there are special commands that it shows lyrics when playing music or the covers etc.
Maybe you make it optional to set it as a speaker or TV. Maybe i am just wrong or its only the small echo show 5 that can't do other stuff than play music (in first place)...

There shouldn't be any disadvantages to making it a TV service. All of the same characteristics (volume, mute, media state, etc.) are available, with options for more that might apply (brightness?). Additionally, you can specific inputs for a TV, so it's possible I could add video skills as TV inputs.

I just released v0.3.0, which includes support for KNIGHT devices as smart speakers. There's also an option to enable representing them as televisions, but it doesn't quite work yet.

Knight support works for me. I updated to 0.3.0 this morning and added my Echo Show. Thanks!

You can add the echo show but the power button when set as TV cannot pause/play or start music. ( haven't tried without TV - can you add it as a regular speaker like the others when TV option in config is set to no?). The regular speakers can pause/play but not the show devices.


Download button not working using Firefox/Chrome/Edge

Hello,
as stated in the title the download button isn't working for me. Nothing happens if I click on it.
Since it doesn't do anything besides changing the style of the button if the mouse hovers over it I can't provide screenshots or error messages.
Probably related to #13
If I remember correctly a few weeks ago it worked fine but I'm not sure about that.

Okay thanks for your report man ;D @gh7531.
I'll see how i can fix this up.

It's due to github raw.. I included my js file from it.. @gh7531


Write a JavaScript program to convert string to pascalcase

Description
Write a JavaScript program to convert string to pascalcase
Pascalcase is a style of writing in which the first letter of each word is capitalized.
Input  : "hello world"
Output : "HelloWorld"

How to contribute

Save the solution in program/ConvertStringToPascalcase.js file
Add ConvertStringToPascalcase.js file in convert-string-to-pascalcase folder

!assign


add the docs to make a new device

Fixes #578
Instructions to reviewer on how to test:

Do thing x
Confirm thing y happens

Checks for reviewer

[ ] Would the PR title make sense to a scientist on a set of release notes
[ ] If a new device has been added does it follow the standards
[ ] If changing the API for a pre-existing device, ensure that any beamlines using this device have updated their Bluesky plans accordingly
[ ] Have the connection tests for the relevant beamline(s) been run via dodal connect ${BEAMLINE}

the  tests are failing because of an ophyd-async issue


Custom acme resolv conf

What this PR does / why we need it:
Adds the ability to use different DNS servers to check for ACME TXT records.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

NONE

Kubernetes 1.9 adds an alpha dnsConfig field to the Kubernetes pod spec, which would alleviate the need for this feature: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pods-dns-config
I'm inclined to suggest we do not use it in favour of the upstream functionality. Would this satisfy your use-case?

I agree, that should work instead of this.
We would need to test it to see if it works for our setup.
We run Tectonic and it hasn't released 1.9 yet so we can't test much till them.

I'm going to close this for now as there is also #261 tracking the new implementation of this feature. Feel free to re-open if you disagree!

@munnerz, i've tested dnsConfig with 1.9.7. I've added the following on deployment.yaml:
      dnsPolicy: "None"
      dnsConfig:
        nameservers:
          - <IP_ADDRESS>
          - <IP_ADDRESS>

I've also added --feature-gates=CustomPodDNS=true to api-server. But it doesn't work in this environment:
k -n cert-manager exec cert-manager-5d97bc9b66-hh7fl cat /etc/resolv.conf
nameserver <IP_ADDRESS>
search cert-manager.svc.cluster.local svc.cluster.local cluster.local
options ndots:5

do you have tested this dnsConfig feature?

Ok, i've forgot to add "--feature-gates" to all other services like: kube-scheduler, kube-controller-manager, kube-proxy, kubelet :) Now i have:
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>


Add test_genesis.py and fix is_genesis_trigger

Fix #1199

is_genesis_trigger

Fix the incorrect variable name.
Instead of using state.eth1_data.deposit_root, the validators have to create the genesis_deposits with proof on the latest deposit tree root and pass it to process_deposit.

get_genesis_beacon_state

Instead of using state.eth1_deposit_index, pass deposit_index of the given deposit to process_deposit.

Add test_genesis.py

@hwwhww What do you think of https://github.com/ethereum/eth2.0-specs/pull/1202/commits/a3f8f50beed9f66801ce266b192b234c2dd11299?

@JustinDrake
In practice, a client, they would probably:

Build deposit_data_list: List[DepositData] from deposit contract log.
Generate proof against the latest deposit_root (can be gotten from the contract, or just merkleize the deposit_data_list).
Build the deposits: List[Deposit] with these proof.
Check the if it's triggered the genesis starting point.

So it's unlikely they would need to regenerate deposit_root after they have created the Deposits, in practice. That's why I'd say we don't need to regenerate the deposit_root again.
Another way to describe the logic is changing the function to def is_genesis_trigger(deposit_data_list: List[DepositData], timestamp: uint64) -> bool, and generate the proof in this function. I hope to balance between (i) making the spec describe the protocol in details and (ii) making it too far from practice. 😄
What do you think about it? 😸

Right. In practice I expect implementers to have a cache (e.g. a Store mapping deposits to beacon states) and an incremental version of is_genesis_trigger. This would avoid recomputing things from genesis, and handle Eth1 reorgs. I'd favour spec readability over efficiency, but don't feel too strongly either way :)

fixed the merge from Justin, it was broken:

introduced back an invalid deposit test, we don't have deposit.index anymore
syntax problem, decorator was over empty line
confusing big merge, few merge conflicts, but know not to pick the old(!!!) diff parts, when they changed intentionally...

Moved genesis tests out of sanity. The idea is that the shape of each test is the same within one file.
Annotated the yielded data, so that it actually gets into a dict of key-value for a future test generator
Fixed the genesis-trigger-true tests partially. Date was the same as the false case...
Introduced local SECONDS_PER_DAY constant. You can make it a real global, but if it's for an "example" part of the code, we shouldn't include it in the main constants imho.
Fixed problems with python syntax, map was used wrong, and generator (... for ... in ...) results were used as if it were lists (they are types.GeneratorType)
The Deposit-root for the truee-trigger is still wrong somehow, but something for you to figure out, may be the expected root that is wrong, or some other funky reason more familiar to the PR authors

Where do we stand on this PR? One test fails. Are any changes and/or this test being worked on still?

@hwwhww is working on it. She's been liaising with me and I'm expecting a push soon.

Reviewed and debugged it.
Findings:

proofs are constructed for the whole tree, not up to the given deposit.
but eth1 deposit root changes per deposit
the full vector hash-tree-root doesn't work, since input is not padded, hence invalid.

1 is solved by adding a special create_merkle_proof_up_to that creates the proof based on part of the tree.
2 is ok, but slow, and coincides with the solution for 3. I recommend changing it to:
    leaves = list(map(lambda deposit: hash_tree_root(deposit.data), deposits))
    for i, deposit in enumerate(deposits):
        state.eth1_data.deposit_root = merkleize_chunks(leaves[:i], pad_to=2**DEPOSIT_CONTRACT_TREE_DEPTH)
        process_deposit(state, deposit)

Alternatively we do a full root, don't change it every deposit, and construct proofs for each deposit by the full tree. But this is not very accumulator like. But valid enough for genesis.

In the end, get_merkle_root is back

I don't understand. Isn't this unnecessary complexity, and go against what we discussed?

Thanks @protolambda!
@JustinDrake as @protolambda mentioned, both SSZ List and Vector are not the normal merkleization that we can use directly. The Vector will initialize the sparse tree with DepostData() instead of ZERO_HASH. And to use List, we might need an extra "flag" in hash_tree_root to escape from mix_in_length, which I don't think it's idea too...
For the merklization, I think it's reasonable to migrate most of these merkle_minimal.py logic with https://github.com/ethereum/eth2.0-specs/blob/dev/specs/light_client/merkle_proofs.md someday when we make light client protocol executable.

Sorry for the delay of this PR!!! I will have time to clean up it at the 29th afternoon (Asia).
TODO thoughts:

is_genesis_trigger and get_genesis_state are really similar. I'm thinking either (i) using one function to check and get the genesis state altogether or (ii) using the result from is_genesis_trigger() as the input of  get_genesis_state().
Clean up merkle_minimal.py code

Added signed=True args to make it work with BLS
Added a few remarks to avoid confusion in genesis/deposit verification

Ready to merge imho. We can add a few additional tests after spec-freeze. Possibly even improve the efficiency of genesis construction. As clients are (very) likely not implementing it like this anyway, and state output will be the same. This description and pseudocode will at least set a baseline, and set the interface to be compatible with SSZ partials in the future.


NETOBSERV-1151: move flp decode grpc pipe to netobserv agent

move FLP grpc decode logic to the agent to just limit flp to pkg update w/o need to do any code changes
depends on https://github.com/netobserv/netobserv-ebpf-agent/pull/168

/ok-to-test

/approve


Support flushing database once per second

fixed in https://github.com/JetBrains/imperative-nodejs/commit/e8d31533bfd8a0e1c070bdc3aaaa4cb4452be408


Escape IRIs and literals

Big fan of your work in Linked Data and we use your projects throughout our services. The workflow requires to generate SPARQL queries to be executed on a QPARQL endpoint and I use would like to use a library to produces strings from RDF.JS objects. When using this library, I got stung by incorrectly escaped literal strings, which caused the SPARQL queries to be syntactically incorrect. This problem would also affect writing to TTL and N-triples files. This issues is also mentioned by https://github.com/rubensworks/rdf-string-ttl.js/issues/1.
With this pull request, I would like to propose a solution for escaping special characters such as newlines, " and such as implemented by the amazing N3.js project. In fact, the escaping function and the escape characters are a copy of the ones they use. I have also included some tests for this new functionality, also based on their tests.
NOTE:

This PR is based on the previous PR about moving to ESLint from deprecated TSLint.
I don't know the implications of copying a function from another project, licensing wise.
This my first attempt at writing TypeScript, my "type-foo" is not up to speed yet.

Thanks so much for this @benjay10!

I don't know the implications of copying a function from another project, licensing wise.

We shouldn't copy code directly from other projects. This will cause licensing issues indeed.
What we can do however, is implementing things similarly by looking at the code of other projects.
In any case, let's merge #3 first.

I came up with a different approach, that actually looks very similar to what rdflib.js does. I only found out while already implementing my idea, so this is a confirmation it should be correct(?). (This can be found here.) This time only backslashes, double quotes and newlines are escaped, and only from string literals. This seems in line with the Turtle spec here.
There is of course another possibility: using """ for encoding strings with newlines, but we would still have to escape backslashes and also check that the string does not contain any """ itself, or we would have to fallback to full escaping everything.

I came up with a different approach, that actually looks very similar to what rdflib.js does. I only found out while already implementing my idea, so this is a confirmation it should be correct(?). (This can be found here.) This time only backslashes, double quotes and newlines are escaped, and only from string literals. This seems in line with the Turtle spec here.

It's simpler indeed, but I think it's not going to be correct for all cases.
For example, \\n would not be additionally encoded in this approach, even though it should be. Because upon decoding, \\n will be converted to \n, which is not what the original value was, so we lose correct round-tripping.
So I think we'll need an approach similar to the previous one to handle these cases.

I'm easily confused with all these escape character, so please bear with me.
If you want the literal to contain \\n, shouldn't that be encoded as \\\\n? I wrote a test for that locally and it seems to work this way, it also seems to be implemented like this in rdflib.

If you want the literal to contain \n, shouldn't that be encoded as \\n? I wrote a test for that locally and it seems to work this way, it also seems to be implemented like this in rdflib.

Yes, you're right. If this already works, then great :-)
What I'm still concerned about is the performance impact.
The previous version was implemented in O(n), while the new one is O(4*n) (n is string length) (since each replaceAll call iterates over the full string).
Also surrogate pairs and 4-bit unicode escape sequences are not handled anymore.

Scanning the string and replacing characters will always have a performance impact, so yes, the performance will be worse with any of the suggestions so far, but we somehow have to because producing incorrect TTL strings is just not OK.
I think your analysis of performance is not correct. Yes, it looks like the string is iterated 4 times, but if you only where to do it once, you would have to combine all the work in a singular, more complex function that might take 4 times as long as one of these simpler functions (or even more due to the increased amount of if or switch cases). I didn't do any research, but maybe simple regex are executed with native code in some JavaScript interpreters and would outperform the complexer replace with a handler function. If performance is so important, then we should really empirically compare several methods.
Also, according to the Turtle specification, there is no mention of surrogate pairs or these 4-bit unicode escape sequences not being allowed. Just mentions about the delimiter characters for strings and newlines, because they would interfere with the Turtle syntax itself. If these special characters are allowed in a Turtle file (given its encoding), are they still problematic?

so yes, the performance will be worse with any of the suggestions so far, but we somehow have to because producing incorrect TTL strings is just not OK.

Yes, we agree on the incorrectness issue :-)
But your first suggestion looked fine performance-wise.

If performance is so important, then we should really empirically compare several methods.

Sure, sounds good!

Also, according to the Turtle specification, there is no mention of surrogate pairs or these 4-bit unicode escape sequences not being allowed.

This is implied by its dependency on unicode, just like SPARQL.
See for example these related SPARQL spec tests: https://github.com/w3c/rdf-tests/pull/65 https://github.com/w3c/rdf-tests/pull/67

Reverted back to the more complex escaping situation, but slightly rewritten. Is this enough to not infringe on the licenses? Is this somewhat of a final result you had in mind?

Thanks @benjay10, that approach looks good to me!
Could you rebase your PR onto master? It looks like the linter changes also slipped in here from your previous PR.

I hope this is okay. The merging got complicated because the linting changed the regular expressions and some tests started failing because of it (hence the eslint-disable directives).


[RFC] Versioning changes for hard fork

An RFC describing changes we'd want for the versioning mechanism in advance of the hard fork.
Closes #10964.

I think we can add the top tag layer when we need it later ... but not opposed to including them if others think strongly that it makes sense.

The RFC is suggesting generating the top-tag module only on-demand, when the appropriate annotation appears.

Based on the text fields in the archive db schema in compatible, the types whose Base58Check serializations must not change are:

public keys
signed command memos
snarked ledger hashes
transaction hashes
epoch data seeds
state hashes
ledger hashes

attn: @deepthiskumar

Took a look at @deepthiskumar 's request, and I'm happy as long as @nholland94 and @bkase are happy. I agree that the existing versioning is overkill (and the CI job is too picky) but any new solution needs to be easy to work with day-to-day in the codebase and I defer to the ocaml pros for that.

any new solution needs to be easy to work with day-to-day in the codebase

I think that comparing against both the release branch + base branch, as I suggested here, will avoid almost all linter noise:
https://github.com/MinaProtocol/mina/pull/11093#discussion_r884022238


unable to create NetworkSecurityGroup using api

code sample is below:
NetworkSecurityGroup nsg = new NetworkSecurityGroup();
      nsg.setName("testnsg");
      nsg.setLocation(context.getLocation());
      SecurityRule sr= new SecurityRule();
      sr.setPriority(100);
      sr.setProtocol("*");
      sr.setSourceAddressPrefix("*");
      sr.setSourcePortRange("*");
      sr.setAccess("Allow");
      sr.setDirection("Inbound");
      sr.setDestinationAddressPrefix("*");
      sr.setDestinationPortRange("*");
      ArrayList<SecurityRule> srs = new ArrayList<SecurityRule>();
      srs.add(sr);

      nsg.setSecurityRules(srs);
      networkResourceProviderClient.getNetworkSecurityGroupsOperations().createOrUpdate(resourceGroupName, nsg
          .getName(), nsg);

server return
PROPERTIES
statusCode:BadRequest serviceRequestId:b9c90aed-1e3d-4708-ae5b-f9dc03560d62 statusMessage:{"error":{"code":"InvalidRequestFormat","message":"Cannot parse the request.","details":[]}} responseBody:{"error":{"code":"InvalidRequestFormat","message":"Cannot parse the request.","details":[]}}

looks like * was remove from the string.

In the request payload security group section appear as
"securityGroup: [ { properties: { "name": ... , ... }, ..]]"
I think it should be:
"securityGroup: [ { { "name": ... , ...}, ...]"
will confirm whether this is a bug in SDK.

@netwmr01 you have to specify a name for the rule
sr.setName("nsgrule1");
@jianghaolu fyi this is not a SDK issue, so no need to patch it.

@anuchandy @jianghaolu without rule, the NSG creation will still failed. so user have to create a rule? but base on rest api and portal, user don't need to creat rules for NSG to be created.

I just tried creating nsg without rule as below and it worked
NetworkResourceProviderClient networkResourceProviderClient = NetworkResourceProviderService.create(config);

        NetworkSecurityGroup newNsg = new NetworkSecurityGroup();
        newNsg.setName("nsg3");
        newNsg.setLocation("eastus");
        networkResourceProviderClient.getNetworkSecurityGroupsOperations().createOrUpdate("nsggrp", "nsg3", newNsg);

sever payload:
{"properties":{"securityRules":[],"defaultSecurityRules":[]},"name":"nsg3","location":"eastus","tags":{}}

@anuchandy @jianghaolu
It will fail when you attach to a nic and creat vm. on 0.9.3

Can you share full repro code?

@anuchandy @jianghaolu
NetworkSecurityGroup nsg = new NetworkSecurityGroup();
nsg.setName(nsgName);
nsg.setLocation(context.getLocation());
networkResourceProviderClient.getNetworkSecurityGroupsOperations().createOrUpdate(resourceGroupName, nsg.getName(), nsg);
NetworkHelper.createVirtualNetwork(networkResourceProviderClient, context);
/*
* some context setting in between
* */
computeManagementClient.getVirtualMachinesOperations()
.beginCreatingOrUpdating(
context.getResourceGroupName(),
context.getVMInput()
);
You will find the following ERROR:
com.microsoft.windowsazure.exception.ServiceException: InvalidRequestFormat: Cannot parse the request.

@netwmr01 thanks.. you mentioned that "It will fail when you attach to a nic and creat vm". In the above repo sample I don't see where exactly we are setting the NSG to VM/NIC. Am i missing something?

@anuchandy That is in additional context setting
// Currently sdk created NSG will fail. Update NIC to use existing NSG is fine.
ResourceId id = new ResourceId();
id.setId(nsg.getId());
context.getNetworkInterface().setNetworkSecurityGroup(id);
networkResourceProviderClient.getNetworkInterfacesOperations().createOrUpdate(context.getResourceGroupName(),
context.getNetworkInterfaceName(), context.getNetworkInterface());

@netwmr01 please see below working code:

            NetworkResourceProviderClient networkClient = createNetworkClient();

            // Create NSG
            //
            NetworkSecurityGroup nsg = new NetworkSecurityGroup();
            nsg.setName("nsg2");
            nsg.setLocation("eastus");

            SecurityRule rule = new SecurityRule();
            rule.setName("rule1");
            rule.setPriority(100);
            rule.setProtocol("*");
            rule.setSourceAddressPrefix("*");
            rule.setSourcePortRange("*");
            rule.setAccess("Allow");
            rule.setDirection("Inbound");
            rule.setDestinationAddressPrefix("*");
            rule.setDestinationPortRange("*");

            ArrayList<SecurityRule> rules = new ArrayList<>();
            rules.add(rule);
            nsg.setSecurityRules(rules);
            networkClient.getNetworkSecurityGroupsOperations().createOrUpdate("nsggrp", "nsg2", nsg);

            // Create virtual network
            //
            VirtualNetwork vnet = new VirtualNetwork();
            vnet.setName("vnet1");
            vnet.setLocation("eastus");

            AddressSpace addressSpace = new AddressSpace();
            ArrayList<String> addressPrefixes = new ArrayList<>();
            addressPrefixes.add("<IP_ADDRESS>/24");
            addressSpace.setAddressPrefixes(addressPrefixes);
            vnet.setAddressSpace(addressSpace);

            Subnet subnet = new Subnet();
            subnet.setName("subnet1");
            subnet.setAddressPrefix("<IP_ADDRESS>/24");
            ArrayList<Subnet> subnets = new ArrayList<>();
            subnets.add(subnet);
            vnet.setSubnets(subnets);

            networkClient.getVirtualNetworksOperations().createOrUpdate("nsggrp", "vnet1", vnet);

            // Gets the subnet
            Subnet s = networkClient.getSubnetsOperations().get("nsggrp", "vnet1", "subnet1").getSubnet();
            ResourceId subnetResourceId = new ResourceId();
            subnetResourceId.setId(s.getId());

            // Gets the NSG
            NetworkSecurityGroup n = networkClient.getNetworkSecurityGroupsOperations().get("nsggrp", "nsg2").getNetworkSecurityGroup();
            ResourceId nsgResourceId = new ResourceId();
            nsgResourceId.setId(n.getId());

            // Create network interface
            //
            NetworkInterface nic = new NetworkInterface();
            nic.setName("nic1");
            nic.setLocation("eastus");

            NetworkInterfaceIpConfiguration nicIPConfig = new NetworkInterfaceIpConfiguration();
            nicIPConfig.setName("Nic-IP-config");
            nicIPConfig.setSubnet(subnetResourceId);

            ArrayList<NetworkInterfaceIpConfiguration> nicIPConfigs = new ArrayList<>();
            nicIPConfigs.add(nicIPConfig);

            nic.setIpConfigurations(nicIPConfigs);
            nic.setNetworkSecurityGroup(nsgResourceId);

            networkClient.getNetworkInterfacesOperations().createOrUpdate("nsggrp", "nic1", nic);

No action to take at this moment.
With 1.0.0-beta2 released, this should be simplified. A sample can be found here: https://github.com/Azure-Samples/network-java-manage-network-security-group/blob/master/src/main/java/com/microsoft/azure/management/network/samples/ManageNetworkSecurityGroup.java.
@selvasingh

@anuchandy @jianghaolu without rule, the NSG creation will still failed. so user have to create a rule? but base on rest api and portal, user don't need to creat rules for NSG to be created.

A valid scenario to be added.

@jianghaolu this sample is absolutely not simplified.  Think of this case:
I want to write an application to deploy resources, including the network, NSG and rules contained in the NSG.  The newer syntax removes any possibility of me being able to write methods to add security rules that are not VERY strictly defined.
There is no method to add ACCESS, beyond "allowInbound, denyInbound, allowOutbound, denyOutbound".  There's no way for me to pass in the Access type without calling those methods from code... this means if I want to be able to have a rule created dynamically, I have to have every possible combination (allow inbound with all ports, allow inbound with a specific inbound port, with a specific destination port, allow inbound with a specific destination port but any source port... etc)  This ends up being A VERY LARGE number of methods, with a very complicated control structure to determine which method to call.
Why is there no way to create a rule, pass it a variable that is the access type, a variable that is the direction, a variable that is the source port (which must be string to allow it to be a single port, a range, or * for any), a variable that is destination port, a variable that is protocol?
It appears there used to be, and now the usage is extremely broken.  I'm not sure I will be able to meet my needs with this SDK now...


Error on login

Hi,
When I try to login using the account I created at the installation, it always tells me "invalid creditentials", but they're right!
How to fix that?

hello, all work right on my test server, maybe you have some error logs?

oh okay, just looking now, you try login as admin in user panel, but need use \admin\login address

Hello, yes that was that problem!
I'm so silly...
Thanks!
I had another question, is there a file where all the translations are written in and that we can share?

Look at here https://github.com/superwow/hopebilling/tree/master/template/front/default/i18n


Group detail - Permission tab UX changes

Fixes https://issues.redhat.com/browse/AAH-364
This contains multiple UX changes to the Group detail screen, mostly in the Permissions tab:

moved the Edit, Save and Cancel buttons from page header to tab header, as these are only related to the tab
keeps the Delete button as is, but disables it when editing a group, and no longer hides it on the users tab
makes the tabs appear disabled (cursor + no action on click) when editing Permissions
sorts the list of available permissions in the Permission selects (note this makes the order unstable between translations once we have i18n)
use plain text styling (remove gray blocks behind input text) unless in edit mode (this is from https://issues.redhat.com/browse/AAH-360 but consistency)

Cc @ZitaNemeckova, @sbuenafe-rh, this should be ready for review :)

Permissions tab in view mode (before and after):

Permissions tab in edit mode (before and after):

(the tab header also switches to the not-allowed cursor when hovering in edit mode)
List of group permissions when editing (before and after):

Users tab (before and after):

Updated to match the labels screenshot, thanks! :)
And added a tab title when disabled, except "you must" felt a bit strong, wdyt?..

And moved the Save & Cancel buttons down, and changed to primary+secondary (from default+link) as in the editor (is that what we want to settle on?);  leaving the Edit button as is..


[SPARK-46378][SQL][FOLLOWUP] Do not rely on TreeNodeTag in Project

What changes were proposed in this pull request?

This is a followup of https://github.com/apache/spark/pull/44310 . It turns out that TreeNodeTag in Project is way too fragile. Project is a very basic node and very easy to get removed/transformed during plan optimization.
This PR switches to a different approach: since we can't retain the information (input data order doesn't matter) from Aggregate, let's leverage this information immediately. We pull out the expensive part of EliminateSorts to a new rule, so that we can safely call EliminateSorts right before we turn Aggregate into Project.
Why are the changes needed?

to make the optimizer more robust.
Does this PR introduce any user-facing change?

no
How was this patch tested?

existing tests
Was this patch authored or co-authored using generative AI tooling?

no

cc @dongjoon-hyun @viirya @ulysses-you

Test failure looks unrelated?

Yea the pyspark failure is unrelated. Thanks for the review, merging to master!

This once again breaks writing sorted partitioned files, last time broken with 3.0.0 and fixed in 3.3.2: #38358, #39431.
When the user calls
ds.repartition(partitionColumns: _*)
  .sortWithinPartitions((partitionColumns ++ sortColumns): _*)
  .write
  .partitionBy(partitionColumns: _*)
  .parquet(...)

then the in-partition sort by sortColumns is not redundant but desired.

@EnricoMi yes, will be fixed soon.

Thanks!


Replace config.xml with a device settings screen

We want to move away from using config.xml to make all device settings configurable via UI on device.
To do this we would want to have a device settings screen.
Based on comments in discord, it would be good to also be accessible without needing to first open a project.

💯 Agree with this, I keep wanting to have a general Settings page for those settings that reach over the app vs. project.
I don't think we need to get rid of config.xml however xml reading/writing is quite processor heavy and I think there are probably better formats.
I do prefer to keep the settings file on the SD Card, because that makes more sense, also allows users to back them up or share their settings instead of keeping them in flash.
Also would prefer to keep as much out of flash due to the limitations we currently have.
I might mock up some ideas for Settings here (including location, accessibility, etc)

@shockdesign Well for me the pro to having config.xml is its human readable/editable but otherwise theres lots of cons like the code it takes to support reading/writing xml and ram usage (even using SAX) and really once you have a UI and say store in a binary format you can still export to a simple binary format for backups/sharing without needing to keep a "heavy" format like xml.
The question of where to store flash vs sdcard is an interesting one! To me it makes sense to store on flash but I'm not strongly opposed to being on sdcard either as currently its not possible to use a device without a sdcard installed.
I think before mocking up a UI, the more important thing is to decide on a implementation for device settings, the question of where its stored, data format, etc. TBH for me the UI layout is the easiest & last piece to work on for this task.

@maks I love the idea of a human readable/editable config... but I think there are better options for text parsers than XML.
A binary file could work, but yes, becomes very propriety and harder to decipher.
Just realised that the project save files are XML too, so if we want to go through to the process of implementing a lightweight parser, we might want to the change and convert the save files (whether thats another simple Python parser).
If we're going to have to support XML as a format going forward tho, then we might as well keep that.
@democloid Thoughts? Should we try and remove the XML parser and change the format of the save files to streamline things better for the Pico?

I can't find a compeling reason to remove the parser or change the format. I'm no XML lover, but it works and it's open, which is important. The way it's implemented is also pretty nice in that each component saves it's own configuration and appends it to the final file, so it should be pretty easy to support saving and loading instrument settings for example. Memory wise I don't think that it's a bit offender, should be pretty efficient.
On the down side, a malformed file may crash the device, but that's a problem of the implementation, not the format.
In terms of config save I strongly believe it should go into the flash. But I could see a reason to want to at least export it if the config gets more complex.
To the mention that the device requires an SD card anyway, what if it didn't? not super high pri, but would be nice to me to be able to turn on a cardless device into a new project and be able to use factory samples and whatnot for an ephemeral experience 😀

Yes good points all round. I keep forgetting about project files being in xml, so yes, no sense to replace it and Ive got lots more interesting things I'd like to work on so no real motivation to replace the xml support with anything else, so I take back by suggestion for a alt binary format for storing config either.
That perhaps points to a first iteration of the device settings: as just exposing existing editing & saving config.xml settings.
Finally its a great suggestion to be able to run without the sdcard, it would be handy especially once there is synth support, but I dont think its essential to work on straight away so my suggestion is to initially keep config.xml on the sdcard with a new device settings screen to edit it and its then trivial to later move to saving it into flash instead.
Any thoughts on something I may have missed with this plan?

done as of #219


suggest to support allowFontScaling or titleMaxFontSizeMultiplier

in React-native,Text and TextInput support allowFontScaling and maxFontSizeMultiplier
when system font size or display size changed,we can control own app font size

selectedTextProps can do it,so closed it


nginx: Check syntax also at nix evaluation time

https://github.com/NixOS/nixpkgs/pull/24664 added config file syntax checking using nginx -t in preStart of the systemd unit.
In https://github.com/NixOS/nixpkgs/pull/24664#issuecomment-366448476 @volth suggested to check it also at nix-evaluation time, thus failing even earlier. An example was provided for how to do it for Varnish, we'd have to do the same for nginx.
I think this is a great idea; this issue tracks doing that.
CC users from the other issue: @Mic92 @domenkozar @joachifm @volth

I would also check sslCertificate at nix evaluation time issuing a warning if the certificate is expiring soon and panicking if it is already expired.

I would also check sslCertificate at nix evaluation time issuing a warning if the certificate is expiring soon and panicking if it is already expired.

That sounds pretty impure though, does that even work when building in the sandbox, where time is stopped?

I am not sure the check has any sense beyond the nixops-like cases, say on Hydra or on the CI bot.
So it could be skipped in sandbox

Or the time might be passed as an argument of the evaluation

This would certainly work.
I'd go step by step though: Keeping this issue about syntax validity (I think we all want that), and if we want time checks, put that into a different issue.

Do you actually mean evaluation time, or build time? https://github.com/NixOS/nixpkgs/pull/32062 is a build time check.
Note BTW that build-time configuration file checks often break if they refer to directories or users that don't exist yet. E.g. httpd -t fails if the user account mentioned in User doesn't exist yet.

And dns or hostnames in case of nginx

Do you actually mean evaluation time, or build time?

Sorry, build time. Will update the description.

Note BTW that build-time configuration file checks often break if they refer to directories or users that don't exist yet. E.g. httpd -t fails if the user account mentioned in User doesn't exist yet.

And dns or hostnames in case of nginx. This could work in special cases, if the user takes care of it, but not in general. In other words, I could imagine an optional function that takes the configuration as input and returns a new store paths while checking the syntax - users would have to enable this feature and it would be required to disable sandboxes for this to work.

Good points. Let's make it optional then.
I also found that nginx supports two kinds of validity checks:
# /nix/store/rzssgadfwrsbclpksvcy1zx39m50ry7r-nginx-1.12.2/bin/nginx -t -c /nix/store/lk94mvs3pv1ns9qv7zg0fhm07c7sic25-nginx.conf
nginx: [alert] could not open error log file: open() "/nix/store/rzssgadfwrsbclpksvcy1zx39m50ry7r-nginx-1.12.2/logs/error.log" failed (30: Read-only file system)
nginx: the configuration file /nix/store/lk94mvs3pv1ns9qv7zg0fhm07c7sic25-nginx.conf syntax is ok
2018/06/27 17:03:54 [emerg] 31414#31414: open() "/nix/store/rzssgadfwrsbclpksvcy1zx39m50ry7r-nginx-1.12.2/logs/nginx.pid" failed (30: Read-only file system)
nginx: configuration file /nix/store/lk94mvs3pv1ns9qv7zg0fhm07c7sic25-nginx.conf test failed

Notice how it does do syntax checks (syntax is ok), and configuration sensibleness checks (test failed).
Also funny how without further configuration it seems to think error.log and nginx.pid are supposed to be in the nix store (of course that can't work).

There could be a hook in switch-to-configuration that is runs in a mount namespace with the updated thew /etc mounted but without any other sandbox, which performs those syntax checks. This hook then could run before any old service is stopped.

Notice how it does do syntax checks (syntax is ok), and configuration sensibleness checks (test failed).

I've had a quick look into the nginx source code; it doesn't right now give a super easy way to check only the syntax, and the function that parses the config (ngx_conf_parse()) cannot be called without initialisation of some other, rather global nginx stuff.

I can easily imagine this, since every module can add additional keywords to the configuration.

may this help ?
https://github.com/yandex/gixy

may this help ?
https://github.com/yandex/gixy

Hmm, this catches the most extreme syntax errors (like forgetting }), but doesn't seem to catch more basic syntax errors (forgetting ;) and also doesn't seem to have any idea over what directives nginx supports (e.g. you can change listen to listena and it's happy with that.
It feels like we need to urge upstream to get a "pure" syntax checking feature in to do this well.

Handled by gixy.


feat(harfbuzz): initial Skia integration

This does a couple of things:

Deprecates hb_new_face by renaming it to hb_face_from_path

A deprecation warning is added in case anyone else uses this API

Refactor the C codepath of creating a new Harfbuzz face to minimize duplication
Adds a hb_face_from_skia which takes a Skia typeface and returns a face
Internally adds a hb_face_from_data which takes a string (blob) and a length and returns a typeface
Moves the HarfbuzzCLI example to use the new Skia-based API

I'm having a hard time debugging that memory leak. I cant duplicate it on my local machine with macOS. If I run it in Instruments.app, I get no leaks:

I wonder if is Linux-specific or maybe another fontconfig problem?

I'm fairly confident that the leak is from fontconfig, and the reason it's not suppressed is because ASAN isn't recording the callstack deep enough. If I test it on my local machine, I get the same leaks, except mine are labeled as being from fontconfig. Not sure why it's different (possibly differing versions of gcc or ASAN or something), but the leaks look exactly the same:
==80510==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 1536 byte(s) in 2 object(s) allocated from:
    #0 0x7f811bc31ffe in __interceptor_realloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dffe)
    #1 0x7f811bafe3a0  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x213a0)

Direct leak of 256 byte(s) in 1 object(s) allocated from:
    #0 0x7f811bc31bc8 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)
    #1 0x7f811bafe2f4  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x212f4)

Indirect leak of 1536 byte(s) in 48 object(s) allocated from:
    #0 0x7f811bc31dc6 in calloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10ddc6)
    #1 0x7f811bafde0f  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x20e0f)

Indirect leak of 544 byte(s) in 17 object(s) allocated from:
    #0 0x7f811bc31dc6 in calloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10ddc6)
    #1 0x7f811bafe93c  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x2193c)

Indirect leak of 468 byte(s) in 26 object(s) allocated from:
    #0 0x7f811bbba3dd in strdup (/lib/x86_64-linux-gnu/libasan.so.5+0x963dd)
    #1 0x7f811bafdb64 in FcValueSave (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x20b64)

Indirect leak of 384 byte(s) in 12 object(s) allocated from:
    #0 0x7f811bc31dc6 in calloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10ddc6)
    #1 0x7f811bafdcae  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x20cae)

Indirect leak of 96 byte(s) in 2 object(s) allocated from:
    #0 0x7f811bc31bc8 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)
    #1 0x7f811baf7e11 in FcLangSetCreate (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x1ae11)

SUMMARY: AddressSanitizer: 4820 byte(s) leaked in 108 allocation(s).

Not sure what the best solution is for this, but maybe I just temporarily disable ASAN until we can find a way to suppress all fontconfig leaks?


BlockOffset::plane_offset()

The function BlockOffset::plane_offset() is supposed to give the offset of a block in plane coordinates.
However, that's not exactly what the implementation does:
https://github.com/xiph/rav1e/blob/64cf7a982a69b2461d9db1d5ab184eedb765992b/src/context.rs#L1170-L1181
In particular, if xdec or ydec is 1, then the last bit of x_offset and y_offset is discarded, because it first right-shifts before left-shifting.
IMO, the expected behavior is this one:
diff --git a/src/context.rs b/src/context.rs
index ef7b267..c31b7af 100644
--- a/src/context.rs
+++ b/src/context.rs
@@ -1175,8 +1175,8 @@ impl BlockOffset {
     let y_offset = self.y & LOCAL_BLOCK_MASK;

     PlaneOffset {
-        x: po.x + (x_offset as isize >> plane.xdec << BLOCK_TO_PLANE_SHIFT),
-        y: po.y + (y_offset as isize >> plane.ydec << BLOCK_TO_PLANE_SHIFT)
+        x: po.x + (x_offset << BLOCK_TO_PLANE_SHIFT >> plane.xdec) as isize,
+        y: po.y + (y_offset << BLOCK_TO_PLANE_SHIFT >> plane.ydec) as isize,
     }
   }

But with this behavior, decoding tests fail. For example:
cargo test --features=decode_test test_encode_decode::chroma_sampling_aom

I think that the function must be fixed to correctly give the plane coordinates, and that callers should set the last bit to 0 if they need to. But I'm not sure what caller should do that.
It's probably related to c74fb90ea05c2477c3b0530e6e49e07dd30f35ca cc @ycho.
Thank you for your help.

By the way, I think that there is no need to compute the superblock offset and the block offset inside the superblock separately:
diff --git a/src/context.rs b/src/context.rs
index ef7b267..f3c2eed 100644
--- a/src/context.rs
+++ b/src/context.rs
@@ -1169,14 +1169,9 @@ impl BlockOffset {

   /// Offset of the top-left pixel of this block.
   pub fn plane_offset(&self, plane: &PlaneConfig) -> PlaneOffset {
-    let po = self.sb_offset().plane_offset(plane);
-
-    let x_offset = self.x & LOCAL_BLOCK_MASK;
-    let y_offset = self.y & LOCAL_BLOCK_MASK;
-
     PlaneOffset {
-        x: po.x + (x_offset as isize >> plane.xdec << BLOCK_TO_PLANE_SHIFT),
-        y: po.y + (y_offset as isize >> plane.ydec << BLOCK_TO_PLANE_SHIFT)
+        x: (self.x >> plane.xdec << BLOCK_TO_PLANE_SHIFT) as isize,
+        y: (self.y >> plane.ydec << BLOCK_TO_PLANE_SHIFT) as isize,
     }
   }

Hi Romain, I am sorry to see that this part of the code struggled you. It also confuses me always, even though I see many many times.
You may have already tried (but seems not since you mentioned nowhere), if you apply your change " x: po.x + (x_offset << BLOCK_TO_PLANE_SHIFT >> plane.xdec) as isize", it works for block sizes >= 8x8 (by the time I wrote this patch there is no rectangular blk sizes though). However, block sizes 4x4 will not work, assuming we use 4:2:0 chroma format.
The reason why we must do "if xdec or ydec is 1, then the last bit of x_offset and y_offset is discard" is that with 420 chroma format, there is four corresponding luma 4x4 blks for one chroma 4x4 in a 8x8 block. And the chroma 4x4 is only encoded when the last 4x4 luma block is finished encoding.
Now, if you look at the block offset of that last 4x4 luma, it is always odd number, for both x and y for 420 case. From  odd block offset, we need map corresponding block offset of chroma and finally pixel offset (i.e. plane offset in the codebase).
Hope this helps you understand why it is required.
Hence it is necessary to do first right-shifts before left-shifting.

Btw, I think I should have split that old commit c74fb90 into to, since it contains one bug fix and unrelated one improvement of factoring out the block of code for calculating plane offset for chroma block.

@ycho Thank you for your explanation :+1:
The block offset is always expressed in MI_SIZE×MI_SIZE (4×4) luma blocks, while the output plane offset is expressed in coordinates according to the plane config (luma or chroma). So a 4×4 block cause a 4:2:0 chroma block to span several MI.

(I opened a PR about the last part of this post: https://github.com/xiph/rav1e/pull/1067)


Feature/sdk 178

Just some code cleanup and version bump to 0.2.3

Current coverage is 0.00%

Merging #39 into develop will not affect coverage as of 3746e08

No diff could be generated. No reports for #39 found.
Review entire Coverage Diff as of 3746e08

Powered by Codecov. Updated on successful CI builds.


change not available to not known

Change not available (and variations) in ACAPS non_compliance_penalty to not known.

Closes #147.

Closes #147.


How to select monitor in multi-monitor environment? - use vision step

If there is a many monitors, it simply fails and never founds an element.

This is not supported as SikuliX can't set this via a configuration setting. Thus to support such a feature requires rewrite of the TagUI-SikuliX integration. Workaround would be setting up workstation to use a single display, or use vision step to run SikuliX commands directly.
More details at SikuliX documentation. First define the screen to be used, then use that screen variable for every action function. This may not be straightforward unless someone is already familiar with SikuliX. Copying @siowyisheng fyi.
https://sikulix-2014.readthedocs.io/en/latest/screen.html#multi-monitor-environments

Closing issue for now because SikuliX can't easily support this by changing a flag or config, will require rewrite of the TagUI-SikuliX integration engine. Can keep this in view for time being until there is substantial interest from users for such use cases.
Rewriting takes effort but it is only part of the challenge, the other part is it is not easy to ensure 100% backward compatibility from existing users' scripts if the integration engine is re-written.


chore: bump some dependencies for .NET 9.0

bump System.Management from 8.0.0 to 9.0.0
bump Npgsql from 8.0.5 to 9.0.1
bump MySqlConnector from 2.3.7 to 2.4.0

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 73.30%. Comparing base (04f377e) to head (2cf4592).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1223   +/-   ##
=======================================
  Coverage   73.30%   73.30%
=======================================
  Files         293      293
  Lines        3679     3679
  Branches      632      632
=======================================
  Hits         2697     2697
  Misses        812      812
  Partials      170      170

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

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests


Connection established and shows tables, but fails when asking a question saying "can't find a schema for the database"

I have a postgres connection established.
When I run
@pg /show

pg
Here are the tables in the database. You can ask for details about any table using show [table].

I get the output of my tables.
However, when I subsequently run @pg show all Users (or really anything) I always get I can't find the schema for the database. Please check the connection string with /conn.. Note, if I re-run @pg /show that continues to work fine. It's not clear why /show works but asking it questions does not.

That's thrown when there's an error, and I should update that message. If you check the logs you should see the output message of the exact error. I'll add something more comprehensive in the next release - and thanks for letting me know!

Apologies, but it's not clear what logs you'd be looking for. I'm looking in the Output panel when I run commands and am not seeing anything relevant. I've looked under "GitHub Copilot Chat", "GitHub Copilot Log", and "GitHub Copilot" in the dropdown of services. I'm happy to help if you can provide that information. Thanks!

Bah - OK thanks. Can you do me a favor and, using the same connection credentials, run the query:
select * from information_schema.tables;

This will help me rule out privilege stuff. I might not have actually deployed that fix yet.

@robconery
https://gist.github.com/n00ge/54da44a4da6e5e6b83b1c5a09dfe2223
Take a look here. Note I removed most of the tables but it should give you enough information. Let me know when you've reviewed. Thanks!

Thanks - how many tables do you have? I've been getting reports of failures on large table count.

137 total "BASE TABLE" records in there.

Yeah, that's the issue. Copilot is bonking due to table size as it makes the prompt too big. Have to come up with a solution for that when I have a moment. Some way of telling it which tables to use for the prompt (Copilot needs to know the schema to answer your question).

Very out of the weeds here but I'm curious. I imagine you're adding the full schema as context up front? Would it be feasible to just add the table names as context and then get the schema for the relevant tables in a follow up?

Good question - the problem is that I'm running the schema query first, without Copilot. I could ask Copilot which tables it needs, I suppose, but then we get into a weird chicken/egg scenario. Not too sure what to do on this one. @isidorn you mention that we might have a larger request size for the API in the future - is that still the plan?

@robconery yes, that is still the plan. We expect to increase the context size to 6K tokens soon, and then to 16K some time in the future (Sep+)

Same issue, 248 tables for the db Im testing against. Cool tool regardless.


[sqlcipher] build failure

Host Environment

OS: Windows
Compiler: MSVC 2019 Toolset

To Reproduce
Steps to reproduce the behavior:
./vcpkg install sqlcipher:x64-windows-static-md
Failure logs
The following packages will be built and installed:
    sqlcipher[core]:x64-windows-static-md -> 4.4.1
Detecting compiler hash for triplet x64-windows-static-md...
Could not locate cached archive: C:\Users\suraj\AppData\Local\vcpkg\archives\bf\bfc8a632a391bcfcb79e2ffb2b212f7e013d3242.zip
Starting package 1/1: sqlcipher:x64-windows-static-md
Building package sqlcipher[core]:x64-windows-static-md...
-- Using community triplet x64-windows-static-md. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: E:\CLIBS\vcpkg-master\triplets\community\x64-windows-static-md.cmake
-- Note: sqlcipher only supports dynamic library linkage. Building dynamic library.
-- Using cached E:/CLIBS/vcpkg-master/downloads/sqlcipher-sqlcipher-v4.4.1.tar.gz
-- Cleaning sources at E:/CLIBS/vcpkg-master/buildtrees/sqlcipher/src/v4.4.1-bd39e5fc8d.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source E:/CLIBS/vcpkg-master/downloads/sqlcipher-sqlcipher-v4.4.1.tar.gz
-- Using source at E:/CLIBS/vcpkg-master/buildtrees/sqlcipher/src/v4.4.1-bd39e5fc8d.clean
-- Pre-building x64-windows-static-md
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:105 (message):
    Command failed: "C:/Program Files (x86)/Microsoft Visual ```
Studio/2019/Community/VC/Tools/MSVC/14.28.29910/bin/Hostx64/x64/nmake.exe" -f Makefile.msc /A /NOLOGO clean tcl TCLSH_CMD="E:\\CLIBS\\vcpkg-master\\installed\\x64-windows-static-md\\tools\\tcl\\bin\\tclsh90sx.exe" TCLVERSION=90s ORIGINAL_SRC="E:\\CLIBS\\vcpkg-master\\buildtrees\\sqlcipher\\src\\v4.4.1-bd39e5fc8d.clean" "EXT_FEATURE_FLAGS=-DSQLITE_TEMP_STORE=2 -DSQLITE_HAS_CODEC" LTLIBS=libcrypto.lib LTLIBPATHS=/LIBPATH:"E:/CLIBS/vcpkg-master/installed/x64-windows-static-md/lib/"
    Working Directory: E:/CLIBS/vcpkg-master/buildtrees/sqlcipher/src/v4.4.1-bd39e5fc8d.clean
    Error code: 2
    See logs for more information:
      E:\CLIBS\vcpkg-master\buildtrees\sqlcipher\pre-build-x64-windows-static-md-out.log
      E:\CLIBS\vcpkg-master\buildtrees\sqlcipher\pre-build-x64-windows-static-md-err.log

Call Stack (most recent call first):
  ports/sqlcipher/portfile.cmake:40 (vcpkg_execute_required_process)
  scripts/ports.cmake:142 (include)

Error: Building package sqlcipher:x64-windows-static-md failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: sqlcipher:x64-windows-static-md
  Vcpkg version: 2021-01-13-d67989bce1043b98092ac45996a8230a059a2d7e

Attached files below :
pre-build-x64-windows-static-md-err.log
pre-build-x64-windows-static-md-out.log
Additional context
Tried to build the sqlcipher port for sqlitecpp, same issue. The lib "tclstub90s.lib" is simply not generated by "tcl" for any given triplet.

FYI, I have the same issue when not using community triplets and using x64-windows-static

@TheCelebrimbor Sorry for the late reply,   I didn't reproduce your question, because sqlcipher does not support static builds now, if you insist on using it, you can reopen it for discussion. :)


[W06H01] Rewrote existing tests a bit to cover more details

Updated the existing tests to cover more details like the prev and next element in the chain and to pre-compare the list sizes for premature test failure on inconsistency

Ich bitte um ein Review

Hab's genauer durchgeschaut, die Tests funktionieren ♡( •ॢ◡-ॢ)✧˖° ♡

@TheAleWu Would be great if you could add tests that check if the next and prev nodes are correctly set after the kinguin sort.

@julian-hartl that check should already be included by the usage of TestBase's assertListEquals - or did you mean something else?


behavior_path_planner creates shift point outside drivable area

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
behavior_path_planner creates a shift point outside drivable area while avoiding the obstacle.

Expected behavior
The shift points behavior_path_planner creates must always be inside drivable area.
Actual behavior
In some cases the shift point comes out of the drivable area.
Steps to reproduce

Download isuzu_vehicle_launch in here
Download test.zip
Change publish_debug_marker parameter to true in avoidance.param.yaml
run ros2 launch scenario_test_runner scenario_test_runner.launch.py sensor_model:=sample_sensor_kit vehicle_model:=isuzu_vehicle \ scenario:=/scenario/path/test.yaml \  architecture_type:=awf/universe launch_rviz:=false launch_autoware:=true

Versions
No response
Possible causes
No response
Additional context
No response

Can you try this PR: https://github.com/autowarefoundation/autoware.universe/pull/2196 ? I think it will fix this issue.

@beyzanurkaya
Could you please add some screenshots or videos explains the issue?

Can you try this PR: #2196 ? I think it will fix this issue.

I already created a PR for this issue actually.

I will close the issue since I was not able to reproduce it anymore.


[mvn] Update maven wrapper

Coverage remained the same at 93.333% when pulling 10efd4ee905fcacfaaeb879574fe3a5fdc004e4c on hazendaz:master into 721376f81b8ae808216da4abd8b2c22818be330e on mybatis:master.


sometimes color tests fail

add non fuzzed tests to find why and fix them

non fuzzed test impied testing every possible color, which takes a few seconds, which annoys me and is far too long for miri.
i have fonud a better solution: added a "repeat" command to cli, that allows a test to be run forever, thus stresstesting it.

but seems to be fixed now


Is this you?

https://retrosystemsrevival.blogspot.com/2023/06/the-impossible-has-been-achieved.html
https://www.paypal.com/paypalme/win32420

Yes, that's my paypal.

Yes that's the website which most people discovered this browser

:octocat: Is this you ? @Alex313031
https://www.reddit.com/r/browsers/comments/18ihls8/dont_use_thorium_browser_if_you_have_it_installed/


MikroORM + Angular + Electron SyntaxError: Cannot use import statement outside a module

Hi @B4nan
I am trying to use MikroORM with Angular and Electron. I managed to create a connection to the db with MikroORM.init ({...}), but when adding the config file and instantiating MikroORM () without options, I have run into this error:

Also when trying to use the Commandline Tool it gives me the same error:

I have added the mikro-orm.config.ts file and the respective settings in the package.json as the documentation says but it gives me the error.
To use MikroORM with Angular and Electron I am using an extra-webpack-config. It was giving me an error referencing webpack so I added  discovery: { disableDynamicFileAccess: true } to my mikro-orm.config.js
For the integration with Angular and Electron I have based on the project: https://github.com/MetaiR/angular-electron-typeorm  which does the same with TypeORM
Is there something else I'm not considering?

How does the package.json settings look like? Feels like you have ts-node enabled there, which is obviously not possible with webpack build.
Why are you using that file anyway? The purpose of the file is to allow to work with CLI, I would suggest to pass the configuration in MikroORM.init() manually in this case.

The package.json settings:

I used the file to check if there was any tool on the command line to generate the db tables based on the entities, is that possible?

I don't really understand what you are doing - what is causing that error? Are you executing CLI somehow?
Would be good if you prepare a reproduction. This is definitely not a bug in the ORM, its a misconfiguration. The error is about you using TS file inside the compiled JS code. I don't understand how you are mixing the CLI commands with webpack build - how can you "use a file to check"?
Btw you can use SchemaGenerator programatically here if you need it: https://mikro-orm.io/docs/schema-generator/#using-schemagenerator-programmatically
I guess what you stated in the first place is your whole issue:

I managed to create a connection to the db with MikroORM.init ({...}), but when adding the config file and instantiating MikroORM () without options, I have run into this error:

You can't do this with webpack, it means that it will use require() to load that config file, based on the paths from package.json. That is the dynamic file access you want to disable in general when using webpack.
So its fine to have that config file for the CLI, also the package.json part looks fine, but you can't use MikroORM.init() without the config param. What you can do is to require it yourself and pass it there -- it won't be dynamic file access this way (the path to the file will be known at compile time), as the path to the file is known to you, it won't be sniffed from package.json.

I did not explain myself well, sorry. I understand that I need the file to use the CLI, that's what I meant, I wanted to see if in the CLI there was any tool to generate the tables based on the entities, for which I see that I can use SchemaGenerator as you mentioned.
I am left in doubt: when using the CLI after adding the file, when I run for example: npx mikro-orm schema: update --run it gives me the error I mentioned above. From what I understand could I not use CLI in the environment I am working on?

Do you have ts-node installed?

Yes, it's installed:

It gives me this error

Weird, maybe it's caused by the tsconfig.json settings, hard to say. If you prepare a reproduction repository I can take a look.
Do you have tsconfig.json file in the root of your project?
Maybe this is your problem: https://github.com/TypeStrong/ts-node/issues/922#issuecomment-571734880

Yes tsconfig.json file is in the project root.
This is a repository where I uploaded the basic structure of the project: https://github.com/wilberalx/mikro-orm-angular-electron

Great thanks for your help

@B4nan This issue still happens when I try to run a compiled ts project even using commonjs

@B4nan This issue still happens when I try to run a compiled typescript project even making  use commonjs

There is no issue, never was, this was just a misconfiguration. Your problem will be most probably again wrong setup - hard to help without seeing the details. Check the example projects.
My guess is that you have wrong paths in entitiesDirs, those need to point to the compiled entities (dist), while entitiesDirsTs should point to the TS files (src).

here is no issue, never was, this was just a misconfiguration. Your problem will be most probably again wrong setup - hard to help without seeing the details. Check the example projects.

You are right @B4nan thanks. This happened when I try to run migrations. I moved my migration away from my root dir.


Artifact configuration should include the test's runtime dependencies

When creating an artifact for a test set, the artifact configuration should extend from the test set's runtime configuration. This way, other projects will get the testRuntime dependencies transitively by depending on the test artifact.
Example: in project A
testSets {
    myTest { createArtifact = true }
}

dependencies {
    myTestCompile 'junit:junit:4.12'
}

in project B
dependencies {
    // this should transitively include the 'junit:junit:4.12' dependency
    testCompile project(path: ':A', configuration: 'myTest')
}

implemented in version 2.0


[BUG] FilesystemTree.filter only filters based on filenames, ignores folder names

https://github.com/nfdi4plants/ARCtrl/blob/e9e8e2e0b0fa710d4767efdee623ea7c47192f39/src/FileSystem/FileSystemTree.fs#L103-L115
this should either be named filterFiles or line 110 should include a check for predicate on the folder name

For context: My usecase is filtering all ghidden files and folders (predicate -> not starts with "."), which will not remove the .git directory with this function.


PubSub bug fixes

Two bug fixes:
1 - We're missing PONG and RECONNECT responses from the server, so they're coming in as errors.
2 - Reward cooldown_expires_at is a timestamp, not amount of seconds, so that's erroring when parsing

Thanks!


director and hash (anchor) links

What's the general method here to allow for anchor links?
I'm talking about these: Go to section 1 [...]
...
.
My routes are being converted from: /#!/current-page to /#section-1 whenever these are clicked.
Can director.js handle these, maybe through /#!/current-page#section-1 ?

:+1: this is a pretty serious shortcoming


Make "Run Current File" work like Sypder

When selecting "Jupyter: Run Current File in Interactive Window", the contents of the file are run in the window.  This will not allow the file parameter, init_.py files nor the path to be properly set for relative imports.  When Spyder runs a file, it actually calls a separate function which takes the path of the file and executes it in the proper environment.  Moreover, Spyder also has a "User Module Reloader" which will detect updated user modules that have changed and reload them.
References to Spyder's functionality:

https://docs.spyder-ide.org/current/panes/ipythonconsole.html#reload-changed-modules
runfile(... wdir=...): https://github.com/spyder-ide/spyder/blob/0a86dcdc57e9e56a91a8b81fafedaede0ab4c1ca/external-deps/spyder-kernels/spyder_kernels/customize/spydercustomize.py#L498
UserModuleReloader: https://github.com/spyder-ide/spyder/blob/0a86dcdc57e9e56a91a8b81fafedaede0ab4c1ca/external-deps/spyder-kernels/spyder_kernels/customize/umr.py#L15

Thanks for the suggestion.

looks like this could be covered by https://github.com/microsoft/vscode-jupyter/issues/5519


Equivalent for HubConnectionBuilder WithConsoleLogger()

What is the equivalent in SignalR 1.0.0 for the WithConsoleLogger() found in preview1?

You use .ConfigureLogging and configure it the same way you configure logging on the server:
var connection = new HubConnectionBuilder()
    .WithUrl("...")
    .ConfigureLogging(logging => {
        logging.AddConsole();
    })
    .Build();

We have some docs on configuration (including logging) coming soon!
Closing this as the question has been answered. Feel free to comment further if you need clarification on something! We can always re-open the issue if there's something to fix here.

'ILoggingBuilder' does not contain a definition for 'AddConsole' and no extension method 'AddConsole' accepting a first argument of type 'ILoggingBuilder' could be found (are you missing a using directive or an assembly reference?)

You need to bring in the appropriate Logging provider package. In for Console that's Microsoft.Extensions.Logging.Console


feat: add Typeahead component

Please check if the PR fulfills these requirements

[x] The commit(s) message(s) follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)

The story is missing some needs: the events are only attached to the 1st item in the list
You could face an error, while refreshing the page when the Typeahead is selected (just refresh the page on another component, then select the Typeahead)
As you can see there is a scss file int stories folder, I put it intentionally to show the case that it's possible to send a theme to the Typeahead component.

What is the new behavior?
A basic customized story for the Typeahead
Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Can we close this one?


Fix integration tests to support crud operations on sms provider configurations in super tenant

Purpose

Modify integration tests to support updation of sms provider configurations for super tenant.

Related PRs: Merge this PR after merging below PRs

https://github.com/wso2-extensions/identity-event-handler-notification/pull/205
https://github.com/wso2/identity-api-server/pull/514

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6649890872

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6649890872
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6650975238

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6650975238
Status: success


does active format list need to be updated here?

https://github.com/hall-lab/svtools/blob/master/svtools/vcf/genotype.py#L14

Not for correct behavior in the current code base because set_formats is only called here: https://github.com/hall-lab/svtools/blob/master/svtools/vcf/variant.py#L36-L44
Notice the matching call to update_active_format_list at the end. I did this because deferring the construction of that list until the batch of samples was processed seemed like a good idea.
It does seem like a bit of a booby-trap though...


Fix landbosse hard crash and access violations SAM issue 784

I'm trying to build this branch but am having issues building SAM (develop):
/Users/dguittet/SAM-Dev/sam/src/defmgr.cpp:292:5: error: no matching constructor for initialization of 'wxArrayString'

Any suggestions?

fixed with latest commit...this was a checkmarx initialization fix that
does not work on macOS
On Fri, 19 Nov 2021 at 08:35, Darice L Guittet @.***>
wrote:

I'm trying to build this branch but am having issues building SAM
(develop):
/Users/dguittet/SAM-Dev/sam/src/defmgr.cpp:292:5: error: no matching constructor for initialization of 'wxArrayString'
Any suggestions?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NREL/ssc/pull/667#issuecomment-974174259, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRSQB4SX344G55PKV4IH7TUMZVCTANCNFSM5IL53CZA
.


NVSHAS-8562: Use the new API "/v1/system/alerts"

Looks good to me, but I'm thinking if we should also keep the /v1/system/rbac.  Would that be slightly beneficial when master cluster still manages 5.3 clusters?

Looks good to me, but I'm thinking if we should also keep the /v1/system/rbac. Would that be slightly beneficial when master cluster still manages 5.3 clusters?
I think it should be ok if we remove it even it's possible that 5.4 master cluster manages a 5.3 cluster. /v1/system/rbac is an internal API, and no one is using it expect our UI.


ncurses-doc added

Add ncurses-doc (which consists of man pages for ncurses functions) into the packages list.

Closed by https://github.com/hashbang/shell-etc/commit/cfb2cf4d5c8bdabdc984aba863a6f49b990ac1e6.
Please use issues for getting packages added, since we usually do an apt install and it's less work for you  ;-)
This will get deployed (on other servers than to1) as soon as the issue with the latest Debian point release is identified.


Metadata from github

With the definition of metadata being laid out here: https://github.com/chanzuckerberg/napari-hub/blob/main/docs/customizing-plugin-listing.md, there are references sourced from GitHub, this becomes an issue across multiple versions, since the GitHub tag may not necessarily correspond to the PyPI release number, for example, a v0.0.1 release may be tagged as 0.0.1 in GitHub, I wonder what people think about managing metadata from github in regards to versions?

I wonder what people think about managing metadata from github in regards to versions?

one of the problems/challenges/complaints about PyPI metadata is the way that metadata is pegged to a release & is therefore immutable. so I think that its important for plugin devs to update the description and other metadata immediately without cutting a new release.
I don't think we should worry about mapping between PyPI releases and Github tags & we should simply pull from HEAD of the main/master branch

I don't think we should worry about mapping between PyPI releases and Github tags & we should simply pull from HEAD of the main/master branch

That would show data that may not yet be published or accurate I would suggest to use the data from the latest PyPI release 🤔

That would show data that may not yet be published or accurate

We have a very limited set of metadata which we will be pulling directly from Github:

Summary
Description
Authors
Project Site
Documentation
Support
Report Issues
Twitter

Everything else will come from PyPI & will reflect the latest release.

(aside: that reminds me that the table and individual field descriptions do not reflect that all of these fields should pull from Github, even though they were called out in the "Github" section and initial metadata spreadsheet)

The service that does this best, IMHO, is ReadTheDocs, which lets their developers choose whether they will build & display the "latest" version of the docs (straight from HEAD) or the "stable" version (the last patch release) and specific versions.


The apoc.export.csv.all doesn't export quotes with bulkImport: true

Expected Behavior (Mandatory)
Should export the " (escaped).
Actual Behavior (Mandatory)
The " is not exported.
How to Reproduce the Problem
Create some nodes with a quote, e.g.:
CREATE (n:DoubleQuoteTest {text:'This is a double quote "'});
CREATE (n:DoubleQuoteTest2 {text:'This is a " double quote2'});

The export without bulkImport print the " char as a "" (to escape it).
CALL apoc.export.csv.all("doublequotedb.csv", {quotes:'always'});

Output file doublequotedb.csv:
"_id","_labels","text","_start","_end","_type"
"0",":DoubleQuoteTest","This is a double quote """,,,
"1",":DoubleQuoteTest2","This is a "" double quote2",,,

On the contrary, with bulkImport, the " is not printed.
CALL apoc.export.csv.all("doublequoteimportdb.csv", {bulkImport:true, quotes:'always'});

Output file doublequoteimportdb.nodes.DoubleQuoteTest.csv:
:ID,text,:LABEL
0,This is a double quote ,DoubleQuoteTest

Output file doublequoteimportdb.nodes.DoubleQuoteTest2.csv:
:ID,text,:LABEL
1,This is a  double quote2,DoubleQuoteTest2

Versions

Neo4j: 4.4.26 (most likely with every version)
Neo4j-Apoc: <IP_ADDRESS>  (most likely with every version)

This has been fixed during October, so will close the issue.


Aether Object Protection Issues

It is possible to bypass the API Protections and modify thang attributes using the Javascript Object keyword to add or change property values directly with .defineProperty()
There are other Object functions which are destructive to API security which could be abused including .freeze() and potentially .defineSetter().  The lodash framework may also expose similar functionality to users but has not been tested (yet).
These functions are available as Javascript in every language in codecombat.
Potential Mitigations:
Determine if a simulation is attempting to modify an object outside of it's purview by hashing the value of a non-changeable attribute before the chooseAction() code is ran then comparing the hash at the end and using that to determine if chooseAction() modified the value.  This would require simulations to take place on a central server (not feasible)
Blacklist Object functions which modify object prototypes.  Overwrite Object to disallow these non-safe functions in the same coffeescript where the rest of the globals are defined.

Should be fixed with @basicer's new Esper interpreter.