Windows support

It would be really nice to support Windows users. However, just currently calls sh explicitly, which isn't available on Windows.
Some ideas:

Use the sh provided by the ubuntu subsystem in Windows 10
Allow using cmd.exe or powershell on windows
Write a sh in rust that runs on every platform

3 is probably the best solution, but also the most work.

This could be support with a "shlex" function like python's. It wouldn't do much but it would probably work for 90% of cases.

It looks like cmd.exe /c COMMAND is the way to run arbitrary commands on windows.

The main thing stopping me from adding windows support at the moment is that I would have no way to test it, since I don't know how to spin up a windows VM, install rust, install just, and test.

AppVeyor is the way to go for windows CI.

Whoops, didn't mean to close.

Hello,
I started a fork when I've succeeded into running just on Windows : https://github.com/Meralis40/just
But there are the following :

justfile must be with '\n' only, but standard on Windows is "\r\n"
sh must be on path

I've just tested basic commands, like running just build and just check on just directory.
It can be a workaround until #161 is resolved. What do you think ?

Hi @Meralis40!
Sorry for not responding earlier. I think that your fork looks reasonable. The justfile grammar can be modified to accept \n or \r\n.
Have you tried running the tests? I think that some of them may have unixisms in them, but they can probably be fixed.
What version of sh are you testing with?
I want to merge your code, but I need to set up a windows environment set up so I can build and test it, and I'm not sure when I'll be able to get to that.

For the sh version I'm testing, I'm using the bash provided with GitHub Desktop (v4.3.46). It's one build with MSys.
For the tests, I've just made a new commit who fix a lot of them, because of exit code (on Windows, we have -1 and not 255).
10 tests keeps failing, it's in this document : https://github.com/Meralis40/just/blob/master/failing_tests_windows.txt
Some on them are because of shebang, not supported on Windows.

Hmm, pretty interesting. I'm guessing that a lot of windows users will have sh on their path from their git installation, so depending on that will be good enough for v1 of windows support.
I got cracking on this in the windows branch:
https://github.com/casey/just/tree/windows
I based a lot of the changes on the code that you uploaded to your branch, I hope that's okay.
I expect to finish some time this week, or this weekend at the latest.

It's ok, the work I've done was more for trying to get a basic version of just in Windows.
I will test it when I can.

Finally fixed with a series of changes, ending with #189
Thanks for getting the ball rolling, @Meralis40!
I've tested things under github desktop for windows and git bash, and it should work under cygwin as well.
It uses the cygpath utility to translate the path to the interpreter in shebang paths and construct an equivalent command, so shebangs should work.
@Meralis40: You mentioned an issue with \r\n line endings, but I didn't run into problems with them. Did I perhaps miss a case?

Closing this issue since everything should be working. I'm going to set up continuous integration on windows with appveyor so that things don't break going forward.


Treat meteor packages as npm packages

I'm using this tool here on a project which is based on Meteor.
Meteor has it's own package-management which is compliant to the npm-notation, but cannot be found in the NPM folder - which looks like following:
import { ValidatedMethod } from 'meteor/mdg:validated-method';

The import stated above imports the module https://atmospherejs.com/mdg/validated-method which has to be installed in your project. The text meteor/ is used as a keyword here to let the meteor-internal NPM fork search for a package in the meteor package list.
I'd like this project to include these packages in the generated output when adding --include-npm or to add another option to allow it.

I'm afraid this is out of the scope for Madge.

Could I then get an option that would not verify that a package actually exists in the node_modules folder bug just lists it in the output ..? I would also be OK if this would then be an additional --include-all-imports or something like this. In my opinion this is within the scope of this package and would even add to other eco-systems where they have their additional package-management-system, like Meteor has.

I'm open for a PR to fix this but nothing I'll be working on. The purpose of Madge is to analyze your own packages and not NPM modules.


data

Can the data be downloaded from Google Cloud Disk etc.?

@hongjianyuan you can use this direct link to download the dataset now: https://drive.google.com/drive/folders/1zqbdkQF8i5cEmZOGmbdQm-EP8dRYtvss?usp=sharing


Update extension properties to support parse value (openAPI)

PR to go with issue https://github.com/swagger-api/swagger-core/issues/3375

This looks nice, thanks a lot! Could you possibly also add a test to the PR?

Added tests now @frantuma :)

Thanks!

Hey @frantuma any idea when the next version of 1.5 will be released with this change?


graphic gliteches

great theme,
but i am experiencing something that seems a graphic glitch in the playlist panel.
i attach two screenshots

That happens if you press CTRL + "some key", it has been already fixed and will be available in the next update.
Thanks for reporting anyways!
-TT

Try top menu Options > Settings > Output device or top menu Shift click on Playback > Device


Add C++ Core Guidelines link on C26405

The rule C26405 references R.3 from the C++ Core Guidelines. This change adds a link to the R.3 section of the C++ Core Guidelines.

@JordanMaples : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Add distro validation

To complete #198 but exiting install if running on anything other than CentOS and Oracle Linux

Tested on OL 7.2 and Centos 7.2 using Vagrant. No apparent issues.


Improved Chinese translation

Added phrases for... a lot of things really. 15 new messages.

@grave-w-grave for working on the translations, please make updates in Transifex; see: http://zulip.readthedocs.io/en/latest/translating.html for details on how that works (basically, translations get synced from Transifex into this repository, so changes you make here would be lost the next time we sync).


spec: Payload nits

Few comments regarding the payload spec.
timestamp
Currently the spec states the timestamp of when the event occurred. This also should mention the format; i'd vote for RFC 3339 format: https://datatracker.ietf.org/doc/html/rfc3339
data
spec states: It can either be passed as part of the data property, or squashed as part of the top-level object.
The drawback of having it squashed at the top level is that it could create collision. Let's say i have user.created event and my payload is a full and we also return the type of user type: foo; we have a collision. We should enforce the producer/consumer data in the data property. Added to this that would make us able to provide a JSON Schema for the standard-webhooks spec.
full payload
I think we also should mention we might want to prefer using thin payloads because it reduces the potential of leeking PIIs over the channels.

Why not just recommend using the structure defined by https://cloudevents.io? They have already spent a lot of time thinking about event structure. I think Standard Webhooks and CloudEvents would work very well together.
They have their own recommendations for WebHooks but yours seem more sophisticated and closer to what's currently out there. Maybe you could work together on some level.

@linuxbasic, there's https://github.com/standard-webhooks/standard-webhooks/issues/36 that > I've been meaning to comment on.
The gist is: we don't currently have any requirements for how to structure the payloads, only recommendations. I think the recommendations are very close to cloudevents, e.g. the type is compatible, timestamp uses the same format for both (but slightly differently named). I think a worthy goal is to have the standard webhooks recommendation be fully compatible so that people can use cloud events and still benefit from tools that follow the recommendations here. Though we definitely need to think about this further.

I'm aware that this spec only makes recommendations regarding the payload, and that's a good decision. I can imagine that it is easier for people to justify the switch of Standard Webhooks if they don't need to rewrite their payload structure.
Like @rikbosch, it came into my mind that the payload recommendation looks a lot like a CloudEvent when I read the spec. My thought was that it would maybe make your life easier by just pointing the readers of your spec at the CloudEvents spec if they do not already have a clear vision for their payload structure.
This way, you and your colleagues don't need to spend brainpower and time discussing how to make the specs compatible. I also agree with @rikbosch that it would be advantageous for this spec to focus on the consumer/producer interactions (like security, and reliability) and treat the payload as a black box as it anyways can be anything.
The CloudEvent folks should probably do the same regarding their WebHook recommendation at some point.

If we switch payload to cloudevent spec then there is lot of benefit we can leverage. Majorly we can now go beyond JSON. We can then package binary payload and use content type to indicate what is the body. Binary payload with compression etc.. will be so much beneficial.


Add Phillip Drake to Contributors list

@pldrake26, I'm quite elated about your PR. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a PR and learned that I merged it?

Hello Roshan!  I felt the tutorial was very easy to follow and gave me no issues.  I have not contributed to any open source projects yet so my first pull request was a good feeling.  When I received the email stating it was merged, the whole process seemed to make a lot of sense to me.  I have been using Github for years for my own projects so I had a basic understanding of creating a repo, staging, commits, pushes, and github pages so this open source tut helped me to grow just a bit further.  Looking forward to contributing to a project soon.

@pldrake26, I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://firstcontributions.herokuapp.com


cargo test --all-targets does not run doc tests

As per title cargo test --all-targets does not run the doc tests on a crate. This is very surprising behaviour. I found this and it looks like running doc tests is done by rustdoc which is apparently not invoked when doing --all-targets.

An attempt to fix this was made in #6671, but there's a bit of a mismatch between cargo test and doc tests that makes the issue complicated, so the PR didn't land.

