API request failed

I face this error after upgrading to 1.6.4 version (after 1M tokens using openrouter with OpenAI 4.o mini):
{
"error": {
"message": "Invalid parameter: messages with role 'tool' must be a response to a preceeding message with 'tool_calls'.",
"type": "invalid_request_error",
"param": "messages.[37].role",
"code": null
}
}
Thanks a lot.

Is this a new task that you recently started or is this an old task you tried to resume?

If you hit 'Export', could you pls paste here the first 5 messages in the conversation history

Hi, it's an old task that I try to resume. Here is the task messages:
claude_dev_task_sep-11-2024_12-54-37-pm.md

I have been unable to reproduce this issue, although one other user reached out to me saying they were facing this as well. It seems like it mostly happens when usingopenai/gpt-4o-mini-2024-07-18 and on rare occasionsopenai/gpt-4o-2024-08-06. I suspect that OpenRouter either has some internal issue when processing the request (could be due to request timing out, seen this happen before), or it's possible that the gpt4o model is reusing tool ID's which according to this post can also cause this issue.

It looks like this happens very inconsistently and usually when the conversation history gets long, at around 1m tokens processed. If anybody can find steps to consistently reproduce this issue I would appreciate it, but for now it's hard for me to tell what I can do to fix this.
One user reported that retrying the request on occasion would fix the issue and the API request would succeed
I suggest trying to use gpt4o through OpenAI's API directly and seeing if you can still repro the issue, and if not then my suspicions about openrouter having some internal server error would be correct.

Closing for inactivity


Manual XRD holder cleaning (until the auto-cleaner is operational)

We need to make this a rotating job - sending automatic rotation messagess?

System changed, manual cleaning is done by whoever runs the experiment.


feat: change FROM to ^OF with support for lowercases GET, ON

Should close #31
Please tests if OK
also tests passes for cargo test with changed source from FROM to OF
add one test case for lower case check

Hey @rizdarmwn thanks for this PR. Will give a proper test this week.

@rizdarmwn lgtm! We just need to fix the conflicts

@iankressin should be resolved now


[test] Reduce the set of available listening ports for isolated runtime environments

There's a chance we're seeing interaction effects between containers in remote test environments. If that's happening, this change should significantly increase the failure rate.

I updated the max port count to ~3000, and left justification for it in a comment.


Heroku / dokku and "ValueError: There's already an active RQ scheduler"

I'm running dokku, which is a "Docker powered mini-Heroku in around 100 lines of Bash".
I switched to RQ a few weeks ago after celery kept locking up workers due to a deep multi-threading issue in python.  RQ is working perfectly except for one small issue...
When I 'git push' my code up to my server, dokku creates a new container with the updated code, then it starts all the services in the NEW container, makes sure they are running, switches traffic to the new container, then shuts down the old container.
The only problem is that rq-scheduler checks to see if there is an active instance of the scheduler running.  Unfortunately there is--in the old container that is about to get killed.

Would a command-line flag to ignore an already running scheduler, be useful?
Another option might be to allow multiple schedulers to run, but only the one that holds the lock can submit new tasks.  If it dies, and the lock expires, another scheduler could grab it and start submitting...
I'd be willing to try my hand at writing a patch if you approve of either idea.

Related issues: #62 and #70

On Aug 17, 2015, at 9:56 PM, Aaron C. de Bruyn<EMAIL_ADDRESS>wrote:
I'm running dokku, which is a "Docker powered mini-Heroku in around 100 lines of Bash".
I switched to RQ a few weeks ago after celery kept locking up workers due to a deep multi-threading issue in python. RQ is working perfectly except for one small issue...
When I 'git push' my code up to my server, dokku creates a new container with the updated code, then it starts all the services in the NEW container, makes sure they are running, switches traffic to the new container, then shuts down the old container.
The only problem is that rq-scheduler checks to see if there is an active instance of the scheduler running. Unfortunately there is--in the old container that is about to get killed.

Would a command-line flag to ignore an already running scheduler, be useful?
Another option might be to allow multiple schedulers to run, but only the one that holds the lock can submit new tasks. If it dies, and the lock expires, another scheduler could grab it and start submitting...
I'd be willing to try my hand at writing a patch if you approve of either idea.
—
Reply to this email directly or view it on GitHub.

I like this idea, please see my comment here: https://github.com/ui/rq-scheduler/issues/70#issuecomment-132827484

Any suggestions how to fix that?

remove all keys in redis if your in development


fix fused_batchnorm_test.py

In file fused_batchnorm_test.py,  the function _reference_training use
element_count = np.size(x) / int(np.shape(x)[0])

to get element_count for NHWC data_format, but it should be
element_count = np.size(x) / int(np.shape(x)[-1])

The last dimention is the channel number, the reason why it works now is that the test data is [2,2,6,2]
np.shape(x)[0] == np.shape(x)[-1] == 2

Can one of the admins verify this patch?

I signed it!

Can anyone help to review this PR? @tensorflow-jenkins

what is the CI fail about? It does not have any error log.

The issue looks like an interesting flake, I cant see how it can be related to your change. Will rerun tests to see what is going on.
Jenkins, test this please.


[Design enhancement to existing functionality] Config Wizard - Convert Chakra tooltip to handrolled state-managed form comments

Is your feature request related to a specific problem?
In the Config Wizard designs, the form comments are separated from the icons/highlighted text and the page is divided. The state management pieces are straightforward, however there is complexity when tying the text to the specific mouseover point on the page. Initial solution was to use the e.target offSetLeft and offSetTop properties, however these don't match well to elements, and additionally we need to wrap the chakra elements in span elements to access mouseover and mouseout handlers.
Further thinking is needed to come up with a working solution for this design.
Describe the solution you'd like
I would like the comments in the wizard to display as designed.
Describe alternatives you've considered, if any
We are currently using the alternative of built-in chakra tooltips.
Additional context
Current:

Desired:

Notice that the text is separated yet still in-line to where the text or icon is relatively.

We haven't revisited the designs for this in a while, but one thing that is still notably missing from our current implementation is that tooltips can't have clickable links in them. We're building up some TODOs where we're just showing the text without a link.


Hardcode integer sizes

My recent playing with benchmarks led me down the slippery slop into profiling,
where I found this oddity. Calling binary.Size() actually involves reflection
on the argument which is expensive (of course). There was really no reason not
to hardcode these other than vague hand-waving towards portability (really).
Saves us about 2.5% of profiled time in the producer benchmarks.
@Shopify/kafka

nice find! :shipit:

slight tangent: crc32 calculations account for nearly 40% of the time, so #255 is real and is the lowest-hanging fruit if we ever desperately need more performance.


Add prepared statements in mysql async

Try to add server-side prepared statements.
Info:
https://dev.mysql.com/doc/refman/8.0/en/sql-syntax-prepared-statements.html
https://dev.mysql.com/doc/refman/8.0/en/c-api-prepared-statements.html

OK, Perhaps the implementation of amp is a good reference.
https://github.com/amphp/mysql/blob/master/src/Internal/Processor.php#L377


New home view

Also, added description to the datasources.

do you have a screenshot how will it look like?

@c0b I've added a screenshot to the PR's description

gr 🎱


What file permissions should be used for Yourls

This is a COPY of Issue 329: What file permissions should be used for Yourls, filed on Google Code before the project was moved on Github.

Submitted on 2010-05-15T13:00:40.000Z by<EMAIL_ADDRESS>Status: Done

Please review the original issue and especially its comments. Comments here on closed issues will be ignored. Thanks.
Original description
Hi, this is an error in code, but i am worried about the security, and i
want to know what CHMOD for the File Permissions i should use for the
folders and files.

Many thanks, Ryan
twitter.com/ryanfitton

Well, what was the answer? O_o


chore(deps): bump aws-cdk-lib, aws-sdk, and fs-extra

Bumps:

aws-cdk-lib to 2.54.0
aws-cdk to 2.54.0
awslint to 2.54.0
aws-sdk to 2.1272.0
@aws-sdk/* to 3.222.0
@types/fs-extra to 9.0.13

I also fixed up some newly deprecated APIs while I was at it. Notably:

SubnetType.PRIVATE_WITH_NAT -> SubnetType.PRIVATE_WITH_EGRESS -- This is non-breaking; I checked the CDK code.
cloudwatch.Statistics.MINIMUM -> cloudwatch.Stats.MINIMUM -- This was just in a test.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Looks good, but we also need to bump the version of the CDK lib in the python examples too.

Right, of course. Missed that...


API error while trying to update device attributes - PUT/devices/id

Hello @tananaev
for the attribute value in device table to be updated via api, what is the format to be used? I am getting the following error.
Can not construct instance of java.util.LinkedHashMap: no String-argument constructor/factory method to deserialize from String value ('{') at [Source: org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream@5d7926f9; line: 1, column: 56] (through reference chain: org.traccar.model.Device["attributes"])

What do you send in the request? You should send the same format as you receive from the server.

I am sending the attributes as JSON. Also the format I receive from the server is in JSON (The content of attributes).
Sharing below exact value/format I am using in the API
{"speedLimit":"20"}

Also would like to add, I am able to edit the device all other values via API, only when I add the attributes I am stuck with the following error.

Can I see full request?

@tananaev I have been using php/curl  hence when you asked for full request, I tried to get the same out and realised that the  Content-Type: value was configured wrong as text/plain every time I set the attributes, I corrected the request content type to Content-Type: application/json and it worked perfect now 👍
Thanks a lot.


3.6 included version required

There is an update for the sandbox mode, version 3.6. please create an update for that included dockerfile.
Thanks :bow:

I'd love to see this too!


Plugin load fails if path contains []

In my project.yml
i've configured ceedling plugins directory like this
:plugins:
:load_paths:
- d:/users/pennam/[TEST]_CEEDLING/Ceedling-0.20.3/plugins
and when i try to run ceedling it fails with the following output
rake aborted!
LoadError: cannot load such file -- stdout_pretty_tests_report.rb
d:/users/pennam/[TEST]_CEEDLING/Ceedling-0.20.3/lib/ceedling/system_wrapper.rb:64:in require_file
d:/users/pennam/[TEST]_CEEDLING/Ceedling-0.20.3/lib/ceedling/plugin_manager.rb:20:in block in load_plugin_scripts
d:/users/pennam/[TEST]_CEEDLING/Ceedling-0.20.3/lib/ceedling/plugin_manager.rb:16:in each
d:/users/pennam/[TEST]_CEEDLING/Ceedling-0.20.3/lib/ceedling/plugin_manager.rb:16:in load_plugin_scripts
d:/users/pennam/[TEST]_CEEDLING/Ceedling-0.20.3/lib/ceedling/setupinator.rb:37:in do_setup
d:/users/pennam/[TEST]_CEEDLING/Ceedling-0.20.3/lib/ceedling/rakefile.rb:46:in <top (required)>
d:/users/pennam/[TEST]_CEEDLING/Ceedling-0.20.3/lib/ceedling.rb:66:in load
d:/users/pennam/[TEST]_CEEDLING/Ceedling-0.20.3/lib/ceedling.rb:66:in load_project
d:/users/pennam/project/CEEDLING/rakefile.rb:4:in <top (required)>
(See full trace by running task with --trace)
Done!
Is there some way to escape square brackets?

I have to admit, I'm shocked. I'm not shocked that Ceedling doesn't support this... I'm shocked that brackets are legal characters on Windows. I had to look it up to convince myself that it was even true (for anyone curious you can look here ).
We can definitely update the regex's involved to support brackets... but why, oh why, would anyone ever use paths like that?  ;)


Need More Code Sample for Simple Backend Web to Send Push Notifications for Xamarin Apps

Iread through the article and was able to follow some parts of it.  I am new developing Mobile aoos with xamarin.  However, I wasable to setup the Firebase, Apple developer, APN certs, etc.  I am also able to send test messages.  The probleis tha tI had a difficult time following the instructions on how to build a simple web backend to send notifications.  Can you direct me to ducumentation that is more straightforward.  I would greatly appreciate it.
[Enter feedback here]

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

ID: ae6b97ae-ec64-6de9-8f02-16f91f5f9519
Version Independent ID: d9748b97-4afb-fc97-9598-188bd460cc13
Content: Send push notifications to Xamarin.Forms apps using Azure Notification Hubs via a backend service
Content Source: articles/mobile-apps/notification-hubs-backend-service-xamarin-forms.md
Service: mobile-services
GitHub Login: @mikeparker104
Microsoft Alias: miparker

Hi @techmanDAV. Were there specific aspects that you found difficult to follow? Would some additional information or hints have helped? The ASP.NET docs has a getting started tutorial covering the basics of building a web API with ASP.NET Core.

Closing this issue due to staleness. We apologize for the delayed response. If you are still encountering the problem you've described, please re-open the issue within 2 weeks and we'll take a look. Thanks!
#label:"UUF-Stale-Not Planned"


reference: write OAI-PMH REST API docs

Add a new section to the REST API reference docs following the same structure as other REST API docs.
The section should cover the new REST API for managing OAI-PMH sets. We will need to make it clear that the API was added in v9 as we don't yet have docs per release.
Important to also mention what it requires to have access to the API.

@rekt-hard I've assigned you to this one. We can chat on monday if you're available to do it or not.


Update GHA.yml

Add CI for Pharo64-12.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4

Relevant Lines:
4

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4

Relevant Lines:
4

💛  - Coveralls


Event Dashboard: Implement a graph to show ticket sales and general sales

Please implement a ticket sales graph to view different ticket sales and specific details on the event dashboard include the following:

Show ticket sales per ticket lines
Show overall ticket sales
Show gross sales
Show net sales
Provide option to choose time range for display

i wonder why I am not seeing anything but Create Next App page. Please clarify

I'd like to work on this issue.
I've some ideas to implement such graphs , but would like to know if any preferred way of implementation is there.


Is it possible to get the HTML content of the body?

Hey, first of all, thanks for this cool project!
My question would be if it is possible to get the HTML content of the body?
When i do this here, i only get the text of the email:
cy.mhGetAllMails().mhFirst() .mhGetBody() .then((body) => {console.log(body)})
Thanks in advance

Yes, it is possible. I'll be releasing a new version very soon the current version is still in beta so API is still in very early stages.
For now, you can get the ID and do the subsequent call to this API.

Thanks, that was really helpful!

Hey, this has been released v0.0.3


Error when trying to upload: Unable to locate element: .../ytcp-mention-textbox[2]

Hi ! I tried to upload a video today but there is this error :
twitchtube | 19:36:09 - error: There was an error Message: Unable to locate element: /html/body/ytcp-uploads-dialog/paper-dialog/div/ytcp-animatable[1]/ytcp-uploads-details/div/ytcp-uploads-basics/ytcp-mention-textbox[2]
 when trying to upload to YouTube

Am I the only one who can't upload recently with twitchtube?
Maybe there was an update of Youtube upload page ? Idk, I will fork and check what's wrong.

Should be able to fix this issue by updating the opplast package pip install --upgrade opplast.
Seems like YouTube have changed around on a couple of things, so it might not work. Works more times than not, but still some videos that just says "Uploading..." on YouTube and nothing ever happens.

Fixed with pip install --upgrade opplast ; it works! Thanks


Error : invalid number of images in '.\capture_0'

When I'm trying to calibrate the images under the sample_data/capture_0, an error occurred. I noticed that the value of len(gc_filenames) is 42 and the value of graycode.getNumberOfPatternImages() is 42.This means that len(gc_filenames) != graycode.getNumberOfPatternImages() + 2.I just don't know why this error occurred and what's the exact meaning of graycode.getNumberOfPatternImages() .

I've tried to add the copy of last 2 images in the path \ capture_0,then the program ran successfully.But the RMS error was very big.

Sorry for being late...
I guess that you ran the caliblate.py with graycode_step=1.
But the sample_data is captured with graycode_step=2.
I added a sample command to README.


Iframe source downgraded to http

I've set a URL that points to an https in my xcomponent definition:
const component = xcomponent.create({
  tag: 'customer-widget',
  url: `https://dvelp-support-client-dev.herokuapp.com/customer/`,
  ...
});

I'm getting this error:

(index):1 Mixed Content: The page at 'https://love-island-jzgfnnjiwu.now.sh/' was loaded over HTTPS, but requested an insecure resource 'http://dvelp-support-client-dev.herokuapp.com/customer/?uid=ffa8ca2c7a&logLevel=info&version=latest&xcomponent=1'. This request has been blocked; the content must be served over HTTPS.

As you can see, the URL has downgraded to http and not loading due to mixed content policy.
Please, see repro here:  https://love-island-jzgfnnjiwu.now.sh/

The repro url is working fine, did you find out what the issue was ?

Yeah, the issue happened when I set env var XCOMPONENT_FRAME_ONLY, otherwise all works great


Error: forwarding ports: error upgrading connection: error dialing backend: dial tcp xx.xx.xxx.xxx:10250: i/o timeout

When I install ingress stable/nginx-ingress by terraform  I first of all apply rbac
kubectl apply -f create-helm-service-account.yml
then add section helm init --service-account tiller --wait
and after all I install nginx-ingress , but I got the same error
Error: forwarding ports: error upgrading connection: error dialing backend: dial tcp xx.xx.xxx.xxx:10250 i/o timeout .
When I connected to cluster i could install nginx-ingress by helm without error .
What it can be ?

Hi @empikls did you solve the problem. I have the same error on running any helm command such as helm list

Hi!
Yes, sure . Problem was in temporary inactivity k8s network.
I use terraform and when cluster is created it need more time for create network policy and port forwarding .
You can add check for ready network plugin and others policies .


Add settings to control environment file name

Something like:
set dotenv-filenames := [".env", "other-dotenv-file"]

This should be like @xorander00 explained in #941, right?

have a setting to specify the file(s) to load and the order in which to load them ... look for and load from left-to-right (later loaded dotenv files overriding values from previously loaded ones).

Yeah, that's right. If a user wants it to be an error if an environment file isn't found, we could add another setting, like set dotenv-require := true, which would default to false, and make just return an error if an environment file isn't found

Just saw this, sweet!  :) Will build from latest commit & give it a shot this weekend and report back if I run into any issues.
@casey I think that would be a good setting, yes.  Although personally, I'd consider making it a numeric (or enum-like) state flag instead of a boolean toggle.  Not sure how it would work in just, but something like dotenv-missing := 0 | 1 | 2.  0 being silently ignore and continue, 1 being warn and continue (default), and 2 being fail and exit.  This offers more flexibility for the user as well as for the future (additional cases can just be new numbers).  Just my personal preference though and not a huge deal.

@casey I think that would be a good setting, yes. Although personally, I'd consider making it a numeric (or enum-like) state flag instead of a boolean toggle. Not sure how it would work in just, but something like dotenv-missing := 0 | 1 | 2. 0 being silently ignore and continue, 1 being warn and continue (default), and 2 being fail and exit. This offers more flexibility for the user as well as for the future (additional cases can just be new numbers). Just my personal preference though and not a huge deal.

I think that would be reasonable. And it can always be a keyword, like dotenv-missing := continue | warn | error, so it's easier to remember.

@casey Can we change .env file in recipe? Like this:
# Start application in dev mode with .dev-env supported
start-dev:
  set dotenv-filenames := [".env", ".dev-env"]

# Start application in test mode with .test-env loaded
start-test:
  set dotenv-filenames := [".env", ".test-env"]

@casey Can we change .env file in recipe? Like this:

I think it's probably impossible to change a .env file once a recipe runs. Different parts of a justfile could read from different environment files, depending on when they ran, which would be super confusing.

@casey Can we change .env file in recipe? Like this:

Different parts of a justfile could read from different environment files, depending on when they ran, which would be super confusing.

Thanks for your reply. As the example I gave above: it's quite common that when a APP starts in dev mode with envs different from in test mode, such as DB config, backend service URL, etc. How to achieve this ?

Thanks for your reply. As the example I gave above: it's quite common that when a APP starts in dev mode with envs different from in test mode, such as DB config, backend service URL, etc. How to achieve this ?

I'm not entirely sure. There's a complication here, which is that just doesn't support arrays, so there's no way to do:
set dotenv-filenames = if FOO == BAR { [".env-dev"] } else { [".env-prod"] }

Since an expression can't be of type array, only string.
You could use just --dotenv-filename NAME to select which one you want when invoking just, perhaps making the dev version .env, and passing just --dotenv-filename .env-prod when you want to run in production mode.

Got it, Thanks

I'd like to suggest one more thing with regards to loading of the .env - it would be usefull if instead of just a file, you could provide a command to run (that would output the .env content to STDOUT). This would (for instance) enable me to load secrets from 1password cli by doing something like set doenv-load = op inject -i .env:

I like @Alxandr proposal,
I just created an issue with a general solution as the goal : https://github.com/casey/just/issues/1584

At the moment, it seems that it's not possible to load a specific path for the .env file from within the justfile, even though it is from the command line. Does that sound right? I did do a lot of searching
What if it could all happen using the same dotenv-load variable? Currently that's a boolean only, but can it be extended to test for a string? And if it's a string then it's the path to the .env file itself?
Regarding being able to use arrays for multiple... This seems to work: set shell := ["bash", "-uc"] .. isn't that an array? But even being able to load one would be nice... perhaps to load multiple, just use source other-env-file.env from within the .env file itself? That would take some weight off of just for loading multiple if it's possible

Is it correct that currently the way to load an .env file is automatically from either the current or parent directory, and there is not an option to specify a path?

Here is a use case why setting a custom path would be helpful: NextJS projects have a convention of putting the .env file into source control and only setting default values there. So you would need to be able to load .env.local to use just in such a project.

Implemented in #1692.

Hey @casey, I was wondering if there are plans to support multiple dotenv files? It seems like the PR implemented only support a single dotenv file compared to what was proposed here.
It would be great to be able to have Just load dotenv files like in https://github.com/bkeepers/dotenv#what-other-env-files-can-i-use.
Thanks! :Raised_hands:

@evandam I'm not opposed! I think it was just left out to make the initial implementation simpler. Can you create a new issue and describe your use case? In particular, I'm curious if you want to load multiple dotenv files at the same time, or if to go through a list of dotenv files, and load the first one that's found.


Near tip of tree flutter start's sky shell crashes immediately on android.

 flutter --version
Flutter from unknown source
Framework: e9e7f44df8867e0bae8c108238971dbc634bd8d3 (3 hours ago)
Engine:    ad37a616354f143c7779dba7f51356f43181e3d6

See https://github.com/flutter/flutter/pull/2371 and  https://github.com/flutter/flutter/issues/2383

https://github.com/flutter/engine/pull/2457 might fix this issue.  Without repro steps, it's hard to know for sure.

Confirmed that patch did fix it.


Add second and minute grains to sqlite

CATEGORY

[x] Enhancement (new features, refinement)

SUMMARY
Sqlite was missing the common time grains of second and minute.
TEST PLAN
Tested locally.

Codecov Report

Merging #7810 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7810   +/-   ##
=======================================
  Coverage   65.89%   65.89%
=======================================
  Files         459      459
  Lines       22014    22014
  Branches     2417     2417
=======================================
  Hits        14507    14507
  Misses       7386     7386
  Partials      121      121

Impacted Files
Coverage Δ

superset/db_engine_specs/sqlite.py
66.66% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


error in Realsence Viewer

librealsense
2.55.1 RELEASE

OS
Windows

Intel RealSense Viewer / Depth Quality Tool has crashed with the following error message:
Unhandled exception escaping from a worker thread!
Error type: Unknown error (-529697949)!

Hi @nohaalaref  Does the error appear when the RealSense Viewer first opens, or does it appear when an option is selected?
This error sometimes occurs when trying to access the RGB camera from the Add Source option, like in https://github.com/IntelRealSense/librealsense/issues/11338

yes exactly this is when I was trying to open the RGB camera (platform camera) from Add Source. However, my main issue is that the Realsense viewer is not reading my camera lidar L515 at all. There is an access to the laptop , tried changing the cable and reinstalled the SDK and viewer more than one time.

Support for L515 has been removed from the RealSense SDK from version 2.55.1 onwards as it is a retired camera model.  If you install the 2.54.2 version then the L515 should be detected.
https://github.com/IntelRealSense/librealsense/releases/tag/v2.54.2

I tried the new version but still, it couldn't read it

Platform Camera is usually used for accessing a non-RealSense RGB camera such as the webcam on a laptop.  Not all webcam laptops will work with the Platform Camera feature though, unfortunately.  Some laptops work with it and others do not.

Hi @nohaalaref  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


[Durable Objects] Hibernatable WebSockets -> just WebSockets.

This PR:

[x] Clarifies this doc covers the entire WebSockets API.
[x] Adds a warning about console.log inside the websocket* handler methods (not currently supported) - fixes https://github.com/cloudflare/workers-sdk/issues/3936

It would be great to get this update cleaned up and landed... 🙏

Closing this because the relevant change seems to have been made in another PR, and the warning about console.log() is no longer required as the runtime has supported it for a while.


#151: Remove colorama init, Only use colorama on windows

Description of new feature, or changes

Colorama.init escapes all ansi codes by default on stdout / stderr when not in a tty, regardless of OS, which breaks color output. Instead of globally affecting stdout and stderr at library import time, only wrap the stream that Halo uses.
Also, I turned colorama into a conditional dependency, seeing as its only needed on windows.
Something to note: there's a change in behavior here.
Previously:

Windows
Other

stdout isatty()
convert
ansi

stdout not isatty()
strip
strip

stream isatty()
ansi
ansi

stream not isatty()
ansi
ansi

Now:

Windows
Other

stdout isatty()
convert
ansi

stdout not isatty()
strip
ansi

stream isatty()
convert
ansi

stream not isatty()
strip
ansi

(convert: ansi converted to win32 calls, strip: ansi removed, ansi: ansi unchanged)
You may consider using colorama to strip the output when the stream is not a tty, regardless of OS, but you should likely have a way to override the behavior. (See also: https://github.com/tartley/colorama/pull/230)
Checklist

[x] Your branch is up-to-date with the base branch
[ ] You've included at least one test if this is a new feature
[x] All tests are passing

Related Issues and Discussions
https://github.com/manrajgrover/halo/issues/151
People to notify

Thanks

Thanks


host.docker.internal not supported

newer docker for mac versions support mapping the docker host address to host.docker.internal, see also https://docs.docker.com/docker-for-windows/networking/
this is not supported in docker machine for parallels.

Hi @rburgst
Yes, I can confirm it's not supported in Docker Machine, but there is nothing what we can do with that on our plugin side.
And unfortunately I don't think it will ever be available in Docker Machine, because both Docker Machine and boot2docker (the Linux distribution with Docker Engine) are in maintenance mode / end-of-support:

https://github.com/docker/machine/issues/4537
https://github.com/boot2docker/boot2docker/pull/1408

I can only recommend you trying the explicit --add-host argument (or its analogue for docker-compose if you use it):
$ docker run -it --add-host=host.docker.internal:$(docker-machine ip) alpine cat /etc/hosts
<IP_ADDRESS>	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
<IP_ADDRESS>	host.docker.internal
<IP_ADDRESS>	063361bb830b

Thanks a lot for your prompt reply!


Update weaver-cats, weaver-discipline, ... to 0.7.12

Updates

com.disneystreaming:weaver-cats
com.disneystreaming:weaver-discipline
com.disneystreaming:weaver-scalacheck

from 0.7.11 to 0.7.12.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.disneystreaming" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "com.disneystreaming" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #152.


added Localization example

This is regarding issue #14

thanks for the PR @skezo! I'll take a look at merging it asap :)

No worries. Let me know if you need anything changed


Fix map display for moving TF frame

Instead of the current time, use Time(0) to get the latest available transform as a fallback.
This is the same logic that is applied in RViz from ROS 1.
Resolves #332
Although we are using TF message_filters to deliver the map to the display, the display itself is doing a transformation:
https://github.com/ros2/rviz/blob/045227a9fc251ab9e5af763bddc1f203aff6feac/rviz_default_plugins/src/rviz_default_plugins/displays/map/map_display.cpp#L576-L579
And even though it is using the current time (just a few lines before), it is off by less than a second causing the extrapolation exception. I noticed the ROS 1 implementation is slightly different, defaulting to the latest available transform by passing Time(0) (the related PR is https://github.com/ros-visualization/rviz/pull/1066):
  if (!context_->getFrameManager()->transform(frame_, transform_time, current_map_.info.origin, position, orientation) &&
      !context_->getFrameManager()->transform(frame_, ros::Time(0), current_map_.info.origin, position, orientation))

https://github.com/ayrton04/rviz/blob/8f482f494ee4031ed04b3065a9755710b61176bf/src/rviz/default_plugin/map_display.cpp#L719-L720

Linux
Linux-aarch64
macOS
Windows

IT'S ALIVE!

I guess using Time(0) should be the same in all displays? If that is true, a quick search reveals that this is also wrong in the axes display (my bad) and all pointcloud displays (see pointcloud common). The background is that when we ported most of the displays, the time API wasn't finished and we mostly tested with static publishers.
Should this be done in a different ticket or do you prefer to do it here?

Should this be done in a different ticket or do you prefer to do it here?

I also noticed these other occurrences. I was going to investigate further to see if I can reproduce the same issue with the other displays before proceeding. I can create a ticket for (potentially) fixing the other displays.

I've opened up a follow-up https://github.com/ros2/rviz/issues/484


PHOENIX-6480 Move phoenix-tool and add support with generating defaul…

…t properties

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 34s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

+0 :ok:
mvndep
5m  0s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
17m  9s
master passed

+0
hbaserecompile
28m 47s
HBase recompiled.

+1 :green_heart:
compile
1m 51s
master passed

+1 :green_heart:
checkstyle
1m 14s
master passed

+1 :green_heart:
javadoc
2m 58s
master passed

+0 :ok:
spotbugs
4m 54s
root in master has 1032 extant spotbugs warnings.

+0 :ok:
spotbugs
3m  5s
phoenix-core in master has 970 extant spotbugs warnings.

+0 :ok:
spotbugs
0m 39s
phoenix-tools in master has 3 extant spotbugs warnings.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
14m  6s
the patch passed

+0
hbaserecompile
20m 28s
HBase recompiled.

+1 :green_heart:
compile
1m 40s
the patch passed

+1 :green_heart:
javac
1m 40s
the patch passed

-1 :x:
checkstyle
1m  6s
root: The patch generated 27 new + 317 unchanged - 25 fixed = 344 total (was 342)

-1 :x:
whitespace
0m  0s
The patch 2 line(s) with tabs.

+1 :green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
2m 21s
the patch passed

-1 :x:
spotbugs
3m 29s
phoenix-core generated 3 new + 970 unchanged - 0 fixed = 973 total (was 970)

_ Other Tests _

-1 :x:
unit
124m 25s
root in the patch failed.

-1 :x:
asflicense
2m 24s
The patch generated 614 ASF License warnings.

209m 25s

Reason
Tests

FindBugs
module:phoenix-core

org.apache.phoenix.schema.tool.SchemaTool.conf should be package protected  In SchemaTool.java: In SchemaTool.java

Possible null pointer dereference of cmdLine in org.apache.phoenix.schema.tool.SchemaTool.parseOptions(String[])  Dereferenced at SchemaTool.java:cmdLine in org.apache.phoenix.schema.tool.SchemaTool.parseOptions(String[])  Dereferenced at SchemaTool.java:[line 114]

Write to static field org.apache.phoenix.schema.tool.SchemaTool.conf from instance method org.apache.phoenix.schema.tool.SchemaTool.run(String[])  At SchemaTool.java:from instance method org.apache.phoenix.schema.tool.SchemaTool.run(String[])  At SchemaTool.java:[line 73]

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1279/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1279

Optional Tests
dupname asflicense javac javadoc unit xml compile spotbugs hbaserebuild hbaseanti checkstyle

uname
Linux 5ebc2ecf8639 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / a4f0304

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1279/1/artifact/yetus-general-check/output/diff-checkstyle-root.txt

whitespace
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1279/1/artifact/yetus-general-check/output/whitespace-tabs.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1279/1/artifact/yetus-general-check/output/new-spotbugs-phoenix-core.html

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1279/1/artifact/yetus-general-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1279/1/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1279/1/artifact/yetus-general-check/output/patch-asflicense-problems.txt

Max. process+thread count
9680 (vs. ulimit of 30000)

modules
C: phoenix-core phoenix-assembly . U: .

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1279/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


"Final" CAD Revisions

[x] Update S2 Magnets
[x] S3 Revisions
[x] Modify lid to cover bot more
[x] Expand buffer around battery
[x] Tighter tolerance on brace
[x] Chamfer brace corners
[x] Make middle lid support wider
[x] Cable management

#111


java.lang.NullPointerException

Sadly, it doesn't go very far...
javadoc: error - In doclet class com.spirit21.Doclet,  method start has thrown an exception java.lang.reflect.InvocationTargetException
java.lang.NullPointerException
at com.spirit21.spring.parser.OperationParser.createOperations(OperationParser.java:49)
at com.spirit21.spring.parser.PathParser.createOperation(PathParser.java:116)
at com.spirit21.spring.parser.PathParser.createPath(PathParser.java:92)
at com.spirit21.spring.parser.PathParser.setPath(PathParser.java:59)
at com.spirit21.spring.parser.Parser.run(Parser.java:43)
at com.spirit21.Doclet.runParser(Doclet.java:55)
at com.spirit21.Doclet.start(Doclet.java:47)

We need some more information to understand the problem.

I just let it run over my codebase. Since the error did not indicate anything more precise than this "NullPointerException" without more information, I do not know where or what in the code might have caused it. It's not a "hello world", it's actual code with many classes.
 The child classes of it are the controllers, with a class-level request mapping, resulting in /child/foo, /child/bar for example.

Thanks for your fast answer.
For the version 0.5 a better logging is planned. I hope to release the new version by the end of the week at the latest. After that you can try it again and hopefully we can fix your problem. 😃

Sorry, it takes a little bit longer. I have updated some dependency versions and some of them has changed a lot.

Has this been fixed? I am getting same error without much explanation


New entities: snapshots

At this time we have created a somewhat special kind of documents: snapshots.
For example, there are snapshots for items: copies of a live item saved by a user. This items differ from the regular ones:

They are not in a room nor in a user inventory.
They are immutable.
They should not be taken into account for unique naming checks.

Because of this, I propose that we create a new entity for each old one that we want to snapshot, and keep the snapshots there.

For now we will proceed with the simplest methods: add a boolean field to the Item entity (the only one that needs snapshots for the time being) that tells us wether it is a snapshot or not.

For now we will proceed with the simplest methods: add a boolean field to the Item entity (the only one that needs snapshots for the time being) that tells us wether it is a snapshot or not.


Define decimal points per currency

In a module for example. Or use 2 as a default and only add exceptions.

Implemented with v1.2.1.


Upgrade to Spark 3.5.0

This issue is created to analyze whether we can upgrade our Spark 3.x dependencies to 3.5.0.
Apache Pinot connects to Apache Spark in two different types of modules:

batch ingestion plugins (modules pinot-batch-ingestion-spark-3.2 and pinot-batch-ingestion-spark-2.4), used to ingest data from Spark.
connectors (modules pinot-spark-3-connector and pinot-spark-2-connector), used to use Spark to query Pinot.

Note that we need to support these two major Spark versions for compatibility reasons.
As explained in https://github.com/apache/pinot/issues/11656, one of the reasons we cannot officially support Java 21 is that Spark 3.x do not support Java 21 until version 3.5. It seems there is no issues with Spark 2.x versions.
It is not clear to me exactly which Spark version we are using. As expected, pinot-batch-ingestion-spark-3.2 uses spark 3.2.x (specifically 3.2.1) while pinot-spark-3-connector uses 3.4.0. It also seems that Pinot distribution does not includes the connectors (which makes sense), and the final jars will contain the 3.2.1 version.
Spark versioning semantics are defined here. Notice that they do not follow semantic versioning. Specifically:

An API is any public class or interface exposed in Spark that is not marked as “developer API” or “experimental”. Release A is API compatible with release B if code compiled against release A compiles cleanly against B. Currently, does not guarantee that a compiled application that is linked against version A will link cleanly against version B without re-compiling. Link-level compatibility is something we’ll try to guarantee in future releases.

There is also a document where they specify the changes from version to version. We would need to understand the changes from 3.2 to 3.3, 3.3 to 3.4 and finally 3.4 to 3.5.
I've done some checks, modifying the dependency to 3.5.0 and:

Tests run correctly
We also need to change our dependency from slf4j from 1.7.x to 2.x.x. This should be a backward compatible change (see https://www.slf4j.org/faq.html#changesInVersion200)

I've opened #11702 to test a blind upgrade from current 3.2.4 to 3.5.0

I've modified #11702 as ready to review.
I was able to run all our tests without issues with Spark 3.5 instead of 3.2, but I didn't tried my branch in an actual scenario where spark is being used. Reading Spark documentation, it seems that the changes are backward compatible.
It would be nice to have a review from contributors with experience in Spark.

We can consider this done

Mostly curious because don't actually use the connector. But why don't we split the connector modules into spark3.x versions?

You mean having one 3.2 and one 3.5 project? We don't usually do that. I mean, imagine we needed to create one single plugin for each technology and each version. It would be very difficult to maintain!
For some wildly used technologies like Kafka and Spark we maintain several backward incompatible projects. For example we have one plugin for kafka 0.9 and another for kafka 2.0. We also had a spark 2.4 and 3.2, so users that use the incompatible 2.x and 3.x versions can actually deploy the plugin they need.
But Spark 3.5 should be backward compatible with 3.2, so we don't see a reason to have to maintain 3 different spark plugins (2.4, 3.2 and 3.5). Therefore we decided to rename 3.2 as 3.x and upgrade spark client version from 3.2 to 3.5.

But Spark 3.5 should be backward compatible with 3.2

ah my bad. I should have read the spark docs first. It does seem they expect all the same major versions to be compatible.

While upgrading Spark 3.3.0 to 3.5.0 facing errors. { using java 17 , scala 2.13} for building spark 3.5.0
step to produce error..

clone spark 3.5.0 from apache spark github
Go to spark directory and run the command. ---->    ./build/mvn -DskipTests clean package

Tried with diff versions of scala also same issue.
[ERROR] Failed to execute goal net.alchim31.maven:scala-maven-plugin:4.8.0:compile (scala-compile-first) on project spark-core_2.13: Execution scala-compile-first of goal net.alchim31.maven:scala-maven-plugin:4.8.0:compile failed: org.apache.commons.exec.ExecuteException.
Please help me on this, i'm stuck here, did research , did googling all but could not solve it .

While upgrading Spark 3.3.0 to 3.5.0 facing errors. { using java 17 , scala 2.13} for building spark 3.5.0
step to produce error..
clone spark 3.5.0 from apache spark github
Go to spark directory and run the command. ----> ./build/mvn -DskipTests clean package

I don't think we compile Spark our self. You may need to go to the Spark github repo to look for support compiling it.


Create REPL aliases to allow filtering REPL configs through kast.

In the latest K version, one can use the command
kast -i kore -o pretty -d <definition_dir> <file.kore>

to format a kore term as a K term.
Note that the output of the REPL configurations might need some fiddling as last time I checked it was not valid KORE :-)

Does kast work with pipes instead of an input file? Like cat file.kore | kast -i kore -o pretty -d .?

I don't know, but it shouldn't be hard to make it accept input from stdin.

[ ] fix kore unparser: https://github.com/kframework/kore/pull/762
[ ] split repl output
[ ] use kast with pipe (or workaround from repl)
[ ] create repl script with aliases


Time conversion - Minutes to hours

Summary
We have the ability to convert and print different time values to minutes for better readability.
It is nicer to implement minute to hour conversion function to make it even more readable.

Hi, @pouriyajamshidi.
I'd like take up this issue.
Is it okay to add the functionality to calcTime?
And, may I add the like following test?
package main

import "testing"

func Test_calcTime(t *testing.T) {
	type args struct {
		time uint
	}
	tests := []struct {
		name string
		args args
		want string
	}{
		{
			name: "1 second",
			args: args{1},
			want: "1 second",
		},
		{
			name: "59 seconds",
			args: args{59},
			want: "59 seconds",
		},
		{
			name: "1 minute",
			args: args{1 * 60},
			want: "1 minute",
		},
		{
			name: "59 minutes",
			args: args{59 * 60},
			want: "59.0 minutes.seconds",
		},
		{
			name: "1.5 minute.seconds",
			args: args{1*60 + 5},
			want: "1.5 minute.seconds",
		},
		{
			name: "2.5 minutes.seconds",
			args: args{2*60 + 5},
			want: "2.5 minutes.seconds",
		},
	}
	for _, tt := range tests {
		t.Run(tt.name, func(t *testing.T) {
			if got := calcTime(tt.args.time); got != tt.want {
				t.Errorf("calcTime() = %v, want %v", got, tt.want)
			}
		})
	}
}

Hi @icemint0828,
Thanks for reaching out. You are more than welcome to take up this ticket.
To answer your questions:

The check has to indeed extend calcTime. However, it is better to have the actual logic in a separate function like calcSeconds for easier referencing and refactoring in the future.
The test at the first glance looks good to me. But it is better to name it like TestCalcTime to conform to Go's styling.

If you see some other parts of the code can use test cases and improvements, please feel free to open issues for them too.
Thanks!

Thank you for your thoughtful response!
I understand both.
I get to work.

Thank you for your thoughtful response! I understand both.
I get to work.

Thanks and best of luck!


Not able to run az ml folder attach

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
az ml folder attach was working with the previous az cli version 2.29.1 vs 2.30.0.
To Reproduce
az ml folder attach
Expected behavior
Instead of a success, we get:
2021-11-02T13:36:50.8211470Z [command]/bin/bash /agent/_work/_temp/azureclitaskscript1635860209071.sh
2021-11-02T13:36:51.8133956Z ERROR: __init__() got an unexpected keyword argument 'async_persist'

Environment summary
Use azure-cli-ml from Azure DevOps agents

route to service team

Relevant service team has been notified and is actively working on a fix.

@rcavalieri819 To unblock you, could you please downgrade the azure-cli/azure-cli-core version to be less than 2.30.0?
You can refer to this comment on how to downgrade the azure cli.  https://github.com/Azure/azure-cli/issues/13331

This is an Issue effecting one of our pipelines as well. Specifically when running the az ml model deploy command. Is there an ETA for the fix?

@ranikamadurawe I have managed to workaround this by editing authentication.py in .Azure\cliextensions\azure-cli-ml\azureml\core. Removing the 'async_persist=False' parameter seems to have done thr trick.

I tried @jhliberis method but was not working for me and then i tried downgrading az cli to 2.29.1 as suggested by @Mossaka , and downgrading worked for me. I am using self hosted agent and i ran below command for downgrading:
sudo apt-get install azure-cli=2.29.1-1~bionic

sudo apt-get install azure-cli=2.29.2 works like a charm!!
Please fix the issues with the azure-cli=2.30.0 version asap... It caused a lot of pipelines to fail in production.

im having the same error, any updates? please

Seeing the same error by running az ml datastore detach and az ml datastore attach-adls-gen2
azure-cli                         2.30.0
core                              2.30.0
telemetry                          1.0.6
Extensions:
azure-cli-ml                      1.33.0

Our error is in our releases in azurecli with the command:
az ml workspace show -g X-AML-RG -w X-AML-WS --query keyVault -o tsv
ERROR: init() got an unexpected keyword argument 'async_persist'

Getting the same error here, any news on updates or quick fixes?

we were able to fix the issue in DevOps using the following (installing 2.29.2)
sudo apt remove azure-cli -y && sudo apt autoremove -y;
            sudo apt-get update;

            sudo apt-get install ca-certificates curl apt-transport-https lsb-release gnupg;

            curl -sL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/microsoft.gpg > /dev/null ;

            AZ_REPO=$(lsb_release -cs);

            echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $AZ_REPO main" | sudo tee /etc/apt/sources.list.d/azure-cli.list ;

            sudo apt-get update;

            apt-cache policy azure-cli;

            sudo apt-get install azure-cli=2.29.2-1~bionic;

Thanks, @Jerry1309 this works great as a work-around, thanks for posting/sharing so we can all get temporarily unblocked!
Silly comment, but could you edit your formatting so that the first/initial line is also included in the code block region?  This initially didn't work for me b/c the COPY CODE feature of the site doesn't include the first line of your script and I missed porting it in my first-pass attempt at duplicating your success for our own pipeline :P
(just a suggestion to save others some time troubleshooting if/when they also attempt to repro based on your post, thanks again!)

Thanks @Jerry1309. I have blocked with this error when I am trying MLOps Poc, My error is also same, I was able to resolve the issue with the workaround you provided. Script lines worked the exact same for me. Only change is, I need to add the "--allow-downgrades" option in the last command, and I tested in 'ubuntu-18.04'.

Thanks @Jerry1309. I have blocked with this error when I tried MLOps Poc, my error is also same, I was able to resolve the issue with the workaround you provided. Script lines worked the exact same for me. Only change for me is, I need to add the "--allow-downgrades" option in the last command when I notice a downgrade error, and I tested in 'ubuntu-18.04'.

Glad to know it worked for you, you might have missed the cli removal part.
Option 2 in this documentation helped me https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux?pivots=apt

Still getting errors while running sudo apt-get install azure-cli=2.29.2-1~bionic;
E: Version '2.29.2-1~bionic' for 'azure-cli' was not found
/home/vsts/work/_temp/azureclitaskscript1636613378792.sh: line 17: az: command not found
/home/vsts/work/_temp/azureclitaskscript1636613378792.sh: line 19: az: command not found
##[error]Script failed with error: Error: The process '/usr/bin/bash' failed with exit code 127

Any help?

Still getting errors while running sudo apt-get install azure-cli=2.29.2-1~bionic;
E: Version '2.29.2-1~bionic' for 'azure-cli' was not found
/home/vsts/work/_temp/azureclitaskscript1636613378792.sh: line 17: az: command not found
/home/vsts/work/_temp/azureclitaskscript1636613378792.sh: line 19: az: command not found
##[error]Script failed with error: Error: The process '/usr/bin/bash' failed with exit code 127

Any help?

did you add the cli software repo by running
AZ_REPO=$(lsb_release -cs)
echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $AZ_REPO main" |
sudo tee /etc/apt/sources.list.d/azure-cli.list
if sudo apt-get install azure-cli=2.29.2-1~bionic is not working for you try with sudo apt-get install azure-cli=2.29.2-1~focus
hope you are following all the commands including the removal of the current version from the Agent

Yes, Thanks. It solves that error by using sudo apt-get install azure-cli=2.29.2-1~focal; but it asks for az login again.
I guess I need to write that step manually again.

I had the same issue with version 2.30.
It did work with 2.29.
I used the command below to change from 2.30 to 2.29.
python -m pip install -U --force-reinstall pip pip install azure-cli==2.29

Downgrading to azure cli to 2.29 is causing new issues  in downloading azure artifacts. As azure-devops extension is not compatible with it.
Any intermediate solutions ?
WARNING: The 'azure-devops' extension version 0.22.0 is not compatible with your current CLI core version 2.29.0.
This extension requires a min of 2.30.0 CLI core.
Please run 'az upgrade' to upgrade to a compatible version.
ERROR: 'artifacts' is misspelled or not recognized by the system.

@pragasv , you need to do something like this:
pip install --upgrade --force-reinstall --no-cache-dir "azure-cli<2.30.0"
az extension remove -n azure-devops
az extension add -n azure-devops --version 0.21.0

@dkmiller thanks for the comment, when i tried the approach you suggested i ran into a following issue for the same service connection. Is this a known issue ?
ERROR: Unable to get 'ResourceType.MGMT_RESOURCE_SUBSCRIPTIONS' in profile 'latest'
##[error]Error Code: [1]
##[error]Error: Azure login failed
##[error]Script failed with error: ERROR: Unable to get 'ResourceType.MGMT_RESOURCE_SUBSCRIPTIONS' in profile 'latest'

also i was able to get the pipeline for the following version configurations now.
azure-cli                         2.30.0

core                              2.30.0
telemetry                          1.0.6

Extensions:
azure-devops                      0.22.0

@ranikamadurawe I have managed to workaround this by editing authentication.py in .Azure\cliextensions\azure-cli-ml\azureml\core. Removing the 'async_persist=False' parameter seems to have done thr trick.

Thanks to this suggestion, I monkey-patched azure.cli.core._profile.Profile.__init__ to accept the old async_persist argument:
import azure.cli.core._profile

profile_init_orig = azure.cli.core._profile.Profile.__init__

def profile_init_new(__self, cli_ctx=None, storage=None, async_persist=False):
    profile_init_orig(__self, cli_ctx, storage)

azure.cli.core._profile.Profile.__init__ = profile_init_new

This still isn't fixed, and updates please?

@pragasv, Downgrade to version 2.29.1 as indicated in Install specific version - Microsoft Docs . In my case most of the Azure ML CLI v1 are failing with the last version of Azure CLI. I won't suggest pip install directly as you may break other things. You can refer to this GitHub Action that installs an specific version of the CLI if needed aml-cli-install

Im facing the same error __init__() got an unexpected keyword argument 'async_persist' in my Github actions workflow. I
cannot downgrade to CLI version to 2.29 since I'm using OIDC authentication for logging in to azure and OIDC requires at least 2.3 version of CLI.  Please suggest a work around for this.

Im facing the same error __init__() got an unexpected keyword argument 'async_persist' in my Github actions workflow. I cannot downgrade to CLI version to 2.29 since I'm using OIDC authentication for logging in to azure and OIDC requires at least 2.3 version of CLI. Please suggest a work around for this.

this issue got resolved with latest version of azml cli extension


[HELP] streamCartesianMotion Input Validation

Under the documentation for streamCartesianMotionForce, it says to stream smooth and continuous motion commands. Is there a standard we can use to validate that a stream is smooth enough? In other words, what is the maximum allowable delta between two subsequent stream values for the position and the quaternion?

Hi @yellownebula10 ,
When using streamCartesianMotionForce, it is up to the user to create the trajectories and motion control profile for robot actions. You can refer to this picture below when streaming cartesian positions:

[Trapezoidal Velocity Profile from Mathworks]
For linear position on Rizon arms:

The typical peak velocity for Rizon arms is at 1 m/s (with max velocity at 2.2 m/s, but note this max velocity may trigger robot fault in some challenging joint poses).
The typical peak acceleration for Rizon arms is at 1.5 m/s^2 (with max acceleration at 3 m/s^2).

For angular rotation on Rizon arms:

The typical peak angular velocity for Rizon arms is at 300 deg/s (with max angular velocity at 800 deg/s, but note this max angular velocity may trigger robot fault in some challenging joint poses).
The typical peak angular acceleration for Rizon arms is at 300 deg/s^2 (with max acceleration at 800 deg/s^2).

Since Streaming is at 1kHz frequency, you could multiply the above numbers by 0.001 seconds to get the delta distance. During the "Phase 2 constant speed" of the motion control profile, with a typical peak velocity, the maximum allowable delta distance is 0.001[s] * 1[m/s] = 0.001[m] (This is not applicable during "Phase 1 Acceleration" and "phase 3 Deceleration").
Using RT streaming control can be quite complex. If your trajectory points are more spread out and less complex (recommended minimum 100Hz frequency), you could save some time by utilizing an NRT discrete cartesian control [sendCartesianMotionForce] and letting the robot's internal motion generator does all the difficult work.
https://github.com/flexivrobotics/flexiv_rdk/blob/06b38ad52fc93b0ffa0b4976d734e2221bf523a4/include/flexiv/Robot.hpp#L495

Thank you @kaibiao-flexiv . If we were to record the robot's position while in joint floating mode and wanted to stream it back, given that the trajectory is not complicated, would it be better to use NRT streaming at <100Hz or RT streaming at 1kHz? We are already automatically recording all the robot states at 1kHz, so it would just be a matter using every point or not.

Hi @yellownebula10 ,
If the position data was recorded at 1kHz, you should be able to RT stream them back to the robot at 1kHz in order to replay the action. If PC's RT streaming performance is not perfect at 1kHz rate, then you can downsample the data to 10% (by averaging them per 10 sample data) and apply NRT sendCartesianMotionForce at 100Hz.

Got it, thanks @kaibiao-flexiv


Test 4 unknown issue

Traceback (most recent call last):
  File "testris.py", line 163, in main
    try: run_tests(cmdline, use_shell)
  File "testris.py", line 135, in run_tests
    run_test(program, opcodes)
  File "testris.py", line 111, in run_test
    program.stdin.flush()
OSError: [Errno 22] Invalid argument

Oh no! Testris encountered an unexpected problem while
attempting to run your program. Please report the above
traceback in the issue tracker, so that we can help you
with the problem and provide a better error message in
the future.

How did you run testris.py? (Also, could you hop on our IRC?)

errno 22:
       EINVAL fd  is  attached  to  an  object  which  is unsuitable for writing; or the file was opened with the
              O_DIRECT flag, and either the address specified in buf, the value specified in count, or  the  cur‐
              rent file offset is not suitably aligned.

so I have no idea how that happened...

This probably was a valid bug, but the subprocess stuff has all changed dramatically since 2015 (the old runner was written for python 2.7), so I'm just going to close this, and not be surprised if something similar crops up on the tanco issues list.


How about support Atlassian Stash

We all use Git in Atlassian Stash : )

it would be great for me too

I have to agree with @foobra please support Stash :)

+1


Screen turns gray after many pages and page memory per book

As commented this on the epdiy slack code channel we could add a full refresh every X pages. No idea what it will be ideal, but after 4 or 5 I'm already experiencing artifacts.
Note that they appear mostly when on battery, when you connect it to USB, they get away after some minutes.
This in conjunction with #23 it may make a better reading experience.
Also for me the feature that will be awesome is to have it to conserve the page number for each book, when you switch between Epub list mode and read mode. So you can read different books at the same time without the need to press the next page a zillion of times to get to the last page you read.
Would be complicated to store a key-> value table in NVS to add this feature?
Characters that are missing and replaced by ?
...  Page 18 of the poetry book
¯   No idea if it's exacly this char but it's called "macron" and it's like the _ but in the center.
in a book I also saw an html space entity:

not being parsed.
Maybe we can detect more and make a special character, for example the 3 dots could be text replaced by 3 real dots, that's a no brainer. And then for the exceptions we replace by " " space that will be in my opinion the safest way to go.

Update: This is partly solved using the Waveform for this epaper (Still waiting to see when battery goes down)
But at least the screen looks clear, the fonts much darker and so far no artifacts like that silly lines that appear below the battery.


Added augumented trees in binary tree guide

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hi @rachita18144 , thanx for opening this pr and congratulations on your first contribution to FCC. We look forward to future contributions :balloon:


Writing to Stderr broke our Azure pipelines!

OS: Ubuntu 22.04
helm 3.10.2 x64
In Azure devops pipelines we have some basic helm commands in powershell tasks. As of 3.10.2 these are writing to stderr and will result in the whole task failing with an error (unless I ignore stderr which I prefer not to). The basic task is like so:
    # Sign into registry
    $env:SP_SECRET | helm registry login $fullRegistryName `
      --username $env:SP_CLIENT_ID `
      --password-stdin

    # Pull and archive chart.
    helm pull $chartUrl --version $latestHelmChart
    tar xf $env:CHART_NAME-$latestHelmChart.tgz

The output of this script is like so:
##[error]PowerShell wrote one or more lines to the standard error stream.
##[error]Login Succeeded
##[error]Pulled: myacr.mychart:myversion

I'm not sure of the context for this changeset but I guess it's the culprit. A successful login should not be an error obviously.

Thanks for the link to the change. I think @jouve will need to comment here.
A possibility is to redirect the stderr output to stdout for the helm registry login command. I'm not familiar with powershell, but I think that should be a possibility, rather than ignoring.

hi, those lines broke helm commands using structured --output (json, yaml) and helm template (#11385).
as a workaround, I guess you can redirect stderr to stdout  (2>&1)

Perhaps those should only go to stderr when using structured output?

@jouve Is there a fix for Helm template output?

We just had all our pipelines fail for the same reason. I can see why the change was made, but printing success messages on stderr is not the greatest idea, and it will cause endless issues if left in this state. Redirecting output for that particular command is a workaround, not a solution.
We're not using structured output, so only using stderr in that case would fix it for us. Without really knowing anything about this, I think a better solution would be to totally disable output of non-errors when using structured output.

@jouve -- perhaps we should consider reverting the stderr change? And consider one of the options above (only use stderr when doing structured output, or don't have these messages logged when doing structured output? Or something else?)

Only using stderr when doing structured output doesn't help with the original issue since neither helm registry login nor helm pull use structured output.
I am not familiar with powershell at all, but this looks like a user error to me.  It is reasonable to expect the caller to check exist status and not assume that stuff in stderr indicates failure.   The redirect suggested in https://github.com/helm/helm/issues/11533#issuecomment-1312176464 is also a reasobale solution. There are plenty of tools that send output to separate streams even on success.  So this seems like a reasonable change in behavior and the broken pipelines should be adjusted to accomodate.

The use of stderr is common among many tools including kubectl. For example, the implementation of API server warnings makes use of this same technique where the warning text is sent to stderr and expected output was sent using stdout.
Given the approach being leveraged by a comparable tool with similar functionality, I am challenged to see a reason that a revert to prior functionality would be warranted.

The use of stderr is common among many tools including kubectl. For example, the implementation of API server warnings makes use of this same technique where the warning text is sent to stderr and expected output was sent using stdout.
Given the approach being leveraged by a comparable tool with similar functionality, I am challenged to see a reason that a revert to prior functionality would be warranted.

I agree stderr is common among various tools. In my experience it is generally reserved for errors or diagnostic information as they relate to warnings like certain flags are being deprecated or we're about to exit with a non zero exit code and here's why. You cited kubectl but they are using it for exactly this purpose, not for normal output.  In my opinion this is a change will present challenges going forward for helm to communicate such warnings and diagnostic information to users. I will respect the collective wisdom of the contributors of this repo.

I would vote to use stderr or errors only, and stdout for information like it was before. Redirecting all stderr to stdout would ignore real errors like a wrong login.

Can we please have an update on this. We have ALLOT of scrips (for many years) that relied on stderr to indicate something is wrong and script should abort (this includes cases where warnings are output on stderr).
Just about all our scripts start with set -e which allows our scripts to fail on the first error/warning (without even having to check error codes after every call)
With this change a successful registry login now fails!
It is very reasonable to suggest (like many other users already suggest) you just simply do not output "information" text when structured output is requested. But directing information text to stderr is just... well think about it, it does not even make logical sense! And to make this breaking change in a minor release even more frustrating!

set -e fails on non-zero exit code, not stderr.
Yes, outputting informational text to stderr does make perfect sense. It's been an industry standard for decades.
For example:
tar cv /etc > /tmp/etc.tar

will output the tarfile to stdout, and the list of files to stderr.
#11593 will solve your issue though. Just need core maintainers to review things and merge them. Nothing I can do about that, unfortunately.

Hi, can we have an update on how is this going?

The use of stderr is common among many tools including kubectl. For example, the implementation of API server warnings makes use of this same technique where the warning text is sent to stderr and expected output was sent using stdout.
Given the approach being leveraged by a comparable tool with similar functionality, I am challenged to see a reason that a revert to prior functionality would be warranted.

I agree stderr is common among various tools. In my experience it is generally reserved for errors or diagnostic information as they relate to warnings like certain flags are being deprecated or we're about to exit with a non zero exit code and here's why. You cited kubectl but they are using it for exactly this purpose, not for normal output. In my opinion this change will present challenges going forward for helm to communicate such warnings and diagnostic information to users. I will respect the collective wisdom of the contributors of this repo but it adds overhead to scrutinize the stderr feed for actual warnings being presented.

Agree. Because of this uncanny code change, we will have to fix our helm version to 3.10.1 forever, or we have to change the default behavior in our code to pickup from stderr, the normal stdout.

Writing messages like Login Succeeded to stderr breaks GitHub Actions too (and likely Jenkins). I've just encountered this today when upgrading from 3.9.3 to 3.12.3.
For tools like GCC using stderr makes a lot of sense when compiling and linking code especially when multiple error cases are reported. For trivial messages maybe adding a --verbose setting is the way to go?

helm logs & interaction is a bit "confused"

users can't control granularity because there is a single --debug "all or nothing"
some modules use go "log" module, sometimes with a "log level" in the string "Warning:   or "[INFO]
some modules use fmt.Fprintf
some fmt.Printf
pkg/registry uses "logrus"

Hey, this behavior surprised us today as well when we upgraded helm to 3.10.2+ (to the latest version actually). Our pipelines started to fail on standard console output actually, example:


Your not actually mounting the docker.sock

docker run -d --restart unless-stopped --privileged -it -v /var/run/docker.sock:/var/run/docker.sock -v /sys/fs/cgroup:/sys/fs/cgroup:rw -e connectionString='<IOT_EDGE_DEVICE_CONNECTION_STRING>' --hostname=edgedevice1 --name iot-edge-device egilhansen/iothub-edge-device:1.5.0-amd64 --dns <IP_ADDRESS> --log-driver "json-file" --log-opt "max-file=10" --log-opt "max-size=200k"
-v /var/run/docker.sock:/var/run/docker.sock
This part is correct and this should mount the docker.sock, but in the docker-entrypoint.sh
exec /lib/systemd/systemd --log-level=info
When this fires off, it will reset /var/run/  and anything you had put in there will be removed.   Docker then runs and creates a new docker.sock file so everything works.
The host and edge container dont see each others containers.   Right now, when this edge container runs,  it uses its nested docker instance causing it to pull images and create containers inside its own instance basically creating a massive layer where all your edge modules live.     When you delete this edge container , you lose all the modules and images that it pulled.
If we can actually pass the docker.sock , then instead of creating the module containers under itself, it can create them as siblings instead of children.   Images are shared with the host and both instances of docker see the same thing.   If you update this container, all the other module containers will still persist.
I have tried moving the docker.sock into a different location and targeting that, but i get the issue from edge deamon
root@edgedevice1:/# iotedge check --verbose

Configuration checks (aziot-identity-service)
---------------------------------------------
√ keyd configuration is well-formed - OK
√ certd configuration is well-formed - OK
√ tpmd configuration is well-formed - OK
√ identityd configuration is well-formed - OK
√ daemon configurations up-to-date with config.toml - OK
√ identityd config toml file specifies a valid hostname - OK
√ aziot-identity-service package is up-to-date - OK
√ host time is close to reference time - OK
√ preloaded certificates are valid - OK
√ keyd is running - OK
√ certd is running - OK
√ identityd is running - OK
× read all preloaded certificates from the Certificates Service - Error
    could not load cert with ID "aziot-edged-trust-bundle"
    Caused by:
        parameter "id" has an invalid value
        caused by: not found
        caused by: could not load cert with ID "aziot-edged-trust-bundle"
                   Caused by:
                       parameter "id" has an invalid value
                       caused by: not found
√ read all preloaded key pairs from the Keys Service - OK
√ check all EST server URLs utilize HTTPS - OK
√ ensure all preloaded certificates match preloaded private keys with the same ID - OK

Connectivity checks (aziot-identity-service)
--------------------------------------------
√ host can connect to and perform TLS handshake with iothub AMQP port - OK
√ host can connect to and perform TLS handshake with iothub HTTPS / WebSockets port - OK
√ host can connect to and perform TLS handshake with iothub MQTT port - OK

Configuration checks
--------------------
√ aziot-edged configuration is well-formed - OK
√ configuration up-to-date with config.toml - OK
√ container engine is installed and functional - OK
× configuration has correct URIs for daemon mgmt endpoint - Error
    SocketError - SocketErrorCode (ConnectionRefused) : Connection refused /var/run/iotedge/mgmt.sock
    One or more errors occurred. (Got bad response: )
        caused by: SocketError - SocketErrorCode (ConnectionRefused) : Connection refused /var/run/iotedge/mgmt.sock
                   One or more errors occurred. (Got bad response: )
        caused by: docker returned exit status: 1, stderr = SocketError - SocketErrorCode (ConnectionRefused) : Connection refused /var/run/iotedge/mgmt.sock
                   One or more errors occurred. (Got bad response: )
√ aziot-edge package is up-to-date - OK
√ container time is close to host time - OK
‼ DNS server - Warning
    Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub.
    Please see https://aka.ms/iotedge-prod-checklist-dns for best practices.
    You can ignore this warning if you are setting DNS server per module in the Edge deployment.
        caused by: Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub.
                   Please see https://aka.ms/iotedge-prod-checklist-dns for best practices.
                   You can ignore this warning if you are setting DNS server per module in the Edge deployment.
‼ production readiness: logs policy - Warning
    Container engine is not configured to rotate module logs which may cause it run out of disk space.
    Please see https://aka.ms/iotedge-prod-checklist-logs for best practices.
    You can ignore this warning if you are setting log policy per module in the Edge deployment.
        caused by: Container engine is not configured to rotate module logs which may cause it run out of disk space.
                   Please see https://aka.ms/iotedge-prod-checklist-logs for best practices.
                   You can ignore this warning if you are setting log policy per module in the Edge deployment.
× production readiness: Edge Agent's storage directory is persisted on the host filesystem - Error
    Could not check current state of edgeAgent container
        caused by: Could not check current state of edgeAgent container
        caused by: docker returned exit status: 1, stderr = Error: No such object: edgeAgent
× production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error
    Could not check current state of edgeHub container
        caused by: Could not check current state of edgeHub container
        caused by: docker returned exit status: 1, stderr = Error: No such object: edgeHub
√ Agent image is valid and can be pulled from upstream - OK
√ proxy settings are consistent in aziot-edged, aziot-identityd, moby daemon and config.toml - OK

Connectivity checks
-------------------
√ container on the default network can connect to upstream AMQP port - OK
√ container on the default network can connect to upstream HTTPS / WebSockets port - OK
√ container on the default network can connect to upstream MQTT port - OK
    skipping because of not required in this configuration
× container on the IoT Edge module network can connect to upstream AMQP port - Error
    Container on the azure-iot-edge network could not connect to my-iothub.azure-devices.net:5671
        caused by: Container on the azure-iot-edge network could not connect to my-iothub.azure-devices.net:5671
        caused by: docker returned exit status: 125, stderr = docker: Error response from daemon: network azure-iot-edge not found.
× container on the IoT Edge module network can connect to upstream HTTPS / WebSockets port - Error
    Container on the azure-iot-edge network could not connect to my-iothub.azure-devices.net:443
        caused by: Container on the azure-iot-edge network could not connect to my-iothub.azure-devices.net:443
        caused by: docker returned exit status: 125, stderr = docker: Error response from daemon: network azure-iot-edge not found.
√ container on the IoT Edge module network can connect to upstream MQTT port - OK
    skipping because of not required in this configuration
27 check(s) succeeded.
2 check(s) raised warnings.
6 check(s) raised errors.
2 check(s) were skipped due to errors from other checks.

root@edgedevice1:/# journalctl -u aziot-edged.service -f
Jun 27 16:47:05 edgedevice1 systemd[1]: Started Azure IoT Edge daemon.
Jun 27 16:47:05 edgedevice1 aziot-edged[1825]: 2024-06-27T16:47:05Z [INFO] - Starting Azure IoT Edge Daemon
Jun 27 16:47:05 edgedevice1 aziot-edged[1825]: 2024-06-27T16:47:05Z [INFO] - Version - 1.5.0
Jun 27 16:47:05 edgedevice1 aziot-edged[1825]: 2024-06-27T16:47:05Z [INFO] - Obtaining Edge device provisioning data...
Jun 27 16:47:05 edgedevice1 aziot-edged[1825]: 2024-06-27T16:47:05Z [INFO] - Device is myDevice on my-iothub.azure-devices.net
Jun 27 16:47:05 edgedevice1 aziot-edged[1825]: 2024-06-27T16:47:05Z [INFO] - Initializing module runtime...
Jun 27 16:47:05 edgedevice1 aziot-edged[1825]: 2024-06-27T16:47:05Z [INFO] - Using runtime network id azure-iot-edge
Jun 27 16:47:05 edgedevice1 aziot-edged[1825]: 2024-06-27T16:47:05Z [WARN] - container runtime error
Jun 27 16:47:05 edgedevice1 aziot-edged[1825]: Caused by:
Jun 27 16:47:05 edgedevice1 aziot-edged[1825]:     0: error trying to connect: Permission denied (os error 13)
Jun 27 16:47:05 edgedevice1 aziot-edged[1825]:     1: Permission denied (os error 13)
Jun 27 16:47:05 edgedevice1 aziot-edged[1825]: 2024-06-27T16:47:05Z [ERR!] - Failed to initialize module runtime: runtime operation error: initialize module runtime
Jun 27 16:47:05 edgedevice1 systemd[1]: aziot-edged.service: Main process exited, code=exited, status=1/FAILURE
Jun 27 16:47:05 edgedevice1 systemd[1]: aziot-edged.service: Failed with result 'exit-code'.
^C

I'm lost as well.   I believe this is a security issue, something like AppArmor maybe.   I really don't know what I am doing with that kind of stuff.  With docker I have learned that you can't always trust error messages to mean what they say.
In any case, your DinD is cool because even if it works in this nested fashion , it proves that version can run on that system.


F6 block grid and sass promblems

hello, i need help with new grid system:
i need to use custom classes in foundation 6.
Example:
.gl{@include grid-row(3); border: 1px solid green;}
.wp{@include grid-column; border: 1px solid orange;}
it looks like: http://awesomescreenshot.com/0225fm6u1e
at the bottom i show a example from docs. so where is the problem?

The column needs to be nested inside to define
.gl {
@include grid-row(3) {
.wp {
@include grid-column(1);
}
}
}
I'll close this as it should solve your issue, but feel free to reopne if it hasn't


Security keep stopping error

Can't open security App. Pop up error ( security keep stopping )

Bug Report
https://t.me/androidryukimodsdiscussions/2618
If you don't do above, it will be closed immediately


Package description for package commands_test

Description
Package description for package commands_test.
Fixes #230
Type of change

Documentation update

Testing steps
N/A

Codecov Report

Merging #231 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #231   +/-   ##
=======================================
  Coverage   70.95%   70.95%
=======================================
  Files          12       12
  Lines         730      730
=======================================
  Hits          518      518
  Misses        208      208
  Partials        4        4

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 953e496...bd3a34b. Read the comment docs.


Improve the listing of past events

Description
The past events page does not sort them, making it difficult to locate a precise item (e.g. the last event to access the corresponding collaborative agenda on HackMD).
These changes sort the past events in reverse choronological order.
Issues Resolved
n/a
By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

Thanks for the PR @smortex!


Switch to Winget from Chocolatey

See comments here
https://github.com/meltano/meltano/pull/5967/files#diff-7622618641d3839332b1af8f4f83486662c86a56ea59e441f758aa2969a32b48R10
For Windows we are currently using Chocolatey for Package Management. Windows now has Winget. With the switch to gitlab this may be easier to switch to? Unclear as we haven't looked into it

Still relevant

We no longer use Chocolatey.


[Bug]: Several times add number "favorited"

Relevant scope
Frontend specs
Description
Steps to reproduce:

For example, move to Gerome's blog (https://demo.realworld.io/#/@Gerome)

Click a few times (for example, 5 times) on the button "favorited".

Wait.

Actual result: The number "favorited" has increased by 5 on the page and the browser sends 5 requests.
Expected result: The number "favorited" has increased by 1 on the page and the browser sends 1 requests.
Before steps to reproduce:

After steps to reproduce:

When I reload this page, the number "favorited" increases by only 1 (on the picture).

I think it happens because the button "favorite" isn't disabled after it has been clicked (shown on the picture).

Hi @AlinkLiy,
Thanks for reporting this issue.
I'll work on z fix later on this week.
Can you tell me which frontend implementation was used for the screenshot? The api url is now api.realworld.io and it's still about the conduit.productionready.io one.

@AlinkLiy,
I can't reproduce this bug with the API and several frontend implementations.
It's more likely due to the implementation you used:
this implementation increments a counter on each click rather than on the real favorite counter.
Can you provide a link to this implementation?

Closing the issue as no info has been provided yet.
Feel free to add a comment later on.


[SPARK-10197] [SQL] Add null check in wrapperFor (inside HiveInspectors).

https://issues.apache.org/jira/browse/SPARK-10197

Merged build triggered.

Merged build started.

Test build #41498 has started for   PR 8407 at commit beeb01f.

Test build #41498 has finished for   PR 8407 at commit beeb01f.

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

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

Merged build finished. Test PASSed.

LGTM, merging to master and branch-1.5.


Move TaskResourceBinding to taskrun_types.go

Changes
Relocate TaskResourceBinding to taskrun_types.go a la #940

Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[ ] Commit messages follow commit message best practices

See the contribution guide
for more details.
Release Notes

release-note

/ok-to-test

/approve


Remove java and go dependencies in WORKSPACE file

In order to build the operations proto library (provided by the com_google_googleapis repository) and generate a corresponding C++ library (currently provided by gax) the WORKSPACE file needs to load and set up the java and go repositories from com_google_googleapis. This is a hack and adds unnecessary dependencies.
Tracking bug to remove the hack.

This repository is obsolete. Closing.


Doesn't plat my wav file

Hey @tdiamane by any chance did this wav file had a .wave extension instead of the mode usual a .wav? Then I fixed an issue with playing them. Otherwise could you perhaps share this file with me? (with<EMAIL_ADDRESS>and I'll have a look.

Also FYI: it's a bit tricky to play wav files because browsers and Flash do not have full support for playing every type of Wav file. Unfortunately depending on sampling size and bit rate some wav file might play and some don't.

None of my .wav files work either, regardless of name, size, extension name, or any metadata. I am using Chrome version 43.

Duplicate of #33


feat(@ciscospark/plugin-people): add support for people.get('me')

fixes #676

@ianwremmel ready for round 2


Milestone: Report on OpenSSF Best Practices Badge program for JavaScript published

### Tasks
- [ ] #73
- [ ] #74
- [ ] Placeholder for PR to publish the report

Replaced by a new issue for 2024: #151


improvesupport push down min/max on unique table

Proposed changes
add session variable enable_pushdown_minmax_on_unique = false,
which could control whether push down min/max to unique table.
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

could we support agg table

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall


Added cmake to packages that need to be installed

Like it says on the tin.

@revprez added you as a collaborator on the repo!


import grouping/formating doesn't work like isort

I want to use ruff as my primary format tool. Even though it fixes some other issues like, unused imports, single quotes and etc. it seems it has no effect on grouping imports.
Ruff version: 0.1.5
Tool: Mac-terminal
There are no settings for isort or ruff
Python file:
from local_file import local_module
import os
print(os)
print(local_module)

Command(tried both):
ruff format <path_to_file>
ruff --fix <path_to_file>

Result:
No change
Isort command:
isort <path_to_file>

Expected and isort result:
import os

from local_file import local_module

print(os)
print(local_module)

Import sorting isn't part of the default rule set, so it's not enabled by default. You can turn it on by enabling the I rules -- so, e.g., if you use a ruff.toml in your project:
[lint]
extend-select = ["I"]

With that, ruff check --fix should group and sort imports.

Thank you for your quick response. It works now.


Spotify

As I am not a Spotify subscriber please let me know how you would like to use Spotify service in Node-RED.
You can add your feedback as a comment to this issue. That will help me to prioritize the tasks.

Hi, we are using Spotify for 90% of the music that is being played.
It would be great if we could:

Insert Spotify playlists
Insert playlists, artists, tracks, albums by their Spotify URI e.g.:
-- spotify:track:4LI1ykYGFCcXPWkrpcU7hn
-- spotify:playlist:5NBncFjcwcgrZZg4odPckW

This functionality is also available in the Sonos HTTP api by jishi (https://github.com/jishi/node-sonos-http-api)
Spotify search might be a cool feature as well but less useful for us.

I am working on it but have to do some code consolidation. On 2019-12-01 the packate 1.0.0 will be available and allow insertion of playlists, albums, tracks from My Sonos and most likely also "direct" by uri.

Thanks a lot. Looking forward to it.

I added the Spotify functionality and published it today. Let me know whether it works on your system. Hint: I changed some property name to have everywhere the camel case notation for properties.

Thank a lot! I will try to test it this week and provide you with feedback.

Hi, finally managed to setup the spotify functionality. It seems to work like a charm.
I used a USB Barcode reader connected to a raspberry pi to convert barcodes to songs, albums or playlists on Spotify. This way my kids can turn on some music based on the album cover without needing a phone.
You nodes greatly simplified things for me, so many thanks. We will be using them every day.

Hi thanks for the feedback - good to hear that it works for your.
Self-service for kids - great projects!
I close this issue now.


Remove URL shortener, use direct link

My web filter blocks most URL shorteners like bit.ly or cutt.ly, and many others -- I'm sure there are other people with the same limitation as well.
This change replaces the URL shortened link with the link it points to, which won't change unless you change your username or rename the repository.
I also updated the documentation to point out that it works with the GoPro 10 as well (since it only specified 8 or 9).

@jschmid1 This is a very minor change, any chance you could approve?

my only justification for the url-shortener is for metrics collection

Fair enough, I reverted to using the original link and then below that included the real link below that.
--
I also added a section about what video format the GoPro streams in when used in the webcam mode. The GoPro is capable of recording in so many formats (4K, 5.3K, etc), and I think a lot of people are assuming they'll be to use those video modes with this utility. This way they'll be able to right away see that only 1080p/30 is supported.
@jschmid1


Support for filtering between dates while getting posts/all

I have added support for fromdt and todt parameters in posts/all API call. Very useful to sync data with other systems.

Thanks @pachisaez. Could you please add tests for your patch?


[Bug] In the same ConsumerGroup, the Consumer instances have different Topics subscribed to do not work on the 5.2.0 SDK

Before Creating the Bug Report

[X] I found a bug, not just asking a question, which should be created in GitHub Discussions.

[X] I have searched the GitHub Issues and GitHub Discussions  of this repository and believe that this is not a duplicate.

[X] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment
OS：openEuler22.03(LTS-SP3)
RocketMQ version
version：rocketmq-all-5.3.1
JDK Version
Run：openjdk 1.8.0_432
Describe the Bug
In the same ConsumerGroup, the Consumer instances have different Topics subscribed to do not work on the 5.2.0 SDK.
Steps to Reproduce
I started two consumer instances with the same consumer group configuration, subscribing to different topics separately. However, the subscription relationship was inconsistent, resulting in chaotic and lost consumer messages. As described in the official documentation, the 5. x version SDK does not support consumer instances under the same consumer group subscribing to different topics.
What Did You Expect to See?
The 5.x version of the SDK supports Consumer instances in the same ConsumerGroup subscribing to different topics.
What Did You See Instead?

Additional Context
I developed in the springboot environment, version 2.7.18，and the version of rocketmq-spring-boot-starter is 2.3.0.

consumers in the same group need to subscribe the same topics and tags or sql

The official documentation states that version 5. x of the SDK now supports subscribing to different topics for Consumer instances under the same ConsumerGroup.

you can try grpc clients，maybe work5.x clients


Not working

When I click on the three dots on my profile or next to a movie I don't get any extra options that weren't there before even though it is running and the gear icon doesn't appear in the tampermonkey menu either. What should I do?

Make sure you installed by checking the dashboard. If yes what browser are you using, Then what URL are you on?

I just tried reinstalling it but no luck. I'm using google chrome. First pic is what I see when I click on any movie, second pic is letterboxd homepage

Enabling developer mode didn't do anything yesterday but it worked today! Thank you :)