Current Layer in Flluid, not shown

I just noticed the current layers are not being shown iun Fluid.  Using Orcaslicer - as fans work as they should-they do not come on at 100%

I noticed in QidiSlicer, it shows layers and gcode preview works in fluid, expcept the layer counts are wrong

I got it working (Gcode preview and layer count"

I removed the M117 command after flashing the GUI, and everythign is working...

closed workrign perfectly


How to reproduce the performance comparison between PandaLM and ChatGPT

thanks for releasing the project!
I want to reproduce the performance comparison between PandaLM and ChatGPT like:

Of course I mean I want to get the same performance of PandaLM on my machine.
Is it gotten based on  ./data/testset-v1.json? If so, what should I run for the second line of performance table?

Feel free to reproduce PandaLM's output with pandalm/utils/pandalm_inference.py, as you could pass our human annotated test dataset with labels(data/testset-v1.json), run inference and calculate any metric you want.
We provide the outputs from gpt-3.5-turbo and parsed the raw outputs to json format in data/gpt-3.5-turbo-testset-v1.json as described here(https://github.com/WeOpenML/PandaLM/tree/main#test-data). You could also run OpenAI's API with your own script or collect data from ChatGPT manually to .json format for comparison.


DependencyResolutionExceptions when building the project.

Hello, I tried building the examples in this project but i keep getting a build failure. I Think this because the wildfly-camel-archetype-cdi:maven-archetype:4.8.0-SNAPSHOT dependency is not available at the repository. I'm I missing something or I'm I the only one getting the this error. Any help would be appreciated. Below is the build error.
[ERROR] Failed to execute goal on project wildfly-camel-archetype-cdi: Could not resolve dependencies for project org.wildfly.camel.archetypes:wildfly-camel-archetype-cdi:maven-archetype:4.8.0-SNAPSHOT: Failure to find org.wildfly.camel:wildfly-camel-feature-pack:pom:4.8.0-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository has elapsed or updates are forced -> [Help 1]

IIRC the examples do not depend on the archetypes. Maybe try to build the entire project from the project root directory first (skip tests for quickness).
mvn clean install -Dts.all -DskipTests`

When the build completes you can cd examples and each of them should have been built.

Did you manage to resolve the problem?

I have not been able to compile the whole project. The build is failing at
[INFO] --- maven-antrun-plugin:1.7:run (default) @ wildfly-camel-swarm ---
[INFO] Executing tasks'

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project wildfly-camel-swarm: An Ant BuildException has occured: Java returned: 1
[ERROR] around Ant part ...<java classname="org.wildfly.swarm.camel.generator.Main" failonerror="true" classpathref="maven.test.classpath">... @ 4:115 in C:\Users\babafemini\Desktop\Base Code\wildfly-camel-master\wildfly-camel-master\swarm\target\antrun\build-main.xml

Any possible solutions?

Please can you run the build with -X so that we can see a stacktrace of what's causing the error?

Also seeing the output from mvn -versions would be helpful so I can get an idea of what your environment looks like.

This is my environment
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T20:39:06+01:00)
Maven home: C:\Program Files\apache-maven-3.5.0\bin\..
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_131\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

And here is the stacktrace of the error
[INFO] Reactor Summary:
[INFO]
[INFO] Wildfly Camel ...................................... SUCCESS [ 31.951 s]
[INFO] Wildfly Camel :: Config ............................ SUCCESS [01:19 min]
[INFO] WildFly Camel :: CXF Undertow ...................... SUCCESS [01:28 min]
[INFO] Wildfly Camel :: Feature ........................... SUCCESS [  7.275 s]
[INFO] Wildfly Camel :: Feature Extras .................... SUCCESS [ 54.650 s]
[INFO] Wildfly Camel :: Subsystem ......................... SUCCESS [  2.431 s]
[INFO] Wildfly Camel :: Subsystem :: Core ................. SUCCESS [ 52.228 s]
[INFO] Wildfly Camel :: Subsystem :: CDI .................. SUCCESS [ 33.853 s]
[INFO] Wildfly Camel :: Subsystem :: Security ............. SUCCESS [ 20.982 s]
[INFO] Wildfly Camel :: Subsystem :: Undertow ............. SUCCESS [ 39.650 s]
[INFO] Wildfly Camel :: Feature Pack ...................... SUCCESS [28:57 min]
[INFO] Wildfly Camel :: Catalog ........................... SUCCESS [07:10 min]
[INFO] Wildfly Camel :: Swarm ............................. FAILURE [03:01 min]
[INFO] Wildfly Camel :: Enricher .......................... SKIPPED
[INFO] Wildfly Camel :: Testsuite ......................... SKIPPED
[INFO] Wildfly Camel :: Testsuite :: Common ............... SKIPPED
[INFO] Wildfly Camel :: Testsuite :: Standalone ........... SKIPPED
[INFO] Wildfly Camel :: Testsuite :: Standalone :: Smoke .. SKIPPED
[INFO] Wildfly Camel :: Testsuite :: Standalone :: Basic .. SKIPPED
[INFO] Wildfly Camel :: Testsuite :: Standalone :: Extra .. SKIPPED
[INFO] Wildfly Camel :: Testsuite :: Standalone :: Docker . SKIPPED
[INFO] Wildfly Camel :: Testsuite :: Camel ................ SKIPPED
[INFO] Wildfly Camel :: Archetypes ........................ SKIPPED
[INFO] Wildfly Camel :: Archetypes :: CDI ................. SKIPPED
[INFO] Wildfly Camel :: Archetypes :: Spring .............. SKIPPED
[INFO] Wildfly Camel :: Docs .............................. SKIPPED
[INFO] Wildfly Camel :: Patch ............................. SKIPPED
[INFO] Wildfly Camel :: Example ........................... SKIPPED
[INFO] Wildfly Camel :: Example :: Camel ActiveMQ ......... SKIPPED
[INFO] Wildfly Camel :: Example :: Camel CDI .............. SKIPPED
[INFO] Wildfly Camel :: Example :: Camel CXF JAX-RS ....... SKIPPED
[INFO] Wildfly Camel :: Example :: Camel CXF JAX-WS ....... SKIPPED
[INFO] Wildfly Camel :: Example :: Camel JMS .............. SKIPPED
[INFO] Wildfly Camel :: Example :: Camel JMS MDB .......... SKIPPED
[INFO] Wildfly Camel :: Example :: Camel JMS Spring ....... SKIPPED
[INFO] Wildfly Camel :: Example :: Camel JMS Tx ........... SKIPPED
[INFO] Wildfly Camel :: Example :: Camel JMS Tx Spring .... SKIPPED
[INFO] Wildfly Camel :: Example :: Camel JPA .............. SKIPPED
[INFO] Wildfly Camel :: Example :: Camel JPA Spring ....... SKIPPED
[INFO] Wildfly Camel :: Example :: Camel Mail ............. SKIPPED
[INFO] Wildfly Camel :: Example :: Camel Mail Spring ...... SKIPPED
[INFO] Wildfly Camel :: Example :: Camel REST Swagger ..... SKIPPED
[INFO] Wildfly Camel :: Example :: Testsuite .............. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 46:16 min
[INFO] Finished at: 2017-06-23T17:50:40+01:00
[INFO] Final Memory: 283M/549M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project wildfly-camel-swarm: An Ant BuildException has occured: Java returned: 1
[ERROR] around Ant part ...<java classname="org.wildfly.swarm.camel.generator.Main" failonerror="true" classpathref="maven.test.classpath">... @ 4:115 in C:\Users\babafemini\Desktop\Base Code\wildfly-camel-master\wildfly-camel-master\swarm\target\antrun\build-main.xml
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project wildfly-camel-swarm: An Ant BuildException has occured: Java returned: 1
around Ant part ...<java classname="org.wildfly.swarm.camel.generator.Main" failonerror="true" classpathref="maven.test.classpath">... @ 4:115 in C:\Users\babafemini\Desktop\Base Code\wildfly-camel-master\wildfly-camel-master\swarm\target\antrun\build-main.xml
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: An Ant BuildException has occured: Java returned: 1
around Ant part ...<java classname="org.wildfly.swarm.camel.generator.Main" failonerror="true" classpathref="maven.test.classpath">... @ 4:115 in C:\Users\babafemini\Desktop\Base Code\wildfly-camel-master\wildfly-camel-master\swarm\target\antrun\build-main.xml
        at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:355)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        ... 20 more
Caused by: C:\Users\babafemini\Desktop\Base Code\wildfly-camel-master\wildfly-camel-master\swarm\target\antrun\build-main.xml:4: Java returned: 1
        at org.apache.tools.ant.taskdefs.Java.execute(Java.java:111)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
        at org.apache.tools.ant.Task.perform(Task.java:348)
        at org.apache.tools.ant.Target.execute(Target.java:390)
        at org.apache.tools.ant.Target.performTasks(Target.java:411)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
        at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:327)
        ... 22 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :wildfly-camel-swarm

I hope I sent what you asked for?

Thanks for the info. If I run with the same versions on Windows 10, it works fine for me (I'm running from the Windows Command prompt cmd.exe). I've also got a JAVA_HOME environment variable configured and the Java bin directory added to the PATH.
It's not obvious what's causing the error so I can only suggest commenting out the swarm module from the project pom.xml modules section to see if that helps move things along.
Maybe one other thing to try would be to bump this version to 1.8 and see if it helps.

Okay so I managed  to build the whole project . After which I started my server.Then i attempted to deploy the camel-cdi example. It came up with an exception just as it was about deploying.
Below was the stacktrace.
[DEBUG] Executing deployment
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 40.112 s
[INFO] Finished at: 2017-06-24T18:02:21+01:00
[INFO] Final Memory: 32M/230M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.2.0.Alpha3:deploy-only (wildfly-deploy) on project example-camel-cdi: Failed to execute goal deploy-only: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"example-camel-cdi-4.8.0-SNAPSHOT.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"example-camel-cdi-4.8.0-SNAPSHOT.war\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"example-camel-cdi-4.8.0-SNAPSHOT.war\"
[ERROR]     Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.wildfly.camel.examples.cdi.SimpleServlet with ClassLoader ModuleClassLoader for Module \"deployment.example-camel-cdi-4.8.0-SNAPSHOT.war:main\" from Service Module Loader
[ERROR]     Caused by: java.lang.NoClassDefFoundError: Lorg/apache/camel/CamelContext;
[ERROR]     Caused by: java.lang.ClassNotFoundException: org.apache.camel.CamelContext from [Module \"deployment.example-camel-cdi-4.8.0-SNAPSHOT.war:main\" from Service Module Loader]"},"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"example-camel-cdi-4.8.0-SNAPSHOT.war\".POST_MODULE"],"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}}}
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.2.0.Alpha3:deploy-only (wildfly-deploy) on project example-camel-cdi: Failed to execute goal deploy-only: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"example-camel-cdi-4.8.0-SNAPSHOT.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"example-camel-cdi-4.8.0-SNAPSHOT.war\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"example-camel-cdi-4.8.0-SNAPSHOT.war\"
    Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.wildfly.camel.examples.cdi.SimpleServlet with ClassLoader ModuleClassLoader for Module \"deployment.example-camel-cdi-4.8.0-SNAPSHOT.war:main\" from Service Module Loader
    Caused by: java.lang.NoClassDefFoundError: Lorg/apache/camel/CamelContext;
    Caused by: java.lang.ClassNotFoundException: org.apache.camel.CamelContext from [Module \"deployment.example-camel-cdi-4.8.0-SNAPSHOT.war:main\" from Service Module Loader]"},"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"example-camel-cdi-4.8.0-SNAPSHOT.war\".POST_MODULE"],"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}}}
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to execute goal deploy-only: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"example-camel-cdi-4.8.0-SNAPSHOT.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"example-camel-cdi-4.8.0-SNAPSHOT.war\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"example-camel-cdi-4.8.0-SNAPSHOT.war\"
    Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.wildfly.camel.examples.cdi.SimpleServlet with ClassLoader ModuleClassLoader for Module \"deployment.example-camel-cdi-4.8.0-SNAPSHOT.war:main\" from Service Module Loader
    Caused by: java.lang.NoClassDefFoundError: Lorg/apache/camel/CamelContext;
    Caused by: java.lang.ClassNotFoundException: org.apache.camel.CamelContext from [Module \"deployment.example-camel-cdi-4.8.0-SNAPSHOT.war:main\" from Service Module Loader]"},"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"example-camel-cdi-4.8.0-SNAPSHOT.war\".POST_MODULE"],"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}}}
        at org.wildfly.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:148)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        ... 20 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Any solutions?

You need to have the wildfly-camel patch overlay applied to the server.
Have you read the docs? See getting started:
http://wildfly-extras.github.io/wildfly-camel/#_getting_started
Download the patch tar.gz file (or copy a local SNAPSHOT from patch/target). Copy it into the WildFly server root directory, extract the contents and then start the server with bin/standalone.sh -c standalone-camel.xml.

I have done this already but I would redownload the wildfly 10.1.0 and wildfly-camel patch afresh. Because that can only be the possible explanation. I have been having the same exceptions before I tried using your project.

Installing the patch on top of the base WildFly install directory and starting the server with the appropriate config file (I.e standalone-camel.xml) should be enough to enable the Camel subsystem. If you've done things properly, you should see the following lines appear somewhere in the server startup log:
[org.wildfly.extension.camel] (MSC service thread 1-7) Activating Camel Subsystem
[org.wildfly.extension.camel] (MSC service thread 1-6) Bound camel naming object: java:jboss/camel/CamelContextFactory
[org.wildfly.extension.camel] (MSC service thread 1-6) Bound camel naming object: java:jboss/camel/CamelContextRegistry

If you don't see this, something is wrong with your installation.

It works now.....Thanks!

Glad you got it working :smiley:


Task Reflection (M3)

For milestone 3, I have learned how to test our final prototype using the Blackbox testing and Whitebox testing. In testing, it is not necessary to test out all possible values as it is impossible as there are millions, billions trillion or even quadrillion combinations to test. Using the Blackbox testing methods, we do not need to test all values. Instead, we can group value into partitions. When we test on a partition, it is equivalent to we have tested all values in the partition. This helps us to reduce our testing time, removing all the repeated testing and spot error in the program. But Blackbox testing cannot spot errors in the implementation. Thus, Whitebox testing is needed. Using the Control-Flow-Graph, we can draw the graph for each function that is implemented. After which, we can list out all of the possible paths and calculate the cyclomatic complexity of the Control-Flow-Graph. With this we can ensure that most of the path in the function can be tested and see how heavy the function is. Other than testing, I have learned a new diagram, a state diagram. State diagrams are very useful in implementation as we can see how pages transition between one another when a condition is met. It will be very helpful for our ICT2104 project.


[Extensions] Synchronize opensearch-plugin-job-details with JobDetailsService map

Description
Adds JobDetailsService as an indexOperationListener for index .opensearch-plugin-job-details. This allows us to update the internal JobDetails map with the entries indexed to the job details meta data index. Additionally, the indicesToListen set is updated with the job index names post-index, configuring onIndexModule to add the JobSweeper as an indexOperationListener once an extension creates their job index
Issues Resolved
Part of https://github.com/opensearch-project/opensearch-sdk-java/issues/309
Check List

[x] New functionality includes testing.

[x] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Once the sanity test case for the workflow is added in the PR. LGTM!

BWC tests are failing since JS main BWC tests use JS 2.5.0, which is no longer wire-compatible with JS 3.x. Currently waiting for OpenSearch 2.6.0-SNAPSHOT to be available in sonatype before merging https://github.com/opensearch-project/job-scheduler/pull/297. Upon merging, I'll update the JS main BWC tests to use 2.6.0. This should resolve the failing checks

Codecov Report

Merging #299 (c841787) into main (fabb639) will decrease coverage by 0.98%.
The diff coverage is 22.85%.

@@             Coverage Diff              @@
##               main     #299      +/-   ##
============================================
- Coverage     39.38%   38.41%   -0.98%
  Complexity       90       90
============================================
  Files            14       14
  Lines           815      846      +31
  Branches         84       85       +1
============================================
+ Hits            321      325       +4
- Misses          471      498      +27
  Partials         23       23

Impacted Files
Coverage Δ

...rg/opensearch/jobscheduler/JobSchedulerPlugin.java
32.20% <0.00%> (-1.73%)
:arrow_down:

...ensearch/jobscheduler/utils/JobDetailsService.java
4.93% <6.52%> (+1.23%)
:arrow_up:

...rch/jobscheduler/transport/GetJobIndexRequest.java
51.06% <57.14%> (ø)

...arch/jobscheduler/transport/GetJobTypeRequest.java
50.00% <57.14%> (ø)

...earch/jobscheduler/rest/RestGetJobIndexAction.java
47.82% <100.00%> (ø)

...search/jobscheduler/rest/RestGetJobTypeAction.java
45.45% <100.00%> (ø)

...rg/opensearch/jobscheduler/sweeper/JobSweeper.java
39.74% <100.00%> (+0.25%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

As per several offline discussions, there have been a few major changes to the job details registration workflow.
Changes to REST APIs
The SPI design allowed Job Scheduler to enforce each extending plugin to submit only one ScheduledJobProvider which includes the job index name and job type. Now that we're retrieving these values from extensions via rest apis, it is difficult to enforce extensions to invoke both the getJobIndex and getJobType sequentially, as Job Details are not indexed to the metadata index until both APIs are invoked. The discussion to keep these APIs separate can be found here, and while mirroring the plugin architecture's existing extension points may make the transition of plugins to extensions easier, separating these API calls have lead to many drawbacks and an overcomplication of the Job Details registration. As a result, we have removed the getJobType API and combined both the getJobIndex and getJobType into one request.
Changes to support extensions registering multiple job types
Previously, the metadata index in which we store job details was keyed with the extension unique ID from which the entry came from. This initial design followed the existing job registration process for plugins. In the case of extensions, there is a possibility that an extension may want to register more than one type of job, and thus in order to support an extension to register multiple times, it was necessary to forgo using the extension ID as the key. As a result, the key shall now be a randomly generated document ID which will be sent back to the caller as a rest response, in order to enable these extensions to further update their Job Details as needed.
CC : @owaiskazi19 @saratvemulapalli @vibrantvarun


Custom Solo Levels

I have fun playing against AIs in solo, so I was wondering is there some guide to create custom solo levels? I've scoured the internet only to find nothing. Thanks in advance
Edit: Would it also be possible to "combine" this  and the master duel's official solo levels?

Editing the solo area is a bit messy at the moment as it's a large blob of json
https://github.com/pixeltris/YgoMaster/blob/master/YgoMaster/Data/Solo.json
It needs an editor written for it or a tool to merge two jsons. There's some basic documentation on the file here https://github.com/pixeltris/YgoMaster/blob/master/Docs/SoloFileFormat.md and some examples here https://github.com/pixeltris/YgoMaster/tree/master/Docs/Solo

Thank you so much! Highly appreciated it


Add user avatar

As per #12, Auth0 provides us with avatar images.

Change the database to use them.
Backfill any old users?
Update when they change?

Use https://www.avatars.io/ for Twitter and Facebook. And a direct link for Github.


Adds a phony make target to check local schema against master

The idea behind this addition is to avoid the CI round-trip for ensuring our currently generated schema produces the results that we expect. Currently missing from schema-tools is an implementation of the version command which means we'll download a new artifact every time we run.
We also don't have a very safe OS check, etc, but it will at least work on apple machines for the time being.

The most recent run:

Really like having the schema check in here. In azure-native we download binaries, with a couple of minor differences that you might want to adopt here too:

We download locally into the repo's bin directory - so this is isolated from any global installations.
We use a [PROGRAM].version file to specify the exact version of each binary to download e.g. schema-tools.version
We take a dependency on schema-tools.version in the makefile so it will be re-downloaded and overwritten if the version file changes (either from a local edit or when checking out).

Example:
https://github.com/pulumi/pulumi-azure-native/blob/db073eee29704f3aa2b36524ffb3be59b6d258ca/Makefile#L157-L167


fix(nuxt): integrate async-context with vue.withAsyncContext

🔗 Linked issue
Followup on #20918
reproduction by @Atinux confirming issue (should run locally)
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[x] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
This PR, tries an alternative method of integrating Native Async Context with Vue by directly patching withAsyncContext import that is injected by Vue for it's non native async context support.
This method has the benefit of being much simpler as we don't need AST based transforms also probably more future compliance because reflects the ideal change we expect from Vue upstream support to improve internal withAsyncContext.
Note: I could confirm this solution externally on reproduction but seems local fixture is not working, investigating more. -- Update: It strangely also works fine in playground but not fixture still! (working both externally and in fixture 🚀 )

Local module to try:
import { defineNuxtModule, addBuildPlugin } from 'nuxt/kit'
import { createUnplugin } from 'unplugin'

export default defineNuxtModule({
  setup(_, nuxt) {
    addBuildPlugin(createUnplugin(() => {
      const virtualFileId = '\0vue-async-context'
      return {
        name: 'nuxt:vue-async-context',
        transformInclude (id) {
          return id.endsWith('.vue')
        },
        resolveId (id) {
          if (id === virtualFileId) {
            return id
          }
        },
        load(id) {
          if (id !== virtualFileId) {
            return
          }
          return `
          import { withAsyncContext as withVueAsyncContext, getCurrentInstance } from 'vue'
          export function withAsyncContext(fn) {
            return withVueAsyncContext(() => {
              const nuxtApp = getCurrentInstance()?.appContext.app.$nuxt
              return nuxtApp ? nuxtApp.runWithContext(fn) : fn()
            })
          }
          `.trim()
        },
        transform (code) {
          if (!code.includes('_withAsyncContext')) {
            return
          }
          code = `import { withAsyncContext as _withAsyncContext } from "${virtualFileId}"
                  ${code.replace('withAsyncContext as _withAsyncContext', '')}`
          return {
            code,
            map: null
          }
        }
      }
    }))
  }
})

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

/cc @antfu Seems Webpack VFS with unplugin is not working well. I couldn't reproduce it externally (https://stackblitz.com/edit/stackblitz-starters-c3p5u7) so pinging you if you can spot any obvious error in usage.
(To reproduce on branch TEST_BUILDER=webpack TEST_CONTEXT=async pnpm nuxt dev test/fixtures/basic)

I can confirm it works locally for the custom module 💯

/trigger release

Shall we add a section on https://nuxt.com/docs/guide/concepts/auto-imports#using-vue-and-nuxt-composables to explain our experimental feature, otherwise I don't know how they can test this 😅

Hi @pi0 do you have an idea of that https://github.com/nuxt/nuxt/issues/23777 ?


INT B-21549

Agility ticket
Summary
Fixing some silly little spacing errors when shipments are listed out.
Out with the old, in with the new.

With UB

How to test

Access MM as a customer
Create a shipment of each kind
Verify that the spacing is not all ugly and wonky with the shipment IDs

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 1ea87f07370c9f12b1f4e2c76e1c1c038c65eb8f


增加代码分析功能

goimports
golint
go vet

Coverage remained the same at 66.667% when pulling 0b43c3f924985f5e29ccb72c191725dc9870367f on code-analysis into 89c98dc1ac7ed4590c8e5352b5ec7d14421f4b6b on master.

Coverage remained the same at 66.667% when pulling 0b43c3f924985f5e29ccb72c191725dc9870367f on code-analysis into 89c98dc1ac7ed4590c8e5352b5ec7d14421f4b6b on master.


Make FutureKit build with Swift Package Manager

swift build previously did not build FutureKit with the swift package manager properly. This PR moves files around slightly so that swift build will work properly.
I had to delete the ObjectiveCExceptionHandler code to make swift build work, since it doesn't support mixed-language targets. This class wasn't exposed anywhere in the framework that I could see, so I don't think this is a big deal.
~I wanted to migrate the unit tests to also work when running swift test, but those tests also include obj-c code that appears to be important to the definition of each test. It may be possible to restructure things so that they can compile, but I'm not familiar with how that could look yet.~
I was able to get the tests to build by adding a separate swiftpm target for the BlockBasedTestCase objc code, which is imported by the unit tests. swift test will now build everything and run the requisite tests properly.

I rebased this onto the xcode9 branch since I need this to work there. If you want me to recreate the PR i'm happy to do so, if this causes issues

Hmm... the test code will probably need to be refactored since it uses an ObjectiveC runtime binding trick to allow it to 'generate' test code cases.   Not sure how to do that in swift only.
Maybe I could look at using Stencil.
I'll try and pull this down tonight and run it...

That’s possible. It all works as expected on a Mac but I haven’t tried running this on Linux at all.
--
Kevin Lundberg

On Oct 25, 2017, at 11:33 AM, Michael Gray<EMAIL_ADDRESS>wrote:
Hmm... the test code will probably need to be refactored since it uses an ObjectiveC runtime binding trick to allow it to 'generate' test code cases. Not sure how to do that in swift only.
Maybe I could look at using Stencil.
I'll try and pull this down tonight and run it...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I noticed you made a new release for swift 4 support. I made sure these commits were up to date with that work, and swift test still compiles and runs the tests properly


Install kubectl using gcloud components

Without kubectl the step make create-context in the management cluster creation fails.

/assign @Bobgy @joeliedtke
PTAL, thanks!

/lgtm
/approve

Thanks for the fix!


use thiserror instead of anyhow in disk_btree

Personally here, I do not see many pros in the proposed variant. It requires manually implementing the Error trait, which thiserror saves us from. I understand the pain of dealing with procmacro. Still, as you said, we have both anyhow and thiserror among our dependencies, so our manual implementations of the Error trait shouldn't affect compile times too much.
I think your proposal will play nicely with top-level errors. Mainly because we use anyhow too much on the deeper code levels and can't get back necessary data from anyhow errors. E g in HTTP handlers


docs: new readme

Motivation
Prettify and update readme.
Solution
Check out the new readme.

Note Any explanations you deem useful should be moved to the book.

It looks like a lot of info and sample code was removed, is this upstreamed to the book yet? We should hold off on merging until it's upstreamed somewhere, otherwise it will be harder for users to find / harder to point them to

I think it's useful to lean towards having too much information, so closing as stale for now, but happy to revisit an updated readme or reopen this when ready

The current readme still suffers from the two issues solved here:

The documentation in the book is out-of-date, and people aren't even aware that certain modules exist.
Even less modules are showcased in the readme, making no mention of the others, giving the impression that's all Forge Std has to offer.

I suggest the following:
If this readme looks good to you, a Read more button can be added next to the sections that have more information. These descriptions will live after everything in the readme, and on the click of the button, the readme will scroll down to the header with the current information. It will also have the ↩ for quickly navigating back.
Let me know what you think.

Agreed that both the book documentation and forge-std README are missing a lot of information, and discoverability of things in forge-std has been a problem. Ideally we only need to maintain it in one place, which probably should be the book so everything users need is in one place.
I'm not sure I follow how your suggestion solves the issues since it contains less information than currently, but I do see two possible plans for solving those issues, cc @Evalir:

First get the book updated to fully document forge-std, require book updates as part of PRs here going forward, then update the README to give a brief overview and link out to the book
Given https://github.com/foundry-rs/foundry/issues/3782, gradually improve docs by first migrating things from forge-std to forge and documenting them in the book at that time. Once fully migrated upstream, then update the README/book accordingly with what's left in forge-std


Build fails with Error: ECONNRESET: aborted

Occasionally the deploy-to-balena-action will fail with the error message Error: ECONNRESET: aborted  despite the build being marked as succeeded on the Balena dashboard. We run several build jobs and randomly 1 of them will flake with this error. Also occasionally, it seems one of these flakes will cause all of the other jobs to flake as well.
Here are the logs:
[service]         Successfully built 91063e1d9bd8

Error: ECONNRESET: aborted

Error:
Error: aborted
    at connResetException (node:internal/errors:704:14)
    at TLSSocket.socketCloseListener (node:_http_client:425:19)
    at TLSSocket.emit (node:events:549:35)
    at TLSSocket.emit (node:domain:482:12)
    at node:net:747:14

Error:     at TCP.done (node:_tls_wrap:582:7)

Error:
For further help or support, visit:
https://www.balena.io/docs/reference/balena-cli/#support-faq-and-troubleshooting

Our fix for this has always been to just rerun the individual job which flaked which will eventually work most of the time but sometimes it doesn't which requires rerunning the action as a whole.

Hey @treygilliland , is there a specific builder that gives you the most trouble? The builder ID is usually printed at the start of the build logs.
Does it happen more with some projects than others? In the past we saw this with larger compose files with many services and it would be interesting to know if that was still a factor.

@klutchell it is a compose file with 5-6 services, 2 of them are ~300 MB, 2 of them are ~2GB and one is ~16GB but normally our builds make good use of the cache so builds stay around 3-5 minutes.
I don't know if it is a specific builder but we are building for the NVIDIA Jetson Orin if that helps. The builder ID for this particular failure is 4b2d7d0 but it seems to fail on the GH action side and pass on the Balena dashboard.

It just happened again with 5 of our 6 build jobs, only 1 succeeded. This time it aborted very early on (while the cache images were still downloading). It may be related to running multiple builds at once for the same fleet but it is hard to tell. The build has the 'running...' status on the balena dashboard despite the build triggered by the retry finishing before it.

Hey @treygilliland , is this still happening with the latest release of the action?


Port changes from Platform-UI-DC

Port changes @tedAir made to Platform-UI-DC

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

Project coverage is 89.59%. Comparing base (91aa506) to head (ff37a07).
Report is 2 commits behind head on stage.

Additional details and impacted files
@@            Coverage Diff             @@
##            stage     #715      +/-   ##
==========================================
- Coverage   90.33%   89.59%   -0.75%
==========================================
  Files          39       39
  Lines        4718     4814      +96
==========================================
+ Hits         4262     4313      +51
- Misses        456      501      +45

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


Update/Add Rust cargo-fmt

Tool information

Tool name: Rust auto-formatter

When running cargo fmt --all -- --check on OSX I get the following error:
error: 'cargo-fmt' is not installed for the toolchain 'stable-x86_64-apple-darwin'
To install, run `rustup component add rustfmt --toolchain stable-x86_64-apple-darwin`

On both Ubuntu and Linux environments the cargo-fmt package is pre-installed. It would be nice to have a more consistent experience between environments.
Area for Triage:

Question, Bug, or Feature?:
Bug, other environments have this tool out of the box
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[x] macOS 10.15
[x] macOS 11.0
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Can this tool be installed during the build?
rustup component add rustfmt --toolchain stable-x86_64-apple-darwin

Tool installation time in runtime
Very little
Are you willing to submit a PR?
Yes

Hello @aibaars , thank you for feature request.
We don't have objections to add this module to macOS images for consistency.
Feel free to submit or please let us know and we will take care about it.

@maxim-lobanov I think pr #1958 should do the trick.

@aibaars , I have merged PR. Thank you for contribution.
Changes should be deployed with next image rollout (approximately next week).
We will keep issue opened until it is deployed

Thanks!

@aibaars the new image was deployed with cargo-fmt on board. I'm going to close the issue, but feel free to contact us if you have any concerns.
Thank you!


translations PR 20170904

Ideally this PR should be review by community members for each language.
Note: In the event that you see an english translation instead of the desired language is because this PR was submitted before the translation was made on the Mattermost Translation Server and probably will be submitted for the next PR.

need to change the base for this one


Docker-compose build hangs when deploying

I seem to be able to create the host fine, but builds hang when I switch to the new env.  Build works fine with the default env.
🕠  [wprl:~/Code/Abc] develop+ ± docker-machine create --driver digitalocean --digitalocean-access-token abc123 staging
Creating SSH key...
Creating Digital Ocean droplet...
To see how to connect Docker to this machine, run: docker-machine env staging
🕠  [wprl:~/Code/Abc] develop+ ± eval "$(docker-machine env staging)"
🕠  [wprl:~/Code/Abc] develop+ ± docker-compose up
Building elasticsearch...

Running docker-compose build also hangs.  I've tried separately building each container in my docker-compose.yml and each hangs.  I've also tried deploying to AWS this way, with the same results.

Does running normal Docker commands work?  If so, sounds like it might make a better fit for an issue at https://github.com/docker/compose.  Would be worth posting the docker-compose output with --verbose enabled.

OK, thank you.  Yes, normal docker commands like docker run -i -t ubuntu /bin/bash work as expected.  I'll open a ticker under the compose repo.
🕖  [wprl:~/Code/Abc] wprl/deploy-staging+ ± docker-compose --verbose up -d
Compose version 1.4.0
Docker base_url: https://<IP_ADDRESS>:2376
Docker version: KernelVersion=3.13.0-71-generic, Os=linux, BuildTime=Fri Nov 20 13:12:04 UTC 2015, ApiVersion=1.21, Version=1.9.1, GitCommit=a34a1d5, Arch=amd64, GoVersion=go1.4.2
docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=abc', u'com.docker.compose.service=elasticsearch', u'com.docker.compose.oneoff=False']})
docker containers -> (list with 0 items)
docker containers <- (all=True)
docker containers -> (list with 7 items)
docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=abc', u'com.docker.compose.service=api', u'com.docker.compose.oneoff=False']})
docker containers -> (list with 0 items)
docker containers <- (all=True)
docker containers -> (list with 7 items)
docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=abc', u'com.docker.compose.service=logstash', u'com.docker.compose.oneoff=False']})
docker containers -> (list with 0 items)
docker containers <- (all=True)
docker containers -> (list with 7 items)
docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=abc', u'com.docker.compose.service=kibana', u'com.docker.compose.oneoff=False']})
docker containers -> (list with 0 items)
docker containers <- (all=True)
docker containers -> (list with 7 items)
docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=abc', u'com.docker.compose.service=app', u'com.docker.compose.oneoff=False']})
docker containers -> (list with 0 items)
docker containers <- (all=True)
docker containers -> (list with 7 items)
docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=abc', u'com.docker.compose.service=elasticsearch', u'com.docker.compose.oneoff=False']})
docker containers -> (list with 0 items)
docker containers <- (all=True)
docker containers -> (list with 7 items)
docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=abc', u'com.docker.compose.service=api', u'com.docker.compose.oneoff=False']})
docker containers -> (list with 0 items)
docker containers <- (all=True)
docker containers -> (list with 7 items)
docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=abc', u'com.docker.compose.service=logstash', u'com.docker.compose.oneoff=False']})
docker containers -> (list with 0 items)
docker containers <- (all=True)
docker containers -> (list with 7 items)
docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=abc', u'com.docker.compose.service=kibana', u'com.docker.compose.oneoff=False']})
docker containers -> (list with 0 items)
docker containers <- (all=True)
docker containers -> (list with 7 items)
docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=abc', u'com.docker.compose.service=app', u'com.docker.compose.oneoff=False']})
docker containers -> (list with 0 items)
docker containers <- (all=True)
docker containers -> (list with 7 items)
docker inspect_image <- (u'abc_elasticsearch')
Building elasticsearch...
docker build <- (pull=False, nocache=False, stream=True, tag=u'abc_elasticsearch', path='/Users/wprl/Code/Abc', rm=True, dockerfile='./Dockerfile-elasticsearch')

Thanks!


Choosing theme colors

Which colors to choose for UI and editor scheme?
We did explicitly not want to recreate another Pink as Heck, as discussed in enhancement Cute pink dark theme? suggested by @demonlol

Could I expect a togglable white/dark theme for this project? I'm a fan of pink themes, but I can't stand the white... If you're unable to, I can. I figured I'd ask first, seeing this repo is still somewhat active. Thanks in advance!

There are existing dark pink themes (at least I know one, Pink as Heck , but a togglable dark/light would be very cool!
Maybe we only need to change the editor theme and/or base theme, but I see you seem to have an idea already.

I've taken a look at Pink As Heck, but the dev(s) went a little too overboard with the pink. I like your attempt much better.

pragmatic approach: not that dark, especially not the editor pane, like this:

... which would either be another, not so dark version, but maybe even a third variation of the pink UI themes

... and for the actual cute pink dark theme:

it could be less pink, so we could use slightly pinkish dark gray of an otherwise unchanged dark mode editor color scheme,
it could be a more like the "Pink as heck theme" but with a more "cute", warm, friendly pink hue than the neon purple-ish cold tone of Pink as Heck.

Updated theme colors:

base UI theme scheme on dark default
set darker default background
adapt foreground and border colors


Instagram to HTML conversion has bad  tag

Just saw this in one of the items in the feed:
<video class="u-video" src="url" controls="controls">

The embedded video tag in the HTML has the correct source. Which reminds me that the video tag should also be removed from the HTML like in #120

fixed! thanks again.


McuBoot Build Error When Serial Recovery is enabled

This issue list is only for bugs in the main Zephyr code base
(https://github.com/zephyrproject-rtos/zephyr/). If the bug is for a project
fork (such as NCS) specific feature, please open an issue in the fork project
instead.
Describe the bug
It seems like it is trying to use both zcbor from mcuboot and zcbor from zephyr.
Please also mention any information which could help others to understand
the problem you're facing:

Tried to build for frdm_k64, nrf52840_dongle

To Reproduce
Steps to reproduce the behavior:
Followed Instructions from here
Expected behavior
Successful Build of McuBoot
Logs and console output
Console Output during Build
warning: ZCBOR (defined at modules/zcbor/Kconfig:7, modules/zcbor/Kconfig:7) has direct dependencies ZEPHYR_ZCBOR_MODULE || (ZEPHYR_ZCBOR_MODULE && 0) with value n, but is currently being y-selected by the following symbols:
- MCUBOOT_SERIAL (defined at /home/devuser/NrfMcuBootTest/my-workspace/bootloader/mcuboot/boot/zephyr/Kconfig.serial_recovery:7), with value y, direct dependencies y (value: y)

error: Aborting due to Kconfig warnings

Environment (please complete the following information):

OS:  Linux

You do not have zcbor in your manifest, add it to your manifest and run west update


The favorite buttons delegate is not called right away

I am using this which I think is great however I think I am experiencing a button with the favorite button.  The button does not respond to the tap event immediately.  This is a causing an issue when the user presses the favorite button and then closes the screen before the button has a chance to respond.  Is there a way to correct this without changing the favorite button's code?  Thanks, Greg.

I fixed the problem with my code.  I did not realize that the favorite button inherits from uibutton and I could just use the tapped inside event.  I was using the delegate isselected event but should have been using tapped inside.


[SPARK-19004][SQL] Fix testH2Dialect by removing getCatalystType

What changes were proposed in this pull request?
JdbcDialect subclasses should return None by default. However, testH2Dialect.getCatalystType returns always Some(StringType) incorrectly. This PR fixes testH2Dialect by removing the wrong getCatalystType implementation.
How was this patch tested?
This is a test only update.

Test build #70612 has started for PR 16409 at commit fe8f827.

Hi, @gatorsmile .
Could you review this PR?

Test build #70612 has finished for PR 16409 at commit fe8f827.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Thanks! Merging to master.

Thank you for review and merging!


routes not working

I used zyhn tutorial, it was working fine but in your package same code, my module routes.php is included but Route::get not working.. any hint?

Modification in description:
Routes::get loaded but second parameter not working. Below is code:
Route::get('people', function(){
return 'hello';
});

Resolved: Problem was Authentication Controller, I was defined Route:controllers and leave blank for alias auth to resolve url with auth/login.

I would recommend to remove all unnecessary controllers (f.a. which are not in your modules)

Not a single controller is unnecessary, Issue found and fixed.

I have the same issue when running it to my server, Centos 6.6 but on my local its working fine. Any idea? thanks

Can u show me error?
On Sep 17, 2015 12:52 PM, "wabsa"<EMAIL_ADDRESS>wrote:

I have the same issue when running it to my server, Centos 6.6 but on my
local its working fine. Any idea? thanks
—
Reply to this email directly or view it on GitHub
https://github.com/Artem-Schander/L5Modular/issues/1#issuecomment-141012406
.

here: https://github.com/Artem-Schander/L5Modular/issues/5
I think its in naming of module, in my cases modules are in small caps, I capitalized my the first letter as the same of the folder name of each modules.

This is incomplete message.

closing due to inactivity


Flip animation bug in Edge 16

Hi!
But I have a bug with flip animation in Edge 16 on Windows 10 :

I'm investigating this but it is a nasty Edge's transform engine bug that seems to be inherited from IE11. I still don't have the solution but I hope to get there 😅.

@eltonmesquita awesome effort .... I might report this to edge team about this one...


when %j exists in a formatted object, it pulls in the timestamp/delta

I found this when debugging some mysql search strings, so for example looking for a name like "jordan" to appear somewhere in a string, but wrapped with % to match anywhere in the string: %jordan%...
repro:
const demo = require('debug')('demo');
const data = [ '%j' ];
demo('%o', data);

Prints:
demo "\u001b[38;5;166m+30m\u001b[0m"

Note that the timestamp/delta is not appended to the end of the output as usual.
I know that %j is for pulling in json, but this is in the data object I'm running through the formatter. Is recursive formatting supposed to be happening? And even if it is, why would it pull in the timestamp/delta as if that were one of the arguments I was passing into the debug function?

I've also seen %s trigger a similar effect, but when I tried to create a simple repro for the ticket it wouldn't happen on command for me. But here it is happening for an array containing %smith%...

Is recursive formatting supposed to be happening?

Definitely not. Which version of debug are you on? I can't reproduce this on the latest.
> debug('hello')
  foo:bar hello +0ms
undefined
> debug('$o', ['hello'])
  foo:bar $o [ 'hello' ] +12s
undefined
> debug('$o', ['%jelly%'])
  foo:bar $o [ '%jelly%' ] +5s
undefined
> debug('$o', ['%j'])
  foo:bar $o [ '%j' ] +19s
undefined

4.3.4


Translated and fixed copyright and get-started page in hi.yml

Fixes #656
Changes:
Completed translation of copyright and get-started page to Hindi. This involves fixing the untranslated parts of the page and the incorrect translations.

@montoyamoraga @limzykenneth @shaharyar-shamshi Please review this PR. Thanks!


Managing Azure Secrets on GitHub

There is a plugin that would be useful for doing a verifiable scan of GitHub for Azure secrets as part of the checklist process.
https://azure.microsoft.com/en-au/blog/managing-azure-secrets-on-github-repositories/

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

ID: 2ee135e3-2efc-3e1d-d0e7-58be674ce30f
Version Independent ID: d0dc7e0c-d189-9491-1b37-b6a22a5adc98
Content: Migration checklist - VSTS Public Project
Content Source: docs/organizations/public/migration-checklist.md
Product: devops
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

Added link to the blog post from the article.


[NBS 1.0] Move notifications service definition to core

Hey, I just made a Pull Request!
Ref: https://github.com/backstage/backstage/issues/24851
Transfer notifications service ref from its plugin to the backend-plugin-api package.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Sorry it's too early to move notifications into core. We at least need to settle the BEP and preferably also have it in use for some time too imo.

Is there a way to mark this experimental? I was wondering if there is a way of telling consumers that this is experimental, might is not stable yet. Maybe export as alpha?

Our decision was to push back on this and give the notifications service more time to be broadly used before moving it into core services.
cc/ @Rugvip


Missing 'sensor.parameters_changed()'

Hi,
Thanks for your excellent work. I'm trying to regenerate the figure in your paper following the instruction in readme. However, I got strange results of the lego scene after running python limitations.py.

Is that the right way to generate the figure? Thanks

Btw, I find there is already something abnormal with the ref images, which have inconsistent sizes from different views.
May be that is the cause?

It seems that a line of code is missed here:
sensor.parameters_changed()
This will fix it.


Unity and .Net Core 2 and forward

Is there any chance for us to get a example/tutorial on how to hook this with Asp.Net Core 2+? tks a lot...

I am a bit busy with v6 at the moment.
Do you want to try to create it yourself? I will help if you get stuck..

yeah sure! i actually have been trying for a day or more to do so... i've been trying to do so like this: https://stackoverflow.com/questions/39173345/unity-with-asp-net-core-and-mvc6-core/39173346?noredirect=1#comment85597225_39173346
right now i'm stuck on 2 parts:

IsRegistered() is yielding false positives for registrations such as "IServer" and other MVC registrations, therefore not using the fallback and then breaking...

After blunt forcing a || !Type.FullName.Contains("MyProject") that forces the fallback, i get a parameter null exception that i can't seem to track back...

Here's a link to a sample code: https://wetransfer.com/downloads/cd1bc4dff43f0cd3a03f312dc414fe5c20180315133154/d28259a05122f4166a8b08b41a49854420180315133155/5934fd

@ENikS the link above is now expired... when you get a chance ping me here and ill re-upload...

Done


[TextField] Fix TextField crashed with composing and maxLength set

Description
This is a fix for TextField, which prevent formatter updates while the TextEditingValue is composing, lead to a crash.
It happens from flutter 1.0.0 until now.

Before
After

Related Issues
Resolves #63753 .
Tests
I added the following tests:
Pending for more support.
Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I signed the [CLA].
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change.

@googlebot I signed it!

Hey I am very new to contributing  , I have read documentations but I am still confused that how to proceed

Looks like this change is causing some tests to fail: https://cirrus-ci.com/task/4806069081866240. This can either mean you're breaking existing functionality or the tests need to be updated. Can you please take a look at those?
Also, in order to accept this PR you will have to write a test to ensure that we never regress and accidentally re-introduce the bug into our code base. Can you please add some tests?
/cc @justinmc

Yeah I just forgot to put this into WIP.

@cv692001 I'm not sure if you're asking in relation to this PR, but if you're just asking about contributing in general, feel free to reach out to me via the contact info in my Github profile.

There's something wrong with my develop environment and I couldn't run tests normally. Scheduled tests update for 2~3 days. Sorry for that. 😢

@goderbauer @justinmc I have a question about using the tester to simulate the composing input.
I wrote something like this:
final EditableTextState state =
  tester.state<EditableTextState>(find.byType(EditableText));

state.updateEditingValue(const TextEditingValue(text: '111 1'));
expect(state.currentTextEditingValue.composing, TextRange.empty);

state.updateEditingValue(const TextEditingValue(text: '111 1', composing: TextRange(start: 2, end: 4)));
expect(state.currentTextEditingValue.composing, const TextRange(start: 2, end: 4));

state.updateEditingValue(const TextEditingValue(text: '111 11', composing: TextRange(start: 2, end: 5)));
expect(state.currentTextEditingValue.composing, const TextRange(start: 2, end: 5));

When I tried to add more text with composing like '111 11' (6 characters) it ends up nothing happened. How can I achieve the effect just like the real device's? (Like the screenshot below)

Forget about it. I forgot that I run this on stable, now it works on the new one.

I worry that this is a problem too:

Maybe we shouldn't count composing characters as part of the character limit?  Would a native Chinese speaker expect the behavior in the screenshot, or should the character count be zero until the composing characters are committed?

CC @LongCatIsLooong

We should watch out for this causing any undesirable behavior in any existing Flutter apps. For example, with this PR, it's now possible to get an invalid value from a TextField using textFieldController.text. That may cause some Flutter apps to receive invalid values when they previously could not, if they're not checking the valid state of the form.

@justinmc I'll see if I can add a test to ensure it won't happened.

IMO we shouldn't specialize LengthLimitingTextInputFormatter. The fix should be applied to the implementation of that formatter if possible.

That make sense.

Other input formatters (even third party ones) may have this issue too, @AlexV525 did you by any chance look into why it crashes?

Basically when the composing editing value is updated by the formatter, the composing TextRange's end is more than the length of the texts.
Let's go back to the crashing screenshot. Such as 12345 (with 5 composing TextRange(start: 3, end: 4)), then type 6, the value was updated to 12346  (with 6  composing). Since then the composing might be TextRange(start: 3, end: 5) which is more than the actual length. At this time, call delete and the substring is failed, and crashed.

After a few hours of investigation, I found that it's hard to land this fix directly on the LengthLimitingTextInputFormatter. Here is a strange behavior I saw:

Input aaaa, with the TextField displayed a a a.
Input another 'a', now the value in _formatAndSetValue becomes a, which means it's been truncated or updated from the method _handleTextInputInvocation.
Continuing input multiple a, then delete when it's over-sized, crashed again.

If we only release the constraint inside the LengthLimitingTextInputFormatter, value won't be truncated when the composing is end and I see no events related.
Maybe it's something with keyboard behavior and the only thing we can do is what we currently have done.

Now the changes is both landed on LengthLimitingTextInputFormatter and the _formatAndSetValue, to keep composing status unified.

We should watch out for this causing any undesirable behavior in any existing Flutter apps. For example, with this PR, it's now possible to get an invalid value from a TextField using textFieldController.text. That may cause some Flutter apps to receive invalid values when they previously could not, if they're not checking the valid state of the form.

The last thing is about this concern. For me, technically, it should be the current value whether it's composing or not. I added a test about form validation when the value composing. Although it can return false if the composing value cannot pass the validator, we definitely should keep our eyes on related behaviors.

I've updated the description for behavior changes.

(knock knock...)


pin version

Pin apps version

No, it ensures that we build the container with the version of an app and not the latest version without knowing
It still does not solve the problem about the versioning when a new release of the app occurs
Figure is certainly the most problematic since it will require a web and server docker change


Duplicate issue with GDrive !!!

Hi,
I encounter the issue of Duplicate file detected error with GDrive. I do only sync from my NAS to Drive and if I check duplicate rclone indicates I find them well on Drive. Is there a way to resolve that problem ? out of emptying directories concerned on Drive and doing the sync again ???
Thanks
Vincèn

What is your rclone version (eg output from rclone -V)
1.32
Which OS you are using and how many bits (eg Windows 7, 64 bit)
FreeNAS 9.3 (FreeBSD 64 bits)
Which cloud storage system are you using? (eg Google Drive)
Google Drive unlimited (Google Apps)
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone sync /localstorage /Drive:remotedirectory
A log from the command with the -v flag (eg output from rclone -v copy /tmp remote:tmp)
rclone.backup.tar.gz

No solution ??

I'm away at the moment with limited Internet (GPRS!) will study your issue
when I get back next week.

Héhé sure, no problem ;) Thanks

Cant you run rclone's dedupe?  You can try with the --dry-run option first to see what it would find.  Maybe I misunderstood though.
rclone dedupe

I looked through your log file and I didn't see any errors?  Did you log stdout and stderr to different places?  (By default the output for -v goes to stdout whereas the log messages go to stderr.)  You can use the --log-file option to get them in the same place.

Hopefully rclone dedupe solved your problem.  If not please re-open!


Version of adapter is not visible for dbt --version command

The common way to know the version of dbt and installed adapters is command dbt --version.
However, for dbt-synapse and dbt-fabric adapters there is no such information at all.
Is is possible to add such information there?
Here is the log of insatllation/re-installation and output for version command:
root@819a2d99aa78:/# pip install -U dbt-synapse
Requirement already satisfied: dbt-synapse in /usr/local/lib/python3.11/site-packages (1.7.0)
Requirement already satisfied: dbt-fabric~=1.7.4 in /usr/local/lib/python3.11/site-packages (from dbt-synapse) (1.7.4)
Requirement already satisfied: dbt-core~=1.7.2 in /usr/local/lib/python3.11/site-packages (from dbt-fabric~=1.7.4->dbt-synapse) (1.7.10)
Requirement already satisfied: pyodbc<5.1.0,>=4.0.35 in /usr/local/lib/python3.11/site-packages (from dbt-fabric~=1.7.4->dbt-synapse) (5.0.1)
Requirement already satisfied: azure-identity>=1.12.0 in /usr/local/lib/python3.11/site-packages (from dbt-fabric~=1.7.4->dbt-synapse) (1.15.0)
Requirement already satisfied: azure-core<2.0.0,>=1.23.0 in /usr/local/lib/python3.11/site-packages (from azure-identity>=1.12.0->dbt-fabric~=1.7.4->dbt-synapse) (1.30.1)
Requirement already satisfied: cryptography>=2.5 in /usr/local/lib/python3.11/site-packages (from azure-identity>=1.12.0->dbt-fabric~=1.7.4->dbt-synapse) (42.0.5)
Requirement already satisfied: msal<2.0.0,>=1.24.0 in /usr/local/lib/python3.11/site-packages (from azure-identity>=1.12.0->dbt-fabric~=1.7.4->dbt-synapse) (1.27.0)
Requirement already satisfied: msal-extensions<2.0.0,>=0.3.0 in /usr/local/lib/python3.11/site-packages (from azure-identity>=1.12.0->dbt-fabric~=1.7.4->dbt-synapse) (1.1.0)
Requirement already satisfied: agate~=1.7.0 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (1.7.1)
Requirement already satisfied: Jinja2<4,>=3.1.3 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (3.1.3)
Requirement already satisfied: mashumaro~=3.9 in /usr/local/lib/python3.11/site-packages (from mashumaro[msgpack]~=3.9->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (3.12)
Requirement already satisfied: logbook<1.6,>=1.5 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (1.5.3)
Requirement already satisfied: click<9,>=8.0.2 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (8.1.7)
Requirement already satisfied: networkx<4,>=2.3 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (3.2.1)
Requirement already satisfied: colorama<0.5,>=0.3.9 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (0.4.6)
Requirement already satisfied: pathspec<0.12,>=0.9 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (0.11.2)
Requirement already satisfied: isodate<0.7,>=0.6 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (0.6.1)
Requirement already satisfied: sqlparse<0.5,>=0.2.3 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (0.4.4)
Requirement already satisfied: dbt-extractor~=0.5.0 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (0.5.1)
Requirement already satisfied: minimal-snowplow-tracker~=0.0.2 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (0.0.2)
Requirement already satisfied: dbt-semantic-interfaces~=0.4.2 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (0.4.4)
Requirement already satisfied: jsonschema>=3.0 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (4.21.1)
Requirement already satisfied: packaging>20.9 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (24.0)
Requirement already satisfied: protobuf<5,>=4.0.0 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (4.25.3)
Requirement already satisfied: pytz>=2015.7 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (2024.1)
Requirement already satisfied: pyyaml>=6.0 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (6.0.1)
Requirement already satisfied: typing-extensions>=3.7.4 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (4.10.0)
Requirement already satisfied: cffi<2.0.0,>=1.9 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (1.16.0)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (3.6)
Requirement already satisfied: requests<3.0.0 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (2.31.0)
Requirement already satisfied: urllib3~=1.0 in /usr/local/lib/python3.11/site-packages (from dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (1.26.18)
Requirement already satisfied: Babel>=2.0 in /usr/local/lib/python3.11/site-packages (from agate~=1.7.0->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (2.14.0)
Requirement already satisfied: leather>=0.3.2 in /usr/local/lib/python3.11/site-packages (from agate~=1.7.0->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (0.4.0)
Requirement already satisfied: parsedatetime!=2.5,>=2.1 in /usr/local/lib/python3.11/site-packages (from agate~=1.7.0->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (2.6)
Requirement already satisfied: python-slugify>=1.2.1 in /usr/local/lib/python3.11/site-packages (from agate~=1.7.0->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (8.0.4)
Requirement already satisfied: pytimeparse>=1.1.5 in /usr/local/lib/python3.11/site-packages (from agate~=1.7.0->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (1.1.8)
Requirement already satisfied: six>=1.11.0 in /usr/local/lib/python3.11/site-packages (from azure-core<2.0.0,>=1.23.0->azure-identity>=1.12.0->dbt-fabric~=1.7.4->dbt-synapse) (1.16.0)
Requirement already satisfied: pycparser in /usr/local/lib/python3.11/site-packages (from cffi<2.0.0,>=1.9->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (2.21)
Requirement already satisfied: importlib-metadata~=6.0 in /usr/local/lib/python3.11/site-packages (from dbt-semantic-interfaces~=0.4.2->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (6.11.0)
Requirement already satisfied: more-itertools<11.0,>=8.0 in /usr/local/lib/python3.11/site-packages (from dbt-semantic-interfaces~=0.4.2->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (10.2.0)
Requirement already satisfied: pydantic<3,>=1.10 in /usr/local/lib/python3.11/site-packages (from dbt-semantic-interfaces~=0.4.2->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (2.6.4)
Requirement already satisfied: python-dateutil~=2.0 in /usr/local/lib/python3.11/site-packages (from dbt-semantic-interfaces~=0.4.2->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (2.9.0.post0)
Requirement already satisfied: MarkupSafe>=2.0 in /usr/local/lib/python3.11/site-packages (from Jinja2<4,>=3.1.3->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (2.1.5)
Requirement already satisfied: attrs>=22.2.0 in /usr/local/lib/python3.11/site-packages (from jsonschema>=3.0->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (23.2.0)
Requirement already satisfied: jsonschema-specifications>=2023.03.6 in /usr/local/lib/python3.11/site-packages (from jsonschema>=3.0->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (2023.12.1)
Requirement already satisfied: referencing>=0.28.4 in /usr/local/lib/python3.11/site-packages (from jsonschema>=3.0->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (0.33.0)
Requirement already satisfied: rpds-py>=0.7.1 in /usr/local/lib/python3.11/site-packages (from jsonschema>=3.0->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (0.18.0)
Requirement already satisfied: msgpack>=0.5.6 in /usr/local/lib/python3.11/site-packages (from mashumaro[msgpack]~=3.9->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (1.0.8)
Requirement already satisfied: PyJWT<3,>=1.0.0 in /usr/local/lib/python3.11/site-packages (from PyJWT[crypto]<3,>=1.0.0->msal<2.0.0,>=1.24.0->azure-identity>=1.12.0->dbt-fabric~=1.7.4->dbt-synapse) (2.8.0)
Requirement already satisfied: portalocker<3,>=1.0 in /usr/local/lib/python3.11/site-packages (from msal-extensions<2.0.0,>=0.3.0->azure-identity>=1.12.0->dbt-fabric~=1.7.4->dbt-synapse) (2.8.2)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.11/site-packages (from requests<3.0.0->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (3.3.2)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.11/site-packages (from requests<3.0.0->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (2024.2.2)
Requirement already satisfied: zipp>=0.5 in /usr/local/lib/python3.11/site-packages (from importlib-metadata~=6.0->dbt-semantic-interfaces~=0.4.2->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (3.18.1)
Requirement already satisfied: annotated-types>=0.4.0 in /usr/local/lib/python3.11/site-packages (from pydantic<3,>=1.10->dbt-semantic-interfaces~=0.4.2->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (0.6.0)
Requirement already satisfied: pydantic-core==2.16.3 in /usr/local/lib/python3.11/site-packages (from pydantic<3,>=1.10->dbt-semantic-interfaces~=0.4.2->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (2.16.3)
Requirement already satisfied: text-unidecode>=1.3 in /usr/local/lib/python3.11/site-packages (from python-slugify>=1.2.1->agate~=1.7.0->dbt-core~=1.7.2->dbt-fabric~=1.7.4->dbt-synapse) (1.3)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
root@819a2d99aa78:/# dbt --version
Core:
  - installed: 1.7.10
  - latest:    1.7.10 - Up to date!


Cartesian Genetic Programming

Implement basic CGP support.  Should go quick if I translate some of my old Java code into Python.

CGP implementation progress & plan:

CGPExecutable: wrap a networkx-based graph phenotype
CGPDecoder: decode integer genomes into CGPExecutables
create_int_vectors(): place in a new leap_ec.int_rep package
int_mutate(): random mutation within integer bounds
cgp_mutate(): call int_mutate(), parameterized with CGP-specific range constraints
cgp_visualize_probe(): display the networkx graph for the best individual in the population


create light color scheme sample override

Partly as a challenge to myself, but also think it's worth showing the power of the theme!

Included in PR #75. Closing.


fix(datastore): Continue initial sync if atleast one model from schema succeeds

Issue #

3136
Description

Initial Sync fails when one or more models fail to sync. In this PR, this condition is changed. Now initial sync will return success if atleast one model sync succeeds.
General Checklist

[x] Added new tests to cover change, if needed
[x] Build succeeds with all target using Swift Package Manager
[x] All unit tests pass
[x] All integration tests pass
[ ] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
[ ] Documentation update for the change if required
[x] PR title conforms to conventional commit style
[x] New or updated tests include Given When Then inline code documentation and are named accordingly testThing_condition_expectation()
[ ] If breaking change, documentation/changelog update with migration instructions

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

Codecov Report

Merging #3224 (45bddcd) into main (9a05bdd) will decrease coverage by 6.04%.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main    #3224      +/-   ##
==========================================
- Coverage   64.61%   58.57%   -6.04%
==========================================
  Files        1091      556     -535
  Lines       37071    16907   -20164
==========================================
- Hits        23952     9903   -14049
+ Misses      13119     7004    -6115

Flag
Coverage Δ

API_plugin_unit_test
?

AWSPluginsCore
?

Amplify
47.86% <ø> (+0.01%)
:arrow_up:

Analytics_plugin_unit_test
?

Auth_plugin_unit_test
?

CoreMLPredictions_plugin_unit_test
?

DataStore_plugin_unit_test
80.07% <100.00%> (+0.07%)
:arrow_up:

Geo_plugin_unit_test
?

Logging_plugin_unit_test
63.18% <ø> (ø)

Predictions_plugin_unit_test
35.17% <ø> (ø)

PushNotifications_plugin_unit_test
?

Storage_plugin_unit_test
?

unit_tests
58.57% <100.00%> (-6.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

...gin/Sync/InitialSync/InitialSyncOrchestrator.swift
83.01% <100.00%> (+0.66%)
:arrow_up:

... and 539 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Improve async cache message and reduce spamminess

@apc999 Please take a look

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/11046/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/11073/
Test PASSed.

alluxio-bot, merge this please


Inconsistent initial state.value on interpreter start

Bug or feature request?
Potential Bug
Description:
The initial state.value is differs when I start an interpreter with a string vs and object
const machine = Machine({
  initial: 'address',
  states: {
    address: {
      id: 'address',
      initial: 'shipping',
      states: {
        shipping: {
          id: 'shipping'
        }
      }
    }
  }
});
const interpreter = interpret(machine).onTransition(state => {
  console.log(state.value);
});
interpreter.start({ address: '' });
// { address: {} }
interpreter.start(State.from({ address: '' }));
// { address: {} }
interpreter.start('address');
// { address: "shipping" }
interpreter.start(State.from('address'));
// { address: "shipping" }

https://codesandbox.io/s/lp12yxl36m
(Bug) Expected result:
Consistent state.value that I think should equal: { address: "shipping" }
(Bug) Actual result:
This codesandbox demonstrates my concern: https://codesandbox.io/s/lp12yxl36m
(Bug) Potential fix:
I would think that the state.value in my example would consistently resolve to:
{
address: "shipping"
}
Required! If you found a bug and can consistently reproduce it, please take a minute to think about what the potential fix might be.
Even if the fix is incorrect, this can help diagnose and find the solution to the issue as quickly as possible.
I also strongly encourage you to create a pull request if you are confident in the potential fix.
(Feature) Potential implementation:
Required! If you would like to see a feature or enhancement make its way to xstate, please describe:

What the API would look like
If this is a breaking change
If this is part of the existing SCXML specification

Link to reproduction or proof-of-concept:
https://codesandbox.io/s/lp12yxl36m

The problem is that { address: '' } is an invalid state value; it's the same as if you were to put { address: 'fake' } - 'fake' is not a state node of address.
It is not intentional (or planned) for empty strings to resolve to state values. What should happen here is for an error to be thrown, that { address: '' } is not a valid state value for the machine and it could not resolve the state.
What is your use-case as to why you are passing in an invalid state value?

I fully agree with what you're saying.  I agree that xstate should throw.
No real use case, just something I ran into when I was tweaking my unit tests when I upgraded from 4.3.3 to 4.5.

I was thinking that you had built a fancy state resolver to handle empty strings.


feat(client): show and execute backend project tests

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.

Related #17548
Need to write tests for apis-and-microservices-projects and information-security-and-quality-assurance-projects

While QA I found that the current state of master is completely broken for the backend projects.
This error seems to be pre-existing on master and I am not sure where it managed to creep in from (thanks no integration tests!).

@ValeraS can you please take a look what's going wrong? Its not linked to your PR, but you are the closest one to the issue.

Everything LGTM now!  One thing that would help during QA is just to push any changes as new commits, rather than rebasing.  Just to make changes easier to track.
The PR looks good, though.  Backend projects can be tested and frontend projects behave like they do in production.

Need to write tests for apis-and-microservices-projects  and information-security-and-quality-assurance-projects

Just to confirm, this PR still needs this before we can land this on master? If yes, would @freeCodeCamp/moderators be interested in adding those tests? This will be a great improvement to land.

Need to write tests for apis-and-microservices-projects  and information-security-and-quality-assurance-projects

Just to confirm, this PR still needs adding the tests before we can land this on master? If yes, would @freeCodeCamp/moderators be interested in adding those tests? This PR will be a great improvement to land.

Tests are already written, see: https://fcc-back-end-tester.glitch.me

@christophrus It is my understanding that the Glitch app you referenced is not quite up to date and many of the tests are either not correct or some of the projects are not tested.

@raisedadead

Just to confirm, this PR still needs adding the tests before we can land this on master?

No, we can land this PR without tests and add tests in other PRs. Where we do not have tests, Campers pass projects without any checks as before.

[...] I compiled this glitch app together from all the different broken or uncomplete glitch apps that I could find and fixed the obvious errors of them while I was testing my projects when I went through the curriculum like 2-3 month ago. So this app includes tests for all current projects and dont has any errors that I would know about.

I think @christophrus wanted to tag @RandellDawson instead.
@christophrus This is some amazing work, we would love your help in bringing some of those tests and fixes to the main repo here and the glitch projects too if needed. I'll ask @scissorsneedfoodtoo and @RandellDawson to help you and guide with this further.
Essentially we would want to have tests for all the projects so that they are tested as per the functionality added in this PR.
Let us know your thoughts in this.

No, we can land this PR without tests and add tests in other PRs. Where we do not have tests, Campers pass projects without any checks as before.

@ValeraS thanks for confirming, I'll pull this down and land this soon.

@raisedadead Yeah I would try to do it, but I would definitly need some assistance with it. First of all I need to know how the current state is. Can I simply set up an fcc dev enviroment, put in the rules into the specific .md files and then try to debug them? Or do I have to turn some switch to get the rules from the .md files applied?

Sure, we are here to help you help us.
You should hit us up in Contributors Chat room for a more real time chat. @RandellDawson and @ojeytonwilliams and a few others including @scissorsneedfoodtoo (from the dev team) can guide you on the approach.

@christophrus Are you still interested in adding the tests from the glitch project?  Just reach out to us on Gitter via the Contributors Chat room or DM on Gitter.

@RandellDawson Yeah absolutely, found it kind of hard to get an overview about what's going on in this gitter thingy and eventually got distracted by other things I moved on to.

@christophrus If you have a forum account, you can also send a DM to me over there.  I have the same username on the forum.

@christophrus, your compilation of all of the broken Glitch projects sound great, and your tests for these projects will be really helpful to other learners.

Hi all. Just chiming in to say, let's discuss this over a new thread so that its tracked instead of this PR thread, for sake of context of the new action items.

Bump https://github.com/freeCodeCamp/freeCodeCamp/issues/36467

let's discuss this over a new thread so that its tracked instead of this PR


docs: update following #3505

Problem:
Annotation and docs were not update accordingly in #3505
Solution:
Update them

Thanks!


ruff check needs --range

I want to be able to use the following command to check existence of type hints across a range in a python file, specifically to prevent new callables from being added without type hints:
ruff check --select ANN --ignore ANN101,ANN102 --range <start_line>-<end_line> <file.py>

Why is this currently not available like it is in ruff format?
It hinders my ability to gradually enter checking over a large mature codebase.

Why is this currently not available like it is in ruff format?

Range formatting is an important formatter that many editors require, linting only a range is something that's less common.
I don't see specific reasons why Ruff can't support linting just a range, but there's quiet a bit of complexity involved and I don't expect us to prioritize this highly in the near future.


runtime: make the weak definition also inline'd

Use the reserved spelling for the weak attribute.  Furthermore, mark the
definition as inline.  THis is needed to build the runtime on Windows where
there are multiply defined instances of the function as weak function
definitions are not supported in the PE/COFF model.  Since the Private.h
header usage is limited to the runtime, which does not link against the LLVM
Support library, the strong definition will never be present anyways and so this
maintains the status quo.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @dcci @jrose-apple

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 62705af705c61b5eef78d4ee4f603898c6977c06

@jrose-apple ... sure, I can try moving the definition into an implementation file to avoid the multiple emissions.  However, weak symbols do not work period.  The closest thing to it is a weak reference that is resolved statically at link time.

IIRC that's actually what we want here, on all platforms. If you know another way to get that that'd be great.

It looks like what's there was mostly just @dcci trying to get things working back in #14138, not a specific solution.

@jrose-apple, sounds good ... lets get this working, but I'll see if I can come up with something that accomplishes that on all the platforms.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 62705af705c61b5eef78d4ee4f603898c6977c06

Build failed
Swift Test OS X Platform
Git Sha - 62705af705c61b5eef78d4ee4f603898c6977c06

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - bdc3b8f1c15ed8b27138cbc49daa465356c0f550

Build failed
Swift Test OS X Platform
Git Sha - bdc3b8f1c15ed8b27138cbc49daa465356c0f550

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 685df1234eb1615f4cfb2ad6350c62276e6e1925

Build failed
Swift Test OS X Platform
Git Sha - 685df1234eb1615f4cfb2ad6350c62276e6e1925

@swift-ci please test


Disable captive portal?

Hi Magnus, to disable the captive portal, is it sufficient to comment these lines?
  ap:
    ssid: "xxxxxxxx Fallback Hotspot"
    password: "xxxxxxxxxxxxxxxxxxxxx"

captive_portal:

Thank you! :)
PS: Ups, maybe I'm just looking at the "wrong" ESP32s of mine, which has not your inetbox2mqqt. If that's the case, ashes on my head, and please forgive me my mistake. blush

indeed! You are in the wrong repo! ;-)

Have fun with fabian :-)

You renegade


'compile' hook doesn't exist in MultiCompiler

Do you want to request a feature or report a bug?
feature
What is the current behavior?
'compile' hook doesn't exist.
What is the expected behavior?
'compile' hook should exist.
If this is a feature request, what is motivation or use case for changing the behavior?
Compatibility with webpack-dev-middleware and webpack-hot-middleware.

There is no compile hook on the MultiCompiler. webpack-dev-server shoudn't use the hook for invalidation. The invalid hook can be used for invalidation. There is no need for a compile hook, and it doesn't make sense.


Elasticsearch 8 compatible high-level client integration

This PR integrates the Elasticsearch 8 compatible high-level client in the index layer. Next to the current obsolete TCP and HTTP clients the new client is available via the IndexAdmin interface (IndexAdmin#es8Client()). This client is only available when the connected cluster is version 8.0 or higher. The currently supported client version is 8.3.2.

Codecov Report

Merging #1047 (f9cdb21) into 8.x (f13da26) will decrease coverage by 0.35%.
The diff coverage is 4.77%.

@@             Coverage Diff              @@
##                8.x    #1047      +/-   ##
============================================
- Coverage     65.01%   64.65%   -0.36%
- Complexity    12268    12275       +7
============================================
  Files          1701     1703       +2
  Lines         56563    56895     +332
  Branches       5231     5286      +55
============================================
+ Hits          36773    36788      +15
- Misses        17543    17859     +316
- Partials       2247     2248       +1

Impacted Files
Coverage Δ

....index/src/com/b2international/index/Searcher.java
50.00% <0.00%> (-50.00%)
:arrow_down:

...m/b2international/index/es/EsDocumentSearcher.java
73.74% <0.00%> (-6.66%)
:arrow_down:

.../com/b2international/index/es/client/EsClient.java
61.53% <ø> (ø)

...2international/index/es/query/Es8QueryBuilder.java
0.00% <0.00%> (ø)

...index/src/com/b2international/index/query/Knn.java
0.00% <0.00%> (ø)

...ternational/index/revision/RevisionIndexAdmin.java
66.66% <0.00%> (-2.30%)
:arrow_down:

...snowowl/core/request/RevisionIndexReadRequest.java
70.83% <0.00%> (-3.08%)
:arrow_down:

...tional/index/revision/DefaultRevisionSearcher.java
61.53% <37.50%> (-6.11%)
:arrow_down:

...m/b2international/index/es/admin/EsIndexAdmin.java
81.37% <57.14%> (-0.49%)
:arrow_down:

...b2international/index/es/EsIndexClientFactory.java
69.69% <60.00%> (-2.31%)
:arrow_down:

... and 8 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 f13da26...f9cdb21. Read the comment docs.


Create User Interface For Web

I'm here, Can i join the UI design

Sir, where are the asset files sir? So we get started

I'm here, Can i join the UI design

Yes you can.

Sir, where are the asset files sir? So we get started

I am still looking for a new one you can use. I'll upload one over soon.

Please sir, can you do that soon?

I uploaded a Figma file to the UI Design team already.

I can't find it though
On Fri, May 1, 2020, 9:06 AM Temitope Ajiboye<EMAIL_ADDRESS>wrote:

I uploaded a Figma file to the UI Design team already.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/codeclannigeria/codeclannigeria.dev/issues/7#issuecomment-622292626,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANRT6JHC3RHH3OG5UODDOFLRPJ7H3ANCNFSM4MTUFHJQ
.

I uploaded a Figma file to the UI Design team already.

I can't find the Figma file too

Follow this conversation if you are part of the UI design team
https://github.com/orgs/codeclannigeria/teams/uidesign/discussions/1


jsc.paths: invalid path added to require in some cases

Describe the bug
I've tried to enable jsc.paths in my project, but with no luck, because swc generate wrong paths in some cases. I've extracted reproducible project to https://github.com/Strate/swc-paths-test
Input code
Test project with reproducible bug located here: https://github.com/Strate/swc-paths-test

Steps:

git clone git@github.com:Strate/swc-paths-test.git
cd swc-paths-test
npm install
npm test
Expected output:

SUCCESS
Actual output:

internal/modules/cjs/loader.js:905
  throw err;
  ^

Error: Cannot find module './core/utilFile'

Config
{
  "jsc": {
    "parser": {
      "syntax": "typescript"
    },
    "target": "es2019",
    "baseUrl": "./src",
    "paths": {
      "core/*": ["core/*"],
      "utils/*": ["utils/*"],
      "core": ["core"],
      "utils": ["utils"]
    }
  },
  "module": {
    "type": "commonjs"
  }
}

Playground link
https://github.com/Strate/swc-paths-test
Expected behavior
swc expected to generate valid path to required file, using jsc.paths mappings
Version
1.2.112
Additional context
No response

I think this is fixed by https://github.com/swc-project/swc/pull/3142

I'll re-close this after adding test

@kdy1 FYI - i've checked my repo with @swc/cli@latest @swc/core@latest with no luck. Maybe your fix is not published yet.

Yeah it's not published.


readme - add pypi version badge

see diff

Codecov Report

Merging #19 (670d21d) into main (464ea92) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #19   +/-   ##
=======================================
  Coverage   94.95%   94.95%
=======================================
  Files          15       15
  Lines         615      615
=======================================
  Hits          584      584
  Misses         31       31

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 464ea92...670d21d. Read the comment docs.