Maybe it is worth to add some context to this issue.
We ran into this because we use cargo test --all-targets on Travis and usually cargo test locally.
A not-compiling doc test sneaked into a last-minute update of a PR but the build was fine since we use --all-targets on Travis.
Later on, someone complained that we have a broken master because of a non-compiling doc test.
I read some of the discussion in the PR and TBH, the whole --doc is a mode would be SUPER confusing.
As a user, I expect cargo test to test LESS than cargo test --all-targets since the latter has all in the name.
In addition, the documentation (--help) lists doc tests next to all the other targets.

This means the command to run absolutely all tests everywhere is cargo test --workspace, not cargo test --workspace --all-targets, right?

This means the command to run absolutely all tests everywhere is cargo test --workspace, not cargo test --workspace --all-targets, right?

It depends on the structure of your packages, but in general there is currently no single command to "test everything".   cargo test is intended to be the usual command.  If you also want to test benchmarks and examples, you can either mark them with test=true in Cargo.toml, or run two commands (cargo test --all-targets and cargo test --doc).

Oh god, I think we've been not running doc tests on our CI for a couple of years due to this...

Just for some clarification, cargo has a model where there is a distinction between a target and a mode. Doctests are a mode, and that is why --all-targets by itself doesn't run them. I understand that can be confusing, isn't obvious from the documentation, and not the mental model some people have. We have talked in the past about making that more explicit (which in part would solve this issue by offering new switches to do both "run tests" and "run doctests"). I can't find that discussion offhand, but I don't think it was very deep anyway (just acknowledging that the CLI is limited and there were some ideas around a --mode flag). Perhaps that's something the testing team could tackle 😉 .

doctests are a mode, and that is why --all-targets by itself doesn't run them. I understand that can be confusing, isn't obvious from the documentation

Documentation is hard

In Documentation tests, we say "Different from normal test targets", implying it is a target
In Target selection, we talk abut doctests being a target

The --all-targets portion of Target selection also needs an edit. I attempted to do that in #12423, but the current structure of the docs makes it difficult to make a carve-out that adds the additional --all-targets clarification for cargo test only, without applying it to --all-targets for other cargo commands that have nothing to do with doctests.

I'd like to copy over some proposals from ehuss that was buried in a closed PR. Fundamentally this is more a UX issue than performance or technical issue.

Method A: --doc is a mode flag.

--doc will doctest all doctestable targets.
--doc <target flags> will only doctest the given targets.
--doc --all-targets would only doctest all targets.
--all-targets would only rustc test all targets.  (Or, maybe it could do both tests and doctests?)
<target flags> will only rustc test the given targets.

Drawbacks here: I'm not sure if this is clear.  If --all-targets only does rustc tests, then you would need two commands (cargo test --all-targets and cargo test --doc --all-targets) to do everything.  If it does both, then it is a special case that people need to learn about.  You wouldn't be able to say "test and doctest all examples", unless all plurality flags like --examples are special, in which case I think it would be confusing if --example foo didn't run doctests (but that seems undesirable to me).
Method B: --mode=... can specify the types of tests that are run.

--mode=test,doctest <target flags> will test and doctest the given targets.
No --mode means rustc test only.

Drawbacks is that this adds another flag, which is very undesirable.
Method C: --doc could take targets as a parameter

--doc --lib doctests all doctestable targets, and rustc tests just the library.
--doc=lib doctests just the lib.
--doc=lib,example=foo,bins  doctests lib, example foo, and all bins.
--doc=all-targets --all-targets does everything

Drawbacks is that I think the first case is confusing, and the last one is awkward.

Yeah it would be great if there was a single command to run all tests, doctests, everything.
having a unified command is a blocker for re-attempting #8437

Just for some clarification, cargo has a model where there is a distinction between a target and a mode. Doctests are a mode, and that is why --all-targets by itself doesn't run them. I understand that can be confusing, isn't obvious from the documentation, and not the mental model some people have. We have talked in the past about making that more explicit (which in part would solve this issue by offering new switches to do both "run tests" and "run doctests"). I can't find that discussion offhand, but I don't think it was very deep anyway (just acknowledging that the CLI is limited and there were some ideas around a --mode flag). Perhaps that's something the testing team could tackle 😉 .

I don't know anything about the internals of cargo and I've been using Rust for close to 6 years now in a full-time setting. This is the first time I am hearing about cargo having a mode (other than the "release mode" toggled by --release).
Can we just remove the --doc flag and always include doc tests in every target that is selected, i.e. --lib, --tests, --examples etc. The usecase of only running doc tests could be served by a new flag of cargo doc: cargo doc --tests although I'd probably play it conservative and not add that one to begin with. It seems odd wanting to run only the doc tests. If doc tests are just more tests that get compiled into the binary, the could be selected via the regular filtering of test names. Perhaps they should all be under a dedicated doc module? Something like cargo test mycrate::doc::my_function_name_that_has_doc_test.

Can we just remove the --doc flag and always include doc tests in every target that is selected

