Ultraloq Pro Z-wave

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?
NO, my problem is NOT within Z-Wave JS UI
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
[77-98-0-latchStatus] Current status of the latch is always reporting "OPEN"
U-tec support said the issue could be on the z wave hub side.
Thread of others reporting the same issue: https://community.u-tec.com/t/expand-and-fix-z-wave-capabilities/502/18
Device information
Manufacturer: u-tec
Model name: U Bolt Pro Z wave
Node ID in your network: <077>
How are you using node-zwave-js?

[X] zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
zwave-js-ui: 8.6.3.c12b1c6
zwave-js: 10.3.1
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Don't know, this is a new device
If yes, where did it work?
No response
Attach Driver Logfile
zwavejs_current.log

Having same issue

I'll try on Monday

Thanks.  There really should be two entities for the pro if the sensor is present.  One for the lock, and one for the door sensor

That's a bug in the device firmware, at least in v1.1.3 which my lock is on.
When being queried for the supported door components, it has the byte set to 6:

which means Bolt and Latch states are supported, Door state isn't:

Given that the manual states that Bolt and Door are supported, this seems like a bug.

Despite that, I can't get the lock to report any change in door state.

Well that's not awesome.  I send an email to them about this issue with this thread... Maybe they can fix it.  Would be great to be able to get door status

Hi @AlCalzone ,
I wonder if we can put some special code in to make a fix for this device and this version firmware? the outdoorhandle value is clearly matching the door sensor state.
Or, if you can give me a quick hint where the related code is, I can try to make a change, then you can choose if you want to merge it in.
Thanks.

We don't hardcode such one-time device-specific behavior.

I've heard that U-Tec finally managed to reproduce the issue, but no idea if and when this will be fixed.

@AlCalzone  do you have a link to their issue I can follow ?

Nope, that was all back-channel information. Haven't head anything since.

I would like to add that they have seemingly made no progress on fixing this issue and I have discovered a second issue and it seems others have as well.
When the lock is triggered to lock, even if the locking process fails, say the door isn't closed all the way or something happens to make it not engage the deadbolt, the lock will beep and error out but the reported status to z-wave is that the lock was successful. This is dangerous as even though you should always manually check for security, it should report some kind of error or at least fallback to the previous state. Kind of disappointed in Ultraloq on the development of this.

Yeah, the lock is good, but if they don't actually fix bugs then it's
really not a great choice
On Tue, Jul 4, 2023, 10:31 TheOgre @.***> wrote:

I would like to add that they have seemingly made no progress on fixing
this issue and I have discovered a second issue and it seems others have as
well.
When the lock is triggered to lock, even if the locking process fails, say
the door isn't closed all the way or something happens to make it not
engage the deadbolt, the lock will beep and error out but the reported
status to z-wave is that the lock was successful. This is dangerous as even
though you should always manually check for security, it should report some
kind of error or at least fallback to the previous state. Kind of
disappointed in Ultraloq on the development of this.
—
Reply to this email directly, view it on GitHub
https://github.com/zwave-js/node-zwave-js/issues/5445#issuecomment-1620360640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADAEABHC2QPSLJ2OFVBKUTLXOQSNJANCNFSM6AAAAAAUXA6EVU
.
You are receiving this because you commented.Message ID:
@.***>

We have decided to terminate the Works with Home Assistant relationship with Ultraloq. We had reported these issues with them and were discussing solutions. However, they ceased communication from their end and have received no further updates.

We have decided to terminate the Works with Home Assistant relationship with Ultraloq. We had reported these issues with them and were discussing solutions. However, they ceased communication from their end and have received no further updates.

Good to see some action being taken about this. Thanks for keeping Home Assistant great!

I'm afraid there's nothing to be done in this project, since the functionality is just broken.

Could we update https://www.home-assistant.io/integrations/ultraloq/ ?

I'll do that on Tuesday!

@TheOneOgre @holblin @AlCalzone https://github.com/home-assistant/home-assistant.io/pull/28166

This problem has been solved in the new firmware, which can be upgraded online through Home assistant.

Will it be added back into the WWHA partner program?

