fix(hubspot): provide default lists of properties

Fixes #305
The error 414 URI too long happens, because we request the list of all the possible properties for an object here:
https://github.com/dlt-hub/verified-sources/blob/a1cf60a718389f63b1b73b3a6e1c92432ee7c269/sources/hubspot/helpers.py#L165-L184
In some cases, object has so many properties, that their list joined by , becomes longer than 8000 of symbols, which causes 414.
Proposed solution:
Instead of reading all the possible properties (most of which are very low-level and unlikely needed, like number of the broker, which processed the record), we create a default list of properties for every endpoint. The default lists are copied from the Hubspot search (see https://developers.hubspot.com/docs/api/crm/search#crm-objects), so for Hubspot users it should be an expected behavior.
However, if user wants, they can initiate a resource with their own list of properties to read, e.g.:
load_info = pipeline.run(
            contacts(api_key="fake_key", include_history=True, props=["prop1", "prop2"])
        )

In case the user still wants to try to read all the possible properties, they can send props=None - in this case, we'll work the old way. The length of the properties list depends on many factors, so it can still work fine in many cases.

@rudolfix, okay, I think I got it. Pushed the code.
There is one hubspot test failing - it's not related, I saw these failures before started the task. After I update the docs, I can take a look at it, if needed. It seems like a test data cleanup error, not functionality.

@rudolfix, there is no easy way in Hubspot to read only custom properties, as in new versions of the API they dropped most of the properties filtering functionality. However, in the newest version, all the Hubspot driven properties have prefix hs_ (while for custom properties this prefix is restricted), so we can read all the properties and filter them before sending a request.
Also, I added constants, because all this properties stuff becomes too complex.

And don't forget to update the documentation here: https://github.com/dlt-hub/dlt/pull/857

I think it's better to merge it already. It fixes an error - errors should not stay in code for long time, especially considering it's a widespread error and it can't be walked around.
Other changes can be done later.


Implement response parsing support

This PR adds the following:

Support for parsing the responses received during token refreshing
Support for decrypting payloads, as defined by the UID2 API spec: https://github.com/IABTechLab/uid2docs/blob/main/api/v2/ref-info/encryption-decryption.md

LGTM


Fix warnings in OpenAPI

Purpose

Fix warnings in OpenAPI

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Closing this in favour of #25770


Attestation config format

In #107 a multitude of X and X_blacklist fields are added and not all of these are consistent.
How about we have [deny] and [allow] sections instead?
E.g.:
[sgx.allow]
hash = "DEADBEEF"
signer = "BEEFDEAD"

[sgx.deny]
signer = "C0FFEE"

How would this look in code? Is this a simple Serde rename?
What about other items in SGX and SNP? Would it be like below, and is that too many [sections]?:

[sgx.allow]
hash = "DEADBEEF"
signer = "BEEFDEAD"

[sgx.deny]
signer = "C0FFEE"

[sgx]
features = ["Debug", "ProvisioningKey", "EInitKey", "KSS"]
enclave_security_version = 0
enclave_product_id = 0


Add VSCode Rust Analyzer Settings

Description
Fixes errors reported by rust analyzer due to differing target and a missing cargo feature.
I'm not sure if I'm the only one who ran into this or not, so feel free to close if this shouldn't be needed for some reason!
Pre-commit steps

[ ] Tested on QEMU and real HW Rasperry Pi.

Not needed if it is just a README change or similar.

[x] Ran ./contributor_setup.sh followed by ./devtool ready_for_publish

You'll need Ruby with Bundler and NPM installed locally.
If no Rust-related files were changed, ./devtool ready_for_publish_no_rust can be used instead (faster).
This step is optional, but much appreciated if done.

Note: I ran the second step above, and it generated a bunch of changes in the "diff to previous" sections, but the only change was to add a timestamp to all the diffs, which I'm assuming is just a different version of diff on my system, and is tangential to the change this PR makes, so I just didn't commit those files.

The individual tutorials have dedicated settings, e.g. https://github.com/rust-embedded/rust-raspberrypi-OS-tutorials/blob/master/17_kernel_symbols/.vscode/settings.json.
99% of the time, I am only opening a dedicated tutorial folder in VS Code, not the entire repo. But I guess it doesn't hurt to have this at the top level as well.
Could you extend your PR so that the added settings file is the same as the one from tutorial 17 linked above?

Ah, that makes sense, pushed an update.

Thanks!


[BUG] Docker Container ssx-server-dev crashes for any log in after the first.

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
I'm using the ssx-server-dev container described in the <repo>/docker-compose.yml to attempt to do local development. I've removed the front-end in order to use my own from the docker-compose.yml, so my file looks like:
services:
  ssx-server:
    container_name: ssx-server-dev
    image: spruce/ssx-server-dev
    env_file: .env
    build:
      context: .
      dockerfile: ssx-server.Dockerfile
    ports:
      - "8443:8443"

The container works for the first log in. The container outputs the following log:
ssx-server-dev  | {
ssx-server-dev  |   userId: 'did:pkh:eip155:1:0xdA3176d77c04632F2862B14E35bc6B4717FB5016',
ssx-server-dev  |   type: 'ssx-login',
ssx-server-dev  |   content: {
ssx-server-dev  |     signature: '0xf977aaedd14c0ee9121edce880fd58132cdf580a6eb1966623f3c2b8d66a77e423dec09db2b9b32149bd79e11a99eb8310f3a5db1d541c6b7bd74f1515c6332d1c',
ssx-server-dev  |     siwe: 'localhost wants you to sign in with your Ethereum account:\n' +
ssx-server-dev  |       '0xdA3176d77c04632F2862B14E35bc6B4717FB5016\n' +
ssx-server-dev  |       '\n' +
ssx-server-dev  |       '\n' +
ssx-server-dev  |       'URI: did:key:z6MkpjgcdvifNmcj5gCz39QSVegUM4mzKG8rMTox8vGnJDWY#z6MkpjgcdvifNmcj5gCz39QSVegUM4mzKG8rMTox8vGnJDWY\n' +
ssx-server-dev  |       'Version: 1\n' +
ssx-server-dev  |       'Chain ID: 1\n' +
ssx-server-dev  |       'Nonce: TtC8dYMIK8rzTT6tW\n' +
ssx-server-dev  |       'Issued At: 2023-01-05T20:53:18.905Z',
ssx-server-dev  |     isGnosis: false
ssx-server-dev  |   },
ssx-server-dev  |   timestamp: '2023-01-05T20:53:21.728Z'
ssx-server-dev  | }

If I refresh the client app, then log in again, it crashes with the message:
ssx-server-dev  | /root/ssx/packages/ssx-server/dist/middlewares/express/middleware.js:59
ssx-server-dev  |             const { success: verified, data } = siweMessageVerify;
ssx-server-dev  |                              ^
ssx-server-dev  |
ssx-server-dev  | TypeError: Cannot destructure property 'success' of 'siweMessageVerify' as it is undefined.
ssx-server-dev  |     at /root/ssx/packages/ssx-server/dist/middlewares/express/middleware.js:59:30
ssx-server-dev  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
ssx-server-dev  |
ssx-server-dev  | Node.js v18.12.1
ssx-server-dev exited with code 1

This is consistently reproducible.
Expected Behavior
The ssx-server-dev container can handle a second user logging in or a malformed message without crashing.
Steps To Reproduce

Clone the repo.
Run the docker container
Visit the app
Log in
Refresh the app
Log in again

Anything else?
One major issue is that de-structuring an undefined property in JavaScript causes an unrecoverable error and program wide crash. De-structuring without validation is always going to risk making a recoverable error into a fatal one.
I think we should strive to make them recoverable, in the sense that one malformed message from one user doesn't crash the whole system for other users. That way a useful error can be returned in the case of accidental malformed messages and the system is not vulnerable to one bad message being enough to launch a DoS attack.

This bug is related to ssx-server middleware

Good news, I'm no longer experiencing this issue after the latest changes. I'm going to close this issue.


[Enhancement]: Complete the Docker image of the Towhee project

Is there an existing issue for this?

[X] I have searched the existing issues

What would you like to be added?
Currently Towhee builds docker images and hardcodes software mirror in China, maybe we should switch this configuration to optional to better meet the needs of all users.
If this proposal is good, I will gradually submit the code to solve this problem:

[x] Allow users to selectively use MIRROR when building docker images #1737
[x] Let the package download source used by the language also follow the user configuration https://github.com/towhee-io/towhee/pull/1747

Why is this needed?
No response
Anything else?
No response

It looks like the problem has been solved and this issue can be closed. @reiase  🍻


Stop building our libraries separately

Currently, the build process is organized in a way that each sub-library (like //common/cpp) is built separately and then has its .lib+.h files installed into a common place (in the NaCl environment). The .lib files are then used when linking the resulting executable.
The original motivation behind this approach is pretty much described in issue #132; additionally, it allows to avoid recompiling a library multiple times for different executables and to test it without compiling the rest of the code. However, similar to that issue, the benefits of that approach don't outweigh the complexity and the fragility caused by it.
Therefore the suggestion is to get rid of that model and separate .lib files, and instead directly compile every library's source file as part of the resulting target.

hello

I'm not sure anymore it'd be a good idea. This would be non-conventional (given that the code is actually consisting of several self-contained blocks that come from different upstreams and are compiled with different flags). Implementation-wise it'd also be weird.


SynchronizingSubscriptionsFailedHandler fires endlessly

Hi!
Last week I upgraded MQTTnet from v2.8.5 to v3.0.4.
Running my first long-term test, after a few hours the system ran into something looking like an endless loop firing the SynchronizingSubscriptionsFailedHandler event over and over again.
I am using the ManagedMqttClient  and my test was running on linux on arm.
The log file looks as follows (I added some comments to let you know which message is printed in which handler):
...
[2019-06-28 06:28:59 INF Mqtt      ] DISCONNECTED from MQTT server: Received packet 'PubAck: [PacketIdentifier=19] [ReasonCode=]' at an unexpected time.
[2019-06-28 06:29:00 INF Mqtt      ] DISCONNECTED from MQTT server.
[2019-06-28 06:29:10 INF Mqtt      ] CONNECTING FAILED to MQTT server (timeout).
[2019-06-28 06:29:40 INF Mqtt      ] CONNECTED to MQTT server
[2019-06-28 06:47:39 INF Mqtt      ] DISCONNECTED from MQTT server: Received packet 'PubAck: [PacketIdentifier=20] [ReasonCode=]' at an unexpected time.
[2019-06-28 06:47:50 INF Mqtt      ] CONNECTING FAILED to MQTT server (timeout).
[2019-06-28 06:47:50 INF Mqtt      ] DISCONNECTED from MQTT server (timeout).
[2019-06-28 06:48:31 INF Mqtt      ] DISCONNECTED from MQTT server (timeout). // <- This is logged in the DisconnectedHandler (with exception type MqttCommunicationTimedOutException)
[2019-06-28 06:48:31 INF Mqtt      ] CONNECTING FAILED to MQTT server (timeout). // <- This is logged in the ConnectingFailedHandler (with exception type MqttCommunicationTimedOutException)
[2019-06-28 06:49:01 INF Mqtt      ] CONNECTED to MQTT server
[2019-06-28 07:04:01 INF Mqtt      ] DISCONNECTED from MQTT server: Received packet 'PubAck: [PacketIdentifier=21] [ReasonCode=]' at an unexpected time.
[2019-06-28 07:04:02 INF Mqtt      ] DISCONNECTED from MQTT server.
[2019-06-28 07:04:12 INF Mqtt      ] CONNECTING FAILED to MQTT server (timeout).
[2019-06-28 07:04:42 INF Mqtt      ] CONNECTED to MQTT server
[2019-06-28 07:08:28 INF Mqtt      ] DISCONNECTED from MQTT server: Received packet 'PubAck: [PacketIdentifier=22] [ReasonCode=]' at an unexpected time.
[2019-06-28 07:08:33 INF Mqtt      ] CONNECTED to MQTT server
[2019-06-28 07:08:35 INF Mqtt      ] DISCONNECTED from MQTT server: Received packet 'PubAck: [PacketIdentifier=24] [ReasonCode=]' at an unexpected time.
[2019-06-28 07:08:36 INF Mqtt      ] CONNECTED to MQTT server
[2019-06-28 07:08:37 INF Mqtt      ] DISCONNECTED from MQTT server: Received packet 'PubAck: [PacketIdentifier=25] [ReasonCode=]' at an unexpected time.
[2019-06-28 07:08:38 INF Mqtt      ] CONNECTED to MQTT server
[2019-06-28 07:08:39 INF Mqtt      ] DISCONNECTED from MQTT server: Received packet 'PubAck: [PacketIdentifier=26] [ReasonCode=]' at an unexpected time.
[2019-06-28 07:08:40 INF Mqtt      ] CONNECTED to MQTT server
[2019-06-28 07:08:41 INF Mqtt      ] DISCONNECTED from MQTT server: Received packet 'PubAck: [PacketIdentifier=27] [ReasonCode=]' at an unexpected time.
[2019-06-28 07:08:42 INF Mqtt      ] CONNECTED to MQTT server
[2019-06-28 07:08:43 INF Mqtt      ] DISCONNECTED from MQTT server: Received packet 'PubAck: [PacketIdentifier=28] [ReasonCode=]' at an unexpected time.
[2019-06-28 07:08:44 INF Mqtt      ] CONNECTED to MQTT server
[2019-06-28 07:08:46 INF Mqtt      ] DISCONNECTED from MQTT server: Received packet 'PubAck: [PacketIdentifier=30] [ReasonCode=]' at an unexpected time.
[2019-06-28 07:08:47 INF Mqtt      ] CONNECTED to MQTT server
[2019-06-28 07:08:48 INF Mqtt      ] DISCONNECTED from MQTT server: Received packet 'PubAck: [PacketIdentifier=31] [ReasonCode=]' at an unexpected time.
[2019-06-28 07:08:49 INF Mqtt      ] CONNECTED to MQTT server
[2019-06-28 07:08:50 INF Mqtt      ] DISCONNECTED from MQTT server: Received packet 'PubAck: [PacketIdentifier=32] [ReasonCode=]' at an unexpected time.
[2019-06-28 07:08:52 INF Mqtt      ] CONNECTED to MQTT server // <- This is logged in the ConnectedHandler
[2019-06-28 07:08:52 INF Mqtt      ] DISCONNECTED from MQTT server: Received packet 'PubAck: [PacketIdentifier=33] [ReasonCode=]' at an unexpected time. // <- This is logged in the DisconnectedHandler ("Received packet 'PubAck: [PacketIdentifier=33] [ReasonCode=]' at an unexpected time." is the exception message)
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.' // <- This is logged in the SynchronizingSubscriptionsFailedHandler ("The client is not connected." is the exception message)
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
[2019-06-28 07:08:52 WRN Mqtt      ] MQTT synchronizing subscriptions failed: The client is not connected.'
... (this is repeated many times per second for days)

Do you have any idea what is going wrong here? Did I something wrong when upgrading? The only things I changed were the event handlers and some namespaces.
Please let me know if you need some more information. Unfortunately I cannot reproduce the behavior at the moment. Before the upgrade it was running fine for month.

Hi,
sorry but I never saw this before. Which transport to you use? WebSockets? Even if the disconnect happens the following tries to subscribe are wrong.
Is it possible to share a small snipped? Then I can see how you setup everything.
Best regards
Christian

Hi Christan,
thank you for your reply! I am using TCP+TLS as transport layer.
Please find my setup code here:
ManagedMqttClientOptions options = new ManagedMqttClientOptionsBuilder()
    .WithAutoReconnectDelay(TimeSpan.FromSeconds(30))
    .WithClientOptions(new MqttClientOptionsBuilder()
        .WithClientId(...)
        .WithTcpServer(..., ...)
        .WithTls()
        .WithCredentials(..., ...)
        .WithCommunicationTimeout(TimeSpan.FromSeconds(10))
        .WithKeepAlivePeriod(TimeSpan.FromSeconds(15))
        .WithKeepAliveSendInterval(TimeSpan.FromSeconds(10))
        .Build())
    .Build();

mqttClient = new MqttFactory().CreateManagedMqttClient();

mqttClient.ApplicationMessageProcessedHandler = new ApplicationMessageProcessedHandlerDelegate((Action<ApplicationMessageProcessedEventArgs>)OnApplicationMessageProcessed);
mqttClient.ApplicationMessageSkippedHandler = new ApplicationMessageSkippedHandlerDelegate((Action<ApplicationMessageSkippedEventArgs>)OnApplicationMessageSkipped);
mqttClient.SynchronizingSubscriptionsFailedHandler = new SynchronizingSubscriptionsFailedHandlerDelegate((Action<ManagedProcessFailedEventArgs>)OnSynchronizingSubscriptionsFailed);
mqttClient.ApplicationMessageReceivedHandler = new MqttApplicationMessageReceivedHandlerDelegate((Action<MqttApplicationMessageReceivedEventArgs>)ReceivedMessageHandler);
mqttClient.ConnectedHandler = new MqttClientConnectedHandlerDelegate((Action<MqttClientConnectedEventArgs>)OnConnected);
mqttClient.DisconnectedHandler = new MqttClientDisconnectedHandlerDelegate((Action<MqttClientDisconnectedEventArgs>)OnDisconnected);
mqttClient.ConnectingFailedHandler = new ConnectingFailedHandlerDelegate((Action<ManagedProcessFailedEventArgs>)OnConnectingFailed);

await mqttClient.StartAsync(options).ConfigureAwait(false);

await mqttClient.SubscribeAsync("s/e").ConfigureAwait(false);
await mqttClient.SubscribeAsync("error").ConfigureAwait(false);

Thank you for your help!
Best regards
Stefan

First of all: Please do not mix async (Tasks) with Threads. So please change new Thread... to Task.Run using proper await statements.
What are you doing here is that you start a thread and that thread starts 2(!) tasks for the subscriptions. These tasks are not awaited. This means they run in parallel. So when the client is disconnected they are still running and throwing exceptions. And you are starting them on every connect. So every connect starts 2 tasks which are not awaited.

Hi Christan,
I agree with you that it is no good idea mixing aync  with threads. This is a remainder of the former v2 implementation and I will fix that. But apart from being bad style it should still work, shouldn't it? Or do I run into some synchronization problems inside your lib?
What I can't see is that I start the command registrations on every connect. This should be prevented due to the isConnectedFirst  flag. Therefore I don't think that the cause of my initial problem lays here.
Best regards
Stefan

I agree that this is probably not the root cause but wrong usage of async/await leads to lot of unexpected behavior. And you are the very first person with this problem. I also have Xamarin Apps etc. using this Lib and this is the first time I see this. So there is a big chance that this is the problem.
But I will also try to find a another reason...l

About five weeks ago I finally had the chance to test the changes I made (no longer mixing async with threads, updating to MQTTnet 3.0.5). I set up two long term tests, one on linux on arm and the other on windows ten, both communicating with the same mqtt server. For five weeks everything went fine, but on friday both of my test set-ups failed with the symptoms as described above.
Part of the first log file (linux on arm):
[2019-08-30 13:02:29 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:02:30 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=3] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:02:30 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Received packet 'PubAck: [PacketIdentifier=3] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:02:31 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:02:41 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 13:02:51 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 13:03:01 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 13:03:11 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 13:03:21 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 13:03:31 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 13:03:41 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 13:03:51 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 13:04:01 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 13:04:11 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 13:04:21 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 13:04:31 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 13:04:41 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 13:04:46 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=23] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:04:46 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Received packet 'PubAck: [PacketIdentifier=23] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:04:53 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:10:40 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=30] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:10:47 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:13:30 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=13] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:13:36 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:16:23 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=15] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:16:25 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:16:26 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=16] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:16:28 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:16:29 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:16:31 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:18:48 INF Mqtt      ] DISCONNECTED from MQTT server (timeout).
[2019-08-30 13:18:50 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:21:26 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=15] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:21:27 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:21:31 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=16] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:21:33 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:21:38 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:21:38 INF Mqtt      ] DISCONNECTED from MQTT server: 'Object reference not set to an instance of an object.'
[2019-08-30 13:21:38 ERR Mqtt      ] CONNECTING FAILED to MQTT server: 'Object reference not set to an instance of an object.'
[2019-08-30 13:22:12 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:23:55 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=15] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:24:05 INF Mqtt      ] DISCONNECTED from MQTT server (timeout).
[2019-08-30 13:24:05 INF Mqtt      ] CONNECTING FAILED to MQTT server (timeout).
[2019-08-30 13:24:37 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:29:26 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=28] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:29:31 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:29:35 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=29] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:29:41 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:55:41 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=98] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:55:45 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:55:59 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:56:01 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:56:02 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=3] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:56:03 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 13:56:05 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 13:56:05 INF Mqtt      ] DISCONNECTED from MQTT server: 'Object reference not set to an instance of an object.'
[2019-08-30 13:56:05 ERR Mqtt      ] CONNECTING FAILED to MQTT server: 'Object reference not set to an instance of an object.'
[2019-08-30 13:56:38 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:01:42 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=27] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:01:46 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:04:42 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=14] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:04:45 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:04:52 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=15] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:04:53 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:04:56 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:04:57 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:05:40 INF Mqtt      ] CONNECTING FAILED to MQTT server (timeout).
[2019-08-30 14:06:10 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:07:12 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=12] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:07:18 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:10:11 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=19] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:10:13 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:10:14 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=20] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:10:14 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Received packet 'PubAck: [PacketIdentifier=20] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:10:15 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:13:13 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=20] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:13:14 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:13:26 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=21] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:13:33 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:16:28 INF Mqtt      ] DISCONNECTED from MQTT server (timeout).
[2019-08-30 14:16:30 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:18:51 INF Mqtt      ] DISCONNECTED from MQTT server (timeout).
[2019-08-30 14:18:54 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:19:04 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=17] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:19:06 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:19:07 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:19:07 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:19:09 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:21:33 INF Mqtt      ] DISCONNECTED from MQTT server (timeout).
[2019-08-30 14:21:35 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:29:57 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=50] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:29:58 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:30:00 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=51] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:30:00 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Object reference not set to an instance of an object.'
[2019-08-30 14:30:02 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:35:42 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=37] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:35:50 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:36:22 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:36:26 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:36:27 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Received packet 'PubAck: [PacketIdentifier=4] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:36:27 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=4] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:36:27 INF Mqtt      ] DISCONNECTED from MQTT server: 'Object reference not set to an instance of an object.'
[2019-08-30 14:36:27 ERR Mqtt      ] CONNECTING FAILED to MQTT server: 'Object reference not set to an instance of an object.'
[2019-08-30 14:36:58 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:39:27 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=26] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:39:30 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=27] [ReasonCode=]' at an unexpected time.'
[2019-08-30 14:39:30 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 14:39:30 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 14:39:30 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 14:39:30 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 14:39:30 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 14:39:30 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 14:39:30 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 14:39:30 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 14:39:30 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 14:39:30 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'

Part of the second log file (windows 10):
[2019-08-30 06:14:15 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:14:16 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Received packet 'PubAck: [PacketIdentifier=3] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:14:16 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=3] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:14:17 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:14:27 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 06:14:37 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 06:14:47 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 06:14:57 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 06:15:07 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 06:15:17 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 06:15:27 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 06:15:37 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 06:15:47 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 06:15:57 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 06:16:07 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 06:16:17 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 06:16:27 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Exception of type 'MQTTnet.Exceptions.MqttCommunicationTimedOutException' was thrown.'
[2019-08-30 06:16:32 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Received packet 'PubAck: [PacketIdentifier=66] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:16:42 INF Mqtt      ] CONNECTING FAILED to MQTT server (timeout).
[2019-08-30 06:17:13 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:19:11 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=51] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:19:13 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:19:14 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=52] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:19:16 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:19:18 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:19:19 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:19:20 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=3] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:19:21 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:21:30 INF Mqtt      ] DISCONNECTED from MQTT server (timeout).
[2019-08-30 06:21:32 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:24:04 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=46] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:24:05 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:26:05 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=43] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:26:08 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:26:10 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=44] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:26:11 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:26:15 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:26:15 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:26:23 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:31:23 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=103] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:31:30 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:38:49 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=145] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:38:50 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:41:38 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=58] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:41:42 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:41:46 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=59] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:41:50 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:46:24 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=95] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:46:26 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:46:30 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=96] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:46:34 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:46:39 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:46:41 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:48:38 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=44] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:48:44 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:48:56 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:49:05 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:49:09 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=3] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:49:10 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:51:24 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=54] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:51:28 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:51:36 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=55] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:51:37 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:51:41 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:51:43 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:54:20 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=53] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:54:29 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:56:41 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=54] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:56:50 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:57:13 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:57:21 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:59:22 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=50] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:59:28 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 06:59:30 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=51] [ReasonCode=]' at an unexpected time.'
[2019-08-30 06:59:37 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 07:00:08 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 07:00:09 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 07:00:10 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=4] [ReasonCode=]' at an unexpected time.'
[2019-08-30 07:00:11 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 07:02:21 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=59] [ReasonCode=]' at an unexpected time.'
[2019-08-30 07:02:24 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 07:02:36 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=60] [ReasonCode=]' at an unexpected time.'
[2019-08-30 07:02:47 INF Mqtt      ] DISCONNECTED from MQTT server (timeout).
[2019-08-30 07:02:47 INF Mqtt      ] CONNECTING FAILED to MQTT server (timeout).
[2019-08-30 07:03:18 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 07:05:15 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=54] [ReasonCode=]' at an unexpected time.'
[2019-08-30 07:05:18 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 07:05:39 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 07:05:46 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 07:05:47 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=3] [ReasonCode=]' at an unexpected time.'
[2019-08-30 07:05:48 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 07:05:49 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 07:05:51 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 07:05:52 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=2] [ReasonCode=]' at an unexpected time.'
[2019-08-30 07:05:57 INF Mqtt      ] CONNECTED to MQTT server
[2019-08-30 07:05:57 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 07:05:57 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 07:05:57 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 07:05:57 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 07:05:57 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 07:05:57 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 07:05:57 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 07:05:57 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-08-30 07:05:57 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'

Please note, that both failures occur at the same date, but not the same time.
This is my current initialization and subscription code:
       ManagedMqttClientOptions options = new ManagedMqttClientOptionsBuilder()
           .WithAutoReconnectDelay(TimeSpan.FromSeconds(30))
           .WithClientOptions(new MqttClientOptionsBuilder()
               .WithClientId(cfg.ClientId)
               .WithTcpServer(cfg.BrokerAddress, (int)cfg.BrokerPort)
               .WithTls()
               .WithCredentials(cfg.Credentials.User, cfg.Credentials.Password)
               .WithCommunicationTimeout(TimeSpan.FromSeconds(10))
               .WithKeepAlivePeriod(TimeSpan.FromSeconds(15))
               .WithKeepAliveSendInterval(TimeSpan.FromSeconds(10))
               .Build())
           .Build();

       mqttClient = new MqttFactory().CreateManagedMqttClient();

       mqttClient.ApplicationMessageSkippedHandler = new ApplicationMessageSkippedHandlerDelegate((Action<ApplicationMessageSkippedEventArgs>)OnApplicationMessageSkipped);
       mqttClient.SynchronizingSubscriptionsFailedHandler = new SynchronizingSubscriptionsFailedHandlerDelegate((Action<ManagedProcessFailedEventArgs>)OnSynchronizingSubscriptionsFailed);
       mqttClient.ApplicationMessageReceivedHandler = new MqttApplicationMessageReceivedHandlerDelegate((Action<MqttApplicationMessageReceivedEventArgs>)ReceivedMessageHandlerAsync);
       mqttClient.ConnectedHandler = new MqttClientConnectedHandlerDelegate((Action<MqttClientConnectedEventArgs>)OnConnectedAsync);
       mqttClient.DisconnectedHandler = new MqttClientDisconnectedHandlerDelegate((Action<MqttClientDisconnectedEventArgs>)OnDisconnected);
      mqttClient.ConnectingFailedHandler = new ConnectingFailedHandlerDelegate((Action<ManagedProcessFailedEventArgs>)OnConnectingFailed);

       logger.LogDebug("Trying to connect to MQTT server");
       await mqttClient.StartAsync(options).ConfigureAwait(false);

       await mqttClient.SubscribeAsync("topic").ConfigureAwait(false);

        private async void OnConnectedAsync(MqttClientConnectedEventArgs e)
        {
            logger.LogInformation("CONNECTED to MQTT server");
            if (isConnectedFirst)
            {
                isConnectedFirst = false;
                await RegisterCommandSubscriptionsAsync().ConfigureAwait(false);
            }
        }

        public async Task RegisterCommandSubscriptionsAsync()
        {
            logger.LogDebug("RegisterCommandSubscriptions called");
            await Task.Delay(10000).ConfigureAwait(false);

            logger.LogDebug("Registering subscriptions for receiving commands");
            if (CallbackCommandReceived != null || CallbackLogfileRequestReceived != null || CallbackSendValuesRequestReceived != null || CallbackConfigurationRequestReceived != null)
            {
                await mqttClient.SubscribeAsync("s/ds").ConfigureAwait(false);
            }
            if (CallbackNewValueReceived != null)
            {
                await mqttClient.SubscribeAsync("topic2").ConfigureAwait(false);
            }
        }

I noticed that in the meantime you released two other versions of your lib. Do you see a chance that the issue is fixed there and should I give them a try?
Best regards
Stefan

I just noticed the problem again, but this time on my development machine (win10), so I had the possibility to dig into it a bit further.
The log output looks as follows:
[2019-10-24 16:41:53 VRB Mqtt      ] MQTT message processed: <topic> | Payload: '<message 1>' // -> In ApplicationMessageProcessedHandler
[2019-10-24 16:42:13 INF Mqtt      ] DISCONNECTED from MQTT server (timeout). // -> In DisconnectedHandler  (with MqttCommunicationTimedOutException)
[2019-10-24 16:42:13 VRB Mqtt      ] MQTT message processed: <topic> | Payload: '<message 2>' // -> In ApplicationMessageProcessedHandler
[2019-10-24 16:42:17 INF Mqtt      ] CONNECTED to MQTT server, subscribing to topics... // -> In ConnectedHandler
[2019-10-24 16:42:17 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=35] [ReasonCode=]' at an unexpected time.' // -> In DisconnectedHandler (with other exception)
[2019-10-24 16:42:17 DBG Mqtt      ] Registering subscriptions for receiving commands // -> In ConnectedHandler
[2019-10-24 16:42:17 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.' // -> SynchronizingSubscriptionsFailedHandler
[2019-10-24 16:42:17 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-10-24 16:42:17 VRB Mqtt      ] MQTT message processed: <topic> | Payload: '<message 2>'
[2019-10-24 16:42:17 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-10-24 16:42:17 VRB Mqtt      ] MQTT message processed: <topic> | Payload: '<message 2>'
[2019-10-24 16:42:17 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-10-24 16:42:17 VRB Mqtt      ] MQTT message processed: <topic> | Payload: '<message 2>'
[2019-10-24 16:42:17 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-10-24 16:42:17 VRB Mqtt      ] MQTT message processed: <topic> | Payload: '<message 2>'
[2019-10-24 16:42:17 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-10-24 16:42:17 VRB Mqtt      ] MQTT message processed: <topic> | Payload: '<message 2>'
[2019-10-24 16:42:17 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-10-24 16:42:17 VRB Mqtt      ] MQTT message processed: <topic> | Payload: '<message 2>'
[2019-10-24 16:42:17 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'

I added comments where the output happens, please refer to my code above.
Due to more debug output, you can see that there are alternating messages from the SynchronizingSubscriptionsFailedHandler and the ApplicationMessageProcessedHandler. It is the same message which is reported as processed over and over again.
Some additional information for the case it helps:

The MqttClient's IsConnected property states true all the time, but no connection is established and the message queue constantly grows.
The ApplicationMessageProcessedEventArgs in the ApplicationMessageProcessedHandler has the exception property set with an exception of the type MqttCommunictaionException ("The client is not connected."). It's stack trace is

   at MQTTnet.Client.MqttClient.ThrowIfNotConnected()
   at MQTTnet.Client.MqttClient.PublishAsync(MqttApplicationMessage applicationMessage, CancellationToken cancellationToken)
   at MQTTnet.Client.MqttClientExtensions.PublishAsync(IMqttClient client, MqttApplicationMessage applicationMessage)
   at MQTTnet.Extensions.ManagedClient.ManagedMqttClient.<TryPublishQueuedMessageAsync>d__59.MoveNext()

The ManagedProcessFailedEventArgs in the SynchronizingSubscriptionsFailedHandler has the exception property set with an exception of the type MqttCommunictaionException ("The client is not connected."). It's stack trace is

   at MQTTnet.Client.MqttClient.ThrowIfNotConnected()
   at MQTTnet.Client.MqttClient.<SubscribeAsync>d__36.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MQTTnet.Extensions.ManagedClient.ManagedMqttClient.<SynchronizeSubscriptionsAsync>d__60.MoveNext()

Screenshot of the internal state of the mqttClient:

This weekend, I had the issue on another testing system (.net core 2, win 10):
// Everything works fine until here
[2019-10-26 05:40:04 INF Mqtt      ] DISCONNECTED from MQTT server: 'Received packet 'PubAck: [PacketIdentifier=1487] [ReasonCode=]' at an unexpected time.'
[2019-10-26 05:40:08 INF Mqtt      ] CONNECTED to MQTT server
[2019-10-26 05:40:08 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-10-26 05:40:08 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-10-26 05:40:08 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-10-26 05:40:08 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-10-26 05:40:08 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-10-26 05:40:08 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-10-26 05:40:08 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
[2019-10-26 05:40:08 WRN Mqtt      ] MQTT synchronizing subscriptions failed: 'The client is not connected.'
...

It's the same behavior - a disconnection due to an unexpected packet followed be a reportedly successful re-connection which brings the lib into an inconsistent state.

@chkr1011 and @SeppPenner , may I ask you if I can provide anything helping you to investigate this issue?
As our MQTT broker seems to send these unexpected packets from time to time (which is out of our scope) this issue occurs frequently and is quite annoying as you can image. I have workarounded it with a watchdog inspecting the packet queue and resetting the service when a specific number of unsent packets is reached, but this is obviously not a good solution.
A comparative test with the former main version of your library (2.8.x) connected to the same MQTT broker runs without interruptions for month.
Please let me know if I can help you in any ways, for example by beta-testing a fix or by providing more information.
Best regards
Stefan

Please test again with the latest version of the library and reopen this ticket if the issue persists.


Integrate beaver in a simple CLI yields error

Here's the mix.exs:
defmodule Boltex.MixProject do
  use Mix.Project

  def project do
    [
      app: :boltex,
      version: "0.1.0",
      elixir: "~> 1.14",
      start_permanent: Mix.env() == :prod,
      deps: deps(),
      escript: [main_module: Boltex.CLI],
    ]
  end

  # Run "mix help compile.app" to learn about applications.
  def application do
    [
      extra_applications: [:logger],
    ]
  end

  # Run "mix help deps" to learn about dependencies.
  defp deps do
    [
      {:beaver, "~> 0.2"},
    ]
  end
end

And here is the main module I added:
defmodule Boltex.CLI do
  def main(args) do
    IO.puts "Hello"
  end
end

The program will succeed in creation if I run mixescript.build, but when I run the app I get a bunch of errors:

19:58:03.877 [notice] Application beaver exited: bad return value: {{Beaver.Application, :start_phase, [:mlir_register_all_passes, :normal, []]}, {:EXIT, {:undef, [{Beaver.MLIR.CAPI, :mlirRegisterAllPasses, [], []}, {Beaver.Application, :start_phase, 3, [file: 'lib/beaver/application.ex', line: 13]}, {:application_starter, :run_the_phase, 4, [file: 'application_starter.erl', line: 99]}, {:application_starter, :start_apps, 3, [file: 'application_starter.erl', line: 59]}, {:application_starter, :start, 3, [file: 'application_starter.erl', line: 45]}, {:application_master, :start_the_app, 5, [file: 'application_master.erl', line: 332]}, {:application_master, :start_it_new, 7, [file: 'application_master.erl', line: 315]}]}}}

19:58:03.877 [warning] The on_load function for module Elixir.Beaver.MLIR.CAPI returned:
{%ArgumentError{message: "unknown application: :beaver"},
 [
   {Application, :app_dir, 1, [file: 'lib/application.ex', line: 954]},
   {Application, :app_dir, 2, [file: 'lib/application.ex', line: 981]},
   {Beaver.MLIR.CAPI, :load_rustler_precompiled, 0,
    [file: 'lib/beaver/mlir/capi.ex', ...]},
   {:code_server, :"-handle_on_load/5-fun-0-", 1, [...]}
 ]}

19:58:03.875 [error] Process #PID<0.140.0> raised an exception
** (ArgumentError) unknown application: :beaver
    (elixir 1.14.0) lib/application.ex:954: Application.app_dir/1
    (elixir 1.14.0) lib/application.ex:981: Application.app_dir/2
    (beaver 0.2.19) lib/beaver/mlir/capi.ex:21: Beaver.MLIR.CAPI.load_rustler_precompiled/0
    (kernel 8.5.4) code_server.erl:1317: anonymous fn/1 in :code_server.handle_on_load/5

19:58:03.924 [notice] Application kinda exited: :stopped

19:58:03.924 [notice] Application zig_parser exited: :stopped

19:58:03.925 [notice] Application rustler_precompiled exited: :stopped

19:58:03.925 [notice] Application castore exited: :stopped

19:58:03.927 [notice] Application ssl exited: :stopped

19:58:03.927 [notice] Application public_key exited: :stopped

19:58:03.927 [notice] Application asn1 exited: :stopped

19:58:03.928 [notice] Application inets exited: :stopped

19:58:03.928 [notice] Application crypto exited: :stopped

19:58:03.928 [notice] Application llvm_config exited: :stopped
ERROR! Could not start application beaver: bad return value: {{Beaver.Application, :start_phase, [:mlir_register_all_passes, :normal, []]}, {:EXIT, {:undef, [{Beaver.MLIR.CAPI, :mlirRegisterAllPasses, [], []}, {Beaver.Application, :start_phase, 3, [file: 'lib/beaver/application.ex', line: 13]}, {:application_starter, :run_the_phase, 4, [file: 'application_starter.erl', line: 99]}, {:application_starter, :start_apps, 3, [file: 'application_starter.erl', line: 59]}, {:application_starter, :start, 3, [file: 'application_starter.erl', line: 45]}, {:application_master, :start_the_app, 5, [file: 'application_master.erl', line: 332]}, {:application_master, :start_it_new, 7, [file: 'application_master.erl', line: 315]}]}}}

ive never used escript before. Are there requirements on how apps should be started under escript？

I'm new to Elixir so sorry I don't know about that...

later i will run it with escript to see what is happening

BYW, it is not recommended to use escript for CLI in most of cases

For running live systems, consider using mix run or building releases. See the Application module for more information on systems life-cycles.

resolved by running with an system env, ERL_LIBS=_build/dev/lib [your Escript executable]
Check out the "The ability to use external modules" section of this blog
http://davekuhlman.org/elixir-escript-mix.html#toc-entry-4

Again it is not recommended to use escript because it is not a "real" executable like what C++/Rust produced.

Thank you.


No yellow blocks?

When I have nothing but yellow minecraft dye and cobble in my inventory, I'm not getting anything showing up in the block maker? It seems to work fine with most other dyes (I haven't tried them all) but for some reason having ONLY yellow leaves me with no blocks available. Is this normal? Am I missing something? I thought maybe it was because yellow is a primary color, but blue and red both work as expected.

Are you using the default configuration?

Is what I'm seeing.

Yes as far as I know. :/ It so weird that it seems to be only yellow that's doing this. It's probably some random mod conflict.

OK so I went and looked at my config file, and yes I did change it. I changed the following lines so we would use less IDs from the default of 32:
I:HUE_SHADES=16
I:HUE_SHADES_GLOWING=16
I:HUE_SHADES_TRANSPARENT=16

But I didn't touch anything else. I tested it with the default config and it works as expected, but changing only these lines makes it so that no yellow blocks exist. This seems (to me) to be an error/issue, since like I was saying, it doesn't seem to happen with any of the other dyes.

Yellow itself is a pretty slim window on the color wheel, orange is basically right on top of it too, which means that this adjustment that changes it from 10 degrees to 20 degrees per hue more or less removes pure yellows from the blocks.
With those configs the most yellow blocks are really more of a "gold" and thus are tied to orange dyes instead of yellow.


[10.x] Introduce new Arr::limit() helper

I reached for this today and could have sworn that it existed, but turns out that it's only a Collection method. I think it makes sense as an Arr helper too, since it reads a lot nicer than the underlying array_slice() syntax.

Ah, yeah not limit(), take() is the correct method name.

Yeah I think that would be good.

@taylorotwell All done :^)

Thanks!

Note: this doesn't preserve array keys while Collection::take does


update dependencies

Current dependencies on/for this PR:

main

PR #210   👈

This stack of pull requests is managed by Graphite.

Merge activity

Feb 14, 1:57 AM EST: @ToastedDev merged this pull request with Graphite.


Add support for paginate_array

The PR exposes the native Kaminari paginate_array as Grape helper. Will you consider this approach for being merged in master?
....
paginate_array(my_array, total_count)
....

This is useful to keep the header response consistent also when you are dealing with simple array of data.

Isn't that the same as writing
paginate Kaminari.paginate_array(some_array)

?
Anyway, I think we could merge that if there was no duplication of header settings in the code (most probable extracting all these lines into separate method)


Add verification for redirect

In http module there are details about status, but I am not see whether there is a way of checking if redirection is valid.
For example
http:
  http://some.domain.here:
    status: 301
    no-follow-redirects: true

Expected to setup something like that (for example):
http:
  http://some.domain.here:
    status: 301
    no-follow-redirects: true
    headers:
      - 'Location https://some.another.domain.here'

This will allow faster and quicker check if redirects are valid.

I think #296 would resolve this when it's merged in, correct?

This has been merged/released.


Zapier

@zakwilson would you mind bundle install, committing the Gemfile.lock, and pushing to your branch? That should let CI pass. Same for the other branch.
I've got the config screens ready for this, so it'll probably be live later this week or next week.

@zakwilson one more tweak. The Pushover service class and Gemfile change is also in the Zapier branch. Would you mind removing those so it's just got the Zapier class and its test class?

zapier_url is now just url


XeTwitterLink is absent

Similar to other "social" Xe*Link classes we should have XeTwitterLink, but it's absent at the moment. Let's create one.

@yegor256 tagged this issue with "bug"

@yegor256 attached this issue to milestone "1.0" (let me know if this is wrong)

@yamstranger it's yours,please go ahead

@yegor256 thanks for the report, I topped your acc for 15 mins, payment ID 000-70cbb012

@davvd , @yegor256. As wrote @alice, I am not with your team any more. So please assign ticket to someone else. Thanks

@davvd , @yegor256. As wrote @alice, I am not with your team any more. So please assign ticket to someone else. Thanks

@yamstranger right, I will find someone else, no problem

@davvd , @yegor256. As wrote @alice, I am not with your team any more. So please assign ticket to someone else. Thanks

@yamstranger deducted 30 from your rating :(

@ikhvostenkov please proceed, it's yours

@ikhvostenkov this task is in your hands for 15 days already; -30 added to your rating, at the moment it is: +85

@ikhvostenkov this task is not yours any more (took too long), please stop. I'll give you something else
-60 added to your rating, current score is: +25

@ekondrashev the task is yours, please go ahead

@davvd I understand you policy, but there is a PR #305 available pending @yegor256 comments.
@ikhvostenkov did provide an implementation for that defect, but the review took more time then expected, so I believe he missed a chance to ask for more time on this.
So, @davvd can you perhaps give @ikhvostenkov another chance to complete this considering all said?
If I take this task, I'll be still pending @yegor256 comments for #305.

@davvd please assign @ikhvostenkov back to this task

@davvd please assign @ikhvostenkov back to this task

@yegor256 done! @ikhvostenkov the task is yours, please proceed

@yegor256 I've closed PR for this ticket due to current Twitter OAuth mechanism should be redone. If you do not have any comments here, could you please close this then.

@ikhvostenkov indeed, this is closed, thanks for the attempt

@elenavolokhova please, let us know what do you think about this ticket, according to our QA rules

@ikhvostenkov
According to our quality rules:

The ticket is closed only when the reported problem is solved.

This ticket was closed with no final solution provided.
@yegor256 Could you please help here? Should it be paid?

@elenavolokhova This ticket was closed due to this ticket not actual any more because of some problem on the upper level. So not actual ticket - no solution.

@ikhvostenkov Thank you for clarification!

@davvd Quality is bad here.

@davvd Quality is bad here.

@elenavolokhova thank you very much

@ikhvostenkov I added 10 mins to @elenavolokhova (for QA review) in transaction 59102833


Exam/all endpoint

Contains an exam/all endpoint that retrieves all courses from the database.

In the future you'll want to reference the issue you are addressing in your PR. i.e. This is for #110.


execSync -> execFileSync for RescriptEditorSupport binary invocation

Part of #81

@cristianoc this works, but then it looks like the hover's path isn't correctly relativized anymore:

I guess the binary doesn't relativize correctly when there's some quoting

The argument should not be quoted anymore now that an array of arguments is passed.

Thanks for the review.


Scroll bar update

https://www.figma.com/file/BNxiYPgG7l5ZxO7JXYGdJ0/Print-Design-System?node-id=0%3A1&t=z63QBWAGHxs3UVMY-0
I would like to keep this pattern up across the UI: If it's clickable, it is golden. If it isn't clickable then it is not golden.

The scrollbars are clickable and should therefore be be golden. They should also be given some margin with the container that they scroll. I'd like to add arrow buttons on either side.

The SVGs for the arrow buttons are here:
https://drive.google.com/drive/folders/1isKmsAtsD6NOga1SOtrIXnInIWVcCQ19

Did a quick search for the solution. It seems that the standard scrollbar styling methods are very limited, as well as there may be problems with adding arrows (it is in the documentation, but in fact the browsers have display problems (at least on macOS)). Need to learn more about ways how this can be done.

there is this - https://www.thisdot.co/blog/creating-custom-scrollbars-with-react
But it's pretty custom and I have a feeling will be a nightmare to maintain across multiple browser types

If the arrows are a pain, forget about them. Just make the bar golden and give it a few pixels margin to the edge of the container, voila.


Remove track1 cognitive packages

Packages impacted by this PR
@azure/cognitiveservices-face
@azure/cognitiveservices-computervision
@azure/cognitiveservices-contentmoderator
@azure/cognitiveservices-customvision-prediction
@azure/cognitiveservices-customvision-training
@azure/cognitiveservices-personalizer
@azure/cognitiveservices-translatortext
Describe the problem that is addressed by this PR
These are old track1 packages that haven't been built or maintained in years. They're not managed by Rush, nor do they use the common core.

/check-enforcer override


Support for EXPO SDK 51 or a walkaround to use the package?

I'm am unable to install this package on expo SDK 51
I'd like Support for Expo SDK 51

I intend to support the package on v51.
Looking to the next week to release it.

In the meantime if you are facing any issues, please share them here. Might help speed up the development.

Cool , Thanks!

The package has been updated to support v48, and v49 is being worked upon. We should be able to reach v51 soon.

That's great, Thanks for the effort!

That's great, Thanks for the effort!

In the meantime, do help me by sharing any feedback on documentation, or any features you think should be available

The documentation is perfect!, Cool package man!

Closing this as the version has been released.


[Bug] monaco.KeyMod.WinCtrl does not work on Windows

Reproducible in vscode.dev or in VS Code Desktop?

[X] Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

[ ] Not reproducible in the monaco editor playground

Monaco Editor Playground Link
https://microsoft.github.io/monaco-editor/playground.html?source=v0.40.0#XQAAAALGAgAAAAAAAABBqQkHQ5NjdMjwa-jY7SIQ9S7DNlzs5W-mwj0fe1ZCDRFc9ws9XQE0SJE1jc2VKxhaLFIw9vEWSxW3yscw2WmWcffboL-OnIHuReyD-esaziiuEaSCBDe-Pnvrl1XDhkRhVU0WTIiZgeB83lmTE6VkYYnWje_Pvjor1u7IiPqx1EvIvROC-vvhr7MS2qOjqcBgN9wYGEvjfLJ0tNT56JB6RPq-TC6COOdqmI1BdSWz1Mcj03RZnn36AdjV5JqrM_MJz_B02t2ARHSGEk1W2Sv8qsS71pQL2n_kbCqEk6tPsz3XHD5O-_-tIbh0JNhv9Cwo3ZCrdkRMpPV7dDMs1By_anaUvnhrxY_T9FH_jVeiGbCBjVbRmNYoTqic4xgXX3glvtnZCS5tcal66cCXIUk0oxHoErEpl2QDwZwoOFFDX8b0NyH7bSx9lQelq5M4Nsty-f4rxx6nQYXp_4miz6r7-9cLsGAZQHlU3PmrPepskA5dBd7ZJ2DC5eLOXbPZro0V5LqFZmr6IrkhaETT9A625IrJNoA4ohsf0Poa65eqJrR-7YClMyHoipraJ_9Ktjmb4kF3_WWTgQ
Monaco Editor Playground Code
monaco.editor.create(document.getElementById('container'), {
  value: "function hello() {\n\talert('Hello world!');\n}",
  language: 'javascript',
  inlineSuggest: {
      enabled: true,
  }
});

class InlineCompleter {
provideInlineCompletions() {
      console.log(arguments);
      return {items: [{insertText: '11111'}, {insertText: '22222'}]};
  }
  freeInlineCompletions() {}
}
monaco.languages.registerInlineCompletionsProvider('javascript', new InlineCompleter());

monaco.editor.addKeybindingRule({
  keybinding: monaco.KeyMod.WinCtrl | monaco.KeyMod.Shift | monaco.KeyCode.Space,
  command: 'editor.action.inlineSuggest.trigger',
})

Reproduction Steps

Open the playground link above on a Windows computer.
Open dev console to watch for output from the inline completions provider
Push Ctrl + Shift + Space and notice nothing happens (it should show a completion request with an explicit trigger)

Do the same thing on a Mac or Linux computer and notice that the above does work.
Actual (Problematic) Behavior
Adding a keybinding rule with monaco.KeyMod.WinCtrl does not seem to work on a Windows computer.
Expected Behavior
monaco.KeyMod.WinCtrl should work on Windows, Mac, and Linux.
Additional Context
No response

Sorry, I think this just might be my misunderstanding of this KeyMod enums and not a bug (using KeyMod.CtrlCmd does work on Windows). Let me close this.


Pipeline getting failed with the Github API secondary rate limit

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
I have added the Github private repo, with one repo the pipeline fails with the following error.

What do you expect to happen
the pipeline should complete successfully be completed
How to reproduce
This error occurs every time the pipeline runs.
Anything else
When this issue occurred last time, I enabled the Graphql APIs, and then the issue was resolved. this time even after enabling Graphql and setting the custom Rate limit also facing the issue.
I tried with another token as well
The private repo has a size of around 1.5 GB
FYI. We are on the GitHub enterprise subscription.
Version
v0.20.0-beta4
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

@pramodh-b https://github.com/apache/incubator-devlake/issues/5864 This problem should have been solved long ago. And regardless of whether graphql is enabled or not, this task is actually executed using non-graphql. You may need to wait for a while before running again.

@pramodh-b #5864 This problem should have been solved long ago. And regardless of whether graphql is enabled or not, this task is actually executed using non-graphql. You may need to wait for a while before running again.

Hi @abeizn FYI I'm running this pipeline weekly once. still same error.

@pramodh-b
I don't mean the frequency of running once a week, I mean that before executing the collectApiPrReviewComments task, a lot of other data such as issues, pull_requests, cicd, etc. are collected. You need to run it again after a while after failure.
And you can reduce the rate limit value to solve this problem：


Failed to get watcher

We are using ES6 in our environment and we would like to use Sentinl as our alarming component.
But I'm having issues at creating new alarm at Sentinl. I've tried to follow http://sentinl.readthedocs.io/en/latest/Tutorial/ but had some problems. After some discussion at here https://github.com/sirensolutions/sentinl/issues/334 I've figured out my input was incorrect so I've fixed it. But still the tacher has problems. Every ti,e I'm trying to execute the watcher I'm getting the message "Watchers: fail to get watcher" and the next output:
Error: fail to get watcher <watcher_id>     at Watcher.<anonymous> (http://localhost:5601/bundles/sentinl.bundle.js?v=16588:1:268707)     at tryCatch (http://localhost:5601/bundles/vendors.bundle.js?v=16588:63:99706)     at Generator._invoke (http://localhost:5601/bundles/vendors.bundle.js?v=16588:63:101781)     at Generator.prototype.(anonymous function) [as throw] (http://localhost:5601/bundles/vendors.bundle.js?v=16588:63:99990)     at step (http://localhost:5601/bundles/sentinl.bundle.js?v=16588:1:264876)     at http://localhost:5601/bundles/sentinl.bundle.js?v=16588:1:265037
Adding watcher configuration:
{   "actions": {     "Testing": {       "throttle_period": "0h0m1s",       "webhook": {         "method": "POST",         "host": "",         "port": 9200,         "proxy": false,         "path": "",         "body": "Found {{payload.hits.total}} Events"       }     }   },   "input": {     "search": {       "request": {         "indices": [           "<mos-{now/d}>",           "<mos-{now/d-1d}>"         ],         "body": {           "query": {             "bool": {               "must": [                 {                   "query_string": {                     "query": "mos:*",                     "analyze_wildcard": true                   }                 }               ],               "filter": {                 "range": {                   "@timestamp": {                     "gte": "now-5m",                     "lte": "now"                   }                 }               }             }           },           "aggs": {             "avg_mos": {               "avg": {                 "field": "mos"               }             }           }         }       }     }   },   "condition": {     "script": "aggregations.avg_mos.value < 3"   },   "transform": {},   "trigger": {     "schedule": {       "later": "every 1 minute"     }   },   "disable": false,   "report": false,   "title": "watcher_title" }

Hi @masterofcloud1 thanks for trying out SENTINL on 6.x - this release is still experimental so there are quirks - we've removed the old tutorial as it was confusing most users due to the discontinued format it used.
I suggest to get rid of that - just create a "default" watcher using the wizard instead with the default query and set the condition to be > 1 then save - basically a watcher counting documents in the cluster and growing each time a watcher result is saved. This should produce a workable watcher you can start with.
I hope this helps, feel free to comment if you need further support here.


Setting up project file structure

I have just setup the project file structure. I will be using ml_collections to do the config management.
@gustheman @sayakpaul

Incorporated the changes.


how to get prefix by ip?

Hello
You recently removed the prefix return value from the lookup function.
How can I now get the prefix from the IP?
old:
Lookup(ip netip.Addr) (lpm netip.Prefix, val V, ok bool)

new:
Lookup(ip netip.Addr) (val V, ok bool)

I see only this option
bart.Table[netip.Prefix]

I woul imagine
(lpm, val, ok) := t.LookupPrefixLPM(ip.Prefix(ip.BitLen()))

should do the trick, no?

use LookupPrefixLPM and read the docstring

If LookupPrefixLPM is to be used for IP addresses, they must be converted to /32 or /128 prefixes.

what is your use case? The fastest method is to add the prefix to the payload and unwrap it from the returned value.

no feedback, closing the issue


No Parameters in validation callback when using yarn workspaces

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Currently moving a project from npm to yarn, because I want to use yarn workspaces. After finishing the whole workspace setup, I realized the validation callback in PassportStrategy(OIDCStrategy) is called without parameters (sub, profile, accessToken, refreshToken, params) after successfully proceeded Azure AD authentication.
Insolating the appropriate workspace in an different location on my workstation and switching back to npm (deleting node_modules and yarn.lock) results in everything working great again.
Interesting is that switching the isolated workspace back to yarn works when using these steps:
rm -rf node_modules yarn.lock
npm install
yarn import
yarn install --check-files

Is it possible that passport-azure-ad does not support yarn workspaces?
Please mention your node.js, yarn and operating system version.
passport-azure-ad 4.3.0
nestjs 7.5.1
node v12.18.4
yarn 1.22.4
npm 6.14.6
os Windows 10

Since the current version is in maintenance and only security fixes are being actively pushed, we want to handle this in the new version of the library. Marking this as an enhancement to track (yarn support)
We are currently in the design phase of a new version of this library, which can be tracked here. The timeline for the new library will be uploaded to our msal js repo.

Thank you for clarification, will keep an eye on the new version of the library.
After various tests, I narrowed the problem down to the nestjs passport library (@nestjs/passport). Somehow I accidently switched from version 7.1.3 to 7.1.5 and things stopped working. Reverting to version 7.1.3 fixed the problem.

@jaunusa Thank you for the update.


Datepicker UTC Timezone issue

Bug description:
I am using the datepicker to handle dates all in the UTC timezone.  I am using the .config to set the ng-model-options to be UTC for all datepickers.  However I noticed that when my timezone is minus UTC timezone the date that shows on the input is actually the day before.  The date is correct on the actual datepicker though.  However if I explicitly put the ng-model-options on the input the date show up correct.  Is this the expected behavior?
http://plnkr.co/edit/YVPT6sNxx92Y1oSFgWqo?p=preview
Version of Angular, UIBS, and Bootstrap
Angular: 1.5.3
UIBS: 1.3.1
Bootstrap: 3.3.6

@RobJacobs I think this is exactly what we were talking about just earlier - we'll likely have this addressed by the next release @msosa.

great thank you! If it helps this was working in 1.2.5

This is turning into a tricky issue.  You will notice in the plunk, it's the date displayed in the input element that is off, the datepicker popup has the correct date displayed.  The datepicker directive tries to handle the timezone correction and does so correctly for the activeDate property.  When I try and move the timezone correction to the datepickerPopup directive, both directives apply the timezone offset resulting in a double timezone shift for the ngModel value.  I'm still trying to figure out what the model-options attribute is doing differently than the config object modelOptions property.

i feel like the problem is here:
https://github.com/angular-ui/bootstrap/blob/master/src/datepickerPopup/popup.js#L36
if you look at datepicker it uses the config:
https://github.com/angular-ui/bootstrap/blob/master/src/datepicker/datepicker.js#L159
the popup doesn't seem to. If i manually set the timezone in the popup.js to UTC everything seems to work.

This is probably right, and I sort of suspect it's a one line change necessary - let me see about opening a PR.

The fix is more complex than that. My initial change was to modify the line mentioned above to be like the datepicker, but that causes the time zone offset to be added twice.

I realized that after heh. This requires some more investigation.

Hmm doesn't that mean if we set the ng model options on the input that this will also cause the zone offset to be added twice?

No, see my comment above, using the model-options works correctly.

I'm not sure if this is any help or not but I put a comment on  #5752 about the fact that correcting this issue using ng-model-options timezone seems to be a bit of a hack over the underlying issue. I don't know what conversations you've had internally but judging by this thread I think you're trying to fix the underlying issue with datepickers selecting the wrong date due to timezone issues.

So I have an updated plunk that formats the dates to include the full time as well as timezone, and it still seems that even using ng-model-options on the input we are not getting the dates we want. I would expect the timezone to be 0 when using a UTC date with a UTC filter just the way the angular filter does so(2016-04-01T00:00:00+0000). But it seems like it still has the timezone in it(2016-04-01T00:00:00-0400). Maybe this is by design but here is the plunk
http://plnkr.co/edit/BZP5ZGjAlwMWgg4Jyenm?p=preview

Going to close this in favor of #5825 - going to schedule for 2.0.0, as it requires a significant breaking change to correctly fix.


AutoRun

Mod name
AutoRun
Curseforge link
https://www.curseforge.com/minecraft/mc-mods/autorun-fabric
Other links
https://modrinth.com/mod/autorun
What it does
Enables auto walking in Minecraft with a keybind, which can also be turned into sprinting by hitting the sprint key.
Why should it be in the modpack
Makes it much less tedious on fingers to go long distances as you don't have to hold down on one key the whole time.
Why shouldn't it be in the modpack
Adds one keybind, which contributes to a bigger list of keybinds in controls that people may find irritating. Also, people accidentally hitting the keybind without knowing what it is could potentially be confused by it.
Categories
New feature
Additional details
No response

Adds a new feature that solves a specific issue for some specific people, so those people should install it manually.
Any new mod I add should be useful for at least 70% of people while keeping the "vanilla experience".


E0001 no attribute 'logging' error validating SAM template

Version
❯❯❯ cfn-lint --version
cfn-lint 0.15.0

Modules
❯❯❯ pip freeze
aws-sam-translator==1.10.0
boto3==1.9.112
botocore==1.12.112
certifi==2019.3.9
cfn-lint==0.15.0
chardet==3.0.4
docutils==0.14
idna==2.8
jmespath==0.9.4
jsonpatch==1.23
jsonpointer==2.0
jsonschema==2.6.0
python-dateutil==2.8.0
PyYAML==3.13
requests==2.21.0
s3transfer==0.2.0
six==1.12.0
urllib3==1.24.1

Description of issue.
Running cnf-lint on serverless template gives E0001 error..
❯❯❯ cfn-lint ./lambdas/**/*.yaml
E0001 Error transforming template: module 'samtranslator.parser.parser' has no attribute 'logging'
./lambdas/rotate-credentials/template.yaml:1:1

The template is here: https://github.com/Sage-Bionetworks/aws-infra/blob/master/lambdas/rotate-credentials/template.yaml
This seems like a regression.  It only happen when aws-sam-translator==1.10.0 is installed.  It does not happen when I replace 1.10.0 with aws-sam-translator==1.9.1.

Hi!
This is introduced by SAM 1.10 and has already been fixed (https://github.com/aws-cloudformation/cfn-python-lint/pull/702). A new release with this fix will be coming today or tomorrow

Release v0.16.0 was just cut.  This fix is included and will be released shortly.


Feature/drive update

Updates callback URL in Readme of Google Drive.

@kushG Can you please resend this from a new branch without all the merge commits?

Also, when you send the new PR, add [skip ci] to your commit message, as this doesn't need a Travis build.

Ok sure !


Do we need a more maintainable and aesthetically pleasing website theme?

Kmesh website now has better flexibility with the theme, but it requires a certain amount of understanding to implement it.
This makes it difficult for developers unfamiliar with the front-end to make the desired adjustments to the website.
So do we need to replace the website theme？
Replace it with, for example Docsy or hugo docs.

This need is not an urgent one, but I think it's one that needs to be done


[BUG]: Blob column doesn't work with turso

What version of drizzle-orm are you using?
0.29.1
What version of drizzle-kit are you using?
No response
Describe the Bug
sqliteTable('table', { 	id: integer('id', { mode: 'number' }).primaryKey({ autoIncrement: true }), 	binary: blob('binary').notNull().type<ArrayBuffer>(), });
When i query the binary column, the typeof binary is a string which is the UTF8 encoded version of initial ArrayBuffer.
Using turso driver with libsql dev environment
Expected behavior
No response
Environment & setup
No response

This problem come from the environment where drizzle is running, in my case cloudflare workers which does not support Buffer.
Just tried in a classic node environment and it works ok.
Maybe we should implement a workaround to use ArrayBuffer in environnement that does not support Buffer ?

Closing it as it is working when using a polyfill to globalThis.Buffer

@theodem I'd reopen the issue because it should be working without polyfill.


Notifications Panel

PR for issue #1807

A test harness is included to show the process of patching a VM / adding test notifications.
When @jjgriff93 has the dynamic form ready it will hook in here via opsContext.addOperation() to hand over the operation to be tracked.

@jjgriff93 - the page refresh / loading all notifications is a future task, as thinking about it there's more to it - since we'd need to get all running operations that the user has access to, under each API endpoint. we'd probably want a new api endpoint to do the heavy lifting here - but it's definitely something we should have on the plan.


Add documentation for the bank_adr1 field on the CvrSoCd database model.

Add documentation for the bank_adr1 field on the CvrSoCd database model.
Step 1: Claim this ticket by leaving a comment below. Tell everyone you're ON IT!
Step 2: Open up the file that contains this model. It should be in
calaccess_raw.models.campaign.py.
Step 3: Hit the little pencil button in the upper-right corner of the code box to
begin editing the file.
Step 4: Find this model and field in the file. We expect it to lack the help_text
field typically used in Django to explain what a field contains.
effect_dt = fields.DateField(
    null=True,
    db_column="EFFECT_DT"
)

Step 5: In a separate tab, open up the official state documentation
and find the page that defines all the fields in this model.
Step 6: Find the row in that table's definition table that spells out what
this field contains. It it lacks documentation. Note that in the ticket and close it now.
Step 7: Return to the GitHub tab.
Step 8: Add the state's label explaining what's in the field,
to our field definition by inserting it a help_text argument. That should
look something like this:
effect_dt = fields.DateField(
    null=True,
    db_column="EFFECT_DT",
    # Add a help_text argument like the one here, but put your string in instead.
    help_text="The other values in record were effective as of this date"
)

Step 9: Scroll down below the code box and describe the change you've made in
the committe message. Press the button below.
Step 10:  Review your changes and create a pull request submitting them to
the core team for inclusion.

Test.


Stackoverflow exception 4.0.3

Hey,
Thanks for this project, we are looking for more performant IOC than autofac for our REST API and dryioc seems to be promising! I have converted most of autofac code to dryioc and it seems to work nice. However one of our REST API controller is throwing stackoverflow exception when calling it.
We are using DryIoc + WebAPI + Owin setup Compiled from sources due to issue in 4.0.3 platform targets.
System.StackOverflowException: 'Exception of type 'System.StackOverflowException' was thrown.'

 Thanks!

The exception seems to occur when parallel requests are done to same controller. Usually 1-2 first requests get resolved correctly and remaining fail.

This error seems to occur with more than one route, when many parallel requests are done.

Thanks for letting me know, will check.

Another q, do you have open-generic services or do you use decorators?

@dadhi Yes. We have many decorators and some open generic too.

Huh, then it may be related to #116. Which is fixed in the master and I planning the release soon.

@Havunen Version 4.0.4 is published


Preparing vCPU for numa and pinning support for vcenter

Description
Preparing for future numa and pinning support for vcenter, it is necessary to change the vCPU attribute assignment, which currently corresponds to the number of sockets in the VM, to number of cores, like KVM does.
Use case
Change required to maintain consistency between KVM and vcenter hosts
Interface Changes
There is no interface changes, only the assignment value into the rbvmomi API for vcenter.

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

[ONE]

https://github.com/OpenNebula/one/pull/4614

@tinova PR to be approved:

One: https://github.com/OpenNebula/one/pull/4658
Docs:  https://github.com/OpenNebula/docs/pull/1098


Deleting an instance in "provisioning" state might not free actual resources

If instance on OpenStack is in spawning/booting state delete might not actually terminate the instance. From PB's point of view there are no instance to be released at that time.

After the requests to worker were changed to arrive in order for a given instance with #320, this no longer is a problem


Refactor default bot config from json to ts

Original comment
There is the default bot config.
We want to able to add comments to the default bot config. We can't transform the config from json to yml or jsonc because it requires using fs.readFile() which causes issues on production netlify build.
What should be done:

refactor the default bot config from json to a plain ts file

If we transform it to ts then how will we read it in pay.ubf.fi?

If we transform it to ts then how will we read it in pay.ubf.fi?

We could add https://github.com/ubiquity/ubiquibot as an npm package to pay.ubf.fi
Perhaps there are better ways

/start

We can add comment as key value pair in json, if it's so necessary, otherwise on using ts instead of json, tool named jq that works with workflow and repo data will fail. Such as https://github.com/ubiquity/ubiquibot/blob/3eaedcc59d2813aaabb63533ae55477fbfc63ff0/.github/workflows/update-config.yml#L72
There is just 3 such cases. Provided any suggestion you have.

@rndquu for example
{
_comment1: "This will be the comment"
}
"Update config" refactoring will be included in this issue or there will be seperate issue for that?
Thank you

Why incentives for commenters and reviewers don't work? @0xcodercrane  Isn't it deployed to production?

I think yeah. need to get it to prod.

Why incentives for commenters and reviewers don't work? @0xcodercrane  Isn't it deployed to production yet?

Commenters seems unreliable and inconsistent, and for reviewers: I think only is now merged in.


SerializerPojo throws NotSerializableException for Class field

I was trying to integrate MapDB in one old project to improve performance and found problem with fields serialization of type java.lang.Class if this class is not serializable.
This is a test case https://github.com/bouchov/mapdb/blob/master/java/org/mapdb/SerializerPojoTest2.java  - test_Pojo fails.
I've also made a workaround https://github.com/bouchov/mapdb/blob/master/SerializerPojo.patch

Fixed in both branches


References and Mapping behave different in geth and testrpc.

http://vessenes.com/solidity-frustrations-references-and-mapping/
This is my test:
https://github.com/u2/ether-router/blob/master/contracts/mocks/List.sol
https://github.com/u2/ether-router/blob/master/test/list.js
References and Mapping behave different in geth and testrpc.
In geth
> List.getAll.call(0)
[]

> List.setList.sendTransaction(0,[1,2,3],{from: web3.eth.accounts[0]})
I0824 10:56:29.761988 eth/api.go:1193] Tx(0x0ada2217b60f6ee69a0de3f1ea0d8c6d0858c228c9a543efe3e0a5bc3597171f) to: 0xd4f3bd8466d1b8e326db1fbf13505b3869e1083d
"0x0ada2217b60f6ee69a0de3f1ea0d8c6d0858c228c9a543efe3e0a5bc3597171f"

> web3.eth.getTransaction('0x0ada2217b60f6ee69a0de3f1ea0d8c6d0858c228c9a543efe3e0a5bc3597171f')
{
  blockHash: "0x16969fec496c7507c788d799c70227a622b5ec0ab30ff7d55acd1c590a45cbb5",
  blockNumber: 429,
  from: "0x7d1ca639d49cf648a97ebb630564abb5c9bd75ec",
  gas: 90000,
  gasPrice:<PHONE_NUMBER>0,
  hash: "0x0ada2217b60f6ee69a0de3f1ea0d8c6d0858c228c9a543efe3e0a5bc3597171f",
  input: "0xb8c58128000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000003",
  nonce: 36,
  to: "0xd4f3bd8466d1b8e326db1fbf13505b3869e1083d",
  transactionIndex: 0,
  value: 0
}

> List.getAll.call(0)
[]

Hi there. Can you please share the List contract code your test refers to?
I won't be able to help otherwise.
On Tue, Aug 23, 2016 at 8:08 PM, YaNing Zhang<EMAIL_ADDRESS>wrote:

http://vessenes.com/solidity-frustrations-references-and-mapping/
This is my test:
https://github.com/u2/ether-router/blob/master/test/list.js
References and Mapping behave different in geth and testrpc.
In geth

List.getAll.call(0)
[]

List.setList.sendTransaction(0,[1,2,3],{from: web3.eth.accounts[0]})
I0824 10:56:29.761988 eth/api.go:1193] Tx(0x0ada2217b60f6ee69a0de3f1ea0d8c6d0858c228c9a543efe3e0a5bc3597171f) to: 0xd4f3bd8466d1b8e326db1fbf13505b3869e1083d
"0x0ada2217b60f6ee69a0de3f1ea0d8c6d0858c228c9a543efe3e0a5bc3597171f"

web3.eth.getTransaction('0x0ada2217b60f6ee69a0de3f1ea0d8c6d0858c228c9a543efe3e0a5bc3597171f')
{
blockHash: "0x16969fec496c7507c788d799c70227a622b5ec0ab30ff7d55acd1c590a45cbb5",
blockNumber: 429,
from: "0x7d1ca639d49cf648a97ebb630564abb5c9bd75ec",
gas: 90000,
gasPrice:<PHONE_NUMBER>0,
hash: "0x0ada2217b60f6ee69a0de3f1ea0d8c6d0858c228c9a543efe3e0a5bc3597171f",
input: "0xb8c58128000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000003",
nonce: 36,
to: "0xd4f3bd8466d1b8e326db1fbf13505b3869e1083d",
transactionIndex: 0,
value: 0
}

List.getAll.call(0)
[]

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ethereumjs/testrpc/issues/144, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFp1eLcZ7hnhNrXeaEz_unzU-gvG8RIks5qi7WTgaJpZM4Jrl9u
.

The contract is here:
https://github.com/u2/ether-router/blob/master/contracts/mocks/List.sol
The test in testrpc:
https://github.com/u2/ether-router/blob/master/test/list.js

@u2 do you still feel this is an issue? if so we'll look into it.

Sorry, I have forgotten this issue already.I think we can close it.Thank you any way.


Refactor code structure

Coverage remained the same at 91.911% when pulling 7631b1d2b5175bf730bb9818073658268527db7d on refactor-code-structure into ce9f9bd62a79f05d94c938fef4ef72cb875c0aa1 on mobile-staging.


Upgrade to idea-ext 0.7

The new version doesn't use some of the deprecated APIs. I tried it out and it seems to work apart from creating the Regenerate Int Test Image task. Though I think we should remove that gradle runner anyway and run the correct task in the subprojects. WDYT?

I'm trying this branch out on my computer. What do you mean "run intTestImage in subprojects" ?
Besides, why comment out the code instead of remove them?

I mean that you can run the corresponding task via the Gradle run action in idea:


README.md - coalesce should say concatentation

Describe the bug
README.md
Schema tests -> unique_combination_of_columns()
"passing the unique test a coalesce of the columns"
should say
"passing the unique test a concatenation of the columns"
Steps to reproduce
n/a
Expected results
"passing the unique test a concatenation of the columns"
Actual results
"passing the unique test a coalesce of the columns"
Screenshots and log output
n/a
Are you interested in contributing the fix?
Yes

@stannnman always happy to see PRs related to documentation! Feel free to rework it 🙏

This has been fixed!