doctests are not unit tests, they are integration tests. In other words, they require a separate rustc process to be spawned for each snippet. On top of that, you have the rustdoc process (which isn't that neccessary, one could move the logic to extract the snippets to a place shared by rustc and rustdoc).

In today's @rust-lang/cargo meeting, we agreed to try the experiment of adding an --all-targets-including-doc unstable option, initially to cargo test and then to other commands like cargo build and cargo check. We don't yet know what we should call it, but we can experiment with implementation of it.

Also, when we do build, check, and fix (and suggest for clippy to do similar), we might want to add --doc flags to them (#6424).
As for naming, one idea is to explore disambiguating the term "target" in cargo.  If we rename "build target", then the --all-<something> could just have the new meaning.
We lean towards a new flag because people likely have broken doctests (as evidenced by this thread).  While they would want to discover and fix them, they likely want to do it on their own timetable and not be forced to by cargo.

Note that in a future edition we could potentially make --all-targets default to this, which would make this an interim option for current editions.

Hmm, I wonder if we can have a project-level switch (maybe in the .cargo/config) for this? cargo c --all-features --all-targets is already pretty verbose and I'm not sure making it more onerous to do the right thing is the best way forward. So for projects that are aware of this and want to eagerly fix the doctests breakage, it would be great if we can opt-in to making --all-targets do (arguably) the right thing without waiting until 2027.

I think we're leaning towards renaming "build target" and having the new name for --all-targets include doctests.  We would then not need to wait for a new edition.

Just note that there are designs needing to figure out, for the interaction between doctesting everything and a subset of doctest-able lib/example/bench/test/bin. See https://github.com/rust-lang/cargo/issues/6669#issuecomment-1850761204

Hmm, I wonder if we can have a project-level switch (maybe in the .cargo/config) for this?

You could maybe solve that with an alias that "does the right thing" whatever that means for you?

I think we're leaning towards renaming "build target" and having the new name for --all-targets include doctests. We would then not need to wait for a new edition.

@epage The idea would still be to default to the "--all-targets includes docs" in edition 2024, is that right? The new edition is just a few months away, so I would be happy just waiting for that instead of having an --all-targets-with-doc.

It is too late to introduce 2024 Edition changes. If a solution needs an Edition, it'd be 2027.

Ah, well, it that case it makes sense to have a new flag for "all targets and docs" 😄 .


Investigate issues with M1 on Mac

I've heard one report that Mac + M1 fails with an error like so:
> Configure project :
Kotlin Multiplatform Projects are an Alpha feature. See: https://kotlinlang.org/docs/reference/evolution/components-stability.html. To hide this message, add 'kotlin.mpp.stability.nowarn=true' to the Gradle properties.

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':kotlinNodeJsSetup'.
> Could not resolve all files for configuration ':detachedConfiguration1'.
   > Could not find org.nodejs:node:14.17.0.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/org/nodejs/node/14.17.0/node-14.17.0.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/nodejs/node/14.17.0/node-14.17.0.pom
       - https://dl.google.com/dl/android/maven2/org/nodejs/node/14.17.0/node-14.17.0.pom
       - https://us-central1-maven.pkg.dev/varabyte-repos/public/org/nodejs/node/14.17.0/node-14.17.0.pom
       - https://nodejs.org/dist/v14.17.0/node-v14.17.0-darwin-arm64.tar.gz
     Required by:
         project :

* Try:
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Exception is:
org.gradle.api.internal.tasks.TaskDependencyResolveException: Could not determine the dependencies of task ':kotlinNodeJsSetup'.
	at org.gradle.api.internal.tasks.CachingTaskDependencyResolveContext.getDependencies(CachingTaskDependencyResolveContext.java:71)
	at org.gradle.execution.plan.TaskDependencyResolver.resolveDependenciesFor(TaskDependencyResolver.java:49)
	at org.gradle.execution.plan.LocalTaskNode.getDependencies(LocalTaskNode.java:168)
	at org.gradle.execution.plan.LocalTaskNode.resolveDependencies(LocalTaskNode.java:133)
	at org.gradle.execution.plan.DefaultExecutionPlan.doAddNodes(DefaultExecutionPlan.java:202)
...

Caused by: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':detachedConfiguration1'.
	at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.rethrowFailure(DefaultConfiguration.java:1503)
	at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.access$3700(DefaultConfiguration.java:159)
	at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$DefaultResolutionHost.rethrowFailure(DefaultConfiguration.java:2139)
	at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$ConfigurationFileCollection.visitContents(DefaultConfiguration.java:1475)
...

Caused by: org.gradle.internal.resolve.ModuleVersionNotFoundException: Could not find org.nodejs:node:14.17.0.
Searched in the following locations:
  - https://repo.maven.apache.org/maven2/org/nodejs/node/14.17.0/node-14.17.0.pom
  - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/nodejs/node/14.17.0/node-14.17.0.pom
  - https://dl.google.com/dl/android/maven2/org/nodejs/node/14.17.0/node-14.17.0.pom
  - https://us-central1-maven.pkg.dev/varabyte-repos/public/org/nodejs/node/14.17.0/node-14.17.0.pom
  - https://nodejs.org/dist/v14.17.0/node-v14.17.0-darwin-arm64.tar.gz
Required by:
    project :

* Get more help at https://help.gradle.org
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

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

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

Exiting continuous build as no executed tasks declared file system inputs.

Starting a Kobweb server (development).

Full pastebin attached: Kobweb startup failure.txt

Seems like this will get fixed (probably) when I can upgrade Kotlin to 1.6.20
A workaround for now is to add the following to your app's build.gradle.kts file:
rootProject.plugins.withType<org.jetbrains.kotlin.gradle.targets.js.nodejs.NodeJsRootPlugin> {
    rootProject.the<org.jetbrains.kotlin.gradle.targets.js.nodejs.NodeJsRootExtension>().nodeVersion = "16.0.0"
}

See also: https://youtrack.jetbrains.com/issue/KT-49109

Old version of compose compiler corresponds to old NodeJs with is not available for arm64

Old version of compose compiler corresponds to old NodeJs with is not available for arm64

Yeah it's not great. I'm still waiting on web compose to update so we can use newer versions. Did you try the workaround in https://github.com/varabyte/kobweb/issues/140#issuecomment-1073294231 ?

Note that Kobweb is now updated so latest (0.10.0+) targets later versions of Kotlin and Compose.
I'm going to mark this as closed, because it should have been fixed long ago; however, if anyone is still seeing this with latest, let me know!


Add Postal Code to the Credit Card Check Out Sample

I would like to have a sample credit card check out with a postal code field either by creating a new sample or adding the postal code to the existing one.
This is a case that we want to handle, I can create a PR if it's ok for you.

Indeed


build error

Hi,
I just can't build by having such errors:
:copyCoberturaDatafile SKIPPED
:compileTestJava
Note: /home/stuser/stormprj/storm-graphite/src/test/java/com/verisign/storm/metrics/GraphiteMetricsConsumerTest.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:processTestResources UP-TO-DATE
:testClasses
:test

com.verisign.storm.metrics.graphite.GraphiteAdapterTest.connectClientToGraphiteServer FAILED
    java.net.BindException at GraphiteAdapterTest.java:53

39 tests completed, 1 failed, 38 skipped
:test FAILED
:generateCoberturaReport SKIPPED
:performCoverageCheck SKIPPED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':test'.
> There were failing tests. See the report at: file:///home/stuser/stormprj/storm-graphite/build/reports/tests/index.html

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 13.698 secs

any ideas?
AL

Btw, my os is ubuntu, seems I am having trouble to get storm-graphite working my box.

@alecinvan it may be that port 2003 is being used by another process. Could you run netstat -ln and ensure that port isn't being bound during the tests?

Awesome, carbon-cache take 2003, I rebuild it, and worked. Next question is, do I have to package it to RPM? My OS is ubuntu, I assume all of your release are in centos, that are not working perfectly on my boxes. Do you have an ubuntu version, and not just tool, and other tools you team released.
thanks

I'll take a look at adding .DEB packaging support.
#5

Thanks a lot.

@alecinvan If I understand correctly your question has been answered, and we track the new feature request for .deb packages in a separate ticket.  Hence I'm closing this ticket.


Inspector : .env texture tool

It seems that we're currently not able to generate .env textures. Is it a bug or a feature not yet re-implemented in the new inspector?
I tried using BJS v3 + inspector from the /dist/ folder, but I don't see the env tool in it.

It should be in the tools tab when you are in the sandbox for instance
I can see it in my computer

yep the button is in place, but clicking on the button do nothing except this console error The cube texture is invalid (not prefiltered).... and I don't know where to upload this envTexture.
img

Ok let's ask @sebavan  :)

It is normal it does not export in your page cause the env in your page is already a .env (you can see the error in the console).
To generate the env open the sandbox drag drop a glb file (not from the url shortcut), drag drop a dds preprocess in lys for instance and then use the export button.
I ll add an error message to the inspector.

yep I'll do that in the next few days


CMake Error with XSD_LIBRARY when manually compiling

Hi, I'm experiencing a similar issue to #208 , but unlike the reporter, I actually have xsd installed on my system and am still receiving the following output:
$ xsd version
CodeSynthesis XSD XML Schema to C++ compiler 4.0.0
Copyright (c) 2005-2014 Code Synthesis Tools CC

$ cmake -DCMAKE_BUILD_TYPE=Debug ..
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Boost version: 1.58.0
-- Found the following Boost libraries:
--   chrono
--   date_time
--   filesystem
--   iostreams
--   program_options
--   python
--   regex
--   system
--   thread
--   atomic
-- Found the following C# Mono versions: 4.6.2
-- Found CSharp: Mono
-- Found Doxygen: /usr/bin/doxygen (found version "1.8.11")
-- Found Git: /usr/bin/git (found version "2.7.4")
-- Found Java: /usr/lib/jvm/java-8-openjdk-amd64/bin/java (found version "<IP_ADDRESS>") found components:  Runtime Development
-- Found JNI: /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libjawt.so
-- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.12", minimum required is "2.7")
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found suitable version "2.7.12", minimum required is "2.7")
-- Found SWIG: /usr/bin/swig3.0 (found version "3.0.8")
-- Found Luabind: /usr/local/lib/libluabind.a
-- Found Torch7 in /home/robert/torch/install
-- Using Mono compiler version 4.6.2
-- Found the following C# Mono versions: 4.6.2
-- Using Mono compiler version 4.6.2
-- Found the following C# Mono versions: 4.6.2
-- Using Mono compiler version 4.6.2
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
XSD_LIBRARY (ADVANCED)
    linked by target "Malmo" in directory /home/robert/repos/MalmoPlatform/Malmo/src

Using Ubuntu 16.04
Any advice to push me in the right direction would be great, I feel stuck at this point.

Can I ask how you installed CodeSynthesis? I realise our build instructions don't have a special section for Ubuntu 16.04 (https://github.com/Microsoft/malmo/blob/master/doc/build_linux.md) - so did you follow the instructions for Ubuntu 15 (and install using sudo apt-get install xsdcxx ), or did you follow the Ubuntu 14 instructions (with the wget and sudo dpkg -i --force-all xsd_4.0.0-1_amd64.deb)?
The extra instructions for Ubuntu 14/Debian 7 are needed because the packaged version of xsd is too old - we require version 4.0. Installing version 4 this way results in the binary being called "xsd". On Ubuntu 15 and 16, Debian 8 etc. version 4.0 comes as standard, and is called "xsdcxx". CMake decides which to look for ("xsd" or "xsdcxx") by checking which OS it's running on.
So my best guess at what's happening is that CMake is looking for xsdcxx, whereas your version is installed as xsd. (To confirm this suspicion, if I type xsd version in my copy of Ubuntu 16, I get Invalid parameters - this is the Mono xsd. On the other hand, typing xsdcxx version gives me what you posted above.)
If this is so, a simple sudo apt-get install xsdcxx should fix things.

I removed xsd because attempting to install xsdcxx complained about directory conflicts, then installed xsdcxx successfully.
I had to backtrack and reinstall a couple other packages, and it finally compiled!
@DaveyBiggers It looks like this happened because I was originally following the tutorial to use the precompiled version, which doesn't have you install xsdcxx, and when I switched over to trying to build it manually, it created some confusion since I already had (the wrong) xsd on my system.
Thanks for the help, now it's time to have some fun!

Great, thanks for the update. I'm glad you got it working in the end. Enjoy!


Feature request: clean the code and make a fastapi just like OpenAI's tts API

Hi, as the LLM got popular, we really want the text can have a voice,
EmotiVoice get the best quality and varianty on Chinese voice tts, there is no such a model can make this better.
As a result, it could be very fun and nice for your team to make it further, integrate it with LLMs. By just make this code more stable, ready for production, and make server as a TTS api just like OpenAI's.

Thank you for your encouragement, and we are currently working on it. Please bear with us for a little while longer!


Revert "Merge pull request #25863: Revert "Adding support for DLQ for…

… ZetaSQL (#25426)""
This reverts commit b2222b5e5d04ca4c0dc1f5860b34629cc54b1114, reversing changes made to eac926878c289cdf917e1eedb7aab1a1c2a2055c.
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

r: @apilloud this makes the DLQ behavior optional - only in case an error consumer is passed. Compliance tests checked in internal cl 517508732

thanks Andrew <3


should we further mitigate threats of identifiers in local storage because some mechanisms won't clear all local storage?

In this questionnaire and in the mitigating browser fingerprinting guidance, we note that local storage mechanisms should be identified for simultaneous clearing to avoid evercookies or other persistent state.
@pes10k noted a concern about unique identifiers, even if cleared with other local storage, because some user mitigation mechanisms (like privacy-focused browser extensions or automatic expiration of cookies) might not clear them. This issue is to track that question and see if we should update guidance that simultaneous clearing of local storage isn't enough. Pete, if you can add any more details on the threat/use cases, that would be helpful.

I note that we do have a positive example in the questionnaire about the Gamepad API, which uses an incrementing integer for its index of devices, rather than a unique identifier: https://w3ctag.github.io/security-questionnaire/#temporary-id
And the section on persistent state also discusses the mitigation of clearing all local storage simultaneously:
https://w3ctag.github.io/security-questionnaire/#persistent-origin-specific-state

At least specification-wise this is being addressed by rewriting all storage APIs to be on top of storage buckets, as defined by https://storage.spec.whatwg.org/.

@annevk im not sure I understand how the buckets definition addresses the concern.  A privacy intervention like "cap all JS cookies to N days lifetime" wouldn't seem to trigger that definition, since it seems like the trigger there is a browser / affect that wants to clear the entire bucket.
The broader concern is that there are privacy mitigations being pursued by vendors that have the goal of reducing how much "stuff" gets stored (e.g. life timing keys / cookies / fields, "garbage collecting" rarely used items, etc) , specifically so that users never need to take the step of "clear all storage".
It would be good to make sure other specs don't undo the intended benefit of these interventions by assuming "any level of identifier is fine, as long as its reset when the relevant storage bucket is cleared"

I don't see how such an intervention is meaningful long term if it doesn't also clear storage.

It does clear storage, it just doesn't clear all storage at the same time.  Safari's ITP, for example, does this, along with Brave, and several extensions.
Its mostly effective for 3p scripts who are riding on the 1p cookie jar

I wouldn't call that clearing storage though and it seems circumventable therefore.

It may be circumventable at some margin (as is the case with nearly every privacy protection on the platform), but its also very frequently useful, and so it would be very good to not have standards making the protection more harmful, by introducing unneeded identifiers that will persist across the reduced cookie lifetimes.  That the issue (globally unique device identifiers in the getUserMedia spec) that started the conversation and led to @npdoty filing this issue.
Another way of putting it is just privacy defense in layers; always prefer a more privacy preserving option, all other things being equal.

It only works until it's worked around en masse. And meanwhile it makes the situation for web developers rather involved as there is no clear set of principles at work. (Nor is any of it standardized.)

@annevk I don't think we need to argue about whether its an effective protection or not; happy to just note that some browser are using the approach to try and improve privacy.
"Reducing the entropy of device identifiers" as just an application of the general principal of "always prefer the more privacy preserving option, when the privacy preserving is >= useful to users".
Reducing the identifiability of device id's from being globally unique to per eTLD+1 (and dual keyed eTLD+1 on dual keyed platforms) seems like it'd neatly fit that description / principal.

Given the ongoing work in the Storage Standard, it should (eventually) be clear, at least spec-wise, that "clear all website data" buttons should do what it says on the tin. That said, I do think it would be useful for our Design Principles document to say something like "when adding new storage mechanisms, make sure you hook it up right so that 'clear all website data' does the right thing". Moving this issue to that repo to track that work.


Location Config

just would be cool that you can choose where the emote combo appears, for example : &Location=
1 (Top left)
2 (Top Right)
3 (Botton Left) as default
4 (Botton Right)
5(center for the weird ones)

Great suggestion! Could you make a PR with these changes for me to review?

Sorry, can you explain me what a PR means? then i can work on it :D


fix: package.json & package-lock.json to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:

https://snyk.io/vuln/SNYK-JS-ANSIREGEX-1583908

This was merged accidentally and I've since reverted and built a new PR. See #1969


The detection score you provide is not normalized?

I find that the detection score you use is not normalized (not in the range of [0, 1]). Which layer or where did you extract those scores from? Are those score the logits before softmax?
Car -1 -1 -8.0728 299.5648 166.8018 457.8472 299.3745 2.0278 1.8372 4.4899 -4.5203 1.9349 13.4348 -8.3923 6.8229 Cyclist -1 -1 -8.3277 743.3280 157.8975 945.0159 374.0000 1.7928 0.7382 1.7908 1.6935 1.6931 5.7445 -8.0567 6.3583 Pedestrian -1 -1 -8.9000 1086.0386 169.0511 1223.0736 325.3153 1.7003 0.7000 1.0835 6.3164 1.6586 8.4887 -8.2776 3.9818 Car -1 -1 -2.0002 0.0000 198.3879 22.4742 238.5690 1.4643 1.6507 3.9074 -26.4072 2.5741 29.8174 -2.7207 -0.4804 Car -1 -1 -7.6264 284.9278 190.2203 347.9479 230.2715 1.5499 1.6856 4.1383 -12.9598 2.3717 31.9821 -8.0090 -0.7022 Car -1 -1 -4.6372 136.7996 189.1622 176.2292 219.5773 1.5594 1.6092 4.0767 -26.0653 2.5465 41.5085 -5.1953 -1.3563 Car -1 -1 -2.5441 0.0000 195.0718 83.9934 227.2724 1.4837 1.6807 3.8615 -28.5618 2.6095 35.5869 -3.2169 -2.0098 Car -1 -1 -4.4626 347.0251 177.7920 392.8701 208.4988 1.6766 1.6258 3.8540 -13.9505 1.9773 42.0110 -4.7817 -2.1874

using sigmoid in trajectory 252,254

The detection score is not normalized before put into the tracker. For the OpenPCDet, you can set the OUTPUT_RAW_SCORE=Ture in the detector config file to obtain the detection results.

Hi, does it mean that the tracker designed only for unnormalized scores? I see that the prediction scores are initialized as 1 for example.


TFS 2017 based process template migration to AzureDevOps Services

Does the migration utility supports migrating process template customised in TFS 2017 environment to AzureDevOps Services? Please confirm

Hi @ktdixit, did you figure this out? The process migrator only supports migration of inherited processes, which was introduced with TFS 2019. For xml based collections you can use the download/upload process template features on the server.

@MOlausson Thanks. So, I have to download the process template from TFS 2017 and upload in TFS 2019... Then use the process migrator from TFS 2019 to AzureDevOps Services.. Correct?

@ktdixit ah, thanks for the additional context, now I understand your scenario. In this case you don't need to use the process migrator at all, instead check out https://learn.microsoft.com/en-us/azure/devops/organizations/settings/work/import-process/import-process?view=azure-devops#import-a-process-from-an-on-premises-azure-devops.

@MOlausson unfortunately our AzureDevOps Services organisation doesn’t support “Hosted XML process model”. So, we don’t have an option to “Import Process”.
Any other recommendations?


Open Webui 0.3.4 timesout with long Ollama responses

Bug Report
openwebui fails with a timeout if ollama is sending back a long running ollama chat
Description
Bug Summary:
openwebui fails with a timeout if ollama is sending back a long running ollama chat
Steps to Reproduce:
Run a chat with a response that takes more than a minute to respond
Expected Behavior:
It should continue to respond
Actual Behavior:
After a few minutes it fails with
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 756, in call
open-webui  |     await self.middleware_stack(scope, receive, send)
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 776, in app
open-webui  |     await route.handle(scope, receive, send)
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 485, in handle
open-webui  |     await self.app(scope, receive, send)
open-webui  |   File "/usr/local/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in call
open-webui  |     await super().call(scope, receive, send)
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/applications.py", line 123, in call
open-webui  |     await self.middleware_stack(scope, receive, send)
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 186, in call
open-webui  |     raise exc
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 164, in call
open-webui  |     await self.app(scope, receive, _send)
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/middleware/base.py", line 189, in call
open-webui  |     with collapse_excgroups():
open-webui  |   File "/usr/local/lib/python3.11/contextlib.py", line 158, in exit
open-webui  |     self.gen.throw(typ, value, traceback)
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/_utils.py", line 93, in collapse_excgroups
open-webui  |     raise exc
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/responses.py", line 261, in wrap
open-webui  |     await func()
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/responses.py", line 250, in stream_response
open-webui  |     async for chunk in self.body_iterator:
open-webui  |   File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 50, in anext
open-webui  |     rv = await self.read_func()
open-webui  |          ^^^^^^^^^^^^^^^^^^^^^^
open-webui  |   File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 317, in readline
open-webui  |     return await self.readuntil()
open-webui  |            ^^^^^^^^^^^^^^^^^^^^^^
open-webui  |   File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 351, in readuntil
open-webui  |     await self._wait("readuntil")
open-webui  |   File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 311, in _wait
open-webui  |     with self._timer:
open-webui  |   File "/usr/local/lib/python3.11/site-packages/aiohttp/helpers.py", line 735, in exit
open-webui  |     raise asyncio.TimeoutError from None
open-webui  | TimeoutError
Environment

Open WebUI Version: [e.g., 0.1.120] 0.3.4

Operating System: linux

Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0]

Reproduction Details
Confirmation:

[ X] I have read and followed all the instructions provided in the README.md.
[ X] I am on the latest version of both Open WebUI and Ollama.
[ X] I have included the browser console logs.
[ X] I have included the Docker container logs.

Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 485, in handle
open-webui  |     await self.app(scope, receive, send)
open-webui  |   File "/usr/local/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in call
open-webui  |     await super().call(scope, receive, send)
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/applications.py", line 123, in call
open-webui  |     await self.middleware_stack(scope, receive, send)
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 186, in call
open-webui  |     raise exc
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 164, in call
open-webui  |     await self.app(scope, receive, _send)
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/middleware/base.py", line 189, in call
open-webui  |     with collapse_excgroups():
open-webui  |   File "/usr/local/lib/python3.11/contextlib.py", line 158, in exit
open-webui  |     self.gen.throw(typ, value, traceback)
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/_utils.py", line 93, in collapse_excgroups
open-webui  |     raise exc
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/responses.py", line 261, in wrap
open-webui  |     await func()
open-webui  |   File "/usr/local/lib/python3.11/site-packages/starlette/responses.py", line 250, in stream_response
open-webui  |     async for chunk in self.body_iterator:
open-webui  |   File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 50, in anext
open-webui  |     rv = await self.read_func()
open-webui  |          ^^^^^^^^^^^^^^^^^^^^^^
open-webui  |   File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 317, in readline
open-webui  |     return await self.readuntil()
open-webui  |            ^^^^^^^^^^^^^^^^^^^^^^
open-webui  |   File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 351, in readuntil
open-webui  |     await self._wait("readuntil")
open-webui  |   File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 311, in _wait
open-webui  |     with self._timer:
open-webui  |   File "/usr/local/lib/python3.11/site-packages/aiohttp/helpers.py", line 735, in exit
open-webui  |     raise asyncio.TimeoutError from None
open-webui  | TimeoutError
Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
docker compose
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

This doesn't seem to be a problem in version v0.2.3

This seems to have been fixed in dfa2cf9e6d784ac5b1458911ef8364258dc54cba

Related - #3107

Related - #3135
This issue should also be fixed viahttps://github.com/open-webui/open-webui/commit/dfa2cf9e6d784ac5b1458911ef8364258dc54cba as well.

Well, not fixed per se, but it can then be adjustable via environment variable.
When I submitted the PR I changed the default to 15 minutes, but I see it's been set back to 5 minutes as default.


Is it possible for nested components ?

Can you provide an example of how you want to use it in a nested scenario?

Closing because of inactivity


[ST] Execution error

Describe the bug
A txn (0.82 WETH) going from Arbitrum to Mode got an execution error. Reconcile already happened. It's asking for a bump (idk why xD) but I can't click the button

https://connextscan.io/tx/0xbf9684b0aab0ba40be9193df855965509350e0aa8c74d5bc9cb63c97b4a77da4
Link to ticket in discord
https://discord.com/channels/454734546869551114/1219576483379417089
@oncall

Another case, BNB to Polygon
https://connextscan.io/tx/0x2383cdd28423134bded6154da4b31db87e17584925a8f073f1eb2cee57f08697
https://discord.com/channels/454734546869551114/1219747497778352148/1219748073761276028

Another case ezETH from Mode to Arbitrum
https://connextscan.io/tx/0x028858d777af75d74cd98a86473b805e7d466e3cad5ea57931241f2779b133c3
https://discord.com/channels/454734546869551114/1219773620159643698

The last 2 cases were fixed and funds arrived, but the first one is stuck since 31 hours. Any update on this?

This transaction says execution error
https://connextscan.io/tx/0x34f65b85eeb0813d2c99dc1c66910f9c18e13b7ed3052092e4b73effb5645d15
Ticket 311 on Intercom

Another tx: https://connextscan.io/tx/0x1d359986bcb901f0d630ad4909006644413501512eddc95f819901526c48cd77
Ticket 314 on Intercom

The last 2 also completed. The first transaction in the thread still remains in ExecutionError after 33 hours

https://connextscan.io/tx/0xbf9684b0aab0ba40be9193df855965509350e0aa8c74d5bc9cb63c97b4a77da4
completed as well after resetting the error status.
I think this and #5892 are related to error status being stale and UI prompts based on that.
@preethamr how are the error statuses on transfers set?

https://github.com/connext/monorepo/pull/5900

#5656?


Bootstrap optional.

One thing that would help a lot of designers is if you made bootstrap optional, similar to how you can change if you want to use Identity or not.

We include Bootstrap in some of our project templates, but it isn't required. You can, for example, create an Empty project and add whatever you want.


Update readme.md

add nodaljs and strapi.

Please read and adhere to the contributing guidelines.

Closing for lack of response.


Fix/cbl 583

Minimal changes, taken from #180 , for Mercury.

Yeah.  As you pointed out, the exception trick doesn't work.  For mercury, instead of trying to get it to work, I'm just going to leave it out.


[Swap Fee Logic] Make swap fee display dynamic

AllFees.fetch() no longer takes in an outputAmount value. So everytime we goto the recieve page, we can call this function and update the fees.
Boltz-fee comes back as a percentage, so as user types in an amount, we can dynamically calculate the fees and display it before the invoice is created.


Fix: navigate to invite list by arrow keys

Details

This PR allows the navigation throw the members list on workspace invite member page
Fixed Issues

$ https://github.com/Expensify/App/issues/41906
PROPOSAL: https://github.com/Expensify/App/issues/41906#issuecomment-2103257894
Tests

Create workspace
Go to Members> Invite member
In the invite members use the keyboard arrow keys
Go back to Members page
Go to Invite member
Try to use the keyboard arrow keys
Verify that you can

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Create workspace
Go to Members> Invite member
In the invite members use the keyboard arrow keys
Go back to Members page
Go to Invite member
Try to use the keyboard arrow keys
Verify that you can

[x] Verify that no errors appear in the JS console

PR Author Checklist

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

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

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

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

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

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

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

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

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

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

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

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

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

NA

Android: mWeb Chrome

NA

iOS: Native

NA

iOS: mWeb Safari

NA

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/12425932/0915efc2-9022-4d94-bb2f-ea7e41c4d29e

MacOS: Desktop

https://github.com/Expensify/App/assets/12425932/08605b38-5506-4569-a41a-d09cd2d5906b

Bump @abdulrahuman5196 for review

Hi sorry for the delay will review now

Checking now

Reviewer Checklist

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

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

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

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

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

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

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

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

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

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

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

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

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/46707890/3b71f101-16c6-4c8e-86f6-395910e6a484

Android: mWeb Chrome

https://github.com/Expensify/App/assets/46707890/45ae142b-c59d-4087-9808-82d2033418cf

iOS: Native

https://github.com/Expensify/App/assets/46707890/640e643d-d3bd-4bd0-a12e-78d3575fbd0f

iOS: mWeb Safari

https://github.com/Expensify/App/assets/46707890/a54f5e71-aac2-4707-a777-e9034363259c

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/46707890/2ea9821a-4ad8-48b7-8c56-dc42bf106fc1

MacOS: Desktop

https://github.com/Expensify/App/assets/46707890/eb5c295d-e0b2-454e-bea6-3ac626e4b67f

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

🚀 Deployed to production by https://github.com/Julesssss in version: 1.4.79-11 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Fix provisioning failing due to partial downloads.

'$COMMIT' was originally printed in '$COMMIT_FILE_PATH' before all
respective files where downloaded, meaning that this step
wouldn't be repeated if one download failed. This commit prints
'$COMMIT' only after all downloads were successful.

Automated message from Dropbox CLA bot
@derAnfaenger, it looks like you've already signed the Dropbox CLA. Thanks!

Merged, after s/where/were/ in the commit message, thanks @derAnfaenger!

@HarshitOnGitHub FYI, you may be interested in the resolution of this bug.


Automatic PR from RestAPI-PR441

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/441

Coverage increased (+0.001%) to 58.642% when pulling 476929db9c0633cf9efee363c5a3978b648f5305 on AutorestCI:RestAPI-PR441 into db28cf3c3b6260aafc6418794b917b605f7e3174 on Azure:dev.


Failed to link source -> source_process

Hi,
We tried to install the openwebrtc in VM.
It has webcam connect to it.
When executing the application, we are facing some errors like this.
0:04:21.279674741  3541       0xaa1e30 ERROR    owrlocalmediasource owr_local_media_source.c:703:owr_local_media_source_request_source: Failed to link source -> source_process
==== Error message start ====
Error in element video-source.
Error: Internal data flow error.
Debugging info: gstbasesrc.c(2943): gst_base_src_loop (): /GstPipeline:local-video-capture-source-bin-0/GstV4l2Src:video-source:
streaming task paused, reason not-linked (-1)
==== Error message stop ====
==== Warning message start ====
Warning in element autoaudiosrc0-actual-src-puls.
Warning: Can't record audio fast enough
Debugging info: gstaudiobasesrc.c(866): gst_audio_base_src_create (): /GstPipeline:transport-agent-1/GstBin:bin0/GstAutoAudioSrc:autoaudiosrc0/GstPulseSrc:autoaudiosrc0-actual-src-puls:
Dropped 7680 samples. This is most likely because downstream can't keep up and is consuming samples too slowly.
==== Warning message stop ====
Thanks.

Did you resolve this? If not, can you set an environment variable GST_DEBUG=2,GST_CAPS:6,*v4l2src*:6 and run your program redirecting the output into a file then upload the file somewhere so we can take a look.

Still having this problem?

I am pretty sure that @suganthikarthick has got past this issue as I know testing has been done with video. Closing but we can reopen if it's still an issue.

Hi Superdump,
We tried to install in VM but we faced some issue. May the error can be resolved but we didnt try in VM after that. And so we installed in native linux machine and used in that.
Thank you.


Right to left Option

Add the option for the slider to go right to left
Useful for curtains

I also would like to see this implemented as my vertical blinds open from right to left.  I am using invert:true for now to get the correct action in the slider but the percentage open is wrong.  My device reports 0% when fully open and 100% fully closed so at 70% open the card shows 30%.


error running helm repo add incubator http://storage.googleapis.com/kubernetes-charts-incubator

In reference
https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/blob/master/docs/volcano-integration.md
Trying to install Volcano I am getting this error
helm repo add incubator http://storage.googleapis.com/kubernetes-charts-incubator
Error: looks like "http://storage.googleapis.com/kubernetes-charts-incubator" is not a valid chart repository or cannot be reached: failed to fetch http://storage.googleapis.com/kubernetes-charts-incubator/index.yaml : 404 Not Found
Please advise.

@michTalebzadeh I will update it today.

Great many thanks
view my Linkedin profile
https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/
Disclaimer: Use it at your own risk. Any and all responsibility for any
loss, damage or destruction of data or any other property which may arise
from relying on this email's technical content is explicitly disclaimed.
The author will in no case be liable for any monetary damages arising from
such loss, damage or destruction.
On Thu, 1 Jul 2021 at 09:21, william-wang @.***> wrote:

@michTalebzadeh https://github.com/michTalebzadeh I will update it
today.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/issues/1289#issuecomment-872035135,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEXMDKDXKMGPXWKXAEIHGP3TVQQR3ANCNFSM47TT6FQQ
.

Thanks so far looks promising
Install Kubernetes Operator for Apache Spark with Volcano enabled
$ helm repo add spark-operator
https://googlecloudplatform.github.io/spark-on-k8s-operator
$ helm install my-release spark-operator/spark-operator --namespace
spark-operator --set enableBatchScheduler=true --set enableWebhook=true
kubectl get pod -n spark-operator
NAME                                         READY   STATUS    RESTARTS
AGE
my-release-spark-operator-5c64448d84-m2gth   1/1     Running   0
5m56s
view my Linkedin profile
https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/
Disclaimer: Use it at your own risk. Any and all responsibility for any
loss, damage or destruction of data or any other property which may arise
from relying on this email's technical content is explicitly disclaimed.
The author will in no case be liable for any monetary damages arising from
such loss, damage or destruction.
On Tue, 6 Jul 2021 at 23:04, Yinan Li @.***> wrote:

Closed #1289
https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/issues/1289
via #1291
https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/pull/1291.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/issues/1289#event-4985713723,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEXMDKDYJBGB4ZW4LJ46S5TTWN4VHANCNFSM47TT6FQQ
.

Hi,
I can see there is a YAML construction in the volcano link as below
Run Spark Application with Volcano scheduler
Now, we can run a updated version of spark application (with
batchScheduler configured),
for instance:
apiVersion: "sparkoperator.k8s.io/v1beta2"kind: SparkApplicationmetadata:
name: spark-pi
namespace: defaultspec:
type: Scala
mode: cluster
image: "gcr.io/spark-operator/spark:v3.1.1"
imagePullPolicy: Always
mainClass: org.apache.spark.examples.SparkPi
mainApplicationFile:
"local:///opt/spark/examples/jars/spark-examples_2.12-v3.1.1.jar"
sparkVersion: "3.1.1"
batchScheduler: "volcano"   #Note: the batch scheduler name must be
specified with volcano
restartPolicy:
type: Never
volumes:
- name: "test-volume"
hostPath:
path: "/tmp"
type: Directory
driver:
cores: 1
coreLimit: "1200m"
memory: "512m"
labels:
version: 3.1.1
serviceAccount: spark
volumeMounts:
- name: "test-volume"
mountPath: "/tmp"
executor:
cores: 1
instances: 1
memory: "512m"
labels:
version: 3.1.1
volumeMounts:
- name: "test-volume"
mountPath: "/tmp"
What is not clear to me how you submit such job please, specifically
referencing batchScheduler below
spark-submit
--master k8s://$K8S_SERVER
--deploy-mode cluster
--name spark-pi
--batchScheduler volcano \  ## is this correct?
--class org.apache.spark.examples.SparkPi
--conf spark.executor.instances=3
--conf spark.kubernetes.namespace=spark
--conf spark.kubernetes.driver.pod.name=spark-master
--conf spark.kubernetes.container.image="gcr.io/spark-operator/spark:v3.1.1"

--conf
spark.kubernetes.authenticate.driver.serviceAccountName=spark-serviceaccount

local:///opt/spark/examples/jars/jars/spark-examples_2.12-v3.1.1.jar
Can you please update the document with the example of spark-submit with
volcano?
Thanks
view my Linkedin profile
https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/
Disclaimer: Use it at your own risk. Any and all responsibility for any
loss, damage or destruction of data or any other property which may arise
from relying on this email's technical content is explicitly disclaimed.
The author will in no case be liable for any monetary damages arising from
such loss, damage or destruction.
On Tue, 6 Jul 2021 at 23:58, Mich Talebzadeh @.***>
wrote:

Thanks so far looks promising
Install Kubernetes Operator for Apache Spark with Volcano enabled
$ helm repo add spark-operator
https://googlecloudplatform.github.io/spark-on-k8s-operator
$ helm install my-release spark-operator/spark-operator --namespace
spark-operator --set enableBatchScheduler=true --set enableWebhook=true
kubectl get pod -n spark-operator
NAME                                         READY   STATUS    RESTARTS
AGE
my-release-spark-operator-5c64448d84-m2gth   1/1     Running   0
5m56s
view my Linkedin profile
https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/
Disclaimer: Use it at your own risk. Any and all responsibility for any
loss, damage or destruction of data or any other property which may arise
from relying on this email's technical content is explicitly disclaimed.
The author will in no case be liable for any monetary damages arising from
such loss, damage or destruction.
On Tue, 6 Jul 2021 at 23:04, Yinan Li @.***> wrote:

Closed #1289
https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/issues/1289
via #1291
https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/pull/1291.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/issues/1289#event-4985713723,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEXMDKDYJBGB4ZW4LJ46S5TTWN4VHANCNFSM47TT6FQQ
.


Publish latest version

Please publish the latest version of caseless which switched to Apache 2 license and includes a license file! Thank you!

v0.11.0


How to reproduce Wavefront's msum on influxDB

Hello Influx Team,
We are migrating our monitoring system form Wavefront to InfluxDB + Grafana. While trying to migrate our dashboards and metrics we found out there's nothing like Wavefront MSUM on influxDB and I could not find anything in the docs/issues like that.
Can you help me out reproduce it or find a variant?
I am using InfluxDB OSS Latest release (1.6.3) running on Ubuntu latest 18.04.

@mgagliardo glad to hear you're migrating to InfluxDB! Would SELECT SUM(<fieldName>) with a GROUP BY time(<timeWindow>) do what you need? Docs for SUM are here. Or, maybe a CONTINUOUS QUERY? Docs for CQs are here.

@mgagliardo glad you found a solution and thanks for posting for others to find!


Port bundle command to use AbstractCommand

See https://github.com/Homebrew/homebrew-services/pull/639
Discovered via https://github.com/Homebrew/brew/blob/master/Library/Homebrew/test/cmd/bundle_spec.rb (this should be the last PR of this type, going by setup_remote_tap call sites in brew tests)

Looks good, thanks again @dduugg!

This change appears to be breaking environments that use HOMEBREW_NO_AUTO_UPDATE=1, which is common in CI.

@ileitch If you set HOMEBREW_NO_AUTO_UPDATE and do not e.g. pin your taps at a specific version: this will happen, sorry. As per all our issue templates: if brew update fixes the problem, we do not consider it a bug.

@MikeMcQuaid Because the lock file contains local environment info, we can't use a lock file in our repo. Having to execute brew update in every workflow is problematic because it introduces a performance impact and potential instability.

@ileitch You'll need to figure out how to solve this yourself then, sorry.

@ileitch Care to explain the 👎🏻?

@MikeMcQuaid The points I mentioned are very real problems for teams maintaining CI environments, and how you simply dismissed them is why I downvoted your comment. In our case, we explicitly introduced HOMEBREW_NO_AUTO_UPDATE=0 to avoid a source of breakages and performance issues. I don't think we can just go back to implicit updates, and we may need to find another approach that doesn't depend on brew bundle, or perhaps even Homebrew altogether.
It's unfortunate you were not able to identify a migration strategy that does not introduce sudden breakages for your users, especially given the inflexibility around lock files. At least a warning of some kind would have been helpful.

@ileitch I'm aware of these problems but also: Homebrew maintainers are volunteers and we are not obligated to help you. Explaining the problem and getting a no context 👎🏻 makes us disinclined to help you in future.
You not need to go back to implicit updates but, in this case, you need to be able to figure out a way to solve this problem yourself as the default, supported Homebrew configuration does not have this problem. If you're tapping a repository during your build process at whatever the latest revision is: you're asking Homebrew (a rolling-release package manager) to not update some parts of itself while running the latest versions of other parts. This is going to break and there's nothing we can do about this.
I've opened https://github.com/Homebrew/brew/pull/17003 to better explain that these issues should not be reported in these situations and that this is a known issue. I'm not sure what we can do beyond that; it's not tenable to have master of Homebrew/homebrew-bundle and other taps to work on arbitrary old versions of Homebrew (note: this issue would not have occurred if you were on the latest stable tag).

I apologize for the flippant downvote, though I felt I was responding in kind to a flippant comment on your part. As an open-source maintainer myself, I completely understand you are under no obligation to help me, nor do I expect you to. I appreciate the full explanation in your last comment, it provides the level of detail I think your initial comment was lacking.
Perhaps there's a way to catch these errors as they occur, and explain the dangers around HOMEBREW_NO_AUTO_UPDATE and missing lock files. HOMEBREW_NO_AUTO_UPDATE is a fairly commonly used feature, in my experience, and I'm sure there are many users out there that will run into this sharp corner over the next few days.

I apologize for the flippant downvote

Thanks, I appreciate the apology ❤

Perhaps there's a way to catch these errors as they occur, and explain the dangers around HOMEBREW_NO_AUTO_UPDATE and missing lock files.

That's exactly the intent of https://github.com/Homebrew/brew/pull/17003.

@ileitch https://github.com/Homebrew/homebrew-bundle/pull/1335 will now print an error if brew bundle is too old, too.


Add Mobile Support

Currently planning to implement mobile and web support by writing a Go wrapper of brackeen/glfm

Will implement mobile support through a fork of golang/mobile (at goki/mobile), and web support will be separate (likely through GopherJS).

Will implement mobile support through a fork of golang/mobile (at goki/mobile), and web support will be separate (likely through GopherJS).

Hello, I searched through the doc, issue and readme and couldn't find the command to build the apk, can you elaborate on that? What should I do after the SDK and NDK are added to the PATH?

Apologies for the missing documentation; it will be improved very soon for the v2 release, but we have been focusing on developing the framework first. You need to install the goki tool (go install goki.dev/goki@latest) and then you can run goki build -t android to build the apk (it will be put at .goki/bin/build/appname.apk). You can also run goki install -t android or goki run -t android to install the app to the device or install and run it in addition to building it, respectively.

Also, for web, you can use goki build -t js and goki run -t js.

(And for ios you can use the same commands as android but with ios instead of android. Also, if your os architecture is different from that of the target mobile device, you may need to add the architecture of the target device; eg: goki run -t ios/arm64).

Apologies for the missing documentation; it will be improved very soon for the v2 release, but we have been focusing on developing the framework first. You need to install the goki tool (go install goki.dev/goki@latest) and then you can run goki build -t android to build the apk (it will be put at .goki/bin/build/appname.apk). You can also run goki install -t android or goki run -t android to install the app to the device or install and run it in addition to building it, respectively.

very nice，i will try, thx you.

If you install the latest version of the core tool (go install cogentcore.org/core/core@main), I have updated the commands so that you no longer need to use -t (eg: core run android instead of core run -t android).


Build playground for every PR

Ideally we should build a hosted version of the playground for every PR. Arguably, the Playground perhaps just needs to belong in Storybook to simplify things.

CodeSandbox is a very good choice for this, imo.

CodeSandbox is a very good choice for this, imo.


Experiment with removing version as a official Tool

https://issues.apache.org/jira/browse/SOLR-16842
Description
this removes bin/solr version but preserves bin/solr -v and bin/solr -version.   This I think makes things more consistent...  If the version tool did something more then put out the specific version ,then maybe I'd want to keep it...  As is, we don't actually have a VersionTool or any tests for it..
Solution
Remove it as a official tool, but preserve the -v and -version commands.
Tests
manual.
I am hoping @Willdotwhite will run the bin/solr.cmd versions of the commands and confirm my edits worked!
Checklist
Please review the following and check all that apply:

[ ] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[ ] I have created a Jira issue and added the issue ID to my pull request title.
[ ] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[ ] I have developed this patch against the main branch.
[ ] I have run ./gradlew check.
[ ] I have added tests for my changes.
[ ] I have added documentation for the Reference Guide

LGTM @epugh  👍🏻
PS C:\Users\Will\Projects\solr\solr\packaging\build\dev\bin> .\solr.cmd -v
Solr version is: 10.0.0
PS C:\Users\Will\Projects\solr\solr\packaging\build\dev\bin> .\solr.cmd -version
Solr version is: 10.0.0
PS C:\Users\Will\Projects\solr\solr\packaging\build\dev\bin> .\solr.cmd version

Invalid command-line option: version

Usage: solr COMMAND OPTIONS
       where COMMAND is one of: start, stop, restart, status, healthcheck, create, create_core, create_collection, delete, zk, auth, assert, config, export, api, package

  Standalone server example (start Solr running in the background on port 8984):

    solr start -p 8984

  SolrCloud example (start Solr running in SolrCloud mode using localhost:2181 to connect to Zookeeper, with 1g max heap size and remote Java debug options enabled):

    solr start -c -m 1g -z localhost:2181 -a "-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044"

  Omit '-z localhost:2181' from the above command if you have defined ZK_HOST in solr.in.cmd.

Pass -help after any COMMAND to see command-specific usage information,
  such as:    solr start -help or solr stop -help

Thanks for the test @Willdotwhite !!!   I am going to leave this open a few more days and see if folks have opinons about committing these changes...

I am closing this as per discussion, instead of removing version as an official tool, we're going to embrace it and have a proper VersionTool ;-)


Globus Transfer Demo Branch

Description
Big update which incorporates several updates that enable Globus Transfer.
Fixes #463 #493 #494 #502 #505 #515 #516  #529 #530 #533
Type of change

New feature (non-breaking change which adds functionality)
This change requires a documentation update

How Has This Been Tested?

[x] Local Pre-commit Checks
[ ] CI/CD Build

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] If applicable - I have commented my code, particularly in hard-to-understand areas
[x] If applicable - I have made corresponding changes to the documentation
[ ] If applicable - I have added tests that prove my fix is effective or that my feature works
[ ] If applicable - New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

