[General Issue]: "Handshake did not complete..."

In raising this issue I confirm that

[X] I have read the documentation
[X] I have read and understood the PiVPN General Guidelines
[X] I have read and understood the PiVPN Troubleshooting Guidelines
[X] The issue I am reporting isn't a duplicate, see closed issues and open issues.
[X] I have searched for similar issues and solutions
[X] I can replicate the issue even after a clean OS installation

Describe the issue
I configured everything to make a VPN on my Raspberry Pi, and it was perfect. I created a few more clients and after a few days it stopped working. I haven't done anything.
But when I try to connect with my IOS mobile and look at the bugs I get "Handshake did not complete...".
I've checked everything the documentation says, but I can't find the bug.
I have seen people with the same error but not the solution.
Thanks in advance
Expected behavior
Successful connection for my clients
Please describe the steps to replicate the issue

Configuration with WireGuard
Use default port to forwarding: 51820
Use duckdns

Have you taken any steps towards solving your issue?
Reinstall
Screenshots
No response
Where did you run pivpn?
Raspberry Pi
Please provide your output from uname -a
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux
Details about Operative System
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Installation
curl -L https://install.pivpn.io | bash
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100  111k  100  111k    0     0   380k      0 --:--:-- --:--:-- --:--:--  380k
:::
::: sudo will be used for the install.
::: Repair option selected.
::: Hostname length OK
::: Verifying free disk space...
:::
::: Package Cache update is needed, running apt-get update -y ...
done!
:::
::: Checking apt-get for upgraded packages.... done!
:::
::: Your system is up to date! Continuing with PiVPN installation...
:::    Checking for git... already installed!
:::    Checking for tar... already installed!
:::    Checking for curl... already installed!
:::    Checking for grep... already installed!
:::    Checking for dnsutils... already installed!
:::    Checking for grepcidr... already installed!
:::    Checking for whiptail... already installed!
:::    Checking for net-tools... already installed!
:::    Checking for bsdmainutils... already installed!
:::    Checking for bash-completion... already installed!
:::    Checking for dhcpcd5... already installed!
:::    Checking for iptables-persistent... already installed!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
::: PiVPN Automated Installer
::: This installer will transform your Raspbian host into an OpenVPN or WireGuard server!
::: Initiating network interface
::: Enable forced IPv6 route with no IPv6 uplink on server.
::: Using interface: eth0 for IPv4
::: Your static IPv4 address:    <IP_ADDRESS>/24
::: Your static IPv4 gateway:    <IP_ADDRESS>
::: Using DHCPCD
::: Static IP already configured.
::: raspi will hold your VPN client configuration files.
:::
::: Checking for existing base files...
:::    Checking /usr/local/src/pivpn is a repo... OK!
::: Repairing an existing installation, not downloading/updating local repos
::: WireGuard will be installed
::: Installing WireGuard from Raspbian package...
:::    Checking for wireguard-tools... already installed!
:::    Checking for qrencode... already installed!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
::: Using port 51820
::: Using DNS <IP_ADDRESS> <IP_ADDRESS>
[2024-03-24T12:56:08+0100]: dig failed, now trying to curl checkip.amazonaws.com
::: Using domain name PRIVATENAME.duckdns.org
::: Backing up the wireguard folder to /etc/wireguard_2024-03-24-125609.tar.gz
::: The Server Keys will now be generated.
::: Server Keys have been generated.
::: Server config generated.
::: Install Complete...
::: Restarting services...
::: Enabling unattended upgrades
:::    Checking for unattended-upgrades... already installed!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
::: Setupfiles copied to /etc/pivpn/wireguard/setupVars.conf
::: Installing scripts to /opt/pivpn...
done.
::: Flushing writes to disk...
::: done.
::: Installation Complete!
::: Now run 'pivpn add' to create the client profiles.
::: Run 'pivpn help' to see what else you can do!
::: If you run into any issue, please read all our documentation carefully.
::: All incomplete posts or bug reports will be ignored or deleted.
::: Thank you for using PiVPN.
::: It is strongly recommended you reboot after installation.
:::
Profile / Client creation
pivpn add -n platano
::: Client Keys generated
::: Client config generated
::: Updated server config
::: WireGuard reloaded
Debug output
pivpn -d
::: Generating Debug Output
::::            PiVPN debug              ::::
::::            Latest commit            ::::
Branch: master
Commit: 20d3a4ccd4f2d080d6f9a13a74e6369aa9d54476
Author: Orazio
Date: Mon Jan 29 08:53:41 2024 +0100
Summary: fix(install): don't treat http errors as unavailable ipv6
::::        Installation settings        ::::
PLAT=Raspbian
OSCN=bullseye
USING_UFW=0
pivpnforceipv6route=1
IPv4dev=eth0
dhcpReserv=
IPv4addr=<IP_ADDRESS>/24
IPv4gw=<IP_ADDRESS>
install_user=raspi
install_home=/home/raspi
VPN=wireguard
pivpnPORT=51820
pivpnDNS1=<IP_ADDRESS>
pivpnDNS2=<IP_ADDRESS>
pivpnHOST=REDACTED
INPUT_CHAIN_EDITED=1
FORWARD_CHAIN_EDITED=1
INPUT_CHAIN_EDITEDv6=
FORWARD_CHAIN_EDITEDv6=
pivpnPROTO=udp
pivpnMTU=1420
pivpnDEV=wg0
pivpnNET=<IP_ADDRESS>
subnetClass=24
pivpnenableipv6=0
ALLOWED_IPS="<IP_ADDRESS>/0, ::0/0"
UNATTUPG=1
INSTALLED_PACKAGES=(wireguard-tools)
::::  Server configuration shown below   ::::
[Interface]
PrivateKey = server_priv
Address = <IP_ADDRESS>/24
MTU = 1420
ListenPort = 51820
begin platano
[Peer]
PublicKey = platano_pub
PresharedKey = platano_psk
AllowedIPs = <IP_ADDRESS>/32
end platano
=============================================
::::  Client configuration shown below   ::::
[Interface]
PrivateKey = platano_priv
Address = <IP_ADDRESS>/24
DNS = <IP_ADDRESS>, <IP_ADDRESS>
[Peer]
PublicKey = server_pub
PresharedKey = platano_psk
Endpoint = REDACTED:51820
AllowedIPs = <IP_ADDRESS>/0, ::0/0
::::    Recursive list of files in       ::::
::::    /etc/wireguard shown below       ::::
/etc/wireguard:
configs
keys
wg0.conf
/etc/wireguard/configs:
clients.txt
platano.conf
/etc/wireguard/keys:
platano_priv
platano_psk
platano_pub
server_priv
server_pub
::::            Self check               ::::
:: [OK] IP forwarding is enabled
:: [OK] Iptables MASQUERADE rule set
:: [OK] Iptables INPUT rule set
:: [OK] Iptables FORWARD rule set
:: [OK] WireGuard is running
:: [OK] WireGuard is enabled
(it will automatically start on reboot)
:: [OK] WireGuard is listening on port 51820/udp
:::: Having trouble connecting? Take a look at the FAQ:
:::: https://docs.pivpn.io/faq
:::: WARNING: This script should have automatically masked sensitive       ::::
:::: information, however, still make sure that PrivateKey, PublicKey      ::::
:::: and PresharedKey are masked before reporting an issue. An example key ::::
:::: that you should NOT see in this log looks like this:                  ::::
:::: YIAoJVsdIeyvXfGGDDadHh6AxsMRymZTnnzZoAb9cxRe                          ::::
::::            Debug complete           ::::
:::
::: Debug output completed above.
::: Copy saved to /tmp/debug.log
:::

Pre-archive closing, more information here


New header layout

This pull request makes the "tick" in a "tick-tock" to rename the headers in this package to have the .hpp rather than the .h extension. The main goal of this is to minimize the delta between this and the ROS 2 branch, but it also just makes more sense and helps a lot of code editors and style checkers infer the right language.
The headers are renamed (8985e48), the code is updated (97176b3), and then the original header files are restored with forwarding includes and deprecation warnings (dc97479). In the case of the class_loader_imp.h header, I just put a #error message because no one should be including that directly anyways.
In a future release (n-turtle) we can remove the legacy headers completely.

It would be possible to create the new header file names in older releases, forwarding the include to the current header name and without any warning (to allow downstream packages to update to the new include name across ROS distros).

If this is taken, then my pr removing boost (https://github.com/ros/pluginlib/pull/67) could be updated to optionally keep the boost function signature when using the old header include, but when including by the new header name. I also plan to update it to use a new function name, deprecating the current function that returns a boost::shared_ptr, but I'll add more details about that there.

btw, #warning was the best way to deprecate a file that I could find, if anyone has a better way to do it, let me know.

btw, #warning was the best way to deprecate a file that I could find, if anyone has a better way to do it, let me know.

This seem to be a common practice that I find better than the pretty popular alternative using a #pragma message :+1: so I'm totally fine with it except if someone suggests a "better" way of doing it

Sounds good, thanks for iterating, would you mind squashing the follow up commits so that we can merge this PR as 3 commits? (renaming, updating, adding backward compatible headers)

Done.

:boom: WHY :boom:
This breaks so much code for no real benefit....
It's to late for complains now, anyway... :unamused:

@v4hn It's never too late :)
The main intent is to allow us to keep the ROS 1 and ROS 2 branches as close as possible, compliant with the ROS 2 style, and to allow to eventually provide a C interface to pluginlib.
As we didn't have time to do all the refactor we wanted to do in pluginlib on time for melodic, I agree with you this doesn't have much benefit currently except making our life easier on the ROS2 side.
I tried to provide an easy migration path by releasing migration scripts as well as opening PRs so that people don't have to migrate themselves.
While this doesn't "break" any code for the time being, I understand that the newly introduced warnings are inconvenient. I am considering removing the deprecation warnings in melodic and adding them back in a future ROS version when the refactor of pluginlib is more advanced and that the API changes will justify this small extension change.
Either ways I will keep providing both versions as well as scripts to perform the migration so that people that want to change can easily do it.
But we would like to get rid of them when we reach the point that this diff is the only code diff between the ROS 1 and ROS 2 version of this package.
I'm happy to consider additional feedback, so please feel free to keep commenting here.

The main problem I see is that you assume all software is well-maintained.
Sadly that's not true in our line of work.
So with each API change you introduce, you make life harder for researchers
to try out software of previous generations...
After all one good thing about the core ros libraries is that their APIs are rather stable, but still supported.
+1 to removing the warning until it is crucial for ROS1-2 support.

Never changing isn’t an option either though. So I’m in favor of avoiding a required change for this case, but thinking nothing will ever change in any future ros distrubtions is unreasonable in my opinion. Also this change doesn’t break anything, at worst it will cause a warning. In the next ros release it would break but there are other more substantive changes that may occur in the future.


Create a version

Could you create a released version of your workflow? It makes version tracking easier.

Hey Erin, just created a Beta version (pre-release) for our codebase

Perfect! This helps when pulling github repos.


Bug: Marey doesn't work after 24:00

Actually, they Marey works fine, it's the map that does not work. This is because there is a step in between the callback that updates the map in which I convert the time to HH:MM:SS format which breaks it


Is MonadBase IO better than MonadIO?

To me, MonadBase IO doesn't seem to add anything that MonadIO doesn't already do. However, the use of MonadBase IO means that my library now incurs a dependency on transformers-base, and potential my downstream users too. I may have misunderstood something, but if possible I think
onExit :: (region ~ RegionT s parent, MonadIO parent) => Finalizer -> region (FinalizerHandle region)

is preferable. If that doesn't work due to the type signature, then I'd just go with
onExit :: MonadIO parent => Finalizer -> RegionT s parent (FinalizerHandle (RegionT s parent))

(as it was before).

Did anything end up happening about this?

I've fixed this in the RegionIOControl branch.


Doesn't want to co-exist with Toga

Hi. Repl mod does not want to co-exist with toga, the TouchOSC grid emulator thing which monkey-patches the grid interface on norns.
It's a bit funny because some scripts work, other don't get any traffic between norns and TouchOSC, and some crash norns. Disabling repl makes toga work. I think it has to do with repl intercepting OSC messages, and maybe not passing on the ones it isn't concerned with.
Please let me know if I can help triage and debug somehow e.g. by running a development branch etc. or placing print statements in the code or something.
Cheers :)

