ClusterAllFailedError: Failed to refresh slots cache. with Cluster mode and TLS enabled

I'm trying to configure an ElastiCache cluster with TLS and Auth configured. I'm getting the following error with trying to connect:
ClusterAllFailedError: Failed to refresh slots cache
Here's my configurations detatils:
ioredis: 4.27.8
ElastiCache: 6.x
Code snippet:
client = new Redis.Cluster([{host: HOST,port:PORT}],{         redisOptions: {           password: PASSWORD,           tls: {}           }       });

I have a same problem.. tls: {} or dnsLookup does not work.

This is an extremely annoying issue tbh, is you search under Issues tab for this repo there is at least 15 issues related to the same ClusterAllFailedError: Failed to refresh slots cache.
I had the same problem i was able to work around but not 100% because from time to time it disconnects and timeout.

If you are using cluster then make sure your ElastiCache Redis Instance Cluster mode is on
Make sure there is AUTH enabled, and TLS
Make sure you can reach the primary endpoint of the Redis Cluster

redis-cli -u redis://PUT_YOUR_AUTH_PASSWORD_HERE@master.your_endpoint.use1.cache.amazonaws.com:6379/0 --tls ping
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
PONG

^ if you see PONG means your computer or EC2 can reach that Redis endpoint. If you're running from your actual computer (LInux, Mac, Windows, etc) you need to be inside the AWS VPN if you are not inside an AWS VPN from your organization you will not reach the Redis Cluster.
4. Make sure you can connect from an EC2 host in same VPC, or make sure you can connect from a lambda test function before going crazy and putting the code in your project.
5. I had to do this before actually connecting via Node/ioRedis code:
redis-cli -u redis://PUT_YOUR_AUTH_PASSWORD_HERE@master.your_endpoint.use1.cache.amazonaws.com:6379/0 --tls

^ after connected to redis i did this:
> cluster slots
^ that should print your shard/cluster replicas/endpoints something similar to this:
1) 1) (integer) 0
   2) (integer) 16383
   3) 1) "YOUR_ENDPOINT_1-001.xyz.use1.cache.amazonaws.com"
      2) (integer) 6379
      3) "5d15665843ae2f5528fe01ae9e...."
   4) 1) "YOUR_ENDPOINT33.xyz.use1.cache.amazonaws.com"
      2) (integer) 6379
      3) "3c33fafba73a4270a5387809c861......"
   5) 1) "YOUR_ENDPOINT_2.xyz.use1.cache.amazonaws.com"
      2) (integer) 6379
      3) "daa36bd8b76d8464344...."

This is the code I used: file: redis_test.js

const connectCluster = () => {
  const cluster = new Redis.Cluster(
    [
      {
        host: "clustercfg.your_cluster_address.xyz.use1.cache.amazonaws.com",
        port: 6379,
      },
    ],
    {
      dnsLookup: (address, callback) => callback(null, address),
      redisOptions: {
        tls: true,
        password:
          "YOUR_AUTH_PASSWORD",
      },
    }
  );

  return cluster;
};

const cluster = connectCluster();
cluster.set("name", "test");
cluster.get("name").then(r => {
  console.log(r); // <- you should see "test"
});

Hopefully this help you both @anax015obs and @jungRoit
Also like others mentioned in different Issues use: DEBUG=ioredis:* node redis_test.js in order to see more information about your message.

This is an extremely annoying issue tbh, is you search under Issues tab for this repo there is at least 15 issues related to the same ClusterAllFailedError: Failed to refresh slots cache.

@juanviamonte THIS WORKED! Thank you for documenting those steps

This is an extremely annoying issue tbh, is you search under Issues tab for this repo there is at least 15 issues related to the same ClusterAllFailedError: Failed to refresh slots cache.
I had the same problem i was able to work around but not 100% because from time to time it disconnects and timeout.

If you are using cluster then make sure your ElastiCache Redis Instance Cluster mode is on  (you have to make sure this is selected at the moment of creation)

Make sure there is AUTH enabled, and TLS, (Encryption at Rest ON, Encryption in Transit ON)
Make sure you can reach the primary endpoint of the Redis Cluster

redis-cli -u redis://PUT_YOUR_AUTH_PASSWORD_HERE@master.your_endpoint.use1.cache.amazonaws.com:6379/0 --tls ping
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
PONG

^ if you see PONG means your computer or EC2 can reach that Redis endpoint. If you're running from your actual computer (LInux, Mac, Windows, etc) you need to be inside the AWS VPN if you are not inside an AWS VPN from your organization you will not reach the Redis Cluster. 4. Make sure you can connect from an EC2 host in same VPC, or make sure you can connect from a lambda test function before going crazy and putting the code in your project. 5. I had to do this before actually connecting via Node/ioRedis code:
redis-cli -u redis://PUT_YOUR_AUTH_PASSWORD_HERE@master.your_endpoint.use1.cache.amazonaws.com:6379/0 --tls

^ after connected to redis i did this: > cluster slots ^ that should print your shard/cluster replicas/endpoints something similar to this:
1) 1) (integer) 0
   2) (integer) 16383
   3) 1) "YOUR_ENDPOINT_1-001.xyz.use1.cache.amazonaws.com"
      2) (integer) 6379
      3) "5d15665843ae2f5528fe01ae9e...."
   4) 1) "YOUR_ENDPOINT33.xyz.use1.cache.amazonaws.com"
      2) (integer) 6379
      3) "3c33fafba73a4270a5387809c861......"
   5) 1) "YOUR_ENDPOINT_2.xyz.use1.cache.amazonaws.com"
      2) (integer) 6379
      3) "daa36bd8b76d8464344...."

This is the code I used: file: redis_test.js

const connectCluster = () => {
  const cluster = new Redis.Cluster(
    [
      {
        host: "clustercfg.your_cluster_address.xyz.use1.cache.amazonaws.com",
        port: 6379,
      },
    ],
    {
      dnsLookup: (address, callback) => callback(null, address),
      redisOptions: {
        tls: true,
        password:
          "YOUR_AUTH_PASSWORD",
      },
    }
  );

  return cluster;
};

const cluster = connectCluster();
cluster.set("name", "test");
cluster.get("name").then(r => {
  console.log(r); // <- you should see "test"
});

Hopefully this help you both @anax015obs and @jungRoit
Also like others mentioned in different Issues use: DEBUG=ioredis:* node redis_test.js in order to see more information about your specific error message.

Thanks, just one note here, tls is not boolean, so you can pass:
  const redisCluster = new Redis.Cluster([{ host, port }], {
    scaleReads: 'all',
    dnsLookup: (address, callback) => callback(null, address),
    redisOptions: {
      password,
      tls: {},
    },
  })


Adjust FlatButton background, hover and ripple colors

Transparent background, and alpha overlays for hover and ripple, to better match Material-Design spec.
Addresses #2467.

Okay - should be good to go, but happy to tweak if it misses the mark. Sorry for squashing your comments. :) All taken into account though.

Thanks for fixing this :+1: But I see this here

I mean are you sure the background should be gray? It seems to me that it should match the text's color.

Shading the background colour is what we discussed in #2367, and also how MDL implements it. If it shaded it with the text colour you would get undesirable effects such as a primary button on a blue background having a purple hover state. Users can always override it with props if they want coloured buttons.

@mbrookes I see your point. I'm sold :smile: Thanks a lot :+1:
@oliviertassinari Please take a look.

@mbrookes Could you remove this line https://github.com/callemall/material-ui/blob/master/src/app-bar.jsx#L199? We do no longer need it now :+1:

Thanks @oliviertassinari - updated and squashed.

Good to go :+1: Thanks @mbrookes


Unable to Index into a steadystate solution using symbols

I am unable to index into the steadystate solution using symbols.
Here is MWE:
using ModelingToolkit,MethodOfLines, DomainSets
using OrdinaryDiffEq, SteadyStateDiffEq

@parameters t x y
@parameters D b
@variables A(..) S(..)
Dx = Differential(x)
Dy = Differential(y)
Dt = Differential(t)
Dxx = Differential(x)^2
Dyy = Differential(y)^2
#2d PDE and bcs
eqs = [Dt(A(t,x,y)) ~ Dxx(A(t,x,y)) + Dyy(A(t,x,y))  + A(t,x,y)^ 2 /S(t,x,y) - b*A(t,x,y), #+ Dyy(A(t,x))
       Dt(S(t,x,y)) ~ D*Dxx(S(t,x,y)) + D*Dyy(S(t,x,y)) + A(t,x,y)^ 2 - S(t,x,y)] #+ D*Dyy(S(t,x))
A0, S0 = homo_turing(0.35)
d = Normal(0.0,1.0)
bcs = [A(0, x,y) ~ A0 * (1 + 0.1*rand(d)) + 0.1*exp(-1.0*x^2*y^2),
S(0, x,y) ~ S0*(1 +  0.1*rand(d))  + 0.1* exp(-1.0*x^2*y^2) , #
Dx(A(t, 0,y)) ~ 0.0,
Dx(A(t, 10,y)) ~ 0.0,
Dx(S(t, 0,y)) ~ 0.0,
Dx(S(t, 10,y)) ~ 0.0,
Dy(A(t, x,0)) ~ 0.0,
Dy(A(t, x,10)) ~ 0.0,
Dy(S(t, x,0)) ~ 0.0,
Dy(S(t, x,10)) ~ 0.0
]
#domain
domains = [t ∈ Interval(0, 1.0), x ∈ Interval(0.0, 10.0),y ∈ Interval(0.0, 10.0)]
dx = 1.0
dy = 1.0
order = 2
#construct the pde sys
@named pdesys = PDESystem(eqs,
    bcs,
    domains,
    [t, x,y],
    [A(t, x,y), S(t, x,y)],
    [D => 30.0, b=> 0.35])
discretization = MOLFiniteDifference([x => dx,y =>dy], t, approx_order = order)
prob = discretize(pdesys, discretization)
steadystateprob = SteadyStateProblem(prob)
@time steadystate = solve(steadystateprob, DynamicSS(AutoTsit5(Rosenbrock23())))

steadystate[A(t,x,y)] # broken
steadystate[A(x,y)]  # broken

