Too many false positive "Preflight Fail: HIGH IMU ACCEL BIAS" warning messages

Problem:
We are getting a lot of false positive "Preflight Fail: HIGH IMU ACCEL BIAS" warning messages preventing arming.  This seems to have started in master this past spring and continues in stable 1.8.0.  I believe a lot of other PX4 users are getting these false positive warnings as well.

(Note: in recent master the text of this warning as changed to "Preflight Fail: High Accelerometer Bias")

This happens to us frequently on known good aircraft that are great fliers and continue to fly great once the fault is cleared.
We recently noticed the error seems correlated to a vehicle sitting level on the ground for some period of time.  @priseborough made a helpful suggestion to try pitching and rolling the vehicle slowly so that the X and Y accels could spend some time facing down (gravity) and EKF2 could better estimate their bias.  This worked to clear the error!  Here is an example of the error which was then easily cleared by pitching and rolling the vehicle:
https://review.px4.io/plot_app?log=278fa376-2a02-4027-b465-12507dbc9062
Possible solution:
It has been suggested that using the bias state uncertainty as a factor in the bias level check could help eliminate false positives.  The bias level check in Commander could use the already existing additional information from EKF2 for this.
Further support:
Anecdotally I know of this exact ACCEL BIAS warning happening to handfuls of other PX4 users, many of whom do not post to Github or Discuss.
There are a large number of github issues and PX4Discuss posts about getting this error.  Probably there are many complicating factors involved with each report, but the fact that there are so many makes me believe there is a systemic issue with the check, or the checks and warnings need to be more specific.
https://github.com/PX4/Firmware/issues/9241
https://github.com/PX4/Firmware/issues/9474
http://discuss.px4.io/t/preflight-fail/7023/10
http://discuss.px4.io/t/ekf2-problem-z-velocity-estimate-weird-behaviour/8395
http://discuss.px4.io/t/auto-land-ekf2-test-ratios-flight-controller-reset/8264

I spoke with the pilot of this log and he said this motion is typical ground handling of this hand launched, fixed wing, foam aircraft. It was windy that day and the vehicle was getting buffeted around in his hands while he walked out to the takeoff and landing location. The vehicle was powered on and booted up while the pilot was walking with it. This type of ground handling is no atypical for hand launched vehicles.
We will try to see if we can make a repeatable method to get the accel bias error.  So far it seems random, but more testing is worth while.

Is it a motion sequence that you have found is able to trigger this fault?

we've tried a bunch of times to see if this motion sequence on boot-up was able to reproduce this.  We also tried temperature changes after boot (move vehicle from warm inside to cold outside).  We have been unable to reproduce it reliably.
However, it still happens seemingly randomly.

I'm having the same problem on Pixhawk 2.1, PX4 V1.8.1.  I'll try the manual pitching/rolling workaround next time.
But is there any update on a more permanent fix?  Do we know at which release it started?  I might consider using an older release.
Thanks

Reverting is unnecessary. As a short term fix until the check is improved to eliminate false positives, increasing the value of COM_ARM_EKF_AB will make it go away.

@priseborough is there any additional testing you can recommend that will help with implementing the improved check?  It has proven difficult to reproduce reliably.

https://review.px4.io/plot_app?log=f176556e-9a43-40c4-bbc7-e0e65895ec7d
https://review.px4.io/plot_app?log=9e0f5243-7cce-4db6-827a-f720abda7d64
Here are two logs with accel bias errors prior to flight. For both of these logs I restarted the vehicle in order to clear the errors.
Prior to these errors the vehicle did go through substantial temperature changes. The outside temperature was around 18F. For the first error the vehicle was sitting inside before being put outside and immediately powered. The second Occurred after the vehicle was sitting outside for about 15 minutes and then powered up.

Not sure if this is related, but I was having a bunch if ACCEL inconsistency issues with PIxhawk 2.1 cubes. I added some debug messages into my firmware and discovered that one of the accels had a lot of change in bias over temperature. We started seeing these errors when the weather turned cold.
I was above to show very large biases on one of the accels up to 1m/s by chilling the aircraft in a thermal chamber to -20C.
I ended up doing the recommended temperature calibration over -30C to 65C in a thermal chamber, and my issues went away. Reference here: https://docs.px4.io/en/advanced_config/sensor_thermal_calibration.html
My issue was specifically the inconsistency among the 3 accels on the cube, but if your accel bias was varying as much as mine with temperature, it could have triggered this error as the system warmed up.

I have the same problem with the "Preflight Fail: HIGH IMU ACCEL BIAS". But after the restart of the drone, the same error appears. I have to recalibrate the ACC with QGroundcontrol to get the drone fly again. Then the drone flies about 2 times and afterwards the error appears again. I have multiple drones with the same HW and SW configuration. One of the drones does not show the error during all flights. But the others always show the "Preflight Fail: HIGH IMU ACCEL BIAS" error.
I'm using the EKF2 with Vision for indoor navigation. Is there a way to check if the "Preflight Fail: HIGH IMU ACCEL BIAS" error appears due to the bug?

I have the same problem (intermittently) when flying indoor with motion capture. I have partially coped by setting the COM_ARM_EKF_AB parameter higher (around 3.5e-3), but that's not a solution.

@priseborough Could you have a very brief and quick look at more of these instances and see if we're too specific on the warning or if we need better detection?

I confirmed this issue with people trying to fly indoors as well.

Closed via https://github.com/PX4/Firmware/pull/11350

@AlexWUrobot Please open a new issue, this was another problem that was 5 years old.


[FEATURE] support non english default prompt injection in DefaultContentInjector

Is your feature request related to a problem? Please describe.

https://github.com/langchain4j/langchain4j/blob/main/langchain4j-core/src/main/java/dev/langchain4j/rag/content/injector/DefaultContentInjector.java is using English in "Answer using the following information"
My RAG is French based, my users too : they query using French language.
Using ollama llama3, the default prompt becomes a concatenation of French and English, because of the "Answer using (...)"
The model response does not always understand that : often, it'll try to translate the generated answer to English

Describe the solution you'd like

the injector may honor the HTTP Accept header from any HTTP client (being quarkus or spring or anything else), select the preferred language and set a i18n default answer injection.

Describe alternatives you've considered

I can alter the prompt and add "never translate your answer in English, keep the original question language", but I believe it could be better to honor the Accept header, and fallback to English if no such header exists.
Additional context
I understand introducing Accept header support may be a breaking change since existing clients may send a non English Accept header.

How are i18n prompts generally handheld : are models expected to assume everything is English based ?
thanks

Hi, you can override the default prompt in the DefaultContentInjector:
        PromptTemplate promptTemplate = PromptTemplate.from(
                "{{userMessage}}\n" +
                        "\n" +
                        "Répondez en utilisant les informations suivantes:\n" +
                        "{{contents}}"
        );

        DefaultRetrievalAugmentor.builder()
                .contentRetriever(...)
                .contentInjector(new DefaultContentInjector(promptTemplate))
                .build();

I am not sure I understand the proposed solution, could you please elaborate?

I did not notice I could override ;)
By proposal I meant honoring Accept-Language from https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Language
Example : Accept-Language: es-ES would be a hint for a pre built Spanish (Castillan) prompt instead of English default.
However this is assuming a pre existing web context where such header may be present.


fix(emojis): Update Emoji Handling Logic

Fetching SVG emojis instead of 72x72px pngs and converting them to pngs of 512x512px using sharp which is more performant.
talking of time taken
current approach takes about 800-1000ms.
where as with svg fetching and conversion, its reduced to about 350-400ms

Will look into it, thanks for the pull request


[v6] Fixed the pristine/dirty state of fields that get reinitialized to an empty value.

Here's a simple fix. I noticed that if a field has a non-empty initial value, then I clear the field and reinitialize the form with an empty string, the field should become pristine, but does not (as of 6.0.0-rc.4). This happens because the code treats an empty string as no value at all and falls back to the original initial value. This pull request fixes the problem by expecting 'undefined' to be the only value that indicates the initial value is missing. Test included.

Very interesting bug. It took me a while to recreate it and verify, but you explained it perfectly.
Great PR! 👍


Using safe multisig cannot sign the eip712 messages to complete or reject grants

I can send the 50% transaction but then when it captures the tx hash and I try to sign the message to complete the grant, I get an "Error completing" or "Error rejecting" if it was the action I was doing.
This is the console errors I had when trying to complete:
Uncaught (in promise) SwitchChainError
    at W.switchChain (560-6c90a744a9b2c549.js:1026:7826)
    at async W.getProvider (560-6c90a744a9b2c549.js:1026:6585)
    at async Promise.all (index 0)
    at async W.getWalletClient (560-6c90a744a9b2c549.js:1026:6675)
    at async ta (8474-80fe7fbb67464fff.js:20:11396)
    at async n (8474-80fe7fbb67464fff.js:20:11744)Caused by: TypeError: Cannot set properties of undefined (setting 'defaultChain')
    at nm.onChainChanged (4817.433a57a23d6241f0.js:33:29553)
    at i.<anonymous> (4817.433a57a23d6241f0.js:33:28293)
    at i.emit (9097-1a60dea03350292a.js:1:82503)
    at nr.setDefaultChain (4817.433a57a23d6241f0.js:33:10503)
    at nr.handleSwitchChain (4817.433a57a23d6241f0.js:33:11777)
    at nr.request (4817.433a57a23d6241f0.js:33:10113)
    at nm.request (4817.433a57a23d6241f0.js:33:22760)
    at nj.request (4817.433a57a23d6241f0.js:33:31782)
    at W.switchChain (560-6c90a744a9b2c549.js:1026:7639)
    at async W.getProvider (560-6c90a744a9b2c549.js:1026:6585)
4938-addd67e57688a2ff.js:1 Object TypeError: Cannot set properties of undefined (setting 'defaultChain')
    at nm.onChainChanged (4817.433a57a23d6241f0.js:33:29553)
    at i.<anonymous> (4817.433a57a23d6241f0.js:33:28293)
    at i.emit (9097-1a60dea03350292a.js:1:82503)
    at nr.setDefaultChain (4817.433a57a23d6241f0.js:33:10503)
    at nm.onChainChanged (4817.433a57a23d6241f0.js:33:29460)
    at i.<anonymous> (4817.433a57a23d6241f0.js:33:27726)
    at i.emit (9097-1a60dea03350292a.js:1:82503)
    at iq.onSessionEventRequest (4817.433a57a23d6241f0.js:7:99774)
    at iq.processRequest (4817.433a57a23d6241f0.js:7:93280)
    at iq.processRequestsQueue (4817.433a57a23d6241f0.js:7:92614)
window.console.error @ 4938-addd67e57688a2ff.js:1
api/grants/7ABG3zfmbBiVJYsv37UG/review:1

       Failed to load resource: the server responded with a status of 401 ()