Yes, we do our best to add it back.
Thanks!
@.***
From: God-TM
Date: 2023-08-23 08:51
To: zwave-js/node-zwave-js
CC: jack; Comment
Subject: Re: [zwave-js/node-zwave-js] Ultraloq Pro Z-wave (Issue #5445)
Will it be added back into the WWHA partner program?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Will it be added back into the WWHA partner program?

I wouldn't think it would or should be added back. Ignoring HA devs, not providing timely updates, not notifying users of issues, and overall not being easy to work with, is an easy disqualifier for being in a partner program. I think the biggest thing was the untimely manner in which they handled this and the complete lack of communication.
Also, I haven't tested it yet but, can anyone confirm if the "false lock" bug is still occurring where if the lock is told to lock, but fails due to the door being slightly open or something, the state is still reported as "Locked"? Was a HUGE oversight before if you relied on that status for your door being locked.

Also, I haven't tested it yet but, can anyone confirm if the "false lock" bug is still occurring where if the lock is told to lock, but fails due to the door being slightly open or something, the state is still reported as "Locked"? Was a HUGE oversight before if you relied on that status for your door being locked.

Tested and the "false lock" bug still exists.

Will it be added back into the WWHA partner program?

I wouldn't think it would or should be added back. Ignoring HA devs, not providing timely updates, not notifying users of issues, and overall not being easy to work with, is an easy disqualifier for being in a partner program.

Things have changed drastically in the last few weeks! Please feel free to put that to a test! I' doing exactly so with the last statement, the "false lock" bug which I expect to be worked on very soon.
But that's why, yes, we plan to add them back to the WWHA partner program!

Also, I haven't tested it yet but, can anyone confirm if the "false lock" bug is still occurring where if the lock is told to lock, but fails due to the door being slightly open or something, the state is still reported as "Locked"? Was a HUGE oversight before if you relied on that status for your door being locked.

Tested and the "false lock" bug still exists.

Thanks for Testing.  I will check it ASAP.

I just tested it. Perhaps I'm not understanding what's wrong here, but when I open and close the door, the sensor labled "Current status of the door" goes from Open to Closed and vice-versa accurately reflecting the state of the door. I can tell it to lock in either state, and the state is still either Open or Closed depending on if it's actually open or closed...

I have tested it, the door status is correct depending the open or close operation.
Please put the door magnet as close as possible to the lock, the farther the magnet is, the weaker the magnetic is.
Can you show me your test environment picture  include the lock and door magnet ？

I used to have a Gen 2 August Pro there, so I left the magnet from that and used it with the Ultraloq Pro. So far it's been working without any issues.

Please let me know if I can take any better measurements or angles that might be helpful for you.

Thanks for your info.

Can you gvie your lock Serial Number （SN：xxxxx）,inside of the battery cover ?
The magnet detection chip in the lock  and the detection algorithm are different from August, we don't  do compatibility test with August magnet.  Can you install ultraloq magnet as installation guide and test again？

I'm not the one having issues with this lock... I'd rather not break what's currently working for me.

I tested the lock jam bug. Does not update status.
lock serial number:<PHONE_NUMBER>130050

Do our best to optimizing them.

hi JPDMaker，
Where should the status of Jam be displayed  in home assistance UI?

It’s the state of the lock entity. Should update state to either ; Jammed, Locked, Locking, Unlocked, Unlocking, Unavailable, Unknown
https://developers.home-assistant.io/docs/core/entity/lock/

Oh we definitely should have those states!

Took me a while to track this down but this appears to be set in https://github.com/home-assistant-libs/zwave-js-server-python/blob/0.51.1/zwave_js_server/const/command_class/lock.py#L81-L86
Then mapped in HA core in https://github.com/home-assistant/core/blob/2023.8.4/homeassistant/components/zwave_js/lock.py#L40-L49

Jammed is not a lock state in node-zwave-js. It's a notification variable, which gets translated to a sensor in HA, I think here:
https://github.com/home-assistant/core/blob/7548c4aced3872c0d685ae0b07529a1f20fddbcd/homeassistant/components/zwave_js/discovery.py#L773-L785

This issue( When the lock is jammed,the lock status is lock, user can not lock again) is fixed. We are trying to add the jammed notifacation funcation, need more time.

New Z-Wave U-Bolt Pro, latest firmware applied, status is still stuck at open in HA. The app shows correctly so the position sensor is working.

I still find it tricky to trigger changes of the sensor without mounting the lock in a doorframe, but I haven't managed to get the state in the app and HA out of sync. When the status does change, I see it in both. Might be a connectivity issue?

I still find it tricky to trigger changes of the sensor without mounting the lock in a doorframe, but I haven't managed to get the state in the app and HA out of sync. When the status does change, I see it in both. Might be a connectivity issue?

Don't think so? After latest update the door status seems to be working slightly better. What consistently seems to not work is auto-lock after X seconds doesn't seem to update the lock status.  Opening the door from outside and then it locking automatically when closed is working. But if I open it from HA, then it auto locks after 15 seconds... the status does not get updated.

auto-lock after X seconds doesn't seem to update the lock status

Wait, are we talking about the lock status or the door status?

auto-lock after X seconds doesn't seem to update the lock status

Wait, are we talking about the lock status or the door status?

Sorry I kind of switched gears. Door open status seems to be a bit better since the latest update. However the auto-lock has been an issue since adding the lock. But anytime I manually unlock it, that gets tracked properly in HA.

Ok I'll try to reproduce that tomorrow

I have tested in our site. The lock updates the correct status after auto-lock.   For testing door status,please move the lock body,don't move magnet.
The version of my lock.
The firmware version(in u-tec app show):02.26.0022
The Z-wave firmware version(HA show):1.5.3
Can you share me the testing video? We want more operate details to debug the issue. Thanks.

I have tested in our site. The lock updates the correct status after auto-lock. For testing door status,please move the lock body,don't move magnet.
The version of my lock. The firmware version(in u-tec app show):02.26.0022 The Z-wave firmware version(HA show):1.5.3
Can you share me the testing video? We want more operate details to debug the issue. Thanks.

Ok I have some further testing results. Door open status seems to be working perfectly fine for the moment. Door lock status status when opened at the lock seems perfectly fine, including when it auto locks. When I open the lock via the app, and it auto locks, status is reported fine. It's only when I open the door via HA that this issue occurs. And it doesn't seem to matter which kind of card I use. I can open the lock, it will update the status, but when the lock auto locks the HA state still reflects unlocked. When I click it again, it will beep and indicate lock. Sometimes this can get totally out of sync where it think it's unlocked but it's actually locked or vice versa. So it's only when controlling via HA that this is occurring. I can try and make a video if it's helpful I just wanted to clarify that first.

Can you give me a interface picture that you operate the lock and the status show ?
I will check it.

Can you give me a interface picture that you operate the lock and the status show ? I will check it.

I will try and upload something a bit later. I did want to add I found something else interesting today. I opened the lock from inside to go out. It captured the door and lock sensors fine. However, it did not capture either door unlock/lock or open/closed events when I came back, using the fingerprint sensor and the door automatically locking when I shut it. I'm not sure if maybe it just didn't have time to register those events or they didn't get sent or what.

My testing enviroment is:  a  Iaptop ( installed  HA virtual machine, Connected a SLUSB700A  hub with new driver, edge Brower
to login to HA in virtual machine and do operation  ); a u-bolt pro z-wave and magnet on a door. I don't use mobile APP.
what's your testing enviroment?  Where do you want to see the events? Let's keep in the same page.

My testing enviroment is: a Iaptop ( installed HA virtual machine, Connected a SLUSB700A hub with new driver, edge Brower to login to HA in virtual machine and do operation ); a u-bolt pro z-wave and magnet on a door. I don't use mobile APP. what's your testing enviroment? Where do you want to see the events? Let's keep in the same page.

Ya not trying to muddy the waters. Just let me know what helps most to troubleshoot.
I'm running a dedicated ASRock BeeBox, with HAOS running Virtualbox (latest version, extension manager installed and USB passthrough), on Windows 10, Zooz ZST10-700 with firmware 7.19.2. Doesn't matter if I login with the HA web interface, or the HA app., I get the same result. I have the magnet on the door frame as well.
I am looking at the entity values/history directly for the most part. I know if those don't work then anything relying on them most likely won't either.

Sorry, I just want to know how to reproduce the bug you mentioned in my side and try  help debug. I will update If i have new info.

100%! No need to apologize I appreciate your help. Will get you info soon.

Any update on the last remaining bug?

Any update on the last remaining bug?

Hi Chris - apologies I was travelling for the better part of the last month and a half.  It is still happening for sure.

Here's a quick video to illustrate what is happening: https://youtu.be/cmq1fcqTxyA
In short: if I click the unlock button, the lock unlocks as expected. Sometimes it takes a second to register on the card in HA but that works pretty consistently. But notice once the door lock auto locks (10 seconds after the unlock), the status doesn't update in HA. It remains as "unlocked".  I guess the lock knows it's locked hence the single beep. For whatever reason HA just won't update with that manual action. This only happens when I use the unlock button on one of the cards. If I use the Utec app, the status updates for both when it unlocks and auto locks as expected.

I agree, I have the same behavior in my instance.

Thank you for sharing the video, I am experiencing the same with my lock.

Interesting. Mine isn't doing that.
I click the unlock button, it unlocks. Mine is set to auto lock after 30 seconds. It locks and the status in HA updates immediately.
Interesting. If I set it to lock after 10 seconds, it does what you're experiencing. Setting it to 20 seconds works fine.
Hopefully this helps with troubleshooting the bug.

Interesting. Mine isn't doing that.
I click the unlock button, it unlocks. Mine is set to auto lock after 30 seconds. It locks and the status in HA updates immediately.
Interesting. If I set it to lock after 10 seconds, it does what you're experiencing. Setting it to 20 seconds works fine.
Hopefully this helps with troubleshooting the bug.

I was optimistic when I saw this but I'm still having mixed results. I set my timeout to 20 seconds. The first time I tried the HA unlock, it worked as you described above. So I tried it again in succession, and it didn't work. Same result as I was getting before. After about 30 minutes I tried again, this time it worked. Again, tried in succession, it didn't work. Using the app, it works flawlessly. I can unlock, auto-lock, then unlock again in succession and the status is updated in HA as expected.
I will say I know when HA is not going to work because when I unlock the lock, it takes a few seconds for it to register in HA. When that happens, I know when it auto locks it's not going to update. When I unlock and it updates almost immediately, I know the auto lock status update is going to work.

So HA removed the "Works With HA". Does that mean we are screwed?  Just hope that U-Tec will fix it at some point?

They fixed the issue and Home Assistant will offer users to update this firmware

They fixed the issue and Home Assistant will offer users to update this firmware

OK and where it is?? I still don't see firmware update.

I find conflicting information on whether ULtraLoq is or is not a WWHA product. At this link: https://www.home-assistant.io/integrations/ultraloq/ it seems that it is, but I've seen threads that indicate ULtraLoq has been unresponsive to fixing issues and it has been removed from WWHA. I am considering replacing my current WiFi UltraLoq with the Z-Wave enabled version, but I don't want to do this if it is not reliably supported in HA. Can anyone shed some light on the state of UltraLoq support in HA?

Late last month I did find a post on the Ultraloq forums talking about the same issue. In it someone from Ultraloq mentioned that a ticket would need to be opened and they would need to replace the lock. After opening the ticket and talking with someone they gave me this https://file.u-tec.com/homekit/U-BOLT-PRO-ZWAVE_V1.7.gbl to update the firmware from HA. That was about 2 weeks ago and things seem to be fixed.
https://file.u-tec.com/homekit/U-BOLT-PRO-ZWAVE_V1.7.gbl
TLDR. Use the above link from Ultraloq and give it a try.

@Daguse how'd you install the firmware? I'm using HA with Z-Wave JS UI and I'm not sure how to upgrade with a downloaded firmware file. Both HA and Z-Wave JS UI shows the device is up-to-date with no option to provide my own firmware files.

What firmware does it show? Mine says it's v1.5.3 which I assume is current for the z-wave model. I do see on their site that 1.41 is available, but it seems only for the wi-fi models.

@zirdum in HA/Z-Wave-JS it shows 1.5.3, however, in U home it shows 02.26.0022. The FW link above seems to indicate it's 1.7

Late last month I did find a post on the Ultraloq forums talking about the same issue. In it someone from Ultraloq mentioned that a ticket would need to be opened and they would need to replace the lock. After opening the ticket and talking with someone they gave me this LINK to update the firmware from HA. That was about 2 weeks ago and things seem to be fixed.
https://file.u-tec.com/homekit/U-BOLT-PRO-ZWAVE_V1.7.gbl
TLDR. Use the above link from Ultraloq and give it a try.

Thank you for posting this! It fixed my issues!


[firebase_messaging] App crashes on startup after adding onBackgroundMessage

I followed everything written in firebase_messaging readme. After adding the onBackgroundMessage handler and "Application.java" to AndroidManifest the app installs but crashes on startup. What am I doing wrong?
Thanks in advance

Hi @GuilhermePontes9 could you provide the stack trace of what your error is when you app crashes?

Sorry, I don't know if it's the correct way to do it but I run .\gradlew build --stacktrace and the result was this:

Task :app:compileFlutterBuildDebug
Parameter format not correct -

Task :app:stripDebugDebugSymbols UP-TO-DATE
Compatible side by side NDK version was not found.

Task :app:lint
Ran lint on variant debug: 4 issues found
Ran lint on variant release: 4 issues found
Ran lint on variant profile: 4 issues found
Wrote HTML report to file:///C:/Flutter%20Projects/sirene_virtual/build/app/reports/lint-results.html
Wrote XML report to file:///C:/Flutter%20Projects/sirene_virtual/build/app/reports/lint-results.xml

Task :audioplayers:lint
Ran lint on variant debug: 2 issues found
Ran lint on variant release: 2 issues found
Ran lint on variant profile: 2 issues found
Wrote HTML report to file:///C:/Flutter%20Projects/sirene_virtual/build/audioplayers/reports/lint-results.html
Wrote XML report to file:///C:/Flutter%20Projects/sirene_virtual/build/audioplayers/reports/lint-results.xml

Task :cloud_firestore:lint
Ran lint on variant profile: 6 issues found
Ran lint on variant release: 6 issues found
Ran lint on variant debug: 6 issues found
Wrote HTML report to file:///C:/Flutter%20Projects/sirene_virtual/build/cloud_firestore/reports/lint-results.html
Wrote XML report to file:///C:/Flutter%20Projects/sirene_virtual/build/cloud_firestore/reports/lint-results.xml

Task :firebase_auth:lint
Ran lint on variant debug: 4 issues found
Ran lint on variant release: 4 issues found
Ran lint on variant profile: 4 issues found
Wrote HTML report to file:///C:/Flutter%20Projects/sirene_virtual/build/firebase_auth/reports/lint-results.html
Wrote XML report to file:///C:/Flutter%20Projects/sirene_virtual/build/firebase_auth/reports/lint-results.xml

Task :firebase_core:lint
Ran lint on variant profile: 2 issues found
Ran lint on variant debug: 2 issues found
Ran lint on variant release: 2 issues found
Wrote HTML report to file:///C:/Flutter%20Projects/sirene_virtual/build/firebase_core/reports/lint-results.html
Wrote XML report to file:///C:/Flutter%20Projects/sirene_virtual/build/firebase_core/reports/lint-results.xml

Task :firebase_core_web:lint
Ran lint on variant debug: 1 issues found
Ran lint on variant release: 1 issues found
Ran lint on variant profile: 1 issues found
Wrote HTML report to file:///C:/Flutter%20Projects/sirene_virtual/build/firebase_core_web/reports/lint-results.html
Wrote XML report to file:///C:/Flutter%20Projects/sirene_virtual/build/firebase_core_web/reports/lint-results.xml

Task :firebase_database:lint
Ran lint on variant release: 3 issues found
Ran lint on variant debug: 3 issues found
Ran lint on variant profile: 3 issues found
Wrote HTML report to file:///C:/Flutter%20Projects/sirene_virtual/build/firebase_database/reports/lint-results.html
Wrote XML report to file:///C:/Flutter%20Projects/sirene_virtual/build/firebase_database/reports/lint-results.xml

Task :firebase_messaging:lint
Ran lint on variant release: 5 issues found
Ran lint on variant profile: 5 issues found
Ran lint on variant debug: 5 issues found
Wrote HTML report to file:///C:/Flutter%20Projects/sirene_virtual/build/firebase_messaging/reports/lint-results.html
Wrote XML report to file:///C:/Flutter%20Projects/sirene_virtual/build/firebase_messaging/reports/lint-results.xml

Task :path_provider:lint
Ran lint on variant profile: 1 issues found
Ran lint on variant debug: 1 issues found
Ran lint on variant release: 1 issues found
Wrote HTML report to file:///C:/Flutter%20Projects/sirene_virtual/build/path_provider/reports/lint-results.html
Wrote XML report to file:///C:/Flutter%20Projects/sirene_virtual/build/path_provider/reports/lint-results.xml

BUILD SUCCESSFUL in 22s
792 actionable tasks: 28 executed, 764 up-to-date

@GuilhermePontes9 I should have been clearer. I was hoping to see the stack trace (hopefully containing some errors) you get when the app crashes.

Sorry for my misunderstanding, I'm still in the process of learning all this!
This is the stacktrace i get when the app crashes:

java.lang.RuntimeException: Unable to instantiate activity ComponentInfo{guilhermepontes.sirene_virtual/guilhermepontes.sirene_virtual.Application}: java.lang.ClassCastException: guilhermepontes.sirene_virtual.Application cannot be cast to android.app.Activity
at android.app.ActivityThread.performLaunchActivity(Unknown Source:645)
at android.app.ActivityThread.handleLaunchActivity(Unknown Source:36)
at android.app.servertransaction.LaunchActivityItem.execute(Unknown Source:57)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(Unknown Source:99)
at android.app.servertransaction.TransactionExecutor.execute(Unknown Source:34)
at android.app.ActivityThread$H.handleMessage(Unknown Source:36)
at android.os.Handler.dispatchMessage(Unknown Source:21)
at android.os.Looper.loop(Unknown Source:207)
at android.app.ActivityThread.main(Unknown Source:107)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(Unknown Source:11)
at com.android.internal.os.ZygoteInit.main(Unknown Source:274)
Caused by: java.lang.ClassCastException: guilhermepontes.sirene_virtual.Application cannot be cast to android.app.Activity
at android.app.AppComponentFactory.instantiateActivity(Unknown Source:8)
at androidx.core.app.CoreComponentFactory.instantiateActivity(CoreComponentFactory.java:41)
at android.app.Instrumentation.newActivity(Unknown Source:22)
at android.app.ActivityThread.performLaunchActivity(Unknown Source:87)
... 11 more

I looked again at the instructions and realised that I added .Application in the activity tag, not on the application tag in the AndroidManifest. You can delete the issue, my bad. Thank you for your time!


Pins don't appear when binding after initial bind

I have a TKCustomMap on my page with the Pins bound to a list.  After the initial binding of the Pins, the map doesn't update.  For example, I have 5 pins located in Denver, CO, then I update the query and now I have 10 pins in Colorado Springs, CO, the map still show the initial 5 even though the Pins property on the map has 10 pins.   Is there a method that needs to be called to refresh the map?
TK.CustomMap v2.0.1

Looks like it was a Nuget package issue.  I uninstalled the TK.CustomMap package, deleted it, and reinstalled the package.  It is working as expected now.


TeXLive appears to require sed at runtime

The TeXLive 2021 distribution (e.g. the texlive.combined.scheme-medium Nixpkgs package) in Nix-on-Droid seems to be missing a dependency on sed, even though it installs fine without it. The culprit is the mktextfm (make TeX font metrics) script, which is invoked every time a previously unused (font, size) combination is requested on the system, and seems to require sed to run (I don't know if it has to be GNU sed or if any POSIX sed will do).
I suspect this is a problem with upstream Nixpkgs, but I'm filing it here for now just in case there is some sort of implicit "base system" assumption in Nixpkgs / NixOS that Nix-on-Droid violates.

Can't say I'm aware of the "base system" assumptions of NixOS either. Please point us at them if you find them; though it doesn't necessarily mean we'll follow them by default though. E.g., preinstalling stdenv is something we avoid on purpose.
The missing dependency does sound like a packaging bug to me.

No package should rely on any base system environment. That is the whole idea of nix packaging. So this should be reproducable in every other (pure) environment and therefore a bug in nixpkgs :)

@Gerschtli

No package should rely on any base system environment. That is the whole idea of nix packaging.

Yeah, that sounded weird to me too, but it’s a fairly common practice in conventional distros and I know next to nothing about the internal organization of Nixpkgs & friends, so I decided to hedge a bit in case Nix-on-Droid does actually do something atypical. I honestly don’t know if it is possible to make a normal NixOS install that wouldn’t have sed (or cp, or ...) in $PATH, and if it is, how.

OK, the problem set is out, I can now try to make a less lazy reproduction for this.
... But it turns out to be trickier than I thought: it’s straightforward to get mktextfm to be invoked by doing what I was doing—typesetting documents in Cyrillic—but that requires a fairly extensive TeXLive installation. I must admit I can’t actually get it to run on e.g. a ‘basic’ installation with a small English-language test document, probably because the default (Latin-only) Computer Modern fonts come with metrics already included.
Still, if you find the combined texlive-whatever package inside the Nix store and look in share/texmf/scripts/texlive/mktexmf, there are a couple of invocations of sed in the very first lines of the script (that accomplish the equivalent of basename and dirname or a shell substitution like ${0##*/}, but it is what it is).
I’ll try to take this to the Nixpkgs people and see what they say.

typesetting documents in Cyrillic—but that requires a fairly extensive TeXLive installation

True. I used to configure elaborate environments with texlive.combine by trial and error, but then decided life's too short and switched to just pulling enormous -scheme based ones =)

@alexshpilkin You are right, conventional distros rely on such a base configuration, which is a problem that nix tries to solve. I never tested it, but is should be possible to remove every package from environment.systemPackages and the user installed ones except for the basic nix-* packages and it should run perfectly fine. If not, then this should be filed as a bug. Sometimes it is just hard to find these runtime dependencies if you do not run everything in a pure mode :)


Query an object based off list of mongo_id's

I have a list of id's and am looking for a simple query that will get a list of the objects that correspond to those id's.  Right now I have to do a loop through my list of id's and do a query.get(id) for each id.  Is there a way to return the list of objects by making one query instead of hundreds of separate ones?

http://www.mongoalchemy.org/api/expressions/query_expressions.html#mongoalchemy.query_expression.QueryField.in_
I think this should do it:
session.query(Foo).filter(Foo.mongo_id.in_(id1, id2, id3, ...))

is there a way to do that using a dynamically generated list instead of (id1, id2, id3, ...)?

Yep, just use *your_list and it will work

I was missing the *.  It works perfectly now. Thanks for the help


Ilogger in IAfterSaveTrigger class causes DI error

Following the wiki examples, I created my trigger class as
`    public class DeviceMessageTrigger : IAfterSaveTrigger
{
protected readonly JAoTSQLContext _context;
protected readonly ILogger _logger;
    public DeviceMessageTrigger(JAoTSQLContext context, ILogger<DeviceMessageTrigger> logger)
    {
        _context = context ?? throw new ArgumentNullException(nameof(context));
        _logger = logger ?? throw new ArgumentNullException(nameof(logger));
    }

    public async Task AfterSave(ITriggerContext<Device_Message> context, CancellationToken cancellationToken)
    {
        switch (context.ChangeType)
        {
            case ChangeType.Added:
                _logger.LogDebug("Executing Trigger Action");
                await _context.ServiceBroker_DeviceMessageAdded(context.Entity.DeviceMessageID, context.Entity.DeviceID);
                break;

------ continue
`
and registered the trigger in both the context itself
 protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)         {             if (!optionsBuilder.IsConfigured)             {                 optionsBuilder.UseSqlServer(_connectionString, x =>                 {                     x.UseNetTopologySuite();                     x.CommandTimeout(GetConnectionTimeout());                 });                 optionsBuilder.UseTriggers(o =>                 {                     o.AddTrigger<DeviceMessageTrigger>();                     o.AddTrigger<ConfigurationDownlinkPayloadTrigger>();                 });             }         }
and in the Progam.Main services configuration:
  services.AddDbContext<JAoTSQLContext >(options =>         {             options.UseSqlServer();             options.UseTriggers(t =>             {                 t.AddTrigger<DeviceMessageTrigger>();                 t.AddTrigger<ConfigurationDownlinkPayloadTrigger>();             });         });
Compilation and application startup are OK, but as soon as an insert into the table is run I get this error stating that the DI cannot create the logger instance.
ERROR|DataConnectors.SQLConnector.Log_DefaultError|Error raised while executing operation SaveDeviceMessageData.|System.InvalidOperationException: Unable to resolve service for type 'Microsoft.Extensions.Logging.ILogger1[DataConnectors.EFCore.EFTrigger.DeviceMessageTrigger]' while attempting to activate 'DataConnectors.EFCore.EFTrigger.DeviceMessageTrigger'.    at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.GetService(IServiceProvider sp, Type type, Type requiredBy, Boolean isDefaultParameterRequired)    at lambda_method878(Closure, IServiceProvider, Object[])    at EntityFrameworkCore.Triggered.Internal.TriggerInstanceFactory1.Create(IServiceProvider serviceProvider)
at EntityFrameworkCore.Triggered.Internal.TriggerFactory.Resolve(IServiceProvider serviceProvider, Type triggerType)+MoveNext()
at EntityFrameworkCore.Triggered.Internal.TriggerDiscoveryService.DiscoverTriggers(Type openTriggerType, Type entityType, Func2 triggerTypeDescriptorFactory)    at EntityFrameworkCore.Triggered.TriggerSession.RaiseTriggers(Type openTriggerType, Exception exception, ITriggerContextDiscoveryStrategy triggerContextDiscoveryStrategy, Func2 triggerTypeDescriptorFactory, CancellationToken cancellationToken)
at EntityFrameworkCore.Triggered.Internal.TriggerSessionSaveChangesInterceptor.SavedChangesAsync(SaveChangesCompletedEventData eventData, Int32 result, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at DataConnectors.SQLConnector.<>c__DisplayClass138_0.<g__SaveDeviceMessage|0>d.MoveNext() in C:\Develop\Projects\Repos\JAoT.Core\DataConnectors\SQLConnector.cs:line 5469
--- End of stack trace from previous location ---
at DataConnectors.SQLConnector.<>c__DisplayClass138_0.<b__1>d.MoveNext() in C:\Develop\Projects\Repos\JAoT.Core\DataConnectors\SQLConnector.cs:line 5435
--- End of stack trace from previous location ---
at DataConnectors.SQLConnector.DataContextExecuteAsync[T](Func2 action, IServiceProvider serviceProvider) in C:\Develop\Projects\Repos\JAoT.Core\DataConnectors\SQLConnector.cs:line 114    at DataConnectors.SQLConnector.DataContextExecuteAsync[T](Func2 action) in C:\Develop\Projects\Repos\JAoT.Core\DataConnectors\SQLConnector.cs:line 103
at DataConnectors.SQLConnector.SaveDeviceMessageData(IDeviceMessage deviceMessage) in C:\Develop\Projects\Repos\JAoT.Core\DataConnectors\SQLConnector.cs:line 5433
Please note that if I remove the logger (leaving the data context) the operations are fully successful: it looks like the problem is only affecting the logger, not the data context.
I also tried to get the ILoggerFactory object from the DI:
` public class DeviceMessageTrigger : IAfterSaveTrigger<Device_Message>
{
protected readonly JAoTSQL _context;
protected readonly ILogger _logger;
    public DeviceMessageTrigger(JAoTSQL context, ILoggerFactory loggerfactory)
    {
        _context = context ?? throw new ArgumentNullException(nameof(context));
        _logger = loggerfactory?.CreateLogger<DeviceMessageTrigger>() ?? throw new ArgumentNullException(nameof(loggerfactory));
    }

    public async Task AfterSave(ITriggerContext<Device_Message> context, CancellationToken cancellationToken)
    {
        switch (context.ChangeType)
        {
            case ChangeType.Added:
                _logger.LogError("Executing Trigger Action");
                await _context.ServiceBroker_DeviceMessageAdded(context.Entity.DeviceMessageID, context.Entity.DeviceID);
                break;

`
This way I do not get any error, and the trigger is called and executed as expected. But the logger does not write anything even if I made sure the instance was created successfully by the ILoggerFactory and I raised the Log level to Error to avoid the log entry to be filtered.
I checked and can confirm the async trigger is called only after  SaveAsync calls not to mix sync and async code and, in addition, please note that I moved the logging configuration before and after the configuration of the db context and trigger components, but did not change the behavior.
Did I miss anything or is it a problem with the Triggers?
Thank you

I think the issue may be related to registering the trigger within the OnConfiguring method. I suspect that during runtime, it uses the internal service provider of EF core to resolve services as there is no application service provider and it fails to resolve the proper logging services.
Can you try and either remove registering the trigger within the OnConfiguring method and always make sure that you use DI to get a DbContext?

if I remove the registration within the OnConfiguring method, I don't get the trigger working anymore:
        protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)         {             if (!optionsBuilder.IsConfigured)             {                 optionsBuilder.UseSqlServer(_connectionString, x =>                 {                     x.UseNetTopologySuite();                     x.CommandTimeout(GetConnectionTimeout());                 });                 //optionsBuilder.UseTriggers(t =>                 //{                 //    t.AddAssemblyTriggers(typeof(JAoTSQL).Assembly);                 //});             }         }
and I also double checked again (I am monitoring just a single operation, so I can be sure) to make sure the dbcontext for that operation is created by the DI container, it is called from here:
        public static async Task<T> DataContextExecuteAsync<T>(Func<JAoTSQLContext, Task<T>> action, IServiceProvider serviceProvider)         {             using IServiceScope scope = serviceProvider.CreateScope();             using JAoTSQL sql = scope.ServiceProvider.GetRequiredService<JAoTSQL>();             return await action(sql);         }
Just to explore the issue, I tried to inject into the dbcontext my IServiceProvider: and to pass it to the trigger configuration:
 protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)         {             if (!optionsBuilder.IsConfigured)             {                 optionsBuilder.UseSqlServer(_connectionString, x =>                 {                     x.UseNetTopologySuite();                     x.CommandTimeout(GetConnectionTimeout());                 });                 optionsBuilder.UseTriggers(t =>                 {                     t.AddAssemblyTriggers(typeof(JAoTSQL).Assembly);                     t.UseApplicationScopedServiceProviderAccessor(s => _serviceProvider);                 });             }         }
this actually solved the problem of the log creation, but ended up creating the usual problems related to injecting a singleton service into a scoped one.
I think it is a problem about injecting the right serviceProvider into the instance, but - at the moment - I did not find a solution.

Maybe not the most elegant solution, but I am ending up using a static method to get the logger instead of requesting it from the DI container:
  private readonly ILogger<DeviceMessageAction> _logger;         public DeviceMessageTrigger(JAoTSQLContext context) : base(context)         {             _logger = Common.Extensions.DefaultLoggerFactory.CreateLogger<DeviceMessageAction>(); //static method         }
it works and I get the logging capabilities.
If you have some ideas or news, I am still very interested in obtaining the result by using the full DI workflow.

I am having the same issue. If I move configuration out of OnConfigure it simply never fires triggers. If I use the OnConfiguring, I cannot resolve any scoped dependencies in my triggers. I've attempted to inject the service provider into the constructor of my DBContext and then use UseApplicationScopedServiceProviderAccessor but it ends up generating another error after sometime about more than twenty IServiceProvider being created. Any recommendations on how I can get the scoped service provider into my DBContext?


Fix learning interact

Description
The agent_selector func was called twice when you select learning and cause an issue with st.selectbox
And for the start script nothing was changed It's a mistake my bad

Motivation and Context

How has this been tested?

Screenshots (if appropriate)
Types of changes

Changes visible to users:

[x] Bug fix (prefix: fix - non-breaking change which fixes an issue)
[ ] New feature (prefix: feat - non-breaking change which adds functionality)
[ ] Breaking change (prefix: feat!! or fix!! - fix or feature that would cause existing functionality to not work as expected)

Internal changes:

[ ] Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)
[ ] Tests (prefix: test - additions and improvements to unit tests and the smoke tests)
[ ] Infrastructure (prefix: chore - examples include GitHub Actions, issue templates)

Checklist

[ ] My code follows the code style of this project and passes yarn run lint.
[ ] My change requires a change to the documentation.
[x] My change works!

Thanks!


[Feature Request] Ability to set folders/views to be non-editable

I don't think this was submitted, so I'm taking cue from this post on the forum:  https://forum.archimatetool.com/index.php?topic=683.msg3873#msg3873
Any way (or any plug-in) to make views such that if set then Archi would not allow elements from the palette to be added or moved, hence 'locking' a view from further manual modifications
Also, the ability to apply this recursively to all sub-folders and views if set at folder level.
I'm guessing this can be achieved by setting up a special "locked" property in the view that Archi can act on?

I'm guessing this can be achieved by setting up a special "locked" property in the view that Archi can act on?

Plus a whole lot more code related to every aspect of Archi - drag and drop, copy and paste, view editors, objects, undo/redo, views, folders, palette, scripting, testing and so on. It would require a deep analysis of what's involved and its impact. Not something that can happen easily.


Backport #16111 into v1.14.x to build 32-bit Python 3.7 wheels for Windows

Addesses https://github.com/grpc/grpc/issues/15968 (after pushed to PyPI)

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Artifact/package build script modification: merging and invoking full artifact build & distribtests in lieu of PR tests.


Enable WriteCore feature for connectedvmwarevsphere

We need to enable WriteCore feature to connectedvmwarevsphere. Therefore add use-write-core: true and do a regen.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.ConnectedVMwarevSphere


calculate field to null?

I can't figure out the syntax for setting values to null.
I've tried:
fl.calculate(where="CustomerID=168453", calcExpression={"field" : "CompanyName_1", "value" : null})
fl.calculate(where="CustomerID=168453", calcExpression={"field" : "CompanyName_1", "value" : NULL})
fl.calculate(where="CustomerID=168453", calcExpression={"field" : "CompanyName_1", "value" : <Null>})
#all errors as expected

fl.calculate(where="CustomerID=168453", calcExpression={"field" : "CompanyName_1", "value" : 'null'})
fl.calculate(where="CustomerID=168453", calcExpression={"field" : "CompanyName_1", "value" : '<Null>'})
#return string values

fl.calculate(where="CustomerID=168453", calcExpression={"field" : "CompanyName_1", "value" : None})
# {'error': {'message': 'Unable to calculate fields.', 'code': 400, 'details': ['Object reference not set to an instance of an object.']}}

Thanks

I think I solved it.
fl.calculate(where="CustomerID=168453", calcExpression={"field" : "CompanyName_1", "sqlExpression" : "'null'"}, sqlFormat="native") )

Perhaps arcREST would benefit with a sample using calculate variations of "value" and "sqlExpression" with sqlFormat="native" or "standard"


examples/bootkube: Use bootkube image and disable auto-updates

Users no longer need to scp a bootkube binary
Disable auto-updates until kube-apiserver checkpointing is done

@aaronlevy

lgtm


how is this test passing?

Feel like I am missing something obvious, but this line compiles to
eq('\\' + '\\/', RegExp('\\' + '\\/').source);

where eq is a reference to node assert's strictlyEqual (right?). So it could be rewritten as
'\\' + '\\/' === RegExp('\\' + '\\/').source

and when simplified further
"\\/" === "\\\/"

which very clearly is not the same thing. Having gone back through older versions, since 0.9.0 when the test was added, it has always resulted in the same not-equal value.
So... how is that test suite passing?

They are in fact the same thing! \\ is an escape sequence that produces the character \, and both \/ (escaped) and / (not escaped) produce the character /.

hmm. but strictEqual doesn't have any logic for interpreting the strings in order to get the escaped value, right? We are just comparing two strings which, as you can see have, different lengths.
Throwing this together on the live compiler shows the error I am talking about

Oh my bad, I looked at the last line and assumed we were talking about that literal JavaScript expression being true (it is).
The actual answer to your question is that Node 0.10 (the engine on which the Travis CI builds are run) claims that the string value \\/ is the value of new RegExp('\\\\/').source, but later versions and most other JavaScript engines seem to disagree and claim it is the string value \\\/.

This is a mess. Does anyone even use the $ regex flag feature? LiveScript seems to have inherited it from Coco, I don't think it's documented on livescript.net, and it seems objectively bad to have an implementation that no longer agrees with (what I think is?) the latest EcmaScript standard. I would vote for removing it altogether.

ah, I didn't check the node version - thanks so much for the explanation :D
two follow ups

would you like a PR that removes that test since it seems flawed (or updates to the passing value)?
would you like a PR that updates your travis config to use node versions that are still supported?

I personally (as a totally unofficial guy who submits PRs sometimes) would like to see this entire $ flag feature removed (which includes the offending test). I'm planning to submit a PR that does just that. Which Node versions LiveScript ought to support is a Question of Policy, so I have no advice other than submit a PR and see if our sporadically-present BDFL smiles upon it? (If I had to guess, I think he probably will, eventually.)

Okay, I've learned some new things: I see that the $ flag feature is used to decent effect in src/mode-ls.ls, and while the test causing problems here is an instance of re$ != re.source, at least it doesn't violate new RegExp(re$).source == re.source, which seems like the more important invariant. This upgrades the feature in my mind from ‘useless and broken’ to ‘undocumented power feature and slightly confusing on modern platforms’. I'm going to research what EcmaScript actually specifies and see if it's not too much work to nudge this to ‘undocumented power feature that is consistent with modern standards’.


do STRING_TABLE

fixes #51

when strict syntax check is enabled it will be reported by the linter, alternatively https://rules.abaplint.org/forbidden_void_type/ can be used until then


Improve performance by using std::string_view

Change Description
Improve performance by using std::string_view instead of std::string. Replicates the swatanabe commit https://github.com/nksanthosh/eos/commit/88cd197c5eb972b6ebfc91fa8bd234aebb8c5554#diff-56f74710b09c4555a3235a296394adb4 in develop

Change Type
Select ONE

[ ] Documentation

[ ] Stability bug fix

[x] Other

[ ] Other - special case

Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

No performance related changes into release/2.0.x at this point


Possible bug: goog.date.Date#add(interval), goog.date.Date#getTime() and DST

This issue was imported from Closure Library's previous home at http://closure-library.googlecode.com
The link to the original issue is:
https://code.google.com/p/closure-library/issues/detail?id=600

WAI - It correctly increments a full day, even over DST boundaries.


hol: k.8 -> k.10

This also fixes HOL to work with new versions of Poly/ML, which require the --enable-shared configuration option.
Rather against its own spirit, I have run the hol interpreter, but not proven it correct. ;-)