Doing steadystate[A(t,x,y)] or  steadystate[A(x,y)] results in the following error message
Error & Stacktrace ⚠
ERROR: ArgumentError: A(t, x, y) is neither an observed nor a state variable.
Stacktrace:
 [1] build_explicit_observed_function(sys::ODESystem, ts::Num; inputs::Nothing, expression::Bool, output_type::Type, checkbounds::Bool, drop_expr::typeof(RuntimeGeneratedFunctions.drop_expr), ps::Vector{…}, throw::Bool)
   @ ModelingToolkit ~/.julia/packages/ModelingToolkit/N1HdY/src/systems/diffeqs/odesystem.jl:375
 [2] build_explicit_observed_function
   @ ~/.julia/packages/ModelingToolkit/N1HdY/src/systems/diffeqs/odesystem.jl:315 [inlined]
 [3] #541
   @ ~/.julia/packages/ModelingToolkit/N1HdY/src/systems/diffeqs/abstractodesystem.jl:476 [inlined]
 [4] get!(default::ModelingToolkit.var"#541#556"{…}, h::Dict{…}, key::SymbolicUtils.BasicSymbolic{…})
   @ Base ./dict.jl:479
 [5] (::ModelingToolkit.var"#649#generated_observed#555"{…})(::Num, ::Vector{…}, ::Vararg{…})
   @ ModelingToolkit ~/.julia/packages/ModelingToolkit/N1HdY/src/systems/diffeqs/abstractodesystem.jl:475
 [6] observed
   @ SciMLBase ~/.julia/packages/SciMLBase/XEPyX/src/solutions/solution_interface.jl:184 [inlined]
 [7] getindex(A::SciMLBase.NonlinearSolution{…}, sym::Num)
   @ SciMLBase ~/.julia/packages/SciMLBase/XEPyX/src/solutions/solution_interface.jl:174
 [8] top-level scope
   @ REPL[41]:1
Some type information was truncated. Use `show(err)` to see complete types.

Environment (please complete the following information):

The version of the packages I am using is below. I am using older version of ModelingToolkit due to latest version being broken as show in https://github.com/SciML/PDEBase.jl/issues/19

[5b8099bc] DomainSets v0.6.7
⌃ [94925ecb] MethodOfLines v0.10.1
⌃ [961ee093] ModelingToolkit v8.71.2
    [9672c7b4] SteadyStateDiffEq v1.16.1
⌃ [1dea7af3] OrdinaryDiffEq v6.59.0

Output of versioninfo()

Julia Version 1.10.0-rc1
Commit 5aaa9485436 (2023-11-03 07:44 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 12 × Intel(R) Xeon(R) CPU E5-2603 v4 @ 1.70GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-15.0.7 (ORCJIT, broadwell)
  Threads: 1 on 12 virtual cores
Environment:
  JULIA_EDITOR = code
  JULIA_NUM_THREADS =

cc @ChrisRackauckas

If you wanted to solve steady state, you need to write your problem independent of time and solve with a NonlinearProblem, see the docs: https://docs.sciml.ai/MethodOfLines/stable/tutorials/heatss/

The reason I formulated the problem as steadystate problem rather than NonlinearProblem because PDEbase doesn't allow setting initial conditions for u0. I solved reformulated steadystate as NonlinearProblem and I run into the same issue

I'll add that feature then, thanks for the heads up!


KEB trial cleanup supports cleaning up failed trial clusters

Description
Besides managing the expiry of trial runtimes, KEB trial cleanup job should also automatically trigger deprovisioning of trial runtimes wich are in failed state from lifecycle management point of view, i.e. in failed provisioning/unsuspension or failed deprovisioning/suspension state.
Reasons
SRE has another automation to automatically perform trial cleanup of failed runtimes which we plan to deprecate as the goal overlaps with the KEB trial cleanup job.
Attachments

As disussed that's fine that after two weeks, we will suspend all types of trials, that means including  failed provisioning/unsuspension or failed deprovisioning/suspension sceanrios.

After analysis (@PK85, @piotrmiskiewicz and @jaroslaw-pieszka) we concluded that we need touch above places:

https://github.com/kyma-project/control-plane/blob/aa836f723a31c05c3d7ce663106c87425fdebf3c/components/kyma-environment-broker/cmd/trialcleanup/main.go#L94C118-L95C1 - action item: job itself must take all instances regardless it is expired or not (this will allow to trigger expiration again for previous expirations that failed).
https://github.com/kyma-project/control-plane/blob/aa836f723a31c05c3d7ce663106c87425fdebf3c/components/kyma-environment-broker/internal/suspension/handler.go#L77C1-L78C1 - action item: we analyzed the code and it looks that it could handle previous expirations that failed. In addition if we adjust suspension from deprovisionings marked as temporary to all deprovisionings then we will handle even the scenario that user triggered deprovisioning and it failed.

@PK85 @piotrmiskiewicz @jaroslaw-pieszka I think you don't be able to suspend all failed trial runtimes.

failed provisioning: -> runtime was not created successfully, call deprovision instead of suspension or marking expiry.
failed deprovisioning -> runtime was to be deleted, call deprovision API again
failed suspension: -> call suspension (instance update with active: false param) again
failed unsuspension: -> runtime was not recreated successfully during unsuspension. call suspension (instance update with active: false param) again

@ebensom we have discussed the issue in the team and decided to prepare a temporary solution which will handle failed provisioning and failed deprovisioning scenarios. Suspension retriggers are already covered. See the PR I'm currently preparing: https://github.com/kyma-project/kyma-environment-broker/pull/66. In the long term, we want to have a new internal endpoint in KEB which will handle the expiration of instances. I will create a separate issue for the new endpoint.


Taking a video on Nexus 5 always returns error message

Version Number of Plugin: 3.0.1
Device Tested On: Nexus 5
Expected Behavior
Taking a video should return a MediaFile result.
Actual Behavior
Always returns message error: Unable to locate media file at content://media/external/video/media/156934
Code snippet
      StoreVideoOptions mediaOptions = new StoreVideoOptions()
		{
			Name = "test.mp4",
			CompressionQuality = 92,
			DesiredLength = TimeSpan.FromSeconds(10),
                            SaveToAlbum = true
		};

         var file = await CrossMedia.Current.TakeVideoAsync(mediaOptions);

Did you setup your file provider? https://github.com/jamesmontemagno/MediaPlugin#android-n
Works fine on my devices that I have tested here.


Add to Cart Form - encryption ajax callback

Create a callback function to encrypt custom form fields on ProductPage. Example - text field to personalize a product.

Not needed in core module. Can be done custom as needed (see Dogzaz.com).
Would make for a good tutorial.
Closing.


At least one of your integrations requires reconfiguration to continue functioning.

Did you read the instructions?

[X] I have read the README, including the advanced debugging section.

The problem
Every now and then overkiz stops working and i get notification that it requires reconfiguration. When i enter credentials it says aborted.
What version of this integration (ha-tahoma) has the issue?
2.8.2
What version of Home Assistant Core has the issue?
core-2021.9.6
Which gateway / hub do you use?
Somfy Tahoma
Device model
No response
Home Assistant log
No response
Additional information
No response

I see. Then only the first sentence stays relevant :)

@dhover could you share your full log perhaps? I wonder if they first had a maintenance error.

I can activate the debug log for this integration if you tell be how to.

I can't authenticate using App password...
On Tue, 19 Oct 2021 at 11:03 Tim Messerschmidt @.***>
wrote:

+1 -- I re-authenticate every few days (which works fine).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/iMicknl/ha-tahoma/issues/599#issuecomment-946509440,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALII6UHNCIMVRLPLMMLPSFTUHUX6LANCNFSM5F46FMHA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Pozdrawiam
Kaczmarski Krystian

I have the same issue on my side, I haven't activated debug log but I will to it right now to see if it was exactly the same bugs.
In the case the it was also the BadCredential issue, classing this error as a ConfigEntryNotReady rather than a ConfigEntryAuthFailed if it was a success maybe one hour before could solve the issue, WDYT?
(Sorry If compltely wrong, I'm really not an expert in HA nor in Python, my last experience with both was three years ago to support  EnOcean cover and I never finish my development to be in production. I'm just trying to help solving the issue)

Just FYI (because I was triggered by github-actions), I haven't seen the issue in the last few weeks.

it's seems there is another connection method on atlantic cozytouch which use altantic api
For me curl --request POST 'https://ha110-1.overkiz.com/enduser-mobile-web/enduserAPI/login' --form 'userId=xxx@xxx' --form 'userPassword=xxx' is down today
But i found on other github this method:
get access token:
curl --header "Content-Type: application/x-www-form-urlencoded" --header "Authorization: Basic czduc0RZZXdWbjVGbVV4UmlYN1pVSUM3ZFI4YTphSDEzOXZmbzA1ZGdqeDJkSFVSQkFTbmhCRW9h"  -d "grant_type=password&username=xxx@xxx&password=xxx" https://api.groupe-atlantic.com/token
then get jwt
curl --request GET --header "Authorization: Bearer access_token_here" https://api.groupe-atlantic.com/gacoma/gacomawcfservice/accounts/jwt
and finally:
curl --request POST 'https://ha110-1.overkiz.com/enduser-mobile-web/enduserAPI/login' --form 'jwt=jwt_here'
hope this helps..
(sorry for my english)

@peka45 this is not related to this issue. If you face issues with this integration, please create a new issue. We already implemented the new authentication method for Cozytouch/Atlantic in this integration.

Today this integration requires a reconfiguration.

I have also just got the message to reconfigurate.

Same for me, got the message about an hour ago. Looks like this was caused by something on Somfy side. As I wrote 6 days ago, I haven't seen it in weeks and now it happened at the same as it happened to other people.

same here

Yes but why do we need a reconfiguration when the server is down?

Yes but why do we need a reconfiguration when the server is down?

Please read back in this issue, it has been explained already multiple times.
TLDR: Somfy does throw a BadCredentials error when you credentials changed, however sometimes they throw this error as well when they have internal issues (e.g. just after maintenance).
For all the others, I faced the same issue indeed and we will still see if we have a better solution. I didn't have time to contact Somfy about this issue yet. For now, you don't need to respond with +1 / same issue. 😉

I understand. Thanks for your explanation.

I had this happen to me tonight, now I have two accounts with the same username. If I have both enabled, one gets ignored.
This outputs to the log,
2021-12-11 21:13:28 ERROR (MainThread) [homeassistant.components.cover] Platform tahoma does not generate unique IDs. ID rts://x-x-x/x already exists - ignoring cover.master_bedroom
2021-12-11 21:13:28 ERROR (MainThread) [homeassistant.components.cover] Platform tahoma does not generate unique IDs. ID rts://x-x-x/x already exists - ignoring cover.living_room
2021-12-11 21:13:28 ERROR (MainThread) [homeassistant.components.cover] Platform tahoma does not generate unique IDs. ID rts://x-x-x/x already exists - ignoring cover.study
2021-12-11 21:13:28 ERROR (MainThread) [homeassistant.components.cover] Platform tahoma does not generate unique IDs. ID rts://x-x-x/x already exists - ignoring cover.bedroom_3

The second one is listed as 'Not loaded'. I also cannot delete either of them, clicking the hamburger, and then Delete->OK does nothing. Even after a reboot.

I have got the message again. But even with my correct password, I get an invalid authentication.

Same here. The integration shows "Aborted" after username/password but the connection is ok. So everything seems ok for now.

