OIDC Authentication: Disable editing of users' key attribtues

Describe the feature you'd like
A user that authenticated via OIDC is still able to edit name and email address, although these values were initally provided by the authenticating server.
Editing these files should be disabled for OIDC provisioned users. Either automatically or configurable by the instance administrator
Describe the benefits this would bring to existing BookStack users
a user email is considered a key attribute or a constant when this data is provided by an external provider.
User should not have the ability to tamper this data in bookstack.
Can the goal of this request already be achieved via other means?
No
Have you searched for an existing open/closed issue?

[X] I have searched for existing issues and none cover my fundemental request

How long have you been using BookStack?
Not using yet, just scoping
Additional context
No response

Hi @mschaefers,
The email address is only editable by those with the Manage Users permission.
In regards to the user's name, There has not been much previous demand for controlling this field so I'm not sure it'd be worth adding such a feature.


Supported Capabilities

Description
In WindowsDriver there are capabilities, such as "waitForAppLaunch", "newCommandTimeout", that as per documentation are not supported by FlaUI.WebDriver. in particular "newCommandTimeout" would be important when dealing with several drivers running.
Environment
.NET 6 with C#
Appium server version 2.5.1
dotnet-client: Appium.WebDriver 5.0.0-rc.6
Selenium.WebDriver 4.18.1
appium-windows-driver
OS Windows 11
npm 10.5.0
Windows Application
Thank you

@valinprogress I don't really like the ms:waitForAppLaunch capability because it is custom and I am not so sure of the purpose. Why would you want to wait before attaching the session? Can't we use the WebDriver 2 pageLoad timeout to do something similar?

Released support for appium:newCommandTimeout with https://github.com/FlaUI/FlaUI.WebDriver/releases/tag/v0.1.1 now!


[Storage] Prepare Storage for STG 78 GA release

Delete HttpAuthorization from Azure.Storage.Common before releasing.

Address commons in Azure.Storage.Common.csproj before shipping.


dataset input parameters?

@aceilers -- I was wondering wha the "coeff_old" and "scatter_old" parameters are in the Dataset code. They cause my existing code to break :). Are they temporary or should we find a way to incorporate them? Perhaps we could make them optional parameters (like _coeff_old and _scatter_old)?

Hi Anna,
I changed things again this week, because we found a bug… Basically coeff_old are the coefficients from using the old Cannon version, i.e. the original one. They are input parameters as an initial guess for the optimizer for the new version. Give me another week or so and it hopefully works ;)
Best,
Christina

Am 24.03.2017 um 19:47 schrieb Anna Ho<EMAIL_ADDRESS>@aceilers https://github.com/aceilers -- I was wondering wha the "coeff_old" and "scatter_old" parameters are in the Dataset code. They cause my existing code to break :). Are they temporary or should we find a way to incorporate them? Perhaps we could make them optional parameters (like _coeff_old and _scatter_old)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/annayqho/TheCannon/issues/72, or mute the thread https://github.com/notifications/unsubscribe-auth/AT1lwBR4kB0aAgUUnW-Y1S96yT4FOupaks5rpA_OgaJpZM4Moo0z.

Oh OK, great. Just wanted to check, thanks!


Widget tear-down: add a public destroy() method

A jQuery widget should support a method to remove the widget. It's standard to name it destroy().

done


CNC plasma cutter

Hi after trials and tribulations I have managed to set this up with everything working, and I really like its potential, shame about not beig able to use M62 though.
To my question... I have started building a portible CNC plasma cutter, I was initially going to use it with mach 3, but wouldnt mind having a go with this controller.
Has anyone done this yet? if so is there a chance you could give a few pointers? it would be great if I could have a THC with it, even if using using a second linked  arduino?
Any thoughts?
Regards
Tony

Give it a try! Go ahead.

I was hoping for advice?

I was hoping for advice?

Hello, if you use shielded cabling and non HF plasma works great, also try using proma-sd THC


🐛 Bug Report: failing to start backend, top-level-await not enabled

📜 Description
After following the Azure Sites Backend configuration steps and attempting to start the back-end with yarn start-backend I am being met with :
"Error: Module parse failed: The top-level-await experiment is not enabled (set experiments.topLevelAwait: true to enable it)
File was processed with these loaders:

../../node_modules_swc-loader/src/index.js
You may need an additional loader to handle the result of these loaders."

👍 Expected behavior
Run succesfully to be able to go to http://localhost:7007/api/azure/health and see a {"status":"ok"} .
👎 Actual Behavior with Screenshots

I've tried looking for a webpack.config.js file to make the change it's asking but I can't seem to find anything matching what would be required.
👟 Reproduction steps
Followed the Readme file from https://github.com/backstage/backstage/tree/master/plugins/azure-sites-backend
Simply followed the steps from the Readme file.
📃 Provide the context for the Bug.
No response
🖥 Your Environment
If relevant, using node version 16.13.1 and this is being run on a Linux VM.
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No response

I'm not able to reproduce this, are you sure you followed https://github.com/backstage/backstage/tree/master/plugins/azure-sites-backend correctly? You shouldn't end up with any top-level awaits.

As far as I can tell, I have.
-The app-config.yaml has been filled with the required details from azure.
-yarn add --cwd packages/backend @backstage/plugin-azure-sites-backend has been run
-Azure.ts has been filled in

-Index.ts has been filled with

Have you tried installing the plugin in a fresh backstage installation? We are not able to reproduce this currently. You should try to verify if you have any top level await in your existing code.

Looks like there's a closing curly here in the end that might be the issue? 🤞

The curly was the culprit, that was embarrassing.
Thank you kindly.


Use WORKITEM_ROOT instead of CORRELATIONPAYLOAD for helix workloads

Better way of fixing https://github.com/aspnet/AspNetCore/pull/9186, but not certain it will work yet. CORRELATION_PAYLOAD is readonly on these new helix payloads.

Maybe still need to update a few other env variables like DOTNET_CLI_HOME="$HELIX_CORRELATION_PAYLOAD/home"
Looks like its still trying to write to the read only directory
System.IO.IOException: Read-only file system
   at System.IO.FileSystem.CreateDirectory(String fullPath)
   at System.IO.Directory.CreateDirectory(String path)
   at Microsoft.Extensions.EnvironmentAbstractions.DirectoryWrapper.CreateDirectory(String path)
   at Microsoft.DotNet.Configurer.FirstTimeUseNoticeSentinel.CreateIfNotExists()
   at Microsoft.DotNet.Configurer.DotnetFirstTimeUseConfigurer.Configure()
   at Microsoft.DotNet.Cli.Program.ConfigureDotNetForFirstTimeUse(IFirstTimeUseNoticeSentinel firstTimeUseNoticeSentinel, IAspNetCertificateSentinel aspNetCertificateSentinel, IFileSentinel toolPathSentinel, Boolean hasSuperUserAccess, DotnetFirstRunConfiguration dotnetFirstRunConfiguration, IEnvironmentProvider environmentProvider)
   at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, ITelemetry telemetryClient)
   at Microsoft.DotNet.Cli.Program.Main(String[] args)
Running non-flaky tests.

Receiving some bad image pulls (https://github.com/dotnet/core-eng/issues/5883).

Minus the IISExpress failures, this PR is working.


Minimize imports in v0.3

In v0.3 it is planned that we will remove models and molparse from the base imports.

Nevermind... we found the source of this issue and optimized it out in #28. Still something to think on and watch out for.


Crash "Failed to send the command after 3 attempts (Status NoAck)"

Plugin Version: 2.0.0
Platform: Linux
Problem description:
sent following message to node
msg.payload ={node:10,
class: "Unmanaged",
operation: "SetValue",
params: [{commandClass:98,endpoint:0,property:"targetMode"}, 0] // Config Param, Config Value, Value Size
}
to an Assa Abloy (Yale YRD240-ZW. Caused the following crash: (note zwave2-mqtt is my hostname, i'm not using zwave-js2mqtt)
Mar 19 15:27:37 zwave2-mqtt Node-RED[5633]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
Steps to reproduce:
I have not been able to reliably reproduce this... It is intermittent.

If this is intermittent, it sounds as if this is a network work issue.
have you tried healing the network?

Well, yes, but a network issue should never cause nodered to crash. I.e there is a code violation that is causing node-red to crash and restart.  Which in turn creates all sorts of issues. Thought it would help to send the info, as it might help to resolve the problem. I’m guessing a series of things have to align before it dies. This isn’t the first crash but it was the first with a bit of a trace back. I’ve not had this problem till I moved to zwave-js.
Hope that helps.
Sent from my iPad

On Mar 19, 2021, at 5:58 PM, Marcus Davies @.***> wrote:

If this is intermittent, it sounds as if this is a network work issue.
have you tried healing the network?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Ok,
Have tracked down a very similar (if not exact) same report, but in a different host environment.
See https://github.com/zwave-js/node-zwave-js/issues/1101
I thought I was catching these  - obviously not.
Will be fixed in 3.0
Thanks

Fixed with https://github.com/zwave-js/node-red-contrib-zwave-js/commit/0c988919d01686aacb500e57005cca3f02e21436

No problem. Anyway I can help.
Im always unsure where to report stuff when there are multiple authors.  You never know who’s code may be responsible.  Ie Zwave-js project vs the node author.
Aside from submitting them as issues. Do you guys have a preferred way?
Sent from my iPhone

On Mar 20, 2021, at 4:22 AM, Marcus Davies @.***> wrote:

Fixed with 0c98891
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Anyway I can help.

Feel free to give the dev branch a run through (3.0) - which includes the fix  😅
A few changes that may be worth reading through.

You never know who’s code may be responsible

In this instance, the node-red module its-self, I was not awaiting on the promise setValue method of the zwave-js driver, causing it to freak out, when it failed. Now that I await, any error (i.e. a timeout) is passed to the user through the node red module, and more importantly, doesn't kill the process.

Aside from submitting them as issues. Do you guys have a preferred way?

The zwave-js project has issue templates for most things, so raising issues via the normal means, is probably preferred.
though we do require logs if submitting issues specific to the zwave driver (3.0 of this repo supports logging options)
This repo (part of the zwave js umbrella) - has issue templates to use also.
👍

Good to know.
It looked like most of the big reports were submitted using logs for Zwave-js2mqtt. Is that the case.
I’ll give the dev track a try.
I may try using Zwave-js2mqtt to report an issue I’m seeing with my Yale lock being reported as dead. I noticed it has the same problem with Zwave-js2mqtt. And it’s only four feet line of sight from the aeotec Zwave stick.
It always works fine if someone touches the lock. So it only effects my ability to send commands to the lock when it thinks it’s dead.
Must have some issue with sleeping I’m guessing.
Anyway. Thanks for the help. Will let you know the results.
Sent from my iPhone

On Mar 20, 2021, at 1:54 PM, Marcus Davies @.***> wrote:

Anyway I can help.
Feel free to give the dev branch a run through (3.0) - which includes the fix 😅
A few changes that may be worth reading through.
You never know who’s code may be responsible
In this instance, the node-red module its-self, I was not awaiting on the promise setValue method of the zwave-js driver, causing it to freak out, when it failed. Now that I await, any error (i.e. a timeout) is passed to the user through the node red module, and more importantly, doesn't kill the process.
Aside from submitting them as issues. Do you guys have a preferred way?
The zwave-js project has issue templates for most things, so raising issues via the normal means, is probably preferred.
though we do require logs if submitting issues specific to the zwave driver (3.0 of this repo supports logging options)
This repo (part of the zwave js umbrella) - has issue templates to use also.
👍
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Yup, Zwavejs2mqtt is a popular front end to zwave-js, so you will see, a lot of logs generated from it)
the zwave-js org comprises of:
zwave-js (The main zwave stack)
Zwavejs2mqtt (MQTT Front End)
node-red-contrib-zwave-js (Node-Red support)
zwave-js-server (Home Assistant Daemon)
All expose the logging provided by the main stack.

Yup, just installed node-redcontrib-zwave-js#dev ... Nice I see you added
logging... Awesome!
Thanks... Will keep you posted to what I find.. I'll try and be as helpful
as possible. I know what it can be like...
Thanks again.. BTW. Love what you've done so far.. I've been porting over
my zwave interface from openzwave to zwave-js...
Had to back out because zwave-js had some issues with the likes of my
battery Door/Window devices.. It could never learn them when I had my other
20 odd nodes running. They came up fine on openzwave. I concluded it had
something to do with all the CommandClass 50 traffic being generated from
my power bars etc..
So, broke it into two networks for now. One with my Door locks and a couple
of Aeotec ZW096's ... And my other zwave network, with all the different
Window sensors, etc.. Both are using two different Raspberry Pi's. One PI
3, and one pi 4. Both using Aeotec zwave sticks...
It's been interesting seeing some of the differences.. Like my zooz power
bars.. openzwave uses and index of 1 to report the total power being used
by the bar, also if you send CommandClass 37 to the index 1, it turns off
the master for the bar... But zwave-js, seems to get confused.. index one
seems to still report the power for the whole bar, but the commandclass 37
seems to just turn on and off the first switch... They seem to align when
you get to index two. Meaning you loose visibility to the first channel on
the power bar.
I decided to just move back to openzwave for those, instead of trying to
figure out where the problem is... Didn't try that under zwave-js2mqtt...
Also didn't bother to report it until I had more details.. so, pretend I
didn't mention it.. more just an observation at this time... When I feel up
to it, I'll try moving one of the power bars back to zwave-js and collect
some logging info.... but right now my focus is getting my door locks
stable and moving them off the Vera.
Anyway, really awesome stuff.
-Chris
On Sat, Mar 20, 2021 at 3:26 PM Marcus Davies @.***>
wrote:

Yup, Zwavejs2mqtt is a popular front end to zwave-js, so you will see, a
lot of logs generated from it)
the zwave-js org comprises of:
zwave-js (The main zwave stack)
Zwavejs2mqtt (MQTT Front End)
node-red-contrib-zwave-js (Node-Red support)
zwave-js-server (Home Assistant Daemon)
All expose the logging provided by the main stack.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zwave-js/node-red-contrib-zwave-js/issues/29#issuecomment-803465570,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGHZ2HGYE6FW6E72YN6QYMLTEUHGRANCNFSM4ZPUO74A
.

If you're  getting funny things going on, open an issue on the main repo - it will get reacted too pretty quickly.
OR - if your on slack.
https://join.slack.com/t/zwave2mqtt/shared_invite/zt-8ns655f6-d407vtI~KjU~1z11jyaQ9Q
another valuable source, is our supported device DB
https://devices.zwave-js.io/

Going to see what happens... So far since I installed this latest version,
the Yale Doorlock has not reported as Dead.. This is good.... :-)
-Chris
On Sat, Mar 20, 2021 at 4:28 PM Marcus Davies @.***>
wrote:

If you're getting funny things going on, open an issue on the main repo -
it will get reacted too pretty quickly.
OR - if your on slack.
https://join.slack.com/t/zwave2mqtt/shared_invite/zt-8ns655f6-d407vtI~KjU~1z11jyaQ9Q
another valuable source, is our supported device DB
https://devices.zwave-js.io/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zwave-js/node-red-contrib-zwave-js/issues/29#issuecomment-803472571,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGHZ2HBN57AZUGVT3WXEN4LTEUOPNANCNFSM4ZPUO74A
.

Hey Marcus,
Quick question for you... I notice now, whenever I do a commit, my lock
goes from UNKNOWN to DEAD... It stays dead till I go and do somthing with
it.. Like a sleeping node, but I don't think Yale Locks follow the typical
node sleep. since they have to receive lock codes, unlike a sensor that
just reports..
In anycase, looking at the log, it looks like it tries to ping the lock and
gets no reply, hence the DEAD status... Is this something that should be
opened with the zwave-js group, or is this something I bring to yourself.
Here is the output from the LOG. The Yale lock is node 10... And, other
than this, it's working great!
2021-03-22T01:54:24.812Z SERIAL « 0x0110000400060a3202217400000208000088
(18 bytes)
2021-03-22T01:54:24.814Z CNTRLR   [Node 006] [~] [Meter] value[66049]: 0 =>
0.52                    [Endpoint 0]
2021-03-22T01:54:24.815Z SERIAL » [ACK]
(0x06)
2021-03-22T01:54:31.909Z SERIAL « 0x0107001304010a7c98
(9 bytes)
2021-03-22T01:54:31.910Z SERIAL » [ACK]
(0x06)
2021-03-22T01:54:31.916Z DRIVER « [REQ] [SendData]
callback id:     4
transmit status: NoAck
2021-03-22T01:54:31.926Z CNTRLR   [Node 010] Node 10 did not respond after
1 attempts, it is presumed dead
2021-03-22T01:54:31.927Z CNTRLR   [Node 010] The node is dead.
2021-03-22T01:54:31.928Z CNTRLR   All nodes are ready to be used
2021-03-22T01:54:31.933Z CNTRLR   [Node 010] ping failed: Failed to send
the command after 1 attempts (Status No
Ack)
2021-03-22T01:54:32.998Z SERIAL « 0x0110000400060a3202217400000000000082
(18 bytes)
2021-03-22T01:54:33.000Z CNTRLR   [Node 006] [~] [Meter] value[66049]: 0.52
=> 0                    [Endpoint 0]
On Sat, Mar 20, 2021 at 7:27 PM Chris Thierman @.***>
wrote:

Going to see what happens... So far since I installed this latest version,
the Yale Doorlock has not reported as Dead.. This is good.... :-)
-Chris
On Sat, Mar 20, 2021 at 4:28 PM Marcus Davies @.***>
wrote:

If you're getting funny things going on, open an issue on the main repo -
it will get reacted too pretty quickly.
OR - if your on slack.
https://join.slack.com/t/zwave2mqtt/shared_invite/zt-8ns655f6-d407vtI~KjU~1z11jyaQ9Q
another valuable source, is our supported device DB
https://devices.zwave-js.io/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zwave-js/node-red-contrib-zwave-js/issues/29#issuecomment-803472571,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGHZ2HBN57AZUGVT3WXEN4LTEUOPNANCNFSM4ZPUO74A
.

Hey!
So, Battery operated nodes that need to stay a wake, work on a protocol called FLiRS.
FLiRS devices go into a very low powered state, then spring back to life, when a message has been received by them.
FLiRS devices, are very much supported by ZWave JS, I have 2 battery operated alarm keypads, that work perfectly.
With that in mind, Zwave JS 7 went through some major re-work, to speed up things even further.
Before submitting a bug to ZWave JS, I want to know if the network cache file from (V6) is still in use (since you migrated to V7).
Lets investigate....
Send the following, to get a footprint of all your nodes.
attach the output to the debug node, and copy /paste the result here.
{
  payload: {
    class: "Controller",
    operation: "GetNodes"
  }
}