api/grants/rvVEKZkm7kj9cL5zg6lC/review:1

       Failed to load resource: the server responded with a status of 401 ()

Completed at #135


Installation and TypeError after upgrading to Node 4.0.0

I just got a new work machine (Windows 7) and installed Node 4 (and npm 2.14.2). While trying to install Karma (both globally and locally), I get a bunch of node-gyp errors that are no longer solved by passing the "--msvs-version=2013" flag and having Python in my path.  However, more pressing is that when running my tests through Gulp on my main project, I'm getting the following error:
ERROR [karma]: [TypeError: options must be a string or an object]
TypeError: options must be a string or an object
at new WriteStream (fs.js:1793:11)
at Object.fs.createWriteStream (fs.js:1779:10)
at C:\[edited]\devtools\node_modules\karma-html-reporter\index.js:89:22
at C:\[edited]\devtools\node_modules\karma\lib\helper.js:80:7
at FSReqWrap.oncomplete (fs.js:82:15)

(node) Buffer.write(string, encoding, offset, length) is deprecated. Use write(string[, offset[, length]][,
encoding]) instead.

What do I need to do?
Update: I rolled back to Node 0.12.7 and I get a soft warning about the deprecation but everything works as normal. So, it must be an issue with the Node 4 interface.

Relates to #1577 and is due to a breakage in a third-party dependency of karma.

Adding to the list: nodejs/node#2798.

@pmq20 that would be stupid, because karma is working.

This is not an issue in karma, but an issue in karma-html-reporter see https://github.com/dtabuenc/karma-html-reporter/pull/27

Should be fixed now


[QUESTION] How does flux handle hardware resoureces competition?

Your question
Ask a clear and concise question about Flux.
I'm puzzled by how flux handles the problem of computation and communication competing for hardware resources when they overlap.
Because in my own project, when I start a gemm kernel and a nccl kernel at the same time, the nccl kernel is likely to be delayed until the gemm is completed because there are not enough SM resources.
What I've observed from flux's code is that in src/all_gather/ths_op/all_gather_gemm_kernel_crossnode.cc, cutlass_op->run and copy_all2all functions will execute separately (my understanding is that the scheduling of these two is entirely determined by the GPU).
In another similar work, nanoflow, the number of SMs available is set for different kernels to avoid the interference.
I would like to know how Flux handles this and thank you for your generous help.

@chenhongyu2048
For flux related:

What I've observed from flux's code is that in src/all_gather/ths_op/all_gather_gemm_kernel_crossnode.cc, cutlass_op->run and copy_all2all functions will execute separately (my understanding is that the scheduling of these two is entirely determined by the GPU).
copy all2all utilize cuda API which use copy engine underline, does not compete with the compute resource with the gemm kernel. For nccl kernel, yes it would use SMs but could be very limited, you need to carefully assign your compute resources, otherwise they could compete and result in deadlock.

Besides, you can play with CUDA_DEVICE_MAX_CONNECTIONS which somehow help you decide the kernel launch/execution order in a certain way.

@wenlei-bao Hello, thanks for your advice first. CUDA_DEVICE_MAX_CONNECTIONS=1 did help me a lot.
And I still have a question, which is also about resources competition.
I'm curious if FLUX has ever faced memory bandwidth contention in the implementation? When ncclsend/recv overlaps with GEMM, they compete for memory bandwidth (although use different SMs and streams), which has a negligible impact on GEMM, but causes NCCL operations to slow down significantly.
There doesn't seem to be any mention of this in the FLUX paper, as the decomposed time reported in the experiment is the exposed communication time, so we can't know the effect of overlapping on communication.

@chenhongyu2048 The overlapping metric we proposed in the paper should demonstrate the overlapping effect.
You probably want to calculate the bandwidth based on latency. And it is also related to your HW interconnect.


adding tests for checkout_repo with mocking framework mockery

The changes for this PR are integrated into PR #83.

The changes for this PR are integrated into PR #83.


Is there a way no to preserve file attributes?

Hi, thanks for creating this tool!
I use it for database archiving, i.e. I generate SQL of a database and then archive it. In case there were no changes in the DB, the content of those files is the same (md5 hash is the same), but the creation, modification, and access time stamps are different. When I use archiver to create an archive, the archive checksum is different of course because of those extended attributes of files that are within it.
Is there a way to disable preserving those attributes while creating archives? Obviously, all 3 would be set to the moment of extraction of such archive.

I am really interested in this as well and am happy to submit a pull request if this is a feature you are interested in? Either separate options to let them control the file header info more: mode, uid, gid, uname, etc or something like "Deterministic" that just takes care of everything that needs to be omitted for you. Something similar to gzip --no-name.

I've been a bit overwhelmed lately... Would anyone like to take up maintenance of this project?

Is this wanted for the command line tool or the core library?
Because the core library has been completely rewritten in #302 and probably allows you to do what you want. The new CLI could certainly honor that.

Ok, I made a pull request that should do what you need, but only you can really determine if it works for your use case. @carolynvs @vdice @ivanduka Can you please give the branch in #280 a try?

Done in #280 - thanks


brightness control(xorg) , Auto login DM, Bootable pendrive maker script, auto power profiling using auto-cpufreq, timeshift backup, samba-ssh server setup

Pull Request
Changes Made

brightness control added into Monitor control util
auto-login feature for display managers added. Fixes #182
added {Create Bootable Pendrive} (using dd command by selecting iso) into utils
the pendrive maker downloads iso from https://archive.archlinux.org/iso/ for arch and official debian website through  curl
sorted the older iso to not show up too old iso's which have different naming convention for the iso file. starts from (2017.04.01)
auto power profiling using auto-cpufreq for desktops and laptops (Feature Request from youtube comments).
Timeshift backup util added.
samba-ssh server setup script (Feature Request from youtube comments).

to be noted
cargo.lock gets modified in my development machine everytime i run cargo run ,tried removing it while i commit it but yet somehow it also gets commited into the fork. :( while accepting pr, if possible ignore that file :)

@guruswarupa Too many bashisms in this PR.

This needs to be using $ESCALATION_TOOL @guruswarupa

@guruswarupa I'd recommend marking this as a draft.

All of these scripts need to be tested in bash & dash. @guruswarupa

@ChrisTitusTech I recommend not merging this, WAY too many issues that need to be addressed.

@guruswarupa Too many bashisms in this PR.

well yes, i'm just waiting for your pr to get approved. later we can make it posix compliant. as of now, i've made a working code for atleast all bash systems. converting it to posix can be done later too. I'll try fixing all those issues right now. but converting it to posix compliant, i've little to no knowledge as of now. i'll try replicating what you did in the pr. thanks

@guruswarupa Can you squash some of those redundant commits please?

@guruswarupa Too many bashisms in this PR.

well yes, i'm just waiting for your pr to get approved. later we can make it posix compliant. as of now, i've made a working code for atleast all bash systems. converting it to posix can be done later too. I'll try fixing all those issues right now. but converting it to posix compliant, i've little to no knowledge as of now. i'll try replicating what you did in the pr. thanks

I'm not sure Chris will accept this without full posix-compliance, everything here needs to be re-written. Take a look at my reviews, they will help you get started.

@guruswarupa Too many bashisms in this PR.

well yes, i'm just waiting for your pr to get approved. later we can make it posix compliant. as of now, i've made a working code for atleast all bash systems. converting it to posix can be done later too. I'll try fixing all those issues right now. but converting it to posix compliant, i've little to no knowledge as of now. i'll try replicating what you did in the pr. thanks

I'm not sure Chris will accept this without full posix-compliance, everything here needs to be re-written. Take a look at my reviews, they will help you get started.

if i try making it to posix compliant and move the stuff to common-scripts, ill have to rewrite changes you've made in this pr https://github.com/ChrisTitusTech/linutil/pull/282 as its still not pushed to the main. is that fine?

@guruswarupa Too many bashisms in this PR.

well yes, i'm just waiting for your pr to get approved. later we can make it posix compliant. as of now, i've made a working code for atleast all bash systems. converting it to posix can be done later too. I'll try fixing all those issues right now. but converting it to posix compliant, i've little to no knowledge as of now. i'll try replicating what you did in the pr. thanks

I'm not sure Chris will accept this without full posix-compliance, everything here needs to be re-written. Take a look at my reviews, they will help you get started.

if i try making it to posix compliant and move the stuff to common-scripts, ill have to rewrite changes you've made in this pr #282 as its still not pushed to the main. is that fine?

Nothing needs to be moved to the common-script, and no don't rewrite anything that will conflict with #282

@guruswarupa Too many bashisms in this PR.

well yes, i'm just waiting for your pr to get approved. later we can make it posix compliant. as of now, i've made a working code for atleast all bash systems. converting it to posix can be done later too. I'll try fixing all those issues right now. but converting it to posix compliant, i've little to no knowledge as of now. i'll try replicating what you did in the pr. thanks

I'm not sure Chris will accept this without full posix-compliance, everything here needs to be re-written. Take a look at my reviews, they will help you get started.

if i try making it to posix compliant and move the stuff to common-scripts, ill have to rewrite changes you've made in this pr #282 as its still not pushed to the main. is that fine?

Nothing needs to be moved to the common-script, and no don't rewrite anything that will conflict with #282

few color codes are missing in common-scripts which i've used.

@guruswarupa Too many bashisms in this PR.

well yes, i'm just waiting for your pr to get approved. later we can make it posix compliant. as of now, i've made a working code for atleast all bash systems. converting it to posix can be done later too. I'll try fixing all those issues right now. but converting it to posix compliant, i've little to no knowledge as of now. i'll try replicating what you did in the pr. thanks

I'm not sure Chris will accept this without full posix-compliance, everything here needs to be re-written. Take a look at my reviews, they will help you get started.

if i try making it to posix compliant and move the stuff to common-scripts, ill have to rewrite changes you've made in this pr #282 as its still not pushed to the main. is that fine?

Nothing needs to be moved to the common-script, and no don't rewrite anything that will conflict with #282

few color codes are missing in common-scripts which i've used.

You should make a separate PR for that, and change all of the current color codes to the ones in the common-script.

@guruswarupa Too many bashisms in this PR.

well yes, i'm just waiting for your pr to get approved. later we can make it posix compliant. as of now, i've made a working code for atleast all bash systems. converting it to posix can be done later too. I'll try fixing all those issues right now. but converting it to posix compliant, i've little to no knowledge as of now. i'll try replicating what you did in the pr. thanks

I'm not sure Chris will accept this without full posix-compliance, everything here needs to be re-written. Take a look at my reviews, they will help you get started.

if i try making it to posix compliant and move the stuff to common-scripts, ill have to rewrite changes you've made in this pr #282 as its still not pushed to the main. is that fine?