I had this happen to me tonight, now I have two accounts with the same username. If I have both enabled, one gets ignored.
The second one is listed as 'Not loaded'. I also cannot delete either of them, clicking the hamburger, and then Delete->OK does nothing. Even after a reboot.

@callifo please create a new issue for this one. This is not a known bug related to this issue. Could you try to remove the integration from HA entity registrry (integrations page) and than reboot and add again?

I also receive this messages, every few days... I need to reenter my password, and then it display aborted, but then works OK. Until I got the same message again...

Same here using Somfy Europe as server. Feels like it is happening around 9-10 CET everyday now.

anyone found a way to get around this other than restarting the HA instance? nothing related in the config to raise
Authentication failed while fetching device events data: Bad credentials

so if this is Tahoma (yes an update is available, as it was when I had the issue before the other day), couldn't the integration create a notification for that instead?

I have also gets this error another time. It seems to be that the interval of those messages are increasing the last days.
I like to see any possiblity to notify me that the integration needs to be re-autorized. Because in the meantime while i not have reentered my password all my automations will
Not work.

I've been playing around with reloading some integrations via rest call as described here: https://community.home-assistant.io/t/add-service-integration-reload/231940/37 and from what I can see this also worked for the Overkiz integration. All covers were available again immediately, however the reconfigure message for the integration remains but everything else seems to be working again.

@redneckdba looks like nice workaround. Many of us have been struggling with automations not getting executed and daily reconfigurations.
Can you share your snippets for configuration and automation ?

Sure thing.
Extracting the integration's id can be done via browser debug tools (F12) as described in https://community.home-assistant.io/t/add-service-integration-reload/231940/21

