Fixing base and user objects

This fixes the base and user object to use the transaction.
Since this is the first time the transaction object is used in the code base, I will appreciate if people can take a quick look to see that everything works as expected.
Thanks!

This looks good overall, very simple changes and I like that you are reformatting the SQL to be structured in a consistent way, perhaps you should take some notes and add a section in the CONTRIBUTING.md file. Also minor note, would perhaps be good to have all SQL keywords be all-caps.
Other reviewers, these are very simple changes so it's quick to go through.

@ElDeveloper comments addressed!

Re: CONTRIBUTING.md, I've added another item to https://github.com/biocore/qiita/pull/1262

:+1:

:+1:


fix 32bits issue

From Fedora QA, on 32bits
There were 2 errors:
1) Faker\Test\Provider\DateTimeTest::testDateTimeAD
mt_rand() expects parameter 1 to be integer, float given
/builddir/build/BUILDROOT/php-Faker-1.5.0-5.fc25.noarch/usr/share/php/Faker/Provider/DateTime.php:56
/builddir/build/BUILD/Faker-d0190b156bcca848d401fb80f31f504f37141c8d/test/Faker/Provider/DateTimeTest.php:27
2) Faker\Test\Provider\DateTimeTest::testFixedSeedWithMaximumTimestamp
mt_rand() expects parameter 1 to be integer, float given
/builddir/build/BUILDROOT/php-Faker-1.5.0-5.fc25.noarch/usr/share/php/Faker/Provider/DateTime.php:56
/builddir/build/BUILD/Faker-d0190b156bcca848d401fb80f31f504f37141c8d/test/Faker/Provider/DateTimeTest.php:83

Second commit is for
There was 1 error:
1) Faker\Test\Provider\InternetTest::testLocalIpv4
mt_rand() expects parameter 1 to be integer, float given
/builddir/build/BUILDROOT/php-Faker-1.5.0-6.fc25.noarch/usr/share/php/Faker/Provider/Base.php:119
/builddir/build/BUILDROOT/php-Faker-1.5.0-6.fc25.noarch/usr/share/php/Faker/Provider/Internet.php:317
/builddir/build/BUILD/Faker-d0190b156bcca848d401fb80f31f504f37141c8d/test/Faker/Provider/InternetTest.php:103

Thanks!

Thanks for the quick merge.
FYI, Fedora QA history for this package:
https://apps.fedoraproject.org/koschei/package/php-Faker?collection=f25
While travis raise build on code change, Koschei raise build on dependency change, which is complementary. And travis is x86_64 only.


Fix file extension typo in Syntaxes section.

Hi all, found this typo, let me know if you have any questions.

.sss is a SugarSS

:D You are not first who send this PR. Maybe we should find better example.

@ai I add a comment that .sss === SugarSS in the new docs, taking it into account, I push them tomorrow when I finally have some spare time for OSS


Storybook - the first story is duplicated in the primary

Please remove the first story from the stories given that is duplicated in the primary one

closed by https://github.com/Capgemini/dcx-react-library/pull/493


Breakpoints can be set up in invalid places😱

Environment data
dotnet --info output:
VS Code version: 1.67.2
C# Extension version: 1.25.0
Steps to reproduce

Open a C# project .cs file.
Set up some breakpoints on comments, or blank lines.

Expected  behavior
Should not allow to set up breakpoints in invalid places.
Actual behavior
Those invalid breakpoints are set. Even they get moved to the next closest valid places after starting to debug, and get restored after stopping debugging. It's very annoying.

This isn't possible today. I opened https://github.com/microsoft/vscode/issues/152388 as a VS Code feature request to make it possible for an extension to do something like this.


Does not support run-completion AWs. AWs must be deleted to free quota.

Reference item #295
The work item is additional design work to support run to completion jobs in QM.  Initial design supported releasing quota only when the AW is deleted.  Advancements in MCAD after initial design of QM now run to completion AW jobs is supported.  In this model, an AW can designate a new status.state=complete or status.state=runningcompletionhold where listed items designated to monitor for a completion condition.  In general these objects have pods that run to a completion state and never restart via a management controller.  Once these pods run to completion, allocated compute resource are release and available to the scheduler for binding.  To support run to completion AW jobs, MCAD will need to detect completed objects and release resources.  The design of this enhancement will require the MCAD controller to monitor and detect run to completion objects and associated released resources and sync quotas based on release resources.

@asm582 time to close this issue?

Yup, agree, closing this issue, thanks for bringing this up!


sfdx force:source:deploy error while deploying labels without a standard name

Summary
CLI is throwing No source-backed components present in the package. when deploying custom labels with a custom name. In my case: fflib-Apex-Common-CustomLabels.labels-meta.xml. The error only shows up if you are trying to deploy using the package.xml.
Steps To Reproduce:
You could use the fflib repository to reproduce this issue: https://github.com/apex-enterprise-patterns/fflib-apex-common
After you have the repo in our machine and a org setup, take this package.xml into consideration under your manifest folder:
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>fflib-Apex-Common-CustomLabels</members>
        <name>CustomLabels</name>
    </types>
    <version>57.0</version>
</Package>

Then run the following command:
sfdx force:source:deploy -u yourusername@domain -o -g -x manifest/package.xml
Then the error pops up. It worth mentioning that, if you change the file name to CustomLabels.labels-meta.xml and also change the package.xml accordingly. Everything works as it should!
Expected result
Expected to deploy all the labels.
Actual result
Error described above.
System Information
{
  "cliVersion": "sfdx-cli/7.188.1",
  "architecture": "darwin-x64",
  "nodeVersion": "node-v18.13.0",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 1.4.5 (core)",
    "@oclif/plugin-commands 2.2.7 (core)",
    "@oclif/plugin-help 5.2.4 (core)",
    "@oclif/plugin-not-found 2.3.18 (core)",
    "@oclif/plugin-plugins 2.3.0 (core)",
    "@oclif/plugin-search 0.0.13 (core)",
    "@oclif/plugin-update 3.1.3 (core)",
    "@oclif/plugin-version 1.2.1 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.26 (core)",
    "@oclif/plugin-which 2.2.14 (core)",
    "@salesforce/lwc-dev-server 2.11.0 (user)",
    "alias 2.2.1 (core)",
    "apex 1.5.1 (core)",
    "auth 2.4.2 (core)",
    "community 2.2.1 (core)",
    "config 1.5.1 (core)",
    "custom-metadata 2.1.1 (core)",
    "data 2.2.1 (core)",
    "generator 2.0.17 (core)",
    "info 2.4.2 (core)",
    "limits 2.3.3 (core)",
    "org 2.3.2 (core)",
    "packaging 1.14.3 (core)",
    "schema 2.3.1 (core)",
    "signups 1.4.0 (core)",
    "source 2.5.1 (core)",
    "telemetry 2.1.1 (core)",
    "templates 55.4.1 (core)",
    "trust 2.4.1 (core)",
    "user 2.3.2 (core)",
    "@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)",
    "salesforce-alm 54.8.5 (core)",
    "sfdmu 4.26.8 (user)"
  ],
  "osVersion": "Darwin 22.2.0",
  "shell": "zsh",
  "rootPath": "/Users/dudunato/.local/share/sfdx/client/7.188.1-4a4bb9c"
}

@dudunato An team member dug into this and the reason for the error is that members in the package.xml can only be API names. The value in your example is a file name.
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>fflib-Apex-Common-CustomLabels</members>
        <name>CustomLabels</name>
    </types>
    <version>57.0</version>
</Package>
flib-Apex-Common-CustomLabels is the name of the custom labels file in their project. seems componentSetBuilder just doesn’t add that to the comp set.
If I change the xml to :
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>fflib_QueryFactory_crossobject_fieldsets_not_allowed_error</members>
        <name>CustomLabel</name>
    </types>
    <version>57.0</version>
</Package>
I can deploy that specific custom label because it is an API name
And
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>*</members>
        <name>CustomLabels</name>
    </types>
    <version>57.0</version>
</Package>
deploys all custom labels.

Closing as stale. If you believe this is still a bug, please open a new issue


atom-shell is now called Electron

With version 0.24.0 atom-shell has been renamed to Electron.
There's a new npm module called electron-prebuilt that replaces the atom-shell module. The old module doesn't seem to be getting any more updates as it's still at version 0.22.3. So I think we should be using the new one.

Released as v1.5.0. Thanks!


Pen thickness is differently recognized when drawing by pen or by hand

Hey,
Even though the same pen thickness is configured, when drawing with an Apple pencil on an iPad, the drawing lines are about twice as thick as when drawing by hand.

hi, @nonameplum:
I don't have Apple pencil, Can you help to verify if the same issue on https://excalidraw.com/
thanks.


Fix build issues on CI

@bebraw could you take a look?

Sure. Most likely updating Antwar to a newer version will fix it once it's good enough. I'll do the styling fix while at it too.

Updated. It should build now. I can see the CI expects to deploy from master branch. The script gets triggered when you push to develop, though. I think we might want to add a check against that and run the deploy script only when you push to master.

And fixed. There were some nasty ^s around so it tried to install wrong version.

awesome


default docker swarm installation ip addresses conflict with google cloud