We'll hold of on this PR until at least v1.0.9

Saw a review request, but I think we can merge once the functionality is reasonable even without all tests working.  The next one may or may not have the tests but should include several additional PRs


[DOCS] Added deploy mode info

Why are the changes needed?

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Was this patch authored or co-authored using generative AI tooling?

Codecov Report

Merging #5227 (e46dfdd) into master (a4b6413) will not change coverage.
Report is 4 commits behind head on master.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #5227   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         589     589
  Lines       33309   33309
  Branches     4398    4398
======================================
  Misses      33309   33309

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

Thanks, merged to master/1.8

Thanks, merged to master/1.8


Distinguishing mobile app vs mobile web

Hi,
Is there a way to distinguish between a request made from a mobile browser (e.g. Safari in iOS) and one made from a webview within an app?
Thanks

I just tried iOS simulator and the iOS webview doesn't include the Safari/:version part. I'm relying on this to make the detection. Can you try the ios-webview branch?

+1 (thanks for a great gem, and sorry I cannot try it myself)

Also, what about Android webview? It looks this is well documented: https://developer.chrome.com/multidevice/user-agent#webview_user_agent

+1, but I don't think that browser.safari? should return true for the webviews.  Our use case involves OTA enterprise app distribution which doesn't work in the webviews and requires standalone safari, which the UIWebKit is decidedly not.
I can understand how this could cause problems for existing apps, but I believe the correct implementation is not to consider a UIWebView as safari, especially considering the UA for the webviews doesn't include the string "Safari."