rest command
reload_tahoma: url: http://ha-ip:8123/api/config/config_entries/entry/<integration id>/reload method: POST headers:   authorization: !secret integration_token   content-type: application/json
automation (this part is untested, I added it after today's outage but should hopefully work):
`alias: System - Reload Overkiz integration in case it goes unavailable.
trigger:

platform: state
entity_id: cover.blinds_patio
to: unavailable
for: 00:05:00
action:
service: rest_command.reload_tahoma`

Hi @tetienne
You're welcome. I just added the automation part today after the latest outage and therefore haven't been able to test it so far. If we're always hitting the same issue it should probably be safe to lower the timeout to 1-2 minutes.

@Mariusthvdb: I just had a look at the official docs for this service and it's still not clear to me what it's supposed to reload and how. If I however interpreted the snippets I gathered in the forums correctly, the following should also work for the automation:
`alias: System - Reload Overkiz integration in case it goes unavailable.
trigger:

platform: state
entity_id: cover.blinds_patio
to: unavailable
for: 00:05:00
action:
service: homeassistant.reload_config_entry
data:
entry_id: "2b70c5ce4efa6fcb24684be8852e4143"`

correct. that how it works.
Not sure about automating that though, but reloading the config_entry is done like that yes.
(Believe we can even use the new integration_entities() template for it and use any entity of the integration there, but I cant find the correct syntax for now.)

@Mariusthvdb: I just had a look at the official docs for this service and it's still not clear to me what it's supposed to reload and how. If I however interpreted the snippets I gathered in the forums correctly, the following should also work for the automation: `alias: System - Reload Overkiz integration in case it goes unavailable. trigger:

platform: state
entity_id: cover.blinds_patio
to: unavailable
for: 00:05:00
action:
service: homeassistant.reload_config_entry
data:
entry_id: "2b70c5ce4efa6fcb24684be8852e4143"`

Under Developer tools, Services: If I choose the service "homeassistant.reload_config_entry" and enter the correct config entry  the button CALL SERVICE stays greyed out. It seems the syntax is not the right. So something is missing.

Yep, I see that too. File an issue in the Frontend repo is what you should do.

#10926

I've been playing around with reloading some integrations via rest call as described here: https://community.home-assistant.io/t/add-service-integration-reload/231940/37 and from what I can see this also worked for the Overkiz integration. All covers were available again immediately, however the reconfigure message for the integration remains but everything else seems to be working again.

If you want to get rid of the reconfigure message in the "Notifications" section within HA (this is a persistent notification with a specific notification_id), add the following action to your automation:
  - service: persistent_notification.dismiss
    data:
      notification_id: config_entry_reconfigure

I've obtained the notification_id using F12 developer tools in the browser using the network tab.
My automation now looks like this:
alias: 'System: Somfy workaround: reload configuration if device becomes unavailable'
description: ''
trigger:
  - platform: state
    entity_id: cover.achtertuin (replace with one of your Somfy devices)
    to: unavailable
    for:
      hours: 0
      minutes: 5
      seconds: 0
      milliseconds: 0
condition: []
action:
  - service: homeassistant.reload_config_entry
    data: {}
    target:
      entity_id: cover.achtertuin (replace with one of your Somfy devices)
  - service: persistent_notification.dismiss
    data:
      notification_id: config_entry_reconfigure
mode: single

There is no way of knowing that this notification relates to the Overkiz integration, so if another integration needs reconfiguration, this information is lost.
Also, when I navigate to Integrations, a reconfigure message still appears, and I haven't found any way to dismiss or disable this (error) message.

#10926

I'd suggest to reformulate that to an issue, and not a question..... then issue is that when entering correct data, the Call Service button remains greyed-out.
All your other  IDK's are prone to be ignored, or re-directed to the community

I'd suggest to reformulate that to an issue, and not a question..... then issue is that when entering correct data, the Call Service button remains greyed-out.

Thanks. I changed it.

my somfy connection just crapped out once again and came back again after exactly 5 minutes when the automation kicked in and triggered homeassistant.reload_config_entry. so the bug for this function seems to be only HA GUI related and not code related. i'll now lower the timeout to 1.5 minutes and see what happens then

my somfy connection just crapped out once again and came back again after exactly 5 minutes when the automation kicked in and triggered homeassistant.reload_config_entry. so the bug for this function seems to be only HA GUI related and not code related. i'll now lower the timeout to 1.5 minutes and see what happens then

Same thing here. The automation got the Entries reporting again at 12:46 CET today. Even if HA still reports “ Integration requires reconfiguration”.

so the bug for this function seems to be only HA GUI related and not code related.

Let me write down the issue here, so everyone understands what we are facing and why we didn't come up with a quick solution yet:

Somfy sometimes returns  {"errorCode": "AUTHENTICATION_ERROR", "error": "Bad credentials"}, which would normally mean that the credentials aren't correct. However, they also return this error when they have service issues as we have noticed in the past.

Before we catched this error, users would be ip-banned / blocked when Somfy returns this error. The issue with this Bad Credentials error is that when you keep trying at that moment (while they have issues), they will ip ban you and this ban will only be lifted if you stop accessing the server for a day or so.
(see #466 and #420)

In other to prevent users from getting banned and complying to Home Assistant standards relating to reauth, we have implemented the mechanism that will ask to enter your credentials again, when Somfy tells us that your credentials aren't correct anymore.

This last change is causing these issues lately and we need to contact Somfy about this. Theoretically we could write a lot of safe guards to see if we can prevent this behavior, but everything will be a hack unless Somfy decides to throw a different error when they are facing issues with the service.
And please, only reply here when you have additional information or workarounds to add. This is a known issue and it doesn't make sense to reply that you have the same issue.

I have temporarily removed the code that will prompt for reauthentication. This means that there is a chance that you will get a temporary ban (which will be lifted if you stop calling the service from HA for a day or so). It will retry on invalid authentication.
You can download https://github.com/iMicknl/ha-tahoma/archive/refs/heads/fix/temporary_reauth_fix.zip. Extract this file and place custom_components/tahoma in your custom_components folder.
Hopefully we will have an answer from Somfy soon.

Is this fixed by Somfy? At least for my setup (homebridge plugin instead of HA) I noticed no errors for the last 24hours+

Is this fixed by Somfy? At least for my setup (homebridge plugin instead of HA) I noticed no errors for the last 24hours+

I'm on the latest release and am still experiencing this problem with Somfy

I'm also experiencing this problem. (just had it happen after over a week since the last time)

We haven't received a response from Somfy yet, and unfortunately it seems that the of the issue is back. This has been reported by the HomeBridge integration as well :(.
We will keep you updated.
First occurred: December 25, 2021, 3:53:59 PM (3 occurrences)
Last logged: 6:37:26 PM

Authentication failed while fetching device events data: Bad credentials

Could you give https://github.com/iMicknl/ha-tahoma/archive/refs/heads/fix/temporary_reauth_fix.zip a try? Extract this file and place custom_components/tahoma in your custom_components folder.
I have posted this version already 17 days ago, however I haven't had any feedback if this works around the issue for now. See https://github.com/iMicknl/ha-tahoma/issues/599#issuecomment-997449439 for more context.
I will unlock this issue for now, please don't reply with +1 that you have the same issue. Happy to gather feedback if the new version works or not. If someone posted the same reply already, you can use thumbs up and thumbs down to add your votes.

@iMicknl - happy to give this a try but one question before I do, having installed using HACS originally, could dropping this on my instance (over the HACS installed version) cause any issues that could prevent HACS from managing this version (that you know)? I can backup of course but worth asking. Thanks.

You can just install this over the HACS installed version. When there is a new update, you can still install it from HACS.

I just want to add in the following. I have had great results with this solution for the past few month.
I created a command line sensor with the following:
- platform: command_line
  name: Error Overkiz Integration
  scan_interval: 600
  command: 'check=`cat /config/home-assistant.log | grep -ic "Authentication failed while fetching device events data: Bad credentials"`; if [ $check -gt 0 ]; then echo on; else echo off; fi'

This sensor is monitored by NodeRed. When the sensor switches to "on" (and stays on for 10 minutes) the following flows executes:

The 10m delay is for not directly trying a reload config entry just after the connecting failed.
The "reload config" node reload any cover entity, the "clear log" node is a shell command to clear the HA log, the "clear system log" node clears the HA log file completely, the last node reload the command line sensor integration to switch the Overkiz error sensor back to "off".
The 1m throttle is to prevent any uncontrolled toggling and can be dismissed...perhaps.
The only drawback is, that the integration keeps showing, that it has to be reauthenticated in the integration overview. But I get a notification via pushover anyway, so i can just restart HA when i feel like. The notifiaction can easily be coupled to the error sensor. The problem for me before was, that when the re-authentication issue happened overnight all covers won't open in the morning. With this solution it never happened again.
I know that this is some kind of quick and dirty hack, but maybe it helps someone.
This is the flow:
[
    {
        "id": "8109c1a9556b8d04",
        "type": "tab",
        "label": "overkiz",
        "disabled": false,
        "info": "",
        "env": []
    },
    {
        "id": "55d4f48bea785fe7",
        "type": "api-call-service",
        "z": "8109c1a9556b8d04",
        "name": "Reload Config entry",
        "server": "d03fc0aa.7f6a18",
        "version": 3,
        "debugenabled": false,
        "service_domain": "homeassistant",
        "service": "reload_config_entry",
        "entityId": "cover.kuche",
        "data": "",
        "dataType": "jsonata",
        "mergecontext": "",
        "mustacheAltTags": false,
        "outputProperties": [],
        "queue": "none",
        "x": 400,
        "y": 380,
        "wires": [
            [
                "5b86181bdb7738b0"
            ]
        ]
    },
    {
        "id": "e76963e3891cfcc4",
        "type": "server-state-changed",
        "z": "8109c1a9556b8d04",
        "name": "Overkiz error in log",
        "server": "d03fc0aa.7f6a18",
        "version": 3,
        "exposeToHomeAssistant": false,
        "haConfig": [
            {
                "property": "name",
                "value": ""
            },
            {
                "property": "icon",
                "value": ""
            }
        ],
        "entityidfilter": "sensor.error_overkiz_integration",
        "entityidfiltertype": "exact",
        "outputinitially": false,
        "state_type": "str",
        "haltifstate": "on",
        "halt_if_type": "str",
        "halt_if_compare": "is",
        "outputs": 2,
        "output_only_on_state_change": true,
        "for": "25",
        "forType": "num",
        "forUnits": "minutes",
        "ignorePrevStateNull": false,
        "ignorePrevStateUnknown": false,
        "ignorePrevStateUnavailable": false,
        "ignoreCurrentStateUnknown": false,
        "ignoreCurrentStateUnavailable": false,
        "outputProperties": [
            {
                "property": "payload",
                "propertyType": "msg",
                "value": "",
                "valueType": "entityState"
            },
            {
                "property": "data",
                "propertyType": "msg",
                "value": "",
                "valueType": "eventData"
            },
            {
                "property": "topic",
                "propertyType": "msg",
                "value": "",
                "valueType": "triggerId"
            }
        ],
        "x": 350,
        "y": 300,
        "wires": [
            [
                "2a2d593bf155695f"
            ],
            []
        ]
    },
    {
        "id": "5b86181bdb7738b0",
        "type": "api-call-service",
        "z": "8109c1a9556b8d04",
        "name": "clear log",
        "server": "d03fc0aa.7f6a18",
        "version": 3,
        "debugenabled": false,
        "service_domain": "shell_command",
        "service": "clear_log",
        "entityId": "",
        "data": "",
        "dataType": "jsonata",
        "mergecontext": "",
        "mustacheAltTags": false,
        "outputProperties": [],
        "queue": "none",
        "x": 600,
        "y": 380,
        "wires": [
            [
                "c144230dd0f28ec8"
            ]
        ]
    },
    {
        "id": "c144230dd0f28ec8",
        "type": "api-call-service",
        "z": "8109c1a9556b8d04",
        "name": "clear system log",
        "server": "d03fc0aa.7f6a18",
        "version": 3,
        "debugenabled": false,
        "service_domain": "system_log",
        "service": "clear",
        "entityId": "",
        "data": "",
        "dataType": "jsonata",
        "mergecontext": "",
        "mustacheAltTags": false,
        "outputProperties": [],
        "queue": "none",
        "x": 400,
        "y": 460,
        "wires": [
            [
                "45ac50c61d1d1893"
            ]
        ]
    },
    {
        "id": "45ac50c61d1d1893",
        "type": "api-call-service",
        "z": "8109c1a9556b8d04",
        "name": "command line sensor reload",
        "server": "d03fc0aa.7f6a18",
        "version": 3,
        "debugenabled": false,
        "service_domain": "command_line",
        "service": "reload",
        "entityId": "",
        "data": "",
        "dataType": "jsonata",
        "mergecontext": "",
        "mustacheAltTags": false,
        "outputProperties": [],
        "queue": "none",
        "x": 640,
        "y": 460,
        "wires": [
            []
        ]
    },
    {
        "id": "2a2d593bf155695f",
        "type": "throttle",
        "z": "8109c1a9556b8d04",
        "name": "1m throttle",
        "throttleType": "time",
        "timeLimit": "1",
        "timeLimitType": "minutes",
        "countLimit": 0,
        "blockSize": 0,
        "locked": false,
        "x": 550,
        "y": 300,
        "wires": [
            [
                "55d4f48bea785fe7"
            ]
        ]
    }
]

great idea, if not using Node Red, you could also use system_log_event to initiate an automation, which would make it event sensitive, instead of the brute force time_pattern:
  - alias: Reload Tahoma integration
    id: Reload Tahoma integration
    mode: restart
    trigger:
      - platform: event
        event_type: system_log_event
        event_data:
          level: ERROR
        id: Error
    condition:
      condition: or
      conditions:
        - >
          {{'[custom_components.tahoma] Authentication failed while fetching device events data: Bad credentials'
            in trigger.event.data.message[0]}}

It would also prevent the need to clear the logs, or reset any sensor.

I like this attempt, but would rather stay with NodeRed. Would this also work:

It's hard to test because I have no idea how to provoke the reconfiguration error for testing.

not using Node-red myself, so I wouldn't know really, but looking at the field options, I would say the Event type needs to change to system_log_event ?
Also, in Jinja, we need the message[0] because thats the way the data is built. Again, not sure if Node-red manipulates data differently , so you'd have to experiment or ask users with more experience... sorry for not being able to answer you in that regard.

No problem, thanks anyway for the hint. This is off-topic here anyway. I will try to figure it out, but I guess NodeRed is not the way to go here.

Could you give https://github.com/iMicknl/ha-tahoma/archive/refs/heads/fix/temporary_reauth_fix.zip a try? Extract this file and place custom_components/tahoma in your custom_components folder.
I have posted this version already 17 days ago, however I haven't had any feedback if this works around the issue for now. See #599 (comment) for more context.
I will unlock this issue for now, please don't reply with +1 that you have the same issue. Happy to gather feedback if the new version works or not. If someone posted the same reply already, you can use thumbs up and thumbs down to add your votes.

I have just replaced the files in the Tahoma folder as stated. I have had the issue a handful of times the recent weeks - just today too.
Will get back in a weeks time with an update :-)

Hi
I also replaced the code by the one containing the auth fix and somfy had a hiccup again today. Good thing is, the integration now does not require reconfiguration after crapping out, however my automation still triggered a reload at 10:27:13.
Devices went offline at 10:25:43 and came back at 10:27:16 as shown in the debug logs below.
2022-01-11 10:25:04 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.214 seconds (success: True) 2022-01-11 10:25:43 ERROR (MainThread) [custom_components.tahoma] Error fetching device events data: Invalid authentication. 2022-01-11 10:25:43 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 9.732 seconds (success: False) 2022-01-11 10:26:13 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.236 seconds (success: False) 2022-01-11 10:26:43 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.250 seconds (success: False) 2022-01-11 10:27:14 ERROR (MainThread) [custom_components.tahoma] Unexpected error fetching device events data: Session is closed Traceback (most recent call last): File "/config/custom_components/tahoma/coordinator.py", line 75, in _async_update_data events = await self.client.fetch_events() File "/usr/local/lib/python3.9/site-packages/backoff/_async.py", line 133, in retry ret = await target(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/pyoverkiz/client.py", line 398, in fetch_events response = await self.__post(f"events/{self.event_listener_id}/fetch") File "/usr/local/lib/python3.9/site-packages/pyoverkiz/client.py", line 516, in __post await self.check_response(response) File "/usr/local/lib/python3.9/site-packages/pyoverkiz/client.py", line 554, in check_response raise NotAuthenticatedException(message) pyoverkiz.exceptions.NotAuthenticatedException: Not authenticated During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh self.data = await self._async_update_data() File "/config/custom_components/tahoma/coordinator.py", line 91, in _async_update_data await self.client.login() File "/usr/local/lib/python3.9/site-packages/pyoverkiz/client.py", line 144, in login await self.register_event_listener() File "/usr/local/lib/python3.9/site-packages/pyoverkiz/client.py", line 379, in register_event_listener response = await self.__post("events/register") File "/usr/local/lib/python3.9/site-packages/pyoverkiz/client.py", line 511, in __post async with self.session.post( File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 1138, in __aenter__ self._resp = await self._coro File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 399, in _request raise RuntimeError("Session is closed") RuntimeError: Session is closed 2022-01-11 10:27:14 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 1.346 seconds (success: False) 2022-01-11 10:27:16 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.030 seconds (success: True)

I have the same problem, sometimes it's several times a day, I have to re-authenticate myself, Madam starts to get angry with the home automation when the shutters do not close automatically at night, please correct this problem, thank you very much

@xekil please read this thread before you reply. Try our temporary version and report if that works.
Otherwise I will lock this thread again and just post updates here..

@iMicknl I'm facing the same re-authentication issue. I'll download the ZIP linked above & give it a go.

I have been running the tempoary version the last 4 days with success. No re-auth errors and devices has been triggered as expected in all cases.
Thank you for the fix so far :-)

I have the temporary fix installed and got a reauth error 10 minutes ago - after 4 days, previously it was failing every 1-2 days

@themaninspain do you reboot your Home Assistant often? You can only get the reauth dialog when Home Assistant starts currently, if your home assistant did start and log in correctly, it will keep retrying when Somfy throws Bad Credentials.

I restarted HA yesterday because of some updates to other integrations that required it

I have also a question. I use an automation to check if there are problems with the Tahoma. The automation is started from HA and the action is done in Node-RED.
The problem is that it is not triggered from HA. When I manual start the action in Node-RED, the integration is succesfully reloaded and all of my covers are working.
Does anybody know what is wrong with my trigger automation?
- id: '1641450175671'
  alias: Reload Tahoma Integration
  description: ''
  trigger:
  - platform: event
    event_type: system_log_event
    id: Error
    event_data:
      level: ERROR
  condition:
  - condition: state
    entity_id: cover.do_not_use_05_hal_1e_etage
    state: '{{''[custom_components.tahoma] Authentication failed while fetching device
      events data: Bad credentials'' in trigger.event.data.message[0]}}'
  action:
  - service: nodered.trigger
    data:
      entity_id: switch.reloadtahomaintegrationswitch
  mode: single

This is wat is logged in the logbook:
2022-01-11 10:25:54 ERROR (MainThread) [custom_components.tahoma] Authentication failed while fetching device events data: Bad credentials

Deze fout is ontstaan door een aangepaste integratie.

Logger: custom_components.tahoma
Source: helpers/update_coordinator.py:227
Integration: Overkiz (by Somfy)
First occurred: 10:25:54 (1 occurrences)
Last logged: 10:25:54

Authentication failed while fetching device events data: Bad credentials

Trying to provide my input in an attempt to help corner the issue.
I have not yet used the temporary patch provided by @iMicknl. I'm restarting HA whenever there is a new release of an integration in HACS or HACS itself (avg. 1/week) and after a monthly upgrade of HA as a whole at end of month.
At my end, the number of errors asking for reconfiguration have been a bit less, but still happening every few days.