tnx!


docs: client libraries definitions

Issues Addressed
closes #5

These docs were added in the respective repositories. It doesn't need to be merged in this repo.


[Event Request]Application “Tests-General Journal”, Codeunit 138907 "O365 Invoice Payment Test"

[Event Request]Application “Tests-General Journal”, Codeunit 138907 "O365 Invoice Payment Test"
Could you please insert the OnTestInitialize Event at the beginning of the Initialize procedure:

Sorry, wrong test app. Correct is Tests-Invoicing

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


[Bug]: New Bug in 1.4 version

What happened?
After a period of running the program, this message appears :
Can't copy bug so I made a screenshot ..
https://i.ibb.co/gt1sJMy/2021-08-10-16-02-52-Greenshot.png
Enroller
GUI
OS
Windows
Relevant log output
No response
Terms

[X] I am using the latest version available.
[X] I agree to follow this project's Code of Conduct

This is Bug Code :
Traceback (most recent call last):
File "urllib3\connection.py", line 169, in _new_conn
File "urllib3\util\connection.py", line 73, in create_connection
File "socket.py", line 953, in getaddrinfo
socket.gaierror: [Errno 11001] getaddrinfo failed
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "urllib3\connectionpool.py", line 699, in urlopen
File "urllib3\connectionpool.py", line 394, in _make_request
File "urllib3\connection.py", line 234, in request
File "http\client.py", line 1257, in request
File "http\client.py", line 1303, in _send_request
File "http\client.py", line 1252, in endheaders
File "http\client.py", line 1012, in _send_output
File "http\client.py", line 952, in send
File "urllib3\connection.py", line 200, in connect
File "urllib3\connection.py", line 181, in _new_conn
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x00000245E79917C0>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "requests\adapters.py", line 439, in send
File "urllib3\connectionpool.py", line 755, in urlopen
File "urllib3\util\retry.py", line 574, in increment
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='110', port=80): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x00000245E79917C0>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "duce.py", line 685, in main1
File "duce.py", line 515, in auto
File "duce.py", line 299, in get_course_id
File "requests\api.py", line 75, in get
File "requests\api.py", line 61, in request
File "requests\sessions.py", line 542, in request
File "requests\sessions.py", line 655, in send
File "requests\adapters.py", line 516, in send
requests.exceptions.ConnectionError: HTTPConnectionPool(host='110', port=80): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x00000245E79917C0>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))