Here are the results:
{"payload":{"node":"Controller","event":"NODE_LIST","timestamp":"2021-03-22T12:53:46.795Z","object":[{"nodeId":1,"status":"Alive","ready":true,"interviewStage":"Complete","isListening":true,"isFrequentListening":false,"canSleep":false,"isRouting":false,"supportedDataRates":[40000],"maxDataRate":40000,"isSecure":false,"protocolVersion":"4.5x
/
@./config/config/devices/0x0086/zw090.json","manufacturer":"AEON
Labs","manufacturerId":134,"label":"ZW090","description":"Z‐Stick Gen5 USB
Controller","devices":[{"productType":1,"productId":90},{"productType":257,"productId":90},{"productType":513,"productId":90}],"firmwareVersion":{"min":"0.0","max":"255.255"},"associations":{},"paramInformation":{"_map":{}},"metadata":{"reset":"Use
this procedure only in the event that the primary controller is missing or
otherwise inoperable.\n\nPress and hold the Action Button on Z-Stick for 20
seconds and then release","manual":"
https://products.z-wavealliance.org/ProductManual/File?folder=&filename=MarketCertificationFiles/1355/Z Stick Gen5 manual 1.pdf"}},"isControllerNode":true},{"nodeId":5,"status":"Alive","ready":true,"interviewStage":"Complete","zwavePlusVersion":1,"zwavePlusNodeType":0,"zwavePlusRoleType":5,"isListening":true,"isFrequentListening":false,"canSleep":false,"isRouting":true,"supportedDataRates":[40000],"maxDataRate":40000,"isSecure":false,"protocolVersion":"4.5x
/
@./config/config/devices/0x0086/zw096.json","manufacturer":"AEON
Labs","manufacturerId":134,"label":"ZW096","description":"Smart Switch
6","devices":[{"productType":3,"productId":96},{"productType":259,"productId":96},{"productType":515,"productId":96},{"productType":7427,"productId":96}],"firmwareVersion":{"min":"0.0","max":"255.255"},"associations":{},"paramInformation":{"_map":{}}},"isControllerNode":false},{"nodeId":6,"status":"Alive","ready":true,"interviewStage":"Complete","zwavePlusVersion":1,"zwavePlusNodeType":0,"zwavePlusRoleType":5,"isListening":true,"isFrequentListening":false,"canSleep":false,"isRouting":true,"supportedDataRates":[40000],"maxDataRate":40000,"isSecure":false,"protocolVersion":"4.5x
/
@./config/config/devices/0x0086/zw096.json","manufacturer":"AEON
Labs","manufacturerId":134,"label":"ZW096","description":"Smart Switch
6","devices":[{"productType":3,"productId":96},{"productType":259,"productId":96},{"productType":515,"productId":96},{"productType":7427,"productId":96}],"firmwareVersion":{"min":"0.0","max":"255.255"},"associations":{},"paramInformation":{"_map":{}}},"isControllerNode":false},{"nodeId":7,"status":"Alive","ready":true,"interviewStage":"Complete","zwavePlusVersion":1,"zwavePlusNodeType":0,"zwavePlusRoleType":5,"isListening":true,"isFrequentListening":false,"canSleep":false,"isRouting":true,"supportedDataRates":[40000,100000],"maxDataRate":100000,"supportsSecurity":false,"isSecure":false,"protocolVersion":"4.5x
/
@./config/config/devices/0x027a/zen25.json","manufacturer":"Zooz","manufacturerId":634,"label":"ZEN25","description":"Double
Plug","devices":[{"productType":40960,"productId":40963}],"firmwareVersion":{"min":"0.0","max":"255.255"},"paramInformation":{"_map":{}}},"isControllerNode":false},{"nodeId":10,"status":"Dead","ready":false,"interviewStage":"Complete","isListening":false,"isFrequentListening":"1000ms","canSleep":false,"isRouting":true,"supportedDataRates":[40000],"maxDataRate":40000,"isSecure":true,"protocolVersion":"4.5x
/
@.***/config/config/devices/0x0129/yrd220.json","manufacturer":"Yale","manufacturerId":297,"label":"YRD220
/ YRD240","description":"Real Living Touchscreen
Deadbolt","devices":[{"productType":2,"productId":0},{"productType":2,"productId":521},{"productType":2,"productId":43520},{"productType":2,"productId":65535},{"productType":8226,"productId":521}],"firmwareVersion":{"min":"0.0","max":"255.255"},"associations":{},"paramInformation":{"_map":{}}},"isControllerNode":false}]},"_msgid":"a0fddc01.81415"}
On Mon, Mar 22, 2021 at 1:53 AM Marcus Davies @.***>
wrote:

Hey!
So, Battery operated nodes that need to stay a wake, work on a protocol
called FLiRS.
FLiRS devices go into a very low powered state, then spring back to life,
when a message has been received by them.
FLiRS devices, are very much supported by ZWave JS, I have 2 battery
operated alarm keypads, that work perfectly.
With that in mind, Zwave JS 7 went through some major re-work, to speed up
things even further.
Before submitting a bug to ZWave JS, I want to know if the network cache
file from (V6) is still in use (since you migrated to V7).
Lets investigate....
Send the following, to get a footprint of all your nodes.
attach the output to the debug node, and copy /paste the result here.
{
payload: {
class: "Controller",
operation: "GetNodes"
}
}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zwave-js/node-red-contrib-zwave-js/issues/29#issuecomment-803846452,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGHZ2HC3J7FT3TSTND6L2Z3TE3ZP3ANCNFSM4ZPUO74A
.

Thought it might be easier to deal with a formatted json file.. so here is
the same result in a file.
On Mon, Mar 22, 2021 at 6:56 AM Chris Thierman @.***>
wrote:

Here are the results:
{"payload":{"node":"Controller","event":"NODE_LIST","timestamp":"2021-03-22T12:53:46.795Z","object":[{"nodeId":1,"status":"Alive","ready":true,"interviewStage":"Complete","isListening":true,"isFrequentListening":false,"canSleep":false,"isRouting":false,"supportedDataRates":[40000],"maxDataRate":40000,"isSecure":false,"protocolVersion":"4.5x
/
@./config/config/devices/0x0086/zw090.json","manufacturer":"AEON
Labs","manufacturerId":134,"label":"ZW090","description":"Z‐Stick Gen5 USB
Controller","devices":[{"productType":1,"productId":90},{"productType":257,"productId":90},{"productType":513,"productId":90}],"firmwareVersion":{"min":"0.0","max":"255.255"},"associations":{},"paramInformation":{"_map":{}},"metadata":{"reset":"Use
this procedure only in the event that the primary controller is missing or
otherwise inoperable.\n\nPress and hold the Action Button on Z-Stick for 20
seconds and then release","manual":"
https://products.z-wavealliance.org/ProductManual/File?folder=&filename=MarketCertificationFiles/1355/Z Stick Gen5 manual 1.pdf"}},"isControllerNode":true},{"nodeId":5,"status":"Alive","ready":true,"interviewStage":"Complete","zwavePlusVersion":1,"zwavePlusNodeType":0,"zwavePlusRoleType":5,"isListening":true,"isFrequentListening":false,"canSleep":false,"isRouting":true,"supportedDataRates":[40000],"maxDataRate":40000,"isSecure":false,"protocolVersion":"4.5x
/
@./config/config/devices/0x0086/zw096.json","manufacturer":"AEON
Labs","manufacturerId":134,"label":"ZW096","description":"Smart Switch
6","devices":[{"productType":3,"productId":96},{"productType":259,"productId":96},{"productType":515,"productId":96},{"productType":7427,"productId":96}],"firmwareVersion":{"min":"0.0","max":"255.255"},"associations":{},"paramInformation":{"_map":{}}},"isControllerNode":false},{"nodeId":6,"status":"Alive","ready":true,"interviewStage":"Complete","zwavePlusVersion":1,"zwavePlusNodeType":0,"zwavePlusRoleType":5,"isListening":true,"isFrequentListening":false,"canSleep":false,"isRouting":true,"supportedDataRates":[40000],"maxDataRate":40000,"isSecure":false,"protocolVersion":"4.5x
/
@./config/config/devices/0x0086/zw096.json","manufacturer":"AEON
Labs","manufacturerId":134,"label":"ZW096","description":"Smart Switch
6","devices":[{"productType":3,"productId":96},{"productType":259,"productId":96},{"productType":515,"productId":96},{"productType":7427,"productId":96}],"firmwareVersion":{"min":"0.0","max":"255.255"},"associations":{},"paramInformation":{"_map":{}}},"isControllerNode":false},{"nodeId":7,"status":"Alive","ready":true,"interviewStage":"Complete","zwavePlusVersion":1,"zwavePlusNodeType":0,"zwavePlusRoleType":5,"isListening":true,"isFrequentListening":false,"canSleep":false,"isRouting":true,"supportedDataRates":[40000,100000],"maxDataRate":100000,"supportsSecurity":false,"isSecure":false,"protocolVersion":"4.5x
/
@./config/config/devices/0x027a/zen25.json","manufacturer":"Zooz","manufacturerId":634,"label":"ZEN25","description":"Double
Plug","devices":[{"productType":40960,"productId":40963}],"firmwareVersion":{"min":"0.0","max":"255.255"},"paramInformation":{"_map":{}}},"isControllerNode":false},{"nodeId":10,"status":"Dead","ready":false,"interviewStage":"Complete","isListening":false,"isFrequentListening":"1000ms","canSleep":false,"isRouting":true,"supportedDataRates":[40000],"maxDataRate":40000,"isSecure":true,"protocolVersion":"4.5x
/
@.***/config/config/devices/0x0129/yrd220.json","manufacturer":"Yale","manufacturerId":297,"label":"YRD220
/ YRD240","description":"Real Living Touchscreen
Deadbolt","devices":[{"productType":2,"productId":0},{"productType":2,"productId":521},{"productType":2,"productId":43520},{"productType":2,"productId":65535},{"productType":8226,"productId":521}],"firmwareVersion":{"min":"0.0","max":"255.255"},"associations":{},"paramInformation":{"_map":{}}},"isControllerNode":false}]},"_msgid":"a0fddc01.81415"}
On Mon, Mar 22, 2021 at 1:53 AM Marcus Davies @.***>
wrote:

Hey!
So, Battery operated nodes that need to stay a wake, work on a protocol
called FLiRS.
FLiRS devices go into a very low powered state, then spring back to life,
when a message has been received by them.
FLiRS devices, are very much supported by ZWave JS, I have 2 battery
operated alarm keypads, that work perfectly.
With that in mind, Zwave JS 7 went through some major re-work, to speed
up things even further.
Before submitting a bug to ZWave JS, I want to know if the network cache
file from (V6) is still in use (since you migrated to V7).
Lets investigate....
Send the following, to get a footprint of all your nodes.
attach the output to the debug node, and copy /paste the result here.
{
payload: {
class: "Controller",
operation: "GetNodes"
}
}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zwave-js/node-red-contrib-zwave-js/issues/29#issuecomment-803846452,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGHZ2HC3J7FT3TSTND6L2Z3TE3ZP3ANCNFSM4ZPUO74A
.

So, the bits I wanted to check where.
"interviewStage": "Complete",
"isFrequentListening": "1000ms"

This tells us that, ZWave JS, knows it's a FLiRS device (1000ms wake up frequency)
This really leaves only 2 possibilities.

Network issues, but then you mentioned you can interact with it, and send it commands - so that doesn't make sense.
The device does not follow specification  - this is a real possibility.
Z Wave JS has been built to follow spec, but some devices do not follow specification (when they should be).
ZWave JS does support providing compatibility flags for non compliance devices

One last thing we can try (which will retrigger an interview on your network)

Kill node-red (therefore the driver).
Delete the folder /%home%/.node-red/zwave-j-cache
Start node-red
Allow ~4-5 minutes for your devices to be interviewed (providing they are not sleeping)
Check if all devices have been interviewed (GetNodes to check the status)
Heal Network (connect output  to debug), as it will tell you when its complete

{
  payload: {
    class: "Controller",
    operation: "StartHealNetwork"
  }
}

Once healed, see if anything is different (or now behaving correctly),
if not, and it is still being reported as dead - then it may be worth reporting it as a bug.

Well.. So far so good. I did all of that at 8am my time today. And it's
3:27pm and it has not reported the node as DEAD. Though the interview
process was painful as it kept reporting the node as dead, so I would go
and unlock or lock the lock manually which would cause it to continue the
interview process till it got through all 100 User codes, and then
everything was good.
Thanks for your help.
-Chris
On Mon, Mar 22, 2021 at 7:35 AM Marcus Davies @.***>
wrote:

So, the bits I wanted to check where.
"interviewStage": "Complete",
"isFrequentListening": "1000ms"
This tells us that, ZWave JS, knows it's a FLiRS device (1000ms wake up
frequency)
This really leaves only 2 possibilities.

Network issues, but then you mentioned you can interact with it, and
send it commands - so that doesn't make sense.
The device does not follow specification - this is a real
possibility.
Z Wave JS has been built to follow spec, but some devices do not
follow specification (when they should be).
ZWave JS does support providing compatibility flags for non compliance
devices

One last thing we can try (which will retrigger an interview on your
network)

Kill node-red (therefore the driver).
Delete the folder /%home%/.node-red/zwave-j-cache
Start node-red
Allow ~4-5 minutes for your devices to be interviewed (providing
they are not sleeping)
Check if all devices have been interviewed (GetNodes to check the
status)
Heal Network (connect output to debug), as it will tell you when its
complete

{
payload: {
class: "Controller",
operation: "StartHealNetwork"
}
}
Once healed, see if anything is different (or now behaving correctly),
if not, and it is still being reported as dead - then it may be worth
reporting it as a bug.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zwave-js/node-red-contrib-zwave-js/issues/29#issuecomment-804065959,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGHZ2HBE4MUFOL5CZCGSCQLTE5BS3ANCNFSM4ZPUO74A
.

Nuts. I shouldn't have sent that... As soon as I did, I did a deploy in
node red. And as soon as I did, it went to status UNKNOWN, and then DEAD.
Is there a way for me to force the zwave controller to treat the node as
awake? ie, allow we to send a command to it.. cause, it seems to respond
fine if I don't do a deploy.
I can live with it as is, till someone else reports the problem. Since I
know exactly what I need to do to fix, since I just have to get the device
to send something to the zwave controller to make it think it's ALIVE
again. Then it seems stable till the next deploy.
On Mon, Mar 22, 2021 at 3:29 PM Chris Thierman @.***>
wrote:

Well.. So far so good. I did all of that at 8am my time today. And it's
3:27pm and it has not reported the node as DEAD. Though the interview
process was painful as it kept reporting the node as dead, so I would go
and unlock or lock the lock manually which would cause it to continue the
interview process till it got through all 100 User codes, and then
everything was good.
Thanks for your help.
-Chris
On Mon, Mar 22, 2021 at 7:35 AM Marcus Davies @.***>
wrote:

So, the bits I wanted to check where.
"interviewStage": "Complete",
"isFrequentListening": "1000ms"
This tells us that, ZWave JS, knows it's a FLiRS device (1000ms wake up
frequency)
This really leaves only 2 possibilities.

Network issues, but then you mentioned you can interact with it,
and send it commands - so that doesn't make sense.
The device does not follow specification - this is a real
possibility.
Z Wave JS has been built to follow spec, but some devices do not
follow specification (when they should be).
ZWave JS does support providing compatibility flags for non
compliance devices

One last thing we can try (which will retrigger an interview on your
network)

Kill node-red (therefore the driver).
Delete the folder /%home%/.node-red/zwave-j-cache
Start node-red
Allow ~4-5 minutes for your devices to be interviewed (providing
they are not sleeping)
Check if all devices have been interviewed (GetNodes to check the
status)
Heal Network (connect output to debug), as it will tell you when
its complete

{
payload: {
class: "Controller",
operation: "StartHealNetwork"
}
}
Once healed, see if anything is different (or now behaving correctly),
if not, and it is still being reported as dead - then it may be worth
reporting it as a bug.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zwave-js/node-red-contrib-zwave-js/issues/29#issuecomment-804065959,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGHZ2HBE4MUFOL5CZCGSCQLTE5BS3ANCNFSM4ZPUO74A
.

Then it seems stable till the next deploy.

This makes sense, as during driver start up, it will ping FLiRS devices, to ensure they are not dead (my alarm keypad LED flickers during deploy) as it has a setting to show activity on the panel
This does sound like the device does not respond to pings however (which is a breach in zwave specification).
I'm not aware of being able to force its status to alive within the driver.
One way potentially, is get the device to send something (so it becomes alive).
THEN
See if there is a config parameter to change the battery report interval, and set it to a shorter time.
check the database to see if there is a param OR the user manual, if one does exist (but isn't in the database, we can add it).
https://devices.zwave-js.io/
As for the device, its self it may be a firmware bug (might be worth checking if there is an update).

Another thought.
You could change the deploy mode, to only deploy changed nodes - so if the zwave node its self, doesn't change, it will hold its state (and not be restarted).

Gosh.... I hadn't noticed that change.... And it looks like that was as
long ago as 1.0.0... Guess I just never look at the menus anymore... sigh..
Thanks.. I'll give that a try moving forward.
So, looked for new firmware, sadly Yale/ASSA Abloy doesn't appear to have
released any new firmware for the YRD220/YRD240 at any time that I can
find.... Looked through the website db, and looked at ASSA ABLOYs Z-wave
Plus System integrators Guide and doesn't look like there are any published
settings to effect anything that looks like it might effectively change
it's behaviour... With respect to checking in..
Interestingly though, I had this lock paired with my VERAPLUS system, and
it never had this problem... So makes me wonder if they had info that maybe
isn't published with respect to a way to ping the device that it responds
to... Or a setting to make the device check in once in a while.
In anycase, I'll just live with it for now... Not the worst thing, since I
know how to work around it...
I have another lock I plan to migrate, a schlage lock, but I first have to
port some of my logic off the vera to node-red. Most of it all was ported
when I migrated the Yale lock to node-red using your zwave-js module, but
there are a few things left to move.
Thanks for the help. Had moved most of my zwave devices off the Vera to
openzwave, but found the locks just didn't port well, especially as a
security device. So I moved them back to theVeraPlus till I had another
solution.
Then with the work being done on zwave-js and how much faster/more reliable
it is... I'm slowly moving what I can to zwave-js. But I found the chatty
nature of all these power devices, appears to leave them hogging all the
zwave bandwidth.
But maybe that all got fixed with 7.0...I have all the zwave interaction
being managed by their own Raspberry Pi's which use the MQTT bus to send
reports and receive commands from the central node-red brain running on an
intel NUC.. Moving things is reasonably easy once I've written the basic
handlers to get the messages into a standardized MQTT message....
It's been fun.. I've integrated ISY Devices, HUE devices, my Vista Alarm
panel, Lutron devices, zwave of course, and Energy Curb power reports, plus
some weather station data. Each technology has it's own Raspberry PI
dedicated to it, running Node-red, which posts data onto the MQTT bus
allowing anything else to subscribe, and action. But 98% of the actions are
all on the central brain...
anyway.. This is great stuff again.. Love what you guys have done... And
thanks again for the help... I'll try and help out where I can...
-Chris
On Mon, Mar 22, 2021 at 4:40 PM Marcus Davies @.***>
wrote:

Another thought.
You could change the deploy mode, to only deploy changed nodes - so if the
zwave node its self, doesn't change, it will hold its state (and not be
restarted).
[image: image]
https://user-images.githubusercontent.com/55892693/112067154-81c11200-8b5f-11eb-9be9-b320e94ef0cd.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zwave-js/node-red-contrib-zwave-js/issues/29#issuecomment-804442845,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGHZ2HAMFF4E3HHYDM26EBLTE7BNZANCNFSM4ZPUO74A
.

OMG, I am so embarrassed... I'm pretty sure that has been there since
before node-red 1.0.0. I think I tried to use it once, but didn't realize
you had to hit deploy after... So, I've been doing a full deploy ever
since... I have so many nodes talking to so many different devices on my
main node, each time doing a reload before.. This makes life so much
easier... Again, I'm so embarrassed that I didn't see that... Thanks
again... Guess it pays to ask questions.. lol
-Chris
On Mon, Mar 22, 2021 at 4:40 PM Marcus Davies @.***>
wrote:

Another thought.
You could change the deploy mode, to only deploy changed nodes - so if the
zwave node its self, doesn't change, it will hold its state (and not be
restarted).
[image: image]
https://user-images.githubusercontent.com/55892693/112067154-81c11200-8b5f-11eb-9be9-b320e94ef0cd.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zwave-js/node-red-contrib-zwave-js/issues/29#issuecomment-804442845,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGHZ2HAMFF4E3HHYDM26EBLTE7BNZANCNFSM4ZPUO74A
.

3.0 released


Internet sharing works only with PC but it does not work with my Phone (lumia 520)

I created a new access point in the following way
create_ap wlan0mon wlan0mon Name 12345678
But when I checked my PC's IP (<IP_ADDRESS>) and gateway (<IP_ADDRESS>) but not with my Phone
IP (<IP_ADDRESS>) and gateway (<IP_ADDRESS>).
Is there any problem with dhcp I guess or st else?
My ISP uses 802.1x authentication. I think this would useful.
I run kali linux 2016.1.

Never mind, I fixed it.


[REQUEST] Please add support for abbreviatons

Please add support for abbreviations as explained in the Markdown Extra proposal.
*[ACRONYM]: Tooltip text

Pandoc and similar renderers do include the tag, while Github does not.
I think it would be a valuable addition...
Regards
Merlin

Close it. We have abbr plugin now.


iCloud authentication issue since 0.94.x

Home Assistant release with the issue:

Last working Home Assistant release (if known):
Hassio 0.93.2
Operating environment (Hass.io/Docker/Windows/etc.):

Component/platform:

Description of problem:
Since 0.94.x Im getting this error in the log continuously:
Since the upgrade to 94.x) I get this error multiple times in the log:
Error logging into iCloud Service: (‘Invalid email/password combination.’, PyiCloudAPIResponseError(‘Failed to validate the credentials from cookie’))

However the username/password and the device tracker config have not changed. I tried deleting the icloud folder and restarting HA multiple times.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
device_tracker.yaml

- platform: icloud
  username<EMAIL_ADDRESS>  password: my@password%here
  account_name: iCloud-Michel

Just wanted to add that I am having the exact same issue; so it isn't a singularity.

Same issue here

I have the same issue

Confirmed here as well.  0.94.1

Same here. Also complains that it failed to validate the credentials from the cookie.

+1

However I just rolled back to 0.93.2 and I see the same errors in the log, think it just coincidence with the release of the newer version

I have rolled back to 0.93.2, 0.93.0 & 0.92.0 and am experiencing the same issue with icloud3. I have deleted the config/icloud account which contains the cookies (I believe) and they are not recreated when requesting authorization. The code that does the authorization and maintains the coookies is in pyicloud.py.
In 0.94.0, the DeviceScanner code was moved from homeassistant.components.device_tracker to homeassistant.components.device_tracker.legacy.
My complete error message in the log file for device_tracker.icloud (not icloud3)is:
2019-06-11 14:53:57 INFO (SyncWorker_9) [pyicloud.base] Authenticating as<EMAIL_ADDRESS>2019-06-11 14:53:57 ERROR (SyncWorker_9) [pyicloud.base.http] Failed to validate the credentials from cookie
2019-06-11 14:53:57 ERROR (SyncWorker_9) [homeassistant.components.icloud.device_tracker] Error logging into iCloud Service: ('Invalid email/password combination.', PyiCloudAPIResponseError('Failed to validate the credentials from cookie'))
2019-06-11 14:53:57 ERROR (SyncWorker_9) [homeassistant.components.icloud.device_tracker] No ICLOUDTRACKERS added
2019-06-11 14:53:57 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform legacy

I don't have home-assistant running. But I'm using PyIcloud. That is causing the problem. And I guess due to a change on Apple side #noconfirmation

Same issue here

Confirming the issue is also present with 0.93.2.

+1

Reported here: https://github.com/picklepete/pyicloud/issues/206

FYI - looks like somebody has solved this by grafting on another Python module and replacing pyicloud's auth procedure: https://github.com/PeterHedley94/pyicloud/commit/6bf11c87c784fa9b0f94318ea845e441b0937cf5

I've tested the modifications made above (there is a difference in variable names which I solved with my own fork: https://github.com/joelmoses/pyicloud
It works, partially. It initiates an authentication process which is picked up properly by HA, and it stores the cookies; however, it pops constant re-authentication 2FA prompts whenever it goes on a device discovery; it appears that the hack doesn't try to reuse prior tokens.
But the important part is that Apple didn't completely shut down 2FA integration, and the underlying discovery still works, albeit prompting constantly. :)

HI All,
i am using build by @viable-harman
https://github.com/viable-hartman/InflatableDonkey/tree/TwoFAHacky for ios 9 icloud backup but i am getting below error could you please help me out why this is coming
" Exception in thread "main" org.apache.http.client.HttpResponseException: Misdirected Request: {"success":false,"error":"Failed to validate the credentials from cookie"}"
HTTP/1.1 421 Misdirected Request [Server: AppleHttpServer/70a91026, Date: Wed, 12 Jun 2019 02:26:45 GMT,

I'm having the same issue

the same issue! :/

Same here, same logs.

add me to the list. also having the same issue

In case more validation is needed, I’m seeing the exact thing things.

Same issue

Like. However, this solution still works and I'm in the process of switching over to it:
https://community.home-assistant.io/t/get-ha-to-ask-your-iphone-where-it-is-and-put-info-in-mqtt-owntrack-device-tracker/15507

I followed the above recommendation from CWGSM3V0 except I used the second setup.  The first didn't work for me.  Then I used mqtt_json device tracker.  I setup a script and it works just like the icloud setup did; except it doesn't get associated devices.  You have to request each device per account separately.  If you need help on this let me know.

I found an iCloud interface called findi that is a python port of a php  script that someone said was still working. I just forked it and finally got it to import into my iCloud3 custom component. I ran into a library issue where it is using both urllib and urllib2 for some error handling. Urllib2 is a python 2 library that was superceded by urllib (according to google). I’ll spend more time with it tomorrow but welcome any assistance/comments since I’m not sure what I am doing and just flapping around hoping something will work.

confirmed.. Brand new build and still seeing this issue...

I am having the exact same issue. Tried removing the icloud component and adding it back, only this time it did not ask me for the 2 factor authentication code to be entered.

+1 same issue here

Same here

Please only post if you have new information to provide. Don't post messages like "+1", "Same here", etc. If you want to show that you're affected the proper way to do that is to react to the top post with :+1: . Then click the subscribe button in the top right bar to be notified of updates.

@joelmoses I’ve forked pyicloud after reviewing some other code (findi.py and others). All of the code Ive looked at is old and most do not address 2fa at all. Have you made any more progress trying to figure out what needs to be done to get pyicloud working again that I can have? I’ve read your comments and approach and want to see if we can all get it working again. My email address is<EMAIL_ADDRESS>if you prefer direct contact.

@gcobb321 Just wanted to chime in and say I've now been made aware of the iCloud breakage, sorry to hear about that. You may want to do as little work to get it working again as possible because I would expect that Apple will make some major changes to the APIs around the time that iOS 13 launches if all the rumors of Apple making their own Tile competitor come true. Furthermore, the new "Find My" stuff isn't even working reliably yet in the latest iOS 13 beta, and they've noted as such in the release notes, so I'd also expect some short term API breakage. You may want to wait to do any work really until that warning is gone from the iOS 13 beta release notes.
As always, let me know if I can provide any more assistance.

@robbiet480 It really did mess everything up. Kinda shut down a years worth of work
One thought comes to mind and that is to not have to access the iCloud account at all. If there was a way that a special type of notification message could be sent to the phones/devices that would then trigger a background fetch transaction.. it’s like querying the device for location/status information. The HA components could then pick up the device data. It could be coded in such a way that I, or any component would send it, and you would send the info to HA and then throw the transaction away. It could probably be done using the existing framework without making major changes anywhere.
Your thoughts?

The problem is that those kind of background fetch notifications are not reliable. They can fail for any number of reasons, almost all of them outside of my control. We do already have the request_location_update notification for this purpose though.

Any news about a fix for this problem?

ICloud3 now supports device tracking using find my friends where you set up a non-2fa iCloud account and tie the devices you want to track (2fa accounts) to it as contacts (first name & email address) in the non-2fa account. It’s in the final beta stage and would have been released but I’m out of town until mid-August.
Go here for iCloud3 info.
Go here for iCloud3 v1.1.0 beta 7.

What about non iCloud3 for a built in iCloud integration ? Sorry guys, but some people just want something easy to use, configure and install :sweat_smile:
But sure @gcobb321, this is a good idea, sound like the Google Maps component actually.
Actually, that would be perfect to use an app specific password to use iCloud instead of 2FA (how to : https://support.apple.com/en-us/HT204397), so it can be revoke at any time in the AppleID account page (https://appleid.apple.com/#!&page=signin).
I've see your work @joelmoses, do you think it's possible to make sometging like that ?

@Quentame No, it's not possible to do it using the ASP. The bulk of the "Find" infrastructure isn't compatible with App-Specific Password. I've tried. It'll work for things like contact lists, reminders, mail, and calendars, but not for the service the iCloud helper depends on. I suppose that's for security's sake - after all, you can wipe a device with the service in question.
I think in the interim, what @gcobb321 has put together is probably the best solution. I think it is possible to add the HSV+2FA functionality directly to the original iCloud helper but I'm hesitant to do it right now. Here's the reason:
Apple is about to release iOS v13.0, and, with it, there are major changes coming for the "Find" infrastructure. The "Find My Friends" stuff and the "Find My iPhone" stuff are merging together, and alongside that there will likely be big changes within the API - and possibly in the structure of the signon. I think it's best to wait to see how the changes are going to pan out first.

This has suddenly started working again for me on 0.97.1. Not sure when it started working as I've had it commented out for a while.

I've noticed yesterday that it was working too, I was very suprised !
But for how long ? iOS 13 isn't released yet (planned around end september)

Actually working from Friday 16th of August at 8:30AM (Paris time)
So, should we close the issue or wait until iOS 13 release ? That is the question :smiley:

Hmm. Browsing the source suggests that nothing has really changed in the 0.97.1 release that would have affected the service positively or negatively. Is it continuing to work for you? That is, it hasn't suddenly started prompting for reauthentication?

Yes it did prompt for re-authentication and is still working for the moment. It took 2 attempts to authenticate.

Location services works for me, and I dont see
Error logging into iCloud Service: (‘Invalid email/password combination.’, PyiCloudAPIResponseError(‘Failed to validate the credentials from cookie’))
in the log. Some 0.97'ish version seems to have fixed it

I also can confirm it is working again for me to in 0.97.2, not sure it was the HA update that fixed it, could also be Apple changed something?

It must be a change on the Apple side. There was nothing changed in the component code that would have fixed this, nor in the linked project "pyicloud".

Confirmed that it appears to be working again.


Speed up token value to name lookup

Grammar test suite sped up from 1.2 seconds to 1.1 seconds.
This went from O(n) (loop over (around half of) 183 constants) to O(1) (hash lookup)

@TysonAndre,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Sure. Thanks!


Loosen oauth2client lower bound for Python

FYI @jonparrott and @dhermes

Current coverage is 91.23% (diff: 100%)

Merging #140 into master will not change coverage

@@             master       #140   diff @@
==========================================
  Files             3          3
  Lines           719        719
  Methods         150        150
  Messages          0          0
  Branches        116        116
==========================================
  Hits            656        656
  Misses           63         63
  Partials          0          0

Powered by Codecov. Last update cd4b7f3...f8762ad

@dhermes Done.

@bjwatson SG.

What was the context behind this change? I see that google-cloud-python is now on version 3: https://github.com/GoogleCloudPlatform/google-cloud-python/commit/28a6004796495329bb8c02fa400aec39e2bc8db2#diff-6512dd83a1839f99da393055ac54c10b

@geigerj We're only on 3.0.0 because google-gax is

@geigerj See @jonparrott's comment for more context.

@geigerj I just pushed a version bump that I used this morning. I'm going to assume it's okay and merge, rather than waste your time with extra reviews.


Fix empty icon in top blocked pills

Reviewer: @andrey-p

Description:
We check whether a tracker is part of a major network in order to know when to show the generic pill.
Oath is part of the major networks but doesn't have an icon yet. Added a special case until we can add the icon for it.
Steps to test this PR:

(optional) Mock Oath being a top tracker network in the code
Build and reload extension
If you didn't do step 1, load 30 sites of which most have third party Oath trackers
Top blocked pills should show up - Oath will have the generic icon

Automated tests:

[ ] Unit tests
[ ] Integration tests

Reviewer Checklist:

[ ] Ensure the PR solves the problem
[ ] Review every line of code
[ ] Ensure the PR does no harm by testing the changes thoroughly
[ ] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR Author Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications

:+1:


Decide whether to automate Voice Chat channel naming ahead of matches

Description of Problem:
When a match is upcoming, it would be ideal if the bot renamed an available Voice Chat (VC) channel for that match, so that the admins don't have to manage this manually.
When that match is over, it would be ideal if the bot were to rename the VC channel back to something generic (e.g. unused-1), so that the admins (and the bot, perhaps) can quickly determine which VC channels are in use vs those that aren't.
Complications

Determining a descriptive but short name for the VC channel may be difficult to automate.  It may be that we need a map of full-team-name to abbreviated name will be necessary (e.g. "Manchester United" -> "ManU", "Sheffield United F.C." -> "Sheffield"), so that the VC chat can be called something like "ManU vs Sheffield".  Given the massive number of team names worldwide, a fallback mechanism that attempts to reasonably shorten team names will also be needed (e.g. take the first word of the name? Take first letter of each word in the name?  Take N characters from the name? Take at least N letters, then stop at the next word break or at M letters if no word break is reached?).

There are many instances where there are more matches running concurrently than there are VC channels, so the bot would need some rule in order to determine which ones are the most important to assign to the (limited) VC channels.

Determining when a match is over (in order to rename it back to something generic) is quite tricky - either the football-data.org match API would need to be polled (which raises the risk of quota violations), or a hardcoded time limit on matches (e.g. 2.5 hours) would need to be chosen.

Duplicate of #79.


Visual Bug on Course Results Page

When the window is narrow, the icons on the course results page render outside of their buttons. We should make them stack on top of the text, or disappear, or truncate the text.

I feel like if we remove the icon on smaller screen sizes, that should be good.
Maybe we should also rename "Prerequisites" to "Prereqs"?

I'll take this one for the fellowship task!

Closing since fix merged


compose: Redesign the  arrow between stream and topic.

The icon is now bigger, slimmer in stroke width and has less horizontal spacing around it.
Fixes: part of #28792.
Screenshots and screen captures:
Light Mode
Before:

After:

Demo Design:

Dark Mode:
Before:

After:

Demo Design:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Thanks! @karlstolley could you please review this one?

For design changes (this one, #29397, etc.), it would be great to have equivalent before/after screenshots, in both light and dark theme. Take a look at @karlstolley 's PRs for some examples.

@alya @karlstolley Thanks for the pointers, will keep them in mind now!
Have made the color a variable, and added screenshots for light mode too to the PR description

Looks nice to me in manual testing!

lgtm, merged, thanks @N-Shar-ma!


"Milcoiu " , "Căzănești" , "Ciutești " , "Izbășești " , "Șuricaru " , "Tepșenari" are listed in the drop-down menu

The villages are listed in the drop-down menu alongside its corresponding county and city, according to the law
Preconditions : the  website is up and runing. After every step delete the text you typed from the search bar.

Step 1
Write in the search bar "Milcoiu "

Expected results
The location appears in the drop-down menu as "Sat Milcoiu , VÂLCEA (Milcoiu)"

Step 2
Write in the search bar "Căzănești"

Expected results
The location appears in the drop-down menu as "Sat Căzănești, VÂLCEA (Milcoiu)"

Step 3
Write in the search bar "Ciutești "

Expected results
The location appears in the drop-down menu as "Sat Ciutești , VÂLCEA (Milcoiu)"

Step 4
Write in the search bar "Izbășești "

Expected results
The location appears in the drop-down menu as "Sat Izbășești , VÂLCEA (Milcoiu)"

Step 5
Write in the search bar "Șuricaru  "

Expected results
The location appears in the drop-down menu as "Sat Șuricaru , VÂLCEA (Milcoiu)"

Step 6
Write in the search bar "Tepșenari"

Expected results
The location appears in the drop-down menu as "Sat Tepșenari, VÂLCEA (Milcoiu)"


rebar deps error changing to yaws-1.92

Upgrading from 1.90 to 1.91 works fine, but attempting to upgrade the rebar.config dependencies to refer to 1.92 results in the following rebar error:
Pulling yaws from {git,"git://github.com/klacke/yaws.git",{tag,"yaws-1.92"}}
Cloning into yaws...
ERROR: 'get-deps' failed while processing /Users/jay/Gitdk/dk_yaws: {'EXIT',{badarg,[{re,run,
[{cmd,"sed -ne '1,/^YAWS_VSN=/s/^YAWS_VSN=//p' vsn.mk 2>/dev/null"},
".*",
[{capture,none}]]},
{rebar_deps,is_app_available,3},
{rebar_deps,use_source,2},
{rebar_deps,'-get-deps/2-lc$^0/1-0-',1},
{rebar_deps,'-get-deps/2-lc$^0/1-0-',1},
{rebar_deps,'get-deps',2},
{rebar_core,run_modules,4},
{rebar_core,execute,4}]}}
Recovering from this error requires a manual 'rm -rf deps/*' before an earlier version can be made to work.
Use https://github.com/duomark/dk_yaws/blob/master/rebar.config as an example config, and try changing to 1.90 and back to 1.91. Then change to 1.92 to see the error.

Erlang R14B03 (erts-5.8.4) [source] [64-bit] [smp:8:8] [rq:8] [async-threads:0] [hipe] [kernel-poll:false]

How new is the rebar you're using? There have been a number of changes recently to rebar, some of them driven by yaws project needs.

I'll try a newer version and post the results.
On Jan 29, 2012, at 1:00 PM, Steve Vinoski wrote:

How new is the rebar you're using? There have been a number of changes recently to rebar, some of them driven by yaws project needs.

Reply to this email directly or view it on GitHub:
https://github.com/klacke/yaws/issues/84#issuecomment-3711219

Upgrading to the latest version of rebar eliminated the issue for more.


Where is the code for firebase when using google actions sdk

I am trying to deploy and test this application but i couldn't find the code for firebase function that needs to be deployed anywhere. Can someone help me with this.?

Depending on whether you're using Dialogflow or Actions SDK, you can look in the functions directory under each service.


Admob Fails. How do I get the errorcode log?

I don't want to burden you with the onus of figuring out why showInterstitial invokes my _onInterstitialEvent callback with a FAILED event. I don't know how to repo this and I'd rather not waste much time trying to figure out how.
All I want to know is this. You are logging the results of a failed interstitial event:
public void onAdFailedToLoad(int errorcode) {
	AdMobEx.getInstance().loadingInterstitial=false;
	AdMobEx.getInstance().failInterstitial=true;
	reportInterstitialEvent(AdMobEx.FAILED);
	Log.d("AdMobEx","Fail to get Interstitial: "+errorcode);
}

(https://github.com/openfl/extension-admob/blob/master/dependencies/admobex/src/admobex/AdMobEx.java#L208)
I'm running my app in -debug mode (esp doing: lime test android -debug ...) and getting practically al logcat messages in my terminal. I also placed a Haxe trace on the onInterstitialEvent in my code, so I'm seeing things like:
09-18 15:54:32.145 24190 24190 I trace   : AdmobController.hx:80: InterstitialEvent: LOADING
09-18 15:54:33.391 24190 24190 I trace   : AdmobController.hx:80: InterstitialEvent: FAILED

What I need is access to the Log.d("AdMobEx","Fail to get Interstitial: "+errorcode); message so I can get that errorcode and debug this further. Any help would be appreciated!

'Log.d' logs it as debug message and i think by default you wont see those in adb logcat.
You could change to 'Log.e' or show debug messages in your logcat  with 'adb logcat *:D'


No available subscription found in current account

Hi,
I've followed the instructions above but at the point of deploying to Azure I get the following error:
[ERROR] Failed to execute goal com.microsoft.azure:azure-webapp-maven-plugin:1.9.0:deploy (default-cli) on project spring-boot: Encoutering error when deploying to azure: 'No available subscription found in current account.'
I have a Free Trial subscription.  I can see when I run "az login" using the CLI I have a listed subscription:
[
{
"cloudName": "AzureCloud",
"homeTenantId": "e5800a50-527b-40c6-950d-3243f52fxxxx",
"id": "f80b6596-dddb-4b54-8d21-671270baxxxx",
"isDefault": true,
"managedByTenants": [],
"name": "Free Trial",
"state": "Enabled",
"tenantId": "e5800a50-527b-40c6-950d-3243f52fxxxx",
"user": {
"name"<EMAIL_ADDRESS>"type": "user"
}
}
]
Please help.
Thanks.

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

ID: 1d6851cb-0c9f-23ef-f231-ff97f44eb721
Version Independent ID: 1fcdbb4a-ee88-9dcd-3ec9-e2064d832ceb
Content: Deploy a Spring Boot JAR file Web App to Azure App Service on Linux
Content Source: articles/java/spring-framework/deploy-spring-boot-java-app-with-maven-plugin.md
Service: app-service
GitHub Login: @bmitchell287
Microsoft Alias: brendm

+1,  Facing the same issue. Any idea why this is happening.

Same issue here!

Hello,
I had the same issue and I solved it by adding "azure cli" to the azure-web-maven-plugin's configuration.
<plugin>
        <groupId>com.microsoft.azure</groupId>
        <artifactId>azure-webapp-maven-plugin</artifactId>
        <version>1.8.0</version>
        <configuration>
            <!-- Specify v2 schema -->
            <schemaVersion>v2</schemaVersion>
            <!-- App information -->
            <authType>azure cli</authType>
            <resourceGroup>RESOURCEGROUP_NAME</resourceGroup>
            <appName>WEBAPP_NAME</appName>
            …

same. @Rachidba 's suggestion actually works

Thanks @Rachidba that worked for me too - fantastic! +1

We've been able to confirm this - our subject-matter expert says "This issue happens when users tried to use maven plugin before installing azure cli, thus left auth files created by Maven plugin but then try to auth with az cli later. Yes adding the auth type (azure_cli) is the right way to solve this."

This Issue also happens if you are having AZ CLI installed within WSL 2 and running MVNW from WSL2 only.
For troubleshooting this on WSL , I tried all steps necessary to clear the Subscriptions, Set Default Subscription from Command Line and also set  in the pom.xml as well.
thing is the Azure.Subscriptions.list() just returns nothing. it could be a bug within the Azure Management JAR itself, but I am not sure as of now.
Moreover, I have also tried using Maven Azure Plugin 1.7, 1.9.1 and 1.10.0 as well. All failed on  WSL2
Once I switched to the Windows 10 native, it worked fine.

Oh, thank you so much for this @Rachidba. I've been battling this issue for a couple of days, including seeing 401 errors even though everything seemed fine. I had indeed run the maven plugins before I had the AZ CLI installed - in my case, I went ahead and blew out ~/.azure and then redid the az login (and, because I have multiple subscriptions, setting the right one with az account) and everything is working great.


API request: an equivalent of boost::intrusive_ptr supported in absl

I have a data structure with a high cardinality. and I want to be able to keep it weakly in a set, returning ref-counted pointers to it to callers. When all the callers drop their refs, I need to remove it from the set. I can easily accomplish this with std::shared_ptr and std::weak_ptr, or using std::enable_shared_from_this. However those options consume excess memory.
https://www.boost.org/doc/libs/1_70_0/libs/smart_ptr/doc/html/smart_ptr.html#intrusive_ptr is a better solution, but comes with the baggage of, well, boost :)  Also see http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0406r1.html
See also a proposed use-case (and a home-grown workaround) in an Envoy Proxy PR: https://github.com/envoyproxy/envoy/pull/7364/files/2de13dd52a0428838a8b3ab2656035956805791e It would be better not to maintain this shared_ptr replacement in Envoy long-term. This feels in-line with absl's pattern of providing generally useful functionality.

I will sum up my response to the internal request here.
We think this is a reasonable request, and internally we have a couple candidate APIs that implement intrusive reference counting. However, we think we need to do some design work and a full API review to come up with an API that we are happy releasing, since we don't think any of the candidates we have are ideal. Then we need to do the cleanup for whatever changes we decide to make to the API we would release. All of this will take a lot of time.


Add missing word

@letmaik Thank you for your contribution. I am merging this PR and it should be live soon.


link metadata removed when remove nested container whas restarted

Description of problem:
When we remove a container, that remove this container from links in metadata of linked containers
docker version:
Client version: 1.6.1
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 97cd073
OS/Arch (client): linux/amd64
Server version: 1.6.1
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 97cd073
OS/Arch (server): linux/amd64

docker info:
Containers: 46
Images: 988
Storage Driver: btrfs
Execution Driver: native-0.2
Kernel Version: 3.16.0-4-amd64
Operating System: Debian GNU/Linux stretch/sid
CPUs: 4
Total Memory: 7.673 GiB
Name: azae02
ID: F3W4:FHMW:WO7H:AUPJ:SOSS:ZDPB:74L5:FCWQ:6KLV:M34Q:MK6C:23YX
Username: tclavier
Registry: [https://index.docker.io/v1/]

uname -a:
Linux azae02 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3 (2015-04-23) x86_64 GNU/Linux
Environment details (AWS, VirtualBox, physical, etc.):
physical, but it's true on all environments.
How reproducible:
Always
Steps to Reproduce:
docker run -d --name db deliverous/blog
docker run -d --name front --link db:db deliverous/blog

docker inspect --format '{{.HostConfig.Links}}' front
[/db:/front/db]

docker stop db
docker inspect --format '{{.HostConfig.Links}}' front
[/db:/front/db]

docker rm db
docker inspect --format '{{.HostConfig.Links}}' front
<no value>

docker run -d --name db deliverous/blog
docker inspect --format '{{.HostConfig.Links}}' front
<no value>

sudo grep db /var/lib/docker/containers/b518f031659680e47410faf2b184ceb6eb8a1e201a5bfef1dcd1c4fe37264da2/hosts
<IP_ADDRESS>	db 84fa62a731fb

docker inspect --format {{.NetworkSettings.IPAddress}} db
<IP_ADDRESS>

Actual Results:
We have an incoherence :

docker inspect say they are no link name DB
inside the container DB point on old IP

Expected Results:
I don't know what it's the good results :

no link in metadata of front container and no entry in hosts file
or link in metadata of front container and good IP in hosts file

Additional info:

Hi!
If you are reporting a new issue, PLEASE make sure that does not have any duplicates already open.
We would like to take this time to remind you of the information we need to debug the problem you are seeing. This is an automated response so if this ticket is not about a bug, do not fret.
If you fail to provide this information within 7 days, we will close this because we cannot debug your issue. We can reopen whenever the information is provided.
Thank you.
Please see:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues
Description of problem:

`docker version`:

`docker info`:

`uname -a`:

Environment details (AWS, VirtualBox, physical, etc.):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual Results:

Expected Results:

Additional info:

#ENEEDMOREINFO

I rebuild my report with the template ... Hay Robot, that match for you ?

Heh, yes Gordon can be quite a PITA, sorry for that, but he can be helpful :smile:
(Part of) this is expected behavior. Links in docker are not "dynamic" and are established between a specific instance of a container, and not based on the container name.
This means that, when the linked container is removed, the link is removed with it, and a new container created with the same name is not automatically linked. If you need to be able to "dynamically" establish links, using a discovery-service might be a better approach, but requires more work.
Libnetwork (https://github.com/docker/libnetwork) is currently being integrated into Docker and will add more options in the future (which will be introduced in "experimental builds" first). I'm not sure if this will include a discovery mechanism, but I will ask the libnetwork team.
This is largely a duplicate of this issue; https://github.com/docker/docker/issues/3155, the discussion on that issue may give some useful information as well.
What I do think should change, is that the entry for the linked container should be removed from /etc/hosts as soon as that container is removed. I seem to remember some changes were made in that area, but I'm not entirely sure.
@estesp I don't recall clearly; did you make changes so that entries were also removed from /etc/hosts?

No--last change I know if there had to do with making the alias and name available in /etc/hosts,  but I agree that this appears to be a synchronization issue with the link behavior, and seems the least we could do is remove entries for containers which don't exist anymore.

Is this has been fixed?

#dibs

I'm going to tentatively close this as links are going away in favor of top level networks and network attachments. Please let me know if you'd like to see it reopened.


Added now-throw and no-try rules.

Fixes: #86

Coverage increased (+0.03%) to 99.304% when pulling e34aa38e44a07a1c9a2d49e331a0c5122a06c220 on RebeccaStevens:issue-86 into 7e27e6ff95d043f0c3da82ac10af57a18df81bbd on jonaskello:master.

Nice work again, and I like that you provide good docs too 👍

Released in 4.7.0


Add cloudstack workload cluster API e2e tests

Issue #, if available:
#1237 (internal)
Description of changes:
This PR add an e2e test that that tests the following features for the CloudStack API. Here we create a management cluster and workload cluster(s) and test it's features using sub tests. The benefits of this approach is the test utilizes a single management cluster rather than spinning a new one up every time to test a workload cluster feature.

create and delete workload clusters for all supported k8 versions
add and remove labels and taints
scale up cp and replace existing worker node groups
scale down cp and scaling worker node groups

See the testing doc for the full list of scenarios we are going to eventually cover [here](https://quip-amazon.com/99bUA1xK7bt0/CloudStack-Full-Lifecycle-API-Testing
Testing (if applicable):

Ran the e2e tests locally

--- PASS: TestCloudStackMulticlusterWorkloadClusterAPI (1846.19s)
    --- PASS: TestCloudStackMulticlusterWorkloadClusterAPI/add_and_remove_labels_and_taints (5.26s)
    --- PASS: TestCloudStackMulticlusterWorkloadClusterAPI/scale_up/down_cp_and_worker_node_group (415.61s)
    --- PASS: TestCloudStackMulticlusterWorkloadClusterAPI/replace_existing_worker_node_groups (115.70s)
PASS

--- PASS: TestCloudStackMulticlusterWorkloadClusterGitHubFluxAPI (2112.32s)
    --- PASS: TestCloudStackMulticlusterWorkloadClusterGitHubFluxAPI/add_and_remove_labels_and_taints (6.31s)
    --- PASS: TestCloudStackMulticlusterWorkloadClusterGitHubFluxAPI/scale_up_and_down_cp_and_worker_node_group (530.08s)
    --- PASS: TestCloudStackMulticlusterWorkloadClusterGitHubFluxAPI/replace_existing_worker_node_groups (140.74s)
PASS

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/test eks-anywhere-presubmit

/approve


Add manual install option to readme and green menu

Hi guys! I'm another one who got metainfo read error on VW MIB2.5 v1367 (bootloader 210, application 8863)
@jilleb is it possible to add script files manually?
Mount sdcard and cp all of it to mib filesystem?
Thank you!
Originally posted by @darkmag666 in https://github.com/jilleb/mib2-toolbox/issues/1#issuecomment-552220581

Yes it's possible. Just copy payload.sh to mqbcoding.esd in the eso/hmi/engdefs folder. I'll add it to the readme.

@jilleb Maybe it would be a good idea to add also "Toolbox update" as another option - for units which the payload trick doesn't work it's necessary to install the toolbox using console. Each time there's a new toolbox, the unit has to be updated by computer. If there would be an "update_toolbox.sh" script, it could copy the new mqbcoding.esd file from sd card to the correspoding location :-)

@jilleb I have copied payload.sh manually today and everything works good.
Scripts also works perfectly.

@jilleb I know it's possible to do that manually. But what I wanted to suggest for improvement is a kind of "update" also for the esd file, like this:
script
value    sys 1 0x0100 "/scripts/copy_phone_customer_plus_mbqencoding.esd.sh"
label    "Get new scripts and files from SD-card (slot1) & update MQBCoding.esd file"
When the Toolbox gets a new version, it would be nice if we could update it without connecting the unit to the computer. This would be very handy for all of us whose units give metainfo error.

yes :-) working on that.
But...It's already possible to install new green menu screens from the mqbcoding.esd and it can also replace mqbcoding.esd.

So can any of you share how to manually copy it? I have the same issue with a 2.5.

Copy payload.sh to eso/hmi/engdefs/mqbcoding.esd
That should be enough.
After copying there will be a new green menu screen. That's all
I'll update the readme in the upcoming days.

Is there a way we can have a short chat? I'm Dutch as well so we can be done quick :)

Haha ok, Facebook me op Jille Berends

When I try to copy it from shell I got this error, that the file system is read only:
cp /net/mmx/fs/sda0/PersonalPOI/PayLoad/0/default/payload.sh /net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd
cp: Can't open destination file.  (/net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd): Read-only file system

You need to mount the volume as writeable. Not to be disrespectful, but maybe you should not mess around with the console if you don't know how to mount the volume as writeable.

Strange I did this before, but always brought an error. I will let you know when it works. Thanks

@jilleb managed to install this using the manual method. Great work! Just some info to add to your stats - my car is the Audi A4 B9 firmware 1329

@jilleb managed to install this using the manual method. Great work! Just some info to add to your stats - my car is the Audi A4 B9 firmware 1329

ymphua, did you connect to the car via telnet? If so, what interface did you use? Thanks

@jilleb managed to install this using the manual method. Great work! Just some info to add to your stats - my car is the Audi A4 B9 firmware 1329

ymphua, did you connect to the car via telnet? If so, what interface did you use? Thanks

Yea I managed to telnet to the car, using the dlink USB Ethernet adapter dub-e100

hello ymphua
you attached a dlink USB dub-e100 to your MIB
Is a special HW Rev. of this USB Ethernet Adapter needed ??? The newest Rev. I see on net is Rev. D ...
Does it work?
The readme of the project states, that the whole SW only works with MIB2 High or MIB2.5 High.
What does High mean?
I have a Media Composition MIB2.5 device (Golf 7  2017).
device: 3Q0035842C
hardware 722
SW: 0876
Is it covered by this project?
Does anybody know?

@rob2e Nope, Media Composition is MIB Standard and therefore this Toolbox won't work there. MIB 2 High is for example Discover Pro at VW, or Columbus at Skoda.


Change sensu_api_validator default test_url

Pull Request Checklist

Description

Upstream removed /info: https://github.com/sensu/sensu-go/pull/2066
The /health endpoint allows unauthenticated queries:
[root@sensu-backend ~]# curl http://localhost:8080/health
{"Alarms":null,"ClusterHealth":[{"MemberID":9882886658148554927,"Name":"default","Err":"","Healthy":true}]}

Related Issue

Fixes #979  .
Motivation and Context

Ensure sensu_api_validator will work with latest sensu-go.
How Has This Been Tested?

[root@sensu-backend ~]# cat test.pp
sensu_api_validator { 'sensu': }
sensu_check { 'test2':
        command       => 'check-cpu.rb',
        subscriptions => ['demo'],
        handlers      => ['email'],
        interval      => 60,
      }
[root@sensu-backend ~]# puppet apply test.pp
Notice: Compiled catalog for sensu-backend.example.com in environment production in 0.12 seconds
Notice: Applied catalog in 0.12 seconds

@treydock could you please rebase this and resubmit

Rebased.

@treydock Travis is unhappy, could you please have a look

Looks like upstream change broke check extra hash property by adding new key to check resource.  Looks like we need to filter out output key.  I'll open new PR


Add functionality to make_draft_json for adding new sources

Currently, the make_all_json function in the make_draft_json module outputs individual json files - one per source in the manifest. This is tricky because adding a new source to meta.json requires the ability to manually review/edit the data (so it can't be totally automated).
Some ideas for additional functionality:

A function to stitch together a group of individual json files
A function to append new, cleaned, individual json files to an existing 'master' meta.json.

I am still new to this code so apologies if I am overlooking existing capabilities or misunderstanding the workflow in any way.

@speedyturkey  I recommend proceeding with just part 2 - a function to append new individual json to an existing master meta.json. Since we have a master json one already, there's no need to stitch together just individual ones. The make_draft_json will still produce one json file per table, the user will then manually validate it, and then the user will run the stitch function.
Keep it simple, but core functionality should be:

check that the tablename does not already exist in the table; give user the option to cancel or overwrite the meta for that table if it already exists.
properly nest the json from a new table into the master file

I looked into the codes in make_draft_json while I was attempting to write an unit test script.  I would like to have a go at this task.

Go for it! Add yourself as an assignee and change the 'ready' label to 'in progress' whenever you actually start work on it.

Finally finished development for this bug fix.  Here is the list of changes:

Added 'checkTable' function to check whether the new table is in table_info.json

Added 'appendJSON' function to append the new table to table_info.json

Added 'duplicateTable' function to handle when the new table is a duplicate entry in table_info.json.  User has the option either overwrite the entry or cancel.

Added a new command line argument 'single-add' to handle the new process

I would like to do a code review before submitting a pull request.  Unit test scripts are still needed.


AO-10072: check the Arg on ResultCode_REDIRECT

Ref: https://swicloud.atlassian.net/browse/AO-10072
When the collector returns ResultCode_REDIRECT it should also bring the new address for redirection in the Arg field.
This PR adds a simple check to make sure the Arg is not empty. Normally it would not happen.
It also slightly moved the place where the redirect counter is increased to exactly follow the meaning of maximum number of redirections.  There is no spec for the number though.

The changes look good to me. Thank Eric for helping me understand a bit more about go and grpc.

Codecov Report

Merging #76 into master will increase coverage by 0.49%.
The diff coverage is 40%.

@@            Coverage Diff             @@
##           master      #76      +/-   ##
==========================================
+ Coverage   83.35%   83.84%   +0.49%
==========================================
  Files          33       33
  Lines        3196     3195       -1
==========================================
+ Hits         2664     2679      +15
+ Misses        456      438      -18
- Partials       76       78       +2

Impacted Files
Coverage Δ

v1/ao/internal/reporter/reporter_grpc.go
66.72% <40%> (+0.28%)
:arrow_up:

v1/ao/internal/host/observer.go
81.59% <0%> (ø)
:arrow_up:

v1/ao/internal/reporter/metrics.go
81.29% <0%> (+2.15%)
:arrow_up:

v1/ao/internal/host/sys_linux.go
57.14% <0%> (+2.85%)
:arrow_up:

v1/ao/internal/host/host.go
69.09% <0%> (+12.72%)
:arrow_up:

Continue to review full report at Codecov.

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


Dockerfile Alpine removed -y

@Ada-Codina how did you create this PR? There are a lot of merge conflicts.
Can you delete your fork and then re-fork and create a branch off of the master to get the latest changes?
Reference(s):

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches


XmlPrefixName.namespaceUri is null in copied XmlNode

I'm using xml to process SAML responses.
dependencies:
  xml: ^5.3.1

import 'package:test/test.dart';
import 'package:xml/xml.dart';

void main() {
  test('clone namespaceUri', () {
    final xml = '<samlp:Response xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">'
        '<saml:Assertion></saml:Assertion>'
        '</samlp:Response>';
    final doc = XmlDocument.parse(xml);
    final assertion = doc.rootElement.firstElementChild;
    final assertion2 = assertion!.copy();

    expect(assertion.name.namespaceUri, 'urn:oasis:names:tc:SAML:2.0:assertion');
    expect(assertion2.name.namespaceUri, 'urn:oasis:names:tc:SAML:2.0:assertion'); // failed
  });
}

https://github.com/renggli/dart-xml/blob/3c587e18c3b507eb737a2aec864f0bc8413f8aed/lib/src/xml/utils/prefix_name.dart#L18
The resolving of a namespace URI is depending on the ancestors.
Consider storing the namespace URI property directly.

I don't know how other libraries handle this situation?
Resolving the property early might be possible, but it breaks the general mutability of the DOM (or require complicated invalidation logic).
Storing the property on copy might be possible, but changes the DOM in unexpected ways.

In xmldom (a Node.js library) it is stored while parsing and creating a new element or attribute node.
https://github.com/xmldom/xmldom/blob/e31e25d9b0ce79e8545d23771181a79d96b80c73/lib/dom.js#L894
https://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-NodeNSname

namespaceURI of type DOMString, readonly, introduced in DOM Level 2
The namespace URI of this node, or null if it is unspecified.
This is not a computed value that is the result of a namespace lookup based on an examination of the namespace declarations in scope. It is merely the namespace URI given at creation time.

I think it's safe to store it at creation time.

Interesting: https://www.w3.org/TR/DOM-Level-2-Core/core.html#Namespaces-Considerations. This basically breaks serialization of the DOM by design :-/


Multiple "Branded" Targets of same underlying App

My first solution was to setup a separate Fastfile for each branded target....but I'm not seeing a way to specify the Fastfile to use with fastlane.
I'll be integrating shortly with Jenkins (just trying to get a manual process working first).
So, what would be your recommendation as to the best way to setup and utilitize fastlane?
Thanks in advance...

Hey @ehlersd ,
I think I should be able to help you out here.
:warning: Official Answer :warning:
A PR of mine was just merged into master a few days ago (I don't think the gem has been pushed out yet) that allows for multiple environments using dotenv.
Ex: fastlane beta --env brand1 or fastlane beta --env brand2
Here is a gist with that example: - https://gist.github.com/joshdholtz/aa902e7ae28c1c0bea2a
:warning: Unofficial Answer :warning:
Since this isn't a "released" feature yet, you can use a gem I wrote that adds this ability AND "brand" specific lanes if you need that - https://github.com/joshdholtz/fastlane-env-lanes
If you use fastlane-env-lanes, you would call fastlane beta:brand1 instead of fastlane beta --env brand1. By using this gem, you can also decorate lanes for a specific brand.
lane :beta do
  # Only gets called if NO environment/brand is used
  puts "Why are you building without a brand?"
end

lane :beta, :brand1 do
  # Do some specific brand 1 stuff

  # Will load CONFIG and SCHEME from .env.<brand> where brand is brand1 because that is the environment specific lane we are in
    ipa({
        workspace: ENV['WORKSPACE'],
        configuration: ENV['CONFIG'],
        scheme: ENV['SCHEME'],
      })
end

lane :beta, :brand2 do
  # Do some specific brand 1 stuff

  # Will load CONFIG and SCHEME from .env.<brand> where brand is brand2 because that is the environment specific lane we are in
    ipa({
        workspace: ENV['WORKSPACE'],
        configuration: ENV['CONFIG'],
        scheme: ENV['SCHEME'],
      })

end

Awesome!  Great answer...thx!

Note: The fastlane-env-lanes also loads the different .env files like my PR does. It just loads it differently :brand instead of --env brand.
Let me know if you need any more help with setting anything up! Always available to help :grin:

@joshdholtz being awesome again :rocket: :grinning: How about putting this information into its own .md file in the repository and link to it from the README?

@KrauseFx I can do that! :fist: Let's keep this issue open until I do that

@joshdholtz I'll assign the issue to you :wink:
I'll be working on the big refactoring of the fastlane documentation, so let's wait until that's finished.

Would love to try this. Wow. iOS tooling has just got even more awesome. :beers:

@joshdholtz I got asked about the multiple targets again, if you have some time it would really be cool to add a short explanation to the docs folder when you have some time :+1:

I cannot make it load different snapshot config files. Am I doing something wrong?
.env.something:
LOCALIZED_CONFIGS_PATH="./fastlane/s_lt"

Fastfile (doesn't work):
lane :deploy do
  snapshot(
      snapshot_file_path: ENV["LOCALIZED_CONFIGS_PATH"],
    )
end

However, it works if I change it to:
lane :deploy do
  snapshot(
      snapshot_file_path: './fastlane/s_lt',
    )
end

Command: fastlane deploy --env something
It would also be very good if I could use ENV is Snapfile (and other config files) but it also doesn't seem to work.

@jaroslavas Can you try replacing
LOCALIZED_CONFIGS_PATH="./fastlane/s_lt"

with
export LOCALIZED_CONFIGS_PATH="./fastlane/s_lt"

Still getting Could not find './Snapfile'

I'll close this issue for now, thanks @joshdholtz for providing the documentation on how to solve this problem :+1:

@joshdholtz and @KrauseFx , any news if fastlane-env-lanes is an official solution by now?

@cytryn Oh man, I haven't update or ran the repo in a while 😇  I am not sure if it still works but definitely not an official solution 😉
Your best bet would probably be to have a separate .env file for each branch .env.brand1, .env.brand2, etc, and switch on stuff in your lane to a different method or something.

@joshdholtz oh ok. I will definitely try that! Thanks for the update.

@cytryn No problem! I should also go mark that repo has no longer supported probably 😬

Correct me if I'm wrong, but dotEnv is already integrated into fastlane, run fastlane --help for more information

@KrauseFx Yup yup, it is! But @cytryn was asking about my environment specific lanes repo (https://github.com/joshdholtz/fastlane-env-lanes) that I made back in the day. I mentioned that I don't support that and the official solution would be to use the .env.* method that is built in already 👌

HI, is there any possible to use gym for a specific target ?


[WFLY-15799] Upgrade to Kafka client 3.1.0

https://issues.redhat.com/browse/WFLY-15799
As mentioned in the Jira, this allows us to remove the temporary downgrade of the embedded Kafka version for testing

Thanks, @kabir


can't parse options.. debian squeeze

/usr/lib/ruby/1.8/optparse.rb:1450:in complete': invalid option: --username (OptionParser::InvalidOption)         from /usr/lib/ruby/1.8/optparse.rb:1448:in catch'
from /usr/lib/ruby/1.8/optparse.rb:1448:in complete'         from /usr/lib/ruby/1.8/optparse.rb:1261:in parse_in_order'
from /usr/lib/ruby/1.8/optparse.rb:1254:in catch'         from /usr/lib/ruby/1.8/optparse.rb:1254:in parse_in_order'
from /usr/lib/ruby/1.8/optparse.rb:1248:in order!'         from /usr/lib/ruby/1.8/optparse.rb:1339:in permute!'
from /usr/lib/ruby/1.8/optparse.rb:1360:in parse!'         from /var/lib/gems/1.8/gems/nirvdrum-svn2git-1.3.1/lib/svn2git/migration.rb:101:in parse'
from /var/lib/gems/1.8/gems/nirvdrum-svn2git-1.3.1/lib/svn2git/migration.rb:12:in initialize'         from /var/lib/gems/1.8/gems/nirvdrum-svn2git-1.3.1/bin/svn2git:25:in new'
from /var/lib/gems/1.8/gems/nirvdrum-svn2git-1.3.1/bin/svn2git:25
from /usr/local/bin/svn2git:19:in `load'
from /usr/local/bin/svn2git:19

I'm closing this out due to lack of necessary information.  If this is still a problem and you can provide the additional info, please feel free to re-open.


How can I get properties from github repository where the name of configuration file is not "application.properties/application.yml"?

I changed the default name of "application.properties"

set spring.cloud.config.name={your config name} in your config client bootstrap.properties.
Here is the document: Locating Remote Configuration Resources


Define NoDataTimeframe type for unmarshaling JSON correctly

Patch for #49.
Replace value into 0 if 'false' value is found.

It looks like the gofmt test is failing? I can't divine why by eyeballing the diff, but can you fix up the format and repush?

Sorry, I fixed up format.

Thanks for the fix!


Add links to open Message and MessageHandler in IDE

I think it could be helpful for developers to have Links, in the Detail-View of a Message, to open the Message and MessageHandler in the IDE.
Same behaviour as in error messages in dev-mode.
https://symfony.com/doc/current/reference/configuration/framework.html#ide
I guess code can be used from here (Code changed a bit, between 6.3 and 6.4)
https://github.com/symfony/symfony/blob/6.4/src/Symfony/Component/ErrorHandler/ErrorRenderer/HtmlErrorRenderer.php#L54
Maybe only add this in env = dev?
WDYT?

Maybe only add this in env = dev?

Do you think this package is useful in dev? I always figured this bundle would be most useful in production.

I use it mostly in dev ;)
Today was the first deploy on live with symfony messenger and your bundle. Useful here as well.

I use it mostly in dev ;)

Ok, fair enough. Then yeah, this would be a cool feature. Could it be possible to use in production? If you're a dev and browsing in production, could you click to open the file in your ide (assuming the project is open)?

If you have the ide option populated in production, I believe this bundle is allowed to assume it is going to work when clicked.

It is harder in production. Every developer has probably checked out the project in a different folder. But every developer could have a agreement about a symylink in there local environment that points to there private folder. Maybe IDE's have a better/dynamic handling. Another problem is the checkout branch vs the branch in production. (Same as in dev, but maybe less obviously).
But this is a general problem and out of scope of this issue.