I have been running the temporary version with success. Today I got a "Error fetching device events data: Invalid authentication." message but no re-authentication needed. So it seems the fix is working!

Please update to V2.11 which includes the temporary fix.
Remove any reload logic that you have applied via automations / node-red, since the error is still in the log and thus a reload will trigger the reauth again.

A week later I can also confirm that the fix seems to be working.
I had the "Invalid authentication" error today, but the integration was restored and all blinds has been functioning flawlessly since the temporary fix was installed.

I updated the integration yesterday and the issue reappeared, but now I can't reauthorize it anymore.

Had the same problem as @sdebruyn, but I've now been able to reauthorize.

I updated the integration yesterday and the issue reappeared, but now I can't reauthorize it anymore.

This could be caused by the reason why we implemented the reauth dialog in the first time. Disable the integration for a while and try again, you are probably temporarily banned for using the wrong credentials.
We are working on a more definitive fix, however in the mean-time we just need to hope that the server will become more stable.

I just tried again and now I can reauthenticate again.

@mstuij this is a known issue unfortunately, the only thing you can do now is disable the integration and wait.

@mstuij this is a known issue unfortunately, the only thing you can do now is disable the integration and wait.

Yes I know but I wanted to share my experience with the fix version of this problem.

I'm afraid that I'm also banned for some time by Somfy. I have posted it on discord channel.
My covers were now for 2 hours unavailable (Somfy Tahoma app still works).
So I decided to reboot Home Assistant. Then I get the notification that some integration was not working (the ha-tahoma).
So I needed to re-enter my credentials and now I get the message: "Invalid authentication"

I also have this problem.

After working perfectly well for a week, I am unable to log in using either the integration or the mobile app. Something tells me that Somfy is having a problem rather than it being an issue with the integration. imho.
If i navigate to the Tahomalink.com site and attempt to log in, I get a "server error" message.
The response code is a 401 but the specific error is:
{ "errorCode": "RESOURCE_ACCESS_DENIED",  "error": "Cannot use JSESSIONID and bearer token in same request" }
This is their website, nothing to do with me, the integration or whichever IP I attempt to log in from. Either they've blocked the account itself and are sending an irrelevant message back rather than "you're banned" or they're having a bad day.
As mentioned, the app is also not working for me.

yup, Tahoma link is down here as well.

They have some trouble currently: https://twitter.com/Somfyfr/status/1481903321858387968
That’s the correct timing to ask for a local API :D