This is Bug Code :
http://txt.do/tao9v

this is course problem 👍 :
https://www.udemy.com/course/the-art-of-doing-video-game-creation-with-python-and-pygame/

#89

any fix ?


Update vocabulary.md: recommended change to AI definition, per Oxford. Suggested for clarity, conciseness.

There is a merge conflict here before we can merge this PR. Once the conflicts are resolved, then we can merge and close this PR.

There is a merge conflict here before we can merge this PR. Once the conflicts are resolved, then we can merge and close this PR.


kia_uvo - Exception in force update : string indices must be integers

Getting this on attempted update:
Have migrated to Kia Account and has been working fine for a while but no longer working
kia_uvo - Exception in force update : string indices must be integers
Traceback (most recent call last):
  File "/config/custom_components/kia_uvo/__init__.py", line 80, in update
    await vehicle.update()
  File "/config/custom_components/kia_uvo/Vehicle.py", line 41, in update
    self.vehicle_data = await self.hass.async_add_executor_job(self.kia_uvo_api.get_cached_vehicle_status, self.token)
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/kia_uvo/KiaUvoApi.py", line 190, in get_cached_vehicle_status
    return response["resMsg"]["vehicleStatusInfo"]
TypeError: string indices must be integers

I am also getting this error in my log, several times each day.
Debug gives a good hint:
DEBUG (SyncWorker_10) [custom_components.kia_uvo.KiaUvoApi] kia_uvo - get_cached_vehicle_status response {'retCode': 'F', 'resCode': '5031', 'resMsg': 'Unavailable remote control - Service Temporary Unavailable', 'msgId': '***MASKED***'}

