View similar projects

We need to know what we should do about "View similar project"!
showing inside the page or on another page?
I agree with @MoeNick to show it inside the single project page, at the bottom, but load them after loading all of the single project page content to prevent slowing the page load, and we can show a show more button to get the user to the new page and list all similar projects.

This link should open new page in the same tab with list of similar projects.


Node/V8 currently disagrees with 6 Date.parse tests.

Just a heads up that builtin Date.parse of Node 20/22 fails 6 unit tests in Date.parse. I'm not sure if it's a bug on them or the shim. Just raising awareness of the differences.

Maybe related to the needsConstructor check V8 will fail one check for allowing invalid dates: Date.parse('2012-11-31T23:59:59.000Z')
Maybe related to the polyfill/shim juggle

Related to the needsConstructor check V8 will fail one check for allowing invalid dates: Date.parse('2012-11-31T23:59:59.000Z')

I see only 2 failures in latest node:
not ok 1 2012-11-31T23:59:59.000Z is an invalid date
  ---
    operator: equal
    expected: NaN
    actual:<PHONE_NUMBER>000
    at: <anonymous> ($PWD/test/Date.parse/tests.js:24:7)
    stack: |-
      Error: 2012-11-31T23:59:59.000Z is an invalid date
          at Test.assert [as _assert] ($PWD/node_modules/tape/lib/test.js:492:48)
          at Test.strictEqual ($PWD/node_modules/tape/lib/test.js:670:7)
          at $PWD/test/Date.parse/tests.js:24:7
          at forEachArray ($PWD/node_modules/for-each/index.js:12:17)
          at forEach ($PWD/node_modules/for-each/index.js:54:9)
          at Test.<anonymous> ($PWD/test/Date.parse/tests.js:23:3)
          at Test.run ($PWD/node_modules/tape/lib/test.js:126:28)
          at Test._end ($PWD/node_modules/tape/lib/test.js:398:5)
          at Test.end ($PWD/node_modules/tape/lib/test.js:211:7)
          at Test.<anonymous> ($PWD/test/Date.parse/builtin.js:10:4)
  ...

not ok 13 2011-02-29T12:00:00.000Z is an invalid date
  ---
    operator: equal
    expected: NaN
    actual:<PHONE_NUMBER>000
    at: <anonymous> ($PWD/test/Date.parse/tests.js:24:7)
    stack: |-
      Error: 2011-02-29T12:00:00.000Z is an invalid date
          at Test.assert [as _assert] ($PWD/node_modules/tape/lib/test.js:492:48)
          at Test.strictEqual ($PWD/node_modules/tape/lib/test.js:670:7)
          at $PWD/test/Date.parse/tests.js:24:7
          at forEachArray ($PWD/node_modules/for-each/index.js:12:17)
          at forEach ($PWD/node_modules/for-each/index.js:54:9)
          at Test.<anonymous> ($PWD/test/Date.parse/tests.js:23:3)
          at Test.run ($PWD/node_modules/tape/lib/test.js:126:28)
          at Test._end ($PWD/node_modules/tape/lib/test.js:398:5)
          at Test.end ($PWD/node_modules/tape/lib/test.js:211:7)
          at Test.<anonymous> ($PWD/test/Date.parse/builtin.js:10:4)
  ...

with builtin.js:
'use strict';

var test = require('tape');

var runTests = require('./tests');

test('builtin', function (t) {
    runTests(Date.parse, t);

    t.end();
});

(notably, these two dates do fail in Safari, but pass in Firefox)

Thanks for digging in and showing the example builtin.js test.


fix(replica): make preload operations of secondary replicas lockless

This PR addresses the issue of preload taking time for secondary replicas causing write ios from controller to timeout. This issue was initially tried to solve by increasing the write timeout from 15 to 30s which is not scalable.
This PR solves the same issue as follows:
Preload will be done only once.
- In case of 1st replica, preload is done when the replica gets a start signal from controller.
- In case of remaining replicas, preload is done after completing the sync operation.
Signed-off-by: Payes<EMAIL_ADDRESS>

@payes we have set timeout to 0 in Open call from controller as well, we need to fix it by other ways like retrying by increasing timeout in other iterations instead of erroring out in first go. This is safe and best that we can do IMO.

@vishnuitta These have been disabled in NewReplica() func in rebuilding state.


Fix command service infinite replay

Signed-off-by: Igor Egorov<EMAIL_ADDRESS>Description of the Change
Persistent cache for some reason was not integrated into command service.
That was resulting in infinite resending of a replayed transaction between Iroha components.
The fix makes CommandServiceImpl aware of persistent cache and the infinite loop is broken now.
Caches lookup strategy during batch processing in command service (even single incoming transaction will be represented as a batch internally):

check command service tx status cache
check persistent storage cache for replays

Benefits
Potentially improved CPU and memory consumption.
Reduced network load.
An infinite resending of a replayed transaction between Iroha components is avoided.
Possible Drawbacks
The test for replay has to be written.
Usage Examples or Tests
command_service_replay_test

compile and run irohad
Check that there is no infinite resending
run repro script https://gist.github.com/igor-egorov/ff56db9ca1de50215d6830f5980155d6
Iroha output should not contain inifinitely repeated message about duplicated transaction from OnDemandOrderingServiceImpl like "Duplicate transaction: ..."
Check that correct statuses are delivered in tx status stream
repro script https://gist.github.com/igor-egorov/152b821faa335193569dec2246e578fb
You have to compile two versions of irohad: one from develop branch, another - from that pr.
Run the script with both irohad's and capture the output to files.
The statuses (their order) should not differ.

Please review the two last commits.


Peripheral scan returns no peripherals

This is bizarre. I've set up a test project which pretty much duplicates your example project. But peripheral scan never finds a peripheral.
I can't see I'm doing anything at all different to you... And your example project works just fine.
Hopspots_Comms_LGBT.zip
Any idea what's up here?

So a little more testing seems to show that the first call always returns nothing, while subsequent calls find the peripherals that are present. Not in your example project though... that works.

Right... so this is an initialisation thing it seems. Some time needs to pass between the first call of sharedInstance and the first write.

yes.you have to access other methods after centralManagerDidUpdateState called.

This is a known issue with Core Bluetooth. The first call is basically useless.


S3storage

@Speedy1991
Adds functionality mentioned in #8 .
Let me test this out during this week and will ping you.

hm, there are many code duplications compared to the normal Storage. Maybe a abstract Storage would be better. I'll think about it.

What do you think about something like this?

This looks good. I can update to your new specification.

#10 done


Use js native String.repeat()

Replacing the _makeIndent() function as talked in #286 😃

<3

Perfect, thanks so much!


Add link to docs in README

Link to client credential docs.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Show parameter names when entering a function in javascript

I just signed up for GitHub only to fill this request, it's very important to me:
Description
When autocompleting a function in Brackets, the parameters of the function are shown, but they hide after I start typing the arguments. I'd really love being able to see what parameters this function requires in the right order (like the autocomplete at http://ternjs.net/doc/demo/. In the demo, even the current argument you are typing is highlighted bold, but I'd be fine if the list of arguments would be visible at all when entering arguments.
Steps to Reproduce

Define a function:
function myFunction(one, two) {  return one + two; }

Start typing:
var sum = my

Autocomplete (press enter):
var sum = myFunction
Note that when autocompleting functions the brackets "()" could be inserted automatically

Press "(":
var sum = myFunction()
The parameters are shown, the first parameter is highlighted

Enter any letter / number:
var sum = myFunction(1)
The tooltip is gone, autocomplete for the number is shown

Finish the first argument by entering a comma:
var sum = myFunction(1,)
The tooltip is still gone

Expected behavior:

When autocompleting a javascript function it usually makes sense to add the parentheses automatically (when not using functions as callbacks)

The tooltip should stay despite the autocomplete popup showing

The tooltip should stay and highlight the next argument

Versions
MacOS 10.12
Brackets Release 1.8 Build 1.8.0-17108

Here is a screenshot of the Tern demo:

The argument names are displayed properly and the current argument is being highlighted.