@samsonasu agree. I changed the detection of webviews and web apps; they aren't detected as Safari anymore. This will require a major versioning bump and warning message, but that's how I think it should be.


Convert STM32 drivers to DT_INST

Superseeds #22807

[x] drivers/adc/adc_stm32.c
[ ] drivers/can/can_stm32.c (cf below comment)
[x] drivers/counter/counter_ll_stm32_rtc.c
[ ] drivers/ethernet/eth_stm32_hal.c (Only impact DT_DTCM_BASE_ADDRESS. To be removed?)
[x] drivers/flash/flash_stm32.c
[ ] drivers/flash/flash_stm32f3x.c (Only impact DT_FLASH_SIZE. To be removed ?)
[ ] drivers/flash/flash_stm32l4x.c (Only impact DT_FLASH_SIZE. be removed ?)
[ ] drivers/gpio/gpio_stm32.c (cf below comment)
[ ] drivers/i2c/i2c_ll_stm32.c (cf below comment)
[ ] drivers/i2s/i2s_ll_stm32.c (cf below comment)
[x] drivers/pwm/pwm_stm32.c
[x] drivers/serial/uart_stm32.c
[x] drivers/spi/spi_ll_stm32.c
[ ] drivers/timer/stm32_lptim_timer.c (To be converted to DT first)
[x] drivers/usb/device/usb_dc_stm32.c