when we installed a swarm cluster on a google cloud east-1a machine, we saw that the default ip addresses were 10.0.0.*.
This is conflicting with the ip addresses that Google Cloud assigns to its machines. On a distributed swarm cluster, we were having miscommunications.
What worked was the 100.64.* ip address range. 100.64 is considered as "carrier grade nat" range (https://en.wikipedia.org/wiki/Carrier-grade_NAT) and is not generally used by the dominant cloud providers.
FYI - some of the other orchestration platforms have also started using 100.64 as their defaults.
In docker swarm case, I recommend adding this to the quickstart docs as a warning. Most people will deploy to AWS or Google Cloud and this will be a big help for them.

@aaronlehmann I don't think this is a docs issue. What do you think?

I'm not sure what the next steps are on this one, so let me ping @docker/core-libnetwork-maintainers.

@nishanttotla PTAL

Issue moved to docker/editions #1442 via ZenHub


Add support for prometheus operator

https://github.com/quickwit-oss/quickwit/pull/1718

Thanks, @mkhpalm!


Implement "flattened" playlist directories

So, it turns out that while conceptually neat (to me, at least), the current playlist-structure is not very convenient when actually listening to music with "smart" media players. Such media players have a tendency to traverse a given directory indefinitely when looking for music. With the current layout of symlinks back-and-forth this makes it pretty much impossible to add a playlist-as-a-directory without first creating a playlist-file (with all the paths) and loading that. And where's the fun in that?
No, instead, I want to create a directory which simply contains each playlist as a directory, which in turn contains a symlink (I think) to the corresponding tracks "track.wav". This should allow us to load all tracks in all playlists, or one at a time into most media players.

Closed. Tracking in #23 instead.


Fixed Forecast Temperature when using OpenWeatherMap

Prior to this code change, forecast temperatures using OpenWeatherMap failed to load correctly. It does now.

Hello Shawnjoseph2001
Thanks for this pull request.
I haven't used my pebble watch for a while.
So I don't work too much on this project anymore and I'm not sure to make a new version...
Pierre

Hello! Can I have your permission to update the version of this app on the Rebble store with this fixed version? One of the maintainers on the store has allowed me to do so as long as I get your permission without any work from you. You can review my code changes if you want, very little is changed between the versions except for the forecast fix. Thank you!

Hello! Can I have your permission to update the version of this app on the Rebble store with this fixed version? One of the maintainers on the store has allowed me to do so as long as I get your permission without any work from you. You can review my code changes if you want, very little is changed between the versions except for the forecast fix. Thank you!

Thanks, @Shawnjoseph2001! Just don't forget about Git's weirdness where it doesn't remove files ignored after they were committed; they still have to be manually removed.

Thanks, @Shawnjoseph2001! Just don't forget about Git's weirdness where it doesn't remove files ignored after they were committed; they still have to be manually removed.

Hello @Shawnjoseph2001!
You will provide the app with your own openweathermap private key?
How do I give you this authorization?

Hello @Shawnjoseph2001!
You will provide the app with your own openweathermap private key?
How do I give you this authorization?

Yeah, I have my own OWM key. Just respond to this thread saying you’d be OK with it, and I’ll show it to the Rebble admins. https://prnt.sc/xxgwxl
Shawn
--
/// ||  ||   /\ \   /\   //|\ ||
\\ ||||||  //\ \ //\ // |\||
/// ||  || //  \ //  \/  ||\|
Shawn Joseph
On Jan 31, 2021, 4:09 AM -0800, plarus<EMAIL_ADDRESS>wrote:

Hello @Shawnjoseph2001!
You will provide the app with your own openweathermap private key?
How do I give you this authorization?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Yeah, I have my own OWM key. Just respond to this thread saying you’d be OK with it, and I’ll show it to the Rebble admins. https://prnt.sc/xxgwxl
Shawn
--
/// ||  ||   /\ \   /\   //|\ ||
\\ ||||||  //\ \ //\ // |\||
/// ||  || //  \ //  \/  ||\|
Shawn Joseph
On Jan 31, 2021, 4:09 AM -0800, plarus<EMAIL_ADDRESS>wrote:

Hello @Shawnjoseph2001!
You will provide the app with your own openweathermap private key?
How do I give you this authorization?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Ok, I give you the permission to update the version of this app on the
Rebble store with this fixed version
Pierre
Le dim. 31 janv. 2021 à 18:47, Shawn Joseph<EMAIL_ADDRESS>a
écrit :

Yeah, I have my own OWM key. Just respond to this thread saying you’d be
OK with it, and I’ll show it to the Rebble admins. https://prnt.sc/xxgwxl
Shawn
--
/// ||  ||   /\ \   /\   //|\ ||
\\ ||||||  //\ \ //\ // |\||
/// ||  || //  \ //  \/  ||\|
Shawn Joseph
On Jan 31, 2021, 4:09 AM -0800, plarus<EMAIL_ADDRESS>wrote:

Hello @Shawnjoseph2001!
You will provide the app with your own openweathermap private key?
How do I give you this authorization?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/plarus/TimeStyleBBPebble/pull/18#issuecomment-770420678,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD5W24QLM6XUPFJJAVMAUBDS4WJUDANCNFSM4VHYYJFA
.


Model fixup customizations

A number of customizations are simply modeling errors—We should be able to share these transformations with the GoV2 SDK if they aren't already upstreamed

To put it another way, go steal customizations from the Go v2 SDK


tooltip cleanup: prevent clipping on the top of the svg

as of #284, we still don't modify the tip when it is going to be clipped by the bounds of the top of the svg (we do handle right/left clipping)

Also, using the third element of the viewBox to define in/out of the svg isn't really correct. We don't often alter the first part of the viewBox, but if we did, it would mess up this logic. From mozilla:
The value of the viewBox attribute is a list of four numbers min-x, min-y, width and height

At some point, it may be advantageous to move into an html tooltip https://codepen.io/billdwhite/pen/rgEbc
A couple of advantages include: no clipping when the bounds of the svg are smaller than the page (i.e., can float outside of the svg), and can wrap text.


Remove high_constraint_region_mito

The addition of mito local constraint on this ticket will enable the removal of high_constraint_region_mito .  There's additional weird case in compare_globals that can be removed.

Removed during reference data refactor.


use of new DateTimeImmutable without \ prefix or use statement

Monolog version 2
https://github.com/Seldaek/monolog/blob/main/src/Monolog/Logger.php#L310
Attempted to load class "DateTimeImmutable" from namespace "Monolog".
Did you forget a "use" statement for another namespace?

Also seen on StackOverflow

That class exists: https://github.com/Seldaek/monolog/blob/main/src/Monolog/DateTimeImmutable.php

Same problem here. We don't know what causes this, everything looks fine (we even debugged autoloading).

This occurred for me today - verified all the files are there, so not sure what's causing it.

Hi,
An upgrade of PHP 8.1 resolved the issue for me. I am on debian 11 with the remi-repo (inside docker).
These are php 8.1 versions :
Unpacking php8.1 (8.1.2-1+0~20220127.12+debian11~1.gbpe46588) over (8.1.1-1+0~20211220.11+debian11~1.gbp519568)
I didn't find any related bug in PHP changelog https://www.php.net/ChangeLog-8.php#8.1.2.

Hi,
An upgrade of PHP 8.1 resolved the issue for me. I am on debian 11 with the remi-repo (inside docker).
These are php 8.1 versions : Unpacking php8.1 (8.1.2-1+0~20220127.12+debian11~1.gbpe46588) over (8.1.1-1+0~20211220.11+debian11~1.gbp519568)
I didn't find any related bug in PHP changelog https://www.php.net/ChangeLog-8.php#8.1.2.

It does not work in all situations... I don't understand what happens, but I'm not sure that the php version fixed the issue... (sorry for the noise).

I have the same issue in symfony app after upgrading to PHP 8.1 in some cases.
Attempted to load class "DateTimeImmutable" from namespace "Monolog".
Did you forget a "use" statement for another namespace?

Clearing opcache fixes the problem in my case.
That is stacktrace:
Symfony\Component\ErrorHandler\Error\
ClassNotFoundError
in /var/www/project/vendor/monolog/monolog/src/Monolog/Logger.php (line 309)
in /var/www/project/vendor/monolog/monolog/src/Monolog/Logger.php -> addRecord (line 494)
in /var/www/project/vendor/symfony/error-handler/ErrorHandler.php -> log (line 538)
in /var/www/project/vendor/composer/ClassLoader.php -> handleError (line 571)
in /var/www/project/vendor/composer/ClassLoader.php include (line 571)
in /var/www/project/vendor/composer/ClassLoader.php Composer\Autoload\includeFile (line 428)
in /var/www/project/vendor/symfony/error-handler/DebugClassLoader.php -> loadClass (line 353)
in /var/www/project/vendor/monolog/monolog/src/Monolog/Logger.php -> loadClass (line 309)
in /var/www/project/vendor/monolog/monolog/src/Monolog/Logger.php -> addRecord (line 507)
in /var/www/project/vendor/symfony/event-dispatcher/Debug/TraceableEventDispatcher.php -> debug (line 319)
in /var/www/project/vendor/symfony/event-dispatcher/Debug/TraceableEventDispatcher.php -> postProcess (line 162)
in /var/www/project/vendor/symfony/http-kernel/HttpKernel.php -> dispatch (line 217)
in /var/www/project/vendor/symfony/http-kernel/HttpKernel.php -> handleThrowable (line 110)
in /var/www/project/vendor/symfony/http-kernel/EventListener/DebugHandlersListener.php -> terminateWithException (line 129)
in /var/www/project/vendor/symfony/error-handler/ErrorHandler.php :: Symfony\Component\HttpKernel\EventListener\{closure} (line 607)
ErrorHandler->handleException(object(ClassNotFoundError))

So, I deploy code to server with PHP 8.1 (change symlink)

send request to clear opcache (opcache_reset() in top of index.php if specific POST param is sent).
send the first healtcheck http-request to app - response is 200 OK.
send the second healtcheck http-request to the same route to app - response is 500. After that, all requests to any route fails with code 500 (btw nothing logged to var/log/). [not always reproduced, sometimes everything is okay]. That's "class not found" issue - as debug showed. But the class is definitely there.
If I clear opcache the second time, everything works fine and I can't reproduce any more till new deployment.

Once, It was reproduced on my local env. But I have no idea what's going on and how to find stable reproduce.

This really seems like an opcache bug if you are all running 8.1, one of you should definitely report this to the php project.

I updated composer dependences to get rid of deprecation warnings, and seems the problem Attempted to load class "DateTimeImmutable" from namespace "Monolog" was gone for me.
In general, it was composer update with a lot of minor changes and some major.
But anyway, it was strange: composer why-not php 8.1  was happy even before this update. I don't know which change exactly did the trick.

Some problem here. I opened a bug in php-src

Some problem here. I opened a bug in php-src

Can you post a link to the bug?

I had the same issue in a Laravel app, after upgrading PHP 8.0.9 to 8.1.3 and laravel/framework from 8.40.0 to 8.67.0.
Adding require_once dirname(__DIR__).'/vendor/monolog/monolog/src/Monolog/DateTimeImmutable.php'; helped but an even better fix was to remove vendor directory, reinstall dependencies and run artisan optimize:clear. One of these steps helped and I no longer experience the issue.

Upstream bug report: https://github.com/php/php-src/issues/8164. I think this ticket can be closed.

I had the same issue in a Symfony app and finally reset the OPcache by restarting the PHP FPM service after the cache warmup did the trick. Just restart the service before the cache warump brought the error back after some request and therefor was not enough.

I had the same issue in a Symfony app and finally reset the OPcache by restarting the PHP FPM service after the cache warmup did the trick. Just restart the service before the cache warump brought the error back after some request and therefor was not enough.

Sadly my assumption of having the bug fixed was wrong, 5 minutes later a run again into the same issue :( If I restart the PHP FPM service again manually issue is gone for the moment. Guess it's a question of time until it's back again...

I'd say track https://github.com/php/php-src/issues/8164 - and add infos there if you can, maybe getting some stack trace would help someone figure it out in php core, but not sure how easy that is on prod systems.

I'd say track php/php-src#8164 - and add infos there if you can, maybe getting some stack trace would help someone figure it out in php core, but not sure how easy that is on prod systems.

Yeah thanks, already doing that and also thought about what to provide to get it fixed. But interesting so far I'm not longer able to reproduce after the third restart. Very weired issue...

For me it works now, I'm not longer able to reproduce the issue!

For me it works now, I'm not longer able to reproduce the issue!

How did you solve it ?

For me it works now, I'm not longer able to reproduce the issue!

How did you solve it ?

Check my comment above https://github.com/Seldaek/monolog/issues/1626#issuecomment-1084314823.
Little adaption in the deployment and multiple FPM service restarts solved the issue for me.

For me it works now, I'm not longer able to reproduce the issue!

How did you solve it ?

Check my comment above #1626 (comment).
Little adaption in the deployment and multiple FPM service restarts solved the issue for me.

Yes we are going to solve this as well by disabling opcache and restarting FPM one extra time at the end of our deployment process. It looks a bit messy but we didn't find any other solution for now

For me it works now, I'm not longer able to reproduce the issue!

How did you solve it ?

Check my comment above #1626 (comment).
Little adaption in the deployment and multiple FPM service restarts solved the issue for me.

Have you checked if it was enough to reset opcache? When do you do multiple restart?
I faced with error 500 starting from the second request to app (the 1st one request was OK).
For me, FPM restart and OPcache reset - both helped, so I was reseting opcache, my comment was https://github.com/Seldaek/monolog/issues/1626#issuecomment-1036307838
I changed my deployment process:

several healthchecks instead of one before returning node to LB
reset opcache second time if healthcheck response code is 500 (later I removed this condition as can't reproduce any more)

Seems to be resolved by PHP now see https://github.com/php/php-src/issues/8164. For me the error did not show up again so far, imho the issue here can be closed too @Seldaek .

Great thanks for the update, closing then.


Add german / international keyboard support to manual_control.py

manual_control.py uses the backquote key ("`") to change the used sensor. That is an issue on German keyboard layouts (and potentially a number of other international layouts) since there is no backquote key in this layout (it's not a single keypress, you need to press a key and another key to create a backquote character). I propose to use the "n" key instead, which is not used so far and which I assume is produced by a single key press on a lot if not all layouts.

This change is

Is this merge request missing something from my side? It's been a while, and it's a really small change, probably like a 60 second review...?

Personally I would keep both "`" and "n" to change the sensor.

Personally I would keep both "`" and "n" to change the sensor.

I don't really care what the actual key is, honestly, or how many there are -- as long as it is available on my keyboard. Do you want me to make a patch on top that adds in the old key as well?

It was just a suggestion, that key is conveniently placed in English keyboards. In any case this PR looks good to me.

Personally I would keep both "`" and "n" to change the sensor.

I don't really care what the actual key is, honestly, or how many there are -- as long as it is available on my keyboard. Do you want me to make a patch on top that adds in the old key as well?

If you could do that, I'll test it and merge very quickly - sorry for the delay!

Personally I would keep both "`" and "n" to change the sensor.

I don't really care what the actual key is, honestly, or how many there are -- as long as it is available on my keyboard. Do you want me to make a patch on top that adds in the old key as well?

If you could do that, I'll test it and merge very quickly - sorry for the delay!

Here you go. I hope.


Honor the schema version set in the configuration in +[RLMRealm migrateRealm:]

:+1:

This seems to have broken all the Swift migration tests.

The deprecated migrateRealm(path:encryptionKey:) isn't setting a schema version on its configuration. All of the tests are using this legacy API rather than the new migrateRealm(configuration:).

Now passes all tests with a few more functional changes.

:+1:


Version for latest uchiwa in sensu apt-repos has likely incorrect version number

When trying to install the latest version via chef with a version pin, the latest can't be found as it as an extra 1: in front of the version number.
> sudo apt-cache show uchiwa | grep Version
Version: 1:0.14.0-1
Version: 0.13.0-1
Version: 0.12.1-1
Version: 0.12.0-1
Version: 0.11.2-1

Thank you for reporting this issue. I'll have new packages available as soon as possible!


AI does not work on spaceship

Description of the bug
When turning AI on your combat ship in a space battle ( Stats > Override AI Control Behaviour > Make Character AI controlled) it simply only ends turns automatically and does not move, nor fight. This option works for companion characters and they fight after turning AI on, but for the spaceship it does not work. Would be possible to fix that?
Steps To Reproduce

Enter to space combat
Open ToyBox > Party > Starships > "Your flagship" > Stats > Override AI Control Behaviour ON > Make Character AI controlled ON

Expected Behavior
AI should control a spaceship and fight as usual in ground combat but instead, AI only skips turns automatically in space combat without moving or firing.
Log Files
No response
Save File
Manual_69_Sotto_s_Tomb__New_Save__21_42_00.zip
Screenshots
No response
Settings
No response
Toybox Version
1.6.10
Operating System
Windows 11
What game are you using Toybox on?
Rogue Trader
Game Version
<IP_ADDRESS>
Anything else?
I love AI fights.

Update: Updated to 1.3v game patch and 1.7.7 ToyBox patch but the issue still persists.

ToyBox does not implement AI. All the toggle does is enable the built-in AI (called brain) of a unit. This works for normal companions as they have a simple brain attached, but it seems like the player Starship(s) don't have a (fitting) brain attached.
My guess is non-AI units all have a default brain which have simple actions, but those simple actions can't be used by Spaceships

ToyBox does not implement AI. All the toggle does is enable the built-in AI (called brain) of a unit. This works for normal companions as they have a simple brain attached, but it seems like the player Starship(s) don't have a (fitting) brain attached.
My guess is non-AI units all have a default brain which have simple actions, but those simple actions can't be used by Spaceships

Ah, that's pretty sad. Space combat looks very nice and it would be interesting to see how AI handles the main voidship with various abilities because AI always makes the best moves and ends up in the best position (for example weapons are out of range to attack and need to perform inconvenient maneuvers to attack enemies on the next turn). It is quite strange why specifically the player's voidship does not have an attached brain, as both enemy and friendly ships do (for example, Imperial Navy cruiser and other capital ships with many abilities have AI and use those abilities during the fight). Thank you for your explanation and support.

ToyBox does not implement AI. All the toggle does is enable the built-in AI (called brain) of a unit. This works for normal companions as they have a simple brain attached, but it seems like the player Starship(s) don't have a (fitting) brain attached.

My guess is non-AI units all have a default brain which have simple actions, but those simple actions can't be used by Spaceships

It is quite strange why specifically the player's voidship does not have an attached brain, as both enemy and friendly ships do (for example, Imperial Navy cruiser and other capital ships with many abilities have AI and use those abilities during the fight).

Because the devs expect them to need to be driven by AI, meaning they attached a brain there. The player-driven ship however isn't supposed to be AI-controlled so nobody attached on there.
Maybe using PatchTool could allow manually attaching a proper brain? I don't know.

Now I understand why AI can be attached to companions, because there are cases where they are controlled by AI in certain fights companion being outside of your party but just an ally. But also, if there is a possibility of attaching AI brains to the spaceship via PatchTool, that would be great.


Remove www

Description
Removes guidance about using www in writing web addresses.
Additional information

Not ready to merge
Will close #162

Definition of Done

[ ] Draft reviewed by other Content Designer
[ ] Update to Updates page
[ ] PR approved by Libby
[ ] Related GitHub issues closed

Linking this PR to issue #162 (:


Bug on DMF pages

Display is broken in DMF pages
https://qonto.github.io/database-monitoring-framework/latest/

Update: we are working on it.

Problem is not fixed.
A v0.2.1 tag was created instead of 0.2.1. Tag was deleted and website were regenerated but for some reason, some Github pages were in cache on Github servers with outdated version.
I just unpublish & restarted the CI to fix it.


[WIP] Proof of concept for using PyO3 in cargo unit tests.

Summary
For now, this is mostly just a proof-of-concept. I'm making a non-draft PR to see how our CI setup works with this.
Details and comments
TBD.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

0 of 0   changed or added relevant lines in 0 files are covered.
14 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.02%) to 88.924%

Files with Coverage Reduction
New Missed Lines
%

qiskit/transpiler/passes/synthesis/unitary_synthesis.py
2
88.26%

crates/qasm2/src/lex.rs
6
91.98%

qiskit/synthesis/two_qubit/xx_decompose/decomposer.py
6
90.91%

Totals

Change from base Build<PHONE_NUMBER>1:
0.02%

Covered Lines:
73479

Relevant Lines:
82631

💛  - Coveralls

If you enable the pyo3/auto-initialize feature during the test-suite build, then the pyo3::prepare_freethreaded_python calls won't be necessary.  Don't know if you had other work around the test harness planned, though.

This should be ready to go, @mtreinish.
The Rust tests for DAGCircuit added in the PR can be seen passing in CI here: https://dev.azure.com/qiskit-ci/qiskit/_build/results?buildId=62018&view=logs&j=bf26c3d0-9b88-5f67-96f4-43488114ea6d&t=5c74c3c4-ab20-5140-0e04-11aec0505a88&l=148


Unexpected results if the node project is located at path containing square brackets []

What were you expecting to happen?
Hi! I'm learning gulp and just wanted to try out a very basic usage, namely copying some files from one folder to another.
What actually happened?
Nothing. No message error, execution seems normal but I've observed no changes in the file structure.
Please give us a sample of your gulpfile
const {src,dest} = require("gulp");

exports.default = (fulfill) => {
	return 	src("index.js").pipe(dest("output"));
}

Terminal output / screenshots
[11:20:47] Starting 'default'...
[11:20:47] Finished 'default' after 35 ms

Please provide the following information:

Windows 7
node version v12.18.2
npm version 6.14.5
CLI version: 2.3.0
Local gulp version: 4.0.2

Additional information
After some testing I've realised that the culprit is the absolute path of the project itself, namely a folder that contained square brackets in the folder name.
For example the path of my node project is like this:
C:/[node]/projects/learning-gulp
When I copied the project to a location that doesn't contain square brackets, everything started to work as expected.
To make sure, I've done two additional tests. Placing the node project under the following path has exactly the same (= none) result:
C:/projects/[learning-gulp]
An interesting case though was when I removed one of the brackets. So for this path:
C:/projects/[learning-gulp
...as the result, the index.js was WAS copied, but under the output/[learning-gulp folder instead of just output.
So the absolute path of the copied file was:
C:/projects/[learning-gulp/output/[learning-gulp/index.js
Note:
I know this issue is similar to #2436 but note that in my case the problem are square brackets in the path "above" the gulpfile.js, and not within the node project folder. My code also doesn't include paths with square brackets at any point, so the problem is not explicitly in the programmer's code, thus rendering it more difficult to detect, especially for new-comers to Gulp.

Whoa! That's definitely an issue. Thanks for pointing it out.
Just curious, why do people put square brackets in file paths? That's such an obscure pattern 😅

I was expecting that question :p I usually just keep my projects with all kinds of important stuff in a synchronised folder, like C:/[Synchronised]. I wanted it to appear always on top of the list and be easily distinguishable, so I figured I can just wrap its name in square brackets. Seemed like a harmless idea at the time... Ha ha, but to be honest, it may sound surprising, but I really so rarely get any issues because of the square brackets that I hardly remember they're there.

This will be fixed in gulp v5 via glob-stream v8. See https://github.com/gulpjs/glob-stream/pull/117 for more information.


Action coverage

Tests set up with code climate and git hub actions

Okay, all tests pass except the ones the 3 that deal with cookie headers. It seems to be a specific problem with code climate. All tests pass locally for me and pass with coverage scripts.


chore: Update killercoda url

Motivation
The Pipekit team forked the old catacoda training course and has been building it up on killercoda. This has now been merged back upstream.
This PR changes the url to the training course in the argo workflows docs.

Any reason for keeping it as draft?

Yes. The documented submission process is that I shouldn't take it out of draft until the build is green.

The failure is irrelevant. Fixing in https://github.com/argoproj/argo-workflows/pull/12245


Discourse Forums

Discourse Forums
Dataset URL - here
Does the dataset exists in a scraped format ?   No
Description
Discourse is a self-hosting platform for communities to create discussions around a particular topic. They include threads of posts and an eco system to discuss a particular topic.
Procedure

[ ] Find a good way of indexing all current discourse websites
[ ] Apply filtering to only include active/popular discourse sites
[ ] Scrape posts that have at least one reply

One thing we can do is look at common crawl for *.discourse.group as that is a commonly used url for these communities. There are a lot of other ones tho, so getting those will be a challenge. The dataset URL link I added has a thread on where we might find a large index of all sites using discourse.

Some more communities: https://www.communitystack.com/communities/

I've started writing a crawler for Discourse servers, using scrapy to fetch the JSON API and save all of the post data to the filesystem.  It works by taking a list of discourse server URLs (the longer the better), and will use the "latest posts", "top posts" and "categories" lists to start walking through the full database of topics.  I'm currently not doing any filtering, but we can add whatever filtering rules we need at crawl time to decide which topics to save.
Now that I've got the crawler working for individual discourse servers, I'll start working on building a list of relevant communities to scrape. Seems there are few different sites which offer categorized lists of open discourse servers, so I can probably just throw them into the crawler too.
Will submit a pull request once I've got the crawler better integrated into the Code-Pile framework, based on conversations I had with other developers.

This query returns around 8400 results for various communities that run Discourse. Definitely needs filtering to narrow down to just code-related ones.
https://www.google.com/search?q="Moderators+have+special+authority%3B+they+are+responsible+for+this+forum.+But+so+are+you.+With+your+help%2C+moderators+can+be+community+facilitators%2C+not+just+janitors+or+police."


cacheValues might be null

cacheValues is null in a test case of AunthenticatorAPIHelperTest
Related PR: https://github.com/AzureAD/ad-accounts-for-android/pull/1916

probably one of the implementations of getAllFilteredBy is returning null - which I guess is okay given that the interface doesn't annotate this as NonNull


Warn when loading a subsystem in virtual mode

Starting a subsystem in virtual mode is often a temporary hack in order to start the parameter framework with a buggy subsystem.
This modification although useful in some case, may lead to hard to debug bug if the user is not aware of the virtual state.
Notify the user by warning when a subsystem in loaded in virtual.

[ ]   General Comment
<img border=0 src='https://avatars.githubusercontent.com/u/6862950?v=3' height=16 width=16'> @dawagner please review

This pull request is now managed with CodeReviewHub. Refresh.

@dawagner please review

@tcahuzax Please review

:+1: @dawagner @dawagner  Please approve

:shipit:


Fix bevy_ggrs example not working on native

Fixes #417

Perhaps we should add the multi-threaded feature as dependency for bevy_matchbox as well? It's already required for the signaling feature. I don't understand exactly why it's needed though.


PoolThreadCache uses wrong variable in IllegalArgumentException

Motivation:
PoolThreadCache includes the wrong value when throwing a IllegalArgumentException because of freeSweepAllocationThreshold.
Modifications:
Use the correct value.
Result:
Correct exception message.

Cherry-picked into 4.1 (b32e07c75a903300b43b8d606f9f2e41579efdff) and 4.0<PHONE_NUMBER>755c86de615a09a2f44ac9f41579fe)


Installer code updated

Hello!
I recently updated the installer code. The improvements I made were:

I removed a double clone from the repository which, frankly, was there without any sense. Now it runs the build directly from the folder containing the installer.

I added an update for Rust. This is because in previous versions of Fedora the Cargo compiler was throwing a compile-time incompatibility error.

I added a process death for the Dunst program. This is because it was successfully uninstalled, but the remnants of Dunst were still running even after uninstallation.

I removed the Git installation check. This because its presence is not necessary, as I removed the double clone from the repository.

And that's it, cheers!

Nice work!


Experimental support for color counts..

Experimental support for color counts.
Added panel for color counts.
Button to see preview of the 1000 most common colors with visuals.
"Save" button will download an array with color counts for all colors in the image.
Preview is limited to most common colors because excessive DOM size causes lag.

more ideas:
only show alpha is alpha channel exists
way to toggle between hex and rgb(a)

Thank you guys!!!
More idea: You can look at how I implemented indexed color table and I think pretty much the same can be applied to here (even reusing the code). The interface can be more compact and we can make use of the original color picker with both RGBA and hex. Also, I don't think we need to show the top 1000 directly in any case, better to restrict it to ~100 and we can add a "More" button if we want, or just let users download the file if they need more than ~100.

Even better: why not just merge indexed color table and counter together into a single panel outside Advanced?

Yeah that sounds like a great idea! Here's what we're thinking in addition:
After pressing the general "color viewer" button, the panel contains a "counter" and a "colormap (gifs)" button. colormap option will be disabled for non-gifs.
Then we will add three new buttons:

compact / expanded toggle - toggles between the current color picker view, and the one tyte made. Expanded view shows the color count or gif color table index
sort (for non-gifs only) - you can sort by count
save - saves all color data into a file

Also an idea for the "more" button:

This container can scroll

Sorry for the long delay - I finally have time to finish the feature.
I added the two features Catz suggested (hex values and alpha channel adjustment). Also, I added page buttons so that people can view all the counts while keeping the interface clean. At the same time, I removed the save and clipboard features as they now don't fully fit in.
Regarding my previous comment, I decide to separate the UIs for color counts and indexed color table, as they represent different user needs. It may be beneficial if people can see all the color values and counts at the same time instead of one by one. The indexed color table may have duplicate or unused colors, which would look awkward in color counts. I will still put the color table under the same button in later commits though.


Question: Why logs are per iteration and not per epoch?

I know that it is easy to log per epoch by calculating the mean of all the iteration. But is there any specific reason for working with iteration and not per epoch?

No specific reason. Just a consistent with SSD paper and official impl https://github.com/weiliu89/caffe/blob/ssd/examples/ssd/ssd_pascal.py#L370-L374.

Thanks.


Make seed type to be Int32 so that it is compatible with TPUs.

Otherwise, @burmako and I encountered the following error when running MNIST on TPUs:
 (OpKernel was found, but attributes didn't match) Requested Attributes: T=DT_INT32, Tseed=DT_INT64, dtype=DT_FLOAT
	.  Registered:  device='TPU'; Tseed in [DT_INT32]; T in [DT_INT32, DT_INT64]; dtype in [DT_FLOAT, DT_BFLOAT16]

@bgogul just purely curious here, you were trying to use s4tf to train a model on a tpu?

@bgogul just purely curious here, you were trying to use s4tf to train a model on a tpu?
That's so cool :o.

@Shashi456, yes.  :) now that GPE is deprecated, we are experimenting with alternative ways of extracting graphs.  I will have more PRs on this shortly.


Vue support

Hi, sorry to post a question here, but I don't have a lot of time to figure out how the plugin works.
I'm trying to understand how to work with the plugin during development. I have everything set up for build and docker. Everything works great. But when I try to run the project locally through: “dev": ‘vite’, the variables I'm trying to get import.meta.env.FOO === undefined. Although when I call __VITE_ENVS through the developer console I get the whole list of variables and it is valid with the data that I would like to get instead of undefined.
Can you briefly describe how to proceed in dev mode, or provide a minimal demo?

Hello @melishev,
It's supposed to work. The plugin is supposed to be transparent.
Everything should work like when you don't have the plugin setup, and just enable you to inject the variables by running the bash script.
There is a demo repo here: https://github.com/garronej/vite-envs-starter
And a demo video here: https://www.youtube.com/watch?v=wsY7VDUIZM0
One thing that does not work is web workers. Beside this if it does not work please share some aditional informations I'll help you debug or fix the issue on my end if there's any.

@garronej
Here is link to reproduction: https://github.com/melishev/vite-envs-demo
I don't think I ever found an explanation of this case in the documentation

Thank you for the repro @melishev,
The important bit of context I was missing was that you're using vue.
I released a patch for supporting it<EMAIL_ADDRESS>PS: Don't forget to add "postinstall": "vite-envs update-types", in the scripts of your package.json. It was missing in your repo.


updating parameters via script

hello @CiaccoDavide
I'm trying to change thickness and rotation from scripting and also from itween component.
Values are changing but not reflecting on the shape, they only reflect when I'm using the Inspector's sliders directly with the mouse.
I changed void Update method to public void Update and calling it from the script, but still not working.
Can you give some tips on how to change the parameters from code?
Thank you
Marlus

solved by creating a redraw method that calls SetVerticesDirty
public void Redraw(){
    SetVerticesDirty();
}


Allow option to compute odometry from unpowered wheels

Is your feature request related to a problem? Please describe.
In the current ackermann controller the odometry is computed from the steering angle, the kinematic setup and the rotation of the traction wheels. Since the traction wheels have slip in contrast to unpowered wheels (which may be quite influential for car-like robots with high inertia), the odometry gets negatively affected by this. Maybe this also affects tickets like #937 since the default gazebo setup often results in high slip driving situations in my experiments.
Describe the solution you'd like
It would be great to have an option to specify the non-traction wheels in the config of the ackermann controller and use them for the odometry computation.
Describe alternatives you've considered
It would probably be possible to write a function on top of the ackermann controller that corrects for these issues by computing the slip, but that seems like an unnecessarily complex setup.

Hi! I was thinking a bit in this direction, to make the steering_library more configurable with setups as you describe. It stopped with https://github.com/ros-controls/ros2_controllers/pull/954 waiting for reviews (you want to proofread it and leave a review there)?
But I certainly won't have time before the Jazzy release to work on this again.


Code redundancy in pipeline.vote

Open models.py and pipeline.vote.py
    vote_pipeline = Pipeline([
        Node(voter.validate_block),
        Node(voter.ungroup),
        Node(voter.validate_tx, fraction_of_cores=1),
        Node(voter.vote),
        Node(voter.write_vote)
    ])

voter.validate_block cotains self.consensus.validate_block(self.bigchain, block) ,and it calls Class Block method validate(self, bigchain) in models.py:184, in this method

        for tx in self.transactions:
            # NOTE: If a transaction is not valid, `is_valid` will throw an
            #       an exception and block validation will be canceled.
            bigchain.validate_transaction(tx)

So in voter.validate_block we validate all of the txs ,then in voter.validate_tx we validate all of the txs again.Whether it affects efficiency? Is it necessary to validate all of the txs in Block.validate()?

in pipeline.vote.py:48

         if not self.bigchain.has_previous_vote(block['id'],
                                               block['block']['voters']):

in models:202
        if bigchain.has_previous_vote(self.id, self.voters):

in voter.validate_block we would do bigchain.has_previous_vote twice.Is it necessary to make sure has_previous_vote in Block.validate()?

in models.py:256  of from_dict(cls, block_body) , Target is to transform a Python dictionary to a Block object. But:

        if block_id != block_body['id']:
            raise InvalidHash()

        if signature is not None:
            # NOTE: CC throws a `ValueError` on some wrong signatures
            #       https://github.com/bigchaindb/cryptoconditions/issues/27
            try:
                signature_valid = public_key\
                        .verify(block_serialized.encode(), signature)
            except ValueError:
                signature_valid = False
            if signature_valid is False:
                raise InvalidSignature('Invalid block signature')

Is it necessary to verify Signature and blockhash in method from_dict()? And in models.py:210 of method validate(self, bigchain)
        if not self.is_signature_valid():
            raise InvalidSignature('Block signature invalid')

verify Signature again..

Sorry, typesetting and English are not very good...

Hi @CsterKuroi, thanks for raising this issue! We'll look into it as soon as possible!
/cc @r-marques

@CsterKuroi you are right.
I created issues to address different points that you mentioned:

[ ] 1. will be addressed in #1132
[ ] 2. is already being addressed in #1130
[ ] 3. will be addressed in #1133

I will leave this issue open until all other issues are resolved

I will close this since all the issues have been resolved.
One thing to note about 3. is that we still do the id validation on the from_dict. The reason for this is that its only place where we have access to the actual json payload. After that Block.id is just a property that is dynamically calculated every time its called.


Since version 2.9.0, APIs with @PathVariable are not picked up anymore due to Spring 4.3.3 code

In our project we are currently using spring 4.2.X and we recently upgraded to version 2.9.0 of this library. After upgrading we discovered that some of our APIs didn't appear anymore. After some digging, we discovered that an error was thrown and then caught which made troubleshooting difficult.
The issue is in the ParameterRequiredReader class
It's using fields in the PathVariable annotation that was introduced in Spring 4.3.3. Using a lower Spring version triggers a "MethodNotFound" exception. In our case, upgrading Spring is not an option.
As a work around, we have extended the offending class, modified the code. Then we told Spring to use ours as Primary. So we got it currently working.
There's a way for the code to do the same thing but without breaking compatibility
This:
Optional<PathVariable> pathVariable = methodParameter.findAnnotation(PathVariable.class);
    if (pathVariable.isPresent()) {
      String paramName = MoreObjects.firstNonNull(
          emptyToNull(pathVariable.get().name()),
          methodParameter.defaultName().orNull());
      if (pathVariable.get().required() ||
          optionalButPresentInThePath(operationContext, pathVariable.get(), paramName)) {
        requiredSet.add(true);
      }
    }

Could become this:
Optional<PathVariable> pathVariable = methodParameter.findAnnotation(PathVariable.class);
    if (pathVariable.isPresent()) {
      Map<String, Object> attributes = AnnotationUtils.getAnnotationAttributes(pathVariable.get());
      String paramName = MoreObjects.firstNonNull(
          emptyToNull((String) attributes.get("name")),
          methodParameter.defaultName().orNull());

      boolean required = !attributes.containsKey("required") || (Boolean) attributes.get("required");
      if (required ||
          optionalButPresentInThePath(operationContext, paramName)) {
        requiredSet.add(true);
      }
    }

Then this:
private boolean optionalButPresentInThePath(
      OperationContext operationContext,
      PathVariable pathVariable,
      String paramName) {

    return !pathVariable.required()
         && operationContext.requestMappingPattern().contains("{" + paramName + "}");
  }

To This:
private boolean optionalButPresentInThePath(
          OperationContext operationContext,
          String paramName) {

    return operationContext.requestMappingPattern().contains("{" + paramName + "}");
  }

AnnotationUtils is present for Spring since early version and certainly present in all of 4.X versions. That utility class contains a method to get all annotation attributes as a Map. In this case, it's useful to make some annotation changes backwards compatible like in this case.

Happy to take a PR for that. You can use the convenience method offered via the spring capabilities utility class


Add-on don't start

Govee Device SKU
H61E1; H6056; H6076
Govee2MQTT Version
2024.04.29-30cf7732
Describe the issue
Recently I can no longer start the add-on. When I start it, the dot turns green for a moment and the CPU load increases. If I reload the page or come back to the add-on later, the dot is red again and the add-on does not run.
Startup Diagnostics
18: std::panicking::try::do_call
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
19: std::panicking::try
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
20: std::panic::catch_unwind
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
21: std::rt::lang_start_internal
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:20
22: main
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_TEMPERATURE_SCALE=C
GOVEE_EMAIL=REDACTED
++ cd /app
++ exec /app/govee serve
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
[2024-06-15T04:00:42 INFO  govee::commands::serve] Starting service. version 2024.04.29-30cf7732
[2024-06-15T04:00:42 INFO  govee::commands::serve] Querying platform API for device list
[2024-06-15T04:00:42 INFO  govee::commands::serve] Querying undocumented API for device + room list
Error: error sending request for url (https://app2.govee.com/account/rest/account/v1/login): error trying to connect: dns error: failed to lookup address information: Try again: error trying to connect: dns error: failed to lookup address information: Try again: dns error: failed to lookup address information: Try again: failed to lookup address information: Try again
Stack backtrace:
0: anyhow::error::::msg
1: anyhow::__private::format_err
2: govee::cache::CacheResult::into_result
3: govee::cache::cache_get::{{closure}}
4: govee::undoc_api::GoveeUndocumentedApi::login_account_cached::{{closure}}
5: govee::commands::serve::ServeCommand::run::{{closure}}
6: govee::Args::run::{{closure}}
7: tokio::runtime::park::CachedParkThread::block_on
8: tokio::runtime::context::runtime::enter_runtime
9: tokio::runtime::runtime::Runtime::block_on
10: govee::main
11: std::sys_common::backtrace::__rust_begin_short_backtrace
12: std::rt::lang_start::{{closure}}
13: core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:284:13
14: std::panicking::try::do_call
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
15: std::panicking::try
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
16: std::panic::catch_unwind
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
17: std::rt::lang_start_internal::{{closure}}
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:48
18: std::panicking::try::do_call
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
19: std::panicking::try
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
20: std::panic::catch_unwind
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
21: std::rt::lang_start_internal
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:20
22: main
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_TEMPERATURE_SCALE=C
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-06-15T04:05:09 INFO  govee::commands::serve] Starting service. version 2024.04.29-30cf7732
[2024-06-15T04:05:09 INFO  govee::commands::serve] Querying platform API for device list
Additional Logs
No response
Home Assistant Logs
No response
Anything else?
No response

...same here.
has someone figuered out, how to reboot this integration in an automation??

I am also having this problem:
's6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_TEMPERATURE_SCALE=F
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=MQTT
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-07-02T13:52:39 INFO  govee::commands::serve] Starting service. version 2024.04.29-30cf7732
[2024-07-02T13:52:39 INFO  govee::commands::serve] Querying platform API for device list
[2024-07-02T13:52:39 WARN  govee::cache] request https://openapi.api.govee.com/router/api/v1/user/devices status 401: Unauthorized. Response body: , will use prior results
Error: request https://openapi.api.govee.com/router/api/v1/user/devices status 401: Unauthorized. Response body:
Stack backtrace:
0: anyhow::error::::msg
1: anyhow::__private::format_err
2: govee::cache::CacheResult::into_result
3: govee::platform_api::GoveeApiClient::get_devices::{{closure}}
4: govee::commands::serve::ServeCommand::run::{{closure}}
5: govee::Args::run::{{closure}}
6: tokio::runtime::park::CachedParkThread::block_on
7: tokio::runtime::context::runtime::enter_runtime
8: tokio::runtime::runtime::Runtime::block_on
9: govee::main
10: std::sys_common::backtrace::__rust_begin_short_backtrace
11: std::rt::lang_start::{{closure}}
12: core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:284:13
13: std::panicking::try::do_call
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
14: std::panicking::try
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
15: std::panic::catch_unwind
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
16: std::rt::lang_start_internal::{{closure}}
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:48
17: std::panicking::try::do_call
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
18: std::panicking::try
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
19: std::panic::catch_unwind
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
20: std::rt::lang_start_internal
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:20
21: main
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped'

I am affected by this as well.
   2: govee::cache::CacheResult<T>::into_result
   3: govee::platform_api::GoveeApiClient::get_devices::{{closure}}
   4: govee::commands::serve::ServeCommand::run::{{closure}}
   5: govee::Args::run::{{closure}}
   6: tokio::runtime::park::CachedParkThread::block_on
   7: tokio::runtime::context::runtime::enter_runtime
   8: tokio::runtime::runtime::Runtime::block_on
   9: govee::main
  10: std::sys_common::backtrace::__rust_begin_short_backtrace
  11: std::rt::lang_start::{{closure}}
  12: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:284:13
  13: std::panicking::try::do_call
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
  14: std::panicking::try
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
  15: std::panic::catch_unwind
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
  16: std::rt::lang_start_internal::{{closure}}
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:48
  17: std::panicking::try::do_call
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
  18: std::panicking::try
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
  19: std::panic::catch_unwind
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
  20: std::rt::lang_start_internal
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:20
  21: main
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_TEMPERATURE_SCALE=F
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-07-04T10:59:52 INFO  govee::commands::serve] Starting service. version 2024.04.29-30cf7732
[2024-07-04T10:59:52 INFO  govee::commands::serve] Querying platform API for device list
[2024-07-04T10:59:53 INFO  govee::commands::serve] Querying undocumented API for device + room list
Error: request https://app2.govee.com/account/rest/account/v1/login status 200: OK: parsing https://app2.govee.com/account/rest/account/v1/login response: Failed with status 400 Bad Request Bad Request: Request to https://app2.govee.com/account/rest/account/v1/login failed with code 400 Bad Request Incorrect password. Full response: {"status":400,"message":"Incorrect password"}

Stack backtrace:
   0: anyhow::error::<impl anyhow::Error>::msg
   1: anyhow::__private::format_err
   2: govee::cache::CacheResult<T>::into_result
   3: govee::cache::cache_get::{{closure}}
   4: govee::undoc_api::GoveeUndocumentedApi::login_account_cached::{{closure}}
   5: govee::commands::serve::ServeCommand::run::{{closure}}
   6: govee::Args::run::{{closure}}
   7: tokio::runtime::park::CachedParkThread::block_on
   8: tokio::runtime::context::runtime::enter_runtime
   9: tokio::runtime::runtime::Runtime::block_on
  10: govee::main
  11: std::sys_common::backtrace::__rust_begin_short_backtrace
  12: std::rt::lang_start::{{closure}}
  13: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:284:13
  14: std::panicking::try::do_call
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
  15: std::panicking::try
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
  16: std::panic::catch_unwind
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
  17: std::rt::lang_start_internal::{{closure}}
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:48
  18: std::panicking::try::do_call
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
  19: std::panicking::try
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
  20: std::panic::catch_unwind
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
  21: std::rt::lang_start_internal
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:20
  22: main
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

I am affected by this as well.
   2: govee::cache::CacheResult<T>::into_result
   3: govee::platform_api::GoveeApiClient::get_devices::{{closure}}
   4: govee::commands::serve::ServeCommand::run::{{closure}}
   5: govee::Args::run::{{closure}}
   6: tokio::runtime::park::CachedParkThread::block_on
   7: tokio::runtime::context::runtime::enter_runtime
   8: tokio::runtime::runtime::Runtime::block_on
   9: govee::main
  10: std::sys_common::backtrace::__rust_begin_short_backtrace
  11: std::rt::lang_start::{{closure}}
  12: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:284:13
  13: std::panicking::try::do_call
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
  14: std::panicking::try
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
  15: std::panic::catch_unwind
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
  16: std::rt::lang_start_internal::{{closure}}
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:48
  17: std::panicking::try::do_call
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
  18: std::panicking::try
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
  19: std::panic::catch_unwind
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
  20: std::rt::lang_start_internal
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:20
  21: main
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_TEMPERATURE_SCALE=F
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-07-04T10:59:52 INFO  govee::commands::serve] Starting service. version 2024.04.29-30cf7732
[2024-07-04T10:59:52 INFO  govee::commands::serve] Querying platform API for device list
[2024-07-04T10:59:53 INFO  govee::commands::serve] Querying undocumented API for device + room list
Error: request https://app2.govee.com/account/rest/account/v1/login status 200: OK: parsing https://app2.govee.com/account/rest/account/v1/login response: Failed with status 400 Bad Request Bad Request: Request to https://app2.govee.com/account/rest/account/v1/login failed with code 400 Bad Request Incorrect password. Full response: {"status":400,"message":"Incorrect password"}

Stack backtrace:
   0: anyhow::error::<impl anyhow::Error>::msg
   1: anyhow::__private::format_err
   2: govee::cache::CacheResult<T>::into_result
   3: govee::cache::cache_get::{{closure}}
   4: govee::undoc_api::GoveeUndocumentedApi::login_account_cached::{{closure}}
   5: govee::commands::serve::ServeCommand::run::{{closure}}
   6: govee::Args::run::{{closure}}
   7: tokio::runtime::park::CachedParkThread::block_on
   8: tokio::runtime::context::runtime::enter_runtime
   9: tokio::runtime::runtime::Runtime::block_on
  10: govee::main
  11: std::sys_common::backtrace::__rust_begin_short_backtrace
  12: std::rt::lang_start::{{closure}}
  13: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:284:13
  14: std::panicking::try::do_call
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
  15: std::panicking::try
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
  16: std::panic::catch_unwind
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
  17: std::rt::lang_start_internal::{{closure}}
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:48
  18: std::panicking::try::do_call
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
  19: std::panicking::try
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
  20: std::panic::catch_unwind
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
  21: std::rt::lang_start_internal
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:20
  22: main
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

After changing my password twice, I was able to get the add-on to start.

Experiencing a similar issue:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_TEMPERATURE_SCALE=C
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-07-31T00:12:23 INFO  govee::commands::serve] Starting service. version 2024.07.13-82ddc6e9
[2024-07-31T00:12:23 INFO  govee::commands::serve] Querying platform API for device list
[2024-07-31T00:13:23 WARN  govee::cache] error sending request for url (https://openapi.api.govee.com/router/api/v1/user/devices): operation timed out, will use prior results
Error: error sending request for url (https://openapi.api.govee.com/router/api/v1/user/devices): operation timed out

Stack backtrace:
   0: anyhow::error::<impl anyhow::Error>::msg
   1: anyhow::__private::format_err
   2: govee::cache::CacheResult<T>::into_result
   3: govee::platform_api::GoveeApiClient::get_devices::{{closure}}
   4: govee::commands::serve::ServeCommand::run::{{closure}}
   5: govee::Args::run::{{closure}}
   6: tokio::runtime::park::CachedParkThread::block_on
   7: tokio::runtime::context::runtime::enter_runtime
   8: tokio::runtime::runtime::Runtime::block_on
   9: govee::main
  10: std::sys_common::backtrace::__rust_begin_short_backtrace
  11: std::rt::lang_start::{{closure}}
  12: std::rt::lang_start_internal
  13: main
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Experiencing a similar issue:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_TEMPERATURE_SCALE=C
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-07-31T00:12:23 INFO  govee::commands::serve] Starting service. version 2024.07.13-82ddc6e9
[2024-07-31T00:12:23 INFO  govee::commands::serve] Querying platform API for device list
[2024-07-31T00:13:23 WARN  govee::cache] error sending request for url (https://openapi.api.govee.com/router/api/v1/user/devices): operation timed out, will use prior results
Error: error sending request for url (https://openapi.api.govee.com/router/api/v1/user/devices): operation timed out

Stack backtrace:
   0: anyhow::error::<impl anyhow::Error>::msg
   1: anyhow::__private::format_err
   2: govee::cache::CacheResult<T>::into_result
   3: govee::platform_api::GoveeApiClient::get_devices::{{closure}}
   4: govee::commands::serve::ServeCommand::run::{{closure}}
   5: govee::Args::run::{{closure}}
   6: tokio::runtime::park::CachedParkThread::block_on
   7: tokio::runtime::context::runtime::enter_runtime
   8: tokio::runtime::runtime::Runtime::block_on
   9: govee::main
  10: std::sys_common::backtrace::__rust_begin_short_backtrace
  11: std::rt::lang_start::{{closure}}
  12: std::rt::lang_start_internal
  13: main
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Update, working again as of today. Might have been an internal Govee API issue.


composer migration:migrate: There are no commands defined in the "migration" namespace

I'm having an issue installing via composer on my CentOS 7...
On the last step of "Step 4: Configuration", when I run
composer migration:migrate
I get an error:
"[Symfony\Component\Console\Exception\CommandNotFoundException]
There are no commands defined in the "migration" namespace."
Thanks!
-Joe
Edit: I just noticed I'm using PHP version 7.2.34, where in your docs you say minimum 7.3... Could this be the issue?

Yes this could be the issue. Because of phpunit 9 the minimum version has been changed to 7.3. See composer.json. So even composer update should fail when using PHP 7.2 and lower.
You could solve this issue by downgrading the phpunit version to v8. Open composer.json and change "phpunit/phpunit": "^9", to "phpunit/phpunit": "^8". Then run composer update and try it again.

Yes this could be the issue. Because of phpunit 9 the minimum version has been changed to 7.3. See composer.json. So even composer update should fail when using PHP 7.2 and lower.
You could solve this issue by downgrading the phpunit version to v8. Open composer.json and change "phpunit/phpunit": "^9", to "phpunit/phpunit": "^8". Then run composer update and try it again.

Wow, I think this is the fastest issue response I've ever got, thanks!
The composer.json phpunit is set to 8 already?:
"require-dev": { ...         "phpunit/phpunit": "^7 || ^8", ...     },
Also, I never had an issue installing because the the minimum php is 7.2:
"require": {         "php": "^7.2", ...     },
I hope I didn't install the wrong slim4-skeleton?
Thanks!

Wow, I think this is the fastest issue response I've ever got, thanks!
The composer.json phpunit is set to 8 already?:
"require-dev": { ...         "phpunit/phpunit": "^7 || ^8", ...     },
Also, I never had an issue installing because the the minimum php is 7.2:
"require": {         "php": "^7.2", ...     },
I hope I didn't install the wrong slim4-skeleton?
Thanks!

Ok, it looks you have installed v0.14.0 (or older) of the slim4-skeleton. The latest version is v0.16.0, which requires PHP 7.3+ or 8.0. So the PHP version should not be the issue here. In version 0.15.0 the composer commands has been renamed. See here.
You can find all composer scripts in composer.json. I guess in your specific version the command
should be composer phinx:migrate

Ok, it looks you have installed v0.14.0 (or older) of the slim4-skeleton. The latest version is v0.16.0, which requires PHP 7.3+ or 8.0. So the PHP version should not be the issue here. In version 0.15.0 the composer commands has been renamed. See here.
You can find all composer scripts in composer.json. I guess in your specific version the command
should be composer phinx:migrate

Thanks! I couldn't find the version I'm using, but I changed to phinx and it installed correctly!
It did have an error:
Invalid migration file /var/www/sites/game.box.biz/resources/migrations/schema.php
Also, when I go to the site and login as admin:admin, I get this JS alert error:
DataTables warning: table id=data-table - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1
Being I used the newest instructions to install this, perhaps I missed something?
Please feel free to just close this issue as fixed and I'll try and figure out this alert error separately.
Thanks again! Great library!

Thanks! I couldn't find the version I'm using, but I changed to phinx and it installed correctly!
It did have an error:
Invalid migration file /var/www/sites/game.box.biz/resources/migrations/schema.php
Also, when I go to the site and login as admin:admin, I get this JS alert error:
DataTables warning: table id=data-table - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1
Being I used the newest instructions to install this, perhaps I missed something?
Please feel free to just close this issue as fixed and I'll try and figure out this alert error separately.
Thanks again! Great library!

It looks like there was a change in phinx. The file schema.php never caused such an issue as far as I know. This looks like a bug to me. I fixed it in the latest version of the project. See changelog here.
It can be solved by moving the schema.php out of the resources/migrations directory to resources/schema.
Then open config/phinx.php and add this key:
$phinx['environments']['local'] = [
    // ...
    'schema_file' => __DIR__ . '/../resources/schema/schema.php',
    // ...
];

It looks like there was a change in phinx. The file schema.php never caused such an issue as far as I know. This looks like a bug to me. I fixed it in the latest version of the project. See changelog here.
It can be solved by moving the schema.php out of the resources/migrations directory to resources/schema.
Then open config/phinx.php and add this key:
$phinx['environments']['local'] = [
    // ...
    'schema_file' => __DIR__ . '/../resources/schema/schema.php',
    // ...
];


Address look ahead not working for POIs

When defining a new destination address, only google addresses are returned.
Expectation: when the name of a poi is entered, the POIs address shall be returned. AAZ is a POI in Basel, located at Petersgraben 4.

Fixed the database, the FULLTEXT statements have been removed in October 2014.
Now it's working again (example):


Automation testing

This PR implements the framework to read files from /test/ui folder and run test cases on it. It reads the files generated selenium test recorder

test


Clicking on next/previous month clears data from the calendar.

Hey guys,
Am having as issue with ui-calendar,when i click on next/previous month,it clears all the events from the calendar,however the data is still available on my model.
Anybody faced the same issue?

That's an FAQ. Look at the fullcalendar docs, event properties, stick.


Document and organize assemblies of materials for commercial template model

Documentation, remember to put our information in a write-up


Replace W1D1 tutorials to pick up fixed workflow processing

This diff looks fine on the surface, but it changes almost all the content in the .ipynb file - is that normal?

I'm not sure what the "outputId" metadata that Colab adds is used for. But I imagine it's some kind of unique ID that is generated anew every time the cell is executed?


Error message on duplicate name is confusing

Below is an example of an error that seems to be a red herring, whereas associated warnings reveal the finer details. When there are other errors & warnings, the duplication error will have other content separating it from the associated warnings. This led to some confusion when developing.
It would be preferred if the warnings were turned into error messages (perhaps deduplicated since one is the other backwards ie "30:7 has same definition as 30:1" & "30:1 has same definition as 30:7"). This is indeed a compilation error, and a warning seems inappropriate.
The error message which refers to the context that contains the duplication seems superfluous - perhaps it can be combined with the warnings, but maybe it is not necessary at all. I will leave that up to the discretion of RIDDL developers.
[warning] Warning: tenantMessages.riddl(30:7): Event 'TenantSuspended' has same name as other definitions in Event 'TenantSuspended' at tenantMessages.riddl(30:1):  Event 'TenantSuspended' at tenantMessages.riddl(44:1):
event TenantSuspended is {
      ^
[warning] Warning: tenantMessages.riddl(30:7): Event 'TenantSuspended' has same name as other definitions in Event 'TenantSuspended' at tenantMessages.riddl(30:1):  Event 'TenantSuspended' at tenantMessages.riddl(44:1):
event TenantSuspended is {
      ^
[info] Errors: 1
[error] Error: tenant.riddl(4:1): Context 'TenantContext' has duplicate content names:

:
context TenantContext is {
^
[info] Severe Errors: 0

Example RIDDL to replicate:
domain Example is {
	context ErrorsToDemonstrateClutter{
		type IntentionalErrors {
      garbage: Blah,
      moreGarbage: BlahBlah
    }
	}
	context ExampleContext is {
		type Foo {
	    name: String
	   }

    type Foo {
     number: Integer
    }
	}
	context WarningsToDemonstrateClutter{
		type Bar is {}
		source UnusedWarningSource is {
        outlet Unused is type Bar
    }
    source SecondUnusedWarningSource is {
        outlet Unused is type Bar
    }
	}
}

Compilation warnings & errors from example RIDDL above:
[info] Warnings: 4
[warning] Warning: example.riddl(9:8): Type 'Foo' has same name as other definitions in Type 'Foo' at example.riddl(9:3):  Type 'Foo' at example.riddl(13:5):
                type Foo {
       ^
[warning] Warning: example.riddl(9:8): Type 'Foo' has same name as other definitions in Type 'Foo' at example.riddl(9:3):  Type 'Foo' at example.riddl(13:5):
                type Foo {
       ^
[warning] Warning: example.riddl(20:9): Outlet 'Unused' is not connected:
        outlet Unused is type Bar
        ^
[warning] Warning: example.riddl(23:9): Outlet 'Unused' is not connected:
        outlet Unused is type Bar
        ^
[info] Errors: 3
[error] Error: example.riddl(4:16): Path 'Blah' was not resolved, in Field 'garbage', but should refer to a Type:
      garbage: Blah,
               ^
[error] Error: example.riddl(5:20): Path 'BlahBlah' was not resolved, in Field 'moreGarbage', but should refer to a Type:
      moreGarbage: BlahBlah
                   ^
[error] Error: example.riddl(8:2): Context 'ExampleContext' has duplicate content names:

:
        context ExampleContext is {
 ^
[info] Severe Errors: 0


[Bug] Issue with Saving to Config and Scoreboard Persistence

I have encountered an issue with version v1.14 of EasyEvent. Specifically, the plugin does not correctly save settings to the config and the scoreboard settings do not persist after server restart. Below are the details of the issue:
Bug Description:
Config Saving Issue:
Changes made to the event settings (e.g., prize, player count) do not persist after restarting the server. The config file does not store the updated values properly, causing these settings to reset each time the server restarts.
Scoreboard Persistence:
After enabling the scoreboard (/event lb on), the settings (like the player count and event prize) are displayed correctly. However, when the server is restarted, the scoreboard does not update to reflect the new settings.
 This resets the scoreboard correctly, but the settings (like player count) are still not saved properly to the config file.

I will prioritize adding the functionality to save event settings (such as prize and player count) to the config file so that they persist after a server restart. Additionally, I will work on ensuring that the scoreboard settings are correctly updated and saved.
I plan to address this as soon as I have time to implement the changes. I appreciate your patience and will update you when a fix is available in the next release!
(Illustrative example)


Add allKeyExists tests

Closes #46 by showing that this has been fixed already. I think. If wrong - maybe somebody can point me in the direction to reproduce it to create  a failing test?

Can you bisect when this was fixed and why it didn't work on April 23rd? (The date on the original issue.) Basically I want you to find the commit where the test still fails, thanks.

Strange, same result on all 0.12.8 (Dec 20), 0.12.9, 0.12.10, 0.12.11, 0.12.12 (Jan) and 0.12.13 (July). I get
 ------ ---------------------------------------------------------------
  Line   foo.php
 ------ ---------------------------------------------------------------
  13     Dumped type: array<array('id' => int)>
  17     Dumped type: array<int, array<string, mixed>&hasOffset('id')>
  21     Dumped type: array<array&hasOffset('id')>
 ------ ---------------------------------------------------------------

Same thing by requiring the same version of phpstan that was reported (0.12.84)
Can this be something else? Not sure what else could be checked if I can't even find the "bad" state basically 🤔

No idea, but issue needs to be reproduced before we can consider it fixed.

@waltertamboer it's been a while since you opened the issue, but do you maybe still know more about it?

There's now a conflict in this PR, please rebase, thanks.

Thank you.

Sorry @herndlm - Missed the notifications, good job :+1:

@waltertamboer no worries, I did not fix anything here though. I just added a test that shows that it seems to be working fine right now. And I was not able to find out why or when it was broken.
Please let us know if the original issue is still relevant!


List of illegal characters

Issue in ./help/sources/tutorials/ui/create/local-system/local-file-upload.md
Customers have run into issues uploading files with illegal characters or column headings.
Can we outline here what characters are considered illegal for both field values and names?

Thank you for submitting this issue. We will review the documentation and make the necessary updates as quickly as possible. Tracking internally in PLAT-134247.


feat: Custom attributes

Context:
Currently, RUM Web Client does not provide a mechanism to add custom attributes (data in the form of <key, value> pairs) to RUM events. This is problematic because users want to add attributes in addition to the default attributes provided by the RUM event schemas for better data analysis when querying or using the RUM console.
Changes:
This PR addresses the problem by doing the following:

Allow the web client to accept session attributes during initialization.
Allow the web client to accept session attributes during runtime through the new addSessionAttributes API.
Allow the web client to accept page attributes during runtime through the existing recordPageViews API.

Invalid custom attributes will be excluded from the event metadata. Custom attributes will be validated to check:
a. Invalid key length
b. Invalid value length
c. Invalid key chars
d. Total number of custom attributes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Duplicate of https://github.com/aws-observability/aws-rum-web/pull/177


problem ssr with api and nuxt content

Describe the feature
Hello, how are you
I am working on a project and testing the project on static hosting.
In the project, I am using "api" and nuxt content
The problem is with: ssr
1- When you are in a situation: true
Which is the default setting: nuxt content does not run when npm run generate and exactly all articles or .md files are never generated and an error appears that there is nothing.
2- When you are in: false
Which is the recommended mode for static plugins, the problem here is with the api and I am saving the json files inside /public/api, and when npm run generate the articles in nuxt content appear but the api data is not present
The problem is between content and api and inverted in each case of ssr
Additional information

[ ] Would you be willing to help implement this feature?
[ ] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

You can use routeRules:
export default defineNuxtConfig({
  routeRules: {
    '/**': { ssr: false }
  }
})

(This route rule only applies to Nuxt and will disable HTML generation for Vue pages.)
However, I would strongly advise that you enable SSR even for static hosting - I do not know where that recommendation came from but it is certainly not mine.


python-onvif doesn't work with python 3

I have a program that works fine with python 2.7
If I try to start this, I get an error message:

from types import InstanceType
ImportError: cannot import name 'InstanceType'

Does some plan to convert the onvif module to python 3?
Best regard
Bernd

Need python 3 version, anything else is just ridiculous.

Please feel free to check the fork https://github.com/FalkTannhaeuser/python-onvif-zeep
I replaced the SOAP client suds (https://pypi.python.org/pypi/suds, Python 2 only and not longer maintained) by zeep (http://docs.python-zeep.org). Although not yet perfect, it works now both with Python 2 and Python 3.


New skills to be added for card editing!

Skill name: Skill Boost
Description: Every - seconds: there is a -% chance that currently active skills will be boosted for - seconds.
Example: https://starlight.kirara.ca/char/223#c_200377_head

Skill name: Cute Focus
Description: Every - seconds there is a -% chance that when there are only Cute idols on the team, you will gain an extra -% combo bonus, and Perfect notes will receive a -% score bonus for - seconds.
Example: https://starlight.kirara.ca/char/164#c_100371_head

Leader skill name: Cute Princess
Description: When there are only cute idols on the team, all appeal stats will be raised by -% for all idols.
Example: https://starlight.kirara.ca/char/164#c_100371_head

Also it might be safe to say that Cool and Passion versions of these skills and leader skills will appear in the future, so maybe it'd be a good idea to add them for now so we don't bombard them on you later.

Skill name: Passion Focus
Description: Every - seconds there is a -% chance that when there are only Passion idols on the team, you will gain an extra -% combo bonus, and Perfect notes will receive a -% score bonus for - seconds.
Leader skill name: Passion Princess
Description: When there are only Passion idols on the team, all appeal stats will be raised by -% for all idols.
Example: https://starlight.kirara.ca/char/247#c_300377_head

Skill name: Cool Focus
Description: Every - seconds there is a -% chance that when there are only Cool idols on the team, you will gain an extra -% combo bonus, and Perfect notes will receive a -% score bonus for - seconds.
Leader skill name: Cool Princess
Description: When there are only Cool idols on the team, all appeal stats will be raised by -% for all idols.
Posting for cool ahead of time since it'll be the same when it gets added in game.