the commit i just did might be a fix.

Sorry I didn't come back to this. I am using toga occasionally nowadays, and I'll try to see if it's ok now. Super mod!

Yes I think that does it. At least now n.Kria, MLRE, Buoys, Awake-Passersby and Dreamsequence seem to run fine while REPL mod is enabled.
I still see
togagrid connect!
togagrid: add new toga client   <IP_ADDRESS>:8002
/home/we/dust/code/toga/lib/togagrid.lua:108: attempt to call a nil value (\
field 'old_osc_in')
stack traceback:
        /home/we/dust/code/toga/lib/togagrid.lua:108: in upvalue 'script_os\
c_in'
        /home/we/dust/code/repl/lib/repl_osc_gw.lua:77: in function 'core/o\
sc.event'
        /home/we/norns/lua/core/osc.lua:109: in function </home/we/norns/lu\
a/core/osc.lua:107>

when togagrid and repl are both enabled and I start connect togagrid, but seems to work ok. And: I can see there error in the REPL mod so that's cool.


feat(custom-object-importer): integrate importer to cli

Summary

Integrates the custom object import module
Description

This PR adds the custom object importer to the import CLI

resolves #80

Good find, thanks @junajan. Removed here https://github.com/sphereio/sphere-node-cli/pull/81/commits/bfcb78e0edf603af8910cc9ddbb0aa9ae59e06b1


Solr Net Cloud Unity exception

Hi I am using Solr.Net.Cloud.Unity ver. 1.0.3, Solr.Net.Cloud.Core ver. 1.0.3, Unity ver. 5.0.0  in .NET Standard 2.0 Console Application.
Here is code:
using (var container = new UnityContainer())
                {
                    var cont = new Unity.SolrNetCloudIntegration.SolrNetContainerConfiguration().ConfigureContainer("desktop-lmqi80k:9984", container);
                    var obj = cont.Resolve<ISolrOperations<Camera>>();
                    SolrQueryResults<Camera> cameras = obj.Query(new SolrQueryByField("Name", "Canon"));
                    Console.WriteLine("Product: " + cameras.FirstOrDefault().Name);

                    Console.WriteLine("Test");

                    Console.ReadKey();
                }