Nothing needs to be moved to the common-script, and no don't rewrite anything that will conflict with #282

few color codes are missing in common-scripts which i've used.

You should make a separate PR for that, and change all of the current color codes to the ones in the common-script.

oh.. so only those color codes which are in common-scripts must be used...

@guruswarupa Too many bashisms in this PR.

well yes, i'm just waiting for your pr to get approved. later we can make it posix compliant. as of now, i've made a working code for atleast all bash systems. converting it to posix can be done later too. I'll try fixing all those issues right now. but converting it to posix compliant, i've little to no knowledge as of now. i'll try replicating what you did in the pr. thanks

I'm not sure Chris will accept this without full posix-compliance, everything here needs to be re-written. Take a look at my reviews, they will help you get started.

if i try making it to posix compliant and move the stuff to common-scripts, ill have to rewrite changes you've made in this pr #282 as its still not pushed to the main. is that fine?

Nothing needs to be moved to the common-script, and no don't rewrite anything that will conflict with #282

few color codes are missing in common-scripts which i've used.

You should make a separate PR for that, and change all of the current color codes to the ones in the common-script.

oh.. so only those color codes which are in common-scripts must be used...

Correct. If you want to add more color-codes in the common-script then make a separate PR for that.

@guruswarupa Too many bashisms in this PR.

well yes, i'm just waiting for your pr to get approved. later we can make it posix compliant. as of now, i've made a working code for atleast all bash systems. converting it to posix can be done later too. I'll try fixing all those issues right now. but converting it to posix compliant, i've little to no knowledge as of now. i'll try replicating what you did in the pr. thanks

I'm not sure Chris will accept this without full posix-compliance, everything here needs to be re-written. Take a look at my reviews, they will help you get started.

if i try making it to posix compliant and move the stuff to common-scripts, ill have to rewrite changes you've made in this pr #282 as its still not pushed to the main. is that fine?

Nothing needs to be moved to the common-script, and no don't rewrite anything that will conflict with #282

few color codes are missing in common-scripts which i've used.

You should make a separate PR for that, and change all of the current color codes to the ones in the common-script.

oh.. so only those color codes which are in common-scripts must be used...

Correct. If you want to add more color-codes in the common-script then make a separate PR for that.
Adding color-codes in each script separate from the common-script is quite redundant.

yes yes i get it. can i get your discord id or something? i need help with squashing. could never squash properly :( , last time i removed old pr and made a new pr with all the changes. this is my first open source contribution :)

@guruswarupa Too many bashisms in this PR.

well yes, i'm just waiting for your pr to get approved. later we can make it posix compliant. as of now, i've made a working code for atleast all bash systems. converting it to posix can be done later too. I'll try fixing all those issues right now. but converting it to posix compliant, i've little to no knowledge as of now. i'll try replicating what you did in the pr. thanks

I'm not sure Chris will accept this without full posix-compliance, everything here needs to be re-written. Take a look at my reviews, they will help you get started.

if i try making it to posix compliant and move the stuff to common-scripts, ill have to rewrite changes you've made in this pr #282 as its still not pushed to the main. is that fine?

Nothing needs to be moved to the common-script, and no don't rewrite anything that will conflict with #282

few color codes are missing in common-scripts which i've used.

You should make a separate PR for that, and change all of the current color codes to the ones in the common-script.

oh.. so only those color codes which are in common-scripts must be used...

Correct. If you want to add more color-codes in the common-script then make a separate PR for that.
Adding color-codes in each script separate from the common-script is quite redundant.

yes yes i get it. can i get your discord id or something? i need help with squashing. could never squash properly :( , last time i removed old pr and made a new pr with all the changes. this is my first open source contribution :)

No, I don't use discord, there should be guides on youtube on how to squash commits.
It's usually just git rebase -i HEAD~2 the number being how many commits you want to rebase, it should take you into your default text editor then you should replace every "pick" with squash and leave the top one as "pick".

@guruswarupa Too many bashisms in this PR.

well yes, i'm just waiting for your pr to get approved. later we can make it posix compliant. as of now, i've made a working code for atleast all bash systems. converting it to posix can be done later too. I'll try fixing all those issues right now. but converting it to posix compliant, i've little to no knowledge as of now. i'll try replicating what you did in the pr. thanks

I'm not sure Chris will accept this without full posix-compliance, everything here needs to be re-written. Take a look at my reviews, they will help you get started.

if i try making it to posix compliant and move the stuff to common-scripts, ill have to rewrite changes you've made in this pr #282 as its still not pushed to the main. is that fine?

Nothing needs to be moved to the common-script, and no don't rewrite anything that will conflict with #282

few color codes are missing in common-scripts which i've used.

You should make a separate PR for that, and change all of the current color codes to the ones in the common-script.

oh.. so only those color codes which are in common-scripts must be used...

Correct. If you want to add more color-codes in the common-script then make a separate PR for that.
Adding color-codes in each script separate from the common-script is quite redundant.

yes yes i get it. can i get your discord id or something? i need help with squashing. could never squash properly :( , last time i removed old pr and made a new pr with all the changes. this is my first open source contribution :)

No, I don't use discord, there should be guides on youtube on how to squash commits.

@guruswarupa I recommend marking this as a draft for now.

@guruswarupa I recommend marking this as a draft for now.

check out now i've changed the code to follow those posix syntax... lemme know if any changes are required :)

@guruswarupa After making these changes these scripts will need indepth testing.

@nnyyxxxx  check the code now :)
and yeah vs code throws error when i try doing squash

@guruswarupa You'll have to fix all of the echo commands, some include backslashes and other printf arguments.

@guruswarupa Fix all of these other issues that I reviewed in the mean-time.

@guruswarupa Fix all of these other issues that I reviewed in the mean-time.

i fixed the pendrive escalation.

@guruswarupa Fix all of these other issues that I reviewed in the mean-time.

i fixed the pendrive escalation.

Alright, thanks. Fix up the rest of the issues in the reviews and this PR should be good now. :)

@guruswarupa Fix all of these other issues that I reviewed in the mean-time.

i fixed the pendrive escalation.

Alright, thanks. Fix up the rest of the issues in the reviews and this PR should be good now. :)

i've done all those just cross check once more and were good to go :)

@guruswarupa After you're done, hide all of your comments with reason "resolved" please & thanks.

Alright @guruswarupa now you'll have to squash all of these commits, here is a video.
https://www.youtube.com/watch?v=V5KrD7CmO4o&t

Looks good, but this needs indepth testing.

yeah. as of what i've used it should work on most of the major distros. and yeah i could force push the rebasing using github desktop. vs code throws errors for some reason. thanks :)

Looks good, but this needs indepth testing.

yeah. as of what i've used, should work on most of the major distros. and yeah i could force push the rebasing using github desktop. vs code throws errors for some reason. thanks :)

You should squash everything into 1 commit, also there are some printf's with arguments at the end of the timeshift script might want to change those to "echo".

Looks good, but this needs indepth testing.

yeah. as of what i've used, should work on most of the major distros. and yeah i could force push the rebasing using github desktop. vs code throws errors for some reason. thanks :)

You should squash everything into 1 commit, also there are some printf's with arguments at the end of the timeshift script might want to change those to "echo".

isn't it better to have different commits for different features added?

Looks good, but this needs indepth testing.

yeah. as of what i've used, should work on most of the major distros. and yeah i could force push the rebasing using github desktop. vs code throws errors for some reason. thanks :)

You should squash everything into 1 commit, also there are some printf's with arguments at the end of the timeshift script might want to change those to "echo".

isn't it better to have different commits for different features added?

It's personal preference, but yeah :).

Looks good, but this needs indepth testing.

yeah. as of what i've used, should work on most of the major distros. and yeah i could force push the rebasing using github desktop. vs code throws errors for some reason. thanks :)

You should squash everything into 1 commit, also there are some printf's with arguments at the end of the timeshift script might want to change those to "echo".

isn't it better to have different commits for different features added?

It's personal preference, but yeah :).

and yeah not able to squash cause i had merged main branch of it to my branch :/ throws conflict errors

Looks good, but this needs indepth testing.

yeah. as of what i've used, should work on most of the major distros. and yeah i could force push the rebasing using github desktop. vs code throws errors for some reason. thanks :)

You should squash everything into 1 commit, also there are some printf's with arguments at the end of the timeshift script might want to change those to "echo".

isn't it better to have different commits for different features added?

It's personal preference, but yeah :).

and yeah not able to squash cause i had merged main branch of it to my branch :/ throws conflict errors

Alright, thanks. It was great converting everything to posix. :)

Looks good, but this needs indepth testing.

yeah. as of what i've used, should work on most of the major distros. and yeah i could force push the rebasing using github desktop. vs code throws errors for some reason. thanks :)

You should squash everything into 1 commit, also there are some printf's with arguments at the end of the timeshift script might want to change those to "echo".

isn't it better to have different commits for different features added?

It's personal preference, but yeah :).

and yeah not able to squash cause i had merged main branch of it to my branch :/ throws conflict errors

Alright, thanks. It was great converting everything to posix. :)

haha yeah, i mean i understood how to make newer scripts for this repo + how to squash and work together :) thank you.

@nnyyxxxx check this script once

@guruswarupa Can you please move that commit to a new PR? Lets keep this one focused, thanks.

Also might be a duplicate of #306

@guruswarupa Can you please move that commit to a new PR? Lets keep this one focused, thanks.

ohh so someone already made it fine.

@guruswarupa Can you please move that commit to a new PR? Lets keep this one focused, thanks.

ohh so someone already made it fine.

You're going to have to reset back to the previous commit.

@guruswarupa I recommend not adding anything new to this, as there is too much stuff being added ATM.

Thanks. @guruswarupa

Thanks. @guruswarupa

lol i worked at the same time he did :) what a coincidence

@nnyyxxxx my docker script seemed better compared to his. do you want me to create another pr?

@nnyyxxxx my docker script seemed better compared to his. do you want me to create another pr?, except it didn't include kvm

@nnyyxxxx my docker script seemed better compared to his. do you want me to create another pr? it didn't include kvm which he can work on ig?

Yeah sure, just make sure you write "closes (pr number)" in the issues section & write why that would be a better implementation of the previous PR.

@guruswarupa Lets hide the rest of these comments please.

@nnyyxxxx my docker script seemed better compared to his. do you want me to create another pr? it didn't include kvm which he can work on ig?

Yeah sure, just make sure you write "closes (pr number)" in the issues section & write why that would be a better implementation of the previous PR.

yeah sure. can you like tell me how to create multiple pr's cause when i try making new branch it contains all these changes in that too...

@guruswarupa You have to change the input to CTT/linutil.

@nnyyxxxx ah thanks man.

Sorry for the inconvenience. We had a massive restructure of the codebase to improve future development. Because of this can you update your PR to the new structure. Thank you for your assistance and contribution.