Given this instability I really regret having bought the way overpriced Connexoon already :( (No complaint to you guys, but to Somfy)
But, I cannot temporarily disable the integration when it is in "Attention required" mode. But I guess in this mode it will also not try to login continuously, or would it?

Given this instability I really regret having bought the way overpriced Connexoon already :( (No complaint to you guys, but to Somfy)
But, I cannot temporarily disable the integration when it is in "Attention required" mode. But I guess in this mode it will also not try to login continuously, or would it?

I agree with you, I also would have chosen a different gate opener if I had know about Somfy's terrible service.
Regarding disabling the integration, I had the same issue, if you look at the integrations screen within HA config you should have the "attention required" but there will also be the Overkiz integration (shows up with the rest of your installed integrations) which you can disable

Oh yeah indeed, thanks a lot. Has that 2nd entry been there all the time, never noticed it?

Oh yeah indeed, thanks a lot. Has that 2nd entry been there all the time, never noticed it?

No, the warning is separate from the integration itself. Once you dismiss the warning only the integration shows up.

OK, I see, thanks once more.

Just came across this thread about replacing the somfy box with a velux klf-200 which has a local API and can also talk to somfy motors. I think, I'll give this one a try as it does not rely on a rather unstable cloud service.
https://community.home-assistant.io/t/velux-klf-200-pairing-with-somfy-io-motors-and-remotes/248075/14

Unfortunatelly, KLF-200 can't speak with climate sensor so it need a Connexoon box or using TaHoma just for that..

What I have heard is that KLF200 also has some troubles.
I think we will have to wait till one day Somfy has added local support or you have to jailbreak your Tahoma (look at this topic)

For me, the mobile/phone application is now working again as is the Overkiz integration.

Same problem for me, every day I need to re-setup the app. I've a Tahoma Switch.
If anyone have an idea.. ?

Same problem for me, every day I need to re-setup the app. I've a Tahoma Switch.
If anyone have an idea.. ?

Please read this issue before you reply to it... If you would scroll up, you would have an idea why you face this.
You can find more context about the current issues in https://github.com/iMicknl/ha-tahoma/issues/599#issuecomment-995825550. We are currently testing an alternate solution and hopefully this will solve this issue..
Please don't reply to this thread with your "+1, I am facing the same issue". I would like to keep this (already way too long) issue thread open for new comments, but otherwise we will lock it again and just broadcast the news here.

Same problem for me, every day I need to re-setup the app. I've a Tahoma Switch.
If anyone have an idea.. ?

Please read this issue before you reply to it... If you would scroll up, you would have an idea why you face this.
You can find more context about the current issues in #599 (comment). We are currently testing an alternate solution and hopefully this will solve this issue..
Please don't reply to this thread with your "+1, I am facing the same issue". I would like to keep this (already way too long) issue thread open for new comments, but otherwise we will lock it again and just broadcast the news here.

Sorry, i've seen the message after. My comment is deleted :)

Just did a little digging as this is a great service and problem caused my bathroom window to be left open overnight - not good given temperature and price of gas!  Sharing my thoughts:
As a workaround hack, it's very easy to setup an automation that triggers "Call service" with "Home AssistantCore Integration: Restart" in the UI every day.  Someone has a video talking you through that here.
Longer term, looks like the server is using an old web scheme (JSESSION) where client is unaware of token expiration time.  This has now been combined with a short token lifetime so client appears to need to send username and password whenever server throws wobbly, currently set to every 24 hours.  That's a bit annoying.  I'd suggest increasing the timeout in the short term (maybe 7 or 24 days) , then changing to a modern auth scheme (OAuth & refresh token).
Short term, I get why it will take a few days to test the fix.  Thank you and we will try to be patient :)

@egoward you are spot on. The move to OAuth is indeed what we are currently investigating, since Somfy moved their mobile app to this login method. They didn't move tahomalink.com yet (?). However, even with OAuth it won't be ideal probably since:

You can only pass the auth token to the login() endpoint, which means you need to (re)register the event listener.
The token is valid for an hour (3600s), however in my initial tests it seems that the session will live longer.

For now, my temporary solution was to use OAuth for the login, and just relogin when we get an Unauthorized exception, just like we do now. It seems that the OAuth server is way more stable and thus BadCredentials shouldn't be thrown anymore.
It seems you are quite technical, would you like to contribute and test as well?

Thanks @iMicknl, sounds like a great temporary solution.  I am technical but pretty bad with python so my code contributions will likely not be very welcome.  Very happy to take test patches on my home setup and will also see if I can get a dev HA setup going so I can be more help.

@iMicknl with auth token isn't there also a refresh token? If so, what is the lifespan for it? In many cases (also mobile apps) uses refresh token that lasts longer than 1 hour. So in case your auth token is gone, you can still refresh it (generate new auth token) with refresh token.
I'm not an python dev, but if you point me to the code where you are doing the stuff with auth maybe I can help. I'm using python in few scripts also with oauth.

@bilak feel free to join us on Discord to discuss development and see https://github.com/iMicknl/python-overkiz-api/issues/321 for the underlying library.
And you are right, it seems possible to not use the /login endpoint to create a session, but just pass the auth bearer to every request (and thus use the refresh token as well).

Update
We have an early test version available that could possibly fix the issues. It would be great if you could give it a try and let us know if you face any issues with the reauth message.
https://github.com/iMicknl/ha-tahoma/archive/refs/heads/enhancement/move_somfy_oauth.zip. Extract this file and place custom_components/tahoma in your custom_components folder.

Please update to v2.12.0 and report back (in a new issue), if you face any issues. Let's close this huge and unclear issue. Thanks all for reporting and looking for workarounds.


Update sprite.js

I;m going to drop this, it doesn't look more readable, I think.

@XhmikosR or we can add eslint-ignore?


Tests: Added some tests for the dataloader

Dataloader Tests
Tests check if the output arrays are correct and if some errors are raised when wrong inputs are given to the dataloader.
Dataloader Speedup
Added manual caching of Dataset locally so it's way quicker when loading.
Function Descriptions
Cleaned them up a bit and expanded

Anyone have any ideas how to make the dataset available to the tests?
Maybe we can give it a fake dataset or something or a shortened version. @mlederbauer what do you think?

HI Tiago! Many thanks for looking into this! We could provide a “dummy dataset” of the first 3 lines of the real dataset, and provide the model with this. I’ll take a look and contribute to the branch if I find it

The error stems likely from the fact that one needs to be authenticated to access the dataset, the “test entity” is not an authenticated user. A dummy dataset, as you say, would be the best approach here

Yeah, I was thinking about passing one of my keys to the hfrepo but I guess the data is sensitive enough that this shouldn't be done. I will do something with a dummy dataset.

Okay; this is weird, as the tests pass locally when running make test, but not on the github workflow here (it’s already a very good sign, but let’s aim to get the green checkmark on Github as well)

Don't worry, its very expected as the dataloader has a function that loads from huggingface and that is dependent on having completed the login to huggingface. As this is not possible, as the test suite kinda sets up its own environment without access to the login token, it won't be able to get the dataset to do the tests. To circumvent this, assuming the dataset won't change, I implemented a test flag to the dataloader, so it loads a dummy test-set with only 5 rows of the original and it doesn't need to access huggingface. Also added this dummy test-set to the public repo.

Is it ready to create a PR and merge? @tiaguinho-code

@mlederbauer was thinking about adding some more tests first, but in principle it already works

Okay perfect, thank you! Let me know if there’s anything to review or discuss!

Ran out of ideas for tests, if the dataloader breaks these will definetly fail.


New release

Could someone please release this plugin?
We really need the feature you merged 2 weeks ago to migrate to Gradle.

This is available in 1.0.3

Thanks! :heart:


Illegal instruction on Chem.MolFromSmiles

Hello,
When using MolFromSmiles function, I get "Illegal instruction" error for some "smile" values:
from rdkit import Chem
print(Chem.MolFromSmiles('C1NCN1.C1NCN1'))
print(Chem.MolFromSmiles('CC1CCCCC1'))
print(Chem.MolFromSmiles('Cc1ccccc1'))
print(Chem.MolFromSmiles('CC1=C(C(=CC=C1)NC2=CC=CC=C2C(=O)O)C'))
and the output is:
<rdkit.Chem.rdchem.Mol object at 0x7fa989a42170>
<rdkit.Chem.rdchem.Mol object at 0x7fa989a42170>
Illegal instruction
When I remove the third print I get the same error on the last line.
I was expecting to get a rdkit object but got an error.
RDKit version: 2020.09.4
OS: Ubuntu 20.04
Python version (if relevant): 3.8.5
Are you using conda? : Yes
If you are using conda, which channel did you install the rdkit from? : conda-forge
Thanks

The issue template asks you a series of questions that make it easier for us to help.
The fact that you've either deleted those or only answered a subset of them makes it more difficult for us to help, so I'm closing this issue.
Please feel free to edit the issue description to include the requested information and reopen the issue and then we'll try to help.

How can I reopen @greglandrum ? Thanks.

No there is not a button like that. May be it's because of I'm not the one closing the topic. Should i open another issue or can you reopen it ?
**

you cannot re-open your own issues if a repo collaborator closed them

**
https://stackoverflow.com/questions/21333654/how-to-re-open-an-issue-in-github

Thanks for the additional info.
I am unable to reproduce this on ubuntu 20.04 using the conda-forge install of the RDKit.
Are you sure that this is exactly the script that you ran?
from rdkit import Chem
print(Chem.MolFromSmiles('C1NCN1.C1NCN1'))
print(Chem.MolFromSmiles('CC1CCCCC1'))
print(Chem.MolFromSmiles('Cc1ccccc1'))
print(Chem.MolFromSmiles('CC1=C(C(=CC=C1)NC2=CC=CC=C2C(=O)O)C'))

@greglandrum Thanks for your answer.
Yes that's exatly the same one that I ran. There are no missing or extra lines.

Could you give us the results of
lscpu
In case it’s a cpu instruction issue?

Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    2
Core(s) per socket:    2
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 54
Model name:            Intel(R) Atom(TM) CPU N2800   @ 1.86GHz
Stepping:              1
CPU MHz:               919.286
CPU max MHz:           1862.0000
CPU min MHz:           798.0000
BogoMIPS:              3733.16
L1d cache:             24K
L1i cache:             32K
L2 cache:              512K
NUMA node0 CPU(s):     0-3
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm dtherm arat

I expect the issue might be you are running an intel atom which doesn’t support AVX.  This is very tough for us to test as we don’t have that particular hardware.

Brian Kelley

On Feb 15, 2021, at 10:44 AM, Gökhan Tahıl<EMAIL_ADDRESS>wrote:

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 54
Model name: Intel(R) Atom(TM) CPU N2800 @ 1.86GHz
Stepping: 1
CPU MHz: 919.286
CPU max MHz: 1862.0000
CPU min MHz: 798.0000
BogoMIPS: 3733.16
L1d cache: 24K
L1i cache: 32K
L2 cache: 512K
NUMA node0 CPU(s): 0-3
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm dtherm arat
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Yeah, I think this is a conda-forge thing. I will transfer the issue there (if I can)

Thank you so much. I will be waiting for more information. Normally I would expect at least the two lines below to give the same result.
print(Chem.MolFromSmiles('CC1CCCCC1'))
print(Chem.MolFromSmiles('Cc1ccccc1'))
It is really interesting.

Maybe one can emulate the missing instruction through QEmu virtualization?

Closing this because it's not actually an RDKit bug.


[WIP][SPARK-38904] Select by schema

Almost copy pasting from https://issues.apache.org/jira/browse/SPARK-38904:
This PR is related to https://stackoverflow.com/questions/71610435. Let's assume I have a pyspark DataFrame with certain schema, and I would like to select/overwrite that schema with a new schema that I know is compatible, I could do:
df: DataFrame
new_schema = ...

df.rdd.toDF(schema=new_schema)

Unfortunately this triggers computation as described in https://stackoverflow.com/questions/37088484/whats-the-performance-impact-of-converting-between-dataframe-rdd-and-back/37090151#37090151.
Note:

the schema can be arbitrarily complicated (nested etc)
new schema includes updates to description, nullability and additional metadata

See POC of workaround/util in https://github.com/ravwojdyla/spark-schema-utils
Also posted in https://lists.apache.org/thread/5ds0f7chzp1s3h10tvjm3r96g769rvpj
What changes were proposed in this pull request?

add DataFrame.select(schema)

Why are the changes needed?

add DataFrame.select(schema)

Does this PR introduce any user-facing change?

yes DataFrame.select(schema)

👋 @HyukjinKwon I'm a little blocked on what's the best way to enforce compatibility of nested columns, do you have any hits please? Also any other comments about the current WIP? Would appreciate your input.

Can one of the admins verify this patch?

@jiangxb1987 who were interested in this.

Seems like https://github.com/apache/spark/pull/37011 will supersede this PR

Seems like https://github.com/apache/spark/pull/37011 will supersede this PR

@HyukjinKwon that's great, thank you! First of all I appreciate the work that went into #37011 and I'm excited to use. I would like to ask for future reference, what's the actual process for PRs/changes/collaboration from the community? This is the 2nd time this is happening where I submit a PR, there's some response and then someone from Databricks submits their own (arguable better) version. The other PR was https://github.com/apache/spark/pull/34863. FYI @cloud-fan @zero323

In https://github.com/apache/spark/pull/34863 case, I slept through my fingers. I think yours had to be merged. I am sorry that was my bad.
This and https://github.com/apache/spark/pull/37011 cases are a bit different because the implementation and approach are pretty much different. I usually put the author of the first PR as a co-author for the sake of respecting the efforts made but technically the authorship of the fix has to be to the one who proposed the different approach IMO.
This isn't specific to a specific company, see also https://github.com/apache/spark/pull/36917.

@HyukjinKwon thanks for the response.

This and https://github.com/apache/spark/pull/37011 cases are a bit different because the implementation and approach are pretty much different. I usually put the author of the first PR as a co-author for the sake of respecting the efforts made but technically the authorship of the fix has to be to the one who proposed the different approach IMO.

Interesting, so you don't expect collaboration? I've marked this PR as WIP, because I wasn't married to this specific implementation. And it was the collaboration that I was hoping for when asking for guidance in https://github.com/apache/spark/pull/36430#discussion_r863267242 (comment above), such that we can find a solution that works best for me, community and Databricks.
At the end of the day I'm excited to see this functionality in Spark, and I'm excited for #37011, will give it a try and provide comments in the other PR if I have any. I'm closing this.

Interesting, so you don't expect collaboration? I've marked this PR as WIP, because I wasn't married to this specific implementation.

How did you reach to that conclusion? I was explaining what happened this and that PR. Collaboration is great but I don't expect contributors or committers know what's going on in every single PR.
I myself didn't find the time to take a closer look of your PR but another contributor spent more time to propose a complete version.
Do you expect that proposal to be rejected and yours have to be reviewed?

Do you expect that proposal to be rejected and yours has to be reviewed?

@HyukjinKwon ofc not, from previous comment:

At the end of the day I'm excited to see this functionality in Spark, and I'm excited for https://github.com/apache/spark/pull/37011, will give it a try and provide comments in the other PR if I have any. I'm closing this.

Oh, I didn't know this PR before submitting https://github.com/apache/spark/pull/37011 . However, I think this PR is still a draft and https://github.com/apache/spark/pull/37011 is much more ready-to-merge.
Conflicting PRs are inevitable as no one can know all the ongoing work. Usually, the first PR wins, but if the approaches are very different, the better version wins.


Event chain support for the same event?

I just wonder if we can register multiple functions on the same event. And there is some chain logic. for example

Event -> fn1 -> fn2

The chain will stop if any of the function in the chain accepts the event.
@app.event("app_mention")
def fn1(event):
    ...

@app.event("app_mention")
def fn2(event)
   ...

Hi @chunyang-wen, thanks for writing in!
Unfortuantely, bolt-python does not support multiple listeners for the same event / constraints. If you would like to have multiple functions to run for a single event, please consider having internal functions and call them in a listener. If it's fine to run those concurrently, using lazy listeners for those would be an option too. The document says it's mainly for FaaS use cases but it's available for non-FaaS apps too.

it seems that middleware can help. There is a next function call or we can use the matcher parameter

Yeah, a giant global middleware can work for your use case. The built-in middleware for custom workflow steps actually works in such a way: https://github.com/slackapi/bolt-python/blob/main/slack_bolt/workflows/step/step_middleware.py
Do you have anything else to discuss on this topic? If not, would you mind closing this issue?


Complete padder proofs

On top of #925 (will be marked draft until #925 is merged).
Padder proofs are now done except for a few lemmas that are not padder-specific (they're only about N, bytes, nat, etc). The full output from Print Assumptions is:
nth_firstn
  : forall (A : Type) (i n : nat) (d : A) (l : list A),
    nth i (firstn n l) d = (if i <? n then nth i l d else d)
nth_bytes_to_Ns
  : forall (i n : nat) (bs : list byte),
    nth i (BigEndianBytes.bytes_to_Ns n bs) 0%N =
    BigEndianBytes.concat_bytes (List.map (fun j : nat => nth (i * n + j) bs "000"%byte) (seq 0 n))
ceiling_range : forall a b : nat, 0 < b -> 0 < a -> Nat.ceiling a b * b - b < a <= Nat.ceiling a b * b
ceiling_add_same
  : forall a b c : nat, 1 < c < b - 1 -> a mod b <= b - c -> Nat.ceiling (a + c) b = Nat.ceiling (a + 1) b
ceiling_add_le_mono : forall a b c : nat, Nat.ceiling a b <= Nat.ceiling (a + c) b
ceiling_add_diff
  : forall a b c : nat, 0 < b -> 0 < c < b -> b - c < a mod b -> Nat.ceiling (a + c) b = Nat.ceiling a b + 1
N_to_byte_to_N : forall x : N, Byte.to_N (N_to_byte x) = (x mod 256)%N

I'm pretty confident that all these lemmas are true and not too terrible to prove.

Cool!
Did you consider an alternative definition of ceiling like this one?
Definition ceiling (a b : nat) := (a + b - 1) / b.

Regarding sha256_padder_invariant, could I also think of it as a simulation relation between the low-level state (state : denote_type (Bit ** sha_word ** Bit ** BitVec 4 ** BitVec 61 ** BitVec 16)) and the high-level state (msg : list Byte.byte) (msg_complete padder_done : bool) (index : nat)?

Did you consider an alternative definition of ceiling like this one?
Definition ceiling (a b : nat) := (a + b - 1) / b.

Yes, I'm not sure which will be easier to work with -- but most of the proofs about ceiling are unproven and I don't think I ever unfold it, so changing the definition as is convenient for its proofs should be easy.

Regarding sha256_padder_invariant, could I also think of it as a simulation relation between the low-level state (state : denote_type (Bit ** sha_word ** Bit ** BitVec 4 ** BitVec 61 ** BitVec 16)) and the high-level state (msg : list Byte.byte) (msg_complete padder_done : bool) (index : nat)?

Yes! Like you can see with padder_done, in some cases it's just directly lifting low-level state variables up to the high-level state; then the precondition and output spec are stated relative to the high-level state.
I'm refining this strategy a bit as I go, but it seems to work well so far for reducing complexity in proofs; you can reason about the circuit with whatever high-level representation makes sense instead of unfolding its entire step function.


Add stubbed txindex metadata structs for lockups

Merge activity

Feb 20, 1:23 PM EST: @lazynina started a stack merge that includes this pull request via Graphite.


Add a division function and test

Closes #2
Add a division function and simple test

I have done it. Thanks


Errors not displaying in MacVim

Terminal Vim & NeoVim display errors inline and show details of an error under the cursor. MacVim however displays nothing other than the exit code. This is all using the same vimrc.
Expected behavior
MacVim should show the errors
Neomake debug information
Async support: 1
Current filetype:
Enabled makers
For the current filetype (with :Neomake): []
NOTE: the current buffer does not have a filetype.
For the project (with :Neomake!): []
NOTE: you can define g:neomake_enabled_makers to configure it.
Settings
g:neomake_javascript_enabled_makers = ['eslint']
g:neomake_php_enabled_ma
Steps to reproduce

Output of the ":verb NeomakeInfo" command

#### Neomake debug information
Async support: 1
Current filetype:

##### Enabled makers
For the current filetype (with :Neomake): []
NOTE: the current buffer does not have a filetype.
For the project (with :Neomake!): []
NOTE: you can define g:neomake_enabled_makers to configure it.

##### Settings
g:neomake_javascript_enabled_makers = ['eslint']
g:neomake_php_enabled_makers = ['php', 'phpcs', 'phpmd']

#### :version

NVIM v0.1.6-201-g4408431
Build type: Dev
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -I/tmp/neovim-20161010-51913-14bagjw/build/config -I/tmp/neovim-20161010-51913-14bagjw/src -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/usr/local/opt/gettext/include -I/usr/include -I/usr/include -I/tmp/neovim-20161010-51913-14bagjw/build/src/nvim/auto -I/tmp/neovim-20161010-51913-14bagjw/build/include
Compiled by<EMAIL_ADDRESS>
Optional features included (+) or not (-): +acl   +iconv    +jemalloc +tui
For differences from Vim, see :help vim-differences

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/HEAD-4408431/share/nvim"

#### :messages
NVIM v0.1.6-201-g4408431
Build type: Dev
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -I/tmp/neovim-20161010-51913-14bagjw/build/config -I/tmp/neovim-20161010-51913-14bagjw/src -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/usr/local/opt/gettext/include -I/usr/include -I/usr/include -I/tmp/neovim-20161010-51913-14bagjw/build/src/nvim/auto -I/tmp/neovim-20161010-51913-14bagjw/build/include
NVIM v0.1.6-201-g4408431
Build type: Dev
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -I/tmp/neovim-20161010-51913-14bagjw/build/config -I/tmp/neovim-20161010-51913-14bagjw/src -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/usr/local/opt/gettext/include -I/usr/include -I/usr/include -I/tmp/neovim-20161010-51913-14bagjw/build/src/nvim/auto -I/tmp/neovim-20161010-51913-14bagjw/build/include
NVIM v0.1.6-201-g4408431
Build type: Dev
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -I/tmp/neovim-20161010-51913-14bagjw/build/config -I/tmp/neovim-20161010-51913-14bagjw/src -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/usr/local/opt/gettext/include -I/usr/include -I/usr/include -I/tmp/neovim-20161010-51913-14bagjw/build/src/nvim/auto -I/tmp/neovim-20161010-51913-14bagjw/build/include
NVIM v0.1.6-201-g4408431
Build type: Dev
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -I/tmp/neovim-20161010-51913-14bagjw/build/config -I/tmp/neovim-20161010-51913-14bagjw/src -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/tmp/neovim-20161010-51913-14bagjw/deps-build/usr/include -I/usr/local/opt/gettext/include -I/usr/include -I/usr/include -I/tmp/neovim-20161010-51913-14bagjw/build/src/nvim/auto -I/tmp/neovim-20161010-51913-14bagjw/build/include

#### Neomake debug information
Async support: 1
Current filetype: php

##### Enabled makers
For the current filetype (with :Neomake): ['php', 'phpcs', 'phpmd']
NOTE: you can define g:neomake_php_enabled_makers to configure it (or b:neomake_php_enabled_makers).
For the project (with :Neomake!): []
NOTE: you can define g:neomake_enabled_makers to configure it.

##### Settings

autocmd! BufReadPost,BufWritePost * Neomake
let g:neomake_php_enabled_makers = ['php', 'phpcs', 'phpmd']
let g:neomake_javascript_enabled_makers = ['eslint']

#### :version

VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Oct  7 2016 05:29:54)
MacOS X (unix) version
Included patches: 1-22
Compiled by Homebrew
Huge version without GUI.
Neomake: phpcs: completed with exit code 1.
Neomake: phpmd: completed with exit code 0.

#### Neomake debug information
Async support: 1
Current filetype: php

##### Enabled makers
For the current filetype (with :Neomake): ['php', 'phpcs', 'phpmd']
NOTE: you can define g:neomake_php_enabled_makers to configure it (or b:neomake_php_enabled_makers).
For the project (with :Neomake!): []
NOTE: you can define g:neomake_enabled_makers to configure it.

##### Settings
g:neomake_javascript_enabled_makers = ['eslint']
g:neomake_php_enabled_makers = ['php', 'phpcs', 'phpmd']

#### :version

VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Oct  6 2016 13:25:03)
MacOS X (unix) version
Included patches: 1-3
Compiled by Homebrew
Huge version with MacVim GUI.  Features included (+) or not (-):
+acl             +diff            +jumplist        +mouse_urxvt     +scrollbind      +virtualedit
+arabic          +digraphs        +keymap          +mouse_xterm     +signs           +visual
+autocmd         +dnd             +lambda          +multi_byte      +smartindent     +visualextra
+balloon_eval    -ebcdic          +langmap         +multi_lang      +startuptime     +viminfo
+browse          +emacs_tags      +libcall         -mzscheme        +statusline      +vreplace
++builtin_terms  +eval            +linebreak       +netbeans_intg   -sun_workshop    +wildignore
+byte_offset     +ex_extra        +lispindent      +num64           +syntax          +wildmenu
+channel         +extra_search    +listcmds        +odbeditor       +tag_binary      +windows
+cindent         +farsi           +localmap        +packages        +tag_old_static  +writebackup
+clientserver    +file_in_path    -lua             +path_extra      -tag_any_white   -X11
+clipboard       +find_in_path    +menu            +perl            +tcl             -xfontset
+cmdline_compl   +float           +mksession       +persistent_undo +termguicolors   +xim
+cmdline_hist    +folding         +modify_fname    +postscript      +terminfo        -xpm
+cmdline_info    -footer          +mouse           +printer         +termresponse    -xsmp
+comments        +fork()          +mouseshape      +profile         +textobjects     -xterm_clipboard
+conceal         +fullscreen      +mouse_dec       -python          +timers          -xterm_save
+cryptv          -gettext         -mouse_gpm       +python3         +title
+cscope          -hangul_input    -mouse_jsbterm   +quickfix        +toolbar
+cursorbind      +iconv           +mouse_netterm   +reltime         +transparency
+cursorshape     +insert_expand   +mouse_sgr       +rightleft       +user_commands
+dialog_con_gui  +job             -mouse_sysmouse  +ruby            +vertsplit
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/Applications/MacVim.app/Contents/Resources/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe  -DMACOS_X_UNIX  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: clang   -L. -L/usr/local/lib -L. -L/usr/local/lib  -L/usr/local/lib -o Vim -framework Cocoa -framework Carbon       -lm  -lncurses -liconv -framework Cocoa   -fstack-protector  -L/System/Library/Perl/5.18/darwin-thread-multi-2level/CORE -lperl  -L/usr/local/Cellar/python3/3.5.2_2/Frameworks/Python.framework/Versions/3.5/lib/python3.5/config-3.5m -lpython3.5m -framework CoreFoundation -F/System/Library/Frameworks -framework Tcl -framework CoreFoundation -framework Ruby

