Invalid default value for 'created_at'

I was getting this error when using $table->timestamps() in a migration:

SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for 'created_at' (SQL: create table vehicles (id int unsigned not null auto_increment primary key, name varchar(255) not null, code varchar(255) not null, description text not null, capacity int not null, company_id int not null, created_at timestamp default 0 not null, updated_at timestamp default 0 not null) default character set utf8 collate utf8_unicode_ci)

with a MySQL backend. Turns out it's because I had NO_ZERO_DATE enabled. This actually makes sense though: created_at should either always contain a valid date, or it needs to be nullable. 0 does not make sense.
I think a more sensible default is this:
public function timestamps()
{
    $this->timestamp('created_at')->default(DB::raw('CURRENT_TIMESTAMP'));
    $this->timestamp('updated_at')->default(DB::raw('CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP'));
}

But it only works on MySql 5.6+, I believe (you're only allowed one CURRENT_TIMESTAMP prior to that, for whatever reason). In which case maybe we should make created_at default to CURRENT_TIMESTAMP and updated_at be nullable? I'm just starting to learn Laravel, I'm not sure if updated_at is intended to start out blank and be updated after the first modify, or always contain a value.

This is due to MySQL not accepting zero as a valid defalt date and thus the table creation fails a constraint check on creation.
You probably have NO_ZERO_DATE enabled in your MySQL configuration. Setting this to off will allow you to create the table (or alternatively remove the default 0 value or change it to CURRENT_TIMESTAMP.

@kingpabel Did you read my initial post? That's exactly what I said. Disabling NO_ZERO_DATE is not a good solution - dates should never be 0, why would I allow it?
Only way to properly fix is to override the blue print class and fix the timestamps() method. I don't know why Laravel's default behavior is to punish us for using strict settings.

I also encountered this issue. I'm thinking about using:
$table->timestamp('created_at');
$table->timestamp('updated_at');

Instead of $table->timestamps();
What do you guys think?

The issue popped up again with the newest version of Homestead. I guess the new version of MySQL shipped with it has different settings than in previous Homestead versions.

Are you inserting records with no time stamp?
On Sun, Nov 15, 2015 at 5:45 AM, Michaël Lecerf<EMAIL_ADDRESS>wrote:

The issue popped up again with the newest version of Homestead. I guess the new version of MySQL shipped with it has different settings than in previous Homestead versions.
Reply to this email directly or view it on GitHub:
https://github.com/laravel/framework/issues/3602#issuecomment-156806583

The exception is thrown when creating the table itself, before inserting any data.
This happens because the default value for timestamp fields is set to be 0.
Example of a crashing migration:
// ...

public function up()
{
    Schema::create('users', function(Blueprint $table)
    {
        $table->increments('id');
        $table->string('email')->unique()->nullable();
        $table->string('name');
        $table->timestamps();// This line causes the issue.
        $table->softDeletes();
    });
}

//...

The error that is thrown when running it:
[Illuminate\Database\QueryException]
SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for 'created_at'
(SQL: create table `users` (
    `id` int unsigned not null auto_increment primary key,
    `email` varchar(255) null,
    `name` varchar(255) not null,
    `created_at` timestamp default 0 not null,
    `updated_at` timestamp default 0 not null,
    `deleted_at` timestamp null
) default character set utf8 collate utf8_unicode_ci)

Laravel 5.1.8, running on the latest Homestead version (v0.3.3).

Hmm, I'm having trouble recreating this on the latest Homestead. I can run
the default user migration fine and insert data.
On Sun, Nov 15, 2015 at 12:15 PM, Michaël Lecerf<EMAIL_ADDRESS>wrote:

The exception is thrown when creating the table itself, before inserting
any data.
This happens because the default value for timestamp fields is set to be 0.
Example of a crashing migration:
// ...public function up(){    Schema::create('users', function(Blueprint $table)    {        $table->increments('id');        $table->string('email')->unique()->nullable();        $table->string('name');        $table->timestamps();// This line causes the issue.        $table->softDeletes();    });}//...
The error that is thrown when running it:
[Illuminate\Database\QueryException]
SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for 'created_at'
(SQL: create table users (
id int unsigned not null auto_increment primary key,
email varchar(255) null,
name varchar(255) not null,
created_at timestamp default 0 not null,
updated_at timestamp default 0 not null,
deleted_at timestamp null
) default character set utf8 collate utf8_unicode_ci)
Laravel 5.1.8, running on the latest Homestead version (v0.3.3).
—
Reply to this email directly or view it on GitHub
https://github.com/laravel/framework/issues/3602#issuecomment-156841038.

Weird. I'm running into this same issue when trying to run migrations after updating Homestead to 0.3.3 with Laravel 5.0.16
SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for 'created_at'

I have the exact same issue since installing Homestead yesterday...
Looks like this has been a problem before, http://stackoverflow.com/a/30555920
Would love to see this fixed or made as a comment in the documentation that you should be wary for this and maybe change the setting mentioned in the stackoverflow answer for the Homestead boxes!?

Hmm, I'm having trouble recreating this on the latest Homestead. I can run the default user migration fine and insert data.

It also works for me on a blank Laravel install (5.1.24). The two default migrations run without any problem and create the tables in the homestead database. Weird.
Did you tweak anything in MySQL’s configuration on your own Homestead instance? As far as I get it, the issue seems related to this SQL mode (NO_ZERO_DATE). Which is deprecated in the latest MySQL versions (such as the one shipped with the latest Homestead box).

Ah, I have found the issue, probably.
My "old" database.php config file does not have strict set to false ('strict' => false) as laravel/laravel does.
When I add that line to the mysql config migrations work just fine...

@Stayallive
Wow. Doing exactly the opposite seems to fix the issue on my side. This setting was already set to false (its default value) and switching it to true allows my migrations to run without any problem.
Now I don’t understand anything any more…

Wait wut... this is not the Laravel magic I heard about 😜

I have the same problem after upgrade. My solution:

use nullableTimestamps() instead of timestamps()
for custom timestamps add nullable , ex:  timestamp('xxxx')->nullable()

It's deprecated but included as part of strict mode.
Laravel should be strict compliant by default.
On Nov 16, 2015 12:31 PM, "Michaël Lecerf"<EMAIL_ADDRESS>wrote:

Hmm, I'm having trouble recreating this on the latest Homestead. I can run
the default user migration fine and insert data.
It also works for me on a blank Laravel install (5.1.24). The two default
migrations run without any problem and create the tables in the homestead
database. Weird.
Did you tweak anything in MySQL’s configuration on your own Homestead
instance? As far as I get it, the issue seems related to this SQL mode
https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sqlmode_no_zero_date
(NO_ZERO_DATE). Which is deprecated in the latest MySQL versions (such as
the one shipped with the latest Homestead box).
—
Reply to this email directly or view it on GitHub
https://github.com/laravel/framework/issues/3602#issuecomment-157160686.

Running into the same issue on an application built using Laravel 4.2.17 & laravel/homestead' (v0.3.3). I've tried adding the 'strict'=>false setting to the database config, but that doesn't seem to do the trick.

I just updated the Homestead, that is using MySQL 5.7.9, and got the same issue.

It's fixed in the very latest 5.1.x dev version atm.

It'll be available in 5.1.25 once it's released.

I see it's going to use default timestamp as the default. Wouldn't it be better to just skip default value entirely?

That's what the fix is I think.

It's fixed in the very latest 5.1.x dev version atm.

Any plan/possibility to backport a fix to 4.x and/or 5.0?

You could set explicit_defaults_for_timestamp to TRUE in your MySQL server configuration file.

I have set explicit_defaults_for_timestamp = TRUE in the my.cnf file and restarted the mysqld server, but I still get the same error, but when I set the config/database.php strict to true, this issue #3602 gets resolved and another (unrelated issue?) crops up.
Currently on Laravel 5.0.33

As @sorinstanila already mentioned, there also nullableTimestamps() method as a workaround for now.

Strict set to false fixed this for me. Thanks for the help.

From @uberbrady in https://github.com/snipe/snipe-it/issues/1303
MySQL released a new version of their docker container which runs in a more strict mode. If you specifically pick out a MySQL version running 5.6 or earlier, it won't happen. I'm updating documentation to note that.

Strict set to false fixed this for me. Any updates on a permanent fix?

There is no "permanent" fix other than either turning off strict mode or putting a valid time stamp on the column when you insert it.
On Mon, Nov 23, 2015 at 1:08 PM, Trevor Greenleaf
<EMAIL_ADDRESS>wrote:

Strict set to false fixed this for me. Any updates on a permanent fix?
Reply to this email directly or view it on GitHub:
https://github.com/laravel/framework/issues/3602#issuecomment-159030482

@taylorotwell Why don't you add a new method called currentTimestamps which has defaults as shown in my original query?
0 is not a good default because it doesn't work in strict mode/NO_ZERO_DATE and null doesn't work either if you want those columns to always be non-null.
I'd say you should update the base timestamps but multiple CURRENT_TIMESTAMPs doesn't work on older versions of MySQL, so for backwards compat I'd just make it a new method.

We already added a new helper ->useCurrent() but it may not be tagged yet.
On Mon, Nov 23, 2015 at 2:19 PM, Mark Penner<EMAIL_ADDRESS>wrote:

@taylorotwell Why don't you add a new method called currentTimestamps which has defaults as shown in my original query?
0 is not a good default because it doesn't work in strict mode/NO_ZERO_DATE and null doesn't work either if you want those columns to always be non-null.
I'd say you should update the base timestamps but multiple CURRENT_TIMESTAMPs doesn't work on older versions of MySQL, so for backwards compat I'd just make it a new method.
Reply to this email directly or view it on GitHub:
https://github.com/laravel/framework/issues/3602#issuecomment-159052364

Refs #10962 (then https://github.com/laravel/framework/commit/15c487fecc00c1a58837ce5692396fec78a5bd9d).
So, you have 3 sensible solutions:

Use ->nullable() in your database schema
Use ->useCurrent() if suitable (or even ->default(yourpick)…)
Specify a value when inserting row

Good catch about the multiple CURRENT_TIMESTAMP restriction.
This has been lifted only starting from MySQL 5.6…

@vlakoff Keep in mind that if you do nothing about the schema and just rely on inserting proper values, you won't be able to alter the table in any way. Any change in the structure, like adding/renaming/removing columns will throw the following error:  Invalid default value for 'some_column'.

I've edited my comment above to clarify this.

May this help?
sudo vi /etc/mysql/my.cnf
add (in [mysqld] section)
sql_mode="ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
restart
More info at http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html . The configuration above may depend on your mysql version.

@dbillionlabs You are suggesting a whole bunch of settings irrelevant to the topic. It's enough to just remove NO_ZERO_DATE mode. But still, this is kind of a workaround, having this mode on is very good idea allowing you to avoid invalid values.

@kokokurak Hello, as I didn't found a way to remove just two (NO_ZERO_IN_DATE, NO_ZERO_DATE) from my.cnf, what I've just copied are the default values for sql_mode in mysql 5.7 without these ones, as stated on the link
The default SQL mode in MySQL 5.7 includes these modes: ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION.

@dbillionlabs thanks for your hint. So I tried this and that's as far as I get (inside a laravel/homestead vagrant environment):
mysql> set sql_mode="ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION";
Query OK, 0 rows affected, 1 warning (0.00 sec)
After running php artisan platform:install the same error still shows up:
Error
*[PDOException] SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default val
ue for 'created_at'
What I haven't done is restarting the mysql-Server. Is that needed, and if so, how?
Thanks guys for digging into the research!

@hithereimhere try
SET GLOBAL sql_mode = 'modes';
but if it works for you know be aware next time mysql restarts you may lose the change, unless yoy modify mysql config file/s

@dbillionlabs thanks for the feedback, it tried it by setting it global and afterwards quit the mysql mode by \q
After that, the laravel-installer came up with the same error. So still no progress.
Some more ways came to my mind:

Is it possible to downgrade the mysql version (< 5.7) inside Laravel/Homestead? (Couldn't find anything on that)
Is it possible to re-install an older Version of Laravel/Homestad? (Couldn't find any infos about specific older versions running < mysql 5.7)
Is there an official announcement from the Laravel community with a general workaround/solution?

For me on all my apps the solution was to set strict to true in my MySQL config (in config/database.php).
    'connections' => [

        'simulise' => [

            'driver'    => 'mysql',
            'host'       => 'localhost',
            'database'  => env('DB_DATABASE', 'homestead'),
            'username'  => env('DB_USERNAME', 'homestead'),
            'password'  => env('DB_PASSWORD', 'secret'),
            'charset'   => 'utf8',
            'collation' => 'utf8_unicode_ci',
            'prefix'    => '',
            'strict'    => true

        ]

    ],

@Stayallive Sir, it looks like you saved my weekend.
One thing: I'm working with Cartalyst/Platform what worked for me:

setting 'strict'    => true in config/database.php
running the web-installer: (myapp.app/installer)

Info: Running php artisan platform:install from console didn't work for me. It somehow overwrites/ignores the strict settings from config/database.php, but maybe that was just in my case.
Thanks so much guys!

Yes, I also had this issue.
Solution was to set strict to true.
Worked fine now. Will have to remember that for each project as it only seems to affect our developers on homestead.

@Stayallive - Solution worked for my laravel 5.0 project
I just ran into this issue after setting up an existing 5.0 project on a new computer. After updating config/database.php, I was able to run migrations successfully using $ php artisan migrate:refresh --seed.
Thanks

Same issue here as well with 5.0. I had to recreate my homestead box and migration would fail on the new box. Choked on first migation which was the default user table. Setting the mysql driver to strict allowed me to run the migrations.

-> useCurrent() helper doesn't work on timestamps() ?

Having the same issue,
Here's my environment:
➜  project git:(master) ✗ php artisan --version
Laravel Framework version 5.1.26 (LTS)
➜  project git:(master) ✗ mysql --version
mysql  Ver 14.14 Distrib 5.7.10, for osx10.11 (x86_64) using  EditLine wrapper
➜  project git:(master) ✗ php -v
PHP 5.6.16 (cli) (built: Nov 28 2015 19:43:54)
Copyright (c) 1997-2015 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2015 Zend Technologies
```

Sequel pro gives me the same error by the way on the same created_at column.

I had the same problem.
SSH into vagrant
sudo vi /etc/mysql/my.cnf
add sql-mode="allow_invalid_dates"
save
sudo service nginx restart
works like a charm :)

As discussed in the MySQL docs for 5.7, MySQL 5.7.8+ enables NO_ZERO_DATE by default, but strict mode does not include NO_ZERO_DATE. Thus the workaround to enable strict mode really does work. However, it is only a temporary fix and will in the future cause the very same issues to return.
Thus the final, long-lasting solution will be to create your timestamp columns with $table->timestamp('created_at')->useCurrent(); followed by $table->timestamp('updated_at')->useCurrent(); instead of using $table->timestamps()

@GrahamCampbell @taylorotwell  - sorry - this is still broken on 5.1.28 on the current versions of Homestead and Forge installations (with the default mySQL 5.6 config that both use)
You can do a migration "ok".
But if you then run a mysqldump (which is common for backups) - then try and import that same SQL file into that same server (or another) - it will fail. This is important - because I just had to do an emergency migration - and the migration failed due to this issue.
The problem is only with $table->timestamps() because they are still creating a field of:
  `created_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
  `updated_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',

So I had to manually "find and replace" the contents of the SQL file and change them to this:
  `created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `updated_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,

I tested running a new migration on 5.1.28, then dumping the file, and trying to import, and the issue remains.

It sounds like you needed to turn off MySQL strict mode?
On Jan 24, 2016, 3:49 AM -0600, Laurence<EMAIL_ADDRESS>wrote:

@GrahamCampbell(https://github.com/GrahamCampbell)@taylorotwell(https://github.com/taylorotwell)- sorry - this is still broken on 5.1.28 on the current versions of Homestead and Forge installations (with the default mySQL 5.6 config that both use)
You can do a migration "ok".
But if you then run a mysqldump (which is common for backups) - then try and import that same SQL file into that same server (or another) - it will fail. This is important - because I just had to do an emergency migration - and the migration failed due to this issue.
The problem is only with$table->timestamps()because they are still creating a field of:
created_at timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',  updated_at timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
So I had to manually "find and replace" the contents of the SQL file and change them to this:
created_at timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,  updated_at timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
I tested running a new migration on 5.1.28, then dumping the file, and trying to import, and the issue remains.
—
Reply to this email directly orview it on GitHub(https://github.com/laravel/framework/issues/3602#issuecomment-174273850).

Typically it requires enabling strict mode.
The issue is that an out of the box homestead install and an out of the box Laravel install with migrations based on the docs will not work.

@taylorotwell - yes, that would also solve it. But the point is the "default" Forge and "default" Homestead configs dont have that - so the "default" Laravel 5.1.28 runs into issues.
It would be nice if something changed so all the "defaults" align? Currently they dont...

@taylorotwell As mentioned in my previous post NO_ZERO_DATE is currently a feature in flux. TheShiftExchange is correct in his explanation of the workaround.

Credits to @dbillionlabs for his answer. It removed the maggots in my head.

@taylorotwell Could you make $table->timestamps() default to either nullable() or useCurrent() on 5.1, like you did in commit 720a116897a4cc6780fa22f34d30c5986eafc581 to 5.2?

He doesn't seem to care to understand this one.

$this->capsule->addConnection(
[
'driver'    => 'mysql',
'host'      => '<IP_ADDRESS>',
'database'  => 'xxxx',
'username'  => 'xxxx',
'password'  => 'xxxx',
'charset'   => 'utf8',
'collation' => 'utf8_unicode_ci',
'port'      => '33060',
'prefix'    => '',
'strict'    => true
]);
Setting strict => true solved the for me

@Stayallive thank you for saving my time. It works.

Thanks @andela-tolotin

For people like me who have just updated to mysql 5.7 and faced this issue and google search results landed them here...
use the below link
https://mattstauffer.co/blog/how-to-disable-mysql-strict-mode-on-laravel-forge-ubuntu

for the issue with strict mode true , check
https://laravel.com/docs/5.3/upgrade#upgrade-5.2.0

MySQL Dates

Starting with MySQL 5.7, 0000-00-00 00:00:00 is no longer considered a valid date, since strict mode is enabled by default. All timestamp columns should receive a valid default value when you insert records into your database. You may use the useCurrent method in your migrations to default the timestamp columns to the current timestamps, or you may make the timestamps nullable to allow null values:

$table->timestamp('foo')->nullable();

$table->timestamp('foo')->useCurrent();

$table->nullableTimestamps();
kinda dump that something like that wasnt properly documented

The problem is the version mysql, i have the same problem, i can solve with run SET sql_mode = 'ALLOW_INVALID_DATES';

I had the same problem, I solved it by running SET sql_mode = 'ALLOW_INVALID_DATES';

Migrating old tables works like that:
Schema::table(
            'table',
            function (Blueprint $table) {
                $table->dateTime('created_at')->nullable()->default(NULL)->change();
                $table->dateTime('updated_at')->nullable()->default(NULL)->change();
            }
        );

Setting strict => true fixed it for me as well.

i have the same error i think on this
Schema::create('notifications', function (Blueprint $table) {
$table->increments('id');
$table->string('notificationText', 2000);
$table->string('url', 2083);
        $table->integer('type')->unsigned();
        $table->foreign('type')->references('id')->on('notificationTypes')->onDelete('cascade');

        $table->bigInteger('concernedUser')->unsigned();
        $table->foreign('concernedUser')->references('id_user')->on('users')->onDelete('cascade');

        $table->boolean('isSeen');
        $table->timestamps('timeNotif'); // got prblm

        $table->timestamps();
    });

[Illuminate\Database\QueryException]
SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to you
r MariaDB server version for the right syntax to use near 'timeNotif) null, updated_at timestamp(timeNotif) null, created_at times
tamp ' at line 1 (SQL: create table notifications (id int unsigned not null auto_increment primary key, notificationText varchar
(2000) not null, url varchar(2083) not null, type int unsigned not null, concernedUser bigint unsigned not null, isSeen tinyin
t(1) not null, created_at timestamp(timeNotif) null, updated_at timestamp(timeNotif) null, created_at timestamp null, updated_a   t timestamp null) default character set utf8mb4 collate utf8mb4_unicode_ci)
[Doctrine\DBAL\Driver\PDOException]
SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to you
r MariaDB server version for the right syntax to use near 'timeNotif) null, updated_at timestamp(timeNotif) null, created_at times
tamp ' at line 1
[PDOException]
SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to you
r MariaDB server version for the right syntax to use near 'timeNotif) null, updated_at timestamp(timeNotif) null, created_at times
tamp ' at line 1

i got this same error
SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for
Here is my solution to it on laravel 5.7
instead of using   $table->timestamp('product_publish_date')
i replaced it by $table->timestamp('product_publish_date')->nullable()
also i modified my AppServiceProvider by adding this : use Illuminate\Support\Facades\Schema;
and also i added Schema::defaultStringLength(191); in public function boot()

I'm locking this issue because it either has gone off-topic, become a dumping ground for things which shouldn't be in an issue tracker or is just too old.


feat(MatDIalog): Allow specifying MatDialogConfig as part of the dialog component

Feature Description
Currently if there is a dialog which is meant to be used with a specific width, height, autoFocus, disableClose, etc... each and every code that opens that dialog need to specify those values. Even if extracted to a const you still need to remember to pass it.
What I wish to have is the ability to specify on the dialog component itself those configuration options or at least some of them that make sense. Allowing to actually "declare" to the one using - If you pass nothing in the open function config - this is the recommended and default config for this specific dialog. If you do pass a config object it overrides the recommended one.
Use Case
When having a dialog that needs for example to have autoFocus as false always as it handles it inside - everyone using that dialog has to remember to declare this specific config when opening otherwise the dialog won't work as expected. Even if it was extracted to a const - the one opening the dialog still needs to know that const exists and remember to pass it.
The suggestion allows the dialog creator to specify the default config.

We have the MAT_DIALOG_DEFAULT_OPTIONS injection token that allows you to configure the defaults for the dialog. Is this what you're looking for?

We have the MAT_DIALOG_DEFAULT_OPTIONS injection token that allows you to configure the defaults for the dialog. Is this what you're looking for?

Unfortunately no... The idea is per component basis. So the component author can specify it. The injection token you mentioned can only be specified from outside the dialog as far as I know. The main idea is the component author should know best what fits the dialog (in most cases) and should provide a default on the component itself and not from outside.

@crisbeto Any news concerning this?


Demonstrate how to approach loading standard products

PWA Kit was originally developed against the SFRA catalogue which primarily consists of master/variants products.
As such, it currently doesn't support standard products out of the box.
This PR shows how you might approach some of customizations required to support standard products.
It is not intended for production use.

PWA Kit was originally developed against the SFRA catalogue which primarily consists of master/variants products.
As such, it currently doesn't support standard products out of the box.

The video games in SFRA are meant to reflect simple products: https://production-sitegenesis-dw.demandware.net/s/RefArch/electronics/gaming/games/ubi-soft-my-spanish-coach-pspM.html?lang=en_US

This PR are available in develop branch? I’m trying to configure using this example, but I getting error when try to add product in cart


Changing endpoint management to respect service prefixes

See #595
This fix requires widespread changes to references to service endpoint types.

Closing this in favor of #599


Removing Premade Elements

I would like to remove all of the premade elements so that I can custom-make all the elements so I can learn the language from the ground up. But, every time I remove the element files in Source/Elements, the menu no longer works. I think this is a great language and it could be very helpful! Thank you so much to anyone that can help me!

That's a good idea! I'll be able to have a look at fixing that today or tomorrow.

Thank you so much!

Hi! I think I fixed it on the main branch. Please let me know if it still doesn't work :)

Thank you! I will try it again when I am done with work and post here if it works!

Yay! It works! Thank you for fixing this!

Actually, am I doing something wrong or is this another bug related to this?
The element does not show up in the menu once I add a rule to it.
My code looks like this (in the customelements.js file)
SpaceTode `
element Sand {
colour "yellow"

rule {
    @ => _
    _    @
}

}
`

it works fine without the rule though

Have you tried opening the console in the web browser? It might give you an error message. I'm wondering, maybe it could be because those @ and _ symbols aren't defined (if you removed all the other element files). I would recommend keeping the Globals.js file - it doesn't make any elements - it just defines some symbols to get you started. Here it is: https://github.com/l2wilson94/SandPond/blob/main/Source/Elements/Globals.js

Yes, Thank You! Adding the Globals file made it work.

Great! Please feel free to let me know if you want any more help with anything :)

Okay, thank you!


Add ES build to react-router and react-router-dom (#4425)

This creates an ES build (still transpiled, but with ES2015 import/exports left in tact to enable tree-shaking) inside es/, updates the relevant gitignores & npm inclusions, and adds a "module" entry point to package.json of react-router and react-router-dom.
Please see https://github.com/ReactTraining/react-router/issues/4425#issuecomment-276717662 before merging, as this also updates the react-router imports from react-router-dom to be top-level rather than cherry-picked (necessary to enable descendent tree-shaking). As-is, this increases the bundle size of cherry-picked CJS imports from react-router-dom, since they now include the entire react-router package.
IMO, this is fine -- if people care about bundle size, they should be using a tree-shaking bundler -- but if you disagree, I can add this babel plugin which would transpile the top-level imports back to cherry-picked ones during the CJS build.

Any idea what's up with travis? The tests pass locally but the build stalls on CI.

See #4430 there were errors in a fix.

Thanks @kwelch -- I'll wait for that to land and rebase onto it.

Landed that. Go nuts!

Rebased and addressed your comments. Any thoughts on https://github.com/ReactTraining/react-router/pull/4432#issue-204659273?

Travis is still sad; tests still passing locally :(

I dunno what was up with it. Maybe a BrowserStack issue?
In any case, I'm not sure about the need for the CJS transformation. Someone can just import from the react-router package to get around that, right?

Someone can just import from the react-router package to get around that, right?

For the simple re-exports, yes, but not for the DOM components that build on top of base ones like BrowserRouter. There won't be a way to import these in CJS without including the entire react-router package.

Awesome, thanks @billyjanitsch 👍


[Improvement][api]Batch query for optimizing query process-list interface

Interface for paging query process definition is not very efficient.
Querying the user's name in a loop makes the interface take a lot of time.
So here we do some efficiency optimization with batch queries

Codecov Report

Merging #13222 (3738d76) into dev (7643d28) will decrease coverage by 0.03%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##                dev   #13222      +/-   ##
============================================
- Coverage     39.44%   39.41%   -0.04%
- Complexity     4298     4316      +18
============================================
  Files          1070     1077       +7
  Lines         40651    40783     +132
  Branches       4674     4664      -10
============================================
+ Hits          16035    16073      +38
- Misses        22825    22917      +92
- Partials       1791     1793       +2

Impacted Files
Coverage Δ

...api/service/impl/ProcessDefinitionServiceImpl.java
35.18% <100.00%> (+0.41%)
:arrow_up:

...er/master/dispatch/host/assign/RandomSelector.java
77.77% <0.00%> (-5.56%)
:arrow_down:

...org/apache/dolphinscheduler/remote/utils/Host.java
42.55% <0.00%> (-2.13%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

...hinscheduler/plugin/alert/script/ScriptSender.java
70.58% <0.00%> (-1.64%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
51.38% <0.00%> (-1.39%)
:arrow_down:

...cheduler/plugin/alert/dingtalk/DingTalkSender.java
34.13% <0.00%> (-0.78%)
:arrow_down:

...rver/master/runner/task/BlockingTaskProcessor.java
75.86% <0.00%> (-0.55%)
:arrow_down:

...inscheduler/plugin/registry/etcd/EtcdRegistry.java
50.69% <0.00%> (-0.35%)
:arrow_down:

.../dolphinscheduler/plugin/task/datax/DataxTask.java
36.62% <0.00%> (-0.26%)
:arrow_down:

... and 27 more

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


test and add info for microbit stand alone

There is a Dockerfile by @ncoghlan that I can test. He also created the docker repository about it.

The @ncoghlan projet is a clone of https://github.com/bbcmicrobit/micropython


fix: fix wrong parameter for resolveControllerRef

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in Fixes #<issue number>, #<issue number>, ... format, will close the issue(s) when PR gets merged):
Fixes #
Checklist:

[ ] Docs included if any changes are user facing

/retest

/assign @johnugeorge


Moving lag with arrow keys

VSCode Version: 1.12.0-Insider
OS Version: Ubuntu 16.04

There is a lag while trying to moving with arrow keys in editor view

@AknOzgen can go into the command palette and run "Developer: Startup performance". Pls append the machine specs to this issue. Also, what file types do you work with? Which extensions do you have installed? Could you also pls attach a screen recording that shows the issue? Thanks!

@AknOzgen without more detailed steps or a description of the problem we cannot act on this issue. I have to close it. Please reopen it with more information.


would it be possible to edit the 'otter'-buffer with the excellent nvim-R- package, so that interactive changes could be saved back to the code chunks

Hi so this is above my skill level to implement my self, but what I really mis about Sublime Text is that I had a plugin that could just send lines of codes to tmux. This meant that I would interatively edit code chunks in a quarto document, because it didn't what type of file it was.
Now I'm using nvim-R  for my R scripts, which is completely amazing. But it does not work in code chunks in a quarto document, so I have to copy back and forth when polising something.
So I was thinking if it is possible to edit the hidden buffer, which I guess is an R file type, so that I would edit that with nvim-R and a terminal, and then changes saved would go back to the code chunks?
As you can hear,  I do not have much knowledge about what's going on under the hood. But I'm hoping it would be possible?

No need to edit the hidden buffer for that. In the kickstarter configuration I included and configured the plugin vim-slime that can send chunks of code to many places, including tmux (which I use as well) and the integrated neovim terminal (which is what I configured for the kickstarter repo). I am working on a video to show the features, which is supposed to go live after I finished the getting started section on Neovim for the quarto website, but I have now put it already out there as unlisted. Once it has finished processing on YouTube's servers in around 30 minutes, you can watch it here. Let me know if you have any suggestions!

I use it for quarto code chunks see https://github.com/jmbuhr/quarto-nvim-kickstarter/blob/main/ftplugin/markdown.lua, but also in plain R or python chunks by adding these comments to designate code chunks: https://github.com/jmbuhr/quarto-nvim-kickstarter/blob/main/ftplugin/r.lua

If you want to use tmux instead of the integrated neovim terminal you can swap the comments in these lines:
https://github.com/jmbuhr/quarto-nvim-kickstarter/blob/38a04c7e3893fc6a92d83c2ec4235ddcfa335144/lua/config/global.lua#L69-L78

That sounds great I'll take a look at it in the beginning of next week! Thank you for all your hard work.


curl/libcurl not supporting --http3

Hello,
While I understand this may not be the most appropriate place or repo for my issue I am just seeking help with running --http3 command following the Cloudflare Quick & HTTP3 article (https://blog.cloudflare.com/http3-the-past-present-and-future/) and I'm hoping this is the fastest and most active way.
I have followed the instruction for "If you're running macOS, we've also made it easy to install an HTTP/3 equipped version of curl via Homebrew"
Step 1) Install Homebrew Curl
$ brew install --HEAD -s https://raw.githubusercontent.com/cloudflare/homebrew-cloudflare/master/curl.rb
Step 2) Added Homebrew curl path to bash profile and checked along with version.
$ curl -V
curl 7.69.0-DEV (x86_64-apple-darwin18.7.0) libcurl/7.69.0-DEV SecureTransport zlib/1.2.11 brotli/1.0.7 libidn2/2.3.0 librtmp/2.3
Release-Date: [unreleased]
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS brotli IDN IPv6 Largefile libz NTLM NTLM_WB SSL UnixSockets

$ which curl
/usr/local/opt/curl/bin/curl

$ curl-config --version
libcurl 7.69.0-DEV

Step 4) THE ISSUE
When I run the example command it says libcurl version doesn't support this.
$ curl -I https://blog.cloudflare.com/ --http3
curl: option --http3: the installed libcurl version doesn't support this
curl: try 'curl --help' or 'curl --manual' for more information

I can find very little information on this online...So I'm hoping someone would be able to help.
Tony

I have also just run the following and noticed curl is showing OS version and not Homebrew version even though "which curl" and "curl -V" is showing and using Brew version. (https://github.com/Homebrew/brew/issues/3433)
$ brew config
HOMEBREW_VERSION: 2.2.2
ORIGIN: https://github.com/Homebrew/brew
HEAD: 13f508d0dc8ada1726ee09a750285d7447ac3df4
Last commit: 3 weeks ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 915cd48b0fdb4d333785be0dbef72243ce6a2b05
Core tap last commit: 6 hours ago
HOMEBREW_PREFIX: /usr/local
CPU: octa-core 64-bit haswell
Homebrew Ruby: 2.6.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby
Clang: 10.0 build 1001
Git: 2.20.1 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 7.54.0 => /usr/bin/curl
Java: 1.8.0_232
macOS: 10.14.6-x86_64
CLT: <IP_ADDRESS>.1.1562985497
Xcode: 11.3
XQuartz: 2.7.11 => /opt/X11

So extra step I have attempted this and refused:
$ brew link curl --force
Warning: Refusing to link macOS-provided software: curl
If you need to have curl first in your PATH run:
  echo 'export PATH="/usr/local/opt/curl/bin:$PATH"' >> ~/.bash_profile

For compilers to find curl you may need to set:
  export LDFLAGS="-L/usr/local/opt/curl/lib"
  export CPPFLAGS="-I/usr/local/opt/curl/include"

For pkg-config to find curl you may need to set:
  export PKG_CONFIG_PATH="/usr/local/opt/curl/lib/pkgconfig"

Running Mac OS X 10.14.6

In my .bash_profile
export PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# Homebrew
export PATH="/usr/local/sbin:$PATH"

# Homebrew Curl Cloudflare HTTP/3
export PATH="/usr/local/opt/curl/bin:$PATH"

@tonyclemmey Thanks. I am able to reproduce on my macbook as well. I think this is because something is wrong with BoringSSL build (required by quiche and curl tls support both) and eventually curl is built without quiche, so http3 support is missing.
[ 65%] Linking C static library libcrypto.a
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: libcrypto.a(cpu-aarch64-fuchsia.c.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: libcrypto.a(cpu-aarch64-linux.c.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: libcrypto.a(cpu-arm-linux.c.o) has no symbol

I'll take a look.

You can try #320 to see if it fixes the issue, using the following patch to curl.rb:
diff --git a/curl.rb b/curl.rb
index 04561a9..8abba98 100644
--- a/curl.rb
+++ b/curl.rb
@@ -39,7 +39,7 @@ class Curl < Formula
     system "./buildconf" if build.head?

     # build boringssl
-    system "git", "clone", "--recursive", "https://github.com/cloudflare/quiche"
+    system "git", "clone", "-b", "boringssl_update", "--recursive", "https://github.com/cloudflare/quiche"
     mkdir_p "quiche/deps/boringssl/build"
     cd "quiche/deps/boringssl/build" do
       system "cmake", "-DCMAKE_POSITION_INDEPENDENT_CODE=on", ".."

@junhochoi Many thanks, working for me now.

  HTTP3:            enabled (quiche)
  ECH:              no      (--enable-ech)
  Protocols:        DICT FILE FTP FTPS GOPHER HTTP HTTPS IMAP IMAPS LDAP LDAPS MQTT POP3 POP3S RTMP RTSP SMB SMBS SMTP SMTPS TELNET TFTP
  Features:         AsynchDNS HTTP2 HTTP3 HTTPS-proxy IDN IPv6 NTLM NTLM_WB PSL SSL UnixSockets alt-svc brotli libz zstd

  WARNING:  HTTP3 enabled but marked EXPERIMENTAL. Use with caution!

but still:
$ ./src/.libs/curl -I https://cloudflare-quic.com --http3
curl: option --http3: the installed libcurl version doesn't support this
curl: try 'curl --help' or 'curl --manual' for more information```

@binarytrails I have exactly the same issue. I followed the openssl installation route. Were you ever able to resolve this?

@jdunk No, I ended up using https://github.com/aiortc/aioquic/blob/main/examples/http3_client.py for the sake of time. Let me know if you find a solution! From what I understood/remember about curl in http3 all curl libraries needs to be aligned and I didn't want to break my curl by replacing them all or otherwise, pointing to the right ones which can get tedious.

Thanks @binarytrails. In my case, my version of libcurl as reported by curl --version was not the right one (much older than the curl version), and while some people reported having to modify the ld load order in /etc/ld.so.conf, in my case I simply needed to sudo ldconfig -v and then curl --version reported the correct (matching) libcurl version and the --http3 option also then worked.

curl's official guide definitely needs to add that step.

18 months later and the guide remains the same, but this fixed my issue, thanks!

Any one help me?
$ curl --version
curl 7.74.0 (x86_64-pc-linux-gnu) libcurl/7.74.0 OpenSSL/1.1.1n zlib/1.2.11 brotli/1.0.9 libidn2/2.3.0 libpsl/0.21.0 (+libidn2/2.3.0) libssh2/1.9.0 nghttp2/1.43.0 librtmp/2.3
Release-Date: 2020-12-09
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps mqtt pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS brotli GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP UnixSockets
$ curl --http3 https://cloudflare-quic.com/
curl: option --http3: the installed libcurl version doesn't support this
curl: try 'curl --help' or 'curl --manual' for more information

Just updating here:
luis@xtreme:~$ curl --version
curl 7.85.0 (x86_64-pc-linux-gnu) libcurl/7.85.0 OpenSSL/3.0.5 zlib/1.2.11 brotli/1.0.9 zstd/1.5.2 libidn2/2.3.3 libpsl/0.21.0 (+libidn2/2.3.2) libssh/0.9.6/openssl/zlib nghttp2/1.49.0 librtmp/2.3
Release-Date: 2022-08-31
Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL threadsafe TLS-SRP UnixSockets zstd
luis@xtreme:~$ curl --http3
curl: option --http3: the installed libcurl version doesn't support this
curl: try 'curl --help' or 'curl --manual' for more information


Problem about kitti2015 eval

I downloaded your pre-trained model and used the following command to test.
python finetune.py --maxdisp 192 --datapath path-to-kitti2015/training/
--save_path results/kitti2015 --datatype 2015 --pretrained checkpoint/kitti2015_ck/checkpoint.tar
--split_file checkpoint/kitti2015_ck/split.txt --evaluate
without spn.The result is :Average test 3-Pixel Error = Stage 0=0.1401, Stage 1=0.1580, Stage 2=0.1008
It is very different from the best result, which makes me very confused.
My CUDA 10.1 python 3.7.3  pytorch 1.5.1

I am having the same problem.  Is there still no answer to this? @mileyan

set the align_corners=True to nn.functional.upsample & grid_upsample. I got this.
Average test 3-Pixel Error = Stage 0=0.1999, Stage 1=0.1046, Stage 2=0.0671, Stage 3=0.0615 torch Version: 1.10.0+cu111 cuda_11.1.TC455_06.29190527_0 Python 3.7.13

could you tell me where to set  the align_corners=True please?,I don't find it in this project

set the align_corners=True to nn.functional.upsample & grid_upsample. I got this.
Average test 3-Pixel Error = Stage 0=0.1999, Stage 1=0.1046, Stage 2=0.0671, Stage 3=0.0615 torch Version: 1.10.0+cu111 cuda_11.1.TC455_06.29190527_0 Python 3.7.13

I can't find grid_upsample,I can only find nn.functional.upsample&F.upsample

set the align_corners=True to nn.functional.upsample & grid_upsample. I got this.
Average test 3-Pixel Error = Stage 0=0.1999, Stage 1=0.1046, Stage 2=0.0671, Stage 3=0.0615 torch Version: 1.10.0+cu111 cuda_11.1.TC455_06.29190527_0 Python 3.7.13

My environment is the same as yours，
I wonder when ‘cd models/spn_t1 bash make.sh’ ，will this error occur？：
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
warning: ‘T* at::Tensor::data() const [with T = float]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]

set the align_corners=True to nn.functional.upsample & grid_upsample. I got this.
Average test 3-Pixel Error = Stage 0=0.1999, Stage 1=0.1046, Stage 2=0.0671, Stage 3=0.0615 torch Version: 1.10.0+cu111 cuda_11.1.TC455_06.29190527_0 Python 3.7.13

May I ask whether you finetune the model trained by yourself or the model given by the author?

set the align_corners=True to nn.functional.upsample & grid_upsample. I got this.
Average test 3-Pixel Error = Stage 0=0.1999, Stage 1=0.1046, Stage 2=0.0671, Stage 3=0.0615 torch Version: 1.10.0+cu111 cuda_11.1.TC455_06.29190527_0 Python 3.7.13

Soory I can't find grid_upsample,i can only find nn.functional.upsample & F.upsample in anynet.py
After adding align_corners=True,my result become better but still lower than yours:
Average test 3-Pixel Error = Stage 0=0.1382, Stage 1=0.1248, Stage 2=0.0874, Stage 3=0.0798


Add a mechanism to interrupt Reader::read_line without user input.

Currently only user input, or an operating system specific signal can interrupt a running Reader::read_line call.
This is not sufficient for concurrent applications that may need to terminate due to reasons other than user input on terminal.

Hm. I don't know about this. It seems like bad form to terminate an application while a user may still be typing input. Would it not be possible to set a flag (outside of linefeed) and terminate after the next read_line call completes?

Wouldn't it suffice, then, to print a message to the terminal indicating that the bot has shut down and wait for the user to exit the terminal client?

That would interfere with mechanisms to automatically restart the bot/etc.
And, well... why? It's not an interactive application.

I feel like it's not a "clean" exit to interrupt read_line and if your application doesn't require a "clean" exit, there are alternatives, in std::process::exit or putting read_line in a background thread.

I don't understand how forcefully terminating the process with process::exit is cleaner than letting all control flow return, by interrupting read_line. It's not a clean exit for an interactive program, but it's one for a server program?
I understand that it may not be a clean exit for the applications you wrote linefeed for, but for the ones I'm using it for, it indeed is far cleaner than anything even resembling waiting for user input to terminate. The perfect shouldn't be the enemy of the good.

I'm not saying exit is cleaner. I'm saying that, comparatively, exit seems no less clean than interrupting read_line, at least on the user interface front.
Perhaps the read_line thread could hold weak Arc references?

It isn't cleaner on the user interface front, no, but it is far cleaner as far as the actual execution path. I would much rather quit the terminal loop through normal control flow than exit, or anything similar. Even given these alternative solutions, my evaluation of this is still that the best solution would be to interrupt read_line somehow.
I don't understand why this is such a point of contention?

I've given this issue some thought and I've realized a solution that I think will be mutually agreeable.
The solution I had initially imagined, which I did not want to implement, was to wake read_line from its wait_for_input call (which currently waits indefinitely) every second or so, to check for a shutdown condition (something like an AtomicBool), regardless of whether an application is using this shutdown condition feature.
The more flexible solution that I realized is instead to expose another method, called something like read_line_step, which would accept an Option<Duration> value. read_line_step would wait only this duration for new input, process any new input that becomes available, and return. It would not loop. Thus, an application that wishes to check for a shutdown condition can do so (in whatever way that application desires) and an application that wishes to block indefinitely on new input can do so without waking the main loop unnecessarily.
I will implement this flexible solution shortly and let you know when it's complete.

@Lymia: I've just pushed the commit (b0032cbe031a96f097e70defd53d1c2995b4006f) implementing the aforementioned solution.


RFBridge assistance

Hi,
Firstly, thank you for the work that you have done on SonoffLAN.
Secondly, I hope you are able (aka willing) to help me. I am a noob when it comes to bespoke home automation and Home Assistant in particular. I've read the help documentation but have struggled to follow much of it, as it seems to assume a certain degree of prior knowledge which, unfortunately, I am lacking. I have, however, managed to set it up with a few integrations by following various tutorials. I have also managed to successfully integrate SonoffLAN for my RF Bridge 433 and PIR and have set up a simple automation whereby my lights are turned on if motion is detected:
- id: '1595050806949'
  alias: Turn lights on when motion detected
  description: ''
  trigger:
  - event_data:
      name: PIR
    event_type: sonoff.remote
    platform: event
  condition: []
  action:
  - data:
      entity_id: switch.sonoff_office_1
    service: switch.turn_on

However, what I am also trying to achieve is for the lights to turn off if motion is not detected for a certain number of minutes. I have found this example: https://www.home-assistant.io/cookbook/turn_on_light_for_10_minutes_when_motion_detected/ which basically explains what I am trying to achieve, but I am struggling to understand how to use the state platform with SonoffLAN rather than event platform.
Any help would be very gratefully appreciated.
Thanks,
Richard
P.S. If anyone knows of a "Dummies Guide to Home Assistant" for complete newbies, I would also be very grateful.

I would recommend posting this in the HA community forums, you'll get a lot more eyes on it.
For your question, I don't use any PIR sensors but I assume they'll have a state similar to on/off for motion detected.
Here's an example where I turn a light off after the state has been set to 'on' for 5 minutes
 #Turn off hallway light after 5 minutes
 - alias: Turn off hallway light
   initial_state: 'on'
   trigger:
     - platform: state
       entity_id: switch.ge_12722_onoff_relay_switch
       from: 'off'
       to: 'on'
       for:
         minutes: 5
   action:
    - service: switch.turn_off
      entity_id: switch.ge_12722_onoff_relay_switch

@cybergrimes in your example, the timer will not refresh for every move

@cybergrimes in your example, the timer will not refresh for every move


Improvising WeatherAlertGeneratorTest.kt

Improvising Update:

Added backticks () around the test method name (getAlerts should return the expected alerts`) to allow spaces in the method name.

Updated the test method signature to use backticks around the method name.

Removed the explicit type emptyList<WeatherAlert>() and replaced it with emptyList() to take advantage of type inference.

Conclusion of this improvement update: Readibility and maintainability.
Ending of this commit message: Thank you very much for this amazing application to exist

Thank you for the contribution, I was not aware of this naming convention and I agree it improves the readability of test methods (https://kotlinlang.org/docs/coding-conventions.html#names-for-test-methods)


Gen0 fills up when idle

When leaving the IDE open, I can see the Gen0 GC bar slowly filling up over time, even without me doing anything in the IDE.
Is it expected, or a possible leak of sorts?

When leaving the IDE open, I can see the Gen0 GC bar slowly filling up over time, even without me doing anything in the IDE.
Is it expected, or a possible leak of sorts?

I've noticed the same in Windows.  It usually climbs just past 50%, and stops right after the "n" in "Gen 0".  But, I haven't seen it completely fill in yet, have you?  I have no idea how this "Heap Monitor" toolbar icon works beyond selecting to hide/show it using an option from under the "View" menu.  Maybe someone can advise why it climbs when nothing is really running.

The IDE calls some Lisp code while running (colorisation code in particular). So yes, it is expected to fill up bit by bit.

Calling colorization code while no code is being edited seems wasteful - it does not change anything in the presentation.


Calculate Next Assessment Depending on Suppressed/Unsuppressed

The frequency of preference assessments depends on the patient's last viral load:
SUPPRESSED: Assessment every 3 months
UNSUPPRESSED: Assessment every month
Account for this in the lib/utils/Utils.dart's calculateNextAssessment method.
Also: Calculate proper next date based on months (currently it's based on days, i.e. 60 days for two months).

Implemented with b54cc75d920fb7dbb3133a8e0d67b0014779d421.


Edits to "Angular Modules (NgModule)" (now "NgModules") and "Angular Module FAQs" (now "NgModule FAQs")

@juleskremer here are my edits for the "Angular Modules (NgModule)" page.
In order to fix some broken links, I also defined destinations in forms.jade and pipes.jade.

@juleskremer I committed updates to change "Angular Module" to "NgModule". I also edited the "Angular Module FAQs" (now "NgModule FAQs") page and reference files. See my commit comments for more details.


WGS84 coordinates transformation to Cartesian coordinates

Hi,
i'm new to geographic coordinate systems. I'm looking for the code example which provide conversion of point and polygon which coordinates are represented in WGS84 coordinate system to cartesian coordinates. Because i want to use NetTopologySuite library to perform some geometry calculations like calculating distance from point to polygon.
Thank you!

If you look in the examples folder in the source code I bet you can find some transformation routines.


Unit test issue: Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'RNCWebView' could not be found

Bug description:
Hello, the problem is the following: each time I want to test a react-native-webview with @testing-library/react-native I get this error "Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'RNCWebView' could not be found. Verify that a module by this name is registered in the native binary." or similar about "getEnforcing".
The workaround is to keep the react-native-webview.tsx file in the mocks folder but it does not help me to test my functionality correctly.
To Reproduce:
Just try to do this
import { render } from "@testing-library/react-native"; ... render(       <WebView         source={{ uri: webViewProps.appUrl }}         ref={webViewProps.webviewRef}         onMessage={webViewProps.invoke.listener}       />     );
Expected behavior:
To be able to test the exact functionality of react-native-webview like renderError, renderLoading
Screenshots/Videos:

Environment:

OS: mac
OS version: Sonoma 14.3.1
react-native version: 0.72.4
react-native-webview version: 13.2.2
@testing-library/react-native: ^12.4.2
@testing-library/jest-native: "^5.4.3"

+1

+1

Was able to overcome this problem with the next workaround:
Put this snippet into your jest.setup.js file (or put this into your spec file locally)

jest.mock('react-native-webview', () => {
  const MockWebView = () => '<RNWebView />';

  return {
    __esModule: true,
    WebView: MockWebView,
    default: MockWebView,
  };
});

I am having the same issue


version up to 1.5.6

Description
Please include a summary of the change and which is fixed.

version up to 1.5.6
updated versions of requirements

How has this been tested?
Please describe the tests that you ran to verify your changes.

[x] UnitTest
[x] Benchmark

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (ea70443) 90.76% compared to head (7283656) 90.76%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #425   +/-   ##
=======================================
  Coverage   90.76%   90.76%
=======================================
  Files         125      125
  Lines        4180     4180
  Branches      662      662
=======================================
  Hits         3794     3794
  Misses        252      252
  Partials      134      134

Files Changed
Coverage Δ

credsweeper/__init__.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Create DNS entries for MTLS and TLS ingresses using new URL structure

For dev we need the following DNS entries
sapig.$env.forgerock.financial
mtls.sapig.$env.forgerock.financial
The existing obdemo DNS entry can become the sapig entry.

Existing DNS entries have been left in place, giving us more flexibility when rolling this change out to dev envs.

Created #832 to cleanup DNS entries at a later date.


[wip] Adds ktor+netty-based API

This is a WIP to add a Ktor + Netty API to libage.
Ideally, it would have a few different API endpoints such as:

/ - get basic information about the API, perhaps version info for libage
/circuits.json
/circuit/add - add a circuit
/circuit/step - step a circuit (possibly with some more information in the request such as a number of steps/time of steps)
/circuit/fetch - get circuit solve values
/circuit/delete - delete a circuit
Some kind of editing API for a circuit. This would require being able to modify connectivity as well. Perhaps for a later version?

The actual format is not set in stone yet, but there's some ideas floating around. I want to be able to use this from within code primarily, so knowing if there are logical errors and such for error handling would be helpful. eg, singular matrices, invalid connectivity, etc. I also currently catch sim side errors and throw those back with a stack trace but we could disable that for production unless debugging is enabled.

I'm challenging @empireu or @Grissess to make this API work with the new API's in Eln2 if they get moved to libage. I doubt I'll be implementing this at this point.


Feature/issue50

The file changes look good to me.  What do you think @cwwalter, @eosullivan?

Nice job Sam!
It it is not too much trouble I would like to ask you to redo this a bit.  Your code itself looks fine on a quick check but this stuff:
" Chris Walter	Merge branch 'hotfix/HK_geometry_check'	 4744f64
Chris Walter	Merge branch 'release/hyperk-v1.2.0'	 0824503
Sam Short	Merge remote branch 'upstream/master' into develop"
That came from your learning how to do everything is going to make the history look confusing.  I'm not sure exactly how it happened but you merged old things from as far back as August onto your current branch including the master which only contains the releases.
In fact, this should still work OK since the changes to the files are really all that matters, but the graph of the branches will have some confusing things related to Master that will make it harder to understand when people are looking at them and trying to understand what happened in the past.
So, can I ask you to try the following?  Now that you are an expert it should go fast.

Close this pull request.
Rename/move the repo on your disk to somewhere else so you still have the work you did.
From the github site, delete the issue50 branch on your fork (click on "branches" to do that)
Re-clone your fork
Make and change to a new issue50 branch
Reapply your changes, commit and then push to your fork
Make a new pull request

This will make the pull request look nice and clean.
Thanks!

BTW, to be safe you better give the new issue50 branch a slightly different name.
I'm now sure but there may be problems if you try to use the same name as it keeps history for everything.
Maybe issue50_2 or something.

Hi Sam! Congrats on your first WCSim pull request!
Once you have fixed up your branch a bit, I've noticed something in your proposed changes:

You left WCCapPMTSpacing as the old SK value for the two SK configs. However, since we are changing photocoverage, we also need to change the photocoverage of the caps. Set WCCapPMTSpacing = (pi*WCIDDiameter/WCBarrelNumPMTHorizontal);
-I would also set the  WCCapEdgeLimit = WCIDDiameter/2.0 - WCPMTRadius; to avoid problems there with the changing number of PMTs.
The spacing of code for the WCBarrelNRings line is a bit off, probably just from where you are cutting and pasting. It does seem to be working ok, but it would be a bit easier to read if the extra spaces were removed.

Have you tried running your new detectors with the visualizer turned on (using vis.mac)? Does everything look ok (no overlapping volumes, etc)?


Support indexed context arrays

To provide some context, I am trying to create a means of passing a method's classname into my logs as I find it quite handy. My aim was to make this as visually clean as I could in my code, so I don't want to use sprintf() or any other means of formatting the message. To start, here's what im passing as my log arguments:
$this->logger->info("Hey there! I'm just testing!", [__CLASS__]);
To those unfamiliar, __CLASS__ is a magic constant that returns the classname, including the namespace.
By default, Monolog will stringify the context array. This produces a log record which looks like this:
(note: i've custom formatted the log message so that the context appears before the message)
[2019-01-02 02:06:12] INFO: [["LFLAPI\\Services\\Ecom\\SomeService"]] Hey there! I'm just testing!
I don't like how this appears in my logs, so I opted to make use of the pushHandler() to pull out just the first element, which is the string by itself.
$logger->pushProcessor(function ($record) {
    $record['context'] = $record['context'][0];
    return $record;
});

This produces the log results im after:
[2019-01-02 02:09:02] INFO: [LFLAPI\Services\Ecom\SomeService] Hey there! I'm just testing!
But it also triggers a warning:
PHP Warning:  Invalid argument supplied for foreach() in /var/www/api/vendor/monolog/monolog/src/Monolog/Formatter/LineFormatter.php on line 81
If I've analyzed this correctly, it occurs because Monolog expects an associative array, whereas I am passing an indexed array. I would like to propose including support for indexed arrays by including a function that can determine if an array is indexed, or associative:
protected $isAssoc;

public function isAssoc(array $record)
{
    $this->isAssoc = count(array_filter(array_keys($record), 'is_string')) > 0;
}

if ($this->isAssoc) {
    foreach ($vars['context'] as $var => $val) {
        if (false !== strpos($output, '%context.'.$var.'%')) {
            $output = str_replace('%context.'.$var.'%', $this->stringify($val), $output);
            unset($vars['context'][$var]);
        }
    }
}

I feel this adds value to Monolog by allowing for more customization, and ultimately, cleaner user-code. Here's a quick side-by-side comparison of what I was aiming to avoid:
$this->logger->info("Hey there! I'm just testing!", [__CLASS__]);
$this->logger->info(sprintf("[%s] Hey there! I'm just testing!", __CLASS__));

$this->logger->info("Hey there! I'm just testing!", [$var]);
$this->logger->info(sprintf("[%s] Hey there! I'm just testing!", $var));

Note: Build failing because of this unit test:
https://github.com/Seldaek/monolog/blob/master/tests/Monolog/Formatter/LineFormatterTest.php#L94

I'll further note, by implementing an array type check, it would not break existing key value use-cases:
$this->logger->info("Hey there! I'm just testing!", ["className" => __CLASS__]);

[2019-01-02 02:06:12] INFO: [{"className":"LFLAPI\Controllers\Ecom\PromoController"}] Hey there! I'm just testing!

It will also not break things out of the box (ie: not using a pushProcessor() as I've done).
$this->logger->info("Hey there! I'm just testing!", [__CLASS__]);

[2019-01-05 17:11:28] INFO: [["LFLAPI\Controllers\Ecom\PromoController"]] Hey there! I'm just testing!

Moreover, you voiced concerns in https://github.com/Seldaek/monolog/issues/675 over adhering to PSR-3 standards. I argue, that this pull request still adhere's to the recommend useage as described in PSR-3. In fact, I believe it stands truer to what PSR-3 states about Context implementation (section 1.3):

The array can contain anything. Implementors MUST ensure they treat context data with as much lenience as possible.

Take a look at https://github.com/Seldaek/monolog/blob/master/src/Monolog/Processor/IntrospectionProcessor.php instead.. this kinda does what you want and will leave your code even cleaner.


Migrate from legacy long-lived token app to scoped app

Ref #409

[ ] Replace existing legacy codes
[ ] Remove legacy connectors

gzcat spec_91.json.gz | jq -r '.[] | select(.conn_scopes[] | contains("business_management")) | .path' | sort -u

business_management:

[ ] connect business_mgmt
[ ] dev ci auth connect
[ ] dev ci auth export
[ ] dev release candidate
[ ] group add
[ ] group batch delete
[ ] group delete
[ ] group member add
[ ] group member delete
[ ] group rename
[ ] member clear externalid
[ ] member delete
[ ] member detach
[ ] member invite
[ ] member quota list
[ ] member quota update
[ ] member reinvite
[ ] member update email
[ ] member update externalid
[ ] member update profile
[ ] team diag explorer
[ ] teamfolder batch replication
[ ] teamfolder replication

business_file

[ ] connect business_file
[ ] dev ci auth connect
[ ] dev ci auth export
[ ] dev release candidate
[ ] group folder list
[ ] member folder list
[ ] member quota usage
[ ] member replication
[ ] team content member list
[ ] team content mount list
[ ] team content policy list
[ ] team device list
[ ] team device unlink
[ ] team diag explorer
[ ] team filerequest clone
[ ] team filerequest list
[ ] team linkedapp list
[ ] team namespace file list
[ ] team namespace file size
[ ] team namespace list
[ ] team namespace member list
[ ] team sharedlink list
[ ] teamfolder add
[ ] teamfolder archive
[ ] teamfolder batch archive
[ ] teamfolder batch permdelete
[ ] teamfolder batch replication
[ ] teamfolder file list
[ ] teamfolder file size
[ ] teamfolder list
[ ] teamfolder member list
[ ] teamfolder permdelete
[ ] teamfolder policy list
[ ] teamfolder replication

business_audit

[ ] connect business_audit
[ ] dev ci auth connect
[ ] dev ci auth export
[ ] dev release candidate
[ ] team activity batch user
[ ] team activity daily event
[ ] team activity event
[ ] team activity user

business_info

[ ] connect business_info
[ ] dev ci auth connect
[ ] dev ci auth export
[ ] dev release candidate
[ ] group list
[ ] group member list
[ ] member list
[ ] team diag explorer
[ ] team feature
[ ] team info

user_full

[ ] connect user_file
[ ] dev ci artifact connect
[ ] dev ci auth connect
[ ] dev ci auth export
[ ] dev release candidate
[ ] dev test kvsfootprint
[ ] dev test monkey
[ ] file compare account
[ ] file compare local
[ ] file copy
[ ] file delete
[ ] file download
[ ] file export doc
[ ] file import batch url
[ ] file import url
[ ] file list
[ ] file merge
[ ] file mount list
[ ] file move
[ ] file replication
[ ] file restore
[ ] file search content
[ ] file search name
[ ] file size
[ ] file sync down
[ ] file sync online
[ ] file sync up
[ ] file watch
[ ] filerequest create
[ ] filerequest delete closed
[ ] filerequest delete url
[ ] filerequest list
[ ] job history ship
[ ] sharedfolder list
[ ] sharedfolder member list
[ ] sharedlink create
[ ] sharedlink delete
[ ] sharedlink file list
[ ] sharedlink list

 gzcat resources/release/en/spec_94.json.gz | jq -r '.[] | select(.conn_scopes[] | contains("business_file")) | .path' | sort -u

member replication
team content mount list
team content policy list
team device list
team device unlink
team filerequest clone
team filerequest list
team linkedapp list
team namespace file list
team namespace file size
team namespace list
team namespace member list
teamfolder add
teamfolder archive
teamfolder batch archive
teamfolder batch permdelete
teamfolder file list
teamfolder file size
teamfolder list
teamfolder member list
teamfolder permdelete
teamfolder policy list

Remaining commands on Release 96
Business file
% gzcat resources/release/en/spec_96.json.gz|  jq -r '.[] | select(.conn_scopes[] | contains("business_file")) | .path' | sort -u
teamfolder add
teamfolder archive
teamfolder batch archive
teamfolder batch permdelete
teamfolder list
teamfolder member list
teamfolder permdelete
teamfolder policy list

User full
% gzcat resources/release/en/spec_96.json.gz|  jq -r '.[] | select(.conn_scopes[] | contains("user_full")) | .path' | sort -u
dev ci artifact connect
dev test kvsfootprint
dev test monkey
filerequest create
filerequest delete closed
filerequest delete url
filerequest list
job history ship
sharedfolder list
sharedfolder member list
sharedlink create
sharedlink delete
sharedlink file list
sharedlink list


createBinary  deadline exeeded

When I try to upload microservice i get the following error:
c8y microservices createBinary --file target/dynamic-mapping-service.zip --id dynamic-mapping-service
? Confirm (job: 1)
Create microservice binary on tenant t15264971
[y] Yes  [a] Yes to All  [n] No  [l] No to All y
elapsed 00:59   dynamic-mapping-service.zip  [━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ] 97 %  207.53 MiB / 213.73 MiB
2024-07-04T10:39:39.716+0200    ERROR   request timed out after 1m0s
2024-07-04T10:39:39.719+0200    ERROR   commandError: command timed out context deadline exceeded
Uploading using the ui works
Version  2.43.0 Platform macos arm64

Just use the “—timeout 10m” global flag to increase the timeout (you can also change this globally in your session settings)

In v2.43.1, the default global request timeout is now 600s


Cannot run the WebGUI

Hi all, as I have same problem as NeilBuc007 since  today, but without much knowledge, can someone please help/ assist on this matter?
I assume I need to use „nano“ to edit the file? If so, where is this file?
The original topic has been closed (saw this a bit to late)
Thx in advance
Sven

Thx a lot for your effort!
Finally I solved it with assistance of this group!
Sven


Add beta banners to storybook for features in beta

🚧🚧 Draft while getting PM and design feedback 🚧🚧
What
Add beta banners to storybook for features in beta:

Canvas Page Banner

Docs Page Banner

Inline sub-prop Banner

Why
Highlight beta features and recommend not for production use.
References
Here is the equivalent DCOM one: https://docs.microsoft.com/en-us/azure/communication-services/concepts/ui-library/ui-library-overview

This is very smart. <3


fix redirect event not being correctly triggered

I think the rationale of triggering manually $stateChangeSuccess was pointless for the redirect.
It ended up resulting in an inconsistent event trigger, with the actual state redirecting to being the one specified in permission.redirectTo, but the state passed to the events being the current toState, which is the denied state.

Are you sure this works for you? I'm almost certain there was a ui-router bug which required that code as workaround.

Does this work for you? I'm pretty sure there was a ui-router bug related to this which is why we had to do. Check #9

yep, it's working for me with ui-router 0.2.11.
by the way the tests are passing ;)

Ok then, I think this looks good, please rebase this to the latest development version so that I can merge it.
Thanks @stefanotorresi for the help, I'll keep an eye on it because I think that like was fixin some old issues.
Let me know when you're done and I'll merge this for the next release

@Narzerus rebased and good to merge

Thanks for this PR @stefanotorresi will wait for other PRs to be closed and bump the current version to master


Compilation failed when running samples/optimization/matmul.py with rocblas

Describe the bug
I got the following compilation error when running on gfx90a AMD GPU. Seems due to unexpected string pre-preprocessing results.
clang-15: error: invalid target ID 'gfxgfx906'; format is a processor name followed by an optional colon-delimited list of features followed by an enable/disable sign (e.g., 'gfx908:sramecc+:xnack-')
To Reproduce
Steps to reproduce the behavior:

Install dace
git submodule update --init --recursive
python3 setup.py install

Run the matmul.py sample case
python3 samples/optimization/matmul.py --version rocblas

Error snapshot:
Screenshots

OS: Ubuntu 20.04.4 LTS
Docker image: rocm/pytorch:rocm5.4.1_ubuntu20.04_py3.7_pytorch_1.12.1

Thank you for reporting. Did you use an old DaCe version to run this before by any chance? We swapped the old settings from something like 90a to gfx90a recently.
I'd first erase the .dacecache folder and retry. If that doesn't work, did you modify the DaCe configuration (~/.dace.conf) by any chance? Is the entry there correct?

@tbennun Just updated the commands I used to install dace. The version I used is @df2aea9fdd368cb30e4bb827fdf4c395a504280b, which is the latest one on master branch.
commit df2aea9fdd368cb30e4bb827fdf4c395a504280b (HEAD -> master, origin/master, origin/HEAD)
Merge: ba25b2b13 082a909b8
Author: Tal Ben-Nun<EMAIL_ADDRESS>Date:   Mon Mar 6 14:34:08 2023 -0500
Merge pull request #1197 from spcl/sdprof

DaCe Profiler

Here is a sample configuration: https://spcldace.readthedocs.io/en/latest/optimization/gpu.html#using-amd-gpus
I cannot reproduce your issue unfortunately, I do not see gfx appear twice on the latest version. What might be happening is that you have two conflicting versions of dace. Could you try running pip uninstall dace multiple times in a row until pip says there is nothing to uninstall?

When I set hip_arch to 90a, not gfx90a as suggested, in .dace.conf, it works.
# Change the backend to HIP (optional)
backend: hip

# Specify the AMD GPU architecture (optional)
hip_arch: '90a'

# Override default block size (optional but important due to warp/wavefront size)
default_block_size: 64,1,1

# Override default HIP arguments (optional)
hip_args: -std=c++17 -fPIC -O3 -ffast-math -Wno-unused-parameter

However, I then got the linking error of missing rocblas path while librocblas.so.0 can be found by cypes.util.
python3 -c "import ctypes.util;print(ctypes.util.find_library('rocblas'))"
librocblas.so.0

I have seen this issue before, the hip cmake module does not properly set the link directories. I can look into it but in the meantime a solution that worked was to add the path to rocblas to the LIBRARY_PATH environment variable.

It works to have the correct results with LIBRARY_PATH, but I am not sure why a segmentation fault happened at the end of the program. Might be some other issues.
python3 samples/optimization/matmul.py --version rocblas
Matrix multiplication 64x64x64 (version: rocblas)
Difference: 0.0
Segmentation fault (core dumped)

@luise1030 I fixed the issue in our CMake (#1219)

Thanks! @tbennun


remove WSS connection, replace w/ a hearbat app…

changes as discussed !

@jcrossley3  I've added the link to the main.go file - good point!
Also, I added a step required by @markito to show how to clone this repo


feat: use new schema endpoint

Removes influxdb and autoscaler integration (not available)
Uses new schema endpoint do download the user configs
Removes go client dependency
Removes goroutine usage
Removes MeasureExecutionTime, nothing to measure

The new schema is a bit different, that makes a diff on several fields. Not critical for my taste. The code can be further simplified in separate PRs:

cobra is an overkill
logger is a global object, which even causes false-positive linting issues
other global variables
lots of one-line functions
etc


⚠ Spryr has degraded performance

In aa60843, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 6733 ms

Resolved: Spryr performance has improved in 0c66c08 after 9 minutes.


Models - Fanuc CNC intermediate model

#5
Develop an intermediate model to assist in auto-generation of YAML model for the Adapter.  The model will be fanuc-driver.Collector dependent, meaning that data harvested at the root, path, and axis/spindle levels will be known ahead of time.  However, the number of axes, spindles, and path will not be known ahead of time.
See https://github.com/Ladder99/fanuc-driver/issues/12.

The model is completely generated on Fanuc-Driver side.


Cherrypick 4840

#4840 was merged in the release-2.5 branch. Because of generated assets, merging it back in master generates too many conflicts while cherry-picking is straightforward. Note that no v2.5.1 has been released but v2.6.0 is only 2 weeks from now so it might not be worth the effort.
cc @brancz

Good catch! lgtm :+1:


LFS-426_LFS-481: As an administrator i can specify the subject types allowed for a questionnaire in the questionnaire designer

This branch is based off LFS-476, with changes from LFS-426 / LFS-431 & LFS-432 pulled in.

I am not sure how to test this PR. When I click on Subject Types I get "Individual SubjectType view not yet implemented."

I am not sure how to test this PR. When I click on Subject Types I get "Individual SubjectType view not yet implemented."

@sashaandjic This change is in the questionnaire designer.
You should be able to go to a questionnaire and see requiredSubjectTypes under the Questionnaire Properties subheader.  From there, you should be able to click the edit button and change the requiredSubjectTypes property. The available subject types in the dropdown for you to choose from should correspond to the subject types currently in the database.
I'm currently building this branch so I can see what is displayed for me on the SubjectTypes page, but unless this PR broke the subject Type view then it is probably out of scope.
I hope that helps!

Also, here is what i see when I navigate to the SubjectTypes tab.

I think the functionality within this PR is working as expected.

@nela-jankechova  What was the problem? I want to re-test it.

@nela-jankechova What was the problem? I want to re-test it.

The dropdown was automatically highlighting the first option, rather than the one that was actually selected.

@nela-jankechova What was the problem? I want to re-test it.

The dropdown was automatically highlighting the first option, rather than the one that was actually selected.

I see. e.g.  in the  Radio Therapy data Tumor region is the only selection.

When I go to edit mode it appears as Patient is the selection, since it is the firt one listed.

The bug is fixed

however, after save I need to refresh in order to see my modified selection. Step to reproduce:

modify existing selection "Tumour region" to "Patient"

click SAVE

the form is still showing the old selection

refresh, all looks good

@sashaandjic , this is the same issue as the one you commented for LFS-172. The questionnaire page doesn't update immediately, I thought it was a big enough change to existing code to be its own issue. If it needs fixing before LFS-172 can get merged, then I will do it on that PR.

Regression after the latest changes. The edit icon is no longer available for Questionnaire Properties. Here is the screenshot showing an older instance built on July 15 and newer one built Aug 28.

@sashaandjic It was being fixed at that time. Please re-test.

I see the pencil button now, however when I create a new questionnaire and click on it to define the type of subject and hit SAVE I get a blank screen

Should minAnswers > 0 be treated as required value?
If so, I created a task for it https://phenotips.atlassian.net/jira/software/c/projects/LFS/issues/LFS-542

I can specify number of forms per subject.

Unselecting all subject types doesn't work, after saving the previous values are still there.

@sdumitriu I've fixed it in 444af9a :heavy_check_mark: . It should work now.

confirming bug reported by @sdumitriu

tested


[Bug]: 0.8.0 - MQTT connection error?

Adapter version
0.8.0
JS-Controller version
3.3.22
Node version
12.22.7
Operating System type
Linux
Operating system version
Raspbian GNU/Linux 10 (buster)
Describe the bug
After updating to update to 0.8.0 I'm getting these errors every second:
eufy-security.0 | 2022-02-05 16:20:36.811 | error | MQTT Error [{"code":5}]
eufy-security.0 | 2022-02-05 16:20:35.673 | info | MQTT connection closed

But I don't find any information about enabling/disabling/configuring MQTT. Only that this version is supporting the MQTT interface of the T8520 Smart Lock now.
Do you have any hints how to solve this?
I've got these devices:
1 x HomeBase T8010
1 x Doorbell T8210
1 x Motion Sensor T8910
2 x IndoorCam Pan 2K T8410
To reproduce

start eufy-security instance
wait some seconds
see errors in the protocol

Screenshots & Logfiles
No response
Additional context
No response

Habe eben die Version installiert bei mir läuft das log voll mit der Meldung immer abwechselnd in Dauerschleife:
`

eufy-security.0
2022-02-05 20:02:57.937
info
MQTT connection closed

eufy-security.0
2022-02-05 20:02:57.936
error
MQTT Error [{"code":5}]

`

Sorry guys. Fixed in version 0.8.1


怎么用akebi捏

Describe the problem

Please fill in here a clear and accurate description of the problem you are experiencing.
How to reproduce this problem

Steps to reproduce this issue:

xx
xxxx
xxxxxx
xxxxxxxx

Help you need

Please fill in the help you need here.
Screenshot/Video

If possible, please attach your screenshot or video here. You can use Ctrl + V to paste the picture directly.
Your device information

System information:

Version:

Additional information

Here you can enter additional information about the help you need.

怎么用akebi捏


Support for cds.compile.to.hdbtable in Typescript

We are currently using SAP Cloud Application Programming Model (CAP) for our project and have encountered a limitation regarding the use of cds.compile.hdbtable in TypeScript. Our goal is to generate the 'gen' folder artifacts directly without using the build command. This approach is crucial for keeping our database in sync with our deployments.
The main challenge we are facing is that the cds.compile.hdbtable method, which is essential for our process, is not available in TypeScript. To bypass this limitation, we have been using const cds = require('@sap/cds'); as a workaround. However, this is not an ideal solution for our TypeScript-based project.
Our imlementation follows
`const cds = require('@sap/cds-dk');
...
cds.compile.to.hdbtable(csn);`
Please let us know if there are any plans to resolve this problem or any possible workarounds.

Hi Ajay,
thank you for reaching out! I have checked the current state of cds.compile and there appears to be a matching overload already. Does that not work for you?
Best,
Daniel

Hi @ajayk0,
just wanted to confirm with you whether the function I pointed out is what you are looking for?

Please note that compile can be fully accessed from @sap/cds, there is no need to use @sap/cds-dk for this application.
If this did not solve your problem, feel free to reopen this issue.
Best,
Daniel


Warnings about missing source map files when used in ParcelJS + TypeScript project

When use-http is used in a Parcel.js + TypeScript project, the build logs several warnings "could not load source file X in source map of node_modules/use-http/dist/Y"
To Reproduce
Create a new Parcel app with TypeScript that uses use-http:

yarn init -y
yarn add --dev parcel-bundler typescript
add index.html:

<html>
<body>
  <script src="./index.ts"></script>
</body>
</html>

add index.ts:

import useFetch from "use-http";

console.log('test', useFetch);

Build and start:
yarn run parcel index.html --open

Expected behavior
Parcel does not log any warnings.
Actual behavior
Parcel logs the following warnings:
⚠  Could not load source file "../src/index.ts" in source map of "node_modules/use-http/dist/index.js".
⚠  Could not load source file "../src/useMutation.ts" in source map of "node_modules/use-http/dist/useMutation.js".
⚠  Could not load source file "../src/useFetch.ts" in source map of "node_modules/use-http/dist/useFetch.js".
⚠  Could not load source file "../src/useQuery.ts" in source map of "node_modules/use-http/dist/useQuery.js".
⚠  Could not load source file "../src/Provider.tsx" in source map of "node_modules/use-http/dist/Provider.js".
⚠  Could not load source file "../src/FetchContext.ts" in source map of "node_modules/use-http/dist/FetchContext.js".
⚠  Could not load source file "../src/types.ts" in source map of "node_modules/use-http/dist/types.js".
⚠  Could not load source file "../src/utils.ts" in source map of "node_modules/use-http/dist/utils.js".
⚠  Could not load source file "../src/doFetchArgs.ts" in source map of "node_modules/use-http/dist/doFetchArgs.js".
⚠  Could not load source file "../src/useFetchArgs.ts" in source map of "node_modules/use-http/dist/useFetchArgs.js".
⚠  Could not load source file "../useSSR.ts" in source map of "node_modules/use-ssr/dist/useSSR.js".
⚠  Could not load source file "../src/index.ts" in source map of "node_modules/use-http/dist/index.js".
⚠  Could not load source file "../src/useFetch.ts" in source map of "node_modules/use-http/dist/useFetch.js".
⚠  Could not load source file "../src/useMutation.ts" in source map of "node_modules/use-http/dist/useMutation.js".
⚠  Could not load source file "../src/useQuery.ts" in source map of "node_modules/use-http/dist/useQuery.js".
⚠  Could not load source file "../src/Provider.tsx" in source map of "node_modules/use-http/dist/Provider.js".
⚠  Could not load source file "../src/FetchContext.ts" in source map of "node_modules/use-http/dist/FetchContext.js".
⚠  Could not load source file "../src/types.ts" in source map of "node_modules/use-http/dist/types.js".
⚠  Could not load source file "../src/utils.ts" in source map of "node_modules/use-http/dist/utils.js".
⚠  Could not load source file "../src/useFetchArgs.ts" in source map of "node_modules/use-http/dist/useFetchArgs.js".
⚠  Could not load source file "../src/doFetchArgs.ts" in source map of "node_modules/use-http/dist/doFetchArgs.js".
⚠  Could not load source file "../useSSR.ts" in source map of "node_modules/use-ssr/dist/useSSR.js".

Several Parcel.js issues (e.g. https://github.com/parcel-bundler/parcel/issues/2356) suggest this is an issue of the published package.

Will take a look asap

It would be nice if you can't get this working in a codesandbox, maybe make a repo reproducing the bug ❤

Sure, I've pushed a small demo project to https://github.com/mdenburger/use-http-202.

@mdenburger this should be fixed in v0.4.5


Add time zone configuration

I'm noticing that the bot is set to Italy time. For a resident of the United States, this time difference can be a bit jarring when the bot starts asking you to fill in your time for the day while it's still morning. I understand that this might be because the instance that I'm using is hosted in Italy; however, it seems limiting to force users to use a bot hosted in their time zone. Could this be fixed?

Yes it can, true story I was about to open an issue myself since I foresaw this problem.
We can detect the tz from the channel and use it to schedule the reminder

@khaelys after a look at the clockify api docs turns out we can infer this from the user settings there, rather than from the channel. So it is channel-independent and reliable

@LorenDB You should receive the reminders between 17:30 and 23:30 now. If the problem persists, please let me know.

The reminders are coming through at 11:30 AM EDT for me (instead of 5:30 PM as they are supposed to, right?).

@LorenDB Sorry, I forgot to update your timezone. Basically, the timezone is read from clockify only for new token setups.
Keep me updated, have a nice weekend.

OK, now it fires at 8:30 PM. I assume that's good enough for y'all?

It should fire from 5:30 PM, your IANA timezone is America/New_York, right?

Yes, it is

It's working now, thanks!


WIP: Make FSDP a regular transform

Here is a draft PR, I'm currently getting the following error :slightly_frowning_face:
 pytest-3  thunder/tests/distributed/test_ddp.py::test_native_fsdp_torch_cuda_float32[FSDPBucketingStrategy.NONE]

gives
RuntimeError: Failed to find an executor for bound symbol bsym=t18 = thunder.distributed.prims.synchronize(t_net1_bias, _torch_distributed_distributed_c10d_ProcessGroup_2)  # t18: "cuda:1 f32[2]"

I'm not 100% sure what should happen instead (transformed in autograd with augmented forward or find an executor, likely)., so any hint appreciated.
Key properties:

This introduces "early transforms", i.e. the code transformation potentially affects prologue, computation, and epilogue,
The ThunderModule is adapted (here with sharding) and matches the code changes,
The original module is left alone, we are using overrides on the ThunderModule.
Things are intended to be composable with other early transforms (and other "classic" transforms).

There are functionality gaps left in the FSDP, I would look at updating this once the first test runs and we had a chance to discuss the design. And I'll drop the debug prints, too...

@crcrpar @IvanYashchuk

This builds on #279 , I'll rebase once it is in.

The error is expected because thunder.distributed.prims.synchronize was not meant to be executed with real PyTorch tensors. It's only a Thunder operation to work with Thunder's TensorProxies, it should be replaced with nothing or allgather in the transformations that should happen before "transform_for_execution".
You could register it in the torch executor with "execution_transform" checking the ddp_type attribute and dispatching it to either nothing or allgather like here: https://github.com/Lightning-AI/lightning-thunder/blob/7ac5684e274c9c14336759451add371221011c8b/thunder/distributed/prims.py#L291-L308

@carmocca  makes the following comments on replacing parameters only in the overrides:

I'm not convinced by this because the current implementation doesn't modify the original module, only the parameters. And those need to be modified by reference because to avoid blowing up the memory of course.

What was your motivation for this originally? Do you expect this from transforms in general? For example, if you had a LoRA transform that replaces Linears, wouldn't you expect it to swap the classes?

Which we should look at more closely soon.


bug: PageCache commit sometimes writes a hash-table page twice

Detected spuriously here: https://github.com/thrumdev/nomt/actions/runs/11274332553/job/31353249826?pr=441
This is probably a page-walker bug, since PageCache::commit just operates on the page diffs produced by that.

Moved to Linear


The documentation should mention all manditory scopes

I got an error message validatign my addin which says that I don't have all the manditory scopes defined. THe documentation mentions "profile" at the only alwasy required scope, but the validation tool also says that I need openid.
❯ npm run validate

><EMAIL_ADDRESS>validate ...
> office-addin-manifest validate manifest.xml

The manifest is not valid.

Error # 1:
WebApplicationInfo mandatory Scopes not defined: WebApplicationInfo Scope field does not contain all mandatory values. Please see https://docs.microsoft.com/en-us/office/dev/add-ins/develop/sso-in-office-add-ins for details.
  - Details: Provided Scopes 'User.Read, profile' does not contain all mandatory scopes 'profile, **openid**'

Additional information:
Package Type Identified: Package of your add-in was parsed successfully.

The documentation and the validation tool should agree :-)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cb06c24b-9d11-9cc5-2e98-561601452638
Version Independent ID: abda21d9-6e80-8319-c56f-004658014e3c
Content: Enable single sign-on for Office Add-ins - Office Add-ins
Content Source: docs/develop/sso-in-office-add-ins.md
Product: non-product-specific
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@mattgeim Is it correct that openid is now mandatory? Or is this a bug in the validation tool?

@mattgeim Is it correct that openid is now mandatory? Or is this a bug in the validation tool?

Mandatory @Rick-Kirkham - I'm updating the overview docs and will have a PR shortly.

We've updated the documentation with PR 2110, I will close the issue with the merge that happened today.  Please feel free to reopen if you have any questions.


Nonce Error

Hi, anyone have solution for this ?
api(....................................) 401 unauthorized
{"code":"woocommerce_rest_missing_nonce","message":"Missing the X-WC-Store-API-Nonce header. This endpoint requires a valid nonce.","data":{"status":401}}

Hi, may be very late but I have same issue after update to WooCommerce 9.3.1.
You can Set header nonce key like "Nonce" not "X-WC-Store-API-Nonce" or leave them both


Support for unwrapped Vectors

We have an unsupported test in
rust-tests/cbmc-reg/Vectors/fixme_main.rs

With --unwind 2, CBMC memory usage exceeds 20 GB in a minute.


Increment version and update README.rst

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8061c21). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master      #10   +/-   ##
=========================================
  Coverage          ?   83.07%
=========================================
  Files             ?       11
  Lines             ?      520
  Branches          ?        0
=========================================
  Hits              ?      432
  Misses            ?       88
  Partials          ?        0

Impacted Files
Coverage Δ

src/aws_okta_processor/cli.py
0% <ø> (ø)

src/aws_okta_processor/__init__.py
100% <100%> (ø)

Continue to review full report at Codecov.

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


Use interleaved gradient noise for alpha hashing

This provides a better appearance of transparency and prevents "streaks" from appearing as the camera's distance from the object changes.
PS: We should do a review of the various alpha antialiasing modes, as none of them seem to have a tangible effect, even when MSAA is enabled. This applies to both Alpha Scissor and Alpha Hash modes.
See https://github.com/godotengine/godot-proposals/discussions/4651.
Testing project: test_alpha_hash.zip

Did you try just replacing ``hash_3d` with IGN? I don't think we should be completely replacing the complex alpha hash logic with simple noise.

Did you try just replacing ``hash_3d` with IGN? I don't think we should be completely replacing the complex alpha hash logic with simple noise.

I've tried to replace hash_2d() with IGN (hash_3d() expects a vec3()) but unfortunately, it looks worse and doesn't get rid of the streaking artifacts when the distance between the camera and the material changes:
https://user-images.githubusercontent.com/180032/173370555-b9d1b2f8-99c7-4bbf-b415-4f5df8beb26b.mp4

I don't think this is a good idea. The original implementation uses object-space coordinates to minimize artifacts in motion from the  use of a hash function. This is explained in detail in the original presentation. This change uses a screen-space hash which means that, the hashing of objects won't be stable as the camera moves around them. Edges will flicker and move and the hash function itself may even be visible as it doesn't change from frame to frame.
Instead, we need to look into why the current implementation is behaving badly and fix the bug in it. It worked well when it was first implemented, so we can make it work well again.

Superseded by #68673 which fixes the implementation of alpha hash without altering the hashing function.


(DOCS)DOC-3896: Changing puppet-lookup to puppet lookup

https://tickets.puppetlabs.com/browse/DOC-3896

CLA signed by all contributors.

Is DOC-3896 a public ticket? I can never remember... If it is, then great! Otherwise, we should move it to a public ticket. Referencing private tickets in a public project is a bummer for community members who don't have access

@melissa Good point! Moved it to https://tickets.puppetlabs.com/browse/DOCUMENT-980

Awesome! Thanks for moving that ticket.  If you want any guidance, I'm happy to help out

@hestonhoffman I'm not sure how the docs team handles ticket lifecycles, so I'll leave updating the ticket to you. Thanks for the contribution!