Conversion of some drivers to DT_INST not possible yet, cf https://github.com/zephyrproject-rtos/zephyr/pull/22807#issuecomment-592481101

Following test is failed:
902/919 qemu_xtensa               tests/kernel/sched/schedule_api/kernel.scheduler.multiq FAILED Failed (qemu 6.259s)

@arnopo, thanks for the review. Points fixed or commented.

One failed test:
919/919 qemu_cortex_r5            tests/kernel/context/kernel.common                 FAILED Failed (qemu 6.129s)

Failing test:
Failures  Sanitycheck / qemu_x86_64:tests/kernel/mem_protect/syscalls/kernel.memory_protection.syscalls / tests/kernel/mem_protect/syscalls/kernel.memory_protection.syscalls

@erwango would it make sense to merge this and have new PRs so we don't have CI growing to large?  I know we'll need a second pass conversion based on what we are doing in PR #23245.

@erwango would it make sense to merge this and have new PRs

@galak Definitely!


can producer length be non-integers?

The following program (with version v0.2-beta.1):
#lang video
(displayln (get-property (clip "vid.mp4") "length"))

prints a non-integer number 83/15.
Is this expected?
(The same program produces an error on master)

fwiw, here's the error on master
bytes->string/locale: contract violation
  expected: bytes?
  given: #<cpointer:av-bprint>
  argument position: 1st
  other arguments...:
   #\?
  context...:
   video/private/init.rkt:68:2: for-loop
   video/private/init.rkt:107:5

