Bug in ReflectionConfigGenerator

I am trying to compile a Java cli app with GraalVM native-image and realized that it emits warnings like WARNING: Method com.example.MyCommand.setVerbosity(boolean[]) not found.
The issue was, that the setVerbosity method was declared as private method in an abstract parent command class, but ReflectionConfigGenerator generates this reflect-config.json
[
  {
    "name" : "com.example.MyCommand",
    "allDeclaredConstructors" : true,
    "allPublicConstructors" : true,
    "allDeclaredMethods" : true,
    "allPublicMethods" : true,
    "methods" : [
      { "name" : "setVerbosity", "parameterTypes" : ["[Z"] }
    ]
  },
  {
    "name" : "com.example.AbstractCommand",
    "allDeclaredConstructors" : true,
    "allPublicConstructors" : true,
    "allDeclaredMethods" : true,
    "allPublicMethods" : true,
    "fields" : [
      { "name" : "commandSpec" }
    ],
    "methods" : [
      { "name" : "setVerbosity", "parameterTypes" : ["[Z"] }
    ]
  }
]

Looking at the ReflectionConfigGenerator I realized that the logic is broken at https://github.com/remkop/picocli/blob/f2f2ac3230b9f6b5f52d159bda515ce805c0be88/picocli-codegen/src/main/java/picocli/codegen/aot/graalvm/ReflectionConfigGenerator.java#L482
I actually believe it should say
if (scope.get().getClass().equals(method.getDeclaringClass())) {

instead of
if (!scope.getClass().equals(method.getDeclaringClass())) {

which always evaluates to true

Thanks for raising this!
I’ll take a look.

I finally have time to look at this. Is my understanding below correct?
Given the code below to reproduce the issue:
package picocli.codegen.aot.graalvm;

import picocli.CommandLine.Command;
import picocli.CommandLine.Model.CommandSpec;
import picocli.CommandLine.Option;
import picocli.CommandLine.Spec;

@Command
public class Issue1274AbstractCommand {
    @Spec
    CommandSpec commandSpec;

    @Option(names = {"-v", "--verbose"})
    private void setVerbosity(boolean[] verbosity) {
    }
}

package picocli.codegen.aot.graalvm;

@picocli.CommandLine.Command
public class Issue1274Command extends Issue1274AbstractCommand {
}

The expected reflect-config.json is:
[
  {
    "name" : "picocli.codegen.aot.graalvm.Issue1274AbstractCommand",
    "allDeclaredConstructors" : true,
    "allPublicConstructors" : true,
    "allDeclaredMethods" : true,
    "allPublicMethods" : true,
    "fields" : [
      { "name" : "commandSpec" }
    ],
    "methods" : [
      { "name" : "setVerbosity", "parameterTypes" : ["[Z"] }
    ]
  },
  {
    "name" : "picocli.codegen.aot.graalvm.Issue1274Command",
    "allDeclaredConstructors" : true,
    "allPublicConstructors" : true,
    "allDeclaredMethods" : true,
    "allPublicMethods" : true,
  }
]

but the reflect-config.json that is actually generated is:
[
  {
    "name" : "picocli.codegen.aot.graalvm.Issue1274AbstractCommand",
    "allDeclaredConstructors" : true,
    "allPublicConstructors" : true,
    "allDeclaredMethods" : true,
    "allPublicMethods" : true,
    "fields" : [
      { "name" : "commandSpec" }
    ],
    "methods" : [
      { "name" : "setVerbosity", "parameterTypes" : ["[Z"] }
    ]
  },
  {
    "name" : "picocli.codegen.aot.graalvm.Issue1274Command",
    "allDeclaredConstructors" : true,
    "allPublicConstructors" : true,
    "allDeclaredMethods" : true,
    "allPublicMethods" : true,
    "methods" : [
      { "name" : "setVerbosity", "parameterTypes" : ["[Z"] }
    ]
  }
]

The Issue1274Command class does not declare a setVerbosity method, so the json for that class should not contain this section:
    "methods" : [
      { "name" : "setVerbosity", "parameterTypes" : ["[Z"] }
    ]

Is that an accurate description of the problem?

Yes, that is the issue I am facing.

Thanks for the confirmation.
I pushed a change that I believe fixes the issue.
This will be included in the upcoming 4.6 release.
Thank you again for raising this!

The fix works. Thanks! Just as a side note, without this fix GraalVM native-images require the option --allow-incomplete-classpath to build without failure.

@sebthom Thanks for letting me know there is a workaround!
I am happy to mention the workaround in the documentation if that makes sense, perhaps in the release notes for 4.6?
(If you can think of a place in the user manual where it would make sense to mention this problem with older picocli versions, and the workaround, we could do that too. I can't think of any off the top of my head, but I have not looked very hard yet.)
:-)


AWS Requirement

Hello Team,
I have a need to convert my configuration to AWS Linux, and was hoping to get confirmation weather this OS is supported with the The Pure Storage OpenMetrics exporter?
Thanks!
Phillip Bruce

@OkieCalUnix Are you planning on using the OME binary in AWS Linux or do you want an AWS Linux-based container to use in Amazon ECS?

We currently running RHEL 7.9 on our VMWare environment, but I am willing to try container one, but our AWS team has recently switched to AWS Linux 2 as the base if we use that one. I'm willing to try an AWS Linux-based container. Just need to ensure I have all the requirements down so we can migrate the RHEL to AWS version.
Thanks for your help

I want to get a response.  I appreciate SDODSLEY's response but have not seen enough to answer my initial question.
What OS is required to run the exporter on AWS?
RHEL 7.9 above or specific release
Ubunto which release
Centos 7.9 above
ECS - What the requirement to run using this AWS feature?
others?
Thanks for taking time to respond.

Hi @OkieCalUnix there's no specific OS requirement. It can be built using Go on any architecture using the makefile https://github.com/PureStorage-OpenConnect/pure-fa-openmetrics-exporter?tab=readme-ov-file#local-development
The container uses alpine linux, and that can be changed by changing the https://github.com/PureStorage-OpenConnect/pure-fa-openmetrics-exporter/blob/master/build/docker/Dockerfile file.
you can use any image in https://hub.docker.com/_/golang

Christopher,
Thanks, I will give AWS Linux 2 a try. But I don't have the patience to compile code. The dependencies vary in how the code is written specifically for a variant. I tried that before with RHEL 7.9, and nothing but grief.  It takes too many cycles to figure out the dependencies. I used to do that over 20+ years ago cause most unix variants had to be in c code. Now, Kernels has drastically changed, and I just stick to using binaries. Now I have to learn another compiler.  I guess c and gcc compilers are getting harder to link the code together.  Since the binaries is already built for RHEL I'll likely go that route.
I would like to see binaries in other flavors if possible.
other suggestions are welcome. I appreciate everyone time and effort in this.
Thanks,

We have our published binaries that I just tested with Amazon Linux 2 and 2023 on AMD64.
https://github.com/PureStorage-OpenConnect/pure-fa-openmetrics-exporter/releases
Under assets, select linux-amd64.tar.gz
if you need other platforms than amd64, please let us know.


Make the prefix for SX1309 configurable

To make it possible to specify for example m_ as prefix instead of _.

The m_ prefix is a violation of SA1308, not SA1309. This means it makes more sense to implement the alternative style as a new rule SX1308.


Add stricter file permissions to comply with CIS DIL 6.2.6.

Fixes #130

This works for me, but I cannot test your specific case @mcgege. Let me know if it still causes issues.

@timstoop Unfortunately this still crashes :-(
I think you have to loop through $folders and make an if !defined File[... to solve this ...

That's weird, ensure_resources docs explicitly state that it should not override already in place resources :/ Could it be that you're deploying the PE stuff after os_hardening?
In any case, it could take a bit before I am able to work on this further, as my conversion project just got some additional priority. (I'm trying to make os_hardening and ssh_hardening enough to no longer fail the cis-dil-benchmark on Debian Stretch. I fully intend to get all my patches accepted upstream, you can follow my progress in my own fork, just look at the branches, I just need to finish it before I can continue creating PRs.)

@mcgege Could it be that you're deploying the PE stuff after os_hardening? Because if that's the case, then there's little I can do to fix your error.

@timstoop I cannot influence this ... this PE stuff is automatically included after os_hardening. Just tried different ideas, but nothing worked ... I think the only way to make this compatible with PE is to skip /usr/local/bin entirely

I'll make that an option in the code.

How do you like this solution? I'm defaulting to a list of the directories as they are mentioned in CIS DIL Benchmark, but I'm happy to remove /usr/local/bin from it if you don't like overriding it. I'm sort of assuming that most puppet users are not use the PE variant, so they wouldn't mind this. Also, I'm not sure if the ensure_resources still adds anything now and I'm considering reverting it to the normal file {} resource. What are your thoughts about that?

@artem-sidorenko What is your opinion here? On Puppet Enterprise you'd need to manually exclude /usr/local/bin from the folders_to_restrict parameter, as there's no way right now to detect PE (is_pe doesn't work any more) ...

@mcgege again this differences between puppet opensource and enterprise :((

On Puppet Enterprise you'd need to manually exclude /usr/local/bin from the folders_to_restrict parameter, as there's no way right now to detect PE (is_pe doesn't work any more) ...

I do not see another way too. Maybe we should have a dedicated section in the README, something like "For puppet enterprise users"

Either that, or we set a global "pe" variable that we can use to change behaviour with. If the fact is no longer working (I honestly didn't know there even was one), then we need to have it set manually. This would be beyond me, though, as we don't use PE I have no way of testing it.

I think this is a very good idea! And hopefully there will a working is_pe flag in the future, or even better: no need for such a bugfix at all :-)

@timstoop I'll take your pr and add this global flag myself

@timstoop @artem-sidorenko Please take a look at #136


Using Cloudflare-only runtime leads to an error during the build step

What version of Remix are you using?
2
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
run npx create-remix --template remix-run/remix/templates/cloudflare-pages
Add app/routes/example.tsx that contains
 import { EmailMessage } from "cloudflare:email";
 export const action = () => {
   console.log(EmailMessage);
   return null;
 };

run npm run build
Expected Behavior
Build succeeds on Cloudflare:
info  built
Actual Behavior
Build fails:
✘ [ERROR] Could not resolve "cloudflare:email"

    app/routes/example.ts:1:29:
      1 │ import { EmailMessage } from "cloudflare:email";
        ╵                              ~~~~~~~~~~~~~~~~~~

  You can mark the path "cloudflare:email" as external to exclude it from the bundle, which will remove this error.

experiencing this with cloudlfare:sockets

Since the build runs on Node it can't access those packages, try to move them to the Cloudflare server file and use getLoadContext to inject them into your Remix app.


Commit change of issue #2548 in current branch

Related issues
https://github.com/DivanteLtd/vue-storefront/pull/2548
Short description and why it's useful
Due to many changes in hotfix branch, I'm creating new pr with hotfix branch
Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility)
[ ] I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

Contribution and currently important rules acceptance

[X] I read and followed contribution rules
[X] I read the TypeScript Action Plan and adjusted my PR according to it
[X] I read about Vue Storefront Modules and I am aware that every new feature should be a module

Related #2556


Add Dragons for Dragons of Nightmare

Ysondre
Emeriss
Lethon
Taerar

Each Dragon can be in any of the 4 locations.

emeriss gray/green
lethon red/grey
taerar blue


import() doesn't honor alias

Do you want to request a feature or report a bug?

bug
What is the current behavior?
import() can't find aliased modules
If the current behavior is a bug, please provide the steps to reproduce.

import("AnyAlias/module")
What is the expected behavior?
It should locate module under the directory defined for the "AnyAlias" alias
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

Thanks for your report. It would be great if you reduce your issue to a small reproducible example. Best put this example into a github repository together with instructions how to get to the problem.


[SPARK-36086][SQL] CollapseProject project replace alias should use origin column name

What changes were proposed in this pull request?
For added UT, without this patch will failed as below
[info] - SHOW TABLES V2: SPARK-36086: CollapseProject project replace alias should use origin column name *** FAILED *** (4 seconds, 935 milliseconds)
[info]   java.lang.RuntimeException: After applying rule org.apache.spark.sql.catalyst.optimizer.CollapseProject in batch Operator Optimization before Inferring Filters, the structural integrity of the plan is broken.
[info]   at org.apache.spark.sql.errors.QueryExecutionErrors$.structuralIntegrityIsBrokenAfterApplyingRuleError(QueryExecutionErrors.scala:1217)
[info]   at org.apache.spark.sql.catalyst.rules.RuleExecutor.$anonfun$execute$2(RuleExecutor.scala:229)
[info]   at scala.collection.LinearSeqOptimized.foldLeft(LinearSeqOptimized.scala:126)
[info]   at scala.collection.LinearSeqOptimized.foldLeft$(LinearSeqOptimized.scala:122)
[info]   at scala.collection.immutable.List.foldLeft(List.scala:91)
[info]   at org.apache.spark.sql.catalyst.rules.RuleExecutor.$anonfun$execute$1(RuleExecutor.scala:208)
[info]   at org.apache.spark.sql.catalyst.rules.RuleExecutor.$anonfun$execute$1$adapted(RuleExecutor.scala:200)
[info]   at scala.collection.immutable.List.foreach(List.scala:431)
[info]   at org.apache.spark.sql.catalyst.rules.RuleExecutor.execute(RuleExecutor.scala:200)
[info]   at org.apache.spark.sql.catalyst.rules.RuleExecutor.$anonfun$executeAndTrack$1(RuleExecutor.scala:179)
[info]   at org.apache.spark.sql.catalyst.QueryPlanningTracker$.withTracker(QueryPlanningTracker.scala:88)

CollapseProject project replace alias should use origin column name
Why are the changes needed?
Fix bug
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added UT

FYI @cloud-fan

Test build #142212 has started for PR 33685 at commit e06f441.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46725/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46725/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46725/

thanks, merging to 3.1!

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142212/


JSON Response with float values gives wrong decimals

Laravel Version: 5.6.9
PHP Version: 7.1.8
Os: OSX using MAMP v4.2.1

Description + Steps To Reproduce::
Hello guys,
I'm trying to do a simple JSON response as follows:
namespace App\Http\Controllers\API;
use App\Http\Controllers\Controller;

class TestController extends Controller {

public function getData()
{
       return response()->json(["data" => 20.51]);
}

}

The output is:
{
    "data": 20.510000000000001563194018672220408916473388671875
}

Which is wrong and I have to truncate all my float values from the frontend.
Any ideas?
Thank you!

I am having the same issue.

You're probably running with default php configuration that is hiding data from you. Use ini_set('precision', 17') to see how your floating point number actually look. Source: https://www.leaseweb.com/labs/2013/06/the-php-floating-point-precision-is-wrong-by-default/
The number of decimals in floating point numbers in json is controlled via another setting, serialize_precision since PHP 7.1 and this RFC. The goal is to send as much data as possible to the client to avoid rounding errors.
There's nothing in this issue that relates to Laravel.

Maybe a little late but I also had the same problem, I answered it here.
https://stackoverflow.com/a/64413695/11567022

I know I'm late, but here's a very simple solution.
Just format the number with number_format() function , it won't be affected by response()->json() function.


Optimized nativeImage fails with flyway

Expected Behavior
Optimized native image works.
Actual Behaviour
./gradlew :app:nativeOptimizedCompile

> Task :app:prepareNativeOptimizations
20:05:02.382 [main] INFO  i.m.context.env.DefaultEnvironment - Established active environments: [dev]
20:05:02.554 [main] INFO  i.m.aot.MicronautAotOptimizer - Detected environments: [dev]
20:05:02.676 [main] INFO  i.m.a.s.s.YamlPropertySourceGenerator - Converting application.yml into Java based configuration
20:05:02.683 [main] INFO  i.m.a.s.s.YamlPropertySourceGenerator - Converting application-dev.yml into Java based configuration
20:05:02.690 [ForkJoinPool.commonPool-worker-5] INFO  i.m.a.s.s.YamlPropertySourceGenerator - Converting application.yml into Java based configuration
20:05:02.693 [ForkJoinPool.commonPool-worker-5] INFO  i.m.a.s.s.YamlPropertySourceGenerator - Converting application-dev.yml into Java based configuration

> Task :app:nativeOptimizedCompile
[native-image-plugin] Using executable path: /Users/sdelamo/.sdkman/candidates/java/21.3.0.r17-grl/bin/native-image
[app:16653]    classlist:   1,805.81 ms,  0.94 GB
[app:16653]        (cap):   2,320.69 ms,  0.94 GB
[app:16653]        setup:   5,770.51 ms,  1.18 GB
[app:16653]     (clinit):   1,931.96 ms,  7.82 GB
[app:16653]   (typeflow):   6,346.67 ms,  7.82 GB
[app:16653]    (objects):  41,342.53 ms,  7.82 GB
[app:16653]   (features):  10,098.99 ms,  7.82 GB
[app:16653]     analysis:  63,860.40 ms,  7.82 GB
[app:16653]     universe:   4,612.64 ms,  7.82 GB
[app:16653]      (parse):   2,833.94 ms,  7.58 GB
[app:16653]     (inline):   6,060.04 ms,  6.64 GB
[app:16653]    (compile):  27,100.80 ms,  6.86 GB
[app:16653]      compile:  39,966.46 ms,  6.86 GB
[app:16653]        image:   5,164.13 ms,  6.88 GB
[app:16653]        write:   1,765.64 ms,  6.88 GB
[app:16653]      [total]: 123,177.00 ms,  6.88 GB
# Printing build artifacts to: /Users/sdelamo/github/micronaut-advocacy/micronaut-live-newsletter/app/build/native/nativeOptimizedCompile/app.build_artifacts.txt
[native-image-plugin] Native Image written to: /Users/sdelamo/github/micronaut-advocacy/micronaut-live-newsletter/app/build/native/nativeOptimizedCompile

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.2/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 2m 16s
6 actionable tasks: 3 executed, 3 up-to-date
sdelamo@ig11 micronaut-live-newsletter % ./app/build/native/nativeOptimizedCompile/app
 __  __ _                                  _
|  \/  (_) ___ _ __ ___  _ __   __ _ _   _| |_
| |\/| | |/ __| '__/ _ \| '_ \ / _` | | | | __|
| |  | | | (__| | | (_) | | | | (_| | |_| | |_
|_|  |_|_|\___|_|  \___/|_| |_|\__,_|\__,_|\__|
  Micronaut (v3.2.3)

20:07:36.892 [main] INFO  i.m.context.env.DefaultEnvironment - Established active environments: [dev]
20:07:36.897 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
20:07:36.911 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
20:07:36.912 [main] INFO  i.m.flyway.AbstractFlywayMigration - Running migrations for database with qualifier [default]
20:07:36.915 [main] INFO  o.f.c.i.license.VersionPrinter - Flyway Community Edition 8.0.2 by Redgate
20:07:36.915 [main] INFO  o.f.c.i.d.base.BaseDatabaseType - Database: jdbc:postgresql://localhost:5432/postgres (PostgreSQL 11.5)
20:07:36.932 [main] ERROR io.micronaut.runtime.Micronaut - Error starting Micronaut server: Bean definition [javax.sql.DataSource] could not be loaded: Unable to obtain inputstream for resource: db/migration/V1__create-subscriber-table.sql
io.micronaut.context.exceptions.BeanInstantiationException: Bean definition [javax.sql.DataSource] could not be loaded: Unable to obtain inputstream for resource: db/migration/V1__create-subscriber-table.sql
	at io.micronaut.context.DefaultBeanContext.initializeContext(DefaultBeanContext.java:1938)
	at io.micronaut.context.DefaultApplicationContext.initializeContext(DefaultApplicationContext.java:237)
	at io.micronaut.context.DefaultBeanContext.readAllBeanDefinitionClasses(DefaultBeanContext.java:3453)
	at io.micronaut.context.DefaultBeanContext.finalizeConfiguration(DefaultBeanContext.java:3883)
	at io.micronaut.context.DefaultBeanContext.start(DefaultBeanContext.java:329)
	at io.micronaut.context.DefaultApplicationContext.start(DefaultApplicationContext.java:183)
	at io.micronaut.runtime.Micronaut.start(Micronaut.java:72)
	at io.micronaut.live.Application.main(Application.java:39)
Caused by: org.flywaydb.core.api.FlywayException: Unable to obtain inputstream for resource: db/migration/V1__create-subscriber-table.sql
	at org.flywaydb.core.internal.resource.classpath.ClassPathResource.read(ClassPathResource.java:118)
	at org.flywaydb.core.internal.resolver.ChecksumCalculator.calculateChecksumForResource(ChecksumCalculator.java:64)
	at org.flywaydb.core.internal.resolver.ChecksumCalculator.calculate(ChecksumCalculator.java:43)
	at org.flywaydb.core.internal.resolver.sql.SqlMigrationResolver.getChecksumForLoadableResource(SqlMigrationResolver.java:123)
	at org.flywaydb.core.internal.resolver.sql.SqlMigrationResolver.addMigrations(SqlMigrationResolver.java:165)
	at org.flywaydb.core.internal.resolver.sql.SqlMigrationResolver.resolveMigrations(SqlMigrationResolver.java:71)
	at org.flywaydb.core.internal.resolver.sql.SqlMigrationResolver.resolveMigrations(SqlMigrationResolver.java:50)
	at org.flywaydb.core.internal.resolver.CompositeMigrationResolver.collectMigrations(CompositeMigrationResolver.java:107)
	at org.flywaydb.core.internal.resolver.CompositeMigrationResolver.doFindAvailableMigrations(CompositeMigrationResolver.java:90)
	at org.flywaydb.core.internal.resolver.CompositeMigrationResolver.resolveMigrations(CompositeMigrationResolver.java:83)
	at org.flywaydb.core.internal.resolver.CompositeMigrationResolver.resolveMigrations(CompositeMigrationResolver.java:41)
	at org.flywaydb.core.internal.info.MigrationInfoServiceImpl.refresh(MigrationInfoServiceImpl.java:92)
	at org.flywaydb.core.internal.command.DbValidate$2.call(DbValidate.java:153)
	at org.flywaydb.core.internal.command.DbValidate$2.call(DbValidate.java:140)
	at org.flywaydb.core.internal.jdbc.TransactionalExecutionTemplate.execute(TransactionalExecutionTemplate.java:55)
	at org.flywaydb.core.internal.command.DbValidate.validate(DbValidate.java:140)
	at org.flywaydb.core.Flyway.doValidate(Flyway.java:380)
	at org.flywaydb.core.Flyway.access$100(Flyway.java:53)
	at org.flywaydb.core.Flyway$1.execute(Flyway.java:126)
	at org.flywaydb.core.Flyway$1.execute(Flyway.java:121)
	at org.flywaydb.core.FlywayExecutor.execute(FlywayExecutor.java:208)
	at org.flywaydb.core.Flyway.migrate(Flyway.java:121)
	at io.micronaut.flyway.AbstractFlywayMigration.runFlyway(AbstractFlywayMigration.java:100)
	at io.micronaut.flyway.AbstractFlywayMigration.forceRun(AbstractFlywayMigration.java:85)
	at io.micronaut.flyway.AbstractFlywayMigration.run(AbstractFlywayMigration.java:65)
	at io.micronaut.flyway.DataSourceMigrationRunner.lambda$null$0(DataSourceMigrationRunner.java:65)
	at java.util.Optional.ifPresent(Optional.java:178)
	at io.micronaut.flyway.DataSourceMigrationRunner.lambda$onCreated$1(DataSourceMigrationRunner.java:63)
	at java.util.Optional.ifPresent(Optional.java:178)
	at io.micronaut.flyway.DataSourceMigrationRunner.onCreated(DataSourceMigrationRunner.java:60)
	at io.micronaut.flyway.DataSourceMigrationRunner.onCreated(DataSourceMigrationRunner.java:37)
	at io.micronaut.context.DefaultBeanContext.doCreateBean(DefaultBeanContext.java:2393)
	at io.micronaut.context.DefaultBeanContext.createAndRegisterSingletonInternal(DefaultBeanContext.java:3281)
	at io.micronaut.context.DefaultBeanContext.createAndRegisterSingleton(DefaultBeanContext.java:3267)
	at io.micronaut.context.DefaultBeanContext.loadContextScopeBean(DefaultBeanContext.java:2653)
	at io.micronaut.context.DefaultBeanContext.initializeContext(DefaultBeanContext.java:1932)
	... 7 common frames omitted

Steps To Reproduce
Clone micronaut-advocacy/micronaut-live-newsletter aot branch.
Open one terminal and run PostgreSQL:
docker run -it --rm -p 5432:5432 -e POSTGRES_USER=dbuser -e POSTGRES_PASSWORD=theSecretPassword -e POSTGRES_DB=postgres postgres:11.5-alpine

Open another terminal:
 export DATASOURCES_DEFAULT_USERNAME=dbuser
export DATASOURCES_DEFAULT_PASSWORD=theSecretPassword
./gradlew :app:nativeOptimizedCompile
./app/build/native/nativeOptimizedCompile/app

Environment Information
Note it works with regular native image.
./gradlew :app:nativeCompile
./app/build/native/nativeCompile/app

Example Application
https://github.com/micronaut-advocacy/micronaut-live-newsletter
Version
3.2.3

mmm, are you using 1.0.0-M4 ?

Actually this is https://github.com/graalvm/native-build-tools/pull/182 which will require the GraalVM plugin 0.9.9 which should be out this week.

Actually this is graalvm/native-build-tools#182 which will require the GraalVM plugin 0.9.9 which should be out this week.

I added the awaiting-third-party flag. I assume this will require a new release of Micronaut Application plugin?

I assume this will require a new release of Micronaut Application plugin?

Correct, so if you want to squeeze some doco changes ;)


In the latest version something weird is going on with js.Build resolve

What version of Hugo are you using (hugo version)?
Hugo Static Site Generator v0.78.1/extended darwin/amd64 BuildDate: unknown
Does this issue reproduce with the latest release?
I am compiling some js code with "js.Build"
I have a file called "util.js" which I import using import { method } from "./util" and then I am also import the npm module "url" from "npm install url" using import { parse } from "url". Inside of the url module there is also an import from "./util" and it's getting resolved to my util.js module and causing crashes. This seems to indicated it's resolving modules by names and not resolved paths.

The code works if I rename my local file "utilities", so I think that seems to validate the name import.

OK, it looks like it's some odd going on with the . imports that needs a fix. Thanks for the report.


NIFI-7943 - Implement application properties for Event Hub messages

Description of PR
EventData coming from the Event Hub bus may contain application properties. These could be useful in NiFi to determine
what kind of processing to execute.
This PR introduces the application properties in the flow as eventhub.property.*. For example, the property application would
be available in the flow as attribute eventhub.property.application.
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[X] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[X] Have you verified that the full build is successful on JDK 11?

Squashed -- properly this time.


Fixed OSX CPU utilization by replacing broken kevent() with select()

Current kevent() implementation in SoftEther is broken.  It always exits with -1.
This causes 100% CPU utilization during connected session.
Attached select() implementation of the same functionality.
Now the CPU usage is normal.
Please use (Contribution option (1))

Your great patch is much appreciated. We are considering to apply your patch into the SoftEther VPN main tree.
SoftEther VPN Patch Acceptance Policy:
http://www.softether.org/5-download/src/9.patch
You have two options which are described on the above policy.
Could you please choose either option 1 or 2, and specify it clearly on the reply?

Thank you so much for your contribution to enrich the SoftEther VPN source code.
Your patch has been merged on the main source-tree of SoftEther VPN.
As a token of our gratitude, your GitHub username has been added on the AUTHORS.TXT file and on the header of the related source file.
Please see: https://github.com/SoftEtherVPN/SoftEtherVPN/blob/master/AUTHORS.TXT
Thanks again for your contribution.


fix: parameter 'camera_wb_red' cannot be set

Fixes wrong naming of two camera parameters which caused the driver to crash with error for color cameras:
./rc_genicam_driver
[INFO] [1701701004.566275110] [genicam_driver]: Initializing
[INFO] [1701701004.566460410] [genicam_driver]: Processing thread started
[INFO] [1701701004.566502296] [genicam_driver]: Configuring
[INFO] [1701701007.695882081] [genicam_driver]: Connecting to sensor '<REDACTED>' alias rc_visard 160c
[INFO] [1701701010.121517660] [genicam_driver]: Start streaming images
[ERROR] [1701701010.773342531] [genicam_driver]: parameter 'camera_wb_red' cannot be set because it was not declared
[INFO] [1701701013.773845873] [genicam_driver]: Cleanup

Thx!


Disable renaming public rooms if the current user is not an admin or the creator of the linked workspace

Details

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/266085
Tests
(if you're using the web proxy, just follow the QA steps instead)

Create a new workspace and create a new room with public visibility on that workspace (FAB > "New Room"). Save the reportID.
Sign out of the account that created the workspace, and sign into a different account that isn't in the workspace.
Navigate to the report from [1] (i.e. localhost:8080/r/<reportID) > Settings.
Verify that you are unable to update the report name.

[ ] Verify that no errors appear in the JS console

Offline tests

QA Steps

Sign in the with following account<EMAIL_ADDRESS>(password asdfASDF00)
Navigate to the following report: https://new.expensify.com/r/6794758698552692
Go to the report details. Verify that you are unable to modify the report name.

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@eVoloshchak @bondydaa One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@eVoloshchak I've updated the testing steps, you don't need that script anymore.

Do I need my account to be added to the policy rooms beta on dev for this to work?
Yes! I'll add that to the testing steps.

Gonna ask for more reviews since we want to get this deployed before Friday

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

After you correct the name here: https://github.com/Expensify/App/pull/15688/files#r1130755483, I'll approve.

Added a commit to this while Jasper is OOO, please give this a review (we want this out before ECX)

Okay tested locally, good to go cc @MonilBhavsar or @aldo-expensify

@bondydaa @aldo-expensify @thienlnam Thank you guys for keeping this moving while I've been out. I have literally been asleep all day 😢
fixed the conditions and consolidated the logic as stated in your review comments, good for another look!

@bondydaa @aldo-expensify @thienlnam Thank you guys for keeping this moving while I've been out sick. I have literally been in bed all day 😢
fixed the conditions and consolidated the logic as stated in your review comments, good for another look!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


Staging of v1.1.0

From discussion in #366 and at the workshop, it looks like the most reasonable option is to release v1.1.0 and skip v1.0.1. This PR stages those changes.

I have just bumped the version number in this PR (i.e. develop) to 1.1.0, so this is now ready for a final review and release.
@rartino: in the wiki release instructions, it talks about doing a -ff-only merge locally. I think this is equivalent to a GitHub PR rebase+merge, which I think is preferable...

@rartino: in the wiki release instructions, it talks about doing a -ff-only merge locally. I think this is equivalent to a GitHub PR rebase+merge, which I think is preferable...

I think the instructions were devised by @CasperWA originally, and were created before GitHub had these merge options. However, reading the documentation, I'm actually not sure that 'Rebase and merge' would be equivalent, because the documentation says the commit hashes will be updated, which we would like to avoid.

I think the instructions were devised by @CasperWA originally, and were created before GitHub had these merge options. However, reading the documentation, I'm actually not sure that 'Rebase and merge' would be equivalent, because the documentation says the commit hashes will be updated, which we would like to avoid.

I'm 90% sure that GitHub will do a ff-only rebase when the history is linear (as it is here) but I will triple check in another repo. The GitHub docs do allude to this too. Let's see what @CasperWA  says.

I'm 90% sure that GitHub will do a ff-only rebase when the history is linear (as it is here) but I will triple check in another repo.

They indeed say that the merge is done fast-forward:
When you select the Rebase and merge option on a pull request on GitHub, all commits from the topic branch (or head branch) are added onto the base branch individually without a merge commit. Pull requests with rebased commits are merged using the fast-forward option. [...]
However, this other paragraph just below makes it sound as if that fast-forward is done using re-written (rebased) commits with different hashes:
The rebase and merge behavior on GitHub deviates slightly from git rebase. Rebase and merge on GitHub will always update the committer information and create new commit SHAs, whereas git rebase outside of GitHub does not change the committer information when the rebase happens on top of an ancestor commit.

Final steps:

I've written a little script to check all external links in the specification, we might consider adding this (or something similar) to the CI.
The release will need release notes: I think it makes sense to also add these to a top-level CHANGELOG.md in this repository (I believe this was discussed at one point, but not actioned upon). I will copy the notes from 1.0.0 and write new ones for 1.1 in a new PR, so we will need one more round of reviews for this.
Once this PR is approved again, I will locally merge the branch.

Proceeding with the local merge... wish me luck!

:tada:


services/keystore: improve health endpoint.

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.
[ ] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[ ] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[ ] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

What
In the /health endpoint, use the PassHandler in the support/render/health package to replace the handler implemented in the keystore itself.
Why
Already described above.
Known limitations
[N/A]

@howardtw

Can you make the What and Why more clear in the description and in the commit message when you merge it?

I have edited the PR description, would you mind to use squash to process it during the merge, thanks.

Out of curiosity, do you plan on using the keystore?

No, I didn't notice the existence of the recoverysigner at first.

@howardtw

Can you make the What and Why more clear in the description and in the commit message when you merge it?

I have edited the PR description, would you mind to use squash to process it during the merge, thanks.

Out of curiosity, do you plan on using the keystore?

No, I didn't notice the existence of the recoverysigner at first.


Add artifact components

[x] mini map for geojson artifacts
[x] bar chart for data frame (dist-alerts-tool data)

@oliverroick I got the bar chart and mini map working, but couldn't get the tooltip for the bar chart to work yet

@oliverroick I added some simple state management using jotai which is like useContext but with less boilerplate. Now we can show the mini map objects on the main map.


Add relations in GraphQL for orgchart.

Coverage decreased (-0.1%) to 86.943% when pulling afb647ae8839d0996ab594608c3cb05c5baaa23b on akatsoulas:graphql-relations into 1d6a8035d0eb1f1bab113db7c480829959634746 on mozilla:dino-park.


Autoload all /.story.js$/

Instead of having consumers require every story file, we can do a glob-pattern match and auto-load.
This is consistent with how tools like jest work.

Another common idiom I see is *.stories.js, but I'd be happy if we agree on a single naming scheme.

IMO it should be able to load any of:
*.stories.js, *.story.js, story.js, stories.js

I would rather have an addon that auto loads all my stories when instructed rather than have this behaviour applied by default

I think the *.jsx extension should be added as well.

If we talk about add this pattern to "getstorybook" as default, I think It's great. It allows people to start writing stories just after adding storybook to their project but also lefts flexibility of manual customization

I'm gonna toss it into the cli.

@danielduan that sounds great!
In #1209 I'd also like the visit the idea of configuring this in a config, much like how you set a testPattern for jest.

Works in 3.3.0-alpha.4

Is there any reason for react-native not to be affected by this change ?


Statics within Django admin panel

BUG: fix styles within Django admin panel.

There was a problem with apache configuration - it was pointing to static directory inside volontulo app instead to global, project static. It shoul server statics properly right now.


403 Forbidden

Environment

Operating System: Linux
Node Version:     v16.14.2
Nuxt Version:     3.4.3
Nitro Version:    2.4.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules, i18n
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
repo: https://stackblitz.com/edit/nuxt-starter-dylnd8
Describe the bug
When use defineI18nLocale dynamically load locale messages, it would happen 403 Forbidden error.

Looks like a path splicing error.

Additional context
No response
Logs
No response

Look like is this function error loadPrecompiledMessages.

I'm fixing now at #2048

I've fixed this issue.
Please check edge channel 8.0.0-beta.11-28059008.d1499b6 version.
Thanks!

So nice!It work fine.


I’ve never been able to make this plugin work

The plugin is installed and enabled.
But nothing works.
@today doesn’t insert the date
Neither does @Today
I just uninstalled and reinstalled.
Nada.

Can you tell me if there are any errors showing up in the developers console? What version of Obsidian are you using and which OS are you on?

I’m seeing what sounds like the same issue, which is with autosuggest.

plugin is installed and enabled
no other 3rd party plugins are installed
command palette commands are available, and they work
“Enable Date Autocorrect” is enabled in settings
Trigger phrase is set to @

But typing @ doesn’t bring up the autosuggest menu, typing @today and doesn’t insert the current date. I tried changing the trigger phrase (to ~ and then to $) but it didn’t fix the issue.
I’m using latest version of Obsidian (1.0.4) on iPad and iPhone, not MacOS. Is there an iOS developer console I can access? Or anything else I can do to help diagnose the issue?

If that is the case, I'll close this in favor of #52


Version 0.8.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.507%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
198

Relevant Lines:
201

💛  - Coveralls


Manage Seach Grid too small

Issue Type: Bug

Connect DB
Select Manage
Can't read the search grid

Azure Data Studio version: azuredatastudio 1.18.1 (5b3b97f4a34018f3b37b0fce30e32f2af7ad78fa, 2020-05-26T21:11:42.467Z)
OS version: Darwin x64 18.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 x 2600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
32.00GB (7.57GB free)

Process Argv
-psn_0_1069317

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

vscodeintellicode
Vis
1.2.1

I think the issue might be a possible corrupt profile caused by an extension.  I will let you know once I do a fresh install.

@johnstontrav , have you customized the database widgets before? to check it:

from main menu -> View

Command Palette...

Run command: Preferences: Open User Settings

search for dashboard.database.widgets

and click 'Edit in settings.json'

do you have this settings edited there? if so, you can update the sizeX and SizeY of the Search widget, the new default value is now SizeX:3 SizeY:2 as shown in my screenshot above, you might still have the old default value.

WOW!!! thanks @alanrenmsft I have been trying to hunt this down for ages!

WOW!!! thanks @alanrenmsft, It work!!

@JorgeTorselli and @johnstontrav , just curious, was the dashboard customization done by you directly or by installing some other extensions?

I just use the dashboard as it is no third party installations, I don´t like the SQL Search from Red Gate, it is better on MSSQL, and here just using it...

@alanrenmsft it was just the default.

Yes just the default...


Async Zarr blog date

This says 2022-12-03, but maybe it should be 2022-12-02?
https://github.com/martindurant/martindurant.github.io/blob/18762d36974bf60e9a953629f88c26fa854f7b0b/Martin Durant/content/blog/async-zarr/contents.lr#L5

I haven't advertised it yet, incase anyone in the zarr group wants to comment.

Ah ok. So this is the date it official ships?

We'll see. I conservatively tend to put the date a day or so in the future, just in case, but it can always be edited.


Add precompilation workload

MWE:
using GeoStatsTransforms
using GeoTables, Meshes
using Random; Random.seed!(123)

n = 100
polys = rand(PolyArea, n) |> Shadow("xy")
gtb = georef((; a=rand(n)), polys)
@time gtb |> Rasterize(100, 100)

main:
julia> @time gtb |> Rasterize(100, 100);
 13.864023 seconds (32.96 M allocations: 2.069 GiB, 4.15% gc time, 98.95% compilation time)

julia> @time gtb |> Rasterize(100, 100);
  0.124126 seconds (2.49 M allocations: 85.001 MiB)

PR:
julia> @time gtb |> Rasterize(100, 100);
  1.185075 seconds (3.69 M allocations: 174.250 MiB, 3.70% gc time, 88.90% compilation time)

julia> @time gtb |> Rasterize(100, 100);
  0.146665 seconds (2.24 M allocations: 77.618 MiB, 18.83% gc time)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.94%. Comparing base (5589f29) to head (b24cf3e).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #48      +/-   ##
==========================================
+ Coverage   94.82%   94.94%   +0.12%
==========================================
  Files          19       20       +1
  Lines         811      831      +20
==========================================
+ Hits          769      789      +20
  Misses         42       42

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


[feat] Port graceful shutdown and connections draining into go-template

📝 Summary
This PR:

Adds a stub of HTTP server with the following implemented features:

Health-check endpoint
Graceful shutdown
Drain/undrain endpoints

⛱ Motivation and Context
Recently we needed to implement graceful shutdown and draining in our rpc-endpoint in order to avoid (short) downtimes during the upgrades (please see the links below).
The idea is to port this solution into the template project.
📚 References

https://github.com/flashbots/rpc-endpoint/pull/114
https://github.com/flashbots/rpc-endpoint/pull/115

✅ I have run these commands

[x] make lint
[x] make test
[x] go mod tidy

@metachris I believe I addressed all of your comments.  could you please have another look?


Add copy-pasteable instructions for Ubuntu LTS

Closing this because we are not going to support 20.04 LTS.


Intro tutorials for About API use cases

Develop some vendor agnostic intro tutorials about the About API that can be easily digested as part of a generic documentation push. I think it would be useful to tie them to some common use cases as suggested below.

About API for storing cluster name and sending as prometheus label in your metrics instrumentation
About API for storing arbitrary, implementation specific cluster properties following the rules listed here and discussed on this slide, possibly a cluster's network name, region, etc

/help

/assign

Hello @lauralorenz,
would something like this be sufficient for the second point?
Regarding an example using metrics, should we present code snippets on how to append the ClusterProperty into the metrics via the Kubernetes Go-Client?
Simple Example for About-API
This example will guide you through the setup and usage, demonstrating how to effectively leverage ClusterProperty to enhance your Kubernetes operations.
Assume you are running multiple Kubernetes clusters. Each clusters has a main purpose e.g. ClusterBootstrapping via CAPI, running your business applications. In order to assign each clusters main purpose as ClusterProperty follow the below example.
ClusterProperty
When choosing a name for the ClusterProperty CR consider the following:

Name must have a suffix as below
Cannot use the reserved *k8s.io or *.kubernetes.io suffix
Do not conflict with the well-known CluserProperties

# Simple Usecase Example
apiVersion: about.k8s.io/v1alpha1
kind: ClusterProperty
metadata:
  name: usecase.example.com
spec:
  value: webserver

Examples
# Owner Example
apiVersion: about-api.k8s.io/v1
kind: ClusterProperty
metadata:
  name: owner
spec:
  value: DevOps-Team

# Compliance Example
apiVersion: about-api.k8s.io/v1
kind: ClusterProperty
metadata:
  name: compliance
spec:
  value: PCI-DSS

# Environment Example
apiVersion: about-api.k8s.io/v1
kind: ClusterProperty
metadata:
  name: environment
spec:
  value: production


Unable to abstract over Pool and Transaction

I've been fighting with this for some time now, and I've only been able to manage partial solutions. I have not reached a full solution for what should logically be possible.
I understand there is a fundamental difference between a pool and a transaction. A pool can spawn multiple connections which would be reasonable to schedule as separate async blocks running in parallel. A transaction is a single connection which cannot support parallel execution. However, given the common pattern of async and then immediately await before the next async, it should be able possible to use a transaction the same as a pool in that scenario.
What I've found that works is:
pub async fn foo(conn: &mut PgConnection) -> Result<i32, sqlx::Error> {
    sqlx::query("SELECT 1 AS v")
        .map(|row: PgRow| row.get("v"))
        .fetch_one(conn)
        .await
}

let pool: PgPool;
let pool_conn = &mut *pool.acquire().await?;
let mut tx = pool.begin().await?;

foo(pool_conn).await();
foo(pool_conn).await();

foo(&mut tx).await();
foo(&mut tx).await();

Despite being able to call the foo function multiple times, the limitation here is the &mut PgConnection inside foo can only be used once. When you call fetch_one, it gets derefed and moved internally. There's an idea where you can abstract over Acquire<Connection = Connection<Postgres>> so you can pass in something that can acquire a connection, but pools implement Acquire for PoolConnection which is different from Connection. I have not found a way to smooth over that discrepancy.

Firstly, you can avoid the consumption of the &mut PgConnection if you reborrow:
pub async fn foo(conn: &mut PgConnection) -> Result<i32, sqlx::Error> {
    sqlx::query("<do something else>")
        .execute(&mut *conn)
        .await?;

    sqlx::query("SELECT 1 AS v")
        .map(|row: PgRow| row.get("v"))
        .fetch_one(&mut *conn)
        .await?
}

Secondly, if you use `impl Acquire<Database = Postgres>` (so don't constrict the `Connection` associated type) then you should be able to use either:

```rust
pub async fn foo(conn: impl Acquire<Database = Postgres>) -> Result<i32, sqlx::Error> {
    // no-op for `PgConnection`, `Transaction`
    let mut conn = conn.acquire().await?;

    sqlx::query("SELECT 1 AS v")
        .map(|row: PgRow| row.get("v"))
        .fetch_one(conn)
        .await
}


Update create-external-load-balancer.md

Change mention of VMs to Pods to avoid confusion.
Assuming the external Load Balancer is programmed with IP:PORT of exposed Services.

This change is

@Qvazar Looks like you need to sign the licence agreement.

@Qvazar Please sign the license agreement.

Signed

/retest

seems like CLA is not detected. @Qvazar could you please check it ?

In the interest of moving this small change forward, I'm going to create a duplicate.
Duplicate of #6022.


Defective import of GMV cell type 'general' if all points lie in the same plane

VisIt 2.6.1 (and earlier releases) incorrectly imports the attached file in GMV ASCII format, 2dexample.hangingnodes.gmv. It seems GMV cell type 'general', if consisting of merely 1 face, is treated wrongly: non-convex elements are created, some elements are even missing. See snapshot (visit0000.png) attached. The file itself has valid syntax and the original GMV viewer version 4.5 imports it correctly. See snapshot file correct.rendering.png
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 1376
Status: Resolved
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: Defective import of GMV cell type 'general' if all points lie in the same plane
Assigned to: Brad Whitlock
Category: -
Target version: 2.7
Author: Karl Knig
Start: 03/12/2013
Due date:
% Done: 100%
Estimated time:
Created: 03/12/2013 04:45 pm
Updated: 05/03/2013 06:24 pm
Likelihood: 2 - Rare
Severity: 4 - Crash / Wrong Results
Found in version: 2.6.1
Impact:
Expected Use:
OS: Linux
Support Group: Any
Description:
VisIt 2.6.1 (and earlier releases) incorrectly imports the attached file in GMV ASCII format, 2dexample.hangingnodes.gmv. It seems GMV cell type 'general', if consisting of merely 1 face, is treated wrongly: non-convex elements are created, some elements are even missing. See snapshot (visit0000.png) attached. The file itself has valid syntax and the original GMV viewer version 4.5 imports it correctly. See snapshot file correct.rendering.png
Comments:
A related GMV fix that I made also fixes this problem. When I plotted the attached GMV file, I get the right picture now.

1384_2dexample.hangingnodes.gmv.zip


Update all dapp dependencies to the latest web / algob version (1.2)

Updated algob version in /htlc
fix yarn add @algo-builder/web in https://github.com/scale-it/algo-builder/pull/442

Please add web package as a dependency in shop template

Wanted to do so. But yarn add @algo-builder/web is not working. PR is mentioned in description.
We cannot add web package until the fix is merged to master & released.


Is it support ES6?

when i using ES6 let and run bundle exec rake webpack:compile.. An error occurred

when i change let to var and run bundle exec rake webpack:compile  It through

but when i using webpack --config config/webpack.config.js to compile let or var，it both throungh..

Therefore，I guess that use bundle exec rake webpack:compile unsupport ES6 sentence？

I found the reason, because uglifyJS does not support ES6..
when i create a file...babelrc and add content
{
  "presets": [
    ["stage-2"],
    ["es2015",  {"modules": false}]
  ],
  "plugins": ["transform-runtime"],
  "comments": false,
  "env": {
    "test": {
      "plugins": [ "istanbul" ]
    }
  }
}

fixed this question..


Added new searchFieldDecoration

Added new searchFieldDecoration to customize the decoration of the search field

@iabdousd Thank you for your contribution but customize search text field was implemented in theme. Released in v2.0.18.
showCurrencyPicker(
  context: context,
  theme: CurrencyPickerThemeData(
    // Optional. Styles the search field.
    inputDecoration: InputDecoration(
      labelText: 'Search',
      hintText: 'Start typing to search',
      prefixIcon: const Icon(Icons.search),
      border: OutlineInputBorder(
        borderSide: BorderSide(
          color: const Color(0xFF8C98A8).withOpacity(0.2),
        ),
      ),
    ),
  ),
  onSelect: (Currency currency) {
    print('Select currency: ${currency.name}');
  },
);


Add a FAQ

This gives us a place to collect great questions and their helpful answers in one place until #331 is hammered out.
I went through all the issues labeled with doc and quoted like the wind to get it jump started.
Here are the issues that I think are resolved with this PR, because they were kept open in order to get the question documented:

#376
#371
#216
#206

Suggestion, since this question comes in very frequently in #vendor:
## Should I commit my vendor directory?

Committing the vendor directory is totally up to you. There is no generally applicable advice. Pros: it's the only way to get truly reproducible builds, as it guards against upstream renames and deletes; and you don't need an extra `dep ensure` step on fresh clones to build your repo. Cons: your repo will be bigger, potentially a lot bigger; and PR diffs are more annoying.

Okeedokee!

Taken another crack at explaining why dep ensure -update didn't work as expected. If I am still getting it wrong, I vote for either removing it for now or you giving me the exact verbiage to use in the FAQ for this question. 😀
Added @peterbourgon 's "Should I commit my vendor directory"?
Updated answer to reflect new behavior for "revision is not a tree"
Added caveats to dep vs. go get

Cool. I'm gonna merge this as it stands now, then push up some more tweaks tonight :)

thanks!


prow/jobs/infra: fix label-sync jobs

The label-config configmap is in the prow namespace and the prowjob runs in the default namespace.
Let's avoid using a configmap altogether and derive labels.yaml from the cloned infra repo.

/ok-to-test
/lgtm
/approve


goreleaser config and RPM+DEB packages

goreleaser.yml and dist directory have been added. dist directory contains RPM and DEB packages.

Thanks a lot for this. Added a small comment
Could we not upload the dist folder here? I think only the goreleaser.yml file is fine and then we build it in the CI later

And could we have some documentation on how to actually use this configuration?

Docs here: https://github.com/geteduroam/linux-app/wiki/Development-info


fix(expo): Revert node-linker=hoisted change

This PR reverts the removal of the .npmrc file because eas-cli doesn't play well with pnpm yet.
See more at https://github.com/t3-oss/create-t3-turbo/issues/867
Tried public-hoist-pattern with expo and eas-cli, but the eas build command still fails because it cannot locate the metro config, a dead end.

Awesome thank you for looking into this @VaniaPopovic
Hopefully eas adds support soon as I've been looking forward to nuking the .npmrc file for a while 😅


fix: articles/machine-learning/team-data-science-process/explore-data-blob.md

Add code fence blocks and languages

@nschonni : Thanks for your contribution! The author, @marktab, has been notified to review your proposed change.

#sign-off

#sign-off

@cjgronlund: I'm sorry - only the author of this article, @marktab, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off


"Real time" testing

I'm stuck.. Can I with CodeceptJS and webdriverio test web chat: in one browser enter message and in another two check this message appears? Is this possible?
thanks.

What you ask is multisession testing. It's not available right now in CodeceptJS. But I think it is possible (somehow) with webdriverio.
I think that's important feature for CodeceptJS to implement...

add AnotherI? :)

I create some helper:
openBrowsers(meetingName) {
    let wdio = require('webdriverio');
    let mbrowser = wdio.multiremote({
        b1: {
            desiredCapabilities: {
                browserName: 'chrome'
            }
        },
        b2: {
            desiredCapabilities: {
                browserName: 'chrome'
            }
        }
    });
    return mbrowser.init().url('http://google.com')
            .then(function () {
                var b1 = mbrowser.select('b1');
                var b2 = mbrowser.select('b2');

                b1.url('http://facebook.com');
            });
}

but test passed without waiting browsers load urls..
Is this possible?

@kerstvo I think you missed the return inside then:
return b1.url('http://facebook.com');

in this case a promise is passed to next iteration

It seems, multisession was implemented :)


Support for Hijri Dates (Islamic Calendar)

I was wondering if there is any plan to support the conversion from Hijri dates to duckling default dates (Gregorian Calendar) if so when will it be available to use?
ex:
7th Safar, 1439h -> 27th October, 2017

Hi @Abdallatif,
If I understand correctly, you're looking for parsing Hijri dates in English and resolve/convert them to the Gregorian calendar. Is it possible to do this by adding rules? Do things like "2 days before 7th Safar, 1439h" make sense?
On another hand, if you're also looking for the other way around (resolve/convert Gregorian dates to Hijri), this would require another set of changes (might be part of the assumptions framework: #29).

Hi @patapizza
Thanks for replying, I'm looking for a way to resolve Hijri to Gregorian dates. The conversion is not that simple.
I think this should be a helper rather than a rule. Because there are some holidays that are in Hijri calendar, like Eid-ul-Fitr which is on 1st Shawwal, and 1st of Shwwal is not on the same Georgian dates every year, for 2018 it's on 15th of Jun (estimated), but in 2017 it was on 25th of June. Each month starts when the lunar crescent is first seen.
There are some formulas to estimate the Hijri date to Georgian dates
php code


Refactor test cases

Refactoring joint_trajectory_controller tests to fix #39.
I'm doing some cleanup since I'm at it.

Codecov Report

Merging #64 into master will increase coverage by 1.89%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #64      +/-   ##
==========================================
+ Coverage   33.12%   35.01%   +1.89%
==========================================
  Files          12       12
  Lines        1123     1068      -55
  Branches      740      683      -57
==========================================
+ Hits          372      374       +2
  Misses        103      103
+ Partials      648      591      -57

Flag
Coverage Δ

#unittests
35.01% <ø> (+1.89%)
:arrow_up:

Impacted Files
Coverage Δ

...int_trajectory_controller/test/test_trajectory.cpp
24.71% <0.00%> (-1.66%)
:arrow_down:

...ectory_controller/test/test_trajectory_actions.cpp
37.63% <0.00%> (+7.39%)
:arrow_up:

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 c6fa0b2...3cd7446. Read the comment docs.

@jordan-palacios I've rebased this PR after merging #53 to ensure we don't break anything

@jordan-palacios I've fixed the compilation on this one but haven't done the refactoring you made to the rest of the tests.

@bmagyar Ready for merge.


⚠ Turnos 24x7 has degraded performance

In 8729e5b, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 858 ms

Resolved: Turnos 24x7 performance has improved in 0d894c1.


Transitions ignored when lights turn on

My setup is Adaptive Lighting with Zigbee2MQTT (most recent versions) and various models of Ikea Tradfri lamps controlled by HA automations. Some lamps seem to have default turn-on transitions set (not sure where they come from), some have defaults set in Z2M, some automations explicitly set transition times in light.turn_on, and AL has the initial_transition set to its default of 1 second.
All of these transitions are ignored while AL is activated and lights turn on instantly to their target brightness. When I disable AL, all transitions are correctly applied.
Here's an example log from Z2M of a light.turn_on call:
Debug 2023-05-08 21:41:12Received MQTT message on 'zigbee2mqtt/Bulb01/set' with data '{"state":"ON","transition":0.5}'
Debug 2023-05-08 21:41:12Publishing 'set' 'state' to 'Bulb01'
Info 2023-05-08 21:41:12MQTT publish: topic 'zigbee2mqtt/Bulb01', payload '{"brightness":136,"color_mode":"color_temp","color_temp":454,"color_temp_startup":65535,"last_seen":"2023-05-08T19:41:13.278Z","level_config":{"on_level":"previous"},"linkquality":40,"power_on_behavior":"previous","state":"OFF","update":{"installed_version":65554,"latest_version":65554,"state":"idle"},"update_available":false}'
Debug 2023-05-08 21:41:12Publishing 'set' 'transition' to 'Bulb01'
Info 2023-05-08 21:41:12MQTT publish: topic 'zigbee2mqtt/Bulb01', payload '{"brightness":136,"color_mode":"color_temp","color_temp":454,"color_temp_startup":65535,"last_seen":"2023-05-08T19:41:13.278Z","level_config":{"on_level":"previous"},"linkquality":40,"power_on_behavior":"previous","state":"ON","update":{"installed_version":65554,"latest_version":65554,"state":"idle"},"update_available":false}'
Debug 2023-05-08 21:41:12Received MQTT message on 'zigbee2mqtt/Bulb01/set' with data '{"state":"ON","transition":1.0,"brightness":129,"color_temp":454}'
Debug 2023-05-08 21:41:12Publishing 'set' 'brightness' to 'Bulb01'
Info 2023-05-08 21:41:12MQTT publish: topic 'zigbee2mqtt/Bulb01', payload '{"brightness":136,"color_mode":"color_temp","color_temp":454,"color_temp_startup":65535,"last_seen":"2023-05-08T19:41:13.409Z","level_config":{"on_level":"previous"},"linkquality":40,"power_on_behavior":"previous","state":"ON","update":{"installed_version":65554,"latest_version":65554,"state":"idle"},"update_available":false}'
Debug 2023-05-08 21:41:12Publishing 'set' 'transition' to 'Bulb01'
Debug 2023-05-08 21:41:12Publishing 'set' 'color_temp' to 'Bulb01'
Info 2023-05-08 21:41:12MQTT publish: topic 'zigbee2mqtt/Bulb01', payload '{"brightness":136,"color_mode":"color_temp","color_temp":454,"color_temp_startup":65535,"last_seen":"2023-05-08T19:41:13.464Z","level_config":{"on_level":"previous"},"linkquality":43,"power_on_behavior":"previous","state":"ON","update":{"installed_version":65554,"latest_version":65554,"state":"idle"},"update_available":false}'
Info 2023-05-08 21:41:12MQTT publish: topic 'zigbee2mqtt/Bulb01', payload '{"brightness":129,"color_mode":"color_temp","color_temp":454,"color_temp_startup":65535,"last_seen":"2023-05-08T19:41:13.464Z","level_config":{"on_level":"previous"},"linkquality":43,"power_on_behavior":"previous","state":"ON","update":{"installed_version":65554,"latest_version":65554,"state":"idle"},"update_available":false}'

The first line contains the transition set by the service call ("transition":0.5), and just moments after, AL sends another call with the initial_transition ("transition":1.0).
Only when I turn on the lights in quick succession, the transition is correctly applied. Logs of two consecutive turn-on sequences:
Debug 2023-05-08 21:49:51Received MQTT message on 'zigbee2mqtt/Bulb01/set' with data '{"state":"ON","transition":0.5}'
Debug 2023-05-08 21:49:51Publishing 'set' 'state' to 'Bulb01'
Info 2023-05-08 21:49:51MQTT publish: topic 'zigbee2mqtt/Bulb01', payload '{"brightness":120,"color_mode":"color_temp","color_temp":454,"color_temp_startup":65535,"last_seen":"2023-05-08T19:49:52.960Z","level_config":{"on_level":"previous"},"linkquality":43,"power_on_behavior":"previous","state":"OFF","update":{"installed_version":65554,"latest_version":65554,"state":"idle"},"update_available":false}'
Debug 2023-05-08 21:49:51Publishing 'set' 'transition' to 'Bulb01'
Info 2023-05-08 21:49:51MQTT publish: topic 'zigbee2mqtt/Bulb01', payload '{"brightness":120,"color_mode":"color_temp","color_temp":454,"color_temp_startup":65535,"last_seen":"2023-05-08T19:49:52.960Z","level_config":{"on_level":"previous"},"linkquality":43,"power_on_behavior":"previous","state":"ON","update":{"installed_version":65554,"latest_version":65554,"state":"idle"},"update_available":false}'
// OFF command removed
Debug 2023-05-08 21:49:55Received MQTT message on 'zigbee2mqtt/Bulb01/set' with data '{"state":"ON","transition":0.5}'
Debug 2023-05-08 21:49:55Publishing 'set' 'state' to 'Bulb01'
Info 2023-05-08 21:49:55MQTT publish: topic 'zigbee2mqtt/Bulb01', payload '{"brightness":120,"color_mode":"color_temp","color_temp":454,"color_temp_startup":65535,"last_seen":"2023-05-08T19:49:56.248Z","level_config":{"on_level":"previous"},"linkquality":43,"power_on_behavior":"previous","state":"OFF","update":{"installed_version":65554,"latest_version":65554,"state":"idle"},"update_available":false}'
Debug 2023-05-08 21:49:55Publishing 'set' 'transition' to 'Bulb01'
Info 2023-05-08 21:49:55MQTT publish: topic 'zigbee2mqtt/Bulb01', payload '{"brightness":120,"color_mode":"color_temp","color_temp":454,"color_temp_startup":65535,"last_seen":"2023-05-08T19:49:56.248Z","level_config":{"on_level":"previous"},"linkquality":43,"power_on_behavior":"previous","state":"ON","update":{"installed_version":65554,"latest_version":65554,"state":"idle"},"update_available":false}'

Now there's only one ON command with "transition":0.5. If I wait a few seconds before turning it on again, there's again a second ON command with "transition":1.0 from AL, and the transition is ignored.
Any ideas how to fix this? It seems to me that Z2M or the Tradfri lights cannot correctly handle overlapping transition commands, and a potential solution could be delaying the first AL adjustment command after turn-on by the initial transition time.
Btw, thanks for developing AL! I started using it a week ago and instantly loved it! It let me simplify light automations and provides a nicer experience :)

Here's a script to reproduce the issue (run with AL disabled!):
alias: transitiontest
sequence:
  - service: light.turn_off
    entity_id: light.badezimmer_decke
  - delay: 2
  # A normal turn-on command, transition works as expected
  - service: light.turn_on
    entity_id: light.badezimmer_decke
    data:
      transition: 1
  - delay: 2
  - service: light.turn_off
    entity_id: light.badezimmer_decke
  - delay: 2
  # Emulation of AL-enhanced turn-on sequence
  # - first, the normal command (e.g. from an automation)
  # - second, the command added by AL
  # Transition ignored, light turns on at full brightness
  - service: light.turn_on
    entity_id: light.badezimmer_decke
    data:
      transition: 1
  - service: light.turn_on
    entity_id: light.badezimmer_decke
    data:
      transition: 1
      brightness: 254
      color_temp: 180
mode: single

The transition is only ignored if both brightness and color_temp data are present. Removing one or the other makes transitions work as expected.
Splitting the commands further into one with only brightness, and one with only color temperature (no matter which order; making three commands in total), leads to the issue that the brightness is not correctly applied.
As mentioned before, it seems like a fix could be to wait for one command (transition) to finish before sending the next command. I am aware of the implications on user experience when then AL adjustment is delayed, so a reasonable trade-off could be to immediately send a brightness-only command and with a delay the color temperature command. The idea is that a wrong brightness (e.g. too high in the middle of the night) is perhaps more problematically perceived than a wrong initial color temperature. If this issue only happens with Tradfri lights (or any subset of brands/products), it could be an optional tweak.

So... I found the separate_turn_on_commands config flag which basically does exactly that 🙈 It seems like it still needs some tweaking to work correctly, but this issue can be closed.

@protyposis Glad you found a solution! I also use the IKEA tradfri bulbs but I haven't noticed this problem. I ran the script you posted and it did not show the issue either. There's another command you might want to play with if you're still having trouble: send_split_delay and adapt_delay

I suspended using separate_turn_on_commands due to the bug described in https://github.com/basnijholt/adaptive-lighting/issues/410#issuecomment-1539788096 (lights turning back on after turning off). Missing transitions are the lesser problem :)


Cant compile anymore

Describe your problem here.
Hi, hxCodec error guy here(again), so, i tried to reinstall all the things(git,haxe and his librays) using this scrip.bat:https://drive.google.com/file/d/1JT3EE7dJk9MKNzr2-YbojiMwJ23Mh4L2/view(which is in the Friday Night Funkin' source code compilation tutorial) but... it only get the things worse, now i cant compile the default game, Seriously, i've tried several things, and nothing works, please help me, i don't know what to do anymore

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

You didn't install lime correctly. Follow ALL intructions given for Vanilla AND Psych Engine.

Ya I just uninstalled everything and installed it again and now it's working. Thanks :)


Unable to receive offers / long delays when starting or restarting.

My cluster consist of 9 slaves server split in 1/2 for two primary applications (Spark | Scala Microservices)
Spark - (server 1,2,3,4,8)  attributes: "rack:spark"
Long running Microservices (server 5,6,7,9) attributes "rack:ms"
The spark jobs run in coarse mode and the majority of them are short lived they run for about  ~10-15 minutes via Chronos and shutdown. They start every 15 minutes about ~45 jobs.
We do lots of deploys daily mostly to the "rack:ms" nodes where these jobs are started via Marathon and run until we need to deploy a new release of code.
Recently I started noticing jobs are taking forever to restart or startup like they're not receiving valid offers.
The cluster resources consists of the following resources I always have more than enough idle resources available to bring up/down new services yet I've seen one scenario where a service took almost 10 minutes to restart.
CPUs	Mem
Total	120	456.8 GB
Used	53.6	140.5 GB
Offered	0	0 B
Idle	66.4	316.3 GB
How can I combat this delay? I'm not using roles could this be the problem?
Chronos jobs always seem to run fine but they require much less resource than my long running Scala services.
Here is a sample job definition for in Marathon.
{
"id": "production/index-service",
"cmd": "env && /opt/orchard/production/index-server/bin/run_jar.sh",
"cpus": 1.0,
"mem": 4096,
"disk": 1000,
"user": "orchard",
"instances": 2,
"constraints": [
[
"hostname","UNIQUE"
],
[
"rack", "LIKE", "ms"
]
],
"requirePorts": true,
"labels": {
"ENV": "production",
"HAPROXY_GROUP": "microservice"
},
"ports": [
31703,
31803,
31903
],
"maxLaunchDelaySeconds": 3,
"backoffFactor": 1.20,
"healthChecks": [
{
"gracePeriodSeconds": 3,
"intervalSeconds": 5,
"maxConsecutiveFailures": 3,
"protocol": "TCP",
"portIndex": 1,
"timeoutSeconds": 5
}
],
"upgradeStrategy": {
"minimumHealthCapacity": 0.5,
"maximumOverCapacity": 0.2
}
}
Any advice appreciated thanks.

@rodrickbrown looking at the Marathon leader logs should help you find out if Marathon is not getting offers often enough, or if the ones it gets don't match the requirements of your apps.


App Store  is  Buzz

It is better on the App Store. Get a Mac-native version of Buzz with a cleaner look, audio playback, drag-and-drop import, transcript editing, search, and more.
Mac Air M2, 1 hour of Chinese conversation audio, using the Medium model, has not been completed after 3 hours. I dare not purchase from the App Store.

Wanted to Support it but it's showing me to download later. Not sure why.

@aycajr  Do you have the open-source version installed? If so, you need to uninstall it first.

Closing as stale, please re-open with more information if still relevant


when the android process exits, flutter logs should exit as well

From https://github.com/flutter/tools/issues/109:
When the android process exits, flutter logs should exit as well. Right now the process will continue to run; it should exit (probably with a code of 0).

What if the user goes into the Android recent tasks list and reselects the app?

I don't think this still applies.  @devoncarew is working on a new mode for flutter run --resident anyway.


Question: How do I use Changed in BeforeUpdate to track changes on a field in an embedded struct?

Question
How do I use Changed in BeforeUpdate to track changes on a field in an embedded struct? I tried Changed("field1->>'field2'") and it did not work.

The document you expected this should be explained
Check if field has changed

Expected Answer
Yes, or no if this is supported. If yes, how would one do it.

it's not support


ng-cookies squashed

@petebacondarwin - the commits are not precisely as you requested since some of the commits you listed didn't seem right to me but I hope it is close enough :)

Apart from a couple of docs tweaks and removing the use of extend in $$cookieWriter this LGTM.
@shahata - let me know when those are done and we can land this

LGTM - just checking the doc-gen and merging


add New AAD Roles to the existing AAD Roles

Updating "includedRoles" to include all new AAD Roles.
excluded from the list is "Directory Synchronization Accounts" Role

@AlexFilipin change order for better review and remove unnecessary blanks


Annotator filter queries - unify on polymorphic params

All annotator filter queries need to reference polymorphic params in a unified way.

[ ] Tag
[ ] Note
[ ] Confidence
[ ] Data attribute
[ ] Alternate value
[ ] Attributions
[ ] Citations (?)
[ ] Protocol relationships


color does not work with ./...

I ran into this while upgrading some tests to check for colorized output. Tests worked fine in the package, but go test ./... fails. You can reproduce this easily in this repo.
tests pass
go test
tests fail
go test ./...

Hi @drewwells. The problem lies with this line:
var NoColor = !isatty.IsTerminal(os.Stdout.Fd())

Somehow this get's set to false when go test ./... is called. If you call just go test it's still true. Another interesting thing is that go test -v ./... also works.
So I'm not quite sure why the stdout changes between go test ./... and go test -v ./.... I don't have the time for debugging, but you can easily fix it by adding the -v flag :)

oh nice, -v is a good workaround. I think that is intended behavior, I have noticed stdout doesn't get populated when recursively executing tests. If each test manually assigned a fd to os.Stdout, would that pass the isTerminal check?

@drewwells I've just set it explicit to false. Tests should always be the same, so depending on the environment is something which should imho be changed. Now even go test ./... works as intended.

Ah okay, since NoColor is exported I should be able to add those to my tests too. Thanks!


BUILD files

to test
go get -u sevki.org/build/cmd/build
git clone git@github.com:sevki/harvey.git harvey-sevki
cd harvey-sevki
build //.:kernel
qemu-system-x86_64 --kernel build_out/amd64/harvey -no-reboot -m 512

closes #47

Conflicts?

@elbing working on it

why not merge?

because the new build isn't working yet

-1
not ready

:-1:
not ready

:-1:

Immediately fails: sys/src/cmd/fossil/BUILD is missing.
I once again urge you to just get these BUILD files installed into the tree so we can all start to help. But I don't say looks good unless you tell me to :-)

Still no good. I do a
hub pull https://github.com/Harvey-OS/harvey/pull/53
and it makes a nice branch and all, and it immediately fails on weird errors about interrupt, or it still looks for libsunrpc stuff. This is really not working well.

yeah, this is supposed to fail with the new build tool. that's why I -1'd it. Please do not review this yet.

Update you master, sevki, or it will be worse later. We havee committed
anything new, so take the chance.
Álvaro
El 24/02/2016 07:42, "Sevki"<EMAIL_ADDRESS>escribió:

yeah, this is supposed to fail with the new build tool. that's why I -1'd
it. Please do not review this yet.
—
Reply to this email directly or view it on GitHub
https://github.com/Harvey-OS/harvey/pull/53#issuecomment-188105124.

LGTM
This meets the minimum requirement: it does not break the old build tool. I just did a full build and boot cycle with the old tool and it all works. Now we can help get the new tool working.
THere are still problems. This can't build riscv. There are amd64 specific settings in sys/src/FLAGS. But we need to get going on this so we'll commit it and fix it.


restore DS.Model -> M3 relationship links

This amounts to having inverse relationship setup defer to model data so that ember-m3 can no-op it.

fixed in ember-data 3.4.0-beta.2


changed the signature matching in FunctionResolver and moved the

responsibility to normalize the data types to the getSignature method
this allows to have more control over how to normalize arguments
and also saves comparisons and roundtrips when resolving functions
the requirement to create types just for matching signatures is also gone
and is replaced by argument matchers

Codecov Report

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

@@            Coverage Diff            @@
##             master    #4916   +/-   ##
=========================================
  Coverage          ?   81.95%
  Complexity        ?    10603
=========================================
  Files             ?     1294
  Lines             ?    44494
  Branches          ?     5647
=========================================
  Hits              ?    36465
  Misses            ?     5377
  Partials          ?     2652

Impacted Files
Coverage Δ
Complexity Δ

...ate/operation/scalar/arithmetic/ArrayFunction.java
100% <100%> (ø)
7 <ø> (?)

...te/operation/scalar/arithmetic/NegateFunction.java
52.17% <100%> (ø)
6 <ø> (?)

...e/operation/scalar/cast/TryCastScalarFunction.java
100% <100%> (ø)
5 <ø> (?)

...e/operation/scalar/conditional/NullIfFunction.java
100% <100%> (ø)
5 <ø> (?)

.../io/crate/operation/predicate/IsNullPredicate.java
76.92% <100%> (ø)
15 <ø> (?)

.../operation/tablefunctions/TableFunctionModule.java
100% <100%> (ø)
2 <1> (?)

sql/src/main/java/io/crate/metadata/Functions.java
97.91% <100%> (ø)
10 <ø> (?)

...o/crate/operation/scalar/geo/DistanceFunction.java
85% <100%> (ø)
18 <1> (?)

...n/java/io/crate/operation/operator/EqOperator.java
77.08% <100%> (ø)
8 <ø> (?)

core/src/main/java/io/crate/types/DataTypes.java
93.93% <100%> (ø)
26 <2> (?)

... and 23 more

Continue to review full report at Codecov.

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

please also check the coverage, there are a few methods that have no coverage/usage


Document 4Q20 release process for updating each of: devfile, starters, stack image to support versioning and updates

This is probably only internal/Wiki doc.
To track updates to each of:

devfile itself
starter
stack image

we should describe the workflow for each of:

The project developer releasing one or more of these
The application developer "Jane" trying to reference the GitHub source for the project they have created from devfile and possibly starter  (understanding they could have made changes we can't track).

We could employ some combo of:  version ids, tags, numbers, image labels, etc. in the appropriate artifacts:  devfile, pom, Git repo, etc within GitHub repos, Docker Hub repos, devfile registry, etc.

comment from #32 (since closed as dup)
With a typical flow creating from a starter, after doing:
$ odo create java-openliberty --starter
you should have a devfile referencing, as its parent, a specific version of the java-openliberty application stack devfile.
However, the starter artifacts will not necessarily be versioned along with the stack devfile and Docker image. The starter could be updated and another project could be created from the same stack version, but with a different starter.
This shouldn't be a big deal, since a user will be customizing the starter themselves.
Every time the stack is updated, it should be tested to ensure a project created from the latest version of EACH starter will worth with this most recent stack version. It won't effect existing projects which should be pinned to an existing version of the devfile.
Every time a starter is update it should be tested to ensure it works with the latest version of the stack.
ASSUMPTION: Once a project is created, it does not use starters again, so it isn't possible for a change in starter to break an existing project. Note, this assumes something like an "application project". You could say here's my "test project", which always does a create from starter, so yes, it is effected by a change in starter at a given stack
At the very least, we should include, within the starter project (POM?) a reference to the SHA that shows the original starter source cloned from the Git repo hosting it.

Not extensively or thoroughly doc'd but basics here:
https://github.com/OpenLiberty/application-stack/wiki/Versioning-stack-artifacts


which output file can be used as the weights?

First thanks for the great codes!
I trained the model on my own data, and get the following output files:
model.ckpt-199.data-00000-of-00001
model.ckpt-199.index
model.ckpt-199.meta
I think model.ckpt-199.data-00000-of-00001 maybe the one, and I replace the model.ckpt-15999 with it, and then rename to "model.ckpt-15999".
However when I run the python demo.py, it says wrong format.
Is there any one can help me?

i believe these outputs the you get are stored in a folder called "RUNS/Runs-xxxxxxxxx/" just give the path to the whole folder as the model, tensorflow will load them automatically

Thanks for @bendidi ~!


ls colorization alias broken on Ubuntu 16.04.1

I'm running oh-my-zsh on two VPS servers running Ubuntu 16.04.1 and the theme-and-appearance.zsh file is creating an alias for ls to ls -G which removes the usergroups from the listing, not - as intended - colorizing the output.
The line setting this is this one:
https://github.com/robbyrussell/oh-my-zsh/blob/master/lib/theme-and-appearance.zsh#L35

Just realized this issue is about the same thing: https://github.com/robbyrussell/oh-my-zsh/issues/5604


update e2e test

What this PR does / why we need it:
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Codecov Report

Merging #672 (2ea512b) into main (5abf833) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #672   +/-   ##
=======================================
  Coverage   30.70%   30.70%
=======================================
  Files          25       25
  Lines        1547     1547
=======================================
  Hits          475      475
  Misses       1007     1007
  Partials       65       65

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