[turborepo]: Enable topological DSL operator to be used alone.

Describe the Feature Request
Turborepo should differentiate between task dependencies and code dependencies.
The dependsOn option is The list of tasks this task depends on. It seems natural that this option would be used to define task dependencies. However, this option is also used to define code level dependencies in a way which is both confusing and prevents even some simple use cases.
For example, lets say my monorepo looks like
> multiply
> subtract
> add

where multiply and subtract both depend on add.
As a responsible developer, I add tests to all three of these workspaces.
add is not compiled. In fact, none of these workspaces require a build step before testing.
Now, I want all these tests to run in parallel. So, for each of these tasks I set dependsOn: []. After all, multiply tests do not depend on add tests. So these things are safe to run in parallel.
Secondly, I want a change in add to force multiply tests to rerun. After all, a change in add might break the multiply.
I don't think this is possible with the current configuration options! With dependsOn: [], code changes in add don't change the computed hash for multiply. With dependsOn: ["^test"], my tests will no longer execute in parallel.
To summarize, my requirements are

All tests run in parallel
A change in a workspace dependency results in a new hash for its dependents

Expected Behavior
I expect two workspaces to be able to depend on each other from a code perspective (a change in one workspace affects the behavior of the other) without having the workspace tasks depend on each other (workspace A must finish this task before workspace B begins)
To Reproduce
Follow the steps in the readme for https://github.com/rubber-duck-software/turborepo-caching-demo
Reproduction Repo
https://github.com/rubber-duck-software/turborepo-caching-demo

I faced a similar issue with my monorepo.
Changes to my tsconfig and eslint packages did not invalidate the caches of tasks depending on either package.
As a workaround, I defined dummy build tasks for both packages:
"@yeger/eslint-config#build": {
    "inputs": ["src/**"],
    "outputs": ["src/**"]
},
"@yeger/tsconfig#build": {
    "inputs": ["base.json", "lib.json", "web.json"],
    "outputs": ["base.json", "lib.json", "web.json"]
}

This approach does not require a dummy build script in the package.json files of both packages.
If you now add
"add#build": {
  "inputs": ["src/**"],
  "outputs": ["src/**"],
},
"test": {
  "dependsOn": ["^build"]
}

to your pipeline, the test caches will invalidate once any of these files changes.
For your use case, you'd have to add the files of add to both its inputs and outputs.

It's really clear what happens here if you take a look at how the graph gets built when it doesn't have a dependsOn relationship:

The issue here is that we don't have a way in our DSL to tell you to depend on your topological dependencies outside of a task. Or, in other words, dependsOn: ["^"].
Fortunately, that's very straightforward to express as a dummy task in turbo.json:
 {
   "$schema": "https://turbo.build/schema.json",
   "pipeline": {
+    "topo": {
+      "dependsOn": ["^topo"]
+    },
     "test": {
+      "dependsOn": ["topo"]
     }
   }
 }

Once you do that you get the behavior you want and the graph looks like this:

It's plausible that we should add "just ^" as an additional syntax rule in the DSL, but it's low priority for us to do that given that there is a clear method to accomplish this task (and the DSL would, under the hood, desugar to exactly this behavior).

```
~/repos/turborepo-caching-demo (main *)$ pnpm run test

<EMAIL_ADDRESS>test /Users/nathanhammond/repos/turborepo-caching-demo
turbo run test

• Packages in scope: add, multiply, subtract
• Running test in 3 packages
• Remote caching disabled
multiply:test: cache miss, executing a4071ac8184f70f3
add:test: cache miss, executing 2c815d3941833b6b
subtract:test: cache miss, executing a17e4fd5c8dad973
multiply:test:
multiply:test: ><EMAIL_ADDRESS>test /Users/nathanhammond/repos/turborepo-caching-demo/multiply
multiply:test: > beartest
multiply:test:
subtract:test:
subtract:test: ><EMAIL_ADDRESS>test /Users/nathanhammond/repos/turborepo-caching-demo/subtract
subtract:test: > beartest
subtract:test:
add:test:
add:test: ><EMAIL_ADDRESS>test /Users/nathanhammond/repos/turborepo-caching-demo/add
add:test: > beartest
add:test:
add:test: add
subtract:test: subtract
multiply:test: multiply
multiply:test: ✓ 3 * 3 = 9
add:test: ✓ 1 + 1 = 2
subtract:test: ✓ 3 - 1 = 2
subtract:test:
add:test:
multiply:test:
Tasks:    3 successful, 3 total
Cached:    0 cached, 3 total
Time:    10.342s
~/repos/turborepo-caching-demo (main *)$ pnpm run test

<EMAIL_ADDRESS>test /Users/nathanhammond/repos/turborepo-caching-demo
turbo run test

• Packages in scope: add, multiply, subtract
• Running test in 3 packages
• Remote caching disabled
multiply:test: cache miss, executing d16ada726e2ef9d6
add:test: cache miss, executing 196aebf803d6ae02
subtract:test: cache miss, executing 44e59a442e41cf15
multiply:test:
multiply:test: ><EMAIL_ADDRESS>test /Users/nathanhammond/repos/turborepo-caching-demo/multiply
multiply:test: > beartest
multiply:test:
subtract:test:
subtract:test: ><EMAIL_ADDRESS>test /Users/nathanhammond/repos/turborepo-caching-demo/subtract
subtract:test: > beartest
subtract:test:
add:test:
add:test: ><EMAIL_ADDRESS>test /Users/nathanhammond/repos/turborepo-caching-demo/add
add:test: > beartest
add:test:
add:test: add
multiply:test: multiply
subtract:test: subtract
multiply:test:
multiply:test: ✗ 3 * 3 = 9
multiply:test:
subtract:test:
subtract:test: ✗ 3 - 1 = 2
subtract:test:
add:test:
add:test: ✗ 1 + 1 = 2
add:test:
add:test: AssertionError [ERR_ASSERTION]: 0 == 2
multiply:test: AssertionError [ERR_ASSERTION]: -9 == 9
multiply:test:     at /Users/nathanhammond/repos/turborepo-caching-demo/multiply/index.test.js:8:12
add:test:     at /Users/nathanhammond/repos/turborepo-caching-demo/add/index.test.js:8:12
add:test:     at async /Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/beartest.js:16:5
add:test:     at async RunSerially (/Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/beartest.js:5:5)
add:test:     at async runSuite (/Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/beartest.js:33:5)
add:test:     at async suite (/Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/beartest.js:71:5)
add:test:     at async Promise.all (index 0)
add:test:     at async runTests (/Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/testrunner.js:15:7) {
add:test:   generatedMessage: true,
add:test:   code: 'ERR_ASSERTION',
add:test:   actual: 0,
add:test:   expected: 2,
multiply:test:     at async /Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/beartest.js:16:5
multiply:test:     at async RunSerially (/Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/beartest.js:5:5)
multiply:test:     at async runSuite (/Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/beartest.js:33:5)
multiply:test:     at async suite (/Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/beartest.js:71:5)
multiply:test:     at async Promise.all (index 0)
multiply:test:     at async runTests (/Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/testrunner.js:15:7) {
multiply:test:   generatedMessage: true,
multiply:test:   code: 'ERR_ASSERTION',
multiply:test:   actual: -9,
multiply:test:   expected: 9,
multiply:test:   operator: '=='
multiply:test: }
add:test:   operator: '=='
add:test: }
subtract:test: AssertionError [ERR_ASSERTION]: 4 == 2
subtract:test:     at /Users/nathanhammond/repos/turborepo-caching-demo/subtract/index.test.js:8:12
subtract:test:     at async /Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/beartest.js:16:5
subtract:test:     at async RunSerially (/Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/beartest.js:5:5)
subtract:test:     at async runSuite (/Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/beartest.js:33:5)
subtract:test:     at async suite (/Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/beartest.js:71:5)
subtract:test:     at async Promise.all (index 0)
subtract:test:     at async runTests (/Users/nathanhammond/repos/turborepo-caching-demo/node_modules/.pnpm/beartest-js@5.0.4/node_modules/beartest-js/testrunner.js:15:7) {
subtract:test:   generatedMessage: true,
subtract:test:   code: 'ERR_ASSERTION',
subtract:test:   actual: 4,
subtract:test:   expected: 2,
subtract:test:   operator: '=='
subtract:test: }
multiply:test:  ELIFECYCLE  Test failed. See above for more details.
subtract:test:  ELIFECYCLE  Test failed. See above for more details.
add:test:  ELIFECYCLE  Test failed. See above for more details.
add:test: ERROR: command finished with error: command (/Users/nathanhammond/repos/turborepo-caching-demo/add) pnpm run test exited (1)
subtract:test: ERROR: command finished with error: command (/Users/nathanhammond/repos/turborepo-caching-demo/subtract) pnpm run test exited (1)
command (/Users/nathanhammond/repos/turborepo-caching-demo/add) pnpm run test exited (1)
command (/Users/nathanhammond/repos/turborepo-caching-demo/subtract) pnpm run test exited (1)
Tasks:    0 successful, 2 total
Cached:    0 cached, 2 total
Time:    10.304s
ERROR  run failed: command  exited (1)
 ELIFECYCLE  Test failed. See above for more details.
</details>

Conceptually dependsOn actually conflates two things: package dependencies (^, docs#) and task dependencies (build). Both need to be specified to get the behavior a person may want.
The reason for the distinction here is that some tasks (think: apps that have bundlers that will do the right thing for dependencies throughout the application, or lint tasks that are simply static analysis of all code unaware of the project architecture) don't need to be aware of any topological dependencies. We can already express those in our DSL gracefully.
Your example is the inverse: topological dependencies, but no task dependencies. We can make our DSL do this, but it requires the ^topo indirection workaround.

Ahh- that example is very helpful. A tool like eslint will not be affected by changes in a dependency, but a tool like tsc will.
As for the dependsOn option, if I understand you correctly, you are saying it expresses two things.

This task is dependent on the following tasks in the same workspace (build)
This task is dependent on the following tasks in other workspaces (^build, docs#)

If I understand the current configuration correctly from the docs
dependsOn: The list of tasks this task depends on.
env: The list of environment variables this task depends on.
inputs: The list of files this task depends on. (defaults to all files in the workspace)
If I understand the topo workaround correctly, it works because multiply#test depends on add#topo which in turn depends on all the files in add workspace via the inputs option.
An equivalent way of solving this (though far more fragile) would be
"test": {
    "dependsOn": []
},
"multiply#test": {
    "inputs": ["../add/*"]
},
"subtract#test": {
    "inputs": ["../add/*"]
}

Now understanding that, I guess I would phrase the request as
Add the ability to express file dependencies (like the input option) but using pnpm filter syntax for packages (like the dependsOn option).

Your alternative proposal is not quite equivalent. You're still not taking advantage of the dependency graph. You're instead specifying a list of inputs which can be individually considered as part of a cache key for a task.
In other words, it's still this:

The trick in the ^topo approach is that you can also specify "add#topo": { "inputs": ["src/**"] } and then all things in the topo graph will do the right thing. (This is a thing I had on my mind for why not ship the "just ^" solution.)
From a Turborepo perspective the inputs pattern you specify has one additional major drawback: each one of those input globs must be individually calculated. Putting it into a tree means it's calculated just once.
We're definitely not going to add a way to express dependencies that are in a separate package like this, nor provide a way to make that less painful by using filter syntax. We want to encourage people into thinking in graphs.

Good point- I had not considered the performance impacts of my proposal.
So, what I think I'm hearing is

We probably do not want to introduce new syntax to handle this use case
We definitely do not want to introduce a new configuration option to handle this use case.

If that is true, it would seem the "workaround" is no longer a workaround but instead the long term way of solving this. Thanks for the PR around documenting this @anthonyshew.
I am also going to create a PR for adding documentation to the Monorepo Handbook under linting. I think running tsc across all workspaces will require this workaround.

I am still open to being convinced that "just ^" is a worthwhile feature which is why I tweaked this issue instead of closed it.
It's not new syntax, it's not a weird overload, and being able to explain everything as a cross product of options is also useful pedagogically.
But I do want to give it time and see precisely how many people head down this path, and see if other features we end up building start to work with it in a graceful way.
We pay a maintenance tax on every public API we support, so I try to be conservative about adding it.

As for the number of people who head down this path, I am going to guess this is common because of typescript.
The monorepo handbook discusses using typescript as a linter. I'd say any monorepo which uses typescript as a linter and wants to run typescript in parallel across their packages will run into this.
See example repo https://github.com/rubber-duck-software/turborepo-tsc-caching
Regarding the "^", I think it's a bit too subtle for my comfort, but I'm only one user. It could very well be introducing "^" is the best answer. This would clean up the most common examples of this issue at any rate and the topo workaround could be used for the remainder.

From your example:

Observed that all tsc tasks succeed because they use a cached result. Desired behavior is that we would not get a cached result but instead all tests would fail.

Isn't this issue expected? Your pipeline is deliberately running tsc in parallel. Considering one package depends on the other, a task dependency is, IMO, required.
That's also how I organized my monorepo:
"typecheck": {
    "dependsOn": ["^build"],
    "inputs": [
      "index.html",
      "tsconfig.json",
      "vite.config.ts",
      "*.d.ts",
      "public/**",
      "src/**",
      "test/**"
    ],
    "outputs": []
  }

with typecheck running tsc --noEmit.

It is possible to run tsc in parallel and still get accurate type check failures. Per @nathanhammond's suggestions above, the correct turbo.json file for this would have been
{
  "$schema": "https://turborepo.org/schema.json",
  "pipeline": {
    "topo": {
      "dependsOn": ["^topo"]
    },
    "tsc": {
      "dependsOn": ["^topo"]
    }
  }
}

You can see this example working at https://github.com/rubber-duck-software/turborepo-tsc-caching/tree/working-example
This configuration will both run tsc in parallel across all projects and will ensure correct caching behavior. However, the configuration is subtle enough that I think most users will miss it and accidentally configure only partial parallelization or (worse) incorrect caching.

It is possible to run tsc in parallel and still get accurate type check failures. Per @nathanhammond's suggestions above, the correct turbo.json file for this would have been
{
  "$schema": "https://turborepo.org/schema.json",
  "pipeline": {
    "topo": {
      "dependsOn": ["^topo"]
    },
    "tsc": {
      "dependsOn": ["^topo"]
    }
  }
}

You can see this example working at https://github.com/rubber-duck-software/turborepo-tsc-caching/tree/working-example
This configuration will both run tsc in parallel across all projects and will ensure correct caching behavior. However, the configuration is subtle enough that I think most users will miss it and accidentally configure only partial parallelization or (worse) incorrect caching.

Yes, across all projects, but not dependency and dependent.
If you change it to
"tsc": {
  "dependsOn": ["^tsc"]
}

it will still run in parallel for unrelated projects (i.e., no dependency on each other).
The result will be identical to your topo approach.

Hi @DerYeger! Thanks for continuing to engage on this.
Your example of
"tsc": {
  "dependsOn": ["^tsc"]
}

is different than the topo approach. Let's say in my example repo tsc takes 10 seconds for add and 10 seconds for subtract. If turbo.json were authored as you suggest, total time to type check the monorepo would be ~20 seconds. Using the topo approach the total time would be ~10 seconds. Both approaches ensure correct caching.
I have added a some sleep time into https://github.com/rubber-duck-software/turborepo-tsc-caching/tree/working-example so you can verify this behavior for yourself.
My opinion is that this is a lot of subtlety for a fairly vanilla example. I am happy to help with documentation on this. :)

Ah, my bad. Because of tsc, I immediately jumped to assumption that your subtract depends on the dist files of add.

@rubber-duck-software @DerYeger Docs for this behavior have landed!
The opinion I've developed working through this issue and doccing is that both options ("^" or the dummy task) feel like they bring equal clarity to a reader of a turbo.json file. If I were stumbling upon either of these in a turbo.json and had never seen them before, I would have to learn what either of them really mean. "^" feels something like a "magic string" to me but, if I know how Turbo tasks work with enough depth, I may be able to grok what the dummy task strategy does - and, if I can't, now it's docced.
@nathanhammond @tknickman Will leave it to y'all's judgment as far as if we think a DSL change is in order or if we can close this. 👍

I believe #2911 is still relevant. Any feedback would be appreciated.

@nathanhammond - In https://github.com/vercel/turbo/issues/2855#issuecomment-1334793695 you mentioned

We want to encourage people into thinking in graphs.

I did not understand this topo “trick” the first time I read it in the docs, but I understand it more now from this issue. As I went to add it to my repo, I considered the alternate name dependencies (for the nice "dependsOn": ["dependencies"]).
Any comments on the word choice here? Does topological “speak this idea better/more precisely” than dependencies?

@connorjs You could call it "get-your-flu-shot" and it'll still work; dependencies has a naming collision with package.json that can be confusing for people so I chose topo to make it clear that it was distinct.


docs: contribution guide

Contribution guide for samba-operator project, which should allow any user to provide valid patches for this code base. Defines the minimal requirements for a pull-request to be classified as valid.

good start, @synarete , thanks for picking this up! According t github's projectcommunity standards, I think the file should be called CONTRIBUTING.md. see https://github.com/samba-in-kubernetes/samba-operator/community

@obnoxxx I tend to agree with you here, but on the other hand other project (e.g., rook's contribution guide) don't follow this convention. Put is differently, I could not to decide with option is better...

@obnoxxx Thinking about it again, I decided you made a valid point. Renamed to CONTRIBUTIONG.md.

@obnoxxx Thinking about it again, I decided you made a valid point. Renamed to CONTRIBUTIONG.md.

Typo here in the comment, but I checked and the actual name of the file is OK. :-)

@obnoxxx Thinking about it again, I decided you made a valid point. Renamed to CONTRIBUTIONG.md.

Typo here in the comment, but I checked and the actual name of the file is OK. :-)

Neatness counts -- will fix.

One last thing prior to approval. I see that the pr is made up of two commits: the new file and then the new file getting renamed. I think it would be cleaner to squash these commits so that the file history just shows CONTRIBUTING.md getting added. What say you?

One last thing prior to approval. I see that the pr is made up of two commits: the new file and then the new file getting renamed. I think it would be cleaner to squash these commits so that the file history just shows CONTRIBUTING.md getting added. What say you?

Agreed. Will do so.

@obnoxxx PTAL when you have a moment


[Health Pickup] - Doesn't spawn periodically

Health pickup only spawns once while it should generate whenever the player's health is below 80.

This problem was the scale transform xy was not being reset.


fix: Catch database exceptions at the end of transactions.

Description
As explained in detail in this issue: #2850 , database exceptions are re-thrown if a transaction is allowed to complete when a database exception has occurred. This PR ensures those errors are caught when the top level test transaction completes.
We should also create a small caveat in the test docs about this. Currently the following code will throw in production code, but will complete successfully in test code:
session.db.transaction((tx) async {
  var data = UniqueData(number: 1, email: 'test@test.com');
  try {
    await UniqueData.db.insertRow(session, data);
    await UniqueData.db.insertRow(session, data);
  } catch (_) {
    // Ignore duplicate key exception from DB
  }
});

While this is a theoretical inconsistency, it should very rarely (if ever) be a problem because this type of code does not make sense and should be considered an anti-pattern. The transaction is aborted when errors happen, so no more operations can be performed anyway.
Changes

Adds catchError to the top level test transaction [4abee2ac7531924c80acaf6df151a674c646a4ae]
Adds a test config for serverpod_test_server to avoid having to pass a production run mode to the withServerpod helper [a05fe24]

Pre-launch Checklist

[x] I read the Contribute page and followed the process outlined there for submitting PRs.
[x] This update contains only one single feature or bug fix and nothing else. (If you are submitting multiple fixes, please make multiple PRs.)
[x] I read and followed the Dart Style Guide and formatted the code with dart format.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///), and made sure that the documentation follows the same style as other Serverpod documentation. I checked spelling and grammar.
[x] I added new tests to check the change I am making.
[x] All existing and new tests are passing.
[x] Any breaking changes are documented below.

@SandPod Added docs here: https://github.com/serverpod/serverpod_docs/pull/184


Adds a getter for participants, groups and scenes

... because there was no nice way to do that before, other than either querying the server again or manually storing a list of (session|group|participant)IDs.

I prefer getScenes and getParticipants as it avoids the private variables with _.
Not sure what others think though

I agree with @ProbablePrime, I think getScenes and getParticipants keeps it consistent with the getScene and getGroup methods.  I'm not so much against _private variables, but I also like to keep things consistent with the style so it's easier to read later.


feat: support dotfiles or something equivalent

Description
Codespace/Gitpod supports dotfiles to init the dev environments.

https://docs.github.com/en/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account#dotfiles

So far, envd can set up the shell prompt. But still lack some features. Maybe we can find a way to support dotfiles or something equivalent.

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

It is possible, I think.

Hi, it sounds like envdlib is a trivial way to implement this? For example, having a dotfiles.envd that accepts a dotfiles github repository link as parameter and setups dotfiles from there.

Hi, it sounds like envdlib is a trivial way to implement this? For example, having a dotfiles.envd that accepts a github repository link as parameter and setups dotfiles from there, so users can do
envdlib.dotfiles(repo="https://github.com/hxu296/mydotfiles")

This might be possible. You can try it. Thanks.


Announcements

I need a way to announcing events, features, milestones, etc.
Some ideas:

A mailing list
Just spam people on twitter
An RSS feed on ordinals.com
A blog
A discord channel

Substack + post on twitter seems to be a pattern that's emerged. You have the space on the newsletter/blog to both do release-notes type posts and also do longer form content about why things are the way they are, interesting ideas you're mulling over, etc. Twitter is a place to have people commend and get spammed.

Seems reasonable to me!


[UX][Publisher] API Definition URL pattern prefix disappears when the version is given without the context

Description:

The prefix should be {context}/v1.0.0 till the context is given
Suggested Labels:
Bug
Affected Product Version:
2.5.0

Jaggery based publisher app is no longer in use. Please reopen if this happens with the latest version.


option to strip accents in tokenizer

Adding an option to strip accents in the tokenizer components:
accénto -> accento
In languages such as french the accents and the possible combinations make it hard to annotate intent / entity data.

@MetcalfeTom does this duplicate your other issue you opened?

Yes, IMO the Preprocessor is a more sustainable solution, since the gives the user the option to do these kinds of token processing at any point in their pipeline https://github.com/RasaHQ/rasa/issues/3439


Move gltf to core.

See https://github.com/godot-extended-libraries/godot-fire/pull/3.
From reduz:

We got quite a lot of demand to make the GLTF importer part of core, given it is needed for VR and other stuff, so I have the feeling we should optimize it for performance (which we should do anyway) and have an option to load actual meshes instead of EditorImporterMesh.. so that means we would need to provide a function to parse the mesh node into a scene node and the editor supplies, otherwise it uses Mesh as a default

General design:
var gstate : GLTFState = GLTFState.new()
var gltf : PackedSceneGLTF = PackedSceneGLTF.new()
print(path);
var raw_f = File.new()
if raw_f.open(path, File.READ) != OK:
	return FAILED
var buffer : PackedByteArray = raw_f.get_buffer(raw_f.get_len())
var root_node : Node = gltf.import_gltf_scene_buffer(buffer, flags, 1000.0, gstate)

Todo from reviewers:

[ ] add explicit security checks and migrate any URI resolving code for textures & buffers & etc. into a common helper which has an explicit check that returns ERR_FAIL_...
[ ] EditorSceneImporterMeshNode to MeshInstance needs to be function pointers that allow the code to switch based on function pointer null to MeshInstance3D
[ ] Blend shape key frames should have service limits requested in https://github.com/godotengine/godot/pull/48947
[ ] Review design of PackedSceneGLTF vs purely using GLTFDocument

Superseded by: https://github.com/godotengine/godot-proposals/issues/3273


Docs on GML32 not clear on Simple Features and version

GML3 class states that it

Currently only supports GML 3.1.1 Simple Features profile.

while GML32 class doesn't. This makes me think that it shouldn't be limited to simple features. So is my assumption right and GML 3.2 does support complex features?
Or are simple features only supported for reading, but not for writing as methods writeFeatures and writeGeometryNode specifically do talk about Simple Features?
Another issue seems to be that methods writeFeatures, writeFeaturesNode and writeGeometryNode talk about GML 3.1.1, and not GML 3.2.1.

GML 3.2 support was sneaked in bit by bit. So if you spot any inconsistencies in the documentation, please submit doc improvements as pull requests! In general, OpenLayers formats only support simple features out of the box. However, it may be possible to make some aspects of complex features work with some extra application code.


Dev Build

Is there any way I could do a dev build? I am trying to run this within an existing aspnet mvc app and running this in dev in a node server does not help me, but running in the aspnet without vue debugging is challenging. So I would like to compile the build, but using the dev flag.

I would change this line to:
if (!process.env.NODE_ENV) {
  process.env.NODE_ENV = 'production'
}

Then you should simply be able to run
NODE_ENV=development node build/build.js

I'll give it a try, although I think I tried copying the build.js file and changing that like to be process.env.NODE_ENV = 'development' and that didn't seem to work properly...


runtime-class.md: update containerd/cri link

The containerd/cri repo was merged into the containerd/containerd repo.
The containerd/cri repo is now archived: https://github.com/containerd/cri

No issues I can see. Looks okay.

/approve


MM-25967 await until cookies are cleared

Summary
as in the ticket
Ticket Link
https://mattermost.atlassian.net/browse/MM-25967

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/6806
https://circleci.com/gh/mattermost/mattermost-mobile/6805

Artifact links:
https://6806-70265724-gh.circle-artifacts.com/0/~/mattermost-mobile/Mattermost_Beta.apk
https://6805-70265724-gh.circle-artifacts.com/0/~/mattermost-mobile/Mattermost_Beta.ipa

/cherry-pick release-1.32


[BUG] "message.author" and "message.author.avatar_url" not working correctly

Summary
When other users are triggering commands/events using "message.author" and "message.author.avatar_url" it returns as "None"
Reproduction Steps
1. Get a different user to send the command that uses "message.author". In my case the command used was ">test"
Code
Relevant code that shows the bug.
class MyClient(discord.Client):
    async def on_ready(self):
        print('Logged on as', self.user)

    async def on_message(self, message):
        if message.content.startswith(">test"):
            await message.channel.send(message.author.avatar_url)

Expected Results
It's supposed to return the correct author tag, and avatar url
Actual Results
It's sending "none"
System Info
Run python -m discord --version and paste the information below.
- Python v3.9.6-final
- discord.py v1.8.1-final
- aiohttp v3.7.4.post0
- system info: Windows 10 10.0.19042

Checklist
Let's make sure this issue is valid!

[x] I am using the latest released version of the library.
[x] I am using a user token.
[x] I have shown the entire traceback and exception information.
[x] I've removed my token from any code.

https://github.com/dolfies/discord.py-self/blob/e62a56d2f06d95db15f962507fae410b482aa3ec/discord/client.py#L869
According to the documentation and example codes, the on_message event requires only the "message" parameter, so everything will work normally.

https://github.com/dolfies/discord.py-self/blob/e62a56d2f06d95db15f962507fae410b482aa3ec/discord/client.py#L869
According to the documentation and example codes, the on_message event requires only the "message" parameter, so everything will work normally.

This example uses Development branch, but also works in 1.8.1

Even so, other users using commands that includes "message.author" are greeted with "None#0"
Result:

Code:
from discord.ext import commands

client = commands.Bot(command_prefix=">", self_bot=False)

@client.event
async def on_message(message):
    if message.content.startswith('$greet'):
        channel = message.channel
        await channel.send('Say hello!')

        def check(m):
            return m.content == 'hello' and m.channel == channel

        msg = await client.wait_for('message', check=check)
        await channel.send(f'Hello {msg.author}!')

client.run('token')

I recommend you to use breakpoints to get more details of this type of
problem, as you can see in the image I sent you, to get the user's nick
it's necessary to use message.author.display_name, and ID with
message.author.discriminator
Em qui., 22 de jul. de 2021 às 08:55, LOST. @.***>
escreveu:

https://github.com/dolfies/discord.py-self/blob/e62a56d2f06d95db15f962507fae410b482aa3ec/discord/client.py#L869
According to the documentation and example codes, the on_message event
requires only the "message" parameter, so everything will work normally.
[image: image]
https://user-images.githubusercontent.com/60858720/126631188-7a8238ca-ed8b-4218-b12d-d4efd3e324c3.png
This example uses Development branch, but also works in 1.8.1
Even so, other users using commands that includes "message.author" are
greeted with "None#0"
Result:
[image: Screenshot_13]
https://user-images.githubusercontent.com/51839454/126635023-5c588040-c970-432b-bb3b-b0a34b795ee8.png
Code:
from discord.ext import commands
client = commands.Bot(command_prefix=">", self_bot=False)
@client.event
async def on_message(message):
if message.content.startswith('$greet'):
channel = message.channel
await channel.send('Say hello!')
    def check(m):
        return m.content == 'hello' and m.channel == channel

    msg = await client.wait_for('message', check=check)
    await channel.send(f'Hello {msg.author}!')

client.run('token')
—
You are receiving this because you commented.

This is a problem related to LazyUsers, which are going to be removed in the next version. The beta is in the development branch.


episode len error

When I run baku on libero, I found in line 55 at eval.py, self.expert_replay_loader.dataset._max_episode_len is zero at initialization. So it makes line 96 at libero.py observation["features"][: state.shape[0]] = state occur an error about dimension because of observation["features"] = np.zeros(self._max_state_dim) create a zero dim numpy array.
full error:
evaluating env 0
Error executing job with overrides: ['agent=baku', 'suite=libero', 'dataloader=libero', 'suite/task=libero_10', 'suite.hidden_dim=256', 'bc_weight=/home/lzh/PycharmProjects/BAKU/weight/baku.pt']
Traceback (most recent call last):
  File "/home/lzh/PycharmProjects/BAKU/baku/eval.py", line 208, in main
    workspace.eval()
  File "/home/lzh/PycharmProjects/BAKU/baku/eval.py", line 107, in eval
    time_step = self.env[env_idx].reset()
  File "/home/lzh/PycharmProjects/BAKU/baku/suite/libero.py", line 327, in reset
    time_step = self._env.reset(**kwargs)
  File "/home/lzh/PycharmProjects/BAKU/baku/suite/libero.py", line 228, in reset
    time_step = self._env.reset(**kwargs)
  File "/home/lzh/PycharmProjects/BAKU/baku/suite/libero.py", line 159, in reset
    return self._env.reset(**kwargs)
  File "/home/lzh/PycharmProjects/BAKU/baku/suite/libero.py", line 293, in reset
    obs = self._env.reset(**kwargs)
  File "/home/lzh/PycharmProjects/BAKU/baku/suite/libero.py", line 98, in reset
    observation["features"][: state.shape[0]] = state
ValueError: could not broadcast input array from shape (47,) into shape (0,)

Hi,
Can you confirm if the root_dir variable in baku/cfgs/config_eval.yaml has been set to where you have stored the dataset?

I got that. I didn't found config_eval.yaml but only found config.yaml. Thank you!

The file is here. This is the root_dir variable that you will need to modify.


Fix compilation error in non-BTF environmnets

Signed-off-by: Tao Wen<EMAIL_ADDRESS>

thank!


Make :expected/:actual compatible with clojure.test

Since the generated :message now has (almost) all the same good stuff that Expectations always used to have, we should make the :expected/:actual keys compatible with what (some) clojure.test tooling expects.
In particular, Cursive performs a test output difference visualization based on the :actual value which is usually of the form (not (= expected-value produced-value)) (not forms).

No longer relevant -- clojure.test compatibility has been rewritten.


[move source language] Remove tentative support for unary negation

Move does not currently have any signed numeric types, so unary negation operations cannot be used. Remove the tentative support for that operation. We can easily add it back if Move later provides signed numeric types.
Motivation
Simplifying the compiler and avoiding the strange error message that we currently provide for unary negation.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Updated the expected output for the existing parser test and removed other tests for later phases of the compiler.

@bors-libra r=tnowacki

:pushpin: Commit 6420352 has been approved by tnowacki

:hourglass: Testing commit 6420352f4d65edb96f7d9594a0e97e26adfefa15 with merge 741c79ec0c84886d714d7f0813a7bc77fd6ee0e1...

:broken_heart: Test failed - checks-circle_commit_workflow

Rebased and fixed the move_check/parser/expr_unary_ops.move test....

@bors-libra retry

@bors-libra r=tnowacki

:pushpin: Commit 09165cc has been approved by tnowacki

:hourglass: Testing commit 09165cc8fe51b64e273c243a634424058bf5502d with merge ea84db439c03fe8f74965896eb53ac2a66bfe537...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: tnowacki
Pushing ea84db439c03fe8f74965896eb53ac2a66bfe537 to master...


Showcase your HTML, CSS and JavaScript Projects.

hey @Mridul2820, can i showcase a drumset project, made of HTML, CSS and JS only

Hi @prnvtripathi , you can showcase the project. Follow the Contibution Guidelines and add the project with the best match section. Thank You.

@Mridul2820  I want to show my HTML, CSS, Js Calculator Project.
can I contribute, if yes then please assign me under Hacktoberfest.
Thank You

Hi @minhaj-313 Just add your project in the respective tech folder and also add details on README.md that's it. Check Contributing Guide for more details

Hi @minhaj-313 Just add your project in the respective tech folder and also add details on README.md that's it. Check Contributing Guide for more details

I could not be able to find respective tech folder

Hi @minhaj-313 Just add your project in the respective tech folder and also add details on README.md that's it. Check Contributing Guide for more details

I could not be able to find respective tech folder

You should add your Calculator Project in the project/javascript folder

Hi @minhaj-313 Just add your project in the respective tech folder and also add details on README.md that's it. Check Contributing Guide for more details

I could not be able to find respective tech folder

You should add your Calculator Project in the project/javascript folder

ok, Thanks

i will like to contribute, pls assign me under hacktoberfest

@Mridul2820 I want to like to contribute, please assign me under hacktoberfest

Hey @Mridul2820 I would like to contribute, can you please assign me to this.
I have several projects to contribute.


upgrade balancer base to aura

API: https://github.com/beefyfinance/beefy-api/pull/1417
WETH-rETH: https://basescan.org/address/0x77B3B76A68B89541Cbb60d3609988376290Cb929
New Strat https://basescan.org/address/0x4352A383757b556a53460860f172ccEA23773A99
cbETH-WETH: https://basescan.org/address/0xbc15d22EA300d0965FD8a19A04CD8525834585Ef
New Strat https://basescan.org/address/0x7FC745a3915839E79FBC0dB648302d4217AFBC48
USDC/USDbC/axlUSDC: https://basescan.org/address/0x18A86f5E00200E1Df11210579fe6CdE565112bB8
New Strat https://basescan.org/address/0x9c7a85f7f5Bbdf145131177B619E4772901100dA

@schnarkus can you keep the same createdAt timestamp and add in a new field updatedAt? That should bump them up to the top


Enable golangci lint

Hey @relistan, this is a big-ish PR with quite a few cleanup changes that I'd like to get merged before I proceed with implementing #44. It was a good way for me to re-explore the code a bit and see what's in here. I'm happy to do adjust these changes in any way or not do them at all, but the main goal was to remove all warnings reported by golangci-lint and enable it for Travis builds.
Changes to  review individually:

4ae802a - Go 1.12 is making goconvey panic so I updated it to latest. I had to fiddle around with getting Dep to update https://github.com/jtolds/gls as a transitive dependency.
c69b1b9 - syscall.SIGSTOP can't be trapped or ignored, so no point trying
5d2c03d - Refactor deprecated http.CloseNotifier. Please have a close look at this one.
2ea6bbc - This looks broken in the current code. The linter has revealed the issue.
013e977 - Refactor RemoveListener to not return an error - This shouldn't have any impact. It's just making the code simpler, since we don't care about errors in that function except for logging purposes
870816f - Change the state in StateChangedEvent to be a pointer type - It looks like this should have been a pointer from the beginning to avoid warnings about potentially copying locks around. I don't think I'm breaking anything by changing this struct.
fd9d9d6 - Return nil from service.Decode in case of error - I'm not too happy with this approach. This function should be refactored to return an error, but not sure if that's acceptable. Sidecar only uses it here, which can easily be refactored. OTOH, I do wonder if this function can be removed completely. WDYT?
4b28168 -
Make the --cluster-ip flag optional and check Kingpin parse errors - We weren't checking the error when parsing the Kingpin flags, so this flag was never mandatory. Looking at its usage, I don't think it should be, given that it stomps over whatever is set in the SIDECAR_SEEDS environment variable. I adjusted the Readme to explain this.
6fe41ac - Generic code cleanup, error handling and extra logging. Shouldn't change any behaviour, but please check.
8d04ef1 - Travis cleanup - Seems to still work, so should be fine
b68bac6 - Enable golangci-lint for Travis builds, yay!
347e714 - Bump up go to 1.12. The latest golangci-lint needs at least go 1.10, so I thought it's best to just upgrade to the latest version. I can fall back to go 1.10 if you prefer that.

@relistan Regarding "Change the state in StateChangedEvent to be a pointer type" I did some testing in our dev environment with the following setup on a test host:

Start 2 haproxy-api Docker containers: haproxy1 on port 7778 and haproxy2 on port 7779
Run Sidecar on the host from this branch with LISTENERS_URLS="http://localhost:7778/update,http://localhost:7779/update" and --cluster-ip="a_valid_sidecar_seed"

At this point, both haproxy-api instances have the expected config written in the container under /etc/haproxy.cfg.
As a first experiment, I bounced a service and noticed that both haproxy-api instances have received the update and started proxying the new service instance.
Then, as a second experiment, I also took down Sidecar on one of the existing nodes in the cluster and observed updates coming into both haproxy-api instances, which seemed consistent.
I didn't observe any crashes or unexpected messages, so I am thinking that 870816f is safe. Please let me know if you wish me to do any other experiments.


Missing methods in LazyCriteriaCollection.php

LazyCriteriaCollection.php in ORM does not contain the methods included in AbstractLazyCollection.php in doctrine/collections
for example the following code is not working properly:
$collection->clear(); as there is no such function in LazyCriteriaCollection.php which is coming from abstract class AbstractLazyCollection.php

Sorry, but your issue makes no sense to me. LazyCriteriaCollection extends AbstractLazyCollection, but it does implement doInitialize. When calling $collection->clear(), it attempts to initialize the collection, using the doInitialize method and then executes the clear.
What is wrong with this approach? Did you experience any issue? Can you offer a sample code where this doesn't work?

When calling $collection->clear(), we have to add its method manually on LazyCriteriaCollection, otherwise it will be called from AbstractLazyCollection which is not correct. if you check LazyCriteriaCollection, methodscount()and isEmpty() are already created, but not other methods like clear().

@hatrena they are inherited. Can you please write a test showing what the problem would be?


doc: add community checks for OCP catalog

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Submit operators to both upstream-community-operators and community-operators at once
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@camilamacedo86, would be grat to have a paragraph with following content perwsenting olution on the new hard stopper: http://mailman-int.corp.redhat.com/archives/operatorframework-pm/2021-May/msg00007.html


Add recommendations for AST viewers in documentation

Would be good to recommend some AST viewers to people. It's much easier to use this library in conjunction with an AST viewer when working on harder problems.

@gdeividas thanks for that! I had looked at it before, but didn't realize it supported TypeScript... it's in the second menu. I'll probably recommend that one because it's easy to access. I guess the one downside is that it only navigates the tree via properties. That's not so bad though.

Yeah for me who is just starting to code/learn the AST on the go was quite helpful.
Anyways good job on the library - please continue improving it.

Implemented. I ended up only recommending the one available in atom-typescript. I also evaluated "TypeScript AST Explorer" in vs code and the "AST Explorer" web site.
I think in order to add an AST viewer to this page, it must have the following:

Show parent/child relationship between nodes.
Have ability to show all nodes (ex. SyntaxList nodes must not be excluded)

In the future, I'll probably add my own ast viewer to the documentation that has everything I'd like.

I've created a basic web-based AST viewer that shows the parent/child relationship between the nodes, shows the SyntaxList nodes, along with all the other small features many AST viewers leave out: https://dsherret.github.io/ts-ast-viewer/


[Website] Increase contrast of input borders to meet accessibility requirements

Related Issue
Fixes ADO 30943601
Description
Updated color of input borders to meet contrast requirements. Contrast between input borders and white background is now 3.544:1
How Verified
Verified contrast on website using dev tools and accessibility insights.
Microsoft Reviewers: Open in CodeFlow

@RebeccaAnne - do we still want to take this?

Sev 3 isssue. Closing for now.


LND sync scanning progress

[ ] change to lnd getinfo

On LND 0.10.X (?!) the log format seem to have changed. The 00infoBlitz.sh (INFO) uses (height but the line (with loglevel DEBUG)  is:
2020-07-20 14:56:39.287 [DBG] LNWL: Filtering block 605826<PHONE_NUMBER>0000000000f383c11667be88942faced981f45e42b4a366b5c31a3) with 3159 transactions
2020-07-20 14:56:42.683 [DBG] LNWL: Filtering block 605827<PHONE_NUMBER>0000000004ee6591455c105127659213990e6aaa1436a022d5d0de) with 2905 transactions

Scanning X/Z <- the X is not changing!

2020-07-20 14:43:18.283 [INF] LTND: Version: 0.10.4-beta commit=v0.10.4-beta, build=production, logging=default
2020-07-20 14:43:18.283 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2020-07-20 14:43:18.284 [INF] LTND: Opening the main database, this might take a few minutes...
2020-07-20 14:46:03.187 [INF] CHDB: Checking for schema update: latest_version=13, db_version=13
2020-07-20 14:46:03.188 [INF] LTND: Database now open (time_to_open=2m44.903992985s)!
2020-07-20 14:46:03.240 [INF] RPCS: password RPC server listening on <IP_ADDRESS>:20009
2020-07-20 14:46:03.240 [INF] RPCS: password gRPC proxy started at <IP_ADDRESS>:8080
2020-07-20 14:46:03.240 [INF] RPCS: password RPC server listening on <IP_ADDRESS>:10009
2020-07-20 14:46:03.262 [INF] LTND: Waiting for wallet encryption password. Use `lncli create` to create a wallet, `lncli unlock` to unlock an existing wallet, or `lncli changepassword` to change the password of an existing wallet and unlock it.
2020-07-20 14:46:12.358 [INF] LNWL: Opened wallet
2020-07-20 14:46:12.870 [INF] LTND: Primary chain is set to: bitcoin
2020-07-20 14:46:12.977 [INF] LTND: Initializing bitcoind backed fee estimator in CONSERVATIVE mode
2020-07-20 14:46:12.978 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on <IP_ADDRESS>:28333
2020-07-20 14:46:12.977 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on <IP_ADDRESS>:28332
2020-07-20 14:46:18.850 [INF] LNWL: The wallet has been unlocked without a time limit
2020-07-20 14:46:19.060 [INF] LTND: LightningWallet opened
2020-07-20 14:46:19.220 [INF] SRVR: Proxying all network traffic via Tor (stream_isolation=true)! NOTE: Ensure the backend node is proxying over Tor as well
2020-07-20 14:46:19.490 [INF] HSWC: Restoring in-memory circuit state from disk
2020-07-20 14:46:19.534 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0
2020-07-20 14:46:19.605 [INF] HSWC: Trimming open circuits for chan_id=592003:77:1, start_htlc_id=0
2020-07-20 14:46:19.850 [INF] LTND: Channel backup proxy channel notifier starting
2020-07-20 14:46:19.864 [INF] ATPL: Instantiating autopilot with active=false, max_channels=5, allocation=0.600000, min_chan_size=20000, max_chan_size=16777215, private=false, min_confs=1, conf_target=3
2020-07-20 14:46:19.901 [INF] RPCS: RPC server listening on <IP_ADDRESS>:10009
2020-07-20 14:46:19.901 [INF] RPCS: RPC server listening on <IP_ADDRESS>:20009
2020-07-20 14:46:19.942 [INF] RPCS: gRPC proxy started at <IP_ADDRESS>:8080
2020-07-20 14:46:19.945 [INF] LTND: Waiting for chain backend to finish sync, start_height=640028
2020-07-20 14:46:20.401 [INF] LNWL: Started rescan from block<PHONE_NUMBER>000000000bafad447afff4d430f97d68f66842ea8c42c089c8c75e (height 605595) for 8 addresses
2020-07-20 14:46:29.434 [INF] RPCS: [debuglevel] changing debug level to: debug
2020-07-20 14:46:31.391 [DBG] LNWL: Filtering block 605599<PHONE_NUMBER>000000000ba919ba32d481703927947745e49126291dcf56d345f6) with 2522 transactions
2020-07-20 14:46:34.839 [DBG] LNWL: Filtering block 605600<PHONE_NUMBER>00000000127bef398960e2edb5a1e276267def3d6f3c217191aaf9) with 2600 transactions
2020-07-20 14:46:37.921 [DBG] LNWL: Filtering block 605601<PHONE_NUMBER>000000000055b04770cdc9ca77d73886ba2ddf880b8ee827515d12) with 2151 transactions
2020-07-20 14:46:40.448 [DBG] LNWL: Filtering block 605602<PHONE_NUMBER>000000000fc284cd7da224890e5e4ca00c6479ece8f643f2b7ae0c) with 2980 transactions
2020-07-20 14:46:43.958 [DBG] LNWL: Filtering block 605603<PHONE_NUMBER>00000000132b08ab9c361abfca21684ec13891684db263dba49f55) with 3007 transactions
2020-07-20 14:46:47.324 [DBG] LNWL: Filtering block 605604<PHONE_NUMBER>00000000112208b4c87fa12b83a6a5ccf3ba6e6a28960767c9af67) with 2309 transactions
2020-07-20 14:46:50.215 [DBG] LNWL: Filtering block 605605<PHONE_NUMBER>0000000001a2d9bd2c8de99dabbf80368b5c0c02e5693b29de2b24) with 2586 transactions
2020-07-20 14:46:53.400 [DBG] LNWL: Filtering block 605606<PHONE_NUMBER>0000000012b939ae969aeae55a209f33ba3643c9f473e415ee4d84) with 3080 transactions
2020-07-20 14:46:56.963 [DBG] LNWL: Filtering block 605607<PHONE_NUMBER>00000000117af6ebe82f0b3d9f708d4d48512681b4db36e1cbc1d7) with 1620 transactions
2020-07-20 14:46:59.382 [DBG] LNWL: Filtering block 605608<PHONE_NUMBER>000000000a82bb01dac73c5efc3204bb12ec5f594458e6c0d967d6) with 2898 transactions
2020-07-20 14:47:02.773 [DBG] LNWL: Filtering block 605609<PHONE_NUMBER>00000000095358d008281b79a7d335c6a7c4bae9b75aa8d43ab50b) with 2221 transactions

I used this to enble debug logging: lncli debuglevel --level debug

The LCD (00infoLCD.sh) calls 80scanLND.sh which uses /home/admin/config.scripts/blitz.statusscan.sh. There getinfo is called and the best_header_timestamp value is used to determine the progress.
I guess it makes sense to switch the 00infoBlitz.sh file to use the same way.

[ ] change to lnd getinfo

looking good on the latest master

Working with the quick fix for v1.6 ... will go with better implementation for v1.7.

@frennkie & @rootzoll  is there a possibility to apply a quick fix to 1.5 release? Like @openoms suggested with an updated script. I would really like to fix this issue on my node running 1.5 release (and manually updated LND to 10.4 & bitcoin to v0.20.0).

@bitsam you can try to apply the changes frennkie made for the v1.6 release manually to your script and reboot:
https://github.com/rootzoll/raspiblitz/pull/1370/files

@bitsam note that (as stated) #1370 requires LND to be run with debug log level.

@frennkie & @rootzoll , i am running v1.6-2020-08-04.img.gz and notice that the LND sync drops out several times a day, similar to the itial reported error by frennkie. Is the fix a work in progress due to changes with bitcoin v0.20.0 & LND v0.11 ? Or could this be my Rpi3 and SATA HDD are not quick enough to keep up with the LND chain ? What info should I be looking at to see why my node is losing LND sync so often ?

I removed the "scanning progress" completly on the ´00infoBlitz.sh´ .. it will just show "Waiting for Chain Sync" now when LND signals that synced_to_chain is false from getinfo. Also I changed the color from red to amber ... because its not a super critical event ... its even normal that LND might take a second to scan a block and if the raspiblitz measures at exactly that point in time the info might stay longer on the screen (until next refresh) than it even takes fro LND to catch up. Also I dont think your LND is "offline" during that time ... to forward or receive it should not be crucial to have the latest block in that second. You just need to know if channel force closed ... and if that channel is making in that second a payment you would have a newer closing transaction to punish that channel partner.

All tests look good ... this wil be part of v1.6.1 release. Closing issue.


[feat] Extend listing records to support attachments and extras

Atrachment will be lazy loaded, content of attachments could be aggregated in JSOn form to the main record - maybe into "json" field or for performance opt. Into "attachments_json" which ahould be then avaiable in the client thru some more telling property like parsed() and parsedAttachments() returning "HealthRecordObjectModelType" which should have also a "status" property telling if it used to be already processed or not

partialy done with attachments stored and serialized


Adding Google Pay Clone

🛠 Fixes Issue
Closes #699

👨💻 Changes proposed
I have added clone of Google Pay in a well simple designed way.

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📷 Screenshots

Can you attach deployed link in Readme
@Rakesh9100

Can you attach deployed link in Readme @Rakesh9100

Done


hyper-parameters for reproducing results on MSCOCO

Thanks for the inspiring implementation :)
I'm having trouble to reproduce the results on MSCOCO with tresnet_m as backbone, 224 as input.
I have varied lr (1e-4 and 2e-4), batch_size (128 and 64), epochs (40/80 and 14/25) and only got around 79.+% mAP (which are lower than reported pre-train models).
I understand you can't share the original training code due to commerical reasons, can you provide your hyper-parameters for the reproduction? Seems these hyper-params influence the results.

for tresnet_m 224 model in the site (posted a week ago), i used a better pretrain than the one you are using, so it's not unreasonable that you are getting lower scores (my pretrain is imagenet21K + special pre-train, yours is imagenet1K).
new prertrain models will be released in a couple of months along with a new article.
still, 79.0% is not a low score, i think it can even be considered SOTA compared to other articles (for resolution 224).
try training with resolution 448, and i think you will reproduce the article results of tresnet_m.

@mrT23 Thanks for the reply, I'll try it :)


11ty/eleventy#2466 Add documentation for skip in pagination

The referenced PR adds the skip parameter and this one adds the required documentation.
The "addedin" will probably need to be updated once the referenced PR got merged.

This can be labeled on-hold as it's waiting for a feature to be merged into 11ty.


feat: Basic components for M(V)P

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


The reason public initialiser isn't available for LocationManager?

It's been great to have .failing becoming available after recent modernisation, which naturally leads to implementing a .noop version of the dependency too, but it isn't possible currently. Was there a reason for keeping init internal?

No reason, I don't think! I think we're relying on the synthesized memberwise initializer. If you'd like to PR an explicit, public one I don't see anything wrong with adding it! I could also see including the .noop version in the PR.


Unpoison the statx buffer for MSAN

Here is how libuv usually handles MSAN (prior to deleting this code and using the glibc wrapper instead), as Keno said: https://github.com/bnoordhuis/libuv/commit/233490819ca4010d0db70a0ae411ae9f73571baa

c.f. https://github.com/libuv/libuv/pull/311

At least I'm consistent ;)

I've opened https://github.com/libuv/libuv/pull/3788 to address this, also for getrandom().

Do we backport/pull the upstream changes, or do we wait for an upstream release?


it downloads nothing

Describe the bug
I upgraded to lastest version today (<IP_ADDRESS>).
I have one blog url, it has been downloaded regularly until today.
Now: Evaluated 1088 tumblr blog sites.
But it downloads nothing.
Dowgrade to TumblThree-v2.4.3-x64-Application
It is working again.
Other issue: since I use W11, filedate of every downloaded image file is 1970.01.01
Desktop (please complete the following information):

TumblThree version: <IP_ADDRESS>
OS: Windows 11 Pro
Browser Edge Chrome
Version 96.0.1054.53

So all your blogs work except one which doesn't download?
Can you try if version 2.4.4 works for you?
We don't have Win11 here yet, but we'll keep an eye on it.
Does anyone else have Win11 and experience the date problem?

I have only one URL (liked/by).
2.4.4 works well.
Downloaded mp4 files have good timestamps.
Downloaded image files (jpg,png,gifv) have bad timestamps.

Hi, I have similar problem.
blog: multiboot2.tumblr.com
After I added blog and select to download everything it doesn't download first post with 2 gifs. Maybe something else also but there is a lot posts and didn't check everything.
Also I get wrong name with video in different post it has default name.
Reblogged both posts so you can find which ones are wrong: https://www.tumblr.com/blog/dajotim937

Hi same issue here.
<IP_ADDRESS> not downloading anythiing, just evaluating.
Previous version does download.

@dajotim937
I created a new issue for that one.
@jjdnl
What blog type are you trying to download?

@thomas694 It's a liked by type of blog

@wacher74 @jjdnl
If you like, you can test whether the upcoming version works for you.

It is working for me, thank you :)
Files are downloaded, and their timestamps are correct.

Yes, working for me too. Thanks

I use the latest version (updated by auto-updater) but it doesn't download... will try to overwrite it with files from zip file

I use the latest version (updated by auto-updater) but it doesn't download... will try to overwrite it with files from zip file

Auto-updater doesn't download because there is nothing download. Actual public release with fix isn't made yet.

Correct. The given link is a version for testing purposes.

The issue has been fixed and closed. You can still comment. Feel free to ask for reopening the issue if needed.


Using "Test Data" and CUDOS deployed via Cloudformation shows "No Data"

Hello!
I am following the workshop: https://dx1572sre29wk.cloudfront.net/cost/200_labs/200_cloud_intelligence/
I have set this up using test data however now that it is deployed via cloudformation my dashboards show no data.

I am able to query the data in athena and customerall (one of the CF deployed datasets) dataset is showing the data.

I think there is an issue with the spice datasets.

I remember there was previously an issue with not having RDS run before in the account so I've deployed a database to test that.

What happens if you query summary view in athena?

SELECT * FROM summary_view LIMIT 10;

Please reopen if still an issue


[BEAM-8396] Default to LOOPBACK mode for local flink runner.

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

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Thanks for the quick review!

The unrelated failing tests is fixed by https://github.com/apache/beam/pull/9845


Misleading information about refresh

This sentence is misleading: "Calculated tables are recalculated if any of the tables they pull data from are refreshed or updated." This is untrue. If your calculated table uses data from a table in DirectQuery, the calculated table will only reflect the changes after the dataset has been refreshed. This needs to be changed. If a table needs to be in DirectQuery mode, so does the calculated table.

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

ID: a23f1335-bb33-544a-67da-006015cfc92f
Version Independent ID: 3e1dc63e-f0ac-5201-c0a5-bc7e4ee30944
Content: Using calculated tables in Power BI Desktop - Power BI
Content Source: powerbi-docs/desktop-calculated-tables.md
Service: powerbi
Sub-service: powerbi-desktop
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Hi @ElegantHaiku , thanks for reaching out to us with your comment. I have forwarded it along to the doc author for consideration.

I have a problem with formatting the value of a  measure in a calculated table. I use UNION to combine two tables and then want to display the result of a new measure in this table as percentage (e.g. 79%). But it is always displayed as 0.79, although the format is set to percentage.
If I do the same measure in the original tables, the result is displayed as desired as 79%.
Thx for an answer.

Thanks for your comment @ElegantHaiku - that clarification is much appreciated, and I've updated the article to include that information.
For @sebohnRAFI, your question looks like a support or community question, rather than a documentation question (though the fix for you might be straightforward). You might find a solution in the Power BI Community, found at https://community.powerbi.com. If not, you can get support by going to https://support.powerbi.com.


Cleanup Java

Hello,
I just cleanup Java (remove singleton, add getter/setter when needed, and rework generic interfaces).
I just checked how to integrate GraphQL, but I don't know what is the role of InventoryItemService.

I am not forgetting you. I just haven't had time to review your work yet. I'm gonna try to spend some time during the long weekend.


Forbid DBAL v4 for now

Symfony doesn't support DBAL 4 yet as it drops support for events that we are using in Messenger for instance (https://github.com/doctrine/dbal/blob/1a307d92f8531b0897176e95040051c7414d80a5/UPGRADE.md?plain=1#L1065).

@stof Done


[DoNotMerge] ssb test

something is wrong with the pinot data loading tool running on GHA -- the data loading tool write to the JVM execution dir by creating and writing into an examples folder that may or may not have write access on the GHA runner


ColorPicker Sizing

I change the default style.json and integrate with FreetypeGenerator, but there is a problem. If I use a big size font, the UI could not be changed, even If setWidth, the layout of ColorPicker seems to be the same.
Hope there is a solution for ColorPicker :(
This is the only widget that works bad with FreetypeFont :(

I found that BasicColorPicker size is locked also, so I could not change it by sizing :(

Have you tried changing Sizes#scaleFactor in your skin.json/usl? Or just generally using X2 Sizes preset.

@kotcrab, That works! But are there anything also affected by Sizes#scaleFactor ? I'm afraid I just want the ColorPicker works expected but other things are going wrong.

It does affect few other widgets (DetailsDialog, FileChooser and TabbedPane) but it was added specifically for bigger font for x2 skin so you should be fine.

I'm going to close this since it looks like this issue was resolved.


[Feature Request] how to update game，

Have you read the Important information text above

[X] Yes i did

Describe the feature
I want to update game ， how can i do it
Additional information

[ ] Would you be willing to help implement this feature?

Final checks

[X] I understand that this is a feature request function. I also unterstand that if i use this to report a bug report, that my issue might be un-answered closed.

Try to restart the docker container? 🤣

Pull the latest image and set ALWAYS_UPDATE_ON_START=true

Yeah that too, thanks @MrMightyNighty 🤣


UPSTREAM: <716>: Disable zones on azure stack cloud

Disable zones on azure stack. Quite rough patch.
Upstream issue: https://github.com/kubernetes-sigs/cloud-provider-azure/issues/715
/hold

/lgtm

/bugzilla refresh

/hold cancel


batch size

Hello,  the research work in this article is particularly meaningful. The batch size in the code is set to 1 by default, but the following problems occur when I set the batch size to 2 or 3. Can you help me solve this problem.
Looking forward to your reply.
File "train.py", line 44, in
model.data_dependent_initialize(data)
File "/home/cvers/Joe/SM/models/cut_model.py", line 176, in data_dependent_initialize
self.compute_G_loss().backward()                   # calculate graidents for G
File "/home/cvers/Joe/SM/models/cut_model.py", line 289, in compute_G_loss
self.loss_SRC, weight = self.calculate_R_loss(real_A_pool, fake_B_pool, epoch=self.train_epoch)
File "/home/cvers/Joe/SM/models/cut_model.py", line 335, in calculate_R_loss
loss_SRC, weight = crit(f_q, f_k, only_weight, epoch)
File "/home/cvers/anaconda3/envs/airnet/lib/python3.8/site-packages/torch/nn/modules/module.py", line 722, in call_impl
result = self.forward(*input, **kwargs)
File "/home/cvers/Joe/SM/models/SRC.py", line 55, in forward
weight_seed.masked_fill(diagonal, -10.0)
RuntimeError: The expanded size of the tensor (768) must match the existing size (256) at non-singleton dimension 2.  Target sizes: [1, 768, 768].  Tensor sizes: [1, 256, 256]

I faced the same question, can you help me to solve it?


Understand how we could build objects into multiple libraries (for make)

Right now, it is assumed that everything is built into one library when using make

Just FYI, BOB does not make that limitation


fix 2fa constant prompt

- What I did

added some documentation for newer contributors and additional logging
remove forced reprompt of OTP, so that we only re-prompt when the token is expired.

Fixes #162, or at least makes it less painful.
A little bit of background...
Upon first login using the 2fa-login endpoint, a token is returned which gives the user full access to all Hub APIs. When refreshing the token, the resulting token has reduced permissions, and so some APIs that initially worked with the first token will now fail. Until the Hub API is modified to allow refreshed tokens to have the same access as the first token, we need to do another prompt of the user's OTP to get another token which gives the tool full access to the Hub APIs.
- How I did it

removed the code that logs in for every "sudo" command.

- How to verify it
Below is output from some commands I ran and the date when they were run to show it working.
Here is the first run with a token that is expired.
❯ date -u && go run main.go account info
Mon Feb  1 15:12:18 UTC 2021
2FA required, please provide the 6 digit code: XXXXXX
Name:           ahokanson
Full name:      Alex Hokanson
Company:        Docker, Inc
Location:
Joined:         17 months ago
Plan:           free
Limits:
  Seats:                1/1
  Private repositories: 1/1
  Teams:                unlimited
  Collaborators:        unlimited
  Parallel builds:      1

Then we run it again within the TTL of the token (30 minutes) and no reprompting of the OTP is required.
❯ date -u && go run main.go account info
Mon Feb  1 15:12:39 UTC 2021
Name:           ahokanson
Full name:      Alex Hokanson
Company:        Docker, Inc
Location:
Joined:         17 months ago
Plan:           free
Limits:
  Seats:                1/1
  Private repositories: 1/1
  Teams:                unlimited
  Collaborators:        unlimited
  Parallel builds:      1

One last run shows that the token has expired, again, and we are correctly prompted to provide the OTP for 2FA authentication
❯ date -u && go run main.go account info
Mon Feb  1 15:56:01 UTC 2021
2FA required, please provide the 6 digit code: XXXXXX
Name:           ahokanson
Full name:      Alex Hokanson
Company:        Docker, Inc
Location:
Joined:         17 months ago
Plan:           free
Limits:
  Seats:                1/1
  Private repositories: 1/1
  Teams:                unlimited
  Collaborators:        unlimited
  Parallel builds:      1

- Description for the changelog

added some documentation for newer contributors and additional logging
remove forced reprompt of OTP.

- A picture of a cute animal (not mandatory)

PTAL @silvin-lubecki @rumpl

@ingshtrom correct me if I'm wrong, but I think that this way all hub-tool commands will prompt for a 6-digit code if 2FA is enabled, right? It means the sudo annotations aren't used anymore? 🤔

Good call. That isn't what we want. Although, that is likely what is already happening since https://github.com/docker/hub-tool/pull/167/files#diff-6830a710a038a65c376a407bfafe6dbcba1561c4994fcfb20aff88375403ac37R86 hasn't changed. I'll take a look at that and post a test here once I check it out. Thanks!

I wonder if we can tell if the stored token is a refreshed token (with less rights) or a new token, with full rights. Maybe we should store refresh tokens and new tokens separately, and depending if the command is a sudo one or not, we take one token or the other 🤔
It adds a lot of complexity, but I don't see any other option 😞

stale, and I do not have any intention of working further on this


RequireHttpsAttribute local requests

Usually http to https redirection is needed only for remote requests. Common case is development environment. Now developers need to use workarounds like this. What about skipping http to https redirection by default on local requests, or creating a property on the attribute that will allow to do so?

We don't want to special case localhost for such a security sensitive scenario. Note that setting up HTTPS in development is pretty easy now with IIS Express.
Alternatively, you can implement a filter override semantic based on the environment you are running in. See http://www.strathweb.com/2015/02/overriding-filters-asp-net-mvc-6/ for an example of how to do this.


api: add method to get the iana value for the negotiated cipher suite

Description of changes:
Currently there's no way to get the IANA value for a connection's negotiated cipher suite. There is the s2n_connection_get_cipher method which returns a const char *, but this is less than ideal when trying to match on values programmatically.
This change adds a s2n_connection_get_cipher_iana_value method which takes two byte pointers and sets those to the negotiated cipher suite. I feel like this is the interface with the fewest sharp edges.
The other options I considered were:

Taking a uint16_t. It's nice to just pass a single pointer, but it leads to some ambiguity in the endianness of the contained value.
Taking a uint8_t * and requiring that there be 2 elements. This is impossible to enforce and hard to document.

Testing:
I added some checks alongside the current tests for the s2n_connection_get_cipher method.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Do you want to put this API with the "semi-public" QUIC APIs for now, or do you think it's worth adding to the main APIs?

I think this is worth having outside of QUIC.


unable to change / remove / add new 2FA device

I am trying to change my 2FA app, however when trying to add a new one, the error is
"Error Account cannot be linked to more than one authentication application at a time". The "remove" option on 2FA app is also greyed.
I removed the creds from my current app, but it didn't impact anything (I didn't think it would either).
Can currently only log in using recovery codes. Tried using one of them as TOTP security key, but it didn't work.
Looks like manual help is needed..?

cc @di @ristomcgehee  May be related to recent changes regarding handling of last 2FA method?

I think this is a duplicate of #14257 and will be resolved by #14260.


chore: create release 0.12.2

What type of PR is this?
/kind chore
What does this PR do / why we need it:
create release 0.12.2

Are we planning a new upstream operator release?

I think the fix that was merged should have a specific argocd-operator release as well for the feature to work if used only via argocd-operator. Although I am okay to skip publishing the image if needed.


Use PlanEnumeration in DetermineJoinDistributionType and ReorderJoins

Supersedes #16

general comments

all the changes in DetermineJoinDistributionType.java should generally go as fixups to the CBO commit that adds cost-based decision there.
you need to update the documentation; it currently says that AUTOMATIC may flip join sides regardless is COST_BASED

i'd like to get some confirmation if this is really what we want? @sopel39 @ilfrin @losipiuk let's talk offline

general comments (cont.)

do we need this Q1?


Event Sourcing Question

I really enjoyed your book, Developing Reactive Microservices and appreciated the Cargo tracker example code. I had a question, specifically around event sourcing. My understanding is event sourcing provides a clean solution to the classic problem of ensuring that both state updates and events are sent in a single operation. It solves this problem by essentially removing a separate state update and instead having the events be the authority and state can be built from those events later. This article provides a great description:
https://www.nginx.com/blog/event-driven-data-management-microservices/
Given that, I'm confused by the cargo tracker example code. When I look at RegistrationServiceImpl.register(), a Cargo immutable is published to the "topic" topic, then the RegisterCargo command is sent to the PersistentEntity (CargoEntity).
https://github.com/lagom/activator-lagom-cargotracker/blob/master/registration-impl/src/main/java/sample/cargotracker/registration/impl/RegistrationServiceImpl.java#L65-L71
I have two issues/questions about this.
First, the Cargo is published to the topic before the CargoEntity has been called, which determines whether it's a valid command or not, given the user inputs. This causes invalid Cargo objects to be published to the topic, which seems like undesirable behavior to me. This is a minor point, but I wanted to bring it up to make sure I'm not missing something here.
Second, and more importantly, the topic appears to be the mechanism for sending events to other services (or in this case the same service). Is that correct or should I be viewing topics as a way to send messages between actors within the same microservice? If topics are the way to send events to other services, then don't you have the same problem of sending a command to the PersistentEntity and then separately publishing an event to a topic? If the process crashes between these operations, you would persist the event generated by the command, but the Cargo topic publish would be lost. Does Lagom somehow ensure both of these happen, maybe by retrying the request?
If topics are not the mechanism used to publish events to other services, then how would you do this in lagom? Are you supposed to publish events to a topic as a side effect in your event handler function in the persistent entity class, i.e., in here?
https://github.com/lagom/activator-lagom-cargotracker/blob/master/registration-impl/src/main/java/sample/cargotracker/registration/impl/CargoEntity.java#L70-L75
I'd appreciate any clarifications you can provide. I'm very excited about Lagom's potential and am trying to understand how I can leverage it.

Hi @jlhood, we've only just noticed this so probably you're not interested in an answer anymore, but the issue tracker is not a good place to ask questions. In future, please ask questions on the mailing list or in the gitter channel. Thanks!


Fix Share somewhere in assign task shows a wrong report

Details

In the assign task page, when we select an assignee, it will automatically find the report of the assignee (using getChatByParticipants) and set it as the value of Share somewhere. However, getChatByParticipants may find a wrong report that has the same participant, for example, task report. This PR make sure getChatByParticipants filtering out task, money request, chat room, and policy expense report.
Fixed Issues

$ https://github.com/Expensify/App/issues/22433
PROPOSAL: https://github.com/Expensify/App/issues/22433#issuecomment-1626989267
Tests

Same as QA Steps

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

Offline tests

Same as QA Steps
QA Steps

Prerequisite: user A assigns a task to user B
As user A:

Open Assign Task
Enter any title and go next
Open the assignee page
Select user B
Verify Share somewhere shows user B

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

PR Author Checklist

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/50919443/74f78597-c9c1-4970-89f0-26a67d09c738

Mobile Web - Chrome

https://github.com/Expensify/App/assets/50919443/2c85d6ea-747f-4434-84da-65fc97bf7117

Mobile Web - Safari

https://github.com/Expensify/App/assets/50919443/7b7bcb6d-68ad-40fa-8f6b-b3f6d6d557d9

Desktop

https://github.com/Expensify/App/assets/50919443/63cb4f3c-a77f-4905-9d69-5fb75c56ce17

iOS

https://github.com/Expensify/App/assets/50919443/0da28c72-bff9-4870-a366-13de41043067

Android

https://github.com/Expensify/App/assets/50919443/2f40460e-a37a-4ed3-a45d-6782db64d3ee

Reviewer Checklist

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

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

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

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

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

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

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

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

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

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

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

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

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

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/46707890/ba5f31b8-c886-4269-b431-fa4bb497932a

Mobile Web - Chrome

https://github.com/Expensify/App/assets/46707890/bae52515-4e1c-4621-8ee9-1ceadcadde6b

Mobile Web - Safari

https://github.com/Expensify/App/assets/46707890/0b73c8d7-747c-4413-9fda-a13fc70e2a35

Desktop

https://github.com/Expensify/App/assets/46707890/2dbb32e9-c530-4179-8b0d-21010b77cc79

iOS

https://github.com/Expensify/App/assets/46707890/16186317-025d-42bd-9535-4b8ff4606f73

Android

https://github.com/Expensify/App/assets/46707890/6019b1b3-6009-40e7-8b6a-69f6b16811af

@bernhardoj Thank you for checking all the instances of getChatByParticipants. Much appreciated.

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

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.45-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Update coverage, javascript and rust gh action to ignore docs/** pa…

…th updates

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 99.02%

Totals

Change from base Build<PHONE_NUMBER>:
0.08%

Covered Lines:
44570

Relevant Lines:
45011

💛  - Coveralls


Deploying a model from a local path using VLLM does not automatically utilize multiple GPUs

Describe the bug

Steps to reproduce

Deploy a Qwen2.5-7B-Instruct non-gguf model form Local Path.
Check the instance deployment.

Result

It only uses one GPU, which results in  in OOM.

torch.OutOfMemoryError: Error in model execution (input dumped to /tmp/err_execute_model_input_20241108-023641.pkl): CUDA out of memory. Tried to allocate 296.00 MiB. GPU 0 has a total capacity of 15.61 GiB of which 55.06 MiB is free. Process 1388164 has 246.00 MiB memory in use. Including non-PyTorch memory, this process has 15.29 GiB memory in use. Of the allocated memory 14.94 GiB is allocated by PyTorch, and 47.04 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True to avoid fragmentation.  See documentation for Memory Management

Expected behavior

Environment

GPUStack version: main(fe77175)
OS: Ubuntu 22.04
GPU: NVIDIA GeForce RTX 4080 SUPER * 2

Additional context
Add any other context about the problem here.

Verified on main  27fa7fe


Trained model not accessible with link

The link provided in the readme is for a private file not available to download.

Changed sharing permissions, it should be open now.


PID mode not following threads

Description
As reported in following issue https://github.com/DataDog/ddprof/issues/276, ddprof in pid mode does not catch the activity of all threads.
# Pid mode
ddprof -p 94375

Workaround
For now we recommend using ddprof in wrapper mode
./ddprof ./my_exe

Closing against https://github.com/DataDog/ddprof/pull/389
This will be available as of ddprof 0.17.0 (which is available as a pre-release)


RESTEASY-1176

Allow ':' in Basic Auth passwords.
https://issues.jboss.org/browse/RESTEASY-1176
Also, reversing a test in ResteasyProviderFactory for RESTEASY-1284.

Merged after having succesfully tested locally


What is the version of tensorflow?

What is the version of tensorflow?

I have used different versions, such as 1.8 and 1.11, but I don't see any problems in using other versions.

Thank you for your reply.
But hdrcnn_predict.py is executed
raceback (most recent call last):
   File "hdrcnn_predict.py", line 42, in
     import tensorlayer as tl
   File "/usr/local/lib/python3.6/dist-packages/tensorlayer/init.py", line 27, in
     "TensorLayer does not support Tensorflow version older than 2.0.0. \ N"
RuntimeError: TensorLayer does not support Tensorflow version older than 2.0.0.
Please update Tensorflow with:
  -pip install --upgrade tensorflow
  -pip install --upgrade tensorflow-gpu
I get an error.
Should Tensorflow version be newer than 2.0 to support TensorLayer?
I am using googlecolab

I don't know about the dependencies of Tensorlayer, but from your error message I guess you have to downgrade it to work with your Tensorflow install.
See e.g. this issue


Revisit INFO logs

Closes https://github.com/api3dao/airseeker-v2/issues/189
Closes https://github.com/api3dao/airseeker-v2/issues/198
Rationale
The INFO logs logged very little. This is now changed because both "data fetching loop" and "update feeds loops" now log a message. I went through each log one-by-one and I updated the severity whenever I felt it's a good idea.
I also changed that we log the chain name instead of chain ID.

Here can be set to WARN.

FYI, a bit related https://github.com/api3dao/airseeker-v2/issues/218


Fix string oid graph transformation bug

What do these changes do?

no need to call the vertex map construct, since every worker has the complete global vertex map.

@pwrliang I have reverted the parallel edge and vertex code, can't you take a look again?