Yes, the length can be any real?. This is because length is written in terms of seconds. In v0.1 it was in terms of frames because I naively thought it was atomic. Looking into video encodings more I realized that was foolish and seconds was a much better unit, allowing for sub-frames clips.
I will take a look into the error, thanks for catching it.

Ok that makes sense, thanks.
(I think the documentation might still in terms of frames though.)


PopOs 20.04 / Ruby 2.6.0 / build failed

I've tried reinstalling rbenv and ruby-build a few times through apt-get.
The behavior:
(base) diego@inspiron:~/code/thinkseg$ rbenv install 2.6.0
Downloading ruby-2.6.0.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.6/ruby-2.6.0.tar.bz2
Installing ruby-2.6.0...

BUILD FAILED (Pop 20.04 using ruby-build 20200819-2-g258455e)

Inspect or clean up the working tree at /tmp/ruby-build.20200910003451.91160.mmtfy3
Results logged to /tmp/ruby-build.20200910003451.91160.log

Last 10 log lines:
The Ruby openssl extension was not compiled.
The Ruby readline extension was not compiled.
ERROR: Ruby install aborted due to missing extensions
Try running `apt-get install -y libssl-dev libreadline-dev` to fetch missing dependencies.

Configure options used:
  --prefix=/home/diego/.rbenv/versions/2.6.0
  --enable-shared
  LDFLAGS=-L/home/diego/.rbenv/versions/2.6.0/lib
  CPPFLAGS=-I/home/diego/.rbenv/versions/2.6.0/include

Thanks <3

I fixed it!
Just type: sudo apt-get install -y libssl-dev libreadline-dev


How to generate all isobars in weak decay?

Bug description
I wanted to checkout ComPWA using the decay Lb->pKgamma (modelled as Lb->LStar(->pK)gamma).
For this, I started from the tensorwaves amplitude analysis notebook which runs fine using binder in my browser. When I implement my decay however, I get stuck at the qrules.generate_transitions() step as it refuses to let the Lb decay via pK resonances.
How to reproduce?
import qrules
reaction = qrules.generate_transitions(
    initial_state=("Lambda(b)0", [-0.5, +0.5]),
    final_state=["p", "K-","gamma"],
    allowed_interaction_types=["weak","strong","em"],
    formalism="helicity",
)

import graphviz
dot = qrules.io.asdot(reaction, collapse_graphs=True)
graphviz.Source(dot)

This finishes happily with possible decays via pgamma and Kgamma states. But it does not show the decay via pK resonances.
When I try to specify an intermediate state.
reaction = qrules.generate_transitions(
    initial_state=("Lambda(b)0", [-0.5, +0.5]),
    final_state=["p", "K-","gamma"],
    allowed_intermediate_particles=["Lambda(1520)"],
    allowed_interaction_types=["weak","strong","em"],
    formalism="helicity",
)

It crashes with this error message
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
Cell In[14], line 3
      1 import qrules
----> 3 reaction = qrules.generate_transitions(
      4     initial_state=("Lambda(b)0", [-0.5, +0.5]),
      5     final_state=["p", "K-","gamma"],
      6     allowed_intermediate_particles=["Lambda(1520)"],
      7     allowed_interaction_types=["weak","strong","em"],
      8     formalism="helicity",
      9 )

File /srv/conda/envs/notebook/lib/python3.8/site-packages/qrules/__init__.py:404, in generate_transitions(initial_state, final_state, allowed_intermediate_particles, allowed_interaction_types, formalism, particle_db, mass_conservation_factor, max_angular_momentum, max_spin_magnitude, topology_building, number_of_threads)
    402     stm.set_allowed_interaction_types(list(interaction_types))
    403 problem_sets = stm.create_problem_sets()
--> 404 return stm.find_solutions(problem_sets)

File /srv/conda/envs/notebook/lib/python3.8/site-packages/qrules/transition.py:626, in StateTransitionManager.find_solutions(self, problem_sets)
    624         violated_rules |= rules
    625     if violated_rules:
--> 626         raise RuntimeError(
    627             "There were violated conservation rules: "
    628             + ", ".join(violated_rules)
    629         )
    630 if (
    631     final_result.execution_info.not_executed_edge_rules
    632     or final_result.execution_info.not_executed_node_rules
    633 ):
    634     not_executed_rules: Set[str] = set()

RuntimeError: There were violated conservation rules: BottomnessConservation

Expected behaviour
The decay via Lambda states should be allowed, it's an electroweak b->sgamma transition with a subsequent strong decay of the resonance to pK.

Hi @redeboer ,
Thank you very much for looking at this so quickly!
Here is maybe an additional clarification that may not be super clear from my question. (Apologies if this is already obvious to you!)
My issue seems to be specific to the Lambda resonance. The Lb decays weakly via all three isobars incl. bottom- and strangeness non-conservation as we go from quark content (udb) to (uud)(ubar s) gamma. But for some reason, QRules selectively ignores Lb -> LStar (-> pK) gamma but finds the other two Lb -> K* (-> Kgamma) p and Lb -> N (-> pgamma) K.
Cheers!


Start tracking release build information in an azure storage table

PR Summary
Start tracking release build information in an azure storage table

Also, fix some issues found when the build is started through a schedule

PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] to your commit messages if the change is significant or affects feature tests

@adityapatwardhan 	 can you update your review?

Can you have a look at the codefactor issues, it is reporting a few trailing spaces.


add metadata check

solves: https://github.com/google-github-actions/deploy-cloudrun/issues/508

add metadata kind check
add unit tests

if make sense i update the docs.

Oops - I was already working on this this morning: https://github.com/google-github-actions/deploy-cloudrun/pull/519


Updated to use pyrabbit2, as this is the latest version.

this is a duplicate of https://github.com/akrzos/collectd-rabbitmq-monitoring/pull/6 .
It should have been opened here https://github.com/centos-opstools/collectd-rabbitmq-monitoring