And I receive this error:
Exception occurred
Unity.Exceptions.ResolutionFailedException: Resolution of the dependency failed, type = 'SolrNet.ISolrOperations`1[GSec.Service.Solr.Camera]', name = '(none)'.
Exception occurred while: while resolving.
Exception is: InvalidOperationException - The current type, SolrNet.ISolrOperations`1[GSec.Service.Solr.Camera], is an interface and cannot be constructed. Are you missing a type mapping?
-----------------------------------------------
At the time of the exception, the container was:
  Resolving SolrNet.ISolrOperations`1[GSec.Service.Solr.Camera],(none)
 ---> System.InvalidOperationException: The current type, SolrNet.ISolrOperations`1[GSec.Service.Solr.Camera], is an interface and cannot be constructed. Are you missing a type mapping?
   at Unity.ObjectBuilder.BuildPlan.DynamicMethod.Creation.DynamicMethodConstructorStrategy.ThrowForAttemptingToConstructInterface(IBuilderContext context) in C:\projects\unity\Container\src\ObjectBuilder\BuildPlan\DynamicMethod\Creation\DynamicMethodConstructorStrategy.cs:line 280
   at lambda_method(Closure , IBuilderContext )
   at Unity.ObjectBuilder.BuildPlan.DynamicMethod.DynamicBuildPlanGenerationContext.<>c__DisplayClass16_0.<GetBuildMethod>b__0(IBuilderContext context) in C:\projects\unity\Container\src\ObjectBuilder\BuildPlan\DynamicMethod\DynamicBuildPlanGenerationContext.cs:line 134
   at Unity.ObjectBuilder.BuildPlan.DynamicMethod.DynamicMethodBuildPlan.BuildUp(IBuilderContext context) in C:\projects\unity\Container\src\ObjectBuilder\BuildPlan\DynamicMethod\DynamicMethodBuildPlan.cs:line 36
   at Unity.ObjectBuilder.Strategies.BuildPlanStrategy.PreBuildUp(IBuilderContext context) in C:\projects\unity\Container\src\ObjectBuilder\Strategies\BuildPlanStrategy.cs:line 35
   at Unity.Container.StrategyChain.ExecuteBuildUp(IBuilderContext builderContext) in C:\projects\unity\Container\src\Container\StrategyChain.cs:line 56
   at Unity.UnityContainer.BuildUp(Type typeToBuild, Object existing, String name, ResolverOverride[] resolverOverrides) in C:\projects\unity\Container\src\UnityContainer.cs:line 211
   --- End of inner exception stack trace ---
   at Unity.UnityContainer.BuildUp(Type typeToBuild, Object existing, String name, ResolverOverride[] resolverOverrides) in C:\projects\unity\Container\src\UnityContainer.cs:line 215
   at Unity.UnityContainer.Resolve(Type type, String name, ResolverOverride[] resolverOverrides) in C:\projects\unity\Container\src\UnityContainer.cs:line 163
   at Unity.UnityContainerExtensions.Resolve[T](IUnityContainer container, ResolverOverride[] overrides) in C:\projects\unity\Abstractions\src\Utility\UnityContainerExtensions.cs:line 469
   at GSec.Service.Solr.MicroserviceRunner.<RunExtraAsync>d__8.MoveNext() in C:\Repos\GSECPOCS\POC\SolrExample\GSec.Service.Culture\GSec.Service.Culture\MicroserviceRunner.cs:line 71

Exception is thrown on this line:
var obj = cont.Resolve<ISolrOperations<Camera>>();
Where Camera is:
    public class Camera
    {
        [SolrField("Name")]
        public string Name { get; set; }

        [SolrField("UID")]
        public int UID { get; set; }

        [SolrField("id")]
        public string Id { get; set; }
    }

Can you tell me what is wrong?
I can provide additional info if you need some. Thanks!

Anyway, maybe someone can post me example of working code that are uses Solr Net Cloud Unity component ? )

@gjunge  Thanks a lot!  I have successfully used Common Service Locator for Solr Net Cloud  but I don't think that it will be acceptable for us because of it limitations.

That is good to know, meaning SolrNet.Cloud itself works good, except for the Unity integration.

@gjunge  That is good to know, meaning SolrNet.Cloud itself works good, except for the Unity integration. - Yes. ) At least I can run simple query. )

I can't seem to recreate it:
Here are tests dealing with SolrCloud with Unity: https://github.com/SolrNet/SolrNet/blob/issues/385/SolrNet.Cloud.Tests/UnityTests.cs
I added your sample , but it works fine.
What might happen though is that some async error occurs in the SolrCloudProvider, could you try
var provider = new SolrCloudStateProvider("desktop-lmqi80k:9984");
await provider.InitAsync();
var state = provider.GetCloudState();
var colcount  = state.Collections.Count;

using (var container = new UnityContainer())
                {
                    var cont = new Unity.SolrNetCloudIntegration.SolrNetContainerConfiguration().ConfigureContainer(provider, container);
                    var obj = cont.Resolve<ISolrOperations<Camera>>();
                    SolrQueryResults<Camera> cameras = obj.Query(new SolrQueryByField("Name", "Canon"));
                    Console.WriteLine("Product: " + cameras.FirstOrDefault().Name);

                    Console.WriteLine("Test");

                    Console.ReadKey();
                }

And see if is all good.

Hi, thanks for help, but error is stay the same. I have created simple project with this chunk of code.
Can you look at it?
https://www.dropbox.com/s/bxfy1i7hyaifwgo/SolrPOC.zip?dl=0

Great, I was able to reproduce the issue, I will now check what the problem is.

I think actually you are not connected to the zookeeper. What value does the colcount variable have in the code snippet above, and what does the state variable show?
I added to version 1.0.5 of SolrNet , a check to see if we are connected to the zookeeper instance.

Hi, thanks. It is working. For now exception is changed:
System.AggregateException
  HResult=0x80131500
  Message=One or more errors occurred. (Cannot connect to the Zookeeper instance desktop-lmqi80k:9984. Current state: CONNECTING )
  Source=System.Private.CoreLib
  StackTrace:
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait()
   at SolrPOC.Program.Main(String[] args) in D:\POC\SolrPOC\SolrPOC\Program.cs:line 27

Inner Exception 1:
SolrNetCloudConnectionException: Cannot connect to the Zookeeper instance desktop-lmqi80k:9984. Current state: CONNECTING

Yes we will update the nuget packages.
@xavier-morera 1.0.5 currently contains a small change and could be published.

Thanks @Fatalityap and @gjunge for fixing this issue. I have updated NuGet to 1.0.5

Thanks for help! )


Update UI for good width and height

@AlexFlorides ,
issue #11 Complited

The UI changes look good, but it's not optimized for smaller screen dimensions like mobile, tablet etc...

The UI changes look good, but it's not optimized for smaller screen dimensions like mobile, tablet etc...

Okay, I will update and create a fully responsive design for cross-platform compatibility.

@AlexFlorides, I'm currently very busy with my project https://github.com/CodeHarborHub/codeharborhub.github.io.
So, in your projects my PRs code is all set, but it needs media queries implemented for different devices.
Due to my responsibilities in managing a large number of contributors on my project, I am unable to complete your repo PRs immediately. If you prefer, I can handle it, but I will need some additional time. I apologize for any inconvenience this delay may cause.
Thank you for your understanding.

Take your time, you can finish it whenever you can


[ISSUE# 2330] Store the properties of MessageBatch

What is the purpose of the change
store the properties of MessageBatch

Coverage increased (+0.03%) to 51.464% when pulling 18e2acc4fda9bfdfc73794cb0518653ff407cc05 on AVP42:batch_properties into 77d24def3a5aafd0d10afd525734bba398cf48b2 on apache:develop.

Codecov Report

Merging #2343 into develop will decrease coverage by 0.09%.
The diff coverage is 61.53%.

@@              Coverage Diff              @@
##             develop    #2343      +/-   ##
=============================================
- Coverage      45.69%   45.59%   -0.10%
+ Complexity      4289     4279      -10
=============================================
  Files            547      547
  Lines          35971    35981      +10
  Branches        4770     4773       +3
=============================================
- Hits           16437    16407      -30
- Misses         17477    17522      +45
+ Partials        2057     2052       -5

Impacted Files
Coverage Δ
Complexity Δ

...ocketmq/broker/processor/SendMessageProcessor.java
40.90% <0.00%> (-0.11%)
26.00 <0.00> (ø)

...pache/rocketmq/common/message/MessageExtBatch.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...main/java/org/apache/rocketmq/store/CommitLog.java
67.52% <88.88%> (+0.20%)
80.00 <0.00> (ø)

...rocketmq/broker/filtersrv/FilterServerManager.java
20.00% <0.00%> (-14.29%)
5.00% <0.00%> (-2.00%)

...tmq/logappender/log4j2/RocketmqLog4j2Appender.java
35.00% <0.00%> (-10.00%)
3.00% <0.00%> (-1.00%)

...org/apache/rocketmq/common/stats/StatsItemSet.java
43.28% <0.00%> (-7.47%)
17.00% <0.00%> (-2.00%)

...ketmq/common/protocol/body/ConsumerConnection.java
95.83% <0.00%> (-4.17%)
13.00% <0.00%> (-1.00%)

...nt/impl/consumer/ConsumeMessageOrderlyService.java
38.98% <0.00%> (-2.53%)
16.00% <0.00%> (-3.00%)

...rocketmq/client/impl/factory/MQClientInstance.java
46.97% <0.00%> (-0.74%)
82.00% <0.00%> (-1.00%)

...etmq/client/latency/LatencyFaultToleranceImpl.java
50.00% <0.00%> (ø)
8.00% <0.00%> (ø%)

... and 2 more

Continue to review full report at Codecov.

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

I don't think the travis error is caused by these commits. Perhaps need to rebuild?

I don't think the travis error is caused by these commits. Perhaps need to rebuild?

The code is OK, I rebuild the CI.


[Tx-Builder] Fix negative input number

Fixes #139 parsing correctly negative number on inputs
From web3 > 1.2.5 there is a bug that parse negative numbers incorrectly adding leading 0's before the minus sign when the value is passed as a string.
The encodeFunctionCall expects that the input values are still passed as string, so to avoid this bug without rolling back to a really old version of web3 we can add the leading 0's for numeric values and that way still send the value as a string

I added the Tx-builder given in this ticket to prod mainnet so I could try the same scenario using the contract and method described in the issue
Contract: 0x034a6626eec82e14ac5b0130f04f85a2ea158f9c
Test Values:
CreatePool (method)
Address1: 0x6B175474E89094C44Da98b954EedeAC495271d0F
Address2: 0x6B175474E89094C44Da98b954EedeAC495271d0F
NumValue1: 100
NumValue2: 100
NumValue3: -10000
NumValue4: -1000
String: "1"
In the new tx builder the negative values are not treated as invalid values
Gif:
I show first the error, with the txbuilder that is in prod by default. The other tab shows the tx already created and ready to be siged, using the tx-builder app provided in this ticket, also in mainnet eth prod.

Looks good to me


No such file or directory: './options.json'

Hi,
Thank you for this interesting research, I want to reproduce the results by running the shell script you provided, I see the following issue though, how can I resolve that? I am using a recent version of TensorFlow on Ubuntu on WSL on Windows 11 and I am NOT using CUDA for testing.

Traceback (most recent call last):
File "Single-Image-SVBRDF-Capture-rendering-loss/material_net.py", line 1162, in
main()
File "Single-Image-SVBRDF-Capture-rendering-loss/material_net.py", line 861, in main
with open(os.path.join(a.checkpoint, "options.json")) as f:
FileNotFoundError: [Errno 2] No such file or directory: './options.json'

Thanks in advance,
Nima

Hi,
I believe this file should be part of the network weights for which you can find a link in the repo readme. Let me know if that doesn't solve your issue.
Valentin


[IOTDB-753] Add a judgement before removing entry from tag inverted index

Hi, should this PR be merged into rel/0.10 ?

Hi, should this PR be merged into rel/0.10 ?

Ok.
By the way, pay attention to the code smell (use log.isWarnEnable() before calling log.warn() because there are too many string concat.)


Add conda forge minimal test

As per discussion in #194 , I am moving a conda forge distribution test to tests/conda.
To not interfere with the rest of the testing setup, I am introducing pytest.ini, registering conda marker and setting the default pytest run to exclude conda marked tests and files.
Note: setting up setup.cfg might reduce number of config files. Shall an issue/PR be opened, which would introduce it? I can imagine it covering settings for pytest, flake8 and coveragerc as for now.
Please, let me know if any changes a needed.
The transition from the current setup (test placed in flaml-feedstock) should happen in following steps in my opinion.

Make appropriate changes to this PR
Merge this PR
Create new FLAML release
Update the conda recipe in flaml-feedstock
Create new distribution for the same FLAML release (bump the build number)

As per discussion in #194 , I am moving a conda forge distribution test to tests/conda.
To not interfere with the rest of the testing setup, I am introducing pytest.ini, registering conda marker and setting the default pytest run to exclude conda marked tests and files.
Note: setting up setup.cfg might reduce number of config files. Shall an issue/PR be opened, which would introduce it? I can imagine it covering settings for pytest, flake8 and coveragerc as for now.

Yes, sounds a good idea.

Please, let me know if any changes a needed.
The transition from the current setup (test placed in flaml-feedstock) should happen in following steps in my opinion.

Make appropriate changes to this PR
Merge this PR
Create new FLAML release
Update the conda recipe in flaml-feedstock
Create new distribution for the same FLAML release (bump the build number)

I can create a new release after this PR is merged. Could you please work on 4 and 5 then?

@sonichi Yes, sure. I will take 4 and 5 and draft the setup.cfg in new PR.


nixos/lib/make-disk-image: performance regression since 16.03

24f8cf08 changes nixos/lib/make-disk-image to use nixos-install, but that doesn't copy the closure correctly so it takes way longer to build.
To reproduce run:
         nix-build \
             '<nixpkgs/nixos>' \
             -A config.system.build.amazonImage \
             --arg configuration "{ imports = [ <nixpkgs/nixos/maintainers/scripts/ec2/amazon-image.nix> ]; ec2.hvm = true; }"

And to make things worse, nixos-install uses -j 1 by default. This is considered a regression, ami image takes now ~35min to build.
cc @obadz

What do you mean by 'downloads files from the internet' ? Shouldn't that be impossible from a chrooted build?
Should -j 1 matter given that everything should be in the cache provided from inside the qemu VM so nothing should be built?
I just ran the exact command you provided and it took 3m22s (I'm on c859ea0).

You don't get nixos-install fetching lots of files like:
*** Copying ‘/nix/store/n2mzj8h0rjp39di41jf762nzjhq6r4w2-libunwind-1.1’ from ‘/tmp/root/nix/store/n2mzj8h0rjp39d
i41jf762nzjhq6r4w2-libunwind-1.1’

fetching path ‘/nix/store/kkqf5mx287fxlsvxm2g8ys0wkfrbwgs1-libxcb-1.12’...

I'm on master branch.

I do, but that's just the nix-env inside the chroot inside nixos-install that's copying derivations from the nix store of the qemu VM onto the new filesystem that's being created.
Fetching here probably mean some substituter is involved, not the network?

Ah I see now! Didn't even realise it's not coming from http.

There is however an inefficiency with:
fixing missing hash on ‘/nix/store/8jwqlpyxp5c2rl5g7yspdfbh58dsciwx-xz-5.2.2’
updating size field on ‘/nix/store/8jwqlpyxp5c2rl5g7yspdfbh58dsciwx-xz-5.2.2’ to 328320

Essentially we don't yet have the ability to create a valid nix store inside a qemu VM that contains the transitive closure of some derivation on the mother system. The thing will boot and be normally usable, but nix operations will not recognize these packages without this step:
https://github.com/NixOS/nixpkgs/blob/master/nixos/lib/make-disk-image.nix#L74-L76
And that step takes time…
Still doesn't explain how you get to 35 minutes. How long does it take you to build it the second time around after a trivial config change?

@obadz this is on EC2. I'll test with 16.09 and 16.03 and compare timings.
I agree that it would be good to get size information etc into exported graph so we don't have to do so much IO. Does nix-store --load-db support such format in the first place?

@obadz opened https://github.com/NixOS/nix/issues/1134

The performance regression is real. This is on EC2:
16.03:
1.33user 0.75system 8:14.34elapsed 0%CPU (0avgtext+0avgdata 252760maxresident)k
0inputs+0outputs (0major+67380minor)pagefaults 0swaps

16.09:
/nix/store/sjlfm79f466ywia405615c2pmafraimp-nixos-disk-image
1.69user 1.11system 31:05.59elapsed 0%CPU (0avgtext+0avgdata 291044maxresident)k
0inputs+0outputs (0major+77253minor)pagefaults 0swaps

Sadly we don't have any jobs on hydra to track build times of image builds

cc @edolstra @rbvermaa

@obadz maybe we could still cp the closure and then use nixos-install?

@domenkozar could it be that this is now doing a lot more in qemu on EC2? Keep in mind that EC2 doesn't support nested virtualization, so everything that happens inside the VM is fully emulated and obscenely slow. That's why I keep pushing for ways to build images that don't involve any VM, because everything I do is in EC2 😄

That would explain the massive perf differential between local and EC2. I vote for trying to fix https://github.com/NixOS/nix/issues/1134 before considering other avenues.

Well, I still think we should stop using VMs to build images, as much as possible, because it's still far slower than it needs to be. But yes, that's also a problem.

We'd need an unprivileged mechanism to write an ext2 filesystem (and a few more things). Can we get fuse-ext2 to work inside the nix sandbox? Without it I think it will be hard.

There's already code that does that with debugfs in nixpkgs today. Not sure how fast it is. There's also https://github.com/rumpkernel/fs-utils and a similar project for Linux that I can't remember right now. I don't think fuse will really work for us.

It might also be btw that the hashing required to validate the nix-store (which we ought to be able to get rid off) is much much slower than the IO required to do the copying, in which case qemu will become much less of a burden once we fix NixOS/nix#1134

https://github.com/rumpkernel/wiki/wiki/Repo:-fs-utils does looks useful here.

@obadz out of 60min in total, 13min is spend rewriting hashes while 40min is spent in nixos-install.

@domenkozar https://github.com/lkl/linux looks like it's planning to be something similar to the rump project for linux, so it might be possible to get something like fs-utils against all the filesystem modules we normally use and love 😄

Hmmm I fail to understand why nixos-install takes any more time than https://github.com/NixOS/nixpkgs/commit/24f8cf08cc897f0b3c2ff4118fe30c38eed85aa6#diff-7fce4d49800213db1196b42209660eb4L94 (line 94-95) as that's essentially what nixos-install runs…
Are you sure the performance is restored when you revert that commit?

Nevermind, I take that back. Seems like the old way copied the store path directly inside the target rather than first installing it inside the qemu VM and then using substituters.

@copumpkin I looked into fs-utils and we won't be able to run nixos-install with it since there's no way to chroot. Did I miss something?

It might be worth trying out methods in https://wiki.debian.org/ManipulatingISOs#Loopmount_an_ISO_Without_Administrative_Privileges

at a glance, i think those are just a group of setuid root tools that do things for you and enforce some security rules

@domenkozar fundamentally, it doesn't seem like nixos-install should need chroot, right?

Trying to build a NixOS image inside EC2 and it's miserable. We need to do something about this. Going to start poking around at minimizing (probably not to 0) the amount of VM time we need for it...

@cleverca22 @domenkozar @obadz see #21943 for current WIP

Since https://github.com/NixOS/nix/issues/1134 has been closed, is there now a way to avoid doing nix-store --verify --check-contents ? I can't seem to find how to use the json exported data from exportReferencesGraph anywhere.

That feature will land in Nix 1.12 so until it's released we can't use it :)

Ok, thx :)

exportReferencesGraph and pathsFromGraph could be replaced with something like:
      # use instead of "perl ${pkgs.pathsFromGraph} /tmp/xchg/closure", no difference
      storePaths = toplevel:
        hostpkgs.runCommand "storepaths" { preferLocalBuild = true; } ''
          ${hostpkgs.nix}/bin/nix-store -qR ${toplevel} > $out
        '';

      # use instead of "printRegistration=1 perl ${pkgs.pathsFromGraph} /tmp/xchg/closure", it has valid sizes and hashes
      dumpDb = toplevel:
        hostpkgs.runCommand "dumpdb" {
          preferLocalBuild = true;
          perlcode = hostpkgs.writeScript "xxx.pl" ''
            my %storePaths={};
            open SP, "<${storePaths toplevel}";
            while (<SP>) {
              $storePaths{$_} = 1;
            }
            close SP;

            open DB, '-|', '${hostpkgs.nix}/bin/nix-store --dump-db' or die $!;
            while (<DB>) {
              my $path  = $_;   print $path  if $storePaths{$path};
              my $hash  = <DB>; print $hash  if $storePaths{$path};
              my $size  = <DB>; print $size  if $storePaths{$path};
                          <DB>; print "\n"   if $storePaths{$path};
              my $count = <DB>; print $count if $storePaths{$path};
              chomp $count;
              for (my $i = 0; $i < $count; ++$i) {
                my $dep = <DB>; print $dep   if $storePaths{$path};
              }
            }
            close DB;
          '';
        } ''
          ${hostpkgs.perl}/bin/perl $perlcode > $out
        '';

@volth your version only works if sandboxing is turned off :/
On Sun, Apr 16, 2017 at 01:14 volth<EMAIL_ADDRESS>wrote:

exportReferencesGraph and pathsFromGraph could be replaced with something
like:
  # use instead of "perl ${pkgs.pathsFromGraph} /tmp/xchg/closure", no difference
  storePaths = toplevel:
    hostpkgs.runCommand "storepaths" { preferLocalBuild = true; } ''
      ${hostpkgs.nix}/bin/nix-store -qR ${toplevel} > $out
    '';

  # use instead of "printRegistration=1 perl ${pkgs.pathsFromGraph} /tmp/xchg/closure", it has valid sizes and hashes
  dumpDb = toplevel:
    hostpkgs.runCommand "dumpdb" {
      preferLocalBuild = true;
      perlcode = hostpkgs.writeScript "xxx.pl" ''
        my %storePaths={};
        open SP, "<${storePaths toplevel}";
        while (<SP>) {
          $storePaths{$_} = 1;
        }
        close SP;

        open DB, '-|', '${hostpkgs.nix}/bin/nix-store --dump-db' or die $!;
        while (<DB>) {
          my $path  = $_;   print $path  if $storePaths{$path};
          my $hash  = <DB>; print $hash  if $storePaths{$path};
          my $size  = <DB>; print $size  if $storePaths{$path};
                      <DB>; print "\n"   if $storePaths{$path};
          my $count = <DB>; print $count if $storePaths{$path};
          chomp $count;
          for (my $i = 0; $i < $count; ++$i) {
            my $dep = <DB>; print $dep   if $storePaths{$path};
          }
        }
        close DB;
      '';
    } ''
      ${hostpkgs.perl}/bin/perl $perlcode > $out
    '';

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/20471#issuecomment-294334169,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAKP4qrd0QdGkwCOwIzVuflUMMi8TaDks5rwaOygaJpZM4K0Bzn
.

@copumpkin that's bad. But NixOS/nix#1134 fix is not in 17.03 yet (even as nixUnstable) and recalculating the hashes from the content (besides being slow) could legalize nixstore corruption or bitrot on the target.

FYI: this is being addressed in https://github.com/NixOS/nixpkgs/pull/24964

Strictly speaking, my PR isn't the only (or smallest) way to fix it, but it does give us some other advantages while also fixing this 😁

Fixed in master by #24964.


False-positive PLW1641 when setting __hash__ = <ParentClass>.__hash__

with v0.3.4, ruff check t.py --select PLW1641 on
class A:
    def __eq__(self, other):
        return False

    def __hash__(self):
        return 7

class B(A):
    def __eq__(self, other):
        return True

    __hash__ = A.__hash__

issues
PLW1641 Object does not implement `__hash__` method
   |
12 | class B(A):
   |       ^ PLW1641
13 |     def __eq__(self, other):
14 |         return True

even though the docs explicitly recommend this:

If a class that overrides eq() needs to retain the implementation of hash() from a parent class, the interpreter must be told this explicitly by setting __hash__ = <ParentClass>.__hash__.

This is now fixed.


ReentrantLock contention

Hi guys,
First on above: thanks for this awesome project and for the hard work on it!!!
Now my question: would be possible to have a contention profiling for Java's ReentrantLocks similar to the -e lock option?
I was looking http://www.brendangregg.com/offcpuanalysis.html to find something similar, given that under contention ReentrantLock uses Unsafe::park/unpark, but having it on the async-profiler toolkit would be awesome.
If there is something I could help to make it possible I would be very happy to contribute :+1:
Thanks,
Franz

Yes, this is absolutely possible. I think I can implement this if not in the nearest, then in the next release.

That's would be awesome, thanks!

-e lock now handles both intrinsic locks and ReentrantLocks.

Thanks for this change!!!
I've just refreshed by local repo with the last changes and compiled the whole with make.
I'm not a C guy and I'm hoping to do not have mess with anything...
I've built this test program:
   public static void main(String[] args) {
      final int tokens = 1;
      final boolean jucLock = true;
      final ReentrantLock lock = new ReentrantLock();
      final Object obj = new Object();
      final int writers = 4;
      final AtomicBoolean stop = new AtomicBoolean();
      ExecutorService executorService = Executors.newCachedThreadPool();
      for (int i = 0; i < writers; i++) {
         if (jucLock) {
            executorService.execute(() -> {
               while (!stop.get()) {
                  lock.lock();
                  Blackhole.consumeCPU(tokens);
                  lock.unlock();
               }
            });
         } else {
            executorService.execute(() -> {
               while (!stop.get()) {
                  synchronized (obj) {
                     Blackhole.consumeCPU(tokens);
                  }
               }
            });
         }
      }
      executorService.shutdown();
      Runtime.getRuntime().addShutdownHook(new Thread(() -> {
         stop.lazySet(true);
      }));
   }

Using synchronized I'm getting this:

While for the ReentrantLock I'm receiving from flamegraph:
ERROR: No stack counts found

Probably I've done something wrong on compilation or the test I've written has something wrong.
There is anything I could do to help beside looking at make output (that  doesn't seems to have emitted any warning/error)?

Works for me. How do you run the target program and the profiler? What JDK version do you use?
./profiler.sh -d 10 -e lock -f locks.svg PID generates the following flame graph:

thanks for the help :+1:

How do you run the target program and the profiler

So, running your command seems to not work for me, so I've tried this one instead:
$ ./profiler.sh -d 10 -o collapsed -f /tmp/collapsed.txt -e lock PID
$ ~/FlameGraph/flamegraph.pl --width=1920 --colors=java /tmp/collapsed.txt > lock.svg

There is anything I need to export (eg FLAMEGRAPH_HOME) in order to just use 1 command?

What JDK version do you use

java -version
openjdk version "1.8.0_161"
OpenJDK Runtime Environment (build 1.8.0_161-b14)
OpenJDK 64-Bit Server VM (build 25.161-b14, mixed mode)

While I'm using the last master of async.profiler and configured the last Fedora with:
$ sudo dnf debuginfo-install java
-- install Package java-1.8.0-openjdk-debuginfo-1:<IP_ADDRESS>-5.b14.fc27.x86_64
$ sudo dnf install java-debug
-- Package java-1.8.0-openjdk-debug-1:<IP_ADDRESS>-5.b14.fc27.x86_64

Before running make with no errors.

I guess in your case the number of contended intrinsic locks is so small comparing to ReentrantLocks, that intrinsic locks were skipped as negligible from the result flamegraph.
You may modify the threshold with --minwidth argument or try different output format (e.g. -o traces) to make sure intrinsic locks are still there.

I guess in your case the number of contended intrinsic locks is so small comparing to ReentrantLocks, that intrinsic locks were skipped as negligible from the result flamegraph.

Guess correct!
Thanks to have added this feature in such a small time!  :+1:


Add more detail to the README

Added more detail to the synopsis section at the top of the README which may make it easier for developers to understand Nautobot #2591

@bryanculver Waiting for your feedback

Done @bryanculver

@Santhusha-bit Please resolve the markdownlint issue: https://github.com/nautobot/nautobot/actions/runs/3236622066/jobs/5392840607


License ?

Hello, under what license is this project released under ? Thank-you.

Good point, I've given it an MIT License.


Support jinja2 2.8

Hi,
Could you add support for jinja2 2.8? I don't know why this version is excluded in the setup.py file.

Fixed in 37aecf52db6f5fd52cdb9e288fde80fa45a37c19

Can we get 2.10 now? I'd open a new issue, but this one is still open.

What's the status on this?


Feature/adding hebrew translation

Hi,
I have translated README.md to Hebrew and created the file README.hb.md.
I had some trouble with the annotation since Hebrew is written from right to left. I looked at other readme files with the same annotation and saw that they wrapped text with a div element that had an attribute of dir.
Also, I would request your assistance in how I can add an emoji with the Israeli flag, so that I can add it to the main README.md.

@TomerPacific, when I checked https://github.com/Roshanjossey/first-contributions/blob/dc96e3cdd6825397e5836f92da5d025a38d9f15c/translations/README.hb.md, I see that the images and links are not rendering correctly.
From what I understand, this is because HTML is used for rtl. This might be preventing Markdown from rendering correctly inside HTML.
Could you please do everything in HTML? You can check Arabic translation for more info

@Roshanjossey ,
on it.

Thank you for making these changes @TomerPacific. ✨ 🖖


Add a method to the DebateService that let's us modify the DebateRoom and the invitee as the second participant or speaker

a965ee9c2958af7e9da46ac595f70ffc15e29da3


Get Started and Components page styles update

List of updates:

Highlighted languages for readme.md files were added
Common styles were added to page.less
HTML structure of Get Started and Components pages was a bit updated

Closes: https://github.com/exadel-inc/ui-playground/issues/469

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


How to differentiate between two keyboards

I have two keyboards attaches to my Windows 7 computer.
Is it possible to know which keyboard sends the input when a keyboard event triggers.
I really need this function in my project.
Can anyone help me out with this.
Thanks a lot

Duplicate of #103 ?

Goo catch @robatwilliams , closing this one in favor of #103


[tests-only][full-ci]Json assertion apigraph master branch

Description
This PR is the forward port of the json-assertion in suite apiGraph https://github.com/owncloud/ocis/pull/5798. It also adds the missing schema assertion for the new steps in the master branch in apiGraph suite. And also updates the expexted to failure line numbers.
Related Issue:
https://github.com/owncloud/ocis/issues/3179

E2E tests failed: https://drone.owncloud.com/owncloud/ocis/21092/88/1
:boom: To see the trace, please open the link in the console ...

npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/21092/tracing/folder-alice-2023-4-4-04-36-16.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/21092/tracing/folder-brian-2023-4-4-04-36-30.zip


branson/refactor

Hmmmm what is wrong with <=  ?

Needa address the case where splitInput is empty or first element of splitInput is an empty string

Interesting so after 1 second time delay it changes back to original styling? But shouldn't it remain as a warning style until something

hahah that means i need to get the CommandBox to manipulate ResultDisplay's CSS. It might be better, am also considering it


Chat - User deletes attachment from uploading attachment text, yet video is shown.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.59
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4472299
Issue reported by: Applause - Internal Team
Action Performed:

Launch app
Tap on a report
Tal plus icon --- add attachment
Upload an mp4 video
Tap send
In conversation page, long press text uploading attachment
Tap delete and confirm deleting it

Expected Result:
User deletes attachment from uploading attachment text, video message must not be shown
Actual Result:
User deletes attachment from uploading attachment text, yet video is shown
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/87e4563d-5b24-44a2-a23a-01cc7a916aff
View all open jobs on GitHub

@CortneyOfstad  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

Still working to recreate this 👍

Going to work with Stevie since I don't have an android

I am unable to reproduce this, so going to apply Needs Reproduction on this to see if anyone gets consistent results 👍

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

Still waiting on someone to pick this up 👍

If I don't hear anything by EOD, going to present to SM or CS 👍

@CortneyOfstad Issue is not reproducible
https://github.com/Expensify/App/assets/78819774/df8a93b0-234d-455d-bcfd-00eecdb402b5

Thanks @lanitochka17! Since this is not reproducible, going to close! Feel free to reopen if it pops up again!


Doesn´t add up

After I Upgraded Goaccess to 4.1.1 the statistic look very strange:

Could you please describe what you mean with statistic look very strange? e.g., data-wise, numbers wrong, user interface? Thanks

I will try to explain what does not go together. If you look at the screenshot, I have received 13,493,850 hits in about a month, it does not get even in a year. If you look at exclusive hits, it is usually around 2000 hits.
To rule out if I had been attacked, I looked at the section ipadress and hostname, where it does not coincide with the total value of the summary.
Now I have gone back to version 1.4, where admittedly a bug means that I have to restart goaccess every day to get goaccess to read the new log file after rotation.
(translated from swedish in google translate)

Hi @allinurl
I believe it is the problem in identifying that the file has been rotated and therefore it is now a new one.
Perhaps GOACCESS should be reprocessing the entire file, similarly to what happened to me in real-time.
 -- So he is running in real-time?
Solution: upgrade to version 1.4.2

@0bi-w6n-K3nobi
Yes, I´m run goaccess in realtime.

Hi @tellustheguru
My problem is described in issue #1958.
But, it is very long and has other subjects as well.
@allinurl fix it in patch a43993b.
The problem occurs if you are using more than (one) 1 LOG.
So, you will need to compile from upstream or upgrade to version 1.4.2

@tellustheguru question for you, did you use either --restore or --persist? I ask because there was an issue with the overall count when attempting to restore from disk which was fixed on v1.4.1. Please upgrade to v1.4.2 for accurate counting BUT you will need to delete your old database files and parse your logs form scratch.
Also, just so I understand better your concern. the 13,493,850 hits, is that what you are comparing against the total in the IP panel? I can't see that total so I'm not sure where the issue is exactly.
From what I can see, looks like you got a few visitors that are hitting your server a lot. I'm not sure what kind of traffic you have so is hard for me to judge, but you could correlate some data, for instance, first IP on the list has visited you only 6 times in one month and has generated that amount of hits to your server/website. So it does look like a bot, but again, hard to say not know the type of website you offer.

Not sure if original poster meant the same, but I also notice that the totals (e.g. total Visitors in UNIQUE VISITORS PER DAY - INCLUDING SPIDERS) are a sum of unique visitors per day. This may very well be (and mostly surely are) the same visitors day-to-day, but are counted as unique for the whole period by adding uniques from every day. Same goes for other metrics.

Sorry, I guess I'm not seeing the issue here. Should the total Visitors on that panel be different than the sum of unique visitors per day? Thanks.

@allinurl, if every day there are different unique visitors then it would be correct. But imagine that every day the visitors are almost the same (true in my case, e.g.): then unique visitors per day are correct, but if you just sum them up for a month total, then the total won't make sense. Because in reality it's all the same visitors every day, so number of unique visitors per month should be almost the same as per day.

@andreychirikba I see and thanks for expanding on that. Currently the way the visitors count works is by generating a unique key composed of IP/date/UA. So the overall count essentially is the summation of each date unique count. This hasn't changed since early versions of goaccess so like you said, I'm not sure if the original poster meant that? BTW, here are some additional notes on this.
However, you could also get a 'more' unique count by looking at the "VISITOR HOSTNAMES AND IPS" panel, which should give you a better sense of actual unique IPs. #117 will add filters, allowing you to see the stats for a given period of time.
Other than that, I don't know if there's a way to keep track of recurring visitors without getting into cookies/sessions. Any feedback/ideas are always welcome :)

I upgraded to 1.4.3 it is now working.


Extension method for calling health check of other services

Codecov Report

Merging #160 (b2f56e3) into main (c842a55) will increase coverage by 20.50%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##             main     #160       +/-   ##
===========================================
+ Coverage   45.82%   66.33%   +20.50%
===========================================
  Files          38      104       +66
  Lines         491     2085     +1594
  Branches       65      230      +165
===========================================
+ Hits          225     1383     +1158
- Misses        255      636      +381
- Partials       11       66       +55

Flag
Coverage Δ

logging
78.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...tics/HealthChecks/HealthChecksBuilderExtensions.cs
0.00% <0.00%> (ø)

...eLiveEndpointHealthCheck/ServiceLiveHealthCheck.cs
0.00% <0.00%> (ø)

...stCommon/FunctionAppHost/FunctionAppHostManager.cs
0.00% <0.00%> (ø)

.../ServiceBus/ListenerMock/WhenProviderExtensions.cs
100.00% <0.00%> (ø)

...ntHub/ResourceProvider/EventHubResourceProvider.cs
92.72% <0.00%> (ø)

...urce/FunctionApp.TestCommon/FunctionAppTestBase.cs
0.00% <0.00%> (ø)

.../RequestResponseMiddleware/Models/IndexTagsKeys.cs
100.00% <0.00%> (ø)

...unctionAppHost/FunctionAppHostManagerExtensions.cs
0.00% <0.00%> (ø)

...mon/ServiceBus/ListenerMock/AssertionExtensions.cs
57.14% <0.00%> (ø)

...source/RequestResponseMiddleware/Models/LogTags.cs
90.69% <0.00%> (ø)

... and 57 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


DQN for flow

Hi,
This is a branch to enable DQN (also by ray) for flow.
Currently it supports single agent and multi-agent tests on traffic_light_grid scripts.
Other examples can be easily enabled by modifying corresponding example file, env file and test file,  according to the modifications in this branch.
Cheers,
Pengyuan

Ya I have zero ideas why the build fails, it works on my pc (without the unittest).

Putting aside the build failure, this sets RLlibs DQN as the default option. We'd prefer you make it so that there's a choice of algorithm, of which DQN is one. You can look at train.py in the flow_maddpg branch for an example.

Putting aside the build failure, this sets RLlibs DQN as the default option. We'd prefer you make it so that there's a choice of algorithm, of which DQN is one. You can look at train.py in the flow_maddpg branch for an example.

Sure, I'll revise it. BTW in that train.py, is the TD3 in setup_exps_rllib same with the one in h-baseline?

Putting aside the build failure, this sets RLlibs DQN as the default option. We'd prefer you make it so that there's a choice of algorithm, of which DQN is one. You can look at train.py in the flow_maddpg branch for an example.

Hi Eugene, I've modified the code according to mappdg's fashion.
Cheers.

Well, not quite. The implementation of TD3 in h-baselines is not identical to the rllib one.

This looks good to me minus comments! @pengyuan-zhou if the changes are made I will merge.

@AboudyKreidieh @kanaadp @kjang96

Hey! I'm really sorry about the state of things here, we are working on getting a new maintainer in the next week or so so this doesn't happen again.


Command Line Arguments

If the main application is launched with some command line arguments and needs to be relaunched via NAppUpdater update.exe, the arguments are lost.
Suggested changes:
Add RelaunchAppArgs property to NauConfigurations class and utilize in Appstart.cs

Have made the required changes. Is it ok to send a pull request ?

Yes please! thanks!

Kindly advise status. Thanks!


Support LTS .Net Core 3.1

Upgraded Project References to Support LTS .Net Core 3.1

it seems the SDK 3.1.100 is not yet available in Azure hosted tool cache.

Thanks for the PR. Will review and test this soon

Can you update the dotnet version here https://github.com/nabinked/NToastNotify/blob/1d8805ce34ca7abfa8f12927689ba488dfef4ce4/azure-pipelines.yml#L27
and see if the builds pass ?

That did it! Thanks


message-of-the-day-configuration.update-type has no effect

When configuring the message of the day, the update-type field appears to have no effect on the behavior of message rotation. Regardless of whether it's set to RANDOM or QUEUE it will first select the third listed motd (or the first if there are less than three) and go through them sequentially from there. Additionally, it will reset this looping behavior, starting with the third (or first) option again on every server restart. This means that any server which restarts regularly will go through the same list of options in the same order after every restart even when RANDOM is selected.

Actually something is up, thank you for the notification!

Fix: #32


use too many memcpy in UART ISR

@ming6842, I think too many memcpy will increase the time in ISR.
in /program/ext_device/lea6h_ubx.c line 39
void UART4_IRQHandler(void)

e34cb53291bfd229f7f099cf0c361f6f9d89228e should solve it


Add TypeScript definitions for v15.0.0.

This pull request adds TypeScript definitions for v15.0.0 of redux-little-router. It focuses on typing the high level aspects of the API, including actions, the Location and History interfaces, routers, and the Link and Fragment components. There is a demo repository created here to demonstrate using redux-little-router with TypeScript. The demo repository copies over the demo/client app, successfully passing the TS compiler. To run the demo locally, follow the instructions in the README.

Type definitions were also created for server-side rendering, but have not been tested against a demo app. This will be important to do before shipping a new release.
Unfortunately, the types submitted to DefinitelyTyped don't fully support the API in its current state. Running the demo repository against these types results in the following Terminal output:

I am concerned that folks using the API with the definitions on DefintelyTyped may run into issues where parts of our API that are supported in JS will not pass the TS compiler because of incorrect typings. Shipping our own TypeScript definitions with redux-little-router ensures we keep them current and consistent with the latest version of our API. I would love to have some folks review these types, critique them, and expand them if possible.

@tptee @ryan-roemer I think I'll need to add in defs for the immutable aspects of the API so the compiler won't yell about imports, I'll make the fix and push to this PR.

@tptee @ryan-roemer Types have been added for the immutable aspects of the API. There is also a corresponding branch in the rlr-ts repo, immutable-demo, that verifies the types pass the compiler. webpack is correctly resolving the pointer to the ES build as well (redux-little-router/es/immutable/index.js). Let me know how I can help you out further!

@tptee We should be good to merge! I tightened up those definitions – they actually helped me to uncover an issue from the old typings that was over-restrictive on the data structures we could store in the routes object. Good eye! 🎉 💯


Logistic Example

In ch2 Logistic example, when we assume our data follows logistic, why then use Bernoulli after that? In previous examples we only had an assumption of the data distribution and calculated the likelyhood form that. But here why has Bernoulli suddenly appeared when we already get a probability from logistic?
def challenger_joint_log_prob(D, temperature_, alpha, beta):
    """
    Joint log probability optimization function.

    Args:
      D: The Data from the challenger disaster representing presence or
         absence of defect
      temperature_: The Data from the challenger disaster, specifically the temperature on
         the days of the observation of the presence or absence of a defect
      alpha: one of the inputs of the HMC
      beta: one of the inputs of the HMC
    Returns:
      Joint log probability optimization function.
    """
    rv_alpha = tfd.Normal(loc=0., scale=1000.)
    rv_beta = tfd.Normal(loc=0., scale=1000.)

    # make this into a logit
    logistic_p = 1.0/(1. + tf.exp(beta * tf.to_float(temperature_) + alpha))

    rv_observed = tfd.Bernoulli(probs=logistic_p)

    return (
        rv_alpha.log_prob(alpha)
        + rv_beta.log_prob(beta)
        + tf.reduce_sum(rv_observed.log_prob(D))
    )

In general its because you need to be able to sample from a distribution, the logistic_p tensor / function is only an estimate of the mean, that is, its just a parameter. The likelihood / pmf on the other hand is calculated using this parameter, you can find it here, in the article they express it using conditionals but you can write it as an equation. To estimate the parameters you need to calculate the log-likelihood which is just the sum of the logarithm of the likelihood over the data / batch, which is what the tf.reduce_sum(rv_observed.log_prob(D)) line is doing.

I believe the formula for the log likelihood of the bernoulli distribution is the same as the sigmoid cross entropy loss function, so looking at it from this perspective, this function is returning a loss, not the predictions.

Got it! So we just get the probability from the logistic function and now since we have to calculate the likelihood, we use the Bernoulli function to do so with this p. Thanks @cgarciae
Can you please explain your second comment about sigmoid cross entropy abit more. Yes, the likleyhood term is the same as the cross entropy without the 1/n and without the negative sign . However we do have a prior term which dictates, for each value of the parameter, how much the loss should be weighted. Which kind of influences the effect that this likleyhood will have on the update. I would be interested in hearing/discussing more about this.


tag storage node and add to Rook later

Cluster.yml adds in the storage node right away. Can it be added later via a tag?
Use the master at first (via RookDir FS) and then later lab add storage. Students add a tag "storage" to the node and then Rook adds it? (new Lab # needed)

I think this should addressed by #12
The idea is to uncomment the second node from the inventory, run scale.yml then the node shows up in Kubernetes.


fix to yaml parse error causing Helm check failure

Error: YAML parse error on harbor/templates/registry/registry-ss.yaml: error converting YAML to JSON: yaml: line 63: did not find expected key

Coverage increased (+0.03%) to 60.718% when pulling 7c3daea0061b13f56c828ac02ecb13f5fa4e18cc on MnrGreg:patch-1 into b4a4eb11c6c3c33eb1df87d1f44191bf10d3303a on vmware:master.


Build with sbt and fix scalastyle checks.

I want to build the project with sbt mainly because i want to set it up with ensime.
However, the build with sbt (./build/sbt -Pkubernetes -Phadoop-2.6 -Pkubernetes-integration-tests -Pmesos -Pyarn -Phive compile test:compile) failed with scalastyle check errors:
$ ./dev/scalastyle
Scalastyle checks failed at following occurrences:
[error] /data/github/spark/spark-k8s/resource-managers/kubernetes/core/src/test/scala/org/apache/spark/deploy/rest/kubernetes/v2/ResourceStagingServerSslOptionsProviderSui
te.scala:99: File line length exceeds 100 characters
[error] /data/github/spark/spark-k8s/resource-managers/kubernetes/core/src/test/scala/org/apache/spark/deploy/kubernetes/SSLUtils.scala:23:0: import.ordering.wrongOrderInG
roup.message
[error] (kubernetes/test:scalastyle) errors exist
[error] Total time: 10 s, completed Apr 23, 2017 3:34:14 PM

@mccheah Can we merge this one?

This LGTM. Merging

Thanks @lins05


build-rust-crate: add stripExclude for .rlib

Description of changes
This disables stripping .rlib files when building crates, which is needed on macOS because it removes metadata that Rust needs
Follow up to https://github.com/NixOS/nixpkgs/pull/218783
Fixes https://github.com/NixOS/nixpkgs/issues/218712
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2675

@SuperSandro2000 done!


nixos/udisks2: add package option

Description of changes

Allows using a custom udisks2 without an overlay.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

What's the problem with using an overlay?

To be honest, I didn't test an overlay because I was assuming it would lead to rebuilds of huge parts of the graphical stack. Apparently not, in my case in fact it rebuilds nothing at all.
Still, package options for services are always great to have because it makes replacing the package the service should use straightforward. In this case, you need to at least figure out if pkgs.udisks or pkgs.udisks2 is the right one to replace because one is an alias to the other. You can't do that without looking at all-packages.nix.

@2xsaiko please rebase


Getting Gauge crashed exception

From @sguptatw on December 7, 2018 3:43
Expected behavior
Should be able to work with Gauge IDE features seamlessly
Actual behavior
09:08:44.953 request #1: textDocument/codeAction: runtime error: invalid memory address or nil pointer dereference
goroutine 43 [running]:
runtime/debug.Stack(0xc0001b3410, 0xa540e0, 0x106a990)
	/usr/local/Cellar/go/1.11.1/libexec/src/runtime/debug/stack.go:24 +0xae
github.com/getgauge/gauge/api/lang.recoverPanic(0xc0004564b0)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/server.go:291 +0x5e
panic(0xa540e0, 0x106a990)
	/usr/local/Cellar/go/1.11.1/libexec/src/runtime/panic.go:513 +0x1c7
github.com/getgauge/gauge/api/lang.createConceptInfo(0xc0004120f0, 0x46, 0x0, 0x0, 0x1, 0xc0002defc0, 0x0)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/codeAction.go:90 +0x25b
github.com/getgauge/gauge/api/lang.getSpecCodeAction(0xc0004120f0, 0x46, 0x0, 0x0, 0x1b, 0x0, 0xc000342840, 0x1, 0x4, 0xc0000aa480, ...)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/codeAction.go:52 +0x387
github.com/getgauge/gauge/api/lang.codeActions(0xc0004564b0, 0xb2ca3d, 0x17, 0x1, 0xffffffffffffffff)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/codeAction.go:44 +0x169
github.com/getgauge/gauge/api/lang.(*LangHandler).Handle(0x109c398, 0xbd9ac0, 0xc0000300f8, 0xbd7940, 0xc0004446c0, 0xc0004564b0, 0x0, 0x0, 0x0, 0x0)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/server.go:159 +0x1d44
github.com/getgauge/gauge/api/lang.(*LangHandler).handle(0x109c398, 0xbd9ac0, 0xc0000300f8, 0xc0004446c0, 0xc0004564b0, 0x0, 0x0, 0x0, 0x0)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/server.go:72 +0xad
github.com/getgauge/gauge/api/lang.(*LangHandler).handle-fm(0xbd9ac0, 0xc0000300f8, 0xc0004446c0, 0xc0004564b0, 0x0, 0x0, 0x0, 0x0)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/server.go:63 +0x59
github.com/getgauge/gauge/vendor/github.com/sourcegraph/jsonrpc2.HandlerWithError.Handle(0xc000057350, 0xbd9ac0, 0xc0000300f8, 0xc0004446c0, 0xc0004564b0)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/vendor/github.com/sourcegraph/jsonrpc2/handler_with_error.go:14 +0x76
created by github.com/getgauge/gauge/api/lang.lspHandler.Handle
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/server.go:67 +0x72

Steps to replicate

Create a new gauge-java project
Add a new step. When the step is partially highlighted initiate a code action.

The above error can be observed

Version
Gauge version: 1.0.4.nightly-2018-12-03
Commit Hash: 62a48e5

Plugins
-------
java (0.7.0.nightly-2018-12-04)

Blocks https://github.com/getgauge/gauge-vscode/issues/83

Copied from original issue: getgauge/gauge-java#206

Got this exception again in gauge-js project. This time I was editing a specification. There were couple of unimplemented steps which I made a comment by removing the *. Then the following error occurred.
Here are the LSP logs of the same. Hope this helps!
12:01:48.688 --> request #0: initialize: {"processId":39516,"rootPath":"c:\\work\\gauge\\FT\\gauge-e2e-taiko","rootUri":"file:///c%!A(MISSING)/work/gauge/FT/gauge-e2e-taiko","capabilities":{"workspace":{"applyEdit":true,"workspaceEdit":{"documentChanges":true,"resourceOperations":["create","rename","delete"],"failureHandling":"textOnlyTransactional"},"didChangeConfiguration":{"dynamicRegistration":true},"didChangeWatchedFiles":{"dynamicRegistration":true},"symbol":{"dynamicRegistration":true,"symbolKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]}},"executeCommand":{"dynamicRegistration":true},"configuration":true,"workspaceFolders":true},"textDocument":{"publishDiagnostics":{"relatedInformation":true},"synchronization":{"dynamicRegistration":true,"willSave":true,"willSaveWaitUntil":true,"didSave":true},"completion":{"dynamicRegistration":true,"contextSupport":true,"completionItem":{"snippetSupport":true,"commitCharactersSupport":true,"documentationFormat":["markdown","plaintext"],"deprecatedSupport":true,"preselectSupport":true},"completionItemKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25]}},"hover":{"dynamicRegistration":true,"contentFormat":["markdown","plaintext"]},"signatureHelp":{"dynamicRegistration":true,"signatureInformation":{"documentationFormat":["markdown","plaintext"]}},"definition":{"dynamicRegistration":true},"references":{"dynamicRegistration":true},"documentHighlight":{"dynamicRegistration":true},"documentSymbol":{"dynamicRegistration":true,"symbolKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]},"hierarchicalDocumentSymbolSupport":true},"codeAction":{"dynamicRegistration":true,"codeActionLiteralSupport":{"codeActionKind":{"valueSet":["","quickfix","refactor","refactor.extract","refactor.inline","refactor.rewrite","source","source.organizeImports"]}}},"codeLens":{"dynamicRegistration":true},"formatting":{"dynamicRegistration":true},"rangeFormatting":{"dynamicRegistration":true},"onTypeFormatting":{"dynamicRegistration":true},"rename":{"dynamicRegistration":true,"prepareSupport":true},"documentLink":{"dynamicRegistration":true},"typeDefinition":{"dynamicRegistration":true},"implementation":{"dynamicRegistration":true},"colorProvider":{"dynamicRegistration":true},"foldingRange":{"dynamicRegistration":true,"rangeLimit":5000,"lineFoldingOnly":true}},"saveFiles":true},"trace":"off","workspaceFolders":[{"uri":"file:///c%!A(MISSING)/work/gauge/FT/gauge-e2e-taiko","name":"gauge-e2e-taiko"}]}
12:01:48.688 <-- result #0: initialize: {"capabilities":{"textDocumentSync":1,"completionProvider":{"resolveProvider":true,"triggerCharacters":["*","* ","\"","\u003c",":",","]},"definitionProvider":true,"documentSymbolProvider":true,"workspaceSymbolProvider":true,"codeActionProvider":true,"codeLensProvider":{},"documentFormattingProvider":true,"renameProvider":true}}
12:01:48.688 --> notif: initialized: {}
12:01:48.688 <-- request #0: client/registerCapability: {"registrations":[{"id":"gauge-fileWatcher","method":"workspace/didChangeWatchedFiles","registerOptions":{"watchers":[{"globPattern":"c:/work/gauge/FT/gauge-e2e-taiko/**/*{.cpt,.spec,.md}","kind":5}]}}]}
12:01:48.689 --> notif: textDocument/didOpen: {"textDocument":{"uri":"file:///c%!A(MISSING)/work/gauge/FT/gauge-e2e-taiko/specs/specifications.spec","languageId":"gauge","version":30,"text":"# Specifications with scenarios\r\n\r\n## Passing Scenarios\r\n* create Project with specifications \"data/passingScenarios\" with implementation \"data/language_features\"\r\n* Run Gauge and ensure success\r\n* open Report\r\n* verify project name\r\n* verify specs statistics in html with \r\n\r\n   |totalCount|passCount|failCount|skippedCount|\r\n   |----------|---------|---------|------------|\r\n   |1         |1        |0        |0           |\r\n* verify scenario statistics in html with \r\n\r\n   |totalCount|passCount|failCount|skippedCount|\r\n   |----------|---------|---------|------------|\r\n   |2         |2        |0        |0           |\r\n\r\n* click Specification \"Basic specification with passing scenarios\"\r\n* verify scenario \"Scenario1\" is displayed above scenario \"Scenario2\"\r\nVerify that execution time is displayed for the scenario\r\nVerify that execution time is displayed for every step\r\n\r\n## Pass, Failed and skipped Scenarios\r\n* create Project with specifications \"data/passFailSkipped\" with implementation \"data/language_features\"\r\n* Run Gauge and ensure failure\r\n* open Report\r\n* verify specs statistics in html with \r\n\r\n   |totalCount|passCount|failCount|skippedCount|\r\n   |----------|---------|---------|------------|\r\n   |1         |0        |1        |0           |\r\n* verify scenario statistics in html with \r\n\r\n   |totalCount|passCount|failCount|skippedCount|\r\n   |----------|---------|---------|------------|\r\n   |3         |1        |1        |1           |\r\n* click Specification \"One Pass, one fail and one skipped\"\r\n* verify scenario \"Failing Scenario\" is displayed above scenario \"Skipped Scenario\"\r\n* verify scenario \"Skipped Scenario\" is displayed above scenario \"Passing Scenario\"\r\n* verify Error details are displayed for the failing step\r\n* verify screenshot is displayed for the failing step"}}
12:01:48.691 --> result #0: client/registerCapability: null
12:01:48.691 --> request #1: textDocument/codeAction: {"textDocument":{"uri":"file:///c%!A(MISSING)/work/gauge/FT/gauge-e2e-taiko/specs/specifications.spec"},"range":{"start":{"line":21,"character":0},"end":{"line":21,"character":0}},"context":{"diagnostics":[{"range":{"start":{"line":21,"character":0},"end":{"line":21,"character":56}},"message":"Step implementation not found","severity":1,"code":"step(\"Verify that execution time is displayed for every step\", async function() {\n\tthrow 'Unimplemented Step';\n});"}]}}
12:01:48.700 <-- notif: window/logMessage: {"type":1,"message":"An error occurred. Refer lsp.log for more details."}
12:01:48.703 request #1: textDocument/codeAction: runtime error: invalid memory address or nil pointer dereference
goroutine 62 [running]:
runtime/debug.Stack(0xc000411410, 0xa540e0, 0x106a990)
	/usr/local/Cellar/go/1.11.1/libexec/src/runtime/debug/stack.go:24 +0xae
github.com/getgauge/gauge/api/lang.recoverPanic(0xc000318320)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/server.go:291 +0x5e
panic(0xa540e0, 0x106a990)
	/usr/local/Cellar/go/1.11.1/libexec/src/runtime/panic.go:513 +0x1c7
github.com/getgauge/gauge/api/lang.createConceptInfo(0xc00032aa00, 0x44, 0x15, 0x0, 0x1, 0xc0002fae40, 0x0)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/codeAction.go:90 +0x25b
github.com/getgauge/gauge/api/lang.getSpecCodeAction(0xc00032aa00, 0x44, 0x15, 0x0, 0x15, 0x0, 0xc00035ef20, 0x1, 0x4, 0x0, ...)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/codeAction.go:52 +0x387
github.com/getgauge/gauge/api/lang.codeActions(0xc000318320, 0xb2ca3d, 0x17, 0x1, 0xffffffffffffffff)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/codeAction.go:44 +0x169
github.com/getgauge/gauge/api/lang.(*LangHandler).Handle(0x109c398, 0xbd9ac0, 0xc000078120, 0xbd7940, 0xc0003024e0, 0xc000318320, 0x0, 0x0, 0x0, 0x0)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/server.go:159 +0x1d44
github.com/getgauge/gauge/api/lang.(*LangHandler).handle(0x109c398, 0xbd9ac0, 0xc000078120, 0xc0003024e0, 0xc000318320, 0x0, 0x0, 0x0, 0x0)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/server.go:72 +0xad
github.com/getgauge/gauge/api/lang.(*LangHandler).handle-fm(0xbd9ac0, 0xc000078120, 0xc0003024e0, 0xc000318320, 0x0, 0x0, 0x0, 0x0)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/server.go:63 +0x59
github.com/getgauge/gauge/vendor/github.com/sourcegraph/jsonrpc2.HandlerWithError.Handle(0xc0003680c0, 0xbd9ac0, 0xc000078120, 0xc0003024e0, 0xc000318320)
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/vendor/github.com/sourcegraph/jsonrpc2/handler_with_error.go:14 +0x76
created by github.com/getgauge/gauge/api/lang.lspHandler.Handle
	/Users/stechops/Documents/go-agent-17.4.0/pipelines/Gauge-Nightly/src/github.com/getgauge/gauge/api/lang/server.go:67 +0x72

From @Apoorva-GA on December 7, 2018 8:8
Unable to replicate the issue, as the unimplemented step is completely highlighted by diagnostics.


Client Agent Training HAC

We currently have SMARTS using remote agents from only a social agent use case with agent workers. The purpose is to have a learning vehicle on the other side as a learning client agent rather than a contributing agent.

This is not an urgent feature.


ZWave Stops working after updating from 0.88.2 to 0.89.1

Home Assistant release with the issue:
0.89.1
Last working Home Assistant release (if known):
0.88.2
Operating environment (Hass.io/Docker/Windows/etc.):
hass.io
Component/platform:
zwave
Description of problem:
So I have about 50 Zwave nodes and after the initial upgrade from 0.88.2 to 0.89.1 they work. But if I restart HASSIO only my Zwave stick is found. If I revert back to 0.88.2 snapshot it all works still with no restart of the system.
The only node showing on 0.89.1 after restarting is my Zwave stick (aeotec gen 5)
Anyone else having this issue and what can I provide for troubleshooting to get this fixed? Thanks!

My Hassbian works running version 0.89.1 (aeotec gen 5),  15 zwave devices.

My guess is that it is not related to 0.89.1. I would guess that you have hit the same issue I have seen randomly at restart of HA. Also once after an upgrade.
And twice the issue locked up in a state where I had to restore a snapshot config.
See https://github.com/home-assistant/home-assistant/issues/21165. If this is true then you should be able to upgrade again and have a chance that it works. And if it does please update bug 21165 because at the moment that bug report gets very little attention

Experiencing this as well with 0.89.1. Haven't had any issues until this version.
Sometimes there are no nodes, sometimes just the Zooz ZST10 shows up and eventually after many restarts, the rest of the nodes will show up.
2019-03-11 21:59:47.201 Always, OpenZwave Version 1.4.3322 Starting Up
2019-03-11 21:59:52.861 Info, Setting Up Provided Network Key for Secure Communications
2019-03-11 21:59:52.861 Info, mgr,     Added driver for controller /dev/ttyACM0
2019-03-11 21:59:52.862 Info,   Opening controller /dev/ttyACM0
2019-03-11 21:59:52.862 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
2019-03-11 21:59:52.862 Info, Serial port /dev/ttyACM0 opened (attempt 1)
2019-03-11 21:59:52.862 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-03-11 21:59:52.862 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-03-11 21:59:52.862 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-03-11 21:59:52.862 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-03-11 21:59:52.862 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-03-11 21:59:52.862 Detail,
2019-03-11 21:59:52.862 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-03-11 21:59:52.864 Detail, contrlr,   Received: 0x01, 0x10, 0x01, 0x15, 0x5a, 0x2d, 0x57, 0x61, 0x76, 0x65, 0x20, 0x36, 0x2e, 0x30, 0x32, 0x00, 0x01, 0x92
2019-03-11 21:59:52.864 Detail,
2019-03-11 21:59:52.864 Info, contrlr, Received reply to FUNC_ID_ZW_GET_VERSION:
2019-03-11 21:59:52.864 Info, contrlr,     Static Controller library, version Z-Wave 6.02
2019-03-11 21:59:52.864 Detail, Node045,   Expected reply was received
2019-03-11 21:59:52.864 Detail, Node045,   Message transaction complete
2019-03-11 21:59:52.864 Detail,
2019-03-11 21:59:52.864 Detail, contrlr, Removing current message
2019-03-11 21:59:52.865 Detail,
2019-03-11 21:59:52.865 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-03-11 21:59:52.871 Detail, contrlr,   Received: 0x01, 0x08, 0x01, 0x20, 0xe8, 0x3a, 0xce, 0x78, 0x01, 0xb3
2019-03-11 21:59:52.871 Detail,
2019-03-11 21:59:52.871 Info, contrlr, Received reply to FUNC_ID_ZW_MEMORY_GET_ID. Home ID = 0xe83ace78.  Our node ID = 1
2019-03-11 21:59:52.871 Detail, Node058,   Expected reply was received
2019-03-11 21:59:52.871 Detail, Node058,   Message transaction complete
2019-03-11 21:59:52.871 Detail,
2019-03-11 21:59:52.871 Detail, contrlr, Removing current message
2019-03-11 21:59:52.871 Detail,
2019-03-11 21:59:52.871 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-03-11 21:59:52.873 Detail, contrlr,   Received: 0x01, 0x04, 0x01, 0x05, 0x08, 0xf7
2019-03-11 21:59:52.873 Detail,
2019-03-11 21:59:52.873 Info, contrlr, Received reply to FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES:
2019-03-11 21:59:52.873 Info, contrlr,     There is no SUC ID Server (SIS) in this network.
2019-03-11 21:59:52.873 Info, contrlr,     The PC controller is a primary controller.
2019-03-11 21:59:52.873 Detail, Node247,   Expected reply was received
2019-03-11 21:59:52.873 Detail, Node247,   Message transaction complete
2019-03-11 21:59:52.873 Detail,
2019-03-11 21:59:52.873 Detail, contrlr, Removing current message
2019-03-11 21:59:52.873 Detail,
2019-03-11 21:59:52.873 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-03-11 21:59:52.877 Detail, contrlr,   Received: 0x01, 0x2b, 0x01, 0x07, 0x02, 0x01, 0x02, 0x7a, 0x04, 0x01, 0x00, 0x02, 0xfe, 0x87, 0x7f, 0x88, 0xcf, 0x7f, 0xc0, 0x4f, 0xfb, 0xdf, 0xfd, 0xe0, 0x67, 0x00, 0x80, 0x80, 0x00, 0x80, 0x86, 0x00, 0x01, 0x00, 0xe8, 0x73, 0x00, 0x80, 0x0f, 0x00, 0x00, 0x60, 0x00, 0x00, 0x32
2019-03-11 21:59:52.877 Detail,
2019-03-11 21:59:52.877 Info, contrlr,  Received reply to FUNC_ID_SERIAL_API_GET_CAPABILITIES
2019-03-11 21:59:52.877 Info, contrlr,     Serial API Version:   2.1
2019-03-11 21:59:52.877 Info, contrlr,     Manufacturer ID:      0x027a
2019-03-11 21:59:52.877 Info, contrlr,     Product Type:         0x0401
2019-03-11 21:59:52.877 Info, contrlr,     Product ID:           0x0002
2019-03-11 21:59:52.877 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_RANDOM: 0x01, 0x04, 0x00, 0x1c, 0x20, 0xc7
2019-03-11 21:59:52.877 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_INIT_DATA: 0x01, 0x03, 0x00, 0x02, 0xfe
2019-03-11 21:59:52.877 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_SET_TIMEOUTS: 0x01, 0x05, 0x00, 0x06, 0x64, 0x0f, 0x97
2019-03-11 21:59:52.877 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_APPL_NODE_INFORMATION: 0x01, 0x07, 0x00, 0x03, 0x01, 0x02, 0x01, 0x00, 0xf9
2019-03-11 21:59:52.877 Detail, Node001,   Expected reply was received
2019-03-11 21:59:52.877 Detail, Node001,   Message transaction complete
2019-03-11 21:59:52.877 Detail,
2019-03-11 21:59:52.877 Detail, contrlr, Removing current message
2019-03-11 21:59:52.877 Detail,
2019-03-11 21:59:52.877 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-03-11 21:59:52.879 Detail, contrlr,   Received: 0x01, 0x04, 0x01, 0x56, 0x00, 0xac
2019-03-11 21:59:52.879 Detail,
2019-03-11 21:59:52.879 Info, contrlr, Received reply to GET_SUC_NODE_ID.  Node ID = 0
2019-03-11 21:59:52.879 Info, Controller Does not Support SUC - Cannot Setup Controller as SUC Node
2019-03-11 21:59:52.879 Detail, Node172,   Expected reply was received
2019-03-11 21:59:52.879 Detail, Node172,   Message transaction complete
2019-03-11 21:59:52.879 Detail,
2019-03-11 21:59:52.879 Detail, contrlr, Removing current message
2019-03-11 21:59:52.879 Detail,
2019-03-11 21:59:52.879 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x1c) - FUNC_ID_ZW_GET_RANDOM: 0x01, 0x04, 0x00, 0x1c, 0x20, 0xc7
2019-03-11 21:59:53.434 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2019-03-11 21:59:53.434 Detail, contrlr,   Received: 0x01, 0x20, 0x5a, 0x95, 0x1b, 0xa5, 0xb8, 0x3a, 0x0f, 0xec, 0x8c, 0xac, 0x48, 0x4e, 0xa7, 0xc3, 0x4f, 0x83, 0x0b, 0x53, 0xe1, 0xa7, 0xd6, 0xc3, 0x28, 0x0b, 0xf5, 0x9d, 0x48, 0xb1, 0xbb, 0x4d, 0x19, 0xbd
2019-03-11 21:59:53.434 Warning, contrlr, WARNING: Checksum incorrect - sending NAK
2019-03-11 21:59:53.435 Detail, contrlr,   Received: 0x01, 0x01, 0x20
2019-03-11 21:59:53.435 Warning, contrlr, WARNING: Checksum incorrect - sending NAK
2019-03-11 21:59:53.435 Warning, WARNING: Out of frame flow! (0x1b).  Sending NAK.
2019-03-11 21:59:53.435 Warning, WARNING: Out of frame flow! (0x1b).  Sending NAK.
2019-03-11 21:59:53.435 Warning, WARNING: Out of frame flow! (0xb8).  Sending NAK.
2019-03-11 21:59:53.435 Warning, WARNING: Out of frame flow! (0x3a).  Sending NAK.
2019-03-11 21:59:53.435 Warning, WARNING: Out of frame flow! (0x3a).  Sending NAK.
2019-03-11 21:59:53.435 Warning, WARNING: Out of frame flow! (0xac).  Sending NAK.
2019-03-11 21:59:53.435 Warning, WARNING: Out of frame flow! (0x4e).  Sending NAK.
2019-03-11 21:59:53.435 Warning, WARNING: Out of frame flow! (0xa7).  Sending NAK.
2019-03-11 21:59:53.435 Warning, WARNING: Out of frame flow! (0x4f).  Sending NAK.
2019-03-11 21:59:53.436 Warning, WARNING: Out of frame flow! (0x0b).  Sending NAK.
2019-03-11 21:59:53.436 Warning, WARNING: Out of frame flow! (0x53).  Sending NAK.
2019-03-11 21:59:53.436 Warning, WARNING: Out of frame flow! (0xa7).  Sending NAK.
2019-03-11 21:59:53.436 Warning, WARNING: Out of frame flow! (0xc3).  Sending NAK.
2019-03-11 21:59:53.436 Warning, WARNING: Out of frame flow! (0x28).  Sending NAK.
2019-03-11 21:59:53.436 Warning, WARNING: Out of frame flow! (0x28).  Sending NAK.
2019-03-11 21:59:53.436 Warning, WARNING: Out of frame flow! (0xf5).  Sending NAK.
2019-03-11 21:59:53.436 Warning, WARNING: Out of frame flow! (0xf5).  Sending NAK.
2019-03-11 21:59:53.436 Warning, WARNING: Out of frame flow! (0xbb).  Sending NAK.
2019-03-11 21:59:53.436 Warning, WARNING: Out of frame flow! (0xbb).  Sending NAK.
2019-03-11 21:59:53.437 Warning, WARNING: Out of frame flow! (0x93).  Sending NAK.
2019-03-11 21:59:53.443 Detail, contrlr,   Received: 0x01, 0x25, 0x01, 0x1c, 0x01, 0x20, 0x5a, 0x95, 0x1b, 0xa5, 0xb8, 0x3a, 0x0f, 0xec, 0x8c, 0xac, 0x48, 0x4e, 0xa7, 0xc3, 0x4f, 0x83, 0x0b, 0x53, 0xe1, 0xa7, 0xd6, 0xc3, 0x28, 0x0b, 0xf5, 0x9d, 0x48, 0xb1, 0xbb, 0x4d, 0x19, 0xbd, 0x93
2019-03-11 21:59:53.443 Detail,
2019-03-11 21:59:53.443 Info, contrlr, Received reply to FUNC_ID_ZW_GET_RANDOM: true
2019-03-11 21:59:53.443 Detail, Node032,   Expected reply was received
2019-03-11 21:59:53.443 Detail, Node032,   Message transaction complete
2019-03-11 21:59:53.443 Detail,
2019-03-11 21:59:53.443 Detail, contrlr, Removing current message
2019-03-11 21:59:53.444 Detail,   Received: 0x01, 0x25, 0x01, 0x1c, 0x01, 0x20, 0x5a, 0x95, 0x1b, 0xa5, 0xb8, 0x3a, 0x0f, 0xec, 0x8c, 0xac, 0x48, 0x4e, 0xa7, 0xc3, 0x4f, 0x83, 0x0b, 0x53, 0xe1, 0xa7, 0xd6, 0xc3, 0x28, 0x0b, 0xf5, 0x9d, 0x48, 0xb1, 0xbb, 0x4d, 0x19, 0xbd, 0x93
2019-03-11 21:59:53.444 Detail,
2019-03-11 21:59:53.444 Info, Received reply to FUNC_ID_ZW_GET_RANDOM: true
2019-03-11 21:59:53.444 Detail,
2019-03-11 21:59:53.444 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x02) - FUNC_ID_SERIAL_API_GET_INIT_DATA: 0x01, 0x03, 0x00, 0x02, 0xfe
2019-03-11 21:59:54.043 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2019-03-11 21:59:54.043 Detail, contrlr,   Received: 0x01, 0x1d, 0xc9, 0xff, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2019-03-11 21:59:54.043 Warning, contrlr, WARNING: Checksum incorrect - sending NAK
2019-03-11 21:59:54.047 Detail, contrlr,   Received: 0x01, 0x02, 0x08, 0x00
2019-03-11 21:59:54.047 Warning, contrlr, WARNING: Checksum incorrect - sending NAK
2019-03-11 21:59:54.048 Detail, contrlr,   Received: 0x01, 0x01, 0x02
2019-03-11 21:59:54.048 Warning, contrlr, WARNING: Checksum incorrect - sending NAK
2019-03-11 21:59:54.053 Warning, WARNING: Out of frame flow! (0x08).  Sending NAK.
2019-03-11 22:00:03.443 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-03-11 22:00:03.443 Detail, contrlr, Removing current message
2019-03-11 22:00:03.444 Detail, contrlr, Notification: Notification - TimeOut
2019-03-11 22:00:03.445 Detail,
2019-03-11 22:00:03.445 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x06) - FUNC_ID_SERIAL_API_SET_TIMEOUTS: 0x01, 0x05, 0x00, 0x06, 0x64, 0x0f, 0x97
2019-03-11 22:00:03.446 Detail, contrlr,   Received: 0x01, 0x05, 0x01, 0x06, 0x64, 0x0f, 0x96
2019-03-11 22:00:03.446 Detail,
2019-03-11 22:00:03.446 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_SET_TIMEOUTS
2019-03-11 22:00:03.446 Detail, Node015,   Expected reply was received
2019-03-11 22:00:03.447 Detail, Node015,   Message transaction complete
2019-03-11 22:00:03.447 Detail,
2019-03-11 22:00:03.447 Detail, contrlr, Removing current message
2019-03-11 22:00:03.447 Detail,
2019-03-11 22:00:03.447 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x00) - FUNC_ID_SERIAL_API_APPL_NODE_INFORMATION: 0x01, 0x07, 0x00, 0x03, 0x01, 0x02, 0x01, 0x00, 0xf9
2019-03-11 22:00:03.448 Detail, contrlr, Removing current message
2019-03-11 22:01:07.064 Detail, Node009,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x09, 0x02, 0x84, 0x07, 0xc7, 0x00, 0xbe
2019-03-11 22:01:07.064 Detail,
2019-03-11 22:05:48.670 Detail, Node009,   Received: 0x01, 0x0e, 0x00, 0x04, 0x00, 0x09, 0x06, 0x31, 0x05, 0x01, 0x42, 0x09, 0x45, 0xc7, 0x00, 0x06
2019-03-11 22:05:48.670 Detail,
2019-03-11 22:05:48.688 Detail, Node009,   Received: 0x01, 0x0e, 0x00, 0x04, 0x00, 0x09, 0x06, 0x31, 0x05, 0x05, 0x42, 0x08, 0xb8, 0xc9, 0x00, 0xf0
2019-03-11 22:05:48.688 Detail,
2019-03-11 22:05:48.706 Detail, Node009,   Received: 0x01, 0x0e, 0x00, 0x04, 0x00, 0x09, 0x06, 0x31, 0x05, 0x03, 0x42, 0x00, 0x68, 0xc9, 0x00, 0x2e
2019-03-11 22:05:48.706 Detail,
2019-03-11 22:05:48.723 Detail, Node009,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x09, 0x03, 0x80, 0x03, 0xff, 0xc9, 0x00, 0x4f
2019-03-11 22:05:48.724 Detail,

My guess is that it is not related to 0.89.1. I would guess that you have hit the same issue I have seen randomly at restart of HA. Also once after an upgrade.
And twice the issue locked up in a state where I had to restore a snapshot config.
See #21165. If this is true then you should be able to upgrade again and have a chance that it works. And if it does please update bug 21165 because at the moment that bug report gets very little attention

I will try again this weekend. The wife doesn't like when things are not working with the HA setup. I saw you were on Ubuntu with a NUC. I have also verified that the USB is accessible over the TTY path. I am running my zwave stick on a Pi with USB over IP and it's been solid. I don't think its the stick as restoring a snapshot brings everything back up correctly.

I have issues related to this as well. Using Hassio on NUC:
After about half of the reboots, I loose all the zwave devices. Usually rebooting solves this.
When I check, as far as I remember most of the times the OZW_log shows a lot of messages and this looks running correctly (only time outs for the 1-2 nodes that are turned off)
2-3 times now, I had to restore a a previous backup to get Zwave back up.
Today again time to restore. The zwave worked for 2 days on 89.2 but after a reboot I lost all nodes.
Tried to get the Zwave back by rebooting several times. In the meantime saw also issue #19686 (relating to battery powered nodes).
For what I have checked:

The Aeotec ZW090 Z-stick Gen5 EU was always on the same /dev/ttyACM0
The OZW_log showed healthy activity

Will now revert to a backup. The home-assistant log is talking about value changes of unknown zwave nodes.
2019-03-18 21:54:48 WARNING (Dummy-4) [openzwave] Z-Wave Notification ValueChanged ({'homeId':<PHONE_NUMBER>, 'nodeId': 16, 'commandClass': 'COMMAND_CLASS_METER', 'instance': 1, 'index': 21, 'id':<PHONE_NUMBER>1377234, 'genre': 'User', 'type': 'Decimal', 'value': 0.4699999988079071, 'label': 'Previous Reading', 'units': 'A', 'readOnly': True}) for an unknown node 16

Going back to an old snapshot introduced another problem (recorder database not found) but all 10 times I rebooted the zwave devices came back. So my guess now is that it is related to some timing issue.

I use the venv and for me its completely all over the place - I currently only have a single zwave, entity in my entities list - however I got some sensor entities from others zwave. entities that are now absent reporting otherwise - no idea what happened or how to resolve this - may try downgrading fist ...

See https://github.com/home-assistant/home-assistant/issues/21165
It should be the same issue and there is a well working work around in the report comments