approx 50% (ish) of the queries get through ok for me though..
For what it is worth, I will reduce the query i my installation to every 30min and see it the error goes away.

in my setup, update is being executed in every 10 minutes and i have received this error only once in last 2 days.
I will keep this issue open and will track the trend.
Moreover, I agree that we should only process when there is a response with retCode S (assuming/hoping it means successful) :) this will go into improvements bucket :)

I've had to back mine back off to every 30 minutes - I don't know if there is a difference between Android and iOS apps, and calls they might do in the background. I use iOS and use it to change the schedule charging fairly regularly and that would be using the same account details.

I have updated code base to fail silently rather than breaking the data. You can get the latest code base, observe couple of days and share your results.

any update here, anyone getting complete disaster when this had happened. If it is not failing apart, i think we can resolve this. please let me know other way around.

Mine has been running stable now with the following settings:
scan interval:31
force interval: 121
On top of this I do run the occasional manual update as well which also works fine.
So no issues right now for me.


chore: minor improvements to github ci

This PR contains minor tweaks to bring the workflow in-line with standard practice.

[x] remove sudo
[x] add missing apt update
[x] add missing -y flags to apt commands

ah nvm. I confused docker with github runners. Looks like we do need sudo after all :sweat_smile:


fix: make drawbridge-type compile with default feature set

Previously the anyhow crate was only enabled with the server feature enabled, which caused compilation failures when that feature was absent.
Signed-off-by: bstrie<EMAIL_ADDRESS>

