Downloading the tbv dataset.

I'm trying to download the tbv dataset and it seems there are two instructions to do so. Do these two methods produce the same result?
One here:

https://github.com/argoai/argoverse2-api/blob/main/DOWNLOAD.md
s5cmd --no-sign-request cp s3://argoai-argoverse/av2/tbv/* target-directory

And another here:
2. https://github.com/argoai/argoverse2-api/blob/main/src/av2/datasets/tbv/README.md
SHARD_DIR={DESIRED PATH FOR TAR.GZ files} s5cmd cp s3://argoai-argoverse/av2/tars/tbv/*.tar.gz ${SHARD_DIR}
When I try 1, I get an error "s5cmd is hitting the max open file limit allowed by your OS. Either increase the open file limit or try to decrease the number of workers with '-numworkers' parameter'.
When I try 2, I get an error
"Error session: fetching region failed: NoCredentialProviders: no valid providers in chain. Deprecated."

probably downloads half of the dataset, while 2. doesn't initiate the download. I will probably continue with 1, but 2. probably is faster. I'm using Linux Ubuntu 18.04.

Hi @tom-bu,
Thanks for your interest!

Have you tried increasing the open file limit? Additionally, does change the numworkers parameter resolve the issue?

I think the second command you listed is missing --no-sign-request. Does this resolve the issue: SHARD_DIR={DESIRED PATH FOR TAR.GZ files} s5cmd --no-sign-request cp s3://argoai-argoverse/av2/tars/tbv/*.tar.gz ${SHARD_DIR}?

Hey @tom-bu, thanks for trying out TbV. If you're having issues with s5cmd even after trying the fixes that Ben suggested, you can just download the 21 tar files, directly, given the links listed here:
wget https://s3.amazonaws.com/argoai-argoverse/av2/tars/tbv/TbV_v1.0_shard0.tar.gz
wget https://s3.amazonaws.com/argoai-argoverse/av2/tars/tbv/TbV_v1.0_shard1.tar.gz
...
wget https://s3.amazonaws.com/argoai-argoverse/av2/tars/tbv/TbV_v1.0_shard20.tar.gz

The TbV dataset is available in two identical formats, for convenience to users. Either you can download the 21 tar.gz files directly, and then use the untar_tbv.py script, or you can pull down all of the files (in their extracted form). Depending upon your connection, one may be much faster than the other (there are almost 8 million images files in the extracted format, for example).

Thanks for the feedback! My s5cmd version doesn't seem to have a sync method, so  I'm currently trying option 2 with the tar files. I realized for option 2 I wasn't waiting long enough to download, but I believe the --no-sign-request is necessary.

Hi @johnwlambert, thanks for the info. Another question I had about the TbV dataset is where can I find the labels for change? Is there a file that indicates different log pairs and what has changed?
Thanks!

Hi @tom-bu, we'll upload more information about the train/val/test splits for TbV in the next day or two.

Thanks for the update @johnlambert-argo. Look forward to it!

@tom-bu I've provided a clustering of logs by spatial location in this PR: https://github.com/argoai/av2-api/pull/26.
A few things to note:

Each log within a cluster shares some significant visual overlap with other logs within its cluster.
These are not necessarily before/after pairs. In some cases, all logs in a cluster may be "after" a change.
Each cluster has at least one log in the val or test set.
Logs of each cluster are provided in chronological order.

@johnlambert-argo great, thanks! Are all of the logs clustered? I believe there are ~1000 logs? Also, will labels be released for which logs include change/no change?

Hi @tom-bu, no, this is only a specific subset of logs, where some log in the cluster had a real-world change.
You could cluster all the log spatially though, using their poses.
Labels for the val set will be released, but labels for the test set will not be (they'll be used for an online leaderboard, which you will be welcome to submit to). We'll release those val set annotations in probably 1-3 days.

Hi @johnlambert-argo,
I just realized that this map change dataset doesn't necessarily have before and after sensor data as shown in the image here. So it seems we're just checking if the corresponding vector map is up-to-date or not?
And I wanted to verify that the training/validation sets have no changes. Therefore, all we need to know is if a log is in the training/validation set to know the label?
Thanks,
Tom

Hi @tom-bu, were you able to get your questions answered?

Have the data splits been released yet? I think that's the only thing I'm waiting on.

@tom-bu These are now available here: https://github.com/argoai/av2-api/blob/main/src/av2/datasets/tbv/splits.py
Please reach out if you have any other questions!


Component as icon

I'm trying to convert a project from leaflet to openlayers. In my project, I need to display custom icons on the map, but the problem is that for this I used a component that changes visually depending on the props. ol-style-icon only accepts the scr of the icon itself, this does not suit me, is there an option to use a Vue component as an icon?

We had a pretty similar problem in the past. As far as I know there is currently no such direct feature.
Our solution was to generate an SVG and return an SVG inline data URL. This URL we passed as the src. It worked since the component generated the URL based on the input params.

We had a pretty similar problem in the past. As far as I know there is currently no such direct feature. Our solution was to generate an SVG and return an SVG inline data URL. This URL we passed as the src. It worked since the component generated the URL based on the input params.

interesting solution, can you be more specific, are you generating svg from a Vue component? if yes, what tool?

I am simply building the SVG string and put it into a data URL.
With this tool, you can try it out: https://yoksel.github.io/url-encoder/


Increase the deadline to 30 seconds in lint

Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

@runcom Alright, travis passes with this one! :)


Incorrect Usage of SQLITE_OPEN_FILEPROTECTION_NONE in FIRMessagingRmqManager.m

Description
Description:
In the method - (void)openDatabase within the file FIRMessagingRmqManager.m, the constant SQLITE_OPEN_FILEPROTECTION_NONE is erroneously passed to the function sqlite3_open_v2(...). This issue is akin to the problem reported for Remote Config in issue #10884 and has now surfaced in the Messaging module. Notably, SQLITE_OPEN_FILEPROTECTION_NONE is not a standard flag provided by SQLite; rather, it's specific to Apple's version of SQLite and has not been merged into the main repository.
Current Implementation:
The following line in the FIRMessagingRmqManager.m,
      int result = sqlite3_open_v2(
          [path UTF8String], &self -> _database,
          SQLITE_OPEN_READWRITE | SQLITE_OPEN_CREATE | SQLITE_OPEN_FILEPROTECTION_NONE, NULL);

Proposed Solution:
To address this issue, the following modifications can be made to the FIRMessagingRmqManager.m file:
Replace the existing line with the following lines:
        int flags = SQLITE_OPEN_READWRITE | SQLITE_OPEN_CREATE;
    #ifdef SQLITE_OPEN_FILEPROTECTION_NONE
        flags |= SQLITE_OPEN_FILEPROTECTION_NONE;
    #endif

        int result = sqlite3_open_v2(
            [path UTF8String], &self -> _database, flags, NULL);

This solution mirrors the approach(#12548) implemented for issue #10884 and ensures compatibility with both Apple's SQLite version and the main repository.
Reproducing the issue
No response
Firebase SDK Version
10.25.0
Xcode Version
15.3
Installation Method
Swift Package Manager
Firebase Product(s)
Messaging
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

@morganchen12 @paulb777 Can you help us with this issue? Let us know if we can contribute to fix it.

Yes, the proposed solution looks reasonable to me and you're welcome to open a PR for this if you'd like.

Done via https://github.com/firebase/firebase-ios-sdk/pull/12909. Thanks again, @doganaltinbas! This will go out in Firebase 10.27.0


Adds Circles2D Pattern.

Adds Circles2D Pattern for generating circle or ring patterns.

Thanks @kwokcb yes some stagger would be useful! @Cinifreak and I had some offline chats, and this circles/rings approach may be absorbed by a more generic nodegraph for generating 2d shapes.

@crydalch @Cinifreak Now that the randomfloat and randomcolor nodes are merged to MaterialX main, would you be ready to move forward with the generic 2D shape node that you're envisioning?


⚠ Bofrost.nl has degraded performance

In 11fdd9c, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1814 ms

Resolved: Bofrost.nl performance has improved in 884b4e5.


S3 access documentation

Getting Spark to connect to S3 can require a bit of trial and error - it would be good if we had the process documented.
This recipe works for me at the moment on my local machine:

build ADAM from source at c8a2202
use scripts to change to scala 2_11 Spark 2.x
local spark installed is spark-2.2.0-bin-hadoop2.7

I downloaded jars:
https://mvnrepository.com/artifact/com.amazonaws/aws-java-sdk/1.7.4
https://mvnrepository.com/artifact/org.apache.hadoop/hadoop-aws/2.7.1
I start adam-shell like:
../adam/bin/adam-shell --jars aws-java-sdk-1.7.4.jar,hadoop-aws-2.7.1.jar,../adam/adam-assembly/target/adam-assembly-spark2_2.11-0.23.0-SNAPSHOT.jar

reading from s3a appears to work
val x = sc.textFile("s3a://1000genomes/CHANGELOG")
scala> val x = sc.textFile("s3a://1000genomes/CHANGELOG")
x: org.apache.spark.rdd.RDD[String] = s3a://1000genomes/CHANGELOG MapPartitionsRDD[1] at textFile at <console>:24

scala> x.count
res0: Long = 11987

Attempts that didn't work for me:

I tried to use --packages rather than --jars to add dependencies, this resulted in errors
It tried to add the maven coordinates for the two dependency files to the pom.xml - this resulted in errors.

todo:

it would be good for the dependencies required for S3 access to be in the POM, perhaps activated by a profile.

test reading BAM/VCF from S3

For the record, I don't need to provide any extra jars when using Elastic Map Reduce (EMR) version emr-5.6.0 on AWS, so Spark 2.1.1 on Hadoop 2.7.3 YARN with Ganglia 3.7.2 and Zeppelin 0.7.1, then build ADAM from source with Hadoop 2.7.3 dependency version, and then
$ ./bin/adam-submit --master yarn -- --version
Using ADAM_MAIN=org.bdgenomics.adam.cli.ADAMMain
Using SPARK_SUBMIT=/usr/bin/spark-submit
17/06/24 22:15:35 INFO ADAMMain: ADAM invoked with args: "--version"

       e         888~-_          e             e    e
      d8b        888   \        d8b           d8b  d8b
     /Y88b       888    |      /Y88b         d888bdY88b
    /  Y88b      888    |     /  Y88b       / Y88Y Y888b
   /____Y88b     888   /     /____Y88b     /   YY   Y888b
  /      Y88b    888_-~     /      Y88b   /          Y888b

ADAM version: 0.23.0-SNAPSHOT
Commit: 0306717cb952511d48e514475b70ae995a468b5a Build: 2017-06-24
Built for: Apache Spark 2.1.0, Scala 2.11.8, and Hadoop 2.7.3

$ ./bin/adam-shell --master yarn --driver-memory 58G --executor-memory 58G
Using SPARK_SHELL=/usr/bin/spark-shell
Spark context Web UI available at http://<IP_ADDRESS>:4040
Spark context available as 'sc' (master = yarn, app id = application_1498339040857_0002).
Spark session available as 'spark'.
Welcome to
      ____              __
     / __/__  ___ _____/ /__
    _\ \/ _ \/ _ `/ __/  '_/
   /___/ .__/\_,_/_/ /_/\_\   version 2.1.1
      /_/

Using Scala version 2.11.8 (OpenJDK 64-Bit Server VM, Java 1.8.0_131)
Type in expressions to have them evaluated.
Type :help for more information.

scala> import org.bdgenomics.adam.rdd.ADAMContext._
import org.bdgenomics.adam.rdd.ADAMContext._

scala> val genotypes = sc.loadGenotypes("s3a://bucket/sample.genotypes.adam")
genotypes: org.bdgenomics.adam.rdd.variant.GenotypeRDD =
GenotypeRDD(MapPartitionsRDD[1] at map at ADAMContext.scala:345,SequenceDictionary{
...

scala> genotypes.rdd.count()
res1: Long = 23600775

+1 to documenting, but also +1 to @heuermh's point. I believe most distros (eg EMR, Databricks, CDH) build some AWS library in. I know this is true for EMR&DB, and I'm pretty sure of the same for CDH.


update blog categories and tags

I think we can close this #60 issue now. I added opinion as a category and edited some categories/tags in existing blog posts. moving forward we will just need to be mindful of category/tag use and edit/clean as needed.

Ok Great. Do let me know if you'd like to help review PRs regarding the tags in the future, as you spearheaded this effort! PR reviewing itself is a separate skill.
Thanks again.

Ok Great. Do let me know if you'd like to help review PRs regarding the tags in the future, as you spearheaded this effort! PR reviewing itself is a separate skill. Thanks again.

@bitkarrot I would love to get some experience doing that

sure thing. will add you as a reviewer for the next blog post someone makes.
There is also an event blog post which i just started, the plan is to automate the events from the Discord over to the markdown event.md post instead of updating it manually. Its a good little starter project.  If you know some basic python and want to work on this, let me know.
Otherwise, I will make an automated script for it in the next few weeks.


Add support for model_name-less models.

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Screenshots
Please attach before and after screenshots of the change if applicable.

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have not rewritten tests relating to key interfaces which would affect backward compatibility

Hey @ArthurConmy, do you want me to take over on this? Looks like we will be able to wrap up 2.0 tomorrow, and I would love to get moving on 2.1 immediately with this and a couple other PRs in mind for what that will include.


JS form sovereign cloud support

JS form sovereign cloud support

API change check
API changes are not detected in this pull request.

@benbp, @hector-norza, @joheredi, @ronniegeraghty, @jsquire, @deyaaeldeen  Could you please help review this PR? Thanks in advance.

You've got the right folks engaged as reviewers.   I'll defer to those folks as the experts on the JS ecosystem.


Change private to protected methods in TranslocoDirectiveBase

My application is using objects implementing an interface Translateable, having a translate key or, if not present, a fallback-value. My idea was to use my own directive extending TranslocoDirectiveBase and pick the translate key or directly return the value if no key is present.
For this I'd need to override private getTranslateFn(lang: string, read: string | undefined): (key: string, params?: HashMap)
Or is there already a better approach for this? Right now everywhere I'm using this markup:
{{ m.displayTextTranslation ? t(m.displayTextTranslation) : m.displayText }}
and I'd like to be able to say {{ t(m) }} where m is my Translateable.

I think that I have a similar case, so I'm posting it here. In order to avoid mistakes like writing a key wrongly or something like that, I generate a d.ts from the .json with all possible keys. It seems like this:
type TranslationKeys = 'a' | 'b.c.d' | '...';

However, unfortunately, I can't have the benefits from type-checking as TranslocoDirective accepts any string... so, I might be wrong, but for this case I described, a simple generic for TranslocoDirective would be sufficient:
- export class TranslocoDirective implements OnInit, OnDestroy, OnChanges {
+ export class TranslocoDirective<TKeys extends string = string> implements OnInit, OnDestroy, OnChanges {

- private getTranslateFn(lang: string, read: string | undefined): (key: string, params?: HashMap) => any {
+ private getTranslateFn(lang: TKeys, read: string | undefined): (key: string, params?: HashMap) => any {

so I'll be able to override/extend the directive like this:
@Directive({ selector: '[transloco]' })
class StronglyTypedTranslocoDirective extends TranslocoDirective<TranslationKeys> {}

Playground

Since typescript wouldn't mind changing the overridden method's parameters having a protected getTranslateFn would solve your problem, too. I guess your use-case is a bit too specific to become part of the main lib.

Since typescript wouldn't mind changing the overridden method's parameters having a protected getTranslateFn would solve your problem, too.

You're correct, both solutions would work.

I guess your use-case is a bit too specific to become part of the main lib.

What I proposed was a simple addition of TypeParameter, which defaults to string... I don't see how this could impact the lib in any way as it generates no additional code at all or breaks something. That wouldn't just benefit my project, but that of anyone who wants to have their strings being checked statically, rather than just praying they're correct and doesn't break at runtime.

That said, I don't really care about the approach, as in the end it will all solve the problem (although this will generate a little more code just to get type-checking working, but ok 🤷🏽♂). With the way you proposed it would look like this:
// Missing `@Input()`
@Directive({ selector: '[transloco]' })
class StronglyTypedTranslocoDirective extends TranslocoDirective {
  override getTranslateFn(lang: TranslationKeys) {
    super.getTranslateFn(lang);
  }
}

Playground

Yeah, sure! I like your idea! But since an extension of TranslocoDirective would be required anyway I guess it's more up to the user to implemented it if really needed. Guess it just complicates the lib unnecessarily. But that's just my opinion! Should the devs decide. We just need this method to be protected, so there's no need to hack around ;)
Would you be so nice and create a PR? Otherwise I could do it, just a bit busy right now.

Done, @angelaki. See #492.

Any reason / idea why this isn't merget, yet? Guess it's not that risky ;)


Order Hardware

@JaiminD99 said that he own many parts such as RFID module, 2 ultrasonic sensors, breadboards, wires, gps module, gsm module, LCD 8x2

Parts using Jaimin's treasures.


Handling new Pillow version with rasterio alternative

Solves https://github.com/sentinel-hub/sentinelhub-py/issues/230

For decoding JPEG images we accept changes brought by new Pillow version.
Decoding 15-bit JP2 images cannot be done with the new Pillow version. In such case users will now get a warning and be suggested to install rasterio. If rasterio is installed then sentinelhub-py will use it to decode JP2 images by default.

Additional improvements in this PR:

better handling of some warnings,
updated deprecated function and parameter from tifffile package,
moved pytest and code coverage configurations into pyproject.toml to resolve some warnings because of clashes of multiple configuration files.

Codecov Report

Merging #249 (7249281) into develop (40a6f36) will decrease coverage by 0.24%.
The diff coverage is 76.31%.

@@             Coverage Diff             @@
##           develop     #249      +/-   ##
===========================================
- Coverage    88.81%   88.56%   -0.25%
===========================================
  Files           43       43
  Lines         4076     4094      +18
===========================================
+ Hits          3620     3626       +6
- Misses         456      468      +12

Impacted Files
Coverage Δ

sentinelhub/decoding.py
73.00% <74.19%> (-15.75%)
:arrow_down:

sentinelhub/io_utils.py
77.57% <85.71%> (-0.42%)
:arrow_down:

sentinelhub/download/handlers.py
80.00% <0.00%> (+10.90%)
:arrow_up:

Continue to review full report at Codecov.

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


px_update_git_header.py: allow -beta/-rc in tag

This changes two things:

This adds "-beta" as a valid tag suffix.
This changes "rc" without "-" to "-rc". "rc" without is now described
as deprecated and with "-rc" is preferred.

@julianoes this is not enough: the rest of the system does not support beta tags either, e.g. https://github.com/PX4/Firmware/blob/master/src/lib/version/version.h#L90. Similar for rc.


Update Jetson bracket

Closes #42

Provides more printable
More printable
Easier to get on/off chassis

Currently it's all 10mm thick. That is likely overkill - Let me know what makes more sense and I can shrink it to improve print time and mass.

Standoffs (highlighted) are a separate part. We are re-using the same screws already in the Jetson plastic stand.

Are you good with 1cm thick?
It should fit on the Style, so let's print it there. Dunno about time or filament.


Need OpenSSL 1.x+ in formula's python virtualenv

So I created a formula following https://github.com/Homebrew/brew/blob/master/docs/Python-for-Formula-Authors.md but it uses the system python to make the virtual environment. How would I go about getting it to install homebrew's python and using that so I can have the newest OpenSSL available?

I was able to get around the issue by doing the following:
class Myformula < Formula

  depends_on "python"

  include Language::Python::Virtualenv

  ...

  def install
    venv = virtualenv_create(libexec, "#{HOMEBREW_PREFIX}/bin/python"
    venv.pip_install resources
    venv.pip_install_and_link buildpath
  end
end

Is this the recommended way to do it?

CC @tdsmith and @ilovezfs who may know this

class Foo < Formula
  include Language::Python::Virtualenv

  desc "my foo formula"
...

  depends_on :python

  def install
    virtualenv_install_with_resources
  end
end

That still uses the system python which doesn't have the newest OpenSSL. The only way I was able to get it to work was to use the code in my 2nd comment.

It should be using the python in $PATH. (If that is not Homebrew's python, it will be if you install with --build-bottle, which is how the bottles will be built.)
Otherwise, the behavior you're describing is surprising.

Yup it is in my path if I install python ahead of time, but it is still using the system python.

Can you provide a gist-logs link for your formula and a link to the software you're installing?

As far as I can tell depends_on :python picks brew's python if it's installed even if you have system python first in the PATH.

Ah sorry I had depends_on :python if MacOS.version <= :snow_leopard switching it to just depends_on :python used the python installed from brew.
However is brew python isn't installed it falls back to the system python which has an old OpenSSL.

However if brew python isn't installed it falls back to the system python which has an old OpenSSL.

Yup, that's as I expected. If you want to force brew python you have to use depends_on "python" or use depends_on :python and build a bottle.

Ok great, thanks! That should probably be noted in the documentation.


add WinSDK 6.1 guids to guids.h

define missing interfaces in qedit.h
fix missing resource.h file
remove strmiids.lib from linker input file
This pull request allows the building of the VS2015 project without the installation of the Windows 6.1 SDK which is deprecated.  I would like to modify the project to build 64 bit executables also but this was a first step.

If SDK6.1 is no longer needed, please update "HOWTO-BuildWindowsNativeCode.txt" to remove references to the SDK and it's associated environment variable.

Also, please take a look at the CONTRIBUTING file. You need to agree to the Google CLA before I can accept code contributions for you (it's super easy to do).

I will take a look at the CLA and also update the txt docuemnt and go through the projects to remove any last vestiges of the Windows 6.1 SDK environment variables. The problem with using an older SDK and building on a newer system is depending on where the old SDK is in the include chain it could bring in a lot more older headers than desired.
I also noticed that there where a multiple of project types for selection.  Do we really need all those or could we boil down to just debug/release and future debug x64/release x64 and build everything?


defineProps breaks types in JS with template

When using defineProps in js the types all revert to any.
Without defineProps:

With defineProps:

We can support template type-check with lang="js" due to typescript limitation. See https://github.com/johnsoncodehk/volar/issues/336#issuecomment-888368947
Will force disable template type-check with lang="js".


repeat attribute in animation not working in web

Current Behavior
The docs imply that it's possible to use repeat for animations, however it doesn't seem to work.
Expected Behavior
repeat and other moti attributes like loop and delay are available in tamagui. This discussion with @nandorojo seems to indicate that loop and sequence might have worked at some point? Hopefully, the new devbox setup should help demo simple tamagui recipes now https://github.com/tamagui/tamagui/issues/2075#issuecomment-2069527142
Alternatively it would be great to have some guidance on how to drop down one level to pass configuration down to moti?
Tamagui Version
1.94.5

Platform (Web, iOS, Android)
web

Reproduction
https://codesandbox.io/p/devbox/angry-monad-t8rmdt?file=%2Fapp%2F(tabs)%2Findex.tsx
System Info
✗ npx envinfo --system --npmPackages --binaries --browsers

  System:
    OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (2) x64 AMD EPYC
    Memory: 962.21 MB / 4.01 GB
    Container: Yes
    Shell: Unknown
  Binaries:
    Node: 20.12.0 - /usr/local/bin/node
    Yarn: 4.0.2 - /usr/local/bin/yarn
    npm: 10.5.0 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/share/npm-global/bin/pnpm
  npmPackages:
    @babel/core: ^7.23.3 => 7.23.7
    @expo/metro-runtime: ~3.1.3 => 3.1.3
    @react-navigation/native: ^6.0.2 => 6.1.9
    @tamagui/config: ^1.94.5 => 1.94.5
    @tamagui/metro-plugin: ^1.94.5 => 1.94.5
    @types/react: ~18.2.14 => 18.2.47
    babel-preset-expo: ^10.0.1 => 10.0.1
    expo: ~50.0.6 => 50.0.6
    expo-font: ~11.10.2 => 11.10.2
    expo-linking: ~6.2.1 => 6.2.2
    expo-router: ~3.4.7 => 3.4.7
    expo-splash-screen: ~0.26.4 => 0.26.4
    expo-status-bar: ~1.11.1 => 1.11.1
    expo-system-ui: ~2.9.3 => 2.9.3
    expo-web-browser: ~12.8.2 => 12.8.2
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    react-helmet-async: ~2.0.4 => 2.0.4
    react-native: 0.73.4 => 0.73.4
    react-native-reanimated: ~3.6.2 => 3.6.2
    react-native-safe-area-context: 4.8.2 => 4.8.2
    react-native-screens: ~3.29.0 => 3.29.0
    react-native-web: ^0.19.10 => 0.19.10
    tamagui: ^1.94.5 => 1.94.5
    typescript: ^5.3.3 => 5.3.3

I think if you pass an array to the animate prop, the second item in the array will be the moti config


Rework items tab

The items tab as it is now is fairly pointless. Originally, it was a quick way of representing the flow of items between recipes, but the current visualization is superior in virtually every way. It should probably be reworked into a list of total item-rates for each item. Those totals are not easily available elsewhere in the calculator, and it could even break down the item-rates in terms of belts, inserters, and/or logistic bots required to service that rate.

Done, or at least started, in da622a95d05ff5b0bb38a20e6e6cc5faa1a8e819.


variable not work

after upgrade 3.0.0, these config report error:
# regex that matches JetBrains apps
apps='^(IntelliJ IDEA|WebStorm|CLion)$'

# float all JetBrains apps
yabai -m rule --add app="${apps}" manage=off

Error:
invalid key-value pair 'app='
missing required key-value pair 'app[!]=..' or 'title[!]=..'

If you create an issue and find the solution yourself, please post the solution so people can find it when they search this issue board.


Add start/stop button for keeping track of the scenes times

The scene has a start time and an end time in the frontmatter. Maybe it would be best to move it to a simpler duration to be tracked with a start timer and end timer that calculates the duration of a session regardless of the start time and end time.

What if...
What if I add a new YAML key in the SceneNavigation code block looking like this:
duration: hh:mm
durations:
  - [start, stop]
  - [start, stop]


⚠ Bofrost.lu has degraded performance

In e6a0125, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1247 ms

Resolved: Bofrost.lu performance has improved in 146410f after 9 minutes.


Medium vulnerability snyk issue

<EMAIL_ADDRESS>has a medium snyk issue that is fixed in version 0.5.0
https://stackoverflow.com/a/75975562/7087480

Hi there,
Thank you for bringing this to our attention. I’m happy to share the steps
required to submit a finding and join our private research group. We use
HackerOne to manage our bug bounty program. You can reach out to their
support to request additional information about their processes for
reviewing and validating bugs. Please send your submission to this email
@.*** Once you submit your findings to that specific
email address, you will receive an auto-response with a direct link to
submit the vulnerability.
Next, you will be prompted to create an account on HackerOne if you don't
already have one, and then you will be able to select a button to submit
the report.
Let us know if you have any questions!
Emily McDonnell
VP, Trust and Safety | Remind
remind.com
On Mon, May 1, 2023 at 10:48 AM JohnCliffe @.***> wrote:

@.*** has a medium snyk issue that is fixed in version 0.5.0
https://stackoverflow.com/a/75975562/7087480
—
Reply to this email directly, view it on GitHub
https://github.com/remind101/express-xml-bodyparser/issues/1, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACAW42Y6OT4NLR6J3MG44YDXD7ZNBANCNFSM6AAAAAAXSAAXVA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Extend the optimistic locking functionality to bulk updates

Optimistic locking using @Version annotation is currently limited to update of a single entity. Extend this functionality to update methods that accept a list of entities.

Implemented.


Add package quality metrics to Pub PM

This issue was originally filed by<EMAIL_ADDRESS>
Pub Package Manager currently does not appear to provide any quality info about the packages. When browsing through packages it can be hard to assess package quality. I am suggesting adding user ratings to pub to enable package quality to be assessed. NPM made the mistake of not including this, and now there are third party tools such as this: http://npmsearch.com/ to enhance the NPM browsing experience.
Both user input and other metrics could be used to assess package quality (as in npmsearch.com). There are several ways this could be done, but anything would almost certainly be better than nothing.
Thanks!
:b

This issue has been moved to dart-lang/pub-dartlang#377.


Tool causing site to 403

Site works perfect but after running link checker links show 403 status. Clicking any link returns 403 and refreshing page does also.
Links from Google also show 403.
Cleared cache and cookies.
Site is https://shop.advanceautoparts.com
https://www.screencast.com/t/8UPQ9cub

Yeah, I think it's some DoS prevention, site does load, https://tools.pingdom.com/#5aac3b43adc00000 it just bans you after "clicking" so many links in a succession..
I guess there's nothing we can do...
Let's close this ticket, it's outside of the scope. @robteee please confirm are you happy to close

Hi Revelt,
Thanks for your responses and insight. I'll close this.


cats.Parallel instance for Task/ParIO[Throwable, ?]

Quickly create a cats.Parallel instance for Task/Task.Par.
Can we promote ParIO and ParTask (ie. ParIO[Throwable, ?]) to be a thing?

Added IONewtype to workout the problem with Scalaz not in classpath see
scalaz72.ParIO is no more. Instead, a newtype type ParIO[E, A] = IONewtype.T[E, A]
Task.Par[A] is no longer Task[A] @@ Tags.Parallel. Instead, a  newtype IONewtype.T[Throwable, ?]

@kaishh please review.

I'd also like to keep the change minimal. But semantically they're the same so that keeping both is confusing.
Anws, I'll update if further requested.

@enzief Looks great! Can you add tests for the laws for parallel to make sure they pass?

@jdegoes added test for Parallel laws.

I took a look and saw that Scalaz adds syntax for the Parallel tag. So we should try to keep that. Otherwise, looks good to merge! Thanks for your work on this.

@jdegoes @kaishh So we just ignore the classpath problem then?

I'd rather have two separate Par types for catz and for scalaz72


[BUG] longhorn rwx volume fails to mount on first pod

Describe the bug (🐛 if you encounter this issue)
Deployed a rwx pvc and pod.  The pod fails to mount the pvc.
`
Events:
Type     Reason                  Age                    From                     Message

Normal   Scheduled               5m41s                  default-scheduler        Successfully assigned default/rwx-node-a to 8c857dec-7cb8-45cb-8e20-a6c7569446c4
Normal   SuccessfulAttachVolume  5m29s                  attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-254b9a67-3a84-4309-b591-b83bac9c4900"
Warning  FailedMount             5m12s (x6 over 5m28s)  kubelet                  MountVolume.MountDevice failed for volume "pvc-254b9a67-3a84-4309-b591-b83bac9c4900" : rpc error: code = Aborted desc = volume pvc-254b9a67-3a84-4309-b591-b83bac9c4900 share not yet available
Warning  FailedMount             84s (x2 over 3m38s)    kubelet                  Unable to attach or mount volumes: unmounted volumes=[rwx1], unattached volumes=[rwx1 kube-api-access-bkm5r]: timed out waiting for the condition
Warning  FailedMount             78s (x4 over 4m56s)    kubelet                  MountVolume.MountDevice failed for volume "pvc-254b9a67-3a84-4309-b591-b83bac9c4900" : rpc error: code = Internal desc = mount failed: exit status 32
Mounting command: /usr/local/sbin/nsmounter
Mounting arguments: mount -t nfs -o vers=4.1,noresvport,intr,hard <IP_ADDRESS>:/pvc-254b9a67-3a84-4309-b591-b83bac9c4900 /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/3816fa16e001ad6c7497b189d35ec998cc5b5416c8d37ba291636e1f9b007e0e/globalmount
Output: mount: /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/3816fa16e001ad6c7497b189d35ec998cc5b5416c8d37ba291636e1f9b007e0e/globalmount: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
`
To Reproduce
`
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: pvc-rwx
spec:
accessModes:

ReadWriteMany
resources:
requests:
storage: 1Gi
storageClassName: longhorn

apiVersion: v1
kind: Pod
metadata:
name: rwx-node-a
namespace: default
spec:
restartPolicy: Always
containers:

name: rwx-node-a
image: busybox
imagePullPolicy: IfNotPresent
command: ["/bin/sh"]
args:

-c
|
while true; do
echo "$(date) node-$(cat /sys/class/net/eth0/address)" >> /rwx-vol/shared-$(cat /sys/class/net/eth0/address).log;
sleep $(($RANDOM % 5 + 5));
done
volumeMounts:
name: rwx1
mountPath: /rwx-vol
volumes:

name: rwx1
persistentVolumeClaim:
claimName: pvc-rwx
`

Expected behavior
Pod successfully mounting the rwx pvc.
Support bundle for troubleshooting
Environment
The os environment is alpine linux kernel 5.10.186, k3s installed in an oci container atop alpine, and then longhorn installed within that k3s container.

Longhorn version: 1.4.x
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: k3s version v1.26.3+k3s1 (01ea3ff2)

Number of management node in the cluster: 1
Number of worker node in the cluster: 1

Node config

OS type and version:
Kernel version: 5.10.186
CPU per node:
Memory per node: 16GB
Disk type(e.g. SSD/NVMe/HDD): SATA SSD
Network bandwidth between the nodes: n/a

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster: 1
Impacted Longhorn resources:

Volume names:

Additional context
If I manually create the mount's path and run the same mount command the nfs export allows the pod to start writing to it.
eg.
`
mkdir -p /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/3816fa16e001ad6c7497b189d35ec998cc5b5416c8d37ba291636e1f9b007e
0e/globalmount; mount -t nfs -o vers=4.1,noresvport,intr,hard <IP_ADDRESS>:/pvc-254b9a67-3a84-4309-b591-b83bac9c4900 /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longh
orn.io/3816fa16e001ad6c7497b189d35ec998cc5b5416c8d37ba291636e1f9b007e0e/globalmount
tail -f /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/3816fa16e001ad6c7497b189d35ec998cc5b5416c8d37ba291636e1f9b007e0
e/globalmount/shared-18:66:da:0b:b4:e6.log
Thu Oct  5 22:37:16 UTC 2023 node-ee:4e:68:2a:14:f9
Thu Oct  5 22:37:24 UTC 2023 node-ee:4e:68:2a:14:f9
Thu Oct  5 22:37:32 UTC 2023 node-ee:4e:68:2a:14:f9
Thu Oct  5 22:37:40 UTC 2023 node-ee:4e:68:2a:14:f9
Thu Oct  5 22:37:48 UTC 2023 node-ee:4e:68:2a:14:f9
Thu Oct  5 22:37:56 UTC 2023 node-ee:4e:68:2a:14:f9
Thu Oct  5 22:38:04 UTC 2023 node-ee:4e:68:2a:14:f9
Thu Oct  5 22:38:12 UTC 2023 node-ee:4e:68:2a:14:f9
Thu Oct  5 22:38:20 UTC 2023 node-ee:4e:68:2a:14:f9
Thu Oct  5 22:38:28 UTC 2023 node-ee:4e:68:2a:14:f9
Thu Oct  5 22:38:36 UTC 2023 node-ee:4e:68:2a:14:f9
Additionally if I create a second pod referencing this rwx volume, the second pod mounts it without issue since the mount point exists.
`

Can you check error messages in longhorn-manager and longhorn-instance-e logs? Also check dmesg on the host as the suggest dmesg(1) may have more information after failed mount system call.. Thank you.

Sorry @derekbit I don't see anything interesting in either of those spots other than some messages about not scheduling the other two replicas but I didn't think those were interesting since this is just a single node.
The longhorn-csi-plugin pod logs just show this same error over and over until I manually created the "globalmount" target directory path and reran the same mount command myself.
2023-10-05T22:31:12.430608783Z stderr F E1005 22:31:12.430494   22709 mount_linux.go:195] Mount failed: exit status 32
2023-10-05T22:31:12.4306202Z stderr F Mounting command: /usr/local/sbin/nsmounter
2023-10-05T22:31:12.430624262Z stderr F Mounting arguments: mount -t nfs -o vers=4.1,noresvport,intr,hard <IP_ADDRESS>:/pvc-254b9a67-3a84-4309-b591-b83bac9c4900 /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/3816fa16e001ad6c7497
b189d35ec998cc5b5416c8d37ba291636e1f9b007e0e/globalmount
2023-10-05T22:31:12.430627916Z stderr F Output: mount: /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/3816fa16e001ad6c7497b189d35ec998cc5b5416c8d37ba291636e1f9b007e0e/globalmount: mount point does not exist.
2023-10-05T22:31:12.430631264Z stderr F        dmesg(1) may have more information after failed mount system call.
2023-10-05T22:31:12.430634404Z stderr F
2023-10-05T22:31:12.430638136Z stderr F time="2023-10-05T22:31:12Z" level=error msg="NodeStageVolume: err: rpc error: code = Internal desc = mount failed: exit status 32\nMounting command: /usr/local/sbin/nsmounter\nMounting arguments: mount -t
nfs -o vers=4.1,noresvport,intr,hard <IP_ADDRESS>:/pvc-254b9a67-3a84-4309-b591-b83bac9c4900 /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/3816fa16e001ad6c7497b189d35ec998cc5b5416c8d37ba291636e1f9b007e0e/globalmount\nOutput: mo
unt: /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/3816fa16e001ad6c7497b189d35ec998cc5b5416c8d37ba291636e1f9b007e0e/globalmount: mount point does not exist.\n       dmesg(1) may have more information after failed mount system ca
ll.\n"
2023-10-05T22:31:44.524268282Z stderr F time="2023-10-05T22:31:44Z" level=info msg="NodeStageVolume: req: {"staging_target_path":"/var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/3816fa16e001ad6c7497b189d35ec998cc5b5416c8d37ba29
1636e1f9b007e0e/globalmount","volume_capability":{"AccessType":{"Mount":{"fs_type":"ext4"}},"access_mode":{"mode":5}},"volume_context":{"dataLocality":"disabled","fromBackup":"","fsType":"ext4","numberOfReplicas":
"3","share":"true","staleReplicaTimeout":"30","storage.kubernetes.io/csiProvisionerIdentity":"1696544670946-8081-driver.longhorn.io"},"volume_id":"pvc-254b9a67-3a84-4309-b591-b83bac9c4900"}"
2023-10-05T22:31:44.596301336Z stderr F time="2023-10-05T22:31:44Z" level=debug msg="trying to ensure mount point /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/3816fa16e001ad6c7497b189d35ec998cc5b5416c8d37ba291636e1f9b007e0e/glo
balmount"
2023-10-05T22:31:44.604248958Z stderr F time="2023-10-05T22:31:44Z" level=debug msg="mount point /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/3816fa16e001ad6c7497b189d35ec998cc5b5416c8d37ba291636e1f9b007e0e/globalmount try read
ing dir to make sure it's healthy"

I think I face the same or somehow similar issue.
I'm using https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner to setup K8s on Hetzner based on MicroOS and a custom installed Longhorn (1.5.1 and 1.4.2), I'm facing this issue in multiple clusters since today.
I see this error message in the system journal:
Oct 11 07:42:23 dev-worker-1 k3s[1294]: Mounting command: /usr/local/sbin/nsmounter
Oct 11 07:42:23 dev-worker-1 k3s[1294]: Mounting arguments: mount -t nfs -o vers=4.1,noresvport,intr,hard <IP_ADDRESS>:/pvc-13538170-4278-4467-b2b0-1f1ba6f54a4c /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/185c34f566c2eca6e8c7c6a2ede2094c076d7d25ddae286dc633eeef80551af0/globalmount
Oct 11 07:42:23 dev-worker-1-autoscaled-small-19baf778f50efd8c k3s[1294]: Output: mount.nfs: Protocol not supported for <IP_ADDRESS>:/pvc-13538170-4278-4467-b2b0-1f1ba6f54a4c on /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/185c34f566c2eca6e8c7c6a2ede2094c076d7d25ddae286dc633eeef80551af0/globalmount

Any help or suggestion is appreciated!

@janosmiko
mount.nfs: Protocol not supported for ...
Does your OS support nfs v4.1?

Well, it definitely should as it worked 1-2 days ago.
Tried to manually run the command using strace, but nothing interesting:
strace -fe mount mount -t nfs -o vers=4.1,noresvport,intr,hard <IP_ADDRESS>:/pvc-35f9342e-2c29-4858-944e-e30410105151 /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/bde63d3d40aa181876e33213ba79359708f2dbfcb84a3e8c09bb30bd56097da3/globalmount
strace: Process 8997 attached
[pid  8997] mount("<IP_ADDRESS>:/pvc-35f9342e-2c29-4858-944e-e30410105151", "/var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/bde63d3d40aa181876e33213ba79359708f2dbfcb84a3e8c09bb30bd56097da3/globalmount", "nfs", 0, "vers=4.1,noresvport,intr,hard,ad"...) = -1 EPROTONOSUPPORT (Protocol not supported)
mount.nfs: Protocol not supported for <IP_ADDRESS>:/pvc-35f9342e-2c29-4858-944e-e30410105151 on /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/bde63d3d40aa181876e33213ba79359708f2dbfcb84a3e8c09bb30bd56097da3/globalmount
[pid  8997] +++ exited with 32 +++
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=8997, si_uid=0, si_status=32, si_utime=0, si_stime=1 /* 0.01 s */} ---
+++ exited with 32 +++

I also enabled nfs debug logging and I see these in the logs:
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs: Deprecated parameter 'intr'
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: --> nfs4_try_get_tree()
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs_create_rpc_client: cannot create RPC client. Error = -22
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs_callback_create_svc: service created
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: NFS: create per-net callback data; net=f0000000
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs_callback_up: service started
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: NFS: nfs4_discover_server_trunking: testing '<IP_ADDRESS>'
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: --> nfs4_proc_create_session clp=000000005e8f4e16 session=00000000895338ef
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs4_init_channel_attrs: Fore Channel : max_rqst_sz=1049620 max_resp_sz=1049480 max_ops=8 max_reqs=64
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs4_init_channel_attrs: Back Channel : max_rqst_sz=4096 max_resp_sz=4096 max_resp_sz_cached=0 max_ops=2 max_reqs=16
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: --> nfs4_setup_session_slot_tables
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: --> nfs4_realloc_slot_table: max_reqs=64, tbl->max_slots 0
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs4_realloc_slot_table: tbl=000000004f77f636 slots=00000000bb02e718 max_slots=64
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: <-- nfs4_realloc_slot_table: return 0
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: --> nfs4_realloc_slot_table: max_reqs=16, tbl->max_slots 0
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs4_realloc_slot_table: tbl=00000000b66c7bf8 slots=000000000e277bfb max_slots=16
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: <-- nfs4_realloc_slot_table: return 0
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: slot table setup returned 0
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs4_proc_create_session client>seqid 2 sessionid 1081:1696637954:541:0
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs4_schedule_state_renewal: requeueing work. Lease period = 5
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: --> nfs4_alloc_slot used_slots=0000 highest_used=4294967295 max_slots=64
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: <-- nfs4_alloc_slot used_slots=0001 highest_used=0 slotid=0
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: encode_sequence: sessionid=1081:1696637954:541:0 seqid=1 slotid=0 max_slotid=0 cache_this=0
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: NFS: nfs4_discover_server_trunking: status = 0
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: --> nfs4_alloc_slot used_slots=0001 highest_used=0 max_slots=64
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: <-- nfs4_alloc_slot used_slots=0003 highest_used=1 slotid=1
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs4_free_slot: slotid 1 highest_used_slotid 0
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs41_sequence_process: Error 0 free the slot
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs4_free_slot: slotid 0 highest_used_slotid<PHONE_NUMBER>
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: <-- nfs41_proc_reclaim_complete status=0
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: --> nfs4_alloc_slot used_slots=0000 highest_used=4294967295 max_slots=16
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: <-- nfs4_alloc_slot used_slots=0001 highest_used=0 slotid=0
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs4_free_slot: slotid 0 highest_used_slotid<PHONE_NUMBER>
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: --> nfs4_alloc_slot used_slots=0000 highest_used=4294967295 max_slots=64
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: <-- nfs4_alloc_slot used_slots=0001 highest_used=0 slotid=0
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs4_free_slot: slotid 0 highest_used_slotid<PHONE_NUMBER>
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs4_destroy_session Destroy backchannel for xprt 00000000cd398012
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: NFS: destroy per-net callback data; net=f0000000
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: nfs_callback_down: service destroyed
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: NFS4: Couldn't follow remote path
Oct 11 19:16:34 worker-autoscaled-medium-47604670eec959dc kernel: <-- nfs4_try_get_tree() = -93 [error]

I did a rollback to the previous version of OpenSUSE MicroOS and it seems like it's working now, so I assume something is wrong with their current version of nfs-client (possibly).

We ran into the similar issue before.
https://longhorn.io/kb/troubleshooting-failed-rwx-mount-due-to-connection-timeout/
Can you please check if it is related to you case?

I have the same problem since yesterday, using MicroOS. Also fixed it with a snapper rollback. The problematic version is:
NAME="openSUSE MicroOS"
# VERSION="20231010"
ID="opensuse-microos"
ID_LIKE="suse opensuse opensuse-tumbleweed"
VERSION_ID="20231010"
PRETTY_NAME="openSUSE MicroOS"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:microos:20231010"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:MicroOS"
LOGO="distributor-logo-MicroOS"

> cat /boot/config-`uname -r`| grep CONFIG_NFS_
CONFIG_NFS_FS=m
CONFIG_NFS_V2=m
CONFIG_NFS_V3=m
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=m
CONFIG_NFS_SWAP=y
CONFIG_NFS_V4_1=y
CONFIG_NFS_V4_2=y
CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN="kernel.org"
# CONFIG_NFS_V4_1_MIGRATION is not set
CONFIG_NFS_V4_SECURITY_LABEL=y
CONFIG_NFS_FSCACHE=y
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
CONFIG_NFS_DEBUG=y
# CONFIG_NFS_DISABLE_UDP_SUPPORT is not set
# CONFIG_NFS_V4_2_READ_PLUS is not set
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_NFS_V4_2_SSC_HELPER=y

cc @longhorn/qa

This can be related:
https://bugzilla.opensuse.org/show_bug.cgi?id=1214540

@janosmiko @primeXchange
CONFIG_NFS_V4=m

Did you check if the nfsv4 kernel module is loaded by lsmod?

It was not loaded previously, but even after loading it, it fails:
worker-autoscaled-medium-47604670eec959dc:~ # lsmod | grep nfs
worker-autoscaled-medium-47604670eec959dc:~ # modprobe nfs
worker-autoscaled-medium-47604670eec959dc:~ # modprobe nfsv4
worker-autoscaled-medium-47604670eec959dc:~ # lsmod | grep nfs
nfsv4                1241088  0
dns_resolver           16384  1 nfsv4
nfs                   634880  1 nfsv4
lockd                 184320  1 nfs
sunrpc                892928  3 nfsv4,lockd,nfs
fscache               405504  1 nfs
netfs                  69632  2 fscache,nfs

Oct 12 07:29:02 worker-autoscaled-medium-47604670eec959dc k3s[1291]: Mounting arguments: mount -t nfs -o vers=4.1,noresvport,intr,hard <IP_ADDRESS>:/pvc-35f9342e-2c29-4858-944e-e30410105151 /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/bde63d3d40aa181876e33213ba79359708f2dbfcb84a3e8c09bb30bd56097da3/globalmount
Oct 12 07:29:02 worker-autoscaled-medium-47604670eec959dc k3s[1291]: Output: mount.nfs: Protocol not supported for <IP_ADDRESS>:/pvc-35f9342e-2c29-4858-944e-e30410105151 on /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/bde63d3d40aa181876e33213ba79359708f2dbfcb84a3e8c09bb30bd56097da3/globalmount
^C

For those facing this issue, here's a (rollback)solution that worked for me:

Connect to the affected machine via SSH:

ssh -i ~/.ssh/<your_private_key> root@<machine-ip>

Once connected, list the snapshots to identify the previous version:
sudo snapper list
Roll back to the desired previous version:
sudo snapper rollback <previous_version>
Reboot the machine
sudo reboot

After some time, all the volumes should be attached again.
Thanks to @janosmiko for highlighting this issue.

@janosmiko @primeXchange @andrewd-zededa @mahmuzicamel  Thanks for raising the issue.
It looks like an environment issue (OS) issue.
We will check any workaround in Longhorn side for it.

Hi @derekbit,
Thanks for your help. Are you in contact with the OpenSUSE Tumbleweed team? We should let them know somehow these infos.

I reported it here:
https://bugzilla.opensuse.org/show_bug.cgi?id=1216201

@janosmiko @mahmuzicamel @primeXchange
Do you know which MircoOS version is OK in your env? Will check the changes in the MicroOS as well.

All versions prior to 2023-10-10

@rome-user
Can you provide a uname -a as well? Thank you.

@rome-user
The issue in OpenSUSE MicroOS's kernel starts from v20231010. The kernel is also upgraded from v6.5.4 to v6.5.6 since then.
I'm checking the changes in the kernel side and the utility side.

@derekbit I tried to downgrade the kernel and restarted the nodes but the issue still persist.
See here:
https://bugzilla.opensuse.org/show_bug.cgi?id=1216201

@janosmiko
Let's clarify your findings.

Use microOS v20231010 and pin 2.6.3-39.4 -> works
Use microOS v20231010 and pin 2.6.3-39.4, but downgrand linux kernel -> not work

Are they correct?

@derekbit ,
I just verified it again, and looks like downgrading the kernel solved the issue finally. 🎉
(Maybe the node where the nfs-server run was still not restarted.)
What I previously tested:

it worked for me when I downgraded MicroOS to a snapshot before 20231010. Eg 20231008.
it did not work when I just downgraded the nfs-client package and I was on a newer MicroOS then 20231010.

We faced the same issue. Thanks all the hints everyone.

6.5.6-1-default not working
Rolling back to a snapshot before 10 Oct, all functionality was restored. We're on 6.5.4-1-default now.

@janosmiko Thank you for the clarification.
The issue looks like a kernel issue and is checked by @neilbrown currently according to the bugzilla ticket.
Hello @neilbrown please let me know if anything I can help in the client side. Thank you,
In addition, we will prepare a knowledge base doc for the workaround.
cc @innobead

@derekbit  One thing that would probably help a lot is a network packet capture for both the work case and the failing case.  Even just one of those might be enough.
Use "tcpdump -w SOMEFILE -s 0 port 2049" on the client.  The "-s 0" is important.
There aren't many changes affecting NFS between 6.5.5 and 6.5.6.  The two that seem most likely to me are:
d1db10f1918d NFSv4.1: fix pnfs MDS=DS session trunking
0317d19e26e3 NFSv4.1: use EXCHGID4_FLAG_USE_PNFS_DS for DS server
as they relate to establishing the state of the server when the filesystem is being mounted.

Hi @neilbrown
I created a tcpdump for you, I hope this helps:
test.txt

Thanks for the tcpdump.  It did help.
I believe the bug is fixed by
<EMAIL_ADDRESS>which was posted about a week ago.
It doesn't seem to have been picked up by the nfs maintainers yet so it might be a few weeks before it lands in upstream-stable.
I have submitted to the SUSE stable kernel which feeds into tumbleweed, so the next kernel released for tumbleweed should have it.  Until then (which will have a 6.5.7 number (or later)) I suggest using the 6.5.5 kernel.

@neilbrown is it possible to downgrade the kernel for ARM architecture servers?
It can be downgraded from this url for amd64:
http://download.opensuse.org/history/20231008/tumbleweed/repo/oss/x86_64/kernel-default-6.5.4-1.1.x86_64.rpm
But I cannot find a repository archive for arm on the download.opensuse.org. :(

@janosmiko I cannot find any AARCH64 history either.
Hopefully the fixed kernel will appear in
https://download.opensuse.org/repositories/Kernel:/stable/ARM/aarch64/
sometime soon.
kernel-default-6.5.7-2.1.g9fcbf99.aarch64.rpm does NOT have the fix. Anything new should do.

Hi @derekbit my issue seems to be unrelated to the OpenSUSE MicroOS 'protocol not supported' others are seeing.  I see a 'mount point does not exist.' for the first pod to attempt mounting the rwx volume.  If I manually create the target mount point and mount the nfs share then the pod completes startup and writes to the rwx volume.
Would it be possible to move the 'protocol not supported' talk to a separate issue?

MicroOS's kernel is updated to 6.5.8 since 20231022 (refhttp://twsnapshot.opensuse.org/tumbleweed/iso/Changes.MicroOS.20231022.txt).
@andrewd-zededa
Sure. Can you provide a support bundle? Thank you.

fedora coreos is also affected in the latest release:
Fedora CoreOS 38.20231014.3.0   6.5.6-200.fc38.x86_64
rollback to the prev. version and disabling autoupdates solves the issus
Fedora CoreOS 38.20231002.3.1   6.5.5-200.fc38.x86_64

supportbundle_f040e893-28c7-41b6-afac-df4338e98a0e_2023-11-08T00-14-22Z.zip
@derekbit Thanks, bundle attached.

@ChanYiLin please follow up this.
cc @derekbit

I can confirm this issue persists with current fedora coreos version:
Fedora CoreOS 38.20231027.3.2 6.5.8-200.fc38.x86_64

@Teslamancer
Has the nfs client been installed on each Longhorn node?
https://longhorn.io/docs/1.5.3/deploy/install/#installing-nfsv4-client

Update to Fedora CoreOS 39.20231119.3.0   6.5.11-300.fc39.x86_64 solved the problem in my setup (v1.27.6+k3s1)

@andrewd-zededa @Teslamancer
Has the nfs client been installed on each Longhorn node? https://longhorn.io/docs/1.5.3/deploy/install/#installing-nfsv4-client

Thanks for pointing this out!
One of nodes on my cluster was causing the same behavior - I simply didn't install nfs package on it.

@andrewd-zededa @Teslamancer
Has the nfs client been installed on each Longhorn node? https://longhorn.io/docs/1.5.3/deploy/install/#installing-nfsv4-client

It turned out that updating to Fedora CoreOS 39+ solved the issue for me

I figured out my issue is due to the mount being completed in the wrong mount namespace (pid 1).  I have a patch ready to resolve my issue which I'll submit soon.

For anyone coming across this running on Ubuntu 22.04 LTS (Jammy Jellyfish), we have had this occur after an upgrade to the 5.15.0-94 kernel.
After rolling back to 5.15.0-92 our RWX volumes mount fine again on the affected cluster.

For anyone coming across this running on Ubuntu 22.04 LTS (Jammy Jellyfish), we have had this occur after an upgrade to the 5.15.0-94 kernel.
After rolling back to 5.15.0-92 our RWX volumes mount fine again on the affected cluster.

Seems to be the issue here as well. One of my nodes which does not have latest kernel does not have this problem. Thanks for the heads up

For anyone coming across this running on Ubuntu 22.04 LTS (Jammy Jellyfish), we have had this occur after an upgrade to the 5.15.0-94 kernel.
After rolling back to 5.15.0-92 our RWX volumes mount fine again on the affected cluster.

Yep. I've got the same issue currently. After 195 days of no issues, suddenly it updated and stopped working... Fun.

@james-munson Let's make sure our doc has this notice. Besides doc, also helps improve our preflight check script to give users a warning about that.

It may be https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689
So theoretically a kernel upgrade should fix it

https://longhorn.io/kb/troubleshooting-rwx-volume-fails-to-attached-caused-by-protocol-not-supported/ is about a different kernel version, maybe it should note 5.15.0-94

https://longhorn.io/kb/troubleshooting-rwx-volume-fails-to-attached-caused-by-protocol-not-supported/ is about a different kernel version, maybe it should note 5.15.0-94

We found the issue in kernel 6.5.6 before and wrote the KB doc. Sure, we will add 5.15.0-94 in it as well.

With https://github.com/longhorn/longhorn/issues/7931 in Review, I think this issue can be closed.

Hello,
Since I'm new to all of this, could you kindly clarify if upgrading/downgrading the kernel version is the sole solution to address the problem?
I'm facing this issue on 2 OS:

OpenSUSE Leap 15.4
Ubuntu 22.04.

Hello, Since I'm new to all of this, could you kindly clarify if upgrading/downgrading the kernel version is the sole solution to address the problem? I'm facing this issue on 2 OS:

OpenSUSE Leap 15.4
Ubuntu 22.04.

Please see https://longhorn.io/kb/troubleshooting-rwx-volume-fails-to-attached-caused-by-protocol-not-supported/ and related infromation.

Hi 👋
I'm having the same issue with kernel 6.5.0-21-generic on Ubuntu Server 22.04.4 LTS although this kernel isn't mentioned in the article mentioned above 🤔

Hi 👋
I'm having the same issue with kernel 6.5.0-21-generic on Ubuntu Server 22.04.4 LTS although this kernel isn't mentioned in the article mentioned above 🤔

Unfortunately, 6.5.0-21-generic of ubuntu hits the same issue.
We suggest the customer downgrade the kernel version to an older one.
git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-lowlatency-hwe-6.5-6.5.0-21.21.1_22.04.1&id=57fe583f2235eda86c66b74d121fe9ccd0dce5c6

@derekbit its the same problem i reported on  #8018 !
kernel version: <IP_ADDRESS>
ubuntu 20.04

@derekbit thanks for the super quick answer 🙌
I've tried upgrading to kernel v6.5.7 as per the article, as it was easier tu upgrade to a newer version, but it causes the same issue.

I'll try downgrading so.

@vincentkelleher  the problem occurs when you restart the nodes ? or suddenly occurs ?

@Siradjedd my home lab cluster (not critical at the moment) has been down for two days now as an apt upgrade caused the kernel to bump up a few patch versions.
The issue occurred after rebooting the nodes, I knew there was a bigger problem because I didn't touch anything related to Longhorn, storage, file system or hardware.

Before downgrading, I decided to upgrade my kernel to the latest version (v6.7.6) and things are working fine now 👍
I used the Mainline upgrade tool to do so.

@vincentkelleher  even if you restart the node again, won't cause a problem ?


Send actual hostname in SMTP Hello

Sending "localhost" in the SMTP Hello can trip some spam filters that expect the Hello hostname to be a valid FQDN.
Note: I don't have a Go development environment set up, so this change is untested.
It seems simple enough, but perhaps someone could run a quick test to see if it runs alright.

util.Hostname will usually be something like "web01" or whatever. Wouldn't the same filters have issues with non-fully-qualified names. May be better to use the hostname as configured in bosun's hostname parameter


chore: add backend tests to CI

:tada: This PR is included in version 1.10.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Thank you!!

This is an amazing project, I am not very good at frameworks and this projects lets me create cool start app with just few lines!, Excellent!

Thank you for your kindly words @rizplate. I don't have too much time lately to move forward with the issues but it's really nice to hear good experiences from time to time, gives me a kind of refill-feeling :)


Bug Report - Control panel button shows incorrectly

Environment
Windows build number: 10.0.18362.175
Windows Terminal version (if applicable): Dev Build

Steps to reproduce
just launch the application
Expected behavior
It should be default control buttons.
Actual behavior
The minimize and the Maximize button didn't show correctly it show like a small corrupted buttons.
(I don't know that is this an UI or a bug, and sorry for my English I'm Thai.)

@DHowett-MSFT has been working on it. Try build the branch dev>duhowett>minmaxcloseme

Thank you.


feat(fxmetrics): Provided module

Codecov Report
Attention: 5 lines in your changes are missing coverage. Please review.

Comparison is base (61ae829) 96.63% compared to head (892b62c) 97.51%.

Files
Patch %
Lines

fxmetrics/testdata/spy/spy.go
68.75%
5 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #32      +/-   ##
==========================================
+ Coverage   96.63%   97.51%   +0.87%
==========================================
  Files          81       10      -71
  Lines        2170      201    -1969
==========================================
- Hits         2097      196    -1901
+ Misses         53        5      -48
+ Partials       20        0      -20

Flag
Coverage Δ

config
?

fxconfig
?

fxgenerate
?

fxlog
?

fxmetrics
97.51% <92.30%> (?)

fxtrace
?

generate
?

healthcheck
?

httpclient
?

httpserver
?

log
?

orm
?

trace
?

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

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


[Discussion] Unify GitSource CRD &  PiplelineResource of type Git

Hi,
I'm Shoubhik from the OpenShift Developer Console team.
The DevConsole operator team is using a CRD called GitSource which represents a Git repo. Here's how it looks like
https://github.com/redhat-developer/devconsole-operator/blob/master/deploy/crds/devconsole_v1alpha1_gitsource_crd.yaml
apiVersion: devconsole.openshift.io/v1alpha1
kind: GitSource
metadata:
  name: example-gitsource
spec:
  url: "https://github.com/sclorg/nodejs-ex"
  ref: master
  contextDir: /cmd/manager
  httpProxy: http://proxy.example.com
  httpsProxy: https://proxy.example.com
  noProxy: somedomain.com, otherdomain.com
  secretRef:
    name: mysecret
  flavor: github

We use this for in our suite of CRDs which also consists of Component CRD and GitSourceAnalysis CRD. The GitSource CRD has a controller which verifies the Git 'connection' for the repository and writes an assertive/negative to the status field.
The structure/spec has been inspired from the BuildConfig type and the reason we went for a new CRD altogether is because we wanted to store Git Source information in a way that we are able to use this outside the context of BuildConfig as well. Example, a user can import an application in OpenShift Developer Console and then launch it in Che in which case we could use the GitSource belonging to the associated app Component in Che for cloning code into Che ( and other Che to Git operations )
I feel the goal of PipelineResource of type 'git' and GitSource is similar - and should try unifying the effort :)
Let me know your thoughts!

( edited the CRD type :) )

Thanks for opening this! Would you be interested in coming to one of the upcoming Tekton weekly calls to discuss some goals/ideas for unifying? I wholeheartedly agree with the idea of fewer CRDs :)

Sure, I would love to, @dlorenc .

Nice, I've added this to the agenda @sbose78 ! And here's the info on our working group meeting just in case you hadn't seen it yet. Talk to you soon!

Sorry, will add this to my calendar and join the next one!

@sbose78 is this something you're still interested in ? (Note that in #1673 we're redesigning PipelineResources)

Gonna close this for now, please re-open if still interested!

Sounds good, @bobcatfish !


How to init spring-cloud-zookeeper-config properties

Question
I have multiple spring boot applications, and I put the properties in application-{profile} file in project. Now I'm trying to use zookeeper as spring cloud config center, what's the best practice to migrate those properties to zookeeper please? I really don't want to add it manually since there are tons of configurations! Thanks in advance

I've raised same question on StackOverflow but got no answer yet, hope someone can help here.

You can make a tool  for solving this problem.

You can make a tool for solving this problem.

Thanks for the comment.
I just not sure if there is already such kind of open source tool, so that I don't need to do duplicate work:-).


Support Aggregate Engines

Is your feature request related to a problem? Please describe.
The UIMA framework has engines composed by primitive engines (annotators) or aggregate engines. At present, the C++ version of the framework cannot handle aggregate engines, only primitives.
An example of a primitive annotator descriptor is the SimpleTextSegmenter.xml. It refers to the annotator itself, SimpleTextSegmenter.cpp.
The aggregate descriptors are discussed in the Apache UIMA Reference. An example descriptor from the Java framework is the NamesAndGovernmentOfficials_TAE.xml.
The Java UIMA aggregate analysis engine implementation involves the class AggregateAnalysisEngine_impl.java and many others.
Describe the solution you'd like
The UIMACPP framework should be able to load and execute Aggregate Engines in XML format composed of other aggregate engines or primitive engines implemented in C++.
This includes parsing the XML descriptors and routing the annotations (as part of the Common Annotation Structure, or CAS) from the different annotators. Note that that aggregators shield annotators based on the input and output annotations present in their descriptors.
Describe alternatives you've considered
Using UIMA-AS it was possible to interoperate between Java and C++, but the UIMA-AS framework has been retired.
Additional context
This has been discussed as one of the main roadblocks in using the C++ version of the framework by its users: https://lists.apache.org/thread/f1r3sghgn2oqhvzz27y26zg6j3olv8qq
Tasks

[ ] Initial classes for aggregate descriptors.
[ ] Parse and validate aggregate descriptor XML files.
[ ] Text cases for base aggregate functionality.
[ ] Base aggregate execution functionality.
[ ] Flow controller (optional/undecided for this issue, might file another in the future).
[ ] SofA mappers (optional/undecided for this issue, might file another in the future).

@DrDub Hi, Would like to work on this issue!!

Hi @ShaiviAgarwal2, do you mind checking whether the instructions in the new readme at #15 work? I'd really appreciate it.
Also, if you're considering applying to the GSoC please send me an email to<EMAIL_ADDRESS>to further discuss.

Hi @ShaiviAgarwal2, do you mind checking whether the instructions in the new readme at #15 work? I'd really appreciate it.
Also, if you're considering applying to the GSoC please send me an email to<EMAIL_ADDRESS>to further discuss.

Sent you the mail

Hi @ShaiviAgarwal2, do you mind checking whether the instructions in the new readme at #15 work? I'd really appreciate it.
Also, if you're considering applying to the GSoC please send me an email to<EMAIL_ADDRESS>to further discuss.

@DrDub I checked the instructions mentioned by you in the new readme at #15. It works fine :)

Hi, I'll be working on this issue

We have identified what has been already been implemented (in internal_aggregate_engine.cpp, annotator_mgr.cpp and related) as well as what's currently missing (eg. when a delegate is a CAS Multiplier the CASIter for Aggregates does not return children CASes).
I will create test cases to examine the capabilities of the XML Parser to see if it conforms to the entire spec and then move on to the Aggregate Engine functionalities.


Use smaller dataset

Issue for app: #333
App pull request

[ ] This is a new app
[x] I am improving an existing app (redesigns/code "makeovers")

Specifying 2 in the prompt allows us to download the 10K dataset instead of the default 7M dataset.

@cldougl Please review.. As discussed, I have updated the omnisci deployment to use "10K" dataset instead of "7M".
I have also increased resources on cluster (RAM increased from 4GB to 16GB) which should help with the performance.

cc: @ycaokris .. !!

@tarzzz I've approved the pr already but 💃 if you were waiting

I was waiting for Kris actually:

but it seems that is not required.. Merging..


How to convert one request to curl cmd?

Hi, guys, could I convert one request to curl cmd with ChromeRestClient? I've try to find it but can't. Could anybody help me with this?

Hi,
Thank you for the issue report.
The command and code generation is not yet supported. It is a planned feature.


EntityBase “requestSpeedChangeWithConstantAcceleration” and “requestSpeedChange” sometimes will not throw an error

Description
Location: enetity_base.cpp: 305, 394, 457
Function isTargetSpeedReached throws an error from speed_change.cpp:47 if it is provided with an invalid entity name in the speed_change::RelativeTargetSpeed argument.
There are several places in requestSpeedChange functions where isTargetSpeedReached is invoked if-and-only-if continuous == false (early return). This means that an invalid speed_change::RelativeTargetSpeed argument will sometimes result in an error immediately, but sometimes will not.
Note that the error will be thrown eventually anyway (might remove this, as it is not technically an issue).
Solution
This could be changed by inverting the order of statements in the if (!continuous && isTargetSpeedReached(target_speed)) statement. However as noted above, this is only a suggestion and can be removed.

Invalid operation should not be permitted, so if the speed_change::RelativeTargetSpeed called with invalid name, it should throw exception.


Create stedelijkgymnijmegen.txt

This seems to be a secondary school; this database is for higher education (post-secondary) institutions. Closing.


Unable to Install on MacOS 10.15.7

When installing with the Mac Intel installer, it fails with exit code 2
When opening the GlamorousToolkit.app through command line open ~/Downloads/GlamorousToolkit-MacOS-x86_64-v0.8.2092/GlamorousToolkit.app
It failed with
LSOpenURLsWithRole() failed with error -10810 for the file /Users/cheung/Downloads/GlamorousToolkit-MacOS-x86_64-v0.8.2092/GlamorousToolkit.app.

When installing through command line curl https://dl.feenk.com/scripts/mac.sh | bash
It failed at the 🔨 Building Glamorous Toolkit... stage with message
Error: Command "/Users/cheung/Downloads/glamoroustoolkit/GlamorousToolkit.app/Contents/MacOS/GlamorousToolkit-cli" "/Users/cheung/Downloads/glamoroustoolkit/GlamorousToolkit.image" "st" "--quit" "--save" "" "load-gt-main.st" failed. See install.log or install-errors.log for more info

In the install.log, the message is
I got an error while cloning: There was an authentication error while trying to execute the operation: .
This happens usually because you didn't provide a valid set of credentials.
You may fix this problem in different ways:
1. adding your keys to ssh-agent, executing ssh-add ~/.ssh/id_rsa in your command line.
2. adding your keys in settings (open settings browser search for "Use custom SSH keys" and
add your public and private keys).
3. using HTTPS instead SSH (Just use an url in the form HTTPS://etc.git). I will try to clone the HTTPS variant.

Please advice what format I shall use in reporting issue and what additional information I can provide.
Appreciate your help.
Thank you

Hi
You can not install and run applications in Downloads. That is a (well-known/hated) MacOS feature. They are sandboxed.

One other possibility is that GitHub throttles https connections, so I've found that when building GT from the curl script, I get  failures sometimes if I've forgotten to use ssh-add to add my credentials (so it can use authenticated connections)

That one I've figured out on my own (since I always forget to run ssh-add after a reboot.

Hi
You can not install and run applications in Downloads. That is a (well-known/hated) MacOS feature. They are sandboxed.

Thanks for the pointer. As I am getting a taste of the smalltalk ecosystem, I had installed the pharo launcher from the Downloads directory without any problem earlier today.
Anyway, I moved the installer to other directories and it solved the problem. Thank you again for taking the time to look into this issue! I'm closing this issue and consider it resolved.


There is an arbitrary file upload vulnerability

版本号：
2.3
问题描述：
After testing, it is found that there is an arbitrary file upload vulnerability in the image upload function of "custom component" of jeecg boot, and the interface is /jeecg-boot/sys/common/upload
截图&代码：
Reuse https://github.com/zhangdaiscott/jeecg-boot After the source code of the project is started, click "custom component" and grab the package to get the interface with arbitrary file upload vulnerability

Modify the upload suffix name and upload content through packet capture

The vulnerability code exists in the following code:\jeecg-boot\jeecg-boot-base-common\src\main\java\org\jeecg\common\system\controller\CommonController.java At line 76 of

友情提示： 未按格式要求发帖，会直接删掉。

具體的功能驗證細節可以自行修改，這個上傳也僅僅是個實例

上传到什么目录可以解析？


Openvr109

First and incomplete pass at upgrading to OpenVR SDK 1.0.9. looking for pointers and feedback. These commits build for me and allow the use of the latest stable steamvr lighthouse drivers.

@krakrjak ,
I'm closing this PR because #37 updates the repo to 1.0.11 version.
Thanks for your contribution to OSVR!


Need a way to update Console's Callback & Allowed Origins

Is your suggestion related to an experience ? Please describe.

ATM, the API restricts any updates to the api/server/v1/applications/<ID>/inbound-protocols/oidc endpoint with PUT  operations for Console application since it's treated as a system application by default.
Describe the improvement

We need to allow this since it's needed if a user wants to externalize the Console.
Proposed UI

Additional context

A similar improvement was done to allow the update of Authentication Sequence of Console. (https://github.com/wso2/identity-api-server/pull/536/files)

@UdeshAthukorala FE PR is merged: https://github.com/wso2/identity-apps/pull/4842
And the tab is disabled. Please enable after BE PRs are merged.

Changing the priority level as this is a blocker for Asgardeo

The UI implementation is already merged to the Console and is hidden from the UI for now until the API is merged.
@malithie Should we keep it hidden and document to use the API for updating these URLs?

Is this a tenat wide config ? Is that why we have an API ?
Or this API is not tenant level but server level ?

Is this a tenat wide config ? Is that why we have an API ? Or this API is not tenant level but server level ?

Hi @malithie ,
With this improvement we can change console application's callBack URLs and allowed origins, from this updateInboundOAuthConfiguration API[1]. Since this is a tenanted API we can change it tenant wise.
[1] https://is.docs.wso2.com/en/latest/apis/application-rest-api/#/Inbound Protocols - OAuth %2F OIDC/updateInboundOAuthConfiguration

IMO, this is a server level requirement. Externalizing the console is not a requirement from the Identity Server perspective but from Asgardeo perspective.
And there's no requirement anyway to have this tenant wise.
@darshanasbg what's your view on this

IMO, this is a server level requirement. Externalizing the console is not a requirement from the Identity Server perspective but from Asgardeo perspective. And there's no requirement anyway to have this tenant wise. @darshanasbg what's your view on this

Yes, externalizing the console, don't needed to be a tenant wise option. Having server level config should be enough.

Hi all,
Previous Tenant wise api improvement to upodate console application's callbaclk urls & allowed orgins willl be reverted with the below PRs.

https://github.com/wso2/identity-api-server/pull/556
https://github.com/wso2/identity-apps/pull/5015

After having a further discussions with the team we have decided to introduce a new toml config as a server level to update console & myacount callback urls.
For update allowed orgins we can use the existing cors configuration toml config. SO no need to have a seperate improvement for this.

This will be fixed with:

https://github.com/wso2/carbon-identity-framework/pull/5304
https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/2301

Introduced a toml config to update console & myaccount callback url & access urls
New Toml Configs
[console]
callback_url = "https://localhost:9001/t/{TENANT_DOMAIN}/console"
access_url = "https://localhost:9001/t/{TENANT_DOMAIN}/console"

[myaccount]
callback_url = "https://localhost:9000/t/{TENANT_DOMAIN}/myaccount"
access_url = "https://localhost:9000/t/{TENANT_DOMAIN}/myaccount"


after migration not able to run this on localhost

how to run after truffle migrations
i see  everything blank in   a browser

Hi,
This is very old project many people tried but it doesn't work now because
of many changes into versions and syntax and many rules etc
Sorry for the late reply
Thanks for taking interest in our project
On Sun, Sep 11, 2022, 6:03 PM thexahmed00 @.***> wrote:

how to run after truffle migrations
i see everything blank in a browser
—
Reply to this email directly, view it on GitHub
https://github.com/rsd511/HealthBuddy-DApp/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI25L3M3NXIPKNBA2KY3QY3V5XGTLANCNFSM6AAAAAAQJYLEJM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Ensure good compatability with InkStitch

Inkstitch Thread:

rgb int
name string
number string or int (should string as manufacturer numbers sometimes have relevant leading zeros, and charaters)
manufacturer (string) -- This is brand.

This is a subset so it's fine.
Inkstitch StitchPlan

Contains list of colorblocks

Inkstitch ColorBlock:

Holds a set of stitches, all with the same thread color.
self.color = color
self.stitches = stitches or []

Inkstitch Stitch:

self.x = x
self.y = y
self.color = color
self.jump = jump
self.trim = trim
self.stop = stop
self.color_change = color_change
self.no_ties = no_ties

Inkstitch Patch:

"A raw collection of stitches with attached instructions."
self.color = color
self.stitches = stitches or []
self.trim_after = trim_after
self.stop_after = stop_after
self.stitch_as_is = stitch_as_is

Some of this is arranging code to feed into libembroidery. Very little does actual work.
def write_embroidery_file(file_path, stitch_plan, svg):
    origin = get_origin(svg)

    pattern = libembroidery.embPattern_create()

    for color_block in stitch_plan:
        add_thread(pattern, make_thread(color_block.color))

        for stitch in color_block:
            if stitch.stop:
                # This is the start of the extra color block added by the
                # "STOP after" handler (see stitch_plan/stop.py).  Assign it
                # the same color.
                add_thread(pattern, make_thread(color_block.color))

            flags = get_flags(stitch)
            libembroidery.embPattern_addStitchAbs(pattern, stitch.x - origin.x, stitch.y - origin.y, flags, 1)

    libembroidery.embPattern_addStitchAbs(pattern, stitch.x - origin.x, stitch.y - origin.y, libembroidery.END, 1)

    # convert from pixels to millimeters
    libembroidery.embPattern_scale(pattern, 1/PIXELS_PER_MM)

    # SVG and embroidery disagree on the direction of the Y axis
    libembroidery.embPattern_flipVertical(pattern)

    libembroidery.embPattern_write(pattern, file_path)

What's your highest level not doing actually work state? Is basically just data you could send to something like pyembroidery? I mean patches are easy to have pyembroidery take in a bunch of points and commands to stop_after, trim_after. It basically does that now flagged with EmbPattern.BREAK commands.

Well, as it stands now, it creates everything up to and including a sequence of stitches, jumps, stops, and trims.  When we were discussing pyembroidery originally, I hadn't really envisioned it taking over figuring out where to put jumps and trims and whatnot.
I understand where you're coming from, when you suggest that pyembroidery should handle lower level stuff like that, but I'm not convinced.  Users of Ink/Stitch are going to want me to continue adding features (e.g. frame-out) and I'd like the flexibility to implement that kind of stuff directly without waiting for code changes in pyembroidery.
I like the way libembroidery handles it now: it takes the low-level commands and writes them out in the chosen binary format.  It needs the addition of SEQUIN and STOP support, but other than that, the model seems good to me.  I'd like to avoid moving large swathes of functionality from Ink/Stitch into pyembroidery.

I can provide much lower level stuff too. But, without consistency of input they will get brittle. Some formats won't write properly if the commands aren't in the right order per se. And it only needs to handle some of the higher level stuff. At a minimum the same stuff libembroidery does with breaking the long stitches into smaller ones and breaking the long moves into smaller ones.
Things like frame_eject wouldn't really be needed, or flagging it to do the tie-on tie-off stuff.

Ah, I understand.  Yes, I definitely feel that pyembroidery is the best place to handle things like splitting stitches that are longer than 12.1mm, for example.
Tie-off is tough.  It'd be cool if I could just tell pyembroidery to tie off a given stitch.  But what would you have it do?  Right now, here's what Ink/Stitch does for a tie-off:

look back at the last few stitches and construct a path from them
do running stitch back along that path at 0.3mm per stitch for 2 stitches
do running stitch forward along that path to get to the original end point

It's important that the tie stitches are hidden inside the stitches that led up to that point, rather than just being in some random direction that potentially sticks off the side of the design.  My understanding is that just doing 3-5 stitches in place isn't good enough to tie off the thread.
Given that, I think Ink/Stitch is the place to handle the tie-offs (and tie-ins which use a similar algorithm), since it already has an algorithm for running stitch along a path.

You wouldn't have to use these functions. And could be made to simply send STOP, COLOR_CHANGE, JUMP, and STITCH commands directly, and should. But, it should also have higher level stuff like, BREAK or BREAK_COLOR which means generally trim this stitch, and jump to the location of the next stitch.
If there would be a need to do the lower level stuff, you could compose those yourself. But, the embroidery machines only can do so many things. They do stitch, move x y, turn on the sequin adaptor, stop, color_change, and fire laser, (the last one's not entirely a joke, some machines do laser cutting of applique).
Anything you can do is broken into those parts. So you need have access to that stuff, and if you aren't doing anything novel being able to simply send it bunch of stitches and a couple of commands like, we are now changing colors and going somewhere else, seems pretty reasonable. Especially with the lower level ones.

The tie-off and tie-on in pyembroidery, checks the previous stitch making sure it doesn't exceed the max-length allowed by the format, and stitches 33%, 66%, 33%, and within that last or first stitch.

It lays out 4 stitches hidden within the last stitch. But, only if requested. You could do whatever else you want and not invoke the feature in the encoder. It would then just stitch them as you requested them. But, if somebody who isn't you is doing something else, they might well want to add those tie-on and tie-off stitches and could request it. But, if you'd rather do that yourself it's entirely reasonable for you to do that. They are features not requirements.

At the low level, pyembroidery needs to do the same stuff libembroidery does.  But, at the higher level it needs to take in the stuff that people actually do and use and render them into something that absolutely will make sense to the binary format.
While you've already written some of that for inkstitch, other people might not. So it will need stuff like tie-down, or frame ejects, or the ability to feed it large blocks of points, and write that to disk. As well as loading a bunch of binary commands and turning that into large blocks of points, some elements of metadata, and thread objects.

I'm not trying to limit your ability to write in new features. I am wildly aware of the things embroidery machines can do and obviously giving you fine grain control is needed, but a lot of the time, it's just stitches to canvas. It stitches, that's basically all it does. Clearly it might need some other commands like slow or fast (ww mentions these exist in U?? format) that slow down the machine or speed them up at a specific point.
It's giving just shorthand for how the work actually gets done, on top of writing the direct binary commands. The shorthand however needs to include some kind of high level stuff but you could implement that yourself. There's really just not that much stuff embroidery machines can do. At a certain point you need something that works but that doesn't require you actually need to write every trim and jump command yourself.
You were stitching over there, in that thread. Now you moved over here with a new thread. I can figure out which commands you need to be written. I'll give you the power to write those yourself. For example, if you wanted an embroidery machine to trim, then jump around randomly for half an hour, that's entirely valid set of commands to write to binary. But, there'd be no shorthand for that.

I updated the readme to better state the intentions here.

Also, anything that required such fine grain control to perform some action, could also be built into pyembroidery as a middle-level capability, as I cannot imagine any such thing wouldn't also be useful in a more general sense (Eg. *1) or that there's that much reason to warrant concern, embroidery machines have so few commands that "stitching these points here in this color" covers 99.9% of everything.
However, waiting for me to do such things would be a non-starter given your general pace at current. I'd be quite willing to give you commit access over the code as needed. The mandate for this project is generally limited by design.  I might wrap up in a couple days or so,  I think I'm down to the VP3 writer has some bug, EXP has an unknown conceptual flaw, hashing out the API, and making the encoder way more automatic between different format writes. Then it's just documenting things, and putting the library in useful places.
But, it would let you, going forward, just edit pyembroidery if you actually did find such a fine grain use case.  I've been programming embroidery stuff for a decade and I cannot actually think of some reason you should want to put your color-changes, trims, stops, and jumps in some particular order that doesn't have everything to do with the exact format you are writing, and, thus, better located here.
I have a pretty extensive embroidery app with lots of interesting bells and whistles and even more proposed ideas and concepts. I cannot at all think of a reason you'd want to touch the stuff at that lowest level. I've never thought of a usecase (outside of moving the head around in circles forever), but it's like a line of code to pass through the lower level commands during encoding.
1
If for some proper established reasons your tie_on and tie_off procedures are better than mine. They could also be offered here, in addition to my chosen method. Though really, those tie-downs should be added to the stitch blocks so they can be toggled on and off at a per object level and not done during the writing, sort of like the check-boxes for stop-after and trim-after ... Actually this gives me a great idea for how to do the encoder and apis (namely have the various toggleable features encoded in commands TOGGLE_TIE_ON(0,0) MAX_STITCH_LENGTH(127, 127), TRANSLATE(x, y) SCALE(1.3, 1.3), then you could have these properties change on the fly and apply to the remaining stitches and never have to see the encoder, and the low level commands would pass through).

Commit access would be excellent!  It's kind of you to offer.
I'm impressed with how fast this is all coming together.  Thank you for all of your work!  Once you're feeling that things are stabilized, I'll start working on integrating it with Ink/Stitch.
I love that this thing is becoming more than a low-level layer for Ink/Stitch.  Hopefully more Python embroidery projects pop up as a result.
In light of that, do you want to move this repo into the inkstitch github organization, or would you rather keep it separate?  Either is fine with me.  If it were in the github org, you'd still be the owner, if I understand these things correctly.

Yup, I saw.  Been a bit busy but I'll try to add you to the organization today.


Image Backend Doesn't work on Arch Linux

I'm running neofetch with the --jp2a and --caca option with the path to a  image of my home, neofetch only shows me the ascii art of my distro.
I tried it on Konsole, cool retro term and tty

#1392
Also. Need your config file and a verbose log.


when POST fails, build-service starts another reconcile, but PaC

actually triggers new build, resulting in endless pipelines
temporary workaround for KFLUXBUGS-1858
Checklist:

PR has reference to the issue(s) it resolves
Write / update unit tests
Write / update integration (envtest) tests
Ensure there is an issue for e2e tests if needed
Ensure make test passes
Ensure test coverage hasn't decreased
Test code changes manually
Update readme and documentation
Write PR description that highlights overall changes and add usage examples if applicable

Will this result in the status updating on the Component?

yes it will be processed as successful and annotation updated

Will this be user facing other than not having many PLRs being triggered?

well PaC actually triggers the pipeline

What process would be required if the sync between build service and PAC legitimately fails? How would a user/SRE notice and recover?
just from build-service logs can error be seen


Support for Missing SVG Font and Text Attributes

There are many font and text properties in the SVG spec. Several of them are missing from your list of supported options. Will you add support for the following?
Font properties:
‘font-size-adjust’
‘font-stretch’
Text properties:
‘direction’
‘letter-spacing’
‘text-decoration’
‘unicode-bidi’
‘word-spacing’
‘alignment-baseline’
‘baseline-shift’
‘dominant-baseline’
‘glyph-orientation-horizontal’
‘glyph-orientation-vertical’
‘kerning’
‘text-anchor’
‘writing-mode’

Yeah, it isn't comprehensive.  If you want to add a few more options I'll accept a PR.