@nnyyxxxx can i know how i can fix all these conflicts without trying to pull the main by discarding all my changes made in main? :(

@guruswarupa Join the linutil discord server, I'll help you out there.

@guruswarupa Join the linutil discord server, I'll help you out there.

can i get the link please?

@guruswarupa Join the linutil discord server, I'll help you out there.

can i get the link please?

https://discord.gg/EKDhdCFt

@guruswarupa Join the linutil discord server, I'll help you out there.

can i get the link please? @nnyyxxxx

@ChrisTitusTech  @nnyyxxxx i've fixed those conflicts. ready to be merged.

Looks good! @guruswarupa This PR is awesome! Next time split this into multiple PRs like I mentioned in the Linutil discord server.

@nnyyxxxx i've fixed those conflicts. ready to be merged.
yeah sure!

I think the create-bootable-usb script could benefit quite a bit from what I've been doing over in https://github.com/quickemu-project/quickget_configs. jq would need to be added as a dependency for online distros, but several more would be available for download than just arch/debian, no invalid URLs would be available, etc.
I'll propose some changes once I get the workflow back up & running (https://github.com/quickemu-project/quickget_configs/pull/12).

I think the create-bootable-usb script could benefit quite a bit from what I've been doing over in https://github.com/quickemu-project/quickget_configs. jq would need to be added as a dependency for online distros, but several more would be available for download than just arch/debian, no invalid URLs would be available, etc.
I'll propose some changes once I get the workflow back up & running (https://github.com/quickemu-project/quickget_configs/pull/12).

Yes... I just wanted these two main distros to be included. I wanted to add windows too but idk what's the static download link for it which is from official Microsoft. Ig someone from winutil can help us who made the downloading of iso in microwin :) ,and other distros too by people like you...

Can you please split this PR into separate feature PRs. The issue is that if anyone of the feature you have provided is not good the whole PR will be rejected which makes other features also getting rejected

Can you please split this PR into separate feature PRs. The issue is that if anyone of the feature you have provided is not good the whole PR will be rejected which makes other features also getting rejected

Well yeah splitting is better but rn it's too much of work to do. As of what each script does, I don't think he'll reject it. All the scripts work really well and I've tested on few systems. Next time I'll make sure to split each into seperate pr's. As I was new to open source contribution in GitHub, I didn't know how exactly to work with pr's.


Symlink collections into .ovm

OVM should symlink <odin version>/core and <odin version>/shared into $OVM_INSTALL so that the user can point their ols.json at those directories.
Symlinking shared may not be a good idea as it's intended as a place for the user to pull down third-party libs and have them available system-wide. core definitely should be linked. Perhaps symlink core and create an empty dir for shared on install that doesn't get removed when installing/switching versions.

Per Odin docs, shared needs to be a sibling to the compiler. We can symlink .ovm/shared/ into the directory of the active version.
https://odin-lang.org/docs/install/#for-linux-and-other-nix

fixed in 1374664


Move oracle related TLV info to Messaging.md

The TOC of Messaging.md including some parts about oracle messages, but actually they were not there. As we discussed moving all TLV serialization info to Messaging I moved them there and updated the TOC.

Looks good but I think you need to modify the table of contents for both files moving the sections from one to the other

Good point thanks updated.


Syntax error

https://github.com/matt-42/silicon/blob/master/silicon/backends/mhd.hh#L235
Needs another ')'

Thanks for noticing. I'll be more careful next time I accept a PR.

Fixed in df56f30f8db8d3be8305f56e198818e83a14c985


[50138] iOS: Implemented custom back button with larger tap area and placed it in …

…all relevant storyboards

Please add some pictures to exemplify the change

Please add some pictures to exemplify the change

Should be no visual differences, but I can add some screenshots to verify


Habitat.config error in Google Colab

For this tutorial session: https://www.youtube.com/watch?v=KbbfD7RlJLM&list=PLGywud_-HlCORC0c4uj97oppQrGiB6JNy
When I run the code 'Path Setup and Imports', habitat.config error doesn't allow me to move forward. Is this happened because of the incompatibility of TensorFlow version?
ImportError: cannot import name 'Config' from 'habitat.config' (/content/habitat-lab/habitat-lab/habitat/config/init.py)
Can some one let me know how to deal with this??
Error Message:
ImportError                               Traceback (most recent call last)
 in
26 import habitat
27 import habitat_sim
---> 28 from habitat.config import Config
29 from habitat.core.registry import registry
30 from habitat_sim.utils import common as ut
ImportError: cannot import name 'Config' from 'habitat.config' (/content/habitat-lab/habitat-lab/habitat/config/init.py)

NOTE: If your import is failing due to a missing package, you can
manually install dependencies using either !pip or !apt.
To view examples of installing some common dependencies, click the
"Open Examples" button below.

Hi @JaechangKo check out this issue. There is a known problem with Colab. Try the solution proposed there and let me know if there are more issues.

Note we have stopped supporting colab and converted tutorials to local Jupyter notebooks instead.


feat: Tiering data changes for volume - template change

[X] volume template changes
[x] volume dashboard changes
[x] aggregare template changes
[ ] aggregate dashboard changes

Aggregate Fabricpool Drilldown:

Added new panels in Volume Statistics


Support for setting UUID of user during credentials creation

When I create a job using jenkins::job, with a specified UUID in the template, I'd like to be able to set that UUID during credential creation.

For my own understanding.
Do you mean the 'id' line as shown below? I can set this value through Jenkins GUI but not through puppet? and breaks my automated jenkins provisioning.
<java.util.concurrent.CopyOnWriteArrayList>
    <com.cloudbees.plugins.credentials.impl.UsernamePasswordCredentialsImpl>
      <scope>GLOBAL</scope>
      <id>dbd9a6c8-c7c5-428b-946e-9c3e2333ef58</id>
      <description>vagrant user for git</description>
      <username>vagrant</username>
      <password>w5oFlgURdduq2RlLJQBJUTmOEeJvFdC4geAHiW3K0Hk=</password>
    </com.cloudbees.plugins.credentials.impl.UsernamePasswordCredentialsImpl>
  </java.util.concurrent.CopyOnWriteArrayList>

@ltutar - yes indeed  ... it's used in numerous places, for example:
http://docs.openstack.org/infra/jenkins-job-builder/scm.html#scm.git refers to it as 'credentials-id', which allows you to set it for use with JJB
I also use it in the job-dsl when specifying credentials to use when needed


[ROUT-103] - Add hover affordance on tiny item when clustering

Jira
Overview of PR
-> This PR includes adding extra hover affordance around item when clustering. The issue this solves is that when zooming, items or clusters can become small and hard to interact with, we add an extra area for users to interact with tiny items. When an item is classified as a tiny item, by the clustering settings, we add a div behind the item so you can trigger hover or interaction events on the item. The increased hover affordance is equal to 49% of the clustering range so it will scale with zooming.
-> Changelog/Readme updated
-> Test added to check that a buffer item is added when dealing with a tinyItem that has clusteringSettings.enableIncreasedHoverOnTinyItem = true
-> Demo added to show increased hover under demo-clustering-increased-hovering called clusteringHoverAffordance.

Do we want the tiny item to be offset to the right of the hoverable area when expanded?


⚠ Bofrost.be has degraded performance

In b73d620, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2353 ms

Resolved: Bofrost.be performance has improved in 8ac19c5.


[c2][decoder] Fixed test case cencSchemeTypeV18 failed

case:com.google.android.exoplayer.gts.CommonEncryptionDrmTest#cencSchemeTypeV18
Simplify the logic, the combination of timestamp and index determines whether it is a duplicate frame.
Tracked-On: OAM-118988

Program name for this pr is not compatable with other dependent prs, for more details please check tracked_on

Program name for this pr is not compatable with other dependent prs, for more details please check tracked_on

Program name for this pr is not compatable with other dependent prs, for more details please check tracked_on

Program name for this pr is not compatable with other dependent prs, for more details please check tracked_on


Wreckfest pitch/roll reversed

Hi,
With the non experimental version under v1.07, i have pitch and roll reversed. With "Wreckfest experimental" (v1.06), traction loss was  reversed but pitch/roll was OK, now,is it the opposite!
I see several reversed axis issues here, with different games (WRC8, Mechwarriors...). Is it possible to add reverse axis button that we can select by ourselves?

Is this connected to Sim Racing Studio?

Yes

Yeah this could be specifically an issue with sim racing studio.
When you say reversed, do you mean that you roll left in the game and you roll right in the game?
or do you mean you roll left in the game, and you pitch in some direction?

roll left in the game and you roll right in the sim

I'll have to check in the sim, but you can reverse it yourself in srs
from here
https://www.simracingstudio.com/forum/motion-profiles-1/srs-2-0-motion-tuning-guide


Django 4.0+ does not Work With djangocms3.11

Django 4.2 Does not work with Django-cms==3.11.4
it only works with djangocms==4
Trid django-cms 3.11.3+ with Django4.2 it did not work and got me this error
raise NodeNotFoundError(self.error_message, self.key, origin=self.origin)
django.db.migrations.exceptions.NodeNotFoundError: Migration cms.0036_alter_cmsplugin_id_alter_globalpagepermission_id_and_more dependencies reference nonexistent parent node ('cms', '0035_auto_20230822_2208')
however as per https://www.django-cms.org/en/blog/2023/09/17/django-cms-3-11-4/
this release notes it says djangocms 3.11.4 works with django 4.2t

@rdawad Indeed, django CMS 3.11.4 works with Django 4.2. Though, I would suggest you update to django CMS 3.11.6 (the latest version of the 3.11 branch).
The error message you get does not originate from django CMS 3.11.4 (which does not include a migration called 0036_alter_cmsplugin_id_alter_globalpagepermission_id_and_more.
It appears that you had temporarily installed the develop-4 branch of django CMS and then created a migration yourself referencing the latest django CMS migration on the development branch. I would assume, the issue disappears if you delete cms.migrations.0036_alter_cmsplugin_id_alter_globalpagepermission_id_and_more.

@rdawad Any news on this?

Great! Good to know! Thanks for reporting back!


Remove the definition of cosmosdb key from helm chart values

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:
Please delete options that are not relevant.

[ ] I have performed a self-review
[ ] Changelog has been updated
[ ] Documentation has been updated
[ ] Unit tests pass locally (./scripts/test)
[ ] Code is linted and styled (./scripts/format)

The integration tests shouldn't be affected by this change. Merging.


[Bug]: relative_time does not return a localized result

Requirements

[X] I checked the troubleshooting section in the README to verify that I have the latest Mushroom version.
[X] I did a search to see if there is a similar issue or if a pull request is open.
[X] I have read the state of card mod support (in pin issues) and understand card mod support is not provided in this repository.

Current Behavior
if you use a template card, to show specific information e.g. as secondary information
{{ states('sensor.rasen_sensor_soil_humidity')  }} % ⸱ {{ relative_time(states.sensor.rasen_sensor_soil_humidity.last_updated) }} ago
relative_time will always return an english localized result "1 hour" instead of "1 Stunde" (German)
This also applies if you are using other time functions like:
{{ time_since(states.sensor.rasen_sensor_soil_humidity.last_updated, 1) }}
Expected Behavior
It's supposed to show the correctly localized result according to the language set up in Home Assistant.
Steps To Reproduce

Have your language set to German
Set up a template sensor
try to show relative_time value of last_updated of your favorite sensor
example: {{ states('sensor.rasen_sensor_soil_humidity')  }} % ⸱ {{ relative_time(states.sensor.rasen_sensor_soil_humidity.last_updated) }} ago
Check card, it show "x hour" instead of "x Stunden", whereas an mushroom-entity-card will properly show the localized version.

Context
YAML state

Environment
- Browser: 127.0.6533.120
- HA Version: 2024.8.4
- Mushroom: 4.0.5

Anything else?
No response

Mushroom is using regular template function from Home Assistant (https://www.home-assistant.io/docs/configuration/templating/#time). I assume it should be a feature request for Home Assistant, not Mushroom.

But how can that be that every Mushroom card supports it correctly translated as well as every HASS built-in card but not the template card? And how can that be an HASS issue then?

Because all cards are using javascript function to get relative time (translated) and template card is using jinja function to get relative time (not translated)


add support for custom fields when creating sql tables

so that in values_of_this_table you can enter something other than the names of the fields, and anything
before: (id, name, password) you
need: (id PRIMARY KEY int, name text, password text) and whatever your heart desires

resolved with #60


[SPARK-9248][SparkR] Closing curly-braces should always be on their own line

JIRA
[SPARK-9248] Closing curly-braces should always be on their own line - ASF JIRA
The result of dev/lint-r
The result of dev/lint-r for SPARK-9248 at the revistion:6175d6cfe795fbd88e3ee713fac375038a3993a8

Merged build triggered.

Merged build started.

Test build #39048 has started for   PR 7795 at commit c8eccd3.

Test build #39048 has finished for   PR 7795 at commit c8eccd3.

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

Merged build finished. Test PASSed.

Thanks @yu-iskw -- LGTM. Merging this

@shivaram thank you for merging it!


mol convert smiles error

ketcher: 2.4.1
indigo: 1.6.1
i use mol file the rendered structure looks like this:

When I converted to SMILES it became this:
C1C=CC=C([La])C=1
I think this La should be turned into CF3, but I don't know where is the mistake that makes the conversion not what I want, is it ketcher or indigo or my own operation mistake, please help me, thank you very much

mol.zip

I'm not a chemist, sorry, I don't know much about chemistry, is this CF3 a superatom that prevents it from being converted to SMILES normally, I would like to ask if there is any way to make ketcher recognize this superatom and convert it to me The desired SMILES, such as adding a dictionary, CF3 corresponds to a readable SMILES fragment, and then can it be replaced and spliced when mol is converted to SMILES? thank you very much

Hi @niuzhenjiang,
thank you for reaching out.
The *.mol you have provided suggests that CF3 in it is not a superatom - it's a La atom with the alias SF3, not a Functional Group or other superatom. You can check by opening it in Ketcher, selecting the Lasso tool and double clicking on the CF3 on the canvas to check the atom properties.

I've attached the *.mol  Issue_1384_CF3 as FG.zip that represent the CF3 as Functional Group in Ketcher. You can use the following instruction in our Help to help you draw the same structure in Ketcher 2.4. : Functional Groups
Regarding the support of superatoms and aliases in SMILES: they are not supported by the format according to the specification. Information on those structures is lost when the structures are saved to SMILES - this happens in other chemical editors also.
I hope those comments help.
Best regards,
Alena & Ketcher team


Desiree css

Ports in design changes from tidymodels.org
New & improved features:

gains sticky TOC for blog posts

gains copy-to-clipboard for code chunks

gains anchorized header links

gains new shortcodes

gains 2 new layout types

better image accessibility

larger base font sizes for improved accessibility

more parameters for site customization of colors and fonts

Small tweaks

hexes on package pages are now symmetric not squished

improved functioning for highlighting active menu items in the upper navbar (even with Hugo nested sections)

jQuery upgrade

improved RSS feed handling

styled footnotes from goldmark renderer work again

Includes chroma CSS styles for highlighting via downlit for hugodown sites

shiny new demo site courtesy of @dcossyleon

new Hugo theme

The way with works is like:
/* Headers */

{{with .Param "headers.font-family"}}

  h1, h2,
  .article-title,
  div.tagline,
  #TableOfContents a {
    font-family:  {{ . }}; # you have: "{{ .Param "headers.font-family" }}";
  }

{{end}}

🎉


[Feature] Extend openapi client generation

Relevant template
No response
Problem description (optional)
After closing this issue the api will be generated automatically.
But using it in the client still leaves some room for improvement. Futhermore there exists not generator for vue.
Desired solution
Generate some api function with vue functionality (reactivity - see example below).
This example exposes reactive variables to the component which simplifies the implementation a lot in VueJS.
The below code can be used to manually create those function for each api call - this is probably doable for a few request but not if this needs to be done for the whole specification.
Example for some generic vue implementation for calling the api:
export function useApiCall<TRequest, TResponse = void>(
  apiMethod: (params: TRequest) => Promise<TResponse>
) {
  const loadingInternal = ref(false);
  const errorInternal = ref(false);
  const dataInternal = ref<TResponse | null>(null);

  const loading = readonly(loadingInternal);
  const error = readonly(errorInternal);
  const data = readonly(dataInternal);

  const call = (params: TRequest): Promise<TResponse | boolean> => {
    loadingInternal.value = true;
    errorInternal.value = false;

    return apiMethod(params)
      .then((data) => (dataInternal.value = data))
      .catch(() => (errorInternal.value = true))
      .finally(() => (loadingInternal.value = false));
  };

  return {
    loading,
    error,
    data,
    call,
  };
}

Considered alternatives (optional)
Alternative soultion would be to customize the openapi generator. This can be done with the provided .mustache files (example for the DefaultApi).
Now there exist two ways to do this:

use the templating mechanism to inject a custom template upon generating the files
donate a contribution to the openapi-generator project with implementing a generator type for typescript-vue

Additional context (optional)
No response
No duplicate

[X] I confirm that this issue is not a duplicate

Code of Conduct

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

This issue depends on the previous openapi issue https://github.com/it-at-m/refarch-templates/issues/619


Breaking in new flutter SDK

Plugin is breaking in new flutter sdk.

See https://github.com/mogol/opengl_texture_widget_example/issues/1#issuecomment-733480880


correct help message

./main.py add 1 2
shows error message
Error: Invalid value for 'A': 'add' is not a valid integer.
correct usage is
./main.py 1 2

I noticed this as well.  add is not an arg in cli pass


Become More Opinionated

Hi. I saw it's possible to develop a Go app in Emacs, and was wondering if we could opinionate our way out of that? Is it possible to make it so people can only develop for Go in VS Code?

If we need a reason to get rid of Emacs, I do have one. I know for a fact you can make very bad, nasty code with Emacs.

Thank you for raising this issue. Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For asking questions, see:

Stack Overflow with questions tagged "go"

The Go Forum, a web-based forum

Gophers Slack, use the invite app for access. The #general channel is a good starting point.

Go Community on Hashnode with questions and posts tagged with "go"

The golang-nuts mailing list

IRC channel #go-nuts on Freenode


tests: DescriptorPoolInUseDestroyedSignaled Viewport

Change-Id: I4f3ba93ff4e117fe9c22165d5983db5860c52846

I'm nitpicking here, but can I get you to change your commit message to use the imperative mood?

Not without exceeding the 50 character limit.
On Tue, Jan 17, 2017 at 9:49 AM, Jeremy Hayes<EMAIL_ADDRESS>wrote:

I'm nitpicking here, but can I get you to change your commit message to
use the imperative mood?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers/pull/1379#issuecomment-273226544,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASZgKQXlZ1Axf1XI6yJKNS51C6X8RHyjks5rTPE0gaJpZM4Lk-gj
.

Can you please make the commit message body a complete sentence.


Trying to pass a regular expression parameter, dollar sign is doubled

Trying to do similar to:
sqlalchemy.select(sqlalchemy.func.regexp_like(col, '^[0-9]*$'))
The dollar sign is doubled in the generated SQL because of this line https://github.com/databendlabs/databend-sqlalchemy/blob/3b65a3005f84127856a18b76d3c754f4ef26d63b/databend_sqlalchemy/connector.py#L41
@hantmac, any idea about the reason for this replacement?

@rad-pat Hi , Replacing a single $ with $$ ensures that $ in the original string is correctly interpreted as a literal character and
this can also helps prevent SQL injection and syntax errors.

Thanks, do you perhaps have an example of this so I can set up a test for it? Obviously I want to fix the issue I have without breaking other use cases.

The best solution by far would be to be able to push the parameters into the driver, but for now the bendSQL doesn't seem to support query parameters for some reason

Thanks, do you perhaps have an example of this so I can set up a test for it? Obviously I want to fix the issue I have without breaking other use cases.

For example:
price = "$100"
query = "SELECT * FROM products WHERE price_display=%s"

after
SELECT * FROM products WHERE price_display='$$100'

orignal
path = "C:\Users\file"
query = "SELECT * FROM files WHERE path=%s"
after
SELECT * FROM files WHERE path='C:\\Users\\file'

@hantmac, I tried these queries with the bendsql, the escaped paths work fine, but the double dollar signs are not substituted..
CREATE TABLE IF NOT EXISTS t_str (c1 string);
INSERT INTO t_str VALUES ('$100');
INSERT INTO t_str VALUES ('$$100');
INSERT INTO t_str VALUES ('c:\\some\\path');
INSERT INTO t_str VALUES ('c:\some\path');
select * from t_str;
┌──────────────────┐
│        c1        │
│ Nullable(String) │
├──────────────────┤
│ c:\some\path     │
│ $$100            │
│ $100             │
│ c:\some\path     │
└──────────────────┘
select * from t_str where c1 = '$100';
┌──────────────────┐
│        c1        │
│ Nullable(String) │
├──────────────────┤
│ $100             │
└──────────────────┘
select * from t_str where c1 = '$$100';
┌──────────────────┐
│        c1        │
│ Nullable(String) │
├──────────────────┤
│ $$100            │
└──────────────────┘

Possible to just remove the replacement of $ with $$ ?

@hantmac, I tried these queries with the bendsql, the escaped paths work fine, but the double dollar signs are not substituted..
CREATE TABLE IF NOT EXISTS t_str (c1 string);
INSERT INTO t_str VALUES ('$100');
INSERT INTO t_str VALUES ('$$100');
INSERT INTO t_str VALUES ('c:\\some\\path');
INSERT INTO t_str VALUES ('c:\some\path');
select * from t_str;
┌──────────────────┐
│        c1        │
│ Nullable(String) │
├──────────────────┤
│ c:\some\path     │
│ $$100            │
│ $100             │
│ c:\some\path     │
└──────────────────┘
select * from t_str where c1 = '$100';
┌──────────────────┐
│        c1        │
│ Nullable(String) │
├──────────────────┤
│ $100             │
└──────────────────┘
select * from t_str where c1 = '$$100';
┌──────────────────┐
│        c1        │
│ Nullable(String) │
├──────────────────┤
│ $$100            │
└──────────────────┘

Possible to just remove the replacement of $ with $$ ?

Oh I forgot it. The replacement is suit for databend-py, but now the driver has been changed to bendSQL, so it should be removed. Thanks!


Enforce trailing commas by default

Enforcing trailing commas by default leads to better diff'ing. A tool like this should aim to make dev lives easier, enforcing trailing commas does that.
<EMAIL_ADDRESS>

oops looks like I didn't merge this into my other PR. https://github.com/jlongster/prettier/pull/47

The problem is right now it also prints trailing commas for function args:
foo(
  1,
  2,
  3,
)

Because that is an upcoming feature (I think it's in stage 4) so that assumes you are using the babel extension to strip that out. I'd like to open this as an issue first and community input to see what the majority says. Do you mind opening an issue instead and we can talk about it there?

I need to start acting on these issues/PRs so closing this because I'd like to have a week or so worth's of discussion around changes like this before implementing them. Please open an issue!


random errors

I have some code doing:
# in tornado handler
...
res = await gen.multi({'1': self.send_task()})
...

async def send_task(self):
    async with self.redis.get() as conn:
      channel, = await conn.subscribe(uuid.uuid1().hex)
      # celery code
      task.apply_async(args=args, kwargs=kwargs, task_id=channel.name)
      await channel.wait_message()
      response = pickle.loads(await channel.get())
      await conn.unsubscribe(channel.name)

within my pytest, I randomly get the following errors(but the tests passed), any hints on where to look for the cause?:
Traceback (most recent call last):
  File "<string>", line 6, in _wrap_awaitable
  File "/xxx/handlers/radar.py", line 102, in get
  File "/xxx/handlers/__init__.py", line 455, in send_task
  File "/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/asyncio/coroutines.py", line 210, in coro
  File "/virtualenv//lib/python3.6/site-packages/aioredis/pool.py", line 333, in __aexit__
  File "/virtualenv//lib/python3.6/site-packages/aioredis/pool.py", line 218, in release
  File "/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/asyncio/tasks.py", line 506, in ensure_future
AttributeError: 'NoneType' object has no attribute 'isfuture'

Exception ignored in: <generator object _wrap_awaitable at 0x10ede50a0>
Traceback (most recent call last):
  File "<string>", line 6, in _wrap_awaitable
  File "/xxx/handlers/radar.py", line 102, in get
  File "/xxx/handlers/__init__.py", line 455, in send_task
  File "/usr/local/Cellar/python3/3.5.2_3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/asyncio/coroutines.py", line 206, in coro
  File "/virtualenv//lib/python3.5/site-packages/aioredis/pool.py", line 333, in __aexit__
  File "/virtualenv//lib/python3.5/site-packages/aioredis/pool.py", line 218, in release
  File "/usr/local/Cellar/python3/3.5.2_3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/asyncio/tasks.py", line 540, in ensure_future
AttributeError: 'NoneType' object has no attribute 'Future'

Exception ignored in: <generator object _wrap_awaitable at 0x117138f68>
Traceback (most recent call last):
  File "<string>", line 6, in _wrap_awaitable
  File "/xxx/handlers/radar.py", line 102, in get
  File "/xxx/handlers/__init__.py", line 455, in send_task
  File "/usr/local/Cellar/python3/3.5.2_3/Frameworks/Python.framework/Versions/3.5/lib/python3.5/asyncio/coroutines.py", line 207, in coro
TypeError: 'NoneType' object is not callable

There might be some problem with your asyncio module (does something monkey-patch it? or is there asyncio module in your project/code?).
First two exceptions are both not finding asyncio.futures module https://github.com/python/cpython/blob/v3.6.1/Lib/asyncio/tasks.py#L506.


[WIP] Set Network status in ForeignCluster

Description
This PR adds a summary of network status in ForeignCluster status
To avoid update race conditions every update is done by discovery component, it woke up thanks to an ownerReference on NetworkConfig and TunnelEndpoint resources when there are updates/deletions
When it is reconciling, it looks for resources with the correct cluster-id label checking their existence to accordingly update FC status

Pull Request Test Coverage Report for Build 291179174

95 of 203 (46.8%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 47.617%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/owner/owner.go
3
6
50.0%

internal/discovery/foreign-cluster-operator/setup.go
2
8
25.0%

api/discovery/v1alpha1/zz_generated.deepcopy.go
10
28
35.71%

internal/liqonet/tunnelEndpointCreator-operator.go
43
65
66.15%

internal/discovery/foreign-cluster-operator/foreign-cluster-controller.go
32
91
35.16%

Totals

Change from base Build 289157469:
0.1%

Covered Lines:
6185

Relevant Lines:
12989

💛  - Coveralls


Texture Update

I was wondering if you had any plans to rework the textures for shredded plant/plastic/starch plus plastic waste and Biomass. They feel more like place holders and somewhat unfinished.

Heh yes they are a little programmer-arty aren't they?
I wanted to add a couple more items then my plan was to ask around for an artist to redo the item textures. If you know of anyone, or any artists see this, let me know though 😊


feat!: change signature format from vrs to rsv

Description
signWithKey returns the signature in vrs order. publicKeyFromSignature likewise uses/expects this order. However, Clarity functions secp256k1-recover? and secp256k1-verify expect the signature in rsv order.
The stacks.js implementation should be following the standards.
This pull request changes the signWithKey signature order from vrs to rsv. This is a breaking change
Linked issues:

https://github.com/hirosystems/stacks-wallet-web/issues/2419
https://github.com/hirosystems/stacks-wallet-web/pull/2429

Type of Change

[ ] New feature
[ ] Bug fix
[ ] API reference/documentation update
[X] Other

Does this introduce a breaking change?
Yes this is a breaking change as the signature order is changing.
Checklist

[ ] Code is commented where needed
[ ] Unit test coverage for new or modified code paths
[ ] npm run test passes
[ ] Changelog is updated
[ ] Tag 1 of @yknl or @zone117x for review

The stacks.js implementation should be following the standards.

Which standards? I don't think any of the SIPs talk about signature order explicitly.
I assume this change breaks transaction signing as-is. Did you try that @pradel?
nextSignature() in stacks.js:
https://github.com/hirosystems/stacks.js/blob/20b721cdccc2fb73f98aad80eb6d5e8e9cb987d0/packages/transactions/src/authorization.ts#L326-L346
from_secp256k1_recoverable in stacks-blockchain uses vrs order:
https://github.com/stacks-network/stacks-blockchain/blob/26bfd5fcdc1f25106288f18ced05290b569f6abb/stacks-common/src/util/secp256k1.rs#L90-L99
CVM special function special_secp256k1_recover in stacks-blockchain uses rsv order:
https://github.com/stacks-network/stacks-blockchain/blob/26bfd5fcdc1f25106288f18ced05290b569f6abb/clarity/src/vm/functions/crypto.rs#L108-L149
(Is that correct @jcnelson?)

Which standards? I don't think any of the SIPs talk about signature order explicitly.

I understood SIP018 was specifying this from the previous conversations.

I assume this change breaks transaction signing as-is. Did you try that @pradel?

I didn't, so far the transactions tests are still failing on this pr, I am not sure what would be the best way to fix them to make sure other components do not break.

just as a suggestion -- I modified the signature to accept a mode param in micro-stacks
https://github.com/fungible-systems/micro-stacks/blob/1d679a08e874a9d94ef6f3ce9c8d4d44b8b60148/src/transactions/keys.ts#L172
so that nothing would break for legacy implementations, but for new applications they can opt into the different order.

I understood SIP018 was specifying this from the previous conversations.

Ah I see! Yes I think SIP018 is the only SIP that discusses signature order. However, the Stacks blockchain appears to be using both vrs (for transactions) and rsv (for the Clarity functions).

I didn't, so far the transactions tests are still failing on this pr, I am not sure what would be the best way to fix them to make sure other components do not break.

Perhaps the least confusing option for developers integrating with stacks.js would be to have a separate signMessage or signStructuredData function that returns the signature in the expected rsv format. Then we can also add counterparts verifyMessage and verifyStructuredData.
@aulneau solution is good too but definitely more advanced. (Developers would have to understand signatures and ordering to make an informed decision.)


Add header comment to generated workspace.bzl

workspace.bzl doesn't have a comment explaining that it is autogenerated. This means that devs unfamiliar with bazel-deps may waste time reading or editing this file, not knowing that the source of truth is dependencies.yaml.
I can see two approaches to avoid this.

Add a header comment to workspace.bzl, eg: # This file is autogenerated by bazel-deps from ${g.depsFile}.
Add an option for a custom header.

The first option is more invasive, but IMO more useful. What do you think?

I agree the first option sounds better. Want to take a stab?


3.4.3 Desktop

when the app opens the input box won't let me type in it and I'm trying to fix that.
3.4.3 Beta Desktop

fixed in Replacord 4.0


ellipsoid mirror setup

Hello Srio:
So sorry to disturb you but I have a trouble setting up the ellipsoid mirror.
In the interface of ellipsoid mirror, at "surface shape" unit, two choices of setup have been given : In the on hand, I can enter the object distance, image distance and incidence angle, then the program can automatically generate optical surface for me (internal/calculated) , in the other hand, I can directly  enter the semi-major axis and semi-minor axis (external/user defined).
Here comes the question: In the "external" model, SHADOW needs a parameter called "Angle of MajAx and Pole", I guess it’s the angle between optical element center normal and the major axis of the ellipsoid mirror. However, when I substitute the calculated value of the angle, the output is very different from the previous "internal" setting.

I would be very grateful if you could provide a specific geometric description of "Angle of MajAx and Pole".

Hi.
The angle is this "delta":

Some draft hand-notes and equations can be found here:
https://github.com/srio/shadow3-docs/blob/master/doc/conics.pdf
Hope this helps.

It actually works.
Thank you so much Srio.

You're welcome.


64 bit python

I've tried with 64 bit python on windows, with mingw / bash emulation. It complained about sys.maxsize has to be integer... It was, but 64 bit integer. I expect that all 64 bit python will fail that way.
It can be checked during program start and reported in more meaningful way, or simply add that info in troubleshoot.

Infer is not supported on Windows at the moment.

Visit our FAQ section on http://fbinfer.com/support.html


Devtool's management extension enabled state

This is a pretty powerful API, we currently use it to show a list of extensions but we can also use it to be able to show if the extension is enabled or disabled using this info.
If it seems like something that users would like we could even enable the extension from that page using the browser.management.setEnabled method.

This is done in #160


Does Audible use hidden watermarks?

This isn't really a code related issue but I figured the people who read this might know about it:
Does Audible instert hidden customer identifying watermarks in their audiobooks? And do they survive the conversion to MP3?
Thanks!

Interesting question. I happen to have access to two accounts with some identical audiobooks. Maybe I can find some time to do a comparison.

Speaking from the perspective of ffprobe, it wouldn't appear that the AAX checksum survives the conversion. That checksum and the encryption of the file itself may or may not identify a user.
I think that @thecb1 suggestion is only way to really tell if there is a difference between the two account outputs after the fact.
My stance however is to always treat any output from this script as your own personal property licensed to you for your personal use only. You should not share the output with anyone as that could be considered a violation of EULA of Audible. I haven't been contacted about this script being in violation of any agreement, but better safe than sorry I suppose.

I would also very much like to know the answer to this.
In some countries (like mine, see https://de.wikipedia.org/wiki/Privatkopie#Österreich ) it is legal to give copies of legally owned material two a few close friends, but of course if those where to do illegal things with it and the copy I gave them is watermarked to identify me that would cause legal problems for me.
So whether there is a watermark or not influences my decision on if I want to execute that right or not.

Good idea @thecb1 . If you can find some time, that'd be great! I have unfortunately only one account, so I can't test this.


Enhancement - Allow snapping of blocks by type

This is not an issue but more of a feature request, could there be a way to only allow certain types of blocks to attach to others, like in your demo only allow Actions and Loggers to be attached to a Trigger block.
Thank you!

This is already a feature, you can use onSnap which gets triggered when a block can attach to another block, and use the parent parameter + the current block to determine on your end if the blocks can attach or not. Just return false to prevent the attachment.
Let me know if that helps.

Do you mean this function on the demo? function snapping(drag, first)

Do you mean this function on the demo? function snapping(drag, first)

Yes, exactly. Here is how it works.

I am having issues getting the value out of the parent block.  parent.querySelector(".blockelemtype").value returns Uncaught TypeError: parent.querySelector is not a function

These are the only properties I get from parent, I can't access the value property
{"parent":-1,"childwidth":318,"id":0,"x":1158,"y":327,"width":318,"height":120}

Oh oops, this is clearly an oversight from my part as the parent property of the on snap method should return a DOM element and not the array. I've just fixed it, so now you can access the div to get the value.

Thank you so much! Worked perfectly :)

One more question, to filter what block can be the root block, the first one in the canvas, I should filter in flowy.endDrag or in the snapping function? If I do it in snapping it seems to attach it anyway. Thank you!


Refresh Token

In this Project How to use the Refresh token

I Solved It

How to use it?
Can you explained to me?

Thank you for your response. I already solved the problem.
On Sat, Oct 14, 2023, 1:16 PM Muhammad Taptazani Adi <
@.***> wrote:

How to use it?
Can you explained to me?
—
Reply to this email directly, view it on GitHub
https://github.com/hasancse91/flutter_getx_template/issues/33#issuecomment-1762675457,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH46RVOPV6A7HQSOHSHDAY3X7I33XANCNFSM6AAAAAATLDUCEU
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

I'm still confused for using this template for my project, can you explained to me for how this template work?

Its working fantastic, I already done 2 project.
On Sat, Oct 14, 2023, 5:11 PM Muhammad Taptazani Adi <
@.***> wrote:

I'm still confused for using this template for my project, can you
explained to me for how this template work?
—
Reply to this email directly, view it on GitHub
https://github.com/hasancse91/flutter_getx_template/issues/33#issuecomment-1762821328,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH46RVO7NXPWIPDSVCE2KDTX7JXPTANCNFSM6AAAAAATLDUCEU
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Can i see your project @Parvez6084 ?


Support for stage1-specific command line options

This issue is a discussion point whether to introduce stage1-specific command line parameters.
As rkt evolves, and more command line options appear, the more the subtle differences between the current stage1 implementations (nspawn, kvm/qemu, fly) leak in the UX experience.
The current PR to opt-out of security in stage1 (https://github.com/coreos/rkt/pull/2983) is bound to the runtime environment of nspawn based stage1 runtimes, not to KVM, and not to fly.
Suggestion: Introduce a new annotation coreos.com/rkt/stage1/parameters, and spec in the stage1 implementors guide, specifying a comma-separated list of strings of stage1-specific CLI options.
Examples nspawn stage1 manifest:
"annotations": [
{
  "name": "coreos.com/rkt/stage1/parameters",
  "value": "insecure,cap-retain,cap-remove"
},
...
]

The above example adds --insecure, --cap-retain, and --cap-remove to the nspawn based stage1. The actual parsing logic would have to be implemented in the binary pointed to by the coreos.com/rkt/stage1/run annotation.
TODO: Investigate whether/how these options can still be added to the cobra library.
/cc @coreos/rkt-maintainers @coreos/rkt-kvm-maintainers

SGTM. But not sure about how to inject into cobra as well.


[LATAM > US] Lead Python Developer @ Jobsity

Hello, everyone! 😁
I am an IT Sourcer working for Jobsity - an american staffing company that works with lots of different clients in the US, Canada and Europe. Our specialty is to find the perfect match between our client's needs with LATAM developers. We have connected more than 400 people with international employment. 👌
Descrição da vaga
We’re looking for a backend engineer who will be working closely with our Head of Engineering.
In the role, you will be responsible for helping to design, plan, and implement the backend services and tooling that power our SaaS platform. You will also be a leader, helping lead our team and especially our BE architecture and engineers. 😎
Local
Fully Remote.
Requisitos

Strong and deep experience writing scalable Django backends, working with relational databases (Postgres).

Engineering GraphQL APIs

Experience with end-to-end ownership of built systems.

Experience in DevOps/SRE practices such as:
Deployments
Managing incident response
Log and monitoring
Debugging in production.

Expertise in architectural design patterns.

Previous experience managing teams and communicating with stakeholders.

+C1 Advanced English level 🗣

Bonus skills:

Experience with React + Typescript
Experience with Hasura
Experience with Vercel
Experience with Fly.io

Benefícios
🔹15 business days of paid vacation yearly.
🔹3 extra off days per year.
🔹Paid local holidays.
🔹Unlimited PTOs.
🔹Learning budget.
🔹Financing program for equipment and home office supplies.
🔹Betterfly app (wellness).
🔹Bonuses for referrals and more!
Contratação
We offer full-time, long-term, 100% remote, and contractor (American contract) positions with USD payments + benefits within an international team and working on international client projects! 🌎
Como se candidatar
If you're interested, please reach out to me on Linkedin  or send me an email with your LinkedIn profile & updated Resume IN ENGLISH at<EMAIL_ADDRESS>with "Lead Python" as the subject.
Tempo médio de feedbacks
No response
Keywords
No response
Alocação

[ ] Alocado
[X] Remoto
[ ] Presencial
[ ] Híbrido

Regime

[ ] CLT
[ ] Estágio
[ ] Freela
[ ] PJ
[ ] Cooperado

Nível

[ ] Júnior
[ ] Pleno
[X] Sênior
[ ] Especialista

Período

[X] Full time
[ ] Part Time
[ ] Projeto

Remuneração
R$ 15k - R$ 20k

Hello!✨
This week we're still looking for a Lead Python Developer to join our team! 🚀
We also have a referrals program at Jobsity (https://careers.jobsity.com/referral-program).


Create walkthrough/sample for multi-targeting

Copied from https://github.com/MicrosoftDocs/mvp-hackadoc-2018/issues/42
https://docs.microsoft.com/en-us/nuget/create-packages/supporting-multiple-target-frameworks describes the capability, but we lack a good example with a walkthrough. Recommend approaching from a basic CLI standpoint using a folder structure to create the .nuspec.
The article itself can use a thorough review and update (see issues below). Needs to address cases where .NET Standard isn't suitable. Include doing this in VS. Include dotnet and nuget CLI commands in all examples.
Relevant issues:
#239
#622
#625

Mitigated somewhat by the new article on multi-targeting:
https://docs.microsoft.com/en-us/nuget/create-packages/multiple-target-frameworks-project-file

Low priority to document manually creating a .nuspec with the newer tooling. We have new articles on creagting a package with dotnet CLI and for multitargeting.


Support Inpaint Preprocessor

With the above commit there is now support for preprocessors that take a Mask input like the Inpaint preprocessor


Process exits after BMS disconnect

Process exits after BMS disconnects
16:23:38 INFO [sampling] ant24: BmsSampl(97.4%,U=26.7V,I=-0.30A,P=-8W,q=97.4Ah/100,mos=28.0°C)
16:23:38 INFO [sampling] ant24 volt=3.333,3.332,3.333,3.333,3.333,3.333,3.333,3.333 temp=[nan, nan]
16:23:44 WARNING [bt] BMS AntBt(9AA68C04-9C48-4FAD-7798-13ABB4878996) disconnected after 309.5s!
16:23:44 INFO [main] All fetch loops ended. shutdown is already False
16:23:44 INFO [main] Disconnecting AntBt(9AA68C04-9C48-4FAD-7798-13ABB4878996)
16:23:44 INFO [main] exit signal handler... (), {}, shutdown already True

see other issue


feat: add Timeline.Indicators.Time component

:tada: This PR is included in version 0.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Does this prompt from the NuGet Package Manager have any impact?

thank you~

Fixed in [https://github.com/datahint-eu/vizor-echarts/commit/bbb65ce254779b0983a7f47f3b436df504c3d940](this commit)


Update react-native-slider.podspec to use install_module_dependencies

Summary:
Fixes #529. More details: https://reactnative.dev/docs/the-new-architecture/backward-compatibility-turbomodules.
Test Plan:
Verify that the package compiles after enabling the new architecture

Superseded by #556


The "Save" event doesn't tell you which file was saved

I'm trying to subscribe to the "save" event so I can take some action as a result of a user editing an image. I noticed that the response from "save" does not include the name of the document that was saved. My workaround for this was to just send a follow-up message asking for the name of the active document, but this doesn't work if they save and close the file immediately after (which can happen quickly if using actions).
I see there is an "imageChanged" event, but it fires too frequently for me. For example, imageChanged fires whenever an edit occurs but the user hasn't saved yet. I've also seen it fire when switching between documents.
What I'd really like is an "imageSaved" event that fires only after a successful save and includes some basic information about the file that was saved (such as path/filename).
Does anything like this already exist?

This issue can be closed. I was able to work around it by subscribing to both "imageChanged" and "save", but only using "imageChanged" for keeping track of the active document.
Example:
client.on('connect', () => {
  subscribeToEvent(client, 'save');
  subscribeToEvent(client, 'imageChanged');
  resolve();
});

client.on('message', (id, parsed) => {
  if (parsed === 'save') {
    console.log('You saved: ', activeDocument);
  }
});

client.on('event', (id, name, parsed) => {
  if (name === 'imageChanged') {
    if (parsed.active && parsed.file) {
      activeDocument = parsed.file;
    }
  }
});


Release a new version from master

@LeonieFierz Hi - could you please cut and release a new version of this library so that it can be picked up by the Arduino Library Manager? There are a number of things added to master such as a new example with some functions currently unavailable for use unless the user has manually tracked this library.

Pls. remember to bump https://github.com/Sensirion/arduino-i2c-scd4x/blob/master/library.properties#L2 as well when you cut a release :)

Dear Brent (@brentru),
Thank you for that, it seems the release got forgotten along the way.
It should now be available.
Cheers,
Quentin


[hi] Localize /docs/setup/prodution-environment/tools/

Fixes #45213
Localized the content at /docs/setup/prodution-environment/tools/ page to Hindi.

/label tide/merge-method-squash

Got it, thanks for the suggestions, Divya! I've made the changes 👍🏻


It's really cool that Taiko's idea is the ZK-Rollup, the equivalent of Ethereum. Taiko allows Ethereum to scale by supporting all EVM opcodes in a Layer-2 architecture that is decentralized and secure. But there are still a lot of unsolved problems and fails with transactions and errors, we need to work on it

  It's really cool that Taiko's idea is the ZK-Rollup, the equivalent of Ethereum. Taiko allows Ethereum to scale by supporting all EVM opcodes in a Layer-2 architecture that is decentralized and secure. But there are still a lot of unsolved problems and fails with transactions and errors, we need to work on it

0x76fb696413C657a9FEDc14F2d664b700440ABb18
Originally posted by @DiForss in https://github.com/taikoxyz/taiko-mono/discussions/12432

Folks, please do not use GitHub issues for feedback. These should be for specific feature requests and bug reports. Thank you.


PUBD 1140: EZID Plugin errors and tests

Refactor code to enable testing and limit repeated code
Do more data validation and report nice errors including if there is no ISSN
don't cause an error if there is no abstract
Test all entry points

I like the direction of this work, and remember seeing a request to review from yesterday, but I can see this has since been switched to a draft, so I'll await another request to review when it's ready. Thanks for tackling this old plugin, and making it better! 🚀

Alas, my Janeway dev environment seems to be completely beyond repair. I cannot adequately test this PR. But it looks fine, so I'm going to approve it anyway.


Pushing new item in the array replace the last item in lit html

I am trying to create dynamic listing in lit-html but I am not able to understand while pushing new item into the array old item is being replaced somehow and DOM updates to the that item instead of adding a new list item.
I have tried several times with many different implementations but always result is same.
import { html, render } from 'lit-html';

const dataMain = {
  running: false,
  status: '',
  tags: [],
};

const chipsFunc = (tags) => {
  return tags.map((t, i) => html`

${t}
      ×

`);
}

function card(data) {
  console.log(data.tags);
  const chips = chipsFunc(data.tags);
  return html`

  ${data.running !== 'loading' ?
      html` <img src="../images/logo-38.png" class="mr-2 icon">` :
      html`<img src="../images/loader.svg" class="mr-2 icon">`
    }

    ${!data.running ?
      `Extension` :
      html`${status}`
    }

 <button type="button" class="btn">
   <svg width="1em" height="1em" viewBox="0 0 16 16" class="bi bi-three-dots" fill="currentColor" xmlns="http://www.w3.org/2000/svg">
  <path fill-rule="evenodd" d="M3 9.5a1.5 1.5 0 1 1 0-3 1.5 1.5 0 0 1 0 3zm5 0a1.5 1.5 0 1 1 0-3 1.5 1.5 0 0 1 0 3zm5 0a1.5 1.5 0 1 1 0-3 1.5 1.5 0 0 1 0 3z"/>
</svg></button>

  ${chips}

  <input type="text" class="form-control" id="add-tag" placeholder="Add Tag" @keyup="${e => addTag(e)}">

  `;
}
function addTag(e){
  if (e.key === 'Enter') {
    dataMain.tags.push(e.target.value);
    // e.target.value = "";
    render(card(dataMain), document.body);
  }
}

render(card(dataMain), document.body);

Please help me understand How can I make it work?

You used @click="${tags.splice(i, 1)}" which is not an action done on click but instead executed immediately. It produces the side effects you see.
Replace it with @click="${() => tags.splice(i, 1)}" and it should already have a better behavior.
You have to render again your cards somehow on deletion but that is something you can solve later

You used @click="${tags.splice(i, 1)}" which is not an action done on click but instead executed immediately. It produces the side effects you see.
Replace it with @click="${() => tags.splice(i, 1)}" and it should already have a better behavior.
You have to render again your cards somehow on deletion but that is something you can solve later

Thanks, I moved to hyperHtml. So I come to know the things work in tagged template literal based rendering.


Translation: Python version missing, tests will fail due to error message

When publishing my Python translation, suddenly the tests failed with error message:
Error: python version python not supported
I noticed that the python version was not shown anymore
https://www.codewars.com/kumite/59b460ba5227dd69dd000477/edit

Oh wow! When selecting a different language, I noticed that now Python has completely disappeared from the languages drop-down box.

@kazk  This issue is still standing: trying to "edit" the python translation gives invalid python version errors, and the version selection is totally missing:

Clicking on the language selector shows a list of languages without python:

However, clicking on "fork" you get the correct controls: language selector show only python and the version selector is also correct:

Yeah, that error message appears because the language version is set to "python". Unfortunately, I have no idea why Codewars does that.
Related: #1412

Try the following test:

create a kumite
publish
fork the kumite
save second kumite
edit second kumite
publish second kumite
edit published kumited

At this point I think the version should be gone.

A more simple workaround for the issue:

unpublish
(do your edits)
publish

@kazk I suggest to remove "python" from the title, because it seems to affect all languages with multiple versions: python and js was already reported, and I just encountered the same issue in ruby.


release a non-beta version -- 0.2.1?

I have never actually released a non-beta version.
Actually my version identifiers are a mess.
Because I didn't know what I was doing when I started this.
But I don't want to mess up e.g. any citations to specific versions of code, so, won't fix those.
so: just release a first non-beta before making any significant changes

Decided to call this final release '0.3.0'.
Who knows what I was thinking with the weird versioning scheme I was using.
But it feels even weirder to go from '0.2.1b1' to '0.2.1' (final) after the overhaul I just did.
So: 0.3.0

released! :tada: :weary:


Fix auto-patching operators generator to handle observable subclasses

This issue was pointed in #1178.
The tools/generate-operator-patches.ts is generating patches to some observable subclasses such as ScalarObservable and SubscribeOnObservable that are not directly export via static operators.

I'm working on this one.

Was this closed by #1178?

No. In the initial version, #1178 was adding to the code base these incorrect patches that the script is currently generating. After review it was removed from the commit but the script is still generating these files.

@luisgabriel you might want to take into account #1113 while working on this.

@blesh sure. I will. ;)

Closing this issue in favor of #1238.


Fixes #5015 - custom image selector not identifying photo location

Fixes #5015
What changes did you make and why?

AndroidManifest.xml - added permission ACCESS_MEDIA_LOCATION

ContributionController.java (line 72) - inside the onPermissionGranted lambda on checking WRITE_EXTERNAL_STORAGE permission, I added code to request ACCESS_MEDIA_LOCATION permission on devices running Android 10 or greater to obtain images without the exif data being redacted

Strings.xml - Added 2 string resources for displaying in the dialog box in case the user rejects ACCESS_MEDIA_LOCATION permission request

Why did I request ACCESS_MEDIA_LOCATION inside the onPermissionGranted lambda?
Case 1: Request ACCESS_MEDIA_LOCATION before WRITE_EXTERNAL_STORAGE
if (VERSION.SDK_INT >= VERSION_CODES.Q) {
                    PermissionUtils.checkPermissionsAndPerformAction(
                        activity,
                        permission.ACCESS_MEDIA_LOCATION,
                        () -> {},
                        R.string.media_location_permission_denied,
                        R.string.add_location_manually
                    );
                }

PermissionUtils.checkPermissionsAndPerformAction(activity,
            Manifest.permission.WRITE_EXTERNAL_STORAGE,
            () -> FilePicker.openCustomSelector(activity, 0),
            R.string.storage_permission_title,
            R.string.write_storage_permission_rationale);

Problem:

This permission dialog is shown once but clicking "Allow" does not navigate to the custom picker screen, a second click needs to be made to get there.
Case 2: Request ACCESS_MEDIA_LOCATION after WRITE_EXTERNAL_STORAGE
PermissionUtils.checkPermissionsAndPerformAction(activity,
            Manifest.permission.WRITE_EXTERNAL_STORAGE,
            () -> FilePicker.openCustomSelector(activity, 0),
            R.string.storage_permission_title,
            R.string.write_storage_permission_rationale);

if (VERSION.SDK_INT >= VERSION_CODES.Q) {
                    PermissionUtils.checkPermissionsAndPerformAction(
                        activity,
                        permission.ACCESS_MEDIA_LOCATION,
                        () -> {},
                        R.string.media_location_permission_denied,
                        R.string.add_location_manually
                    );
                }

Problem: The permission dialog is shown once and clicking "allow" navigate to the custom picker screen, but the location is not detected. As FilePicker.openCustomSelector(activity, 0) is executed when "allow" Is clicked, the app navigates to the custom picker screen before the code to request ACCESS_MEDIA_LOCATION can be executed.
Case 3: Requesting ACCESS_MEDIA_LOCATION inside the onPermissionGranted lambda (as in this pull request)
When requesting ACCESS_MEDIA_LOCATION inside the onPermissionGranted lambda, the permission dialog is shown once, on clicking "allow" navigates to the custom picker screen, and the location is successfully detected from pictures.
Tested betaDebug on

Realme Narzo 30 5G  with API level 33 (Android 13)
OnePlus dn2101 with API level 31 (Android 12)
Realme 3 Pro with API level 30 (Android 11)

Screenshots

Location successfully obtained from image picked using custom image picker [Realme Narzo 30 5G  with API level 33]

Code is great, maybe could have used a comment. Custom picker now finds location as intended on Android 13, anyone with other Android versions please test and report on the issue. Brilliant work, especially for a first GitHub pull request!

Thank you for the kind words Nicolas 😊