@bstrie please apply the following patch to your commit:
diff --git a/Cargo.nix b/Cargo.nix
index 20a5f53..4e3c154 100644
--- a/Cargo.nix
+++ b/Cargo.nix
@@ -801,7 +801,6 @@ in
     registry = "unknown";
     src = fetchCrateLocal (workspaceSrc + "/crates/type");
     features = builtins.concatLists [
-      [ "anyhow" ]
       [ "axum" ]
       [ "default" ]
       [ "headers" ]

Also see #226 - the patch in these situations will now be both uploaded as artifact and printed to the log


DO NOT MERGE: fix for RHEL

@ibuildthecloud @alena1108
This fixes that RHEL issue (https://github.com/rancher/rancher/issues/7769). I don't understand this fix....
@ibuildthecloud Can you please review this?

Steps to test that this actually really works (according to @ibuildthecloud):

Start docker with various storage drivers (overlay, devicemapper)
Start kubelet, and launch a bunch of pods
Restart kubelet
Remove pods
Ensure all pods actually get removed without errors (systemctl status docker.service)


Implemented Add Media API.

Add Media API is completely implemented. This implementation is different from the one I did previously. Main highlights are:

No need to start the cineast server with --server option along with a config file. When a request arrives, provider will be initialized/opened if closed, extraction will take place and then session will be ended so as to write data to ADAMPro.

Instead of starting cineast server with --server config, there must be 4 config files (for image, video, audio, 3d model) in the same directory as cineast.jar. This is done mainly because of three reasons.
i. If there is only one config files, all the exporters need to be specified (ShotThumbNails, AudioWaveformExporter, Model3DThumbnailExporter etc) for all different media types. The problem with this is if say an image is getting processed, and if AudioWaveformExporter is specified, it will process and export the waveform even though it doesn't make any sense for an image.
ii. In case of single config files, only a single set of extractors can be specified for all types even when say LightfieldZernike doesn't make any sense while extracting an image. This doesn't necessary creates any problem except taking some extra time in checking. When using multiple configs, different set of extractors can be specified for different media types.
iii. In case two or more media type uses a same exporter (ex both IMAGE and VIDEO can use ShotThumbNails) then they will be exported to the same directory (which is specified in config). This creates problems when retrieving thumbnails in current client scenario which expects thumbnails of different media types to be in different directories. When using multiple config files, this problem will also be solved.
Also if required, request can specify the extractors and exporters to be used while extraction. This isn't implemented yet as I'm not very sure about it's utility.
The current implementation requires image_extraction_config.json, video_extraction_config.json, audio_extarction_config.json, and 3dmodel_extraction_config.json in the same directory as cineast.jar each having input (for Unique id generator), extractors and exporters block.

Users can upload mutiple files at once of the SAME type (viz IMAGE, VIDEO, AUDIO, MODEL3D) along with the metadata if any. Specifically
i. Request will be of type multipart/form-data.
ii. A header media_type needs to be specified which tells the media type of all the files.
iii. files to be extracted should be uploaded with filename as their key.
iv. A key extract_config should be specified along with the file which will be deserialized to 'ExtractionItemContainer'.
v. In the object section of ExtractionItemContainer, name and path fields should be set to file name and uri can be any valid dummy uri (because of URI validations eg file:///dummy)

Valid objectlocation needs to be specified in api section of cineast.json. The uploaded files will be segregated according to their media types so as to comply with the current client specifications.

As mentioned in our conversation offline, we'll merge this into a gsoc-2018 branch for submission


Deprecating visualizer

The visualizer was intended as a placeholder until we had a proper GUI for creating training data. Thanks to @azazdeaz we now have one, which you can check out here.
With version 0.6 we will remove the visualizer, in favour of using this GUI directly. There will be a separate tool for converting wit/LUIS/api exports to the rasa NLU format, so you'll use it like:
python -m rasa_nlu.convert -d wit_download.json -o rasa_data.json

Where the rasa_data.json will be ready to upload to the web app.
Questions / comments / concerns welcome!

👍

PR is #122


Patch the open_clip/ViT-SO400M-14-SigLIP-384/webli model

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
bug fix

What is the current behavior? (You can also link to an open issue here)
This model errors out with the model.eval() call. The root cause is our torch version is too old (1.12.x)

What is the new behavior (if this is a feature change)?
We remove the model from the registry until we upgrade the torch version

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
YES

Have unit tests been run against this PR? (Has there also been any additional testing?)

Related Python client changes (link commit/PR here)

Related documentation changes (link commit/PR here)

Other information:

Please check if the PR fulfills these requirements

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

Close to avoid unnecessary gh runs

Close to avoid GH runs


Handle: CSS transform -> CSS positioning

Hey, first off, thanks for your hard work on this awesome component!
Our app uses transform: rotate(45deg) to make a diamond-shape handle.
This change allows our style to work. Without it, the transform style applied here overrides what's in the class.
Positioning seems more intuitive, and matches what I've seen in e.g. jQueryUI Slider.
Alternatively:

To specify multiple transforms to a single element, they need to be concatenated.
I could nest a second div inside the slider div. It's simpler though to have one element.

First of all thanks for your kind words :)
I have to say I'm no entirely convinced that this is a good idea.
Basically the reason to use transform is that it should more performant (I use the component myself in a mobile web app).
However it is not at all clear whether this is actually the case (could be that each handle having its own layer adds too much of an overhead). Also, positioning an absolute positioned element should not cause an entire reflow. But basically we don't know until we try out.
Until I can do some experiments I'd like to keep this open.

Ah, makes sense, worth testing.
Let me know if I can help in some way!

Hey, just an update on this.
I tried out applying my rotate(45deg) transform to a second div inside the translated slider element, and the results weren't great. The handle loses some of its sharpness – it stops being square. Looks much crisper when using one position and one transform.
So, just wanted to say that this change still seems worth testing!

This is now part of the master brach, but I didn't use this pr.

Thanks, latest master is working great!

Hey, would you be interested in adding some different CSS examples to the repo and hosting? I'd be happy to put a couple together. One of the great things about this lib is that it's CSS agnostic and it'd be cool to show that off.


Compliance test FlushNIUnspecified() is expecting an error which differs from the gribi.proto file comments

From gribi.proto:
  // network_instance specifies the Network Instance that should be flushed. If
  // the client specifies neither name nor all the server should respond with
  // an error specifying the INVALID_ARGUMENT canonical error code, and the
  // UNSPECIFIED_NETWORK_INSTANCE error code.

However, the FlushNIUnspecified() test is expecting codes.FailedPrecondition.  I believe it should instead expect codes.InvalidArgument based on what gribi.proto says.

Thanks for catching this, @jeremyrandnokia. I'll file a quick PR to update it.

https://github.com/openconfig/gribigo/pull/161

The updated testcase looks good.  Thanks for the fix!


[W6.6g][W11-B3] Kevin Leonardo

PR for LO W6.6g Use Cases
Add use case for Rename tag to Developer Guide, with MSS and extensions

Good work.


How to clean/clear addresses of long lost nvim processes?

I am trying to create a simple bash-script to have neovim-qt work like sublime-text when opening files. I am using neovim-remote for that. However, I would like a way to clean/clear/delete address of nvim processes that no longer exist..
How can I do that?

I'll reopen, if there's something I can act on.


Add separate image with az cli

This PR adds a az cli enabled image based on the latest official az-cli docker image published by Microsoft.
mcr.microsoft.com/azure-cli:2.48.1
I tried to just extend your curent build process, more or less copying the gcp related parts.
New lines were added to the files I touched as requested here
If that's not consistent with the current guidelines I can remove them.

@msamendinger thanks for the contribution 🙏

That's fine :D feel free to force push and we can re-approve.

Should be good to go now @peterdeme @Yantrio


[FUZZ] beaconfuzz_v2 identify a mismatch between clients with attester_slashing

beaconfuzz_v2 just found an attester_slashing that is interpreted differently by eth2 clients:

Lighthouse and Prysm accept and process the file
Nimbus and Teku accept but don't process the file

Info to Reproduce
Download: issue_pat_attester_slashing.zip
Run:
$ unzip issue_pat_attester_slashing.zip
$ cd issue_pat_attester_slashing
$ ../beaconfuzz_v2 debug beacon.ssz attslash.ssz attesterslashing

[+] beaconfuzz_v2
[DEBUG] beaconstate_path = beacon.ssz
[DEBUG] beaconstate length = 2720473
[DEBUG] container_path = debug_file.ssz
[DEBUG] container length = 496
Using z.Allocator with starting ref: c5e0000000000000
[LIGHTHOUSE] SSZ decoding true
[LIGHTHOUSE] Ok(())
[LIGHTHOUSE] Processing true
[PRYSM] Processing true
[NIMBUS] Processing false
[TEKU] Processing false

Your Environment

Fuzzer ran: beaconfuzz_v2
Version/Commit used: a990138210cc412ab6d96b07014e4011d2d6664a
Operating System and version: ubuntu

Lighthouse accepts that attestation because the fuzzer is running with VerifySignatures::False rather than fake_crypto. The difference is that, with fake crypto, verification will attempt to load the pubkeys from the state, whereas with VerifySignatures::False, the pubkeys won't be loaded at all and we don't detect the index out of bounds.
https://github.com/sigp/beacon-fuzz/blob/9404192347e59c448d19fa77cc58c20ca69ab43f/beaconfuzz_v2/libs/lighthouse/src/attester_slashing.rs#L19-L24
^For beacon_fuzz to use fake_crypto would require turning it on at the Cargo.toml, which might mean that you need two fuzz targets or something. I'll leave that design decision up to you. If it's really a hassle, we could consider modding Lighthouse so that it detects the index out of bounds even when VerifySignatures::False is set.
For debugging I added a transition-op command to lcli, but it's not very fleshed out so we shouldn't merge it. Something like that seems like it's planned for eth2diff?
https://github.com/sigp/lighthouse/tree/lcli-op
Compiling that branch with:
cargo install --path lcli --force --locked --features fake_crypto

And then running:
lcli transition-ops issue_pat_attester_slashing/beacon.ssz issue_pat_attester_slashing/attslash.ssz output.ssz

Yields the expected result:
Failed to run lcli: Failed to transition ops: State transition failed: AttesterSlashingInvalid { index: 0, reason: IndexedAttestation1Invalid(SignatureSetError(ValidatorUnknown(68116944363978752))) }

Idk about why Prysm is accepting the slashing, but it might be something similar

Thanks, that lcli feature will indeed be quite handy for eth2diff. This issue looks the same as #61 (also described in detail in the latest beacon fuzz update).
This explains why Prysm accepts this AttesterSlashing:

When BLS signatures are disabled, PublicKeyFromBytes() returns an empty BLS signatures, regardless of the attesting indices provided (therefore not checking for out-of-range attesting indices).


Credit Calculation | View CI Limits |5|

Story:
As an IDIR user, I want to be able to view the carbon intensity limits for the two fuel classes so that I can understand how current and future credits will be calculated.

This card is to build a table in both the back-end and front-end to track and view the carbon intensity limits used in the calculation of credits (section 6 of the Act).
The table can be found in section 11.02 (1) of the Regulation. Screenshot attached.
Instead of having a "2020 and subsequent compliance periods", have a row for each compliance period out to 2030. That is, one row for 2020, one for 2021, ... , one for 2030. The values for 2020 to 2030 are all the same right now, but this allows the Branch to make the necessary changes when reduction targets are set beyond 2020. We should also look to expand the current compliance periods in TFRS to 2030 (currently only have to 2020).

Scenario 1:
GIVEN that I am an IDIR user
AND I am on the Administration tab
WHEN I click on the "Compliance Reporting" sub-tab
THEN I am taken to the Compliance Reporting sub-tab within the Administration tab
AND I can view the CI Limits
Forward looking usage:

We will be using/pulling these values when we implement compliance reporting as they are used in the calculation of credits/debits.
We will want IDIR users to be able to edit these values as they change from time to time.https://trello.com/c/mfCiH2IR/888-credit-calculation-view-ci-limits-5

 Credit Calculation | View CI Limits |5|


Implementation on ABR algorithm

Thank you, Hongzi, for such a great work!
I have tried to use the multi-critic algorithm based on Pensieve structure. However, you mentioned pregenerated input seuqnces are required as the training input. How should I process my input in the ABR environment? Do I need to sample a fized N traces and use N critics to train the RL model? In this case, I think the training data will be constrained in these N traces.
Can you explain how to implement the algo in ABR environment?
Thanks!

Yes, your understanding is correct - we need to sample a fixed set of N traces and create N corresponding critics for them. The implementation would be similar to https://github.com/hongzimao/input_driven_rl_example/blob/master/load_balance_actor_multi_critic_train.py#L219-L225, where we pick a trace (controlled by a random seed) for the environment and map to a fixed critic (indexed by m). The hope for this approach is that the agent can generalize its policy when N gets large (a more scalable approach would be meta-learning and we provide an implementation in #2 if you are interested).
Along this line of idea, a different approach (perhaps easier to implement) is to (1) sample a trace, (2) sample the rollouts with this fixed trace multiple times (you can do it with parallel actors to speed up), (3) compute the baseline using time-average total reward from these rollouts. This approach would be "critic-network-free" but capture the essence of "input-driven baseline". We used this simple approach in this work: https://openreview.net/forum?id=SJlCkwN8iV.

@hongzimao
Thanks for your quick reply.
I am still a little bit confused about how to get the baseline. Now, my input is a trace in batch format. The baseline is calculated by sampling the rewards from the batch and averaging them. Am I right?

To be more specific - it's a "time-"average total reward from the batch. I don't get what you meant by "trace in batch format" though.
What we did was fixing an input trace, run a batch of MDP trajectories (agent interact with the environment with the same external input sequence). Now in this batch, we compute the baseline value b_t at step t using average total reward R_t (R_t = r_t + r_{t+1} + ...) from all trajectories (i.e., average of R_t_traj_1, R_t_traj_2, ...).

Understand! I changed my setting, and the experimental results showed the effectiveness of this approach. Thank! Respect!


More fine-grained mixed-precision configuration

I noticed that haiku intergrate JMP and supports mixed-precision. An example code for ResNet is as follows:
# Assign mixed precision policies to modules. Note that when training in f16
# we keep BatchNorm in  full precision. When training with bf16 you can often
# use bf16 for BatchNorm.
mp_policy = get_policy()
bn_policy = get_bn_policy().with_output_dtype(mp_policy.compute_dtype)
hk.mixed_precision.set_policy(hk.BatchNorm, bn_policy)
hk.mixed_precision.set_policy(hk.nets.ResNet50, mp_policy)

The practice is to keep the computation of BN in full precision. I wonder if there is anapproach for me to do something like configuring a designated layer to some precision, instread of by module. For instance,
ln_policy = jmp.get_policy('p=f16,c=f16,o=f16')
special_policy = jmp.get_policy('p=f32,c=f32,o=f32')
model = get_model() # with 3 linear layers
hk.mixed_precision.set_policy(hk.Linear, ln_policy)
hk.mixed_precision.set_policy(the-last-linear-layer, special_policy)

I wonder if:

haiku supports such functionality?
if no, do you have any suggestions to do a workround?

Hi there, instance level mixed precision with jmp is not built into Haiku, however you can implement this in a few ways. I've added them in this colab notebook: https://colab.research.google.com/gist/tomhennigan/874de0420c55f7bd062f24f7ec6b0e51/instance-level-half-precision.ipynb
Approximately the options are:

Create a subclass and use that for instances you want in a different precision.

class LowPrecisionLinear(hk.Linear):
  pass

half_policy = jmp.get_policy('compute=half')
hk.mixed_precision.set_policy(LowPrecisionLinear, half_policy)

def f(x):
  net = hk.Sequential([
      hk.Linear(300), jnp.tan,
      hk.Linear(100), jnp.tan,
      LowPrecisionLinear(10),
  ])
  return net(x)

Create a wrapper function that applies a specific policy before calling the call method.

def wrap_with_policy(mod: hk.Module, policy: jmp.Policy):
  cls = type(mod)
  @functools.wraps(mod.__call__)
  def wrapper(*args, **kwargs):
    old_policy = hk.mixed_precision.get_policy(hk.Linear)
    hk.mixed_precision.set_policy(cls, policy)
    try:
      return mod(*args, **kwargs)
    finally:
      if old_policy is not None:
        hk.mixed_precision.set_policy(cls, old_policy)
      else:
        hk.mixed_precision.clear_policy(cls)
  return wrapper

half_policy = jmp.get_policy('compute=half')

def f(x):
  net = hk.Sequential([
      hk.Linear(300), jnp.tan,
      hk.Linear(100), jnp.tan,
      wrap_with_policy(hk.Linear(10), half_policy),
  ])
  return net(x)

Thank you for the suggested options. This is of great help to me.


Post display problems

@RhymesWithMecca @jamesma560 check your post- it's not displaying properly.  Perhaps because of the comma in the filename, but see if there are other errors.

@eah13 @jamesma560 New pull request is #512.

@eah13 @jamesma560 New and improved pull request is #518.  See comments there - #512 was also incorrect.

@eah13 @jamesma560 Pull request the fourth (#532) doesn't seem to work either - it's not displaying on the People page.  I can't figure out why.  Can I show you in class on Tuesday?

Sure thing.  I'm pretty sure that it has to do with the lack of a space after the hyphen.

@eah13 @jamesma560 I got this to work on Monday - closing the issue.


Feature Request: select single option

The component is amazing, but when I need to use a simple single select I need to use another component. So, may be a good idea provide the option to this component provide a single option select too.

Duplicate of #417
@jeffsmonteiro I have been thinking about this for a long time but since this requires some fundamental changes in component, I'll try to add this in near future
PRs are welcome

Kind of a hacky way to do it, but you can use useEffect to ensure that there is only one option selected. I did it like this:

// assuming your selected options are stored in the 'selected' state
const [selected, setSelected] = useState([])

useEffect(() => {
    if (selected.length > 1) {
      setSelected([selected[selected.length - 1]])
    }
}, [selected])

closing this so we can track this on other issue


Sonoff M5 switches

I’ve been testing the integration with the Sonoff M5 family of light switches, and have noticed there’s a delay on home assistant for updating the current status of the entity.
Sometimes you’ll switch it on, the light will switch on but home assistant will timeout on waiting for the confirmation, so the state on the GUI will remain as off. That issue is particularly bad for setting up two way switches with automations.
I currently have a TX and M5 running a sync automation, it works perfectly when activating the keys on the TX, it sends its states and the other one updates accordingly, but not the other way around because the states don’t update on home assistant, which is weird because they do on the ewelink app. Anyway, as the M5 is not listed as tested, would like to know if its a limitation to the current version of the integration or if I’m missing something on my end.

This is what I could get from the System Health debug page, the entry shows up every time I flick the switch, wether if it is using the app or Home Assistant.

Hi Sorry to comment on an old thread but is there any change in the no plan to support position on the  M5 switch please? Was thinking of getting some but no HA is a deal breaker


Support custom report filenames via toBeAccessible

It's a good idea to open an issue first for discussion.

[x] Tests pass
[x] Appropriate changes to README are included in PR

I did not know it was recommended to raise a issue for discussion until creating the PR and seeing this template.
This change is to support passing in a custom report filename into the toBeAccessible assertion to allow for multiple axe reports to be generated within a single test; without this change generated reports are continuously overwritten each time you call toBeAccessible (whether that is on the page or a locator).

Looks like linting is not happy with the catch empty arrow function 😢

If I use await expect(page).toBeAccessible({ timeout: 2000, filename }).catch() it no longer fails linting but test doesn't like it. What about if I use a soft expect so that it fails but doesn't fail the test? I.E. await expect.soft(page).toBeAccessible({ timeout: 2000, filename })
The soft failure is a bit odd because it reports the two tests as failures but will not cause an exit code of failure; personally I prefer the test.fail() to indicate we expect it to fail.
What would you prefer?

Ah, found a way to do it using catch so linting and tests are happy, pushing changes now...

Looks like prettier is failing. Can you run:
yarn prettier --write .

Running this command has modified 26 files! Not sure I should commit all of those?

🤞 This hopefully will be the last required change, I resolves prettier issues in 3 or 4 files and now lint prettier and test all seem to be happy - lets hope the build is also happy! 😄

Thanks @mskelton - Do you know when a new version will be released to npm? Assume that it will be version 2.2.0 given it was a minor bump?


When using pre-build commands cross build hangs under Windows

Checklist

[X] I've looked through the issues and pull requests for similar reports

Describe your issue
When I am adding a Cross.toml file with pre-build commands the build hands indefinitely. The identical setup is working when doing the build from Linux, so this seems to be a Windows-specific problem.
What target(s) are you cross-compiling for?
aarch64-unknown-linux-gnu
Which operating system is the host (e.g computer cross is on) running?

[ ] macOS
[X] Windows
[ ] Linux / BSD
[ ] other OS (specify in description)

What architecture is the host?

[X] x86_64 / AMD64
[ ] arm32
[ ] arm64 (including Mac M1)

What container engine is cross using?

[ ] docker
[X] podman
[ ] other container engine (specify in description)

cross version
0.2.5
Example
My Cross.toml file:
# Install libudev into the machine for gilrs and serialport
[target.aarch64-unknown-linux-gnu]
pre-build = [
    "dpkg --add-architecture $CROSS_DEB_ARCH",
    "apt-get update && apt-get install -y pkg-config libudev-dev:$CROSS_DEB_ARCH",
]

Additional information / notes
The console output:
PS I:\myproj> cross build --release -p myapp --target=aarch64-unknown-linux-gnu -v
+ cargo metadata --format-version 1 --filter-platform aarch64-unknown-linux-gnu
+ rustc --print sysroot
+ rustup toolchain list
+ rustup target list --toolchain stable-x86_64-unknown-linux-gnu
+ rustup component list --toolchain stable-x86_64-unknown-linux-gnu
+ "C:\Program Files\RedHat\Podman\podman.exe"
+ "I:\\myproj" "C:\Program Files\RedHat\Podman\podman.exe" build --label 'org.cross-rs.for-cross-target=aarch64-unknown-linux-gnu' --label 'org.cross-rs.workspace_root=I:\myproj' --tag cross-custom-myproj:aarch64-unknown-linux-gnu-207c1-pre-build --build-arg 'CROSS_CMD=dpkg --add-architecture $CROSS_DEB_ARCH
apt-get update && apt-get install -y pkg-config libudev-dev:$CROSS_DEB_ARCH' --build-arg 'CROSS_DEB_ARCH=arm64' --file 'I:\myproj\target\aarch64-unknown-linux-gnu\Dockerfile.aarch64-unknown-linux-gnu-custom' 'I:\myproj'

I doubt this is a cross issue.
Does running
podman build --label 'org.cross-rs.for-cross-target=aarch64-unknown-linux-gnu' --label 'org.cross-rs.workspace_root=I:\myproj' --tag cross-custom-myproj:aarch64-unknown-linux-gnu-207c1-pre-build --build-arg 'CROSS_CMD=ls' --build-arg 'CROSS_DEB_ARCH=arm64' --file 'I:\myproj\target\aarch64-unknown-linux-gnu\Dockerfile.aarch64-unknown-linux-gnu-custom' 'I:\myproj'

work? if it doesn't then you'll need to figure out what's wrong with podman build

basically, copy the command cross is running, be careful with copying --build-arg 'CROSS_CMD=... as it will contain newlines

Use cross installed from main, we switched to build with buildx (and podman should also support it if installed). Buildx doesn't needlessly copy all files and folders.
you can also add a .containerignore file at the root of the workspace that includes target as a ignored folder.

Use cross installed from main

Why not make a new release?

.containerignore is working!

It is good to have a workaround. But it is not an expected behavior, therefore could someone reopen this issue until a fixed version is released, please?

I don't think this warrants reopening, the issue is expected behaviour, just happens to work better in newer code base.
I want to make a new release, but I don't feel like i's ready yet

the issue is expected behaviour

By "expected" I mean expected by users. As a user, I can definitely say that it was not expected. Otherwise, the reporter would not have created this issue, and I wouldn't have been searching for it.

I don't think this warrants reopening

As you wish. But I should warn that the decision to close unfixed issues leads to duplicate issues (not everyone searches for a similar issue among the closed ones before creating a new one), which means wasting time for both reporters and maintainers.

But the issue is fixed/made irrelevant, just not released as a version, but I understand what you mean and appreciate the direction @AndreyMZ !
One thing with that though, we have a checkmark in the issue template that basically asks users to do look through all issues, so hopefully we can mitigate some of that.
We have other completed issues that are only solved on coming 0.3.0 release, my only known praxis of how to handle issues is to close them when a fix is not possible or made available  on the default (or backported) branch. But maybe that is bad maintence? I for one don't mind doing it that way anyway.


Font icon cannot be displayed, still display default icon

Nerd fonts font is already installed, run: Defx - columns = the ICONS: text-indent: filename: type
However, ICONS cannot be displayed in directories

I think you are not running the Defx command correctly. Please give me the exact command that you are running.

我认为您没有正确运行 Defx 命令。请给我您正在运行的确切命令。

I think you are not running the Defx command correctly. Please give me the exact command that you are running.

Thank you, rerun will display the icon


Make error

Hello,
I get an error at make.
When it come to PHKAccessory.cpp compil error:
PHKAccessory.cpp: In function 'void updateValueFromDeviceEnd(characteristics*, int, int, std::string)':
PHKAccessory.cpp:336:114: error: cannot pass objects of non-trivially-copyable type 'std::string {aka class std::basic_string}' through '...'
snprintf(broadcastTemp, 1024, "{"characteristics":[{"aid":%d,"iid":%d,"value":%s}]}", aid, iid, value);
^
makefile:42: recipe for target 'PHKAccessory.o' failed
make: *** [PHKAccessory.o] Error 1
What's wrong ?
Thanks

What platform and compiler version are you using?

Raspberry on raspbian

Clang version?

How to check on raspberry ?

clang -v ?

Clang does not exist....
-bash: clang : commande introuvable
Need to install it ?

How about gcc?
You can check with gcc -version

$ clang -v
Debian clang version 3.0-6.2 (tags/RELEASE_30/final) (based on LLVM 3.0)
Target: arm-unknown-linux-gnueabihf
Thread model: posix

$ gcc --version
gcc (Raspbian 4.8.2-21~rpi3rpi1) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Hello @etwmc I redownloaded the code and found the same issue, I tested with gcc gcc version 4.7.2 20121015 (Red Hat 4.7.2-5) (GCC) and clang version 3.4.2 both are poping the error, is it safe If I make a rollback? and use the previous version?

the problem is with the sprintf method, so I just commented, and the compiler continued

Can you guys try the new push?
My Linux box haven't have gcc 4.8 for a while now

it says PHKAccessory.cpp:609:1: error: stray '\357' in program

yes it compiles now fine, my previous error was a strange char I added, thanx ;)

Works too
Thanks !


error with WUnderground

I am getting a JSON error when trying to use the WUnderground API
[WeatherPlus] Error retrieving weather report and forecast
[WeatherPlus] Error Message: SyntaxError: Unexpected end of JSON input
with the config
    {
        "units": "si",
        "interval": 5,
        "stations": [
            {
                "nameNow": "Bromley",
                "service": "weatherunderground",
                "key": "cbbb61c3b6c64125bb61c3b6c66125ee",
                "stationId": "iBromley15",
                "language": "en",
                "compatibility": "both",
                "conditionCategory": "detailed",
                "now": true,
                "extraHumidity": true,
                "tresholdWindSpeed": 10
            }
        ]
        "platform": "WeatherPlus"
    }

Seeing this as well.

Seeing this as well.
This was caused by my weather station being unplugged and not sending data to weather underground.

My issue was that the weather station was case sensitive, I need to use the name from my profile, not what I use to search in WUnderground.
now working :)

I've just set up the weather station and I can see it's report correctly to Weatherunderground but my HomeBridge is the error message
[WeatherPlus] Error Message: SyntaxError: Unexpected end of JSON input
followed by
[WeatherPlus] Error retrieving weather report and forecast
repeated


the content must be served over HTTPS

Please set HTTPS for the links

I see this error e.g. at
https://exploratoria.github.io/cookbook/models/index.html

@evdem thanks for catching this! I think I got all the links needing update, but let me know if you find any others. Please be aware that pages in this part of the repository were old works in progress and may not function completely.

@evdem thanks for catching this! I think I got all the links needing update, but let me know if you find any others. Please be aware that pages in this part of the repository were old works in progress and may not function completely.

"can't save the file" in Chrome
https://github.com/exploratoria/exploratoria.github.io/tree/master/templates/
<a href="http://exploratoria.github.io/templates/index.html" title="View file as a web page"

"can't save the file" in Chrome
https://github.com/exploratoria/exploratoria.github.io/tree/master/templates/
<a href="http://exploratoria.github.io/templates/index.html" title="View file as a web page"

@evdem with latest Chrome on Windows 10 the save file feature works for me. The file goes automatically to my Downloads folder without the option to choose the location. If this is not the same for you, please be more specific.

@evdem with latest Chrome on Windows 10 the save file feature works for me. The file goes automatically to my Downloads folder without the option to choose the location. If this is not the same for you, please be more specific.


Roll Packages from 407b7da0079e to 6bd59cdb8fb5 (5 revisions)

https://github.com/flutter/packages/compare/407b7da0079e...6bd59cdb8fb5
2023-05-04<EMAIL_ADDRESS>[pigeon][reland]enable treat warnings as errors for swift code in unit test (flutter/packages#3901)
2023-05-04<EMAIL_ADDRESS>[video_player] Fix Android lints (flutter/packages#3886)
2023-05-04<EMAIL_ADDRESS>[quick_actions] Fix Android lint issues (flutter/packages#3885)
2023-05-03<EMAIL_ADDRESS>[camera_platform_interface] [camera] [camera_android] Add NV21 as an image stream format (flutter/packages#3277)
2023-05-03<EMAIL_ADDRESS>Revert "[pigeon]enable treat warning as errors for swift code in unit test" (flutter/packages#3898)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-packages-flutter-autoroll
Please CC flutter-ecosystem<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


A step-by-step guide on setting up KSS documentation for your project

A guide to set up KSS-powered style guide documentation in a {Rails,Sinatra,plain HTML} project would be nice.

Agreed! I would love to see this as well!

Definitely. I'd love more explanations all over. Hopefully I'll have time in the next weekish to put together a website that focuses on the spec + getting started.

I eco this suggestion. I'm very excited of being able to auto document SASS with this gem, but haven't been able to get started as the instructions are not clear on how to install and use.

+1
Can't wait to see some explanations, then start using.

Anyone willing to do a quick and dirty explanation on how to get this up and going at least? Would love this.


About (possibly inefficient) iDMRG sweep schedule function?

If we look at the following function
def get_sweep_schedule(self) in mps_common.py
for the case where bc = 'infinite' (iDMRG), the scheduling seems not working as I expected. For example, for conventional L=2 n=2 case, LP and RP get increased by four sites in every sweep, not two sites. This is not intuitive as for L=4 n=2 case, LP and RP get increased by four sites in every sweep as well.
What is the clear advantage of the current sweep schedule compared to the toy DMRG sweeping method in  (https://github.com/tenpy/tenpy/blob/main/examples/d_dmrg.py)?  This toy DMRG sweeping method does not have the problem I pointed out above for L=2 case, for example.
Of course, this (maybe 'naive') approach has some problems. After the sweep, updated LP[0] and RP[L-1] acquire contributions not only from newly calculated A/B matrices, but also involves guess input B matrix. On the other hand, using the current DMRG sweep schedule, this does not happen.
I wonder whether there is some clear argument to prefer the current sweeping schedule.

I wouldn't really consider this a bug, it's just a slightly different meaning of what we call a "sweep". With L=2,n=2, you increase both the left and right environment by exactly 1 site after each bond update,  alternating between left and right - this is completely the same as in the toy code. The only difference is how many updates to do - in the toy code, we go up to psi.n_bonds - 1 = psi.L -1, while in TeNPy, we go up to psi.L. In other words, in TeNPy, when sweeping right, we continue a little bit further into the next unit cell before turning back sweeping left. It doesn't really matter that much, but it can actually help a little bit to update the bonds at the unit cell boundary (where the environments grow!) more, such that eventually we might even need less overall sweeps.


Fixed/Enabled ElasticSearchCollector tests + Added alias support.

Description
Fixed ElasticSearchCollector tests
Re-enabled ElasticSearchCollector tests
Added support for pushing index metrics by alias.
Update tests
Test Results:
tox  passes
 tox -- -c elasticsearch passes

lgtm


Rerun omega without stereo requirement if initial conf gen failed

[x] Fix #515
[x] Fix #382
[x] Add tests
[ ] Update changelog

If people have an OFFMol with undefined stereo, they should be able to just parameterize it.
I could add a warning for when the stereo requirement is relaxed, but we have enough warnings.

Codecov Report

Merging #517 into master will increase coverage by 0.01%.
The diff coverage is 75%.

Thanks for the comments and typo catch, @jchodera. I've fixed it and this is ready for re-review.
Regarding throwing a warning, I want to move toward a model of "less warnings", since we throw so many that people ignore all of them. When we add paranoid_mode (more likely publication_mode), we could throw this warning. But basically, there shouldn't be a reasonable path for the user to get here with a stereoambiguous molecule without having specified allow_undefined_stereo=True at least once.

Let's just make sure omega is actually generating a large number of conformers with random stereochemistry if this happens.

Good call. The changes proposed in #492 (which will be added in #471) will result in a much higher number of confs being generated, so that should be covered.


Release uefi-0.23.0 and uefi-services-0.20.0

This release is to provide the fix for https://github.com/rust-osdev/uefi-rs/issues/842.

Why not uefi 0.22.1?

The public function's signature changed (https://github.com/rust-osdev/uefi-rs/pull/843/files#diff-566d37cddda511108f02e563520d31d6b2f2c897ef3bbf61ea8a97358f16ae35L1164), so it's a breaking API change.

I think it would also have been fine to yank 0.22 and just release it as 0.22.1. IMHO breaking changes are fine if the release is less than a couple of days old..
But technically, this is also correct.