#### :messages
Messages maintainer: Bram Moolenaar<EMAIL_ADDRESS>"~/Desktop/test.php" 4 lines, 21 characters
Neomake: phpmd: completed with exit code 127.
Neomake: phpcs: completed with exit code 127.
Neomake: php: completed with exit code 0.

I'll re-open this a little later when I've got the details down correctly.

Use let g:neomake_verbose = 3 to get more details, and watch out for invalid entries being removed.


Improve docs for convertColors

The docs for most of the plugins are… scant.
I was writing a custom plugin when I realized that the convertColors plugin already did what I wanted, but the currentColor param was completely undocumented.
Here's a PR to fix that part of the docs.

Please run "npm run fix"

Thanks for opening the PR and proposing we document this behavior. This has been resolved through publishing documentation svgo.dev.
You can read more about convertColor and the currentColor param here:
https://svgo.dev/docs/plugins/convert-colors/#parameters
Contributions to improve our documentation are welcome! 👍🏽


New package: Surrogates v0.1.0

Registering package: Surrogates
Repository: https://github.com/JuliaDiffEq/Surrogates.jl
Created by: @ludoro
Version: v0.1.0
Commit: ffaaae16039fe84e79936524e721efa65085728a
Git reference: master
Release notes:

First release of Surrogates.jl

SurrogateModels.jl?

Do you think it's better? To me the addition of models seems redundant. Also the package is about sampling methods and optmization methods and not just models. But if you think it's better like that I can change that no problem

What should we do here? Proceed or close this in favor of a different name?

Yeah close please, I will go for SurrogateModels! :)

I'm not sure that makes sense. This isn't a package for Surrogate models, that's one thing. It's Surrogate models, surrogate sampling (AKA design strategies), and surrogate optimization. SurrogateModelsSamplingAndOptimization? That's why I just shortend it to Surragates: it's a package that tries to do everything you can ever think of with surrogates. If you can think of something people commonly do with surrogates that this package cannot do, that is a valid feature request.

(though changing to SurrogateModels.jl would not be the worst change)

My suggestion was just based on the description in the repo which says it is a package for surrogate modeling.
Merge this?

Let's merge!

My suggestion was just based on the description in the repo which says it is a package for surrogate modeling.
I will soon update the docs and the README.md because it must be a bit misleading!


A browser edition

Recently I forked this repo and make it run in browser (Why). And I think the fork can be useful for others. What do you think about it?
BTW, this repo is really awesome!
codemirror demo
my fork

Very cool. Nice work. Put a PR in to show it in our README if you'd like.


Question about hand evaluation.

Hi, I found that there is no evaluation codes in FreiHAND.py. Could you please provide the codes of FreiHAND to calculate MPJPE and PA-MPJPE or provide some reference links? I think FreiHand is needed to see the evaluation results of the second stage which pretrains the hand-only pose2pose.
Looking forward to your reply!

You should use official evaluation server of the FreiHAND dataset: https://competitions.codalab.org/competitions/21238


docs(api): add egghead link to snapshots

Summary
Because it's a handy intro to people new to the concept.
Original PR: https://github.com/facebook/jest/pull/2440
Test plan
N/A

Hmmm, this commit removed the Egghead link: https://github.com/kentcdodds/jest/commit/f4d69fc4bcbc60d9a04276376fab31bd06506814 🤔

I moved it to a more appropriate place in 29285ad59fe29007e456bd236e81040e2f771d8c.

Oh, missed that. Great! Thank you!


Use license in package.json

Array deprecated in<EMAIL_ADDRESS>https://github.com/npm/npm/blob/master/doc/files/package.json.md#license
Should fix license image from shields in the readme as well

Thanks!


Cannot reproduce all examples

Hi,
I'm trying out this tool, so far it's looking good with the default styles.
Then I wanted to try out the given examples (resume, book, etc), however not all documents look the same as in the readme (book and letter), also the slides one just doesn't work, it says : hljs is not defined. Do I need to install another global JS library to make it work?
Example with the book (left is mine, right is git repo) :

Example with letter (pdf on left, html on right which seems ok!) :

For each file I used the following command line:
asciidoctor-pdf <file>.adoc --template-require ./template.js
So I was wondering if I'm missing some parameters in the command line or if the CSS files are not updated to what is seen on the repo.
They seem to have margins specified in it but for the book they just get ignored.
I'm using :

Ubuntu 18.04
Asciidoctor PDF 1.0.0-alpha.3 using Asciidoctor.js 2.0.3 (Asciidoctor 2.0.9)
node 13.1.0.

Can you reproduce the issue?

Duplicate of issue #36, it was the network connection

Duplicate of issue #36, it was the network connection

https://github.com/Mogztter/asciidoctor-pdf.js/pull/113 might improve the situation. We are now using networkidle0 (on master).

networkidle0 - consider navigation to be finished when there are no more than 0 network connections for at least 500 ms.

Yeah I was behind a corporate network blocking most domains...so it's more like what you mentioned in issue #36.

In the next version, the processor will output the warning and error messages from the console. I'm entirely sure that Chrome will output a warning/error message when a ressource is blocked or cannot be fetched but if it's the case you will see the message on your terminal console.

Another note: the current example reflect the latest development in master. If you convert it using the alpha.3-release the output will look different.
Hopefully there will be a alpha.4-soon :-) #96

It did end up looking the same when I used my phone network and not the corporate's.
Anyway I'm happy now, I'll experiment with it more later. I'm looking to customize the title page with a complicated table (typical of a corporate archived document following a defined process) so the template.js capabilities are really interesting me. Seems a lot easier than using a xsl/fop tool chain!


[Bug]: [Sentry] Error   call(sagas/ActionExecution/PluginActionSaga) | APPSMITH-6PF

Is there an existing issue for this?

[X] I have searched the existing issues

Description
sentry error https://appsmith.sentry.io/issues/4305136175
Steps To Reproduce
NA
Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Cloud

Error occurs in PluginActionSagas.ts , where it appears that the collection of js actions sometimes fails to load. Watch the smartlook video attached in sentry for more details.


Readme incorrectly says P key pauses the sim instead of the spacebar

the title sums it up, this issue is more of a trying to get an idea on how git hub issues work rather than actually writing about a big, am just writing words here for the sake of words. This is the second sentence. After further inspection I've made an interesting observation whereby pressing the spacebar would pause the simulation. Maybe consider updating the README and make sure the pause button is clearly stated within the program.

I updated the Readme file in line with this issue.


Assign devices in Snipe

Thank you for writing this.  It doesn't appear to assign devices to users in Snipe if the asset is assigned in JAMF?  Am I understanding this correctly?
If so I can take a look and try and add that functionality.

I guess a large part of that would be that the logged in username would need to match a user in snipe.
Since there's already an endpoint to thee patch request on snipe-it for assigned_to
https://snipe-it.readme.io/reference#hardware-partial-update
I think you just need to add it to the API mapping section.
[api-mapping]
name = general name
_snipeit_mac_address_1 = general mac_address
assigned_to = location username

@syoung-quizlet Can you test that mapping and let me know if it works for you?

Would it be email if our username is just our prefix?  Thanks!
Sean Young
IT Manager @ Quizlet
On Thu, Aug 22, 2019 at 8:44 AM, Brian Monroe <<EMAIL_ADDRESS>> wrote:

I guess a large part of that would be that the logged in username would
need to match a user in snipe.
Since there's already an endpoint to thee patch request on snipe-it for assigned_to
https:/ / snipe-it. readme. io/ reference#hardware-partial-update (
https://snipe-it.readme.io/reference#hardware-partial-update )
I think you just need to add it to the API mapping section.
[api-mapping] name = general name _snipeit_mac_address_1 = general
mac_address assigned_to = location username
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (
https://github.com/ParadoxGuitarist/jamf2snipe/issues/12?email_source=notifications&email_token=AKMSMFXPCWGCSJBGIFZNNZ3QF2X4XA5CNFSM4IMBZ4I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD45QKYI#issuecomment-523961697
) , or mute the thread (
https://github.com/notifications/unsubscribe-auth/AKMSMFQVHJXSMAIGNAQYHV3QF2X4XANCNFSM4IMBZ4IQ
).

Ah I see that isn't pulled in your script (I believe).   I can try and add it or figure it out if needed.
Sean Young
IT Manager @ Quizlet
On Fri, Aug 23, 2019 at 1:53 PM, Sean Young <<EMAIL_ADDRESS>> wrote:

Would it be email if our username is just our prefix?  Thanks!
Sean Young
IT Manager @ Quizlet
On Thu, Aug 22, 2019 at 8:44 AM, Brian Monroe < notifications@ github. com
<EMAIL_ADDRESS>) > wrote:

I guess a large part of that would be that the logged in username would
need to match a user in snipe.
Since there's already an endpoint to thee patch request on snipe-it for assigned_to
https:/ / snipe-it. readme. io/ reference#hardware-partial-update (
https://snipe-it.readme.io/reference#hardware-partial-update )
I think you just need to add it to the API mapping section.
[api-mapping] name = general name _snipeit_mac_address_1 = general
mac_address assigned_to = location username
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (
https://github.com/ParadoxGuitarist/jamf2snipe/issues/12?email_source=notifications&email_token=AKMSMFXPCWGCSJBGIFZNNZ3QF2X4XA5CNFSM4IMBZ4I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD45QKYI#issuecomment-523961697
) , or mute the thread (
https://github.com/notifications/unsubscribe-auth/AKMSMFQVHJXSMAIGNAQYHV3QF2X4XANCNFSM4IMBZ4IQ
).

Looking at Snipe's code it looks like there is a separate API call for checking in / checking out devices.
Sean Young
IT Manager @ Quizlet
On Fri, Aug 23, 2019 at 2:10 PM, Sean Young <<EMAIL_ADDRESS>> wrote:

Ah I see that isn't pulled in your script (I believe).   I can try and add
it or figure it out if needed.
Sean Young
IT Manager @ Quizlet
On Fri, Aug 23, 2019 at 1:53 PM, Sean Young < sean. young@ quizlet. com (
<EMAIL_ADDRESS>) > wrote:

Would it be email if our username is just our prefix?  Thanks!
Sean Young
IT Manager @ Quizlet
On Thu, Aug 22, 2019 at 8:44 AM, Brian Monroe < notifications@ github. com
<EMAIL_ADDRESS>) > wrote:

I guess a large part of that would be that the logged in username would
need to match a user in snipe.
Since there's already an endpoint to thee patch request on snipe-it for assigned_to
https:/ / snipe-it. readme. io/ reference#hardware-partial-update (
https://snipe-it.readme.io/reference#hardware-partial-update )
I think you just need to add it to the API mapping section.
[api-mapping] name = general name _snipeit_mac_address_1 = general
mac_address assigned_to = location username
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (
https://github.com/ParadoxGuitarist/jamf2snipe/issues/12?email_source=notifications&email_token=AKMSMFXPCWGCSJBGIFZNNZ3QF2X4XA5CNFSM4IMBZ4I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD45QKYI#issuecomment-523961697
) , or mute the thread (
https://github.com/notifications/unsubscribe-auth/AKMSMFQVHJXSMAIGNAQYHV3QF2X4XANCNFSM4IMBZ4IQ
).

Thanks for that info. I’ll see what I can do.
Sean Young
IT Manager @ Quizlet
On Mon, Aug 26 2019 at 8:26 AM, <<EMAIL_ADDRESS>> wrote:

There is another endpoint for checkins. I did do a patch for assigned_to,
which succeeds, and returns the input that you send making it look like it
worked, but then immediately drops the string you send it. Later I found
out that when you assign it, it actually holds an array, which if you try
to send an array to assigned_to, you immediately get a 500 error.
That all being said, new functions will need to be written for checkout,
and we should probably have some sort of check to see if the default
status is a type that can check out assets. I know some users prefer to
check out to locations rather than specific users, so that might need to
be a factor as well.
All that being said, I'd love to have you work on this if you want. My
only requirement is that this action is triggered by the settings.conf
file or a runtime flag with the jamf2snipe working the same without any
config.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (
https://github.com/ParadoxGuitarist/jamf2snipe/issues/12?email_source=notifications&email_token=AKMSMFU3VIUM37RXCBB46QDQGPY2HA5CNFSM4IMBZ4I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5EW3DQ#issuecomment-524905870
) , or mute the thread (
https://github.com/notifications/unsubscribe-auth/AKMSMFTOLRFSRTKOELMQTIDQGPY2HANCNFSM4IMBZ4IQ
).

That sounds great.  Thanks for the addition.
Sean Young
IT Manager @ Quizlet
On Thu, Jan 30, 2020 at 9:52 AM, Dan Christovic <<EMAIL_ADDRESS>> wrote:

Great, that'll give me some time to make sure it's all tidy. Have a great
vacation!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (
https://github.com/ParadoxGuitarist/jamf2snipe/issues/12?email_source=notifications&email_token=AKMSMFXNS2VDSU3EV2TAOZ3RAMHWFA5CNFSM4IMBZ4I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKL5FFY#issuecomment-580375191
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AKMSMFXYBQS2UAB7TAVOHDDRAMHWFANCNFSM4IMBZ4IQ
).

Created a pull request that would close this issue but not sure how to link them! Maybe I had to do that at the time of creating the request...

Is this in master now or should I check out a different branch to test?

Hey Sean, sorry for the late reply, still getting used to how GitHub notifies you - turns out everything was going to my 'Forums' section in Gmail... Ugh!
Anyway, my branch should be up to date with this one with the additions.
Let me know if you do try it out.

This was added by PR #20