This is a bug caused by token caching in TokenUtils.js, so it keeps returning ) as the current token and thinks you're outside of the function call. Probably need to disable token caching for parameter hints but not sure about the performance impact. 😐
For now you can probably get by with using Ctrl+Shift+Space to bring the parameter hints back up again, or you can open the function call with a single bracket e.g. function( and close it after you type all the parameters.


docs: Update "Pass a falsy query key" section in README.md

The docs have been updated to remove the deprecated option to supply falsey items in the key, but this section in the README.md was not updated. This PR make the update!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


handle error when failing to load config

I'm guessing this is ignored because if this fails, the node will just use the default config but perhaps you want to distinguish between the config not existing and it existing but failing to decode

Codecov Report

Merging #1919 (ae39b5a) into main (596c16b) will decrease coverage by 0.13%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main    #1919      +/-   ##
==========================================
- Coverage   57.81%   57.69%   -0.13%
==========================================
  Files         245      245
  Lines       16156    16190      +34
==========================================
  Hits         9341     9341
- Misses       5869     5897      +28
- Partials      946      952       +6

Impacted Files
Coverage Δ

cmd/flags_node.go
48.33% <50.00%> (+2.71%)
:arrow_up:

... and 38 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Closing after sync discussion w @cmwaters


Silence pandas groupby() warning when running Augur predict

When running Augur predict, I stumbled upon this warning:

This should silence the warning.

Thanks!


How can i download this package from yarn add command?

When i try to download it, yarn brings me another package with the same name. But it seems that that package is dead

No, It isnt published to npm. This repo isn't supported and wasnt ready for production. So the only option to create your own fork and finish this implementation.


Update BoringSSL to 7c522995d1ea5386b3223a19b0f62e73c1f76b17

Also remove a temporary BoringSSL patch and deal with no C files being
in fiat/

@swift-nio-bot test this please

@swift-nio-bot test this please


Update queries to support multiple servers

I changed around the queries in the MySQL statements to not check for server = 1. This should allow the queries to iterate over X number of servers if the community has more than one.

I will implement another better way to let the owner of the bot make the choice which servers the bot should check for stats 👍
Thanks for your contribution in advance!


streamslice() and streamparticles() not working correctly

When using streamslice() to draw well-spaced streamlines (with direction arrows), lines and arrows are being plotted as a 3-D scatter chart.
load wind
streamslice(x,y,z,u,v,w,[],[],5)

fig2plotly(gcf, 'offline', false);

Expected and generated (https://chart-studio.plotly.com/~xarico10/1005/#/) plots:

Examples on using streamslice() can be found on:
https://www.mathworks.com/help/matlab/ref/streamslice.html

PR #330 fix this issue


Caught  by controller[37]:     at StateRedisClient.setState  (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)

host.raspberrypi-iobroker
2023-05-05 08:28:45.136
error
Caught by controller[37]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.136
error
Caught by controller[37]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)

host.raspberrypi-iobroker
2023-05-05 08:28:45.136
error
Caught by controller[37]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.136
error
Caught  by controller[36]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.136
error
Caught by controller[35]:     at processImmediate (node:internal/timers:437:9)

host.raspberrypi-iobroker
2023-05-05 08:28:45.136
error
Caught by controller[35]:     at runNextTicks (node:internal/process/task_queues:61:5)

host.raspberrypi-iobroker
2023-05-05 08:28:45.136
error
Caught  by controller[35]:     at Roborock.setState  (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6492:35)

host.raspberrypi-iobroker
2023-05-05 08:28:45.135
error
Caught  by controller[35]:     at StateRedisClient.setState  (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)

host.raspberrypi-iobroker
2023-05-05 08:28:45.135
error
Caught by controller[35]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.135
error
Caught by controller[35]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)

host.raspberrypi-iobroker
2023-05-05 08:28:45.135
error
Caught by controller[35]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.135
error
Caught  by controller[34]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.135
error
Caught by controller[33]:     at processImmediate (node:internal/timers:437:9)

host.raspberrypi-iobroker
2023-05-05 08:28:45.135
error
Caught by controller[33]:     at runNextTicks (node:internal/process/task_queues:61:5)

host.raspberrypi-iobroker
2023-05-05 08:28:45.134
error
Caught  by controller[33]:     at Roborock.setState  (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6492:35)

host.raspberrypi-iobroker
2023-05-05 08:28:45.134
error
Caught  by controller[33]:     at StateRedisClient.setState  (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)

host.raspberrypi-iobroker
2023-05-05 08:28:45.134
error
Caught by controller[33]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.134
error
Caught by controller[33]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)

host.raspberrypi-iobroker
2023-05-05 08:28:45.134
error
Caught by controller[33]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.134
error
Caught  by controller[32]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.134
error
Caught by controller[31]:     at processImmediate (node:internal/timers:437:9)

host.raspberrypi-iobroker
2023-05-05 08:28:45.133
error
Caught by controller[31]:     at runNextTicks (node:internal/process/task_queues:61:5)

host.raspberrypi-iobroker
2023-05-05 08:28:45.133
error
Caught  by controller[31]:     at Roborock.setState  (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6492:35)

host.raspberrypi-iobroker
2023-05-05 08:28:45.133
error
Caught  by controller[31]:     at StateRedisClient.setState  (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)

host.raspberrypi-iobroker
2023-05-05 08:28:45.133
error
Caught by controller[31]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.133
error
Caught by controller[31]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)

host.raspberrypi-iobroker
2023-05-05 08:28:45.132
error
Caught by controller[31]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.132
error
Caught  by controller[30]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.132
error
Caught by controller[29]:     at processImmediate (node:internal/timers:437:9)

host.raspberrypi-iobroker
2023-05-05 08:28:45.131
error
Caught by controller[29]:     at runNextTicks (node:internal/process/task_queues:61:5)

host.raspberrypi-iobroker
2023-05-05 08:28:45.131
error
Caught  by controller[29]:     at Roborock.setState  (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6492:35)

host.raspberrypi-iobroker
2023-05-05 08:28:45.131
error
Caught  by controller[29]:     at StateRedisClient.setState  (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)

host.raspberrypi-iobroker
2023-05-05 08:28:45.131
error
Caught by controller[29]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.131
error
Caught by controller[29]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)

host.raspberrypi-iobroker
2023-05-05 08:28:45.131
error
Caught by controller[29]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.131
error
Caught  by controller[28]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.130
error
Caught by controller[27]:     at processImmediate (node:internal/timers:437:9)

host.raspberrypi-iobroker
2023-05-05 08:28:45.130
error
Caught by controller[27]:     at runNextTicks (node:internal/process/task_queues:61:5)

host.raspberrypi-iobroker
2023-05-05 08:28:45.130
error
Caught  by controller[27]:     at Roborock.setState  (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6492:35)

host.raspberrypi-iobroker
2023-05-05 08:28:45.130
error
Caught  by controller[27]:     at StateRedisClient.setState  (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)

host.raspberrypi-iobroker
2023-05-05 08:28:45.130
error
Caught by controller[27]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.130
error
Caught by controller[27]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)

host.raspberrypi-iobroker
2023-05-05 08:28:45.129
error
Caught by controller[27]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.129
error
Caught  by controller[26]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.129
error
Caught by controller[25]:     at processImmediate (node:internal/timers:437:9)

host.raspberrypi-iobroker
2023-05-05 08:28:45.129
error
Caught by controller[25]:     at runNextTicks (node:internal/process/task_queues:61:5)

host.raspberrypi-iobroker
2023-05-05 08:28:45.129
error
Caught  by controller[25]:     at Roborock.setState  (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6492:35)

host.raspberrypi-iobroker
2023-05-05 08:28:45.129
error
Caught  by controller[25]:     at StateRedisClient.setState  (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)

host.raspberrypi-iobroker
2023-05-05 08:28:45.129
error
Caught by controller[25]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.128
error
Caught by controller[25]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)

host.raspberrypi-iobroker
2023-05-05 08:28:45.128
error
Caught by controller[25]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.128
error
Caught  by controller[24]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.128
error
Caught by controller[23]:     at processImmediate (node:internal/timers:437:9)

host.raspberrypi-iobroker
2023-05-05 08:28:45.128
error
Caught by controller[23]:     at runNextTicks (node:internal/process/task_queues:61:5)

host.raspberrypi-iobroker
2023-05-05 08:28:45.128
error
Caught  by controller[23]:     at Roborock.setState  (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6492:35)

host.raspberrypi-iobroker
2023-05-05 08:28:45.128
error
Caught  by controller[23]:     at StateRedisClient.setState  (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)

host.raspberrypi-iobroker
2023-05-05 08:28:45.128
error
Caught by controller[23]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.127
error
Caught by controller[23]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)

host.raspberrypi-iobroker
2023-05-05 08:28:45.127
error
Caught by controller[23]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.127
error
Caught  by controller[22]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.127
error
Caught by controller[21]:     at processImmediate (node:internal/timers:437:9)

host.raspberrypi-iobroker
2023-05-05 08:28:45.127
error
Caught by controller[21]:     at runNextTicks (node:internal/process/task_queues:61:5)

host.raspberrypi-iobroker
2023-05-05 08:28:45.127
error
Caught  by controller[21]:     at Roborock.setState  (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6492:35)

host.raspberrypi-iobroker
2023-05-05 08:28:45.127
error
Caught  by controller[21]:     at StateRedisClient.setState  (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)

host.raspberrypi-iobroker
2023-05-05 08:28:45.126
error
Caught by controller[21]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.126
error
Caught by controller[21]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)

host.raspberrypi-iobroker
2023-05-05 08:28:45.126
error
Caught by controller[21]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.126
error
Caught  by controller[20]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.126
error
Caught by controller[19]:     at processImmediate (node:internal/timers:437:9)

host.raspberrypi-iobroker
2023-05-05 08:28:45.126
error
Caught by controller[19]:     at runNextTicks (node:internal/process/task_queues:61:5)

host.raspberrypi-iobroker
2023-05-05 08:28:45.126
error
Caught  by controller[19]:     at Roborock.setState  (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6492:35)

host.raspberrypi-iobroker
2023-05-05 08:28:45.125
error
Caught  by controller[19]:     at StateRedisClient.setState  (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40)

host.raspberrypi-iobroker
2023-05-05 08:28:45.125
error
Caught by controller[19]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.125
error
Caught by controller[19]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)

host.raspberrypi-iobroker
2023-05-05 08:28:45.125
error
Caught by controller[19]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.125
error
Caught  by controller[18]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.125
error
Caught by controller[17]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.125
error
Caught by controller[17]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.124
error
Caught by controller[17]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.124
error
Caught by controller[17]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.124
error
Caught  by controller[17]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.124
error
Caught by controller[17]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.124
error
Caught by controller[17]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.124
error
Caught  by controller[17]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.124
error
Caught by controller[16]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.123
error
Caught by controller[16]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.123
error
Caught by controller[16]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.123
error
Caught by controller[16]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.123
error
Caught  by controller[16]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.123
error
Caught by controller[16]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.123
error
Caught by controller[16]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.122
error
Caught  by controller[16]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.122
error
Caught by controller[15]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.122
error
Caught by controller[15]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.122
error
Caught by controller[15]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.122
error
Caught by controller[15]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.122
error
Caught  by controller[15]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.121
error
Caught by controller[15]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.121
error
Caught by controller[15]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.121
error
Caught  by controller[14]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.121
error
Caught by controller[13]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.121
error
Caught by controller[13]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.121
error
Caught by controller[13]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.121
error
Caught by controller[13]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.120
error
Caught  by controller[13]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.120
error
Caught by controller[13]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.120
error
Caught by controller[13]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.120
error
Caught  by controller[13]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.120
error
Caught by controller[12]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.120
error
Caught by controller[12]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.119
error
Caught by controller[12]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.119
error
Caught by controller[12]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.119
error
Caught  by controller[12]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.119
error
Caught by controller[12]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.119
error
Caught by controller[12]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.119
error
Caught  by controller[12]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.119
error
Caught by controller[11]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.119
error
Caught by controller[11]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.118
error
Caught by controller[11]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.118
error
Caught by controller[11]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.118
error
Caught  by controller[11]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.118
error
Caught by controller[11]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.118
error
Caught by controller[11]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.118
error
Caught  by controller[11]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.118
error
Caught by controller[10]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.117
error
Caught by controller[10]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.117
error
Caught by controller[10]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.117
error
Caught by controller[10]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.117
error
Caught  by controller[10]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.117
error
Caught by controller[10]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.117
error
Caught by controller[10]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.117
error
Caught  by controller[10]: This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.116
error
Caught by controller[9]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.116
error
Caught by controller[9]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.116
error
Caught by controller[9]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.116
error
Caught by controller[9]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.116
error
Caught  by controller[9]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.116
error
Caught by controller[9]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.116
error
Caught by controller[9]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.115
error
Caught  by controller[9]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.115
error
Caught by controller[8]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.115
error
Caught by controller[8]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.115
error
Caught by controller[8]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.115
error
Caught by controller[8]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.115
error
Caught  by controller[8]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.115
error
Caught by controller[8]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.114
error
Caught by controller[8]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.114
error
Caught  by controller[8]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.114
error
Caught by controller[7]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.114
error
Caught by controller[7]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.114
error
Caught by controller[7]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.114
error
Caught by controller[7]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.114
error
Caught  by controller[7]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.113
error
Caught by controller[7]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.113
error
Caught by controller[7]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.113
error
Caught  by controller[7]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.113
error
Caught by controller[7]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.113
error
Caught by controller[7]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.113
error
Caught by controller[7]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.113
error
Caught by controller[7]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.112
error
Caught  by controller[7]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.112
error
Caught by controller[7]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.112
error
Caught by controller[7]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.112
error
Caught  by controller[7]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.112
error
Caught by controller[6]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.112
error
Caught by controller[6]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.111
error
Caught by controller[6]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.111
error
Caught by controller[6]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.111
error
Caught  by controller[6]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.111
error
Caught by controller[6]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.111
error
Caught by controller[6]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.111
error
Caught  by controller[6]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.111
error
Caught by controller[6]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.110
error
Caught by controller[6]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.110
error
Caught by controller[6]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.110
error
Caught by controller[6]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.110
error
Caught  by controller[6]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.110
error
Caught by controller[6]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.110
error
Caught by controller[6]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.110
error
Caught  by controller[6]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.109
error
Caught by controller[6]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.109
error
Caught by controller[6]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.109
error
Caught by controller[6]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.109
error
Caught by controller[6]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.109
error
Caught  by controller[6]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.109
error
Caught by controller[6]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.109
error
Caught by controller[6]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.108
error
Caught  by controller[6]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.108
error
Caught by controller[5]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.108
error
Caught by controller[5]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.108
error
Caught by controller[5]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.108
error
Caught by controller[5]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.108
error
Caught  by controller[5]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.108
error
Caught by controller[5]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.107
error
Caught by controller[5]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.107
error
Caught  by controller[5]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.107
error
Caught by controller[5]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.107
error
Caught by controller[5]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.107
error
Caught by controller[5]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.107
error
Caught by controller[5]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.107
error
Caught  by controller[5]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.106
error
Caught by controller[5]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.106
error
Caught by controller[5]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.106
error
Caught  by controller[5]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.106
error
Caught by controller[5]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.106
error
Caught by controller[5]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.106
error
Caught by controller[5]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.106
error
Caught by controller[5]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.105
error
Caught  by controller[5]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.105
error
Caught by controller[5]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.105
error
Caught by controller[5]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.105
error
Caught  by controller[5]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.105
error
Caught by controller[4]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.105
error
Caught by controller[4]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.105
error
Caught by controller[4]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.104
error
Caught by controller[4]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.104
error
Caught  by controller[4]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.104
error
Caught by controller[4]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.104
error
Caught by controller[4]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.104
error
Caught  by controller[4]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.104
error
Caught by controller[4]:     at TCP. (node:net:301:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.104
error
Caught by controller[4]:     at Socket.emit (node:domain:489:12)

host.raspberrypi-iobroker
2023-05-05 08:28:45.103
error
Caught by controller[4]:     at Socket.emit (node:events:513:28)

host.raspberrypi-iobroker
2023-05-05 08:28:45.103
error
Caught by controller[4]:     at Object.onceWrapper (node:events:628:26)

host.raspberrypi-iobroker
2023-05-05 08:28:45.103
error
Caught  by controller[4]:     at Socket.  (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)

host.raspberrypi-iobroker
2023-05-05 08:28:45.103
error
Caught by controller[4]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)

host.raspberrypi-iobroker
2023-05-05 08:28:45.103
error
Caught by controller[4]: Error: DB closed

host.raspberrypi-iobroker
2023-05-05 08:28:45.103
error
Caught  by controller[4]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.103
error
Caught by controller[3]:     at processImmediate (node:internal/timers:437:9)

host.raspberrypi-iobroker
2023-05-05 08:28:45.102
error
Caught by controller[3]:     at runNextTicks (node:internal/process/task_queues:61:5)

host.raspberrypi-iobroker
2023-05-05 08:28:45.102
error
Caught by controller[3]:     at /opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:291:23

host.raspberrypi-iobroker
2023-05-05 08:28:45.102
error
Caught by controller[3]: TypeError: Cannot read properties of null (reading 'val')

host.raspberrypi-iobroker
2023-05-05 08:28:45.102
error
Caught  by controller[2]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

host.raspberrypi-iobroker
2023-05-05 08:28:45.102
error
Caught by controller[1]:     at /opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:321:17

host.raspberrypi-iobroker
2023-05-05 08:28:45.101
error
Caught by controller[1]: TypeError: Cannot read properties of null (reading 'val')

host.raspberrypi-iobroker
2023-05-05 08:28:45.100
error
Caught  by controller[0]: This error originated either by throwing inside of an  async function without a catch block, or by rejecting a promise which  was not handled with .catch(). The promise rejected with the reason:

roborock.0
2023-05-05 08:28:43.967
warn
setTimeout called, but adapter is shutting down

roborock.0
2023-05-05 08:28:43.927
warn
setTimeout called, but adapter is shutting down

roborock.0
2023-05-05 08:28:43.894
warn
setTimeout called, but adapter is shutting down

roborock.0
2023-05-05 08:28:43.851
warn
setTimeout called, but adapter is shutting down

roborock.0
2023-05-05 08:28:43.819
warn
setTimeout called, but adapter is shutting down

roborock.0
2023-05-05 08:28:43.787
warn
setTimeout called, but adapter is shutting down

roborock.0
2023-05-05 08:28:43.750
warn
setTimeout called, but adapter is shutting down

roborock.0
2023-05-05 08:28:43.710
warn
setTimeout called, but adapter is shutting down

roborock.0
2023-05-05 08:28:43.675
warn
setTimeout called, but adapter is shutting down

javascript.0
2023-05-05 08:28:43.616
error
script.js.common.Smart_Home_Zuhause.Hildegard.Error_Meldung: telegram: No error

roborock.0
2023-05-05 08:28:43.636
warn
setTimeout called, but adapter is shutting down

javascript.0
2023-05-05 08:28:43.606
info
script.js.common.Smart_Home_Zuhause.Hildegard.Status_Meldung: telegram: Idle

roborock.0
2023-05-05 08:28:43.595
warn
setTimeout called, but adapter is shutting down

roborock.0
2023-05-05 08:28:43.547
warn
setTimeout called, but adapter is shutting down

roborock.0
2023-05-05 08:28:43.517
error
Cannot read properties of null (reading 'val')

roborock.0
2023-05-05 08:28:43.516
error
TypeError: Cannot read properties of null (reading 'val')     at /opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:291:23     at runNextTicks (node:internal/process/task_queues:61:5)     at processImmediate (node:internal/timers:437:9)

roborock.0
2023-05-05 08:28:43.514
error
unhandled promise rejection: Cannot read properties of null (reading 'val')

roborock.0
2023-05-05 08:28:43.513
error
Unhandled  promise rejection. This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch().

roborock.0
2023-05-05 08:28:43.458
warn
Terminated (UNCAUGHT_EXCEPTION): Without reason

roborock.0
2023-05-05 08:28:43.456
info
terminating

roborock.0
2023-05-05 08:28:43.432
error
Cannot read properties of null (reading 'val')

roborock.0
2023-05-05 08:28:43.431
error
TypeError: Cannot read properties of null (reading 'val')     at /opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:321:17

roborock.0
2023-05-05 08:28:43.425
error
unhandled promise rejection: Cannot read properties of null (reading 'val')

roborock.0
2023-05-05 08:28:43.424
error
Unhandled  promise rejection. This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch().

roborock.0
2023-05-05 08:28:38.503
info
MQTT initialized

roborock.0
2023-05-05 08:28:37.790
info
starting.  Version 0.1.6 (non-npm: copystring/ioBroker.roborock#dev) in  /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0,  js-controller: 4.0.24

host.raspberrypi-iobroker
2023-05-05 08:28:34.322
info
instance system.adapter.roborock.0 started with pid 24517

host.raspberrypi-iobroker
2023-05-05 08:28:31.831
info
instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

roborock.0
2023-05-05 08:28:31.162
info
Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

roborock.0
2023-05-05 08:28:31.160
info
terminating

roborock.0
2023-05-05 08:28:31.157
info
Got terminate signal TERMINATE_YOURSELF

host.raspberrypi-iobroker
2023-05-05 08:28:31.156
info
stopInstance system.adapter.roborock.0 send kill signal

host.raspberrypi-iobroker
2023-05-05 08:28:31.151
info
stopInstance system.adapter.roborock.0 (force=false, process=true)

roborock.0
2023-05-05 08:28:15.821
error
Username or password missing!

roborock.0
2023-05-05 08:28:15.714
info
starting.  Version 0.1.6 (non-npm: copystring/ioBroker.roborock#dev) in  /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0,  js-controller: 4.0.24

Könnte allerdings auch daran liegen das ich den Adapter neu installiert habe wärend der Roboter in Stand-By war (siehe anderes Issue). Nach einem Neustart kommen keine Fehler mehr.

Nun habe ich unter "floors" nurnoch den Ordner "1" mit dem richtigen Namen der aktuellen Karte, allerding gibt es hier keine Räume mehr. Der Ordner ist leer.

Mir ist da etwas code reingerutscht, der nicht reinsollte. Diesen habe ich wieder entfernt.
Dann habe ich weitere Anpassungen vorgenommen. Diese konnte ich bei mir erfolgreich testen.
Probier es nochmal aus.

 Und evtl. dort eine überzählige/falsche Karte löschen?

Bearbeiten kann man das aktuell nicht über den Adapter. Du könntest aber mal den Inhalt von HomeData hier anhängen. Da sind zumindest alle bekannten Räume hinterlegt, egal von welcher Karten diese stammen.

Hei, jetzt sieht es gut aus!
Na da sag ich mal vielen Dank, auch dafür das du dich so bemüht hast! 👍

Da es nur eine Karte gibt, kann der Befehl load_multi_map nicht ausgeführt werden. Dafür musste eine entsprechende Logik eingebaut werden. Jetzt gibt es den Befehl nur dann, wenn mehr als eine Karte erlaubt ist.


Add metadata restore CLI

to restore mysql and postgres data after the backup

Also @MilanBariya let's update the docs based on this once we get it merged

Also @MilanBariya let's update the docs based on this once we get it merged

Sure @pmbrull I will do that.


Fix broken link to contributors

Was renamed to CONTRIBUTORS.md in https://github.com/wagtail/sphinx_wagtail_theme/pull/142

Thanks, missed that one :D


[backport] Refacotring train_mnist_dual_parallel.py

Backport of #5678

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 454cd8db99e2a9d1ac4cd13f14710c7c9d210f93, target branch v5) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

jenkins, test this please.

Jenkins CI test (for commit 454cd8db99e2a9d1ac4cd13f14710c7c9d210f93, target branch v5) succeeded!


Win32 error code 267

[true] I am on the latest Hyper.app version
[true ] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name:
Hyper.app version:

No work.(( pyton to PATH (true). I have error after command(npm run app)

Exact same error here.

Windows 10 compilation 14393.447
Latest in master, In about Hyper says "Hyper 810e0a9"

@urec @DanielRamosAcosta i had the same issue, after removing the directory and cloning it again it works fine. Try that, if it doesn't work report back please.

I completly deleted the repo, I cloned it again freshly and I still have the same issue 😢

I have python version 2.7.6, just in case:
D:\...\hyper [master ≡]> python --version
Python 2.7.6

@stefanivic no work

Hey there, please try again with the new Hyper v2 release and open a new issue if the problem stills exists. Thank you!


Deepspeed activation Partitioning

📚 Documentation
Hello,

https://lightning.ai/docs/pytorch/stable/api/lightning.pytorch.strategies.DeepSpeedStrategy.html

partition_activations (bool) – Enables partition activation when used with ZeRO stage 3 and model parallelism. Still requires you to wrap your forward functions in deepspeed.checkpointing.checkpoint. See deepspeed tutorial.

Upon encountering issues with activation partitioning and after checking, I found that Deepspeed activation partitioning is not significantly related to the use of zero-3; rather, it appears that the setup of model parallelism and mpu object is crucial.
Also, it is explicitly stated that pipeline parallelism, a model parallelism method provided by Deepspeed, cannot be used in conjunction with zero-2 and zero-3 from the outset.

https://deepspeed.readthedocs.io/en/latest/pipeline.html

Additionally, in the GitHub issue referenced in the official documentation, zero-stage3 and activation partitioning are used together; however, this pairing holds no particular significance.
Therefore, it is thought that there should be clearer statements regarding the use conditions for activation partitioning, beyond simply specifying that it should be used with zero3 + mp.
cc @borda

Please assign me, I want to do it.

Thank you, is there anything I need to do?


UI outline offset calculated incorrectly

Bevy version
0.12.0
What you did
Setting Outline.offset has no effect - however setting Outline.width affects both offset and outline.
The 'outline_offset' appears to be using outline.width instead of outline.offset. You can see the code here:
https://github.com/bevyengine/bevy/blob/1065028154b1a2b3b28cf137bb391fbba41328ce/crates/bevy_ui/src/layout/mod.rs#L412
What went wrong
Looks like a simple typo. It should be using '.offset' instead of '.width'.

 I wrote a few implementations, a third party plugin, one for the border radius PR, and a few for experimental forks of 0.11 and 0.12 with lots of rendering changes, and just the one I upstreamed to bevy has this bug. IIRC I just added some outlines to the borders example with offset and width set to 5 pixels, which worked of course, and assumed it was good :sweat:


Feature/get files method

In script docManager.js added method getFilesInFolderInfo(). First, we get the files using the getStoredFiles() method, then iterate over them. An object fileObject is created with information about the file. Each object is added to an array, which we send to the client in script app.js.
In the app.js script, a app.get("/files", function(req, res) request handler has been added, which receives information about files using the getFilesInFolderInfo() method and sends it back to the client.

@hellonadya
Please add a GET /files request to readme


DiscreteBar Chart Legend

Hello,
is there any chance to show a Legend at the DiscreteBar Chart?
My Problem is the names of the labels can be to long.. and because this i want to have a Legend and hide the labels :)
Or if somebody have a other idea to solve this problem, please write it :D
Bye Andreas

Hi!
Did you try the option "staggerLabels" which let the labels "jump" up and down to provide more space?


Clarity of examples using MRS

One thing with MRS that confuses me is the separation of the client and the server. It appears all these examples run on an MRS node. I'd like to see clarification of that in the examples and perhaps a commented out section showing how to run it if it were to run it from a Windows and/or Linux client.

Right now there is weak separation between R Server and R Client. (For an overview of R Client see https://msdn.microsoft.com/en-us/microsoft-r/r-client-get-started).
All the examples we show will run both using R Server and R Client.
I think your question is how to use R Client to connect to a remote compute context (e.g. Hadoop or SQL Server). You can find information on using compute contexts at https://msdn.microsoft.com/en-us/microsoft-r/scaler-distributed-computing.

Right, I think my suggestion is to note that in the readme's or examples somewhere how to run these examples on a remote compute context. Like so:
# For Windows
mySshUsername <- "username"
#name of PuTTY saved session
mySshHostname <- "putty_saved_sessionname"
myShareDir <- paste("/var/RevoShare", mySshUsername, sep = "/")
myHdfsShareDir <- paste("/user/RevoShare", mySshUsername, sep = "/")

myHadoopCluster <- RxSpark(
    hdfsShareDir = myHdfsShareDir,
    shareDir = myShareDir,
    sshUsername = mySshUsername,
    sshHostname = mySshHostname,
    sshClientDir = "c:\\program files (x86)\\putty")


actions-cell not aligned properly in collapsible data table

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Framework7 Version: 1.6.4

What you did
I am using collapsible data tables to show tables as list view.
If i add any actions-cell like

            compose
            trash

In collapsible format its aligned as new rows with collapsible label attribute as null.
I tried the same using

			<input type="checkbox" checked>

its aligned to the top left as expected
Expected Behavior
td>actions-cell  in collapsible format should be aligned to the top of the record.
Actual Behavior
td>actions-cell are displayed as new row with label as null
kindly help me how to fix this out.
regards,
suren

Can you show screenshot of what you have?

Issue is closed because of outdated/irrelevant/not actual
If this issue is still actual and reproducible for latest version of Framework7, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue


feature/buf-actions

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ

src/brokrpc/message.py
87.74% <ø> (ø)


Random blocking pages appearing

Hi, I've set my  configs to block Facebook, Instagram and other social media websites when I'm in my work schedule. However, the app frequently shows the overlay saying I'm trying to access one of the blocked websites even though I'm not (see below). This is kinda annoying because it only goes away after refreshing the page.
These blocking overlays also go away after some minutes if I leave them unattended

Hi @Kronos25
Do you mean that the overlay is blocking the wrong website? or is it blocking the right websites but on the wrong time schedule?
If you can send me a screenshot of your settings it would really help :)

Hi @Kronos25
Do you mean that the overlay is blocking the wrong website? or is it blocking the right websites but on the wrong time schedule?
If you can send me a screenshot of your settings it would really help :)

It is blocking the wrong websites. For example, in the above screenshots the overlay is blocking me from accessing clickup.com and it's saying I'm trying to access facebook even though I don't even have a tab with it open. At this time schedule it is indeed expected for my facebook to be blocked, but I'm not trying to open it.
These are my configs:

Still happening up to this day, not trying to pressure or something for a solution - just coming back to report that this kind of random error still occurs.

My plate is a bit full right now, I hope to get to that soon. In the meantime, try this  and let me know if it helped:
1.go to chrome://extensions/
2. disable and enable the extension

Hi @Kronos25 , did it help?

Hi @Kronos25 , did it help?

It does solve the issue when I disable and enable it, still happens some times but this is the workaround so far.

I'm having the same problem on Firefox. For example, Pinterest will be blocked after a few minutes with a message saying that Tumblr is being blocked.


cluster down while feeding large number of documents

Describe the bug
Hi, I faced an issue while trying to large number of documents in vespa cluster having 12 content nodes.
cluster has 2 groups. each group having 6 content nodes.
i am using an implementation similar to jsonFileFeeder to feed the docs.
cluster went down after feeding few million docs. I checked the logs and found the following error.
1675145234.326723       qa-content-0.qa-internal.d19.svc.cluster.local     25871    searchnode      stderr  warning vespa-proton-bin: /builddir/build/BUILD/vespa-8.82.24/vespalib/src/vespa/vespalib/datastore/buffer_type.cpp:153: virtual size_t vespalib::datastore::BufferTypeBase::calcArraysToAlloc(uint32_t, vespalib::datastore::BufferTypeBase::ElemCount, bool) const: Assertion `result >= neededArrays' failed.
1675145238.423702       qa-content-0.qa-internal.d19.svc.cluster.local     491/41265        config-sentinel sentinel.sentinel.service       event   crash/1 name="searchnode" pid=25871 signal="Aborted"
1675145238.426273       qa-content-0.qa-internal.d19.svc.cluster.local     491/41265        config-sentinel sentinel.sentinel.service       info    searchnode: incremented restart penalty to 1800.000 seconds
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

Infrastructure: Kubernetes

Vespa version
8.82.24
Let me know if you need more info.
unable to bring the cluster up. Tried restarting the nodes but seeing the above error msg in logs

We have had a look at this issue today. As this is an explicit assert it means that it is a condition that should not be possible.
After we have investigated the code we have found 2 situations what can trigger this.
1 - A single word that is longer than 16MB in a field with indexing:index.
2 - A single document with a very large field with more than 4MB occurrences of a single word, also with indexing:index.
3 - A logic flaw that we were not able to find by code inspection.
We have made a PR that will shed some more light on what it causing this in #25838. When that is merged you will get more information in the log enabling us to pinpoint the issue better.
An alternative is to inspect the issue with a debugger (gdb) and the a coredump if it is/can be enabled. Then it is possible extract the information now. But that requires some knowledge of debugging. If you want to go this way we can assist.
But then we probably need to use slack or similar. What is your timezone ?

thanks @baldersheim
I have found the document that caused this issue. for now, We are trying to find a way to figure out whether we have more similar documents that can cause this issue.
whenever this document is ingested, whole cluster went down and we are unable to bring the cluster up.
I was able to bring the cluster up only after removing the data by running following cmd in content nodes
/opt/vespa/bin/vespa-stop-services && /opt/vespa/bin/vespa-remove-index -force && /opt/vespa/bin/vespa-start-services
But right now, even after running the above cmd, my cluster is still down.
Is there any other way to check whether the whole data is removed when cluster is down.

I don't understand what you mean by 4mb occurrences of a single word in 2nd situation.

That a single word repeats 4MB times in the same document.

I was able to bring the cluster up only after removing the data by running following cmd in content nodes
/opt/vespa/bin/vespa-stop-services && /opt/vespa/bin/vespa-remove-index -force && /opt/vespa/bin/vespa-start-services

That wipes all data, and after starting the cluster (and waiting for all services) the cluster should be good to go.

4M occurrences, I think.

No, you need to upgrade to a recent version and see if the issue still persist.
We have added logging that will pinpoint more that root cause is.
If you have a document that will reproduce the issue, you can provide that a the searchdefinition and we can pinpoint it ourselves.
So far no more action planned from our side until further information is available.

No more information available. Assuming fixed. reopen with addition information if problem still persist.


How do I refresh another component after a day is selected?

Hi there,
I need to have call a API based on a selected date and show list of items with that selected date. Can you suggest a way to do this?  It might not be this component related question and more of react native but couldn't find anywhere else to ask this. Thank you in advance.
Thanks

Do you use Redux in your app? Using it, the state will change and the render component will update


XML: correct API signatures

This PR improves the accuracy of the public API signatures in the XML classes, in comparison with Darwin.
https://developer.apple.com/documentation/foundation/archives_and_serialization/xml_processing_and_modeling was used as a reference.
CC: @rothomp3

There are some changes which I'm not sure improve the existing codebase, even if they bring in the same as Darwin. For example:
- uri:
+ uri URI:

Replacing an internal variable with an uppercase variant of the same name causes unnecessary confusion. In any case, it doesn't affect the public API which remains to call with uri:
The other implementation change is options: to options mask: and then called elsewhere with options:mask. I think this reduces visibility of what it is, especially if the external parameter name is called options. It may be that the internal variable name used mask on Darwin but it doesn't add much value to have it in the Swift codebase.
Lastly there are some changes of capitalised types, like .dtd to .DTDKind. Although this might mirror the original import name from Darwin, I think it is less 'swifty' (as if such a widely used term had specific meaning ...).
That said there other changes (like DTDKind -> XMLDTDNode.DTDKind) which may have a more precise definition, but they probably need to be gone through individually to see if the changes have value or avoid ambiguity.

Thanks for your comments @alblue.
Apple do publish the parameter names of functions. For example, in the case of NSXMLElement.init(name:uri:) which you mentioned, this is documented as init(name: String, uri URI: String?) so I believed it formed part of the published API specification and hence for consistency should be the same in this project. The same applies to the mask parameter name you mention - I did'nt see any harm in being consistent.
XMLNode.Kind's DTDKind case is documented here so I believe this is perhaps less controversial and should just be corrected?  I did check this one on Darwin too. It is less Swifty as you say but that's not really the point - unless the cases are named the same code cannot be shared between Darwin and Linux without using #if os() - unless I'm missing something.
For your final comment (the DTDKind -> XMLDTDNode.DTDKind changes etc.) I believe these increase clarity in the codebase as the properties are documented in this way. Xcode has Option-click but this type of IDE feature is not widespread for Swift on Linux yet.

@swift-ci please test and merge


feat(popups): Popup Positioning

resolves #972
Summary

In several instances, the components that create popups like OverflowMenu, Tooltip, and FlyoutMenu, go offscreen.
To resolve this, a utility function was made in PopupPositioning.js. This function will reposition the popups if they're offscreen.
To use this functionality, you pass the utility function into the menuOffset prop of the component. In the specific case of OverflowMenu, when flipped is true, it needs to be passed into menuOffsetFlip
For OverflowMenu and Tooltip, if a direction is specified, it will default to that direction unless that direction is offscreen.
For FlyoutMenu, direction is completely ignored and behaves as described in #1266

Change List (commits, features, bugs, etc)

Created PopupPositioning.js, which contains the utility function
Created PopupPositioning.test.jsx which tests that the function is working as intended with the components
Created PopupPositiong.story.jsx which can be used to see the functionality and how to use it
Edited FlyoutMenu.jsx to support the menuOffset prop being a function. Also added a max width to the Flyout as described in #1266
Changed flyout-menu.scss to allow variable after distance

Acceptance Test (how to verify the PR)
Go to the PopupPositioning story, verify that when Auto Positioning is checked the popups appear within the viewport.

After some review @davidicus and I have found that the core logic around positioning values is a solid starting point, though there are places where component props/attributes/classes are accessed and modified imperatively outside of the react render cycle. Functionally this mostly works, but there are a couple edge cases related to browser resize that cause some odd rendering effects.
We need to retool this a bit to remain in sync with when the underlying components are (re)rendered. We're going to close this unmerged as it's becoming stale and unfortunately isn't a high priority at the moment for the core team to take on and push it over the finish line. We'll begin work on a new approach with this PR as a starting/inspiration point hopefully sometime soon.
Thanks for the hard work @Jessepy and getting this off to a solid start! 🎉


Jerome dev

Profiling, lmdb dataset, Ckpt saving on CPU, augmentation select (GPU or CPU), Ruff format, Bypass PIL Image and go to Tensor directly, use teacher crops, Interpolate positional embeddings, Safer load pretrained weights, Use whoi dataset means, torchvision transforms v2, torch compile, more metrics, print number of shards, add ALL split, fix Koleo loss to inf


feature: the PythonAction should not wrap any returned TaskFailed or TaskError exceptions

Sometimes, I have actions that have run time-evaluated conditions.
These actions follow the same strategy: try one thing, if it fails, try something else.
These are implemented as python actions; an example is here: https://bitbucket.org/biobakery/anadama_workflows/src/ec0cb09417f7ba5ec801b9fa021db7d934c7c015/anadama_workflows/usearch.py?at=master#cl-139
If the python action fails, it's usually because a nested CmdAction returned a TaskError or TaskFailed exception. In that case, the action raises a TaskError with the actual error string masked. The raised TaskError just describes the type of object that was returned; it doesn't tell the user how the action failed.
This feature shows the user how it failed if the PythonAction returns a meaningful exception.

Coverage increased (+0.0%) to 99.76% when pulling 47cdde57746f5a851f4be5bc84256bca35d7ac6e on schwager-hsph:PythonAction_return_error_given into 1f9c3c755c96508ca2b1b2668f102f9d2da9c614 on pydoit:master.

Well, CmdAction is supposed to be used only by doit itself, not for you to use inside a PythonAction.
You should be using plain stdlib's  subprocess. Any specific reason you chose to use CmdAction over subprocess?

I chose to use CmdAction because it does exactly what I need:

CmdAction inspects command exit status and returns exceptions understood by doit upon nonzero exit status
CmdAction substitutes task-level items intelligently into the command to be run

These are features I'd re-implement if I were not able to use doit's CmdAction

That is to say, if you have suggestions on how to make conditional actions, I'm all ears.

CmdAction inspects command exit status and returns exceptions understood by doit upon nonzero exit status

That is trivial and we can expose somehow.

CmdAction substitutes task-level items intelligently into the command to be run

But you don't even pass the a task to the CmdAction, so it wont do anything special.
I am not convinced, hehe. Can you provide me a minimal example ?

Ok. After thinking more about it... Although explicit creation of a CmdAction from a PythonAction wont ever be recommended. If doit ever support some way to to execute commands from a python-action that preserve the verbose settings it will require your patch anyway. So this patch is ok.
Please add:

your name on AUTHORS file
an entry on CHANGES
update docs mentioning that a PythonAction can directly return TaskError/TaskFailed

Ok! I've made the proposed changes to the branch. Please let me know if there's more I can / should do!

Coverage increased (+0.0%) to 99.76% when pulling 4eff8cc1c529d6872f1b8604eb530fc29eadd84a on schwager-hsph:PythonAction_return_error_given into 1f9c3c755c96508ca2b1b2668f102f9d2da9c614 on pydoit:master.

Merged. thanks! github doesnt detect because i squashed your commits.
Please pay attention not to add white-space at the end of lines... I had to clean up several of those


Refactor class interrupts into generic function

Right now most class behaviors have some sort of interrupt function laying around, merge these into a generic interrupt function instead.
https://github.com/TeamWector/Pallas/blob/master/behaviors/wow_retail/demonhunter/common.lua#L25
https://github.com/TeamWector/Pallas/blob/master/behaviors/wow_retail/mage/common.lua#L25
https://github.com/TeamWector/Pallas/blob/master/behaviors/wow_retail/warrior/common.lua#L70
https://github.com/TeamWector/Pallas/blob/master/behaviors/wow_wrath/deathknight/common.lua#L265
etc

Not touching Wrath, because cannot test, diff account for retail, other one is asleep. Fixed for DH/Mage/Sham/Huntard/Monk/Pal. Leaving Warrior retail for @ejt1.


[#326] Add a YAML tab on the Broker details view

Added a YAML tab on the Broker Details view to make it easier for users to access the Broker's details.

fixes: #326

This PR is recreated on the new arkmq-org repo: PR#4


Create a new pull request by comparing changes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 95.487%

Files with Coverage Reduction
New Missed Lines
%

js/src/dom/event-handler.js
1
91.82%

Totals

Change from base Build<PHONE_NUMBER>:
-0.07%

Covered Lines:
1961

Relevant Lines:
2015

💛  - Coveralls


Add preview image to the repository

Hi! Thank you for the xontrib!
Please add the preview image to the repository: "Settings" - "Options" - "Social preview". It allows to show preview image in Github Topics and social networks.
You already have the image for this:

Thanks!

Added, thanks!

Added, thanks!


Fix: all environment variables are exposed to the client

Greetings.
This pull request fixes: #185
Rules based on:

Storybook — Environment variables
Vite — Env Variables and Modes

Allowed on the client
Environment variables prefixes

STORYBOOK_;
VITE_.

Used for setup default envPrefix value in Vite config.
Environment variables

Storybook:

STORYBOOK;

Vite:

BASE_URL;
MODE;
DEV;
PROD;
SSR.

Used for filtering.
Best wishes,
Sergey.

I swapped out a few findIndex for startsWith and includes, and added to the existing environment variable stories to confirm it's working.  Great work here, thanks for tackling it.


Patch 15

I don't think NAIST is a good place. I need a negative words. thank for PR, but I'll close.


TypeError: Cannot read property 'filter' of undefined

Hey @ all
i had a problem with the tsconfig and pbiviz. When i use the exclude or include feature i get the Error in the headline.
But when i add the files feature i do not get the Error.
What does mean the Error? Where is filter defined? What file i miss?

This report does not provide any useful information to help diagnose the issue. If this generated in your sources, then StackOverflow would be the right place to ask this. if you believe this is a TS compiler bug, or that the crash is happening in the TS compiler sources, please file an issue on https://github.com/Microsoft/TypeScript, provide information on the version, what you are doing, and what is going wrong. also include a code sample, and/or a sample of your tsconfig.json.


CONTRIBUTING.md still refers to mapbox

This file is linked when opening a pull request against this repository and is therefore a rather high priority to overwork for maplibre. As I don't know what the contents of that file should be I can't do that myself.

file link https://github.com/maplibre/maplibre-gl-native/blob/master/CONTRIBUTING.md
next step would be

Mapbox Maps SDK for iOS
Mapbox Maps SDK for macOS

as initial step I submitted https://github.com/maplibre/maplibre-gl-native/pull/189


Added a type representing Span future

The type can be stored on the heap.
It's subject to tearing, and should not be used in multi-threaded context, or passed to user code.
The type is used as a buffer or abstract buffer pool (either managed or native)

cc @davidfowl


Improve run speed

Maybe the mapping can be improved with a different nmap command, or by changing dynamically the order of the dictionary using the bruteforcing results, or maybe you even have other ideas to improve the speed!
Any improvement would be very appreciated!

Currently, attacking a local subnetwork of 4 cameras using a virtual machine running with the following specs :
2.8GHz dual-core Intel Core i7
8GB of 1600MHz DDR3L onboard memory

takes around 3 minutes.
Discovery : 52 to 57 seconds
Dictionary attack : 65 to 155 seconds depending on the camera's credentials' position in the dictionary
Thumbnail generation : 3 seconds per camera
Stream check : less than 80ms per camera
However on a blade that has 32GB RAM and a very powerful processor, it takes significantly less time. Some tests were as low as 10 seconds for the whole process. (It might also be because the machine is on the same subnetwork as the cameras and can directly communicate with them, contrary to the testing virtual machine.)


How to set the height of datazoom

What problem does this feature solve?
dataZoom 组件:如果所需要的展示的图表本身占用的位置较低，而现在dataZoom本身的高度太高，就会导致展示图表本身的内容显示更小。
What does the proposed API look like?
可以给dataZoom，添加一个设置高度的属性

For anyone who wish to fix this issue:
It's probably related to https://github.com/apache/incubator-echarts/blob/master/src/component/dataZoom/SliderZoomView.js#L38
You should provide a new option like fillterSize and replace the constant DEFAULT_FILLER_SIZE.

@Ovilia 我发现已经有相关属性了，文档里面没写。

好的，已经设置成功。谢谢您的解答！
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年5月9日(星期六) 凌晨0:24
收件人<EMAIL_ADDRESS>抄送: "陈慧敏"<869729893<EMAIL_ADDRESS>主题: Re: [apache/incubator-echarts]  How to set the height of datazoom (#12582)
@Ovilia 我发现已经有相关属性了，文档里面没写。
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Is this issue fixed? if not can I work on this, I have the solution.

@kevalbhatt it's fixed. There is an undocumented property height for slider

@e-cloud Would you mind helping add this property to the documentation repository? https://github.com/apache/echarts-doc

Fixed in apache/echarts-doc#198


Upgrade qdata-version to 2.1.0

This is a feature change, rather than revision, since in qdata it was a feature change.


Webhook - Bad Request 400

Hi, i'm trying to use github webhook but i recieve error 400.
Prints:

Caddyfile:
www.xxxx.com.br {
	tls<EMAIL_ADDRESS>	root /var/www/html/
	fastcgi / /run/php/php7.1-fpm.sock php
	header / {
    		X-XSS-Protection "1; mode=block"
		X-Content-Type-Options "nosniff"
		X-Frame-Options "SAMEORIGIN"
		Strict-Transport-Security "max-age=15768000; includeSubdomains; preload;"
	}
  git git@github.com:derevandal/xxxx {
    key ~/.ssh/id_rsa
    path  xxxx/
    hook /webhook secret-password
    hook_type github
  }
	log /var/www/log/teste-access.log
	errors /var/www/log/teste-errors.log
	realip cloudflare
}

What did I wrong?

Same here... +1

Apparently, you need to configure Content-type to JSON.

@derevandal kindly confirm if setting the correct content-type fixed it.

@rigon where can I configure? in caddy or in github?

On GitHub, webhook settings.

Thanks. I got it.

@abiosoft could you close?

I'd like to ask that this be put in the documentation on the Caddy site.


wrong magic (invalid input file)

https://twitter.com/neauoire/status/1098029621457575937

mystery solved: their version of butler was from 2017

maybe worth adding a version check when pushing? is there a way for the server to know and send a message back

maybe worth adding a version check when pushing? is there a way for the server to know and send a message back

well, butler push isn't supposed to break across versions - protobufs allow backward-compatible wire formats, and our signature format hasn't changed ever since the first public release. The only thing that changed is.. we've upgraded the brotli compressor/decompressor. But that's also not supposed to break, content compressed with older versions might be less optimal, but it should always be decompressible with newer versions.
So, I honestly don't know why the push failed with the build of butler from 2017. But, for a year+, butler has been doing update checks on each push, and showing a pretty large message saying to update if they're out-of-date. (We did switch from a GCS bucket to broth/itch.io, but for a few months, versions were deployed to both places).
So, I don't think it's worth it!


dynamodb2 put_item returnvalues all_old return wrong value

I have this code:
class Test(unittest.TestCase):
    @mock_dynamodb2
    def test_t1(self):
        self.conn = boto3.resource('dynamodb', region_name=_region_name)
        self.conn.create_table(
            TableName=_table_name,
            KeySchema=[
                {
                    'AttributeName': 'partition_key',
                    'KeyType': 'HASH'
                },
                {
                    'AttributeName': 'sort_key',
                    'KeyType': 'RANGE'
                }
            ],
            AttributeDefinitions=[
                {
                    'AttributeName': 'partition_key',
                    'AttributeType': 'S'
                },
                {
                    'AttributeName': 'sort_key',
                    'AttributeType': 'S'
                },

            ],
            ProvisionedThroughput={
                'ReadCapacityUnits': 1,
                'WriteCapacityUnits': 1
            }
        )

        item = {
            'partition_key': 'test',
            'sort_key': 'test',
            'attr1': 'value1'
        }
        item_new = {
            'partition_key': 'test',
            'sort_key': 'test',
            'attr1': 'value1',
            'attr2': 100
        }

        self.conn.Table(_table_name).put_item(Item=item)

        r = self.conn.Table(_table_name).put_item(Item=item_new, ReturnValues='ALL_OLD')
        print(r)

when I run this test, in the terminal should be the value of item, but the output is the value of item_new
here is the doc http://boto3.readthedocs.io/en/latest/reference/services/dynamodb.html#DynamoDB.Table.put_item

ReturnValues (string) --
Use ReturnValues if you want to get the item attributes as they appeared before they were updated with the PutItem request. For PutItem , the valid values are:
NONE - If ReturnValues is not specified, or if its value is NONE , then nothing is returned. (This setting is the default for ReturnValues .)
ALL_OLD - If PutItem overwrote an attribute name-value pair, then the content of the old item is returned.

Please tell me if there is another way to do this.

I have experienced this as well.  For additional clarity, in the example above the line:
self.conn.Table(_table_name).put_item(Item=item)
will return the value of item.

Thanks for opening.
It looks like we don't support ALL_OLD for the put_item endpoint right now. I'll add this as a feature request.

This should be fixed with https://github.com/spulec/moto/pull/1938


AWS: Forbid case-insensitive credential_process

A previous commit (#2306 / 13ea4f47) put in checks to forbid the use of credential_process in AWS config/credentials files. It turns out that AWS accepts this key case-insensitively, so this commit updates our checks accordingly.
HIVE-2485

/assign @jstuever

/lgtm

/test security
Fix has merged for this 'un.
Once e2e and e2e-pool pass the first time, I'm just going to force merge this. The things that have merged in the interim are orthogonal and we don't need to burn retests.


Notebooks Feature Flag & Banner - SEAB-5261/SEAB-5262

Description
Hides notebooks from the UI for 1.14 with a notebooks feature flag (SEAB-5261) and adds a warning banner for users that get past the flags (SEAB-5262). Also adds a tab for notebooks on the search page and notebooks on the dashboard.
Pages where the feature flag can be used:

Search page (display Notebooks tab)
Dashboard (replaces the Services box)
My Starred page (displays Notebooks tab)
Sitemap (displays link to /notebooks)

Sitemap

Hidden
Enabled

Search

Hidden
Enabled

Starred

Hidden
Enabled

Dashboard

Hidden
Enabled

Additional:

I made a circle notebooks icon to match the existing circle entryType icons

I renamed the style container-background to tool-background so we can use entryType:

https://github.com/dockstore/dockstore-ui2/blob/6c1c6632558db133aa99b369d64e1158654740c2/src/app/home-page/widget/entry-box/entry-box.component.html#L23

Renamed services.svg to service.svg so we can use entryType:

https://github.com/dockstore/dockstore-ui2/blob/6c1c6632558db133aa99b369d64e1158654740c2/src/app/workflows/workflows.component.html#L37

I set the notebooks ink-bar to be purple (like orgs) since it matches the icon (previously black)

https://github.com/dockstore/dockstore-ui2/blob/6c1c6632558db133aa99b369d64e1158654740c2/src/styles.scss#L879-L883
Also side-note, I switched the sitemap to be horizontal:

Before
After

Review Instructions
Notebooks should not appear in the UI unless feature flag is used.
Tests should pass.
Issue
SEAB-5261 & SEAB-5262
Security
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that your code compiles by running npm run build
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[x] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[x] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[x] Do not use cookies, although this may change in the future
[x] Run npm audit and ensure you are not introducing new vulnerabilities
[x] Do due diligence on new 3rd party libraries, checking for CVEs
[x] Don't allow user-uploaded images to be served from the Dockstore domain
[x] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.
[x] Check whether this PR disables tests. If it legitimately needs to disable a test, create a new ticket to re-enable it in a specific milestone.

For quick reference, a couple relevant URLs are

/sitemap?notebooks=
/dashboard?notebooks=&newDashboard=


Bug: image passwords ignoring hash character

What happened?
After setting an image password, e.g. Password, a user can enter Password#123 to unlock the image. From looking at the logs, I can see everything after the # character has been removed. I've attached a video demonstrating the issue.
Kooha-2023-02-17-13-28-22.webm
Version
latest (ghcr.io/diced/zipline:latest)
What browser(s) are you seeing the problem on?
Firefox, Firefox Mobile
Zipline Logs
info  [server::response] GET /api/auth/image?id=19&password=Password123 -> 400 // Did not use hashtag
info  [server::response] GET /api/auth/image?id=19&password=Password -> 200 // Hashtag used

Seems like anything after the # character is ignored, leaving it a valid password as the request sent only contains Password (which is the correct password).

Issue was that the password supplied in the query was not URL encoded, and the # is treated like an id attribute. It has been fixed in https://github.com/diced/zipline/commit/e1003d4bb67dd679776202202e42ea94ac329698


Why is the realm lib in the release build so big?

Problem
Why is the realm lib in the release build so big?

My project is hitting 123mb after adding the realm

Solution
Decrease lib size in realm build
Alternatives
No response
How important is this improvement for you?
Would be a major improvement
Feature would mainly be used with
Local Database only

@lucas3g Thanks for reporting. We will investigate this with high priority.

@lucas3g We just released a fix for this.


Introduce Namespace

At last minute in the Gem for XML output, since namespaces are so painful.

We should also somehow allow other inline documents like SVG and MathML in the ISO document.
So we will need some namespacing eventually


V2 Authentication Migration

V2 Authentication Migration

@MistApproach
So currently for V1, authentication has been a huge issue due to the did-jwt implementation
However
It seems V2 is making this 100000x easier and way better based off this document
tldr; you generate a bearer token by signing a message and a few other steps, then request an authentication token
I created a small example of this here: https://github.com/TheLDB/fc-rust-bearer-example
AFAIK the /v2/auth endpoint isnt live/working yet, so theres no way to ensure it works, however it generates the same thing as the JS example in there so :D
any thoughts would be appreciated

First time seeing that Merkle API v2 document, thanks!
Excellent that you already wrote authentication prototype. Maybe we should create a new branch, v2-api? And start commiting to have something more or less complete for testing when v2 api goes live?

yeah good idea. having a rough model for when v2 apis go live is important
being the first library to support v2 apis would be super cool

First time seeing that Merkle API v2 document, thanks!
Excellent that you already wrote authentication prototype. Maybe we should create a new branch, v2-api? And start commiting to have something more or less complete for testing when v2 api goes live?

btw, i pushed some stuff to the v2-api branch, heres a rundown of whats there:

Added functions to:

Create a new wallet (relocated from user -> auth)
Generate a bearer token
Get a session token
Added a test route for notifications, not live yet though so unclear if itll work

Added a constants folder w/ API_ROUTE so we can change one thing and every root route changes just in case

Very happy that authenticat

ion is now working, though (see attached photo)

Very cool Landon!
Since V2 adds HTTP token headers we need to keep track of (apart from rate limits) think we should create abstraction (struct) that wraps reqwest calls. We could then keep both token and rate limit status inside this struct.
What do you think?

btw good job with extracting API base URL, was thinking of doing exactly that.

Very cool Landon!
Since V2 adds HTTP token headers we need to keep track of (apart from rate limits) think we should create abstraction (struct) that wraps reqwest calls. We could then keep both token and rate limit status inside this struct. What do you think?

I did create two custom structs (Bearer & Secret) that wrap the bearer token/payload, and the secret token with an expires at, respectively.
I'm open to any suggestions on how to improve this, just couldnt come up w/ much besides that.
To view the types:
https://github.com/TheLDB/farcaster-rs/tree/v2-api/src/types/auth
https://github.com/TheLDB/farcaster-rs/tree/v2-api/src/types/v2

Already familiar with this :) right now working on encapsulating authentication token using your code. PR soon!

Already familiar with this :) right now working on encapsulating authentication token using your code. PR soon!

just merged your PR.
since we pretty much have authentication nailed down at this point (maybe some future changes will be needed)
what should the next steps be? just slowly rebuilding calls/endpoints to call merkle endpoints vs the current ones?
if so, how should that look? was thinking of taking it section by section, archiving the old calls, writing new ones, then deleting the old ones after v2 has been tested
then, when v2 goes fully live, we can polish & publish super fast

since we pretty much have authentication nailed down at this point (maybe some future changes will be needed)

Hold on, there's one more big thing incoming :)
When speaking about higher level abstractions and encapsulation i meant more structured API from crate user point of view. Majority of my last PR is to prepare for new FarcasterAccount struct - abstraction of account used behind the scenes to obtain Merkle API authentication token, signing messages etc.
I think we need more structure as opposed to tons of unstructured, public functions implemented under Farcaster.
The way you would use FarcasterAccount is something like this:
let account = FarcasterAccount::from_mnemonic("highly secret mnemonic phrase ...");
let farcaster = Farcaster::new(ethereum_provider, account);

In addition to from_mnemonic() you can use from_private_key() - both implemented using your code. Serializing/deserializing to disk could also be implemented (security considerations though).
Behind the scenes FarcasterAccount uses auth code you wrote to prepare Bearer token and get/refresh Session token when needed.
It should fit nicely with a new "proxy" struct that could wrap all reqwest calls to add auth headers and keep track of rate limit headers etc.

what should the next steps be? just slowly rebuilding calls/endpoints to call merkle endpoints vs the current ones?
if so, how should that look? was thinking of taking it section by section, archiving the old calls, writing new ones, then deleting the old ones after v2 has been tested

The way i see it:

integrate types/v2
everything that breaks compilation (mostly get_*) - comment out for now (or even rm)
(optional) write reqwest proxy struct
start adjusting/replacing endpoint calls one by one (Casts, Notifications etc.)
when v2 goes live: v2-api -> main

Just pushed another PR that includes FarcasterAccount. Let me know what you think.