why the Validation-accuracy drops so much when I use  mx.mod.BucketingModule() to redefine a symbol model?

this is a very important problem

it looks that the training con't be convergent  after I use:
    model=   mx.mod.BucketingModule(         sym_gen             = sym_gen,         default_bucket_key  = data_train.default_bucket_key,         context             = [mx.gpu(int(i)) for i in range(1)])

well ,while I turn off the batch_size and learning_rate ,it looks that the Validation-accuracy runs up to the same level  as it was


Where does the package advtools comes from.

->models/imagenet.py: line 5;
from advtools.utils import normalize_model, requires_grad_
What is advtools here

Hi,
advtools does not correspond to any published package. It was the initial name of the adversarial library package before it was released. It can be replaced by adv_lib.

Thanks for the quick resolution


Removed React Native video and added React Native playlist

What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
There was video of React Native but React Native playlist needed so I added it.
How do we know it's really free?
It's publicly available on Youtube
For book lists, is it a book? For course lists, is it a course? etc.
It's a course of React Native
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Closing as duplicate of #11571.


Identity factors in sum_product_edges

When sum_product_edges sees a node that appears both in edges and ext, it duplicates the node and puts an identity factor between them. This keeps things simple but is not very efficient. It would be better if sum_product_edges can avoid the duplication by returning some extra info. Hopefully that extra info can also get rid of the handling of disconnected external nodes, which is also not very efficient.

Probably related: https://github.com/diprism/perpl/issues/97


Update README.md

This pull request has been deployed to Vercel.

Latest commit:
5edc8fe

✅ Preview:
https://refdocs-ag2hba6rb-rootcircle.vercel.app

🔍 Inspect:
https://vercel.com/rootcircle/refdocs-io/CuBd1VgKvUKeJA43Ad9VM25whEbB

View Workflow Logs


editorInterface methods do not reset custom editor extension

Summary
Fix for a new custom editor extensions feature.
Description
Change in editorInterface implementation so migrations don't override editor property if it was set already.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Base operation

This creates the BaseOperation superclass for all operations to inherit from. This superclass provides for additional functionality for all operations, like the runner_parameters field.
Tests have also been added to ensure proper initialization of fields of some operations. In the future, tests should be added for all operation fields.

Needs formatting, but otherwise looks like a clean method.


[stable/stackdriver-exporter] update k8s deployement api version

As of v1.16, k8s won't accept a deployment with apps/v1beta1
or apps/v1beta2 apiVersion. The accepted apiVersion is apps/v1
that is available since k8s v1.9.
See https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16
@apenney
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @viglesiasce

/ok-to-test

Hey @paulczar @cpanato @viglesiasce sorry not really sure what the process is to get it reviewed? :))

Hey @paulczar @cpanato @viglesiasce
Could you review this PR, please?
This feature is really needed on 1.16 and more version of K8s
Thank you! :)


Recommended graphics card for high resolution point clouds?

Hello,
I managed to get the drivers running with the depth processing being done with opencl and the depth registration being done with cpu (some buffer errors appear if trying to get it to work through opencl), the graphics card I used for this task was the Nvidia 8800 GTS which is quite an old graphics card.
I manage to display high/low resolution images with it just fine (most of the time...), the viewer runs on 30 fps using the lower resolution images and around 11 fps when displaying the higher resolution ones but if I try to display the high resolution point clouds everything freezes/crashes and I have to manually reset the computer (the screen turns either green or black and just stays there while 2 lighs flicker on the keyboard).
I assume this has something to do with the graphics card since it is quite old and also has some flickering going on.
Do you maybe know what range Nvidia cards would do a decent/good job with it or rather what card are you using if you can get high resolution point cloud to display properly?

Hi,
if you look at the images using the viewer on the same machine the kinect is connected to, you might want to add the raw parameter of the viewer. This way the images don't get compressed and decompressed, which saves a lot CPU time.
Well I used a nvidia 640, a 770 and a 970. They all do the job fine. What are the timings printed on the console? Just past some of the console output here.
What CPU are you using? How is the CPU load? While running kinect2 you could also look at the cpu load with htop for example.

Never mind, getting a new graphics card fixed all the issues I had at that moment. Got a 960 and things are running quite well for the time being.


deps: update for https://github.com/celestiaorg/celestia-node/pull/1913 and v0.8.0 and common docker pipeline

Overview
https://github.com/celestiaorg/celestia-node/pull/1913
Resolves #17 and #11

Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[x] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates
[x] Linked issues closed with keywords

Logs from run with v0.8.0-rc2: https://app.warp.dev/block/eafrK0V7JZaJseW42OnOmz

@jrmanes - accidentally committed to my fork. adds a common CI pipeline here too

Yeah, I know, I only tagged node because error was related. Thanks for picking this up 🙏


Prevent setting newTag in kustomization file

This PR updates KOTS to allow different tags from the same image to be used. The current KOTS implementation generates a Kustomize patch to replace images after specifying the local registry. This doesn't work when there are two different tags in use by the same image (see kubernetes-sigs/kustomize#2701). In addition, the type that we use from Kustomize plainly states that the tag should not be set, and does not have a field for tag to be set (https://github.com/kubernetes-sigs/kustomize/blob/1c24fe7d16ec0031b68b946afbb2f9d70b7b0937/api/types/image.go#L9)
There are several options available here, but we want KOTS to stick closely to the upstream tools. Currently KOTS always uses the same tag, so removing the newTag field from this Kustomization before writing the file results in the correct behavior because Kustomize will retain each tag separately.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Update README.md add videos and pictures

Update README.md add videos and pictures
Updates the README.md to add pictures and videos and a more in-depth
explanation for the extension.

DO NOT MERGE UNTIL:
https://quay.io/bootsy/bootc-extension is publically accessible.
Can you flip the switch to make it public @benoitf ?

@cdrage we should publish to ghcr.io now

I mean, the image

@cdrage we should publish to ghcr.io now

Are you able to set it up? I don't believe I have permissions for the correct repo. Let me know which org / repo you choose and I can update the README.md
For the README.md I've updated it to use images / videos from the github storage rather than our own doc.

@cdrage https://github.com/containers/podman-desktop-extension-bootc/pull/56

Thank you @cdrage for working on this documentation!

@cdrage https://github.com/containers/podman-desktop-extension-bootc/pkgs/container/podman-desktop-extension-bootc

I've updated the README with the new link, and I can confirm I'm able to pull / install it now (see the new video I've added to the README):
https://github.com/containers/podman-desktop-extension-bootc/assets/6422176/99cad4b3-77b9-4118-85e9-e785c26641ec


/get occasionally returns 204 instead of 200

It's my understanding that /get should always return a JSON payload. However, when running our test suite for Alamofire, we may see a test fail due to /get returning a 204 instead.
Also, in general, what sort of traffic limits does httpbin.org have? We run our test suite against it in irregular bursts and there are occasional failures when our 5 second request timeouts trigger. Aside from running our own instance, is there a good way to avoid these?

Intermediaries are perfectly allowed to return a 204. By which I mean, relying on httpbin.org will never be fixed since the code itself very clearly only ever returns a 200 with a JSON body.


Proposal for eth_getCodeHash

Motivation
In certain cases, knowing whether an address is a contract or not can be useful. A number of users/devs face a common issue that they are interacting with a contract on an incorrect network. The eth_estimateGas returns a value (21000 + calldata estimate), the transaction goes through but nothing happens. For eth_calls, it returns '0x' and that's what happens when a contract reverts with empty revert data. This makes beginners quite confused about why their code doesn't emit logs or reverts when there's no revert in it.
Clientside libraries could do a preflight check to see if the user/dev is trying to interact with an account that is not an address and throw a useful error. The eth_getCode exists however it's not cheap, due to the huge payload. However the Account struct in already contains a codeHash. However, there doesn't seem to be a way to get that directly.
Spec
eth_getCodeHash takes in an account address and results with the codeHash 32 bytes value.

The method generally makes sense to me and is straightforward to implement. I'm curious if you can expand on "not cheap" though? Max contract size is 24 kilobytes -- this seems to be quite cheap to request when webpages are often in the megabytes?

I mostly had in mind that some websocket providers charge on bandwidth, but later I checked and the actual charge is not very significant because the use case would involve occasional queries and mostly no runtime queries. It doesn't seem that the method is necessary hence closing this issue.


Add option for bootstrapped effect sizes

Closes #18
Adds option to provide parameter bootstrap_iterations to calculate bootstrapped CIs. Reshuffles data with replacement to generate 95% CI.
Also refactors some of the DataHandler internals to clean up code. CC @dhakim87 who had the idea for the reorganization of _bulk_power_analysis such that we can drop the LRU caching.
TODO: Update docstrings

Ha! Just saw that this is a draft ..

No problem - gonna try this out on some real data to make sure it works in practice. Also wanna benchmark the performance a little bit since this changes a good deal of the internals.


Take me (viric) out of most maintenance

Since years I'm not maintaining anything of the list below other
than some updates when I needed them for some reason. Other people
is doing that maintenance on my behalf so I better take me out but
for very few packages. Finally!

I opened the PR just in case someone wants to take over the maintenance declaration before I merge this.

@GrahamcOfBorg eval

@viric does list contain packages that do no longer work and should be better marked as broken?

@Mic92 there are some packages in the list that are marked as broken.

:+1:  Removing yourself from the list shouldn't make breakages worse (or better).  Still, if you know that some are broken, please mark them so :-)

I have no idea whether some are broken. Those which I use often they are not broken.
Ok I merge.


Replace map flatten with flat_map

Replace map flatten with flat_map
Using flat_map over map.flatten is 1.6 faster according to Enumerable#map...Array#flatten vs Enumerable#flat_map.
Failing specs are unrelated i.e. they also fail on master branch.

Thank you 😄

Failing specs are unrelated i.e. they also fail on master branch.

Yeah it's unfortunate but the CI only passes with dry-schema from master. It's a temporary situation of course, just need to release new dry-schema 😅


add volume filesystem usage metrics

This patch add filesystem metrics (rawfile_volume_fs_used_bytes and rawfile_volume_fs_total_bytes) for rawfile volume. They represent the actual space usage from filesystem perspective:
# HELP rawfile_volume_fs_used_bytes Used space of volume filesystem
# TYPE rawfile_volume_fs_used_bytes gauge
rawfile_volume_fs_used_bytes{device="/dev/loop0",fstype="ext4",img="/data/pvc-c4ecfd41-9966-44fd-bd76-a88c34edc884/disk.img",loop="/dev/loop0",mountpoint="/var/lib/kubelet/plugins/kubernetes.io/csi/rawfile.csi.openebs.io/60498c10621c39b8674c272877221113fa5b1afc104a0826a8b4bb632f62e6b5/globalmount/mount",node="node-a",volume="pvc-c4ecfd41-9966-44fd-bd76-a88c34edc884"} 1.080041472e+09
# HELP rawfile_volume_fs_total_bytes Size of volume filesystem
# TYPE rawfile_volume_fs_total_bytes gauge
rawfile_volume_fs_total_bytes{device="/dev/loop0",fstype="ext4",img="/data/pvc-c4ecfd41-9966-44fd-bd76-a88c34edc884/disk.img",loop="/dev/loop0",mountpoint="/var/lib/kubelet/plugins/kubernetes.io/csi/rawfile.csi.openebs.io/60498c10621c39b8674c272877221113fa5b1afc104a0826a8b4bb632f62e6b5/globalmount/mount",node="node-a",volume="pvc-c4ecfd41-9966-44fd-bd76-a88c34edc884"} 2.046640128e+09

We used to actually expose those metrics, but apparently kubelet extracts the same metrics using CSI calls and exposes them as kubelet_volume_stats_capacity_bytes and kubelet_volume_stats_used_bytes, and that's why I dropped those metrics from the metrics endpoint. Will you please explain your usecase and why those metrics are not good enough?

thanks, kubelet_volume_stats_**  metrics are enough for us.


Roaring -- Flip

Implement the Flip method in RoaringBitset. It should add an index to the set if it isn't already a member or remove it from the set if it is a member. A test for this is in the BaseBitSetTests class.

Got this one.


Scaladoc Unavailable from Link

I attempted to follow the link to the scaladoc from http://quasar-analytics.org/docs/scaladoc/ which directed me to http://<IP_ADDRESS>:8180/job/Quasar/lastSuccessfulBuild/artifact/core/target/scala-2.11/api/index.html#package which was either unavailable or blocked in some manner.
I confirmed with isitup that it wasn't just me.

Yeah we should change the link so that it points to javadoc.io or something similar, since quasar's javadoc is all on maven central.


[BUG] Ocaml LSP

What did you expect to happen?
...
Pass the +lsp flag to the ocaml language in init.el to use the ocaml-language-server in Tuareg Mode
What actually happened?
...
LSP: No LSP server for tuareg-mode(check lsp-log)
Additional details:

Include a link to your private config
Include screenshots/casts of your issue
If you mention key sequences, include what commands they're bound to (use SPC h k KEY or C-h h k KEY to inspect keys).
Include any warnings or errors logged to *Messages* (use M-x view-echo-area-messages to see it).

If an error message is involved include a backtrace of it.
How to acquire a backtrace:
https://github.com/hlissner/doom-emacs/blob/develop/docs/getting_started.org#how-to-extract-a-backtrace-from-an-error

Steps to reproduce:

Select these example steps,
Delete them,
And replace them with precise steps to reproduce your issue.
Fill in "system information" below.

System information:

Place the output of `M-x doom/info` or `~/.emacs.d/bin/doom info` here.

Please fill out the "system information" section of the issue template.

Did you run doom refresh on the command line after activating :lang (ocaml +lsp)?

I did run doom refresh upon adding (ocaml +lsp) but I still get the same error. The mode in the bottom right corner also shows Tuareg// instead of Tuareg (which is shown without +lsp modifier)

If you open up a shell and run which ocaml-language-server and which ocaml-lsp-server, do either of these commands print out a path?
If so, then try running ~/.emacs.d/bin/doom env to generate an envvar file (creates a snaptshot of your shell environment that doom will load at startup).
If neither do, then it would seem neither lsp server was successfully installed.

Upon reinstallation, ocaml-language-server does work but the ocaml-lsp-server does not, as it is also undergoing constant development. I'm sure once the package is officially on OPAM it will work as required.


Autobuild and Publish Docker Image to Docker Hub

This should auto build and branches in the git repo (as well as any tags) and then upload them to Docker Hub with the correct image name.
It is worth noting that ANY tag that is created will push to the stable image so we may want to create a naming scheme to narrow this so tags only containing a certain prefix get uploaded to stable if we want to use tags for anything other than stable builds. All tags will also be pushed to their own image with the tag as the image name.
Any build that is not tagged will be uploaded as beta-branchname where branchname is the name of the branch. If there is already a beta-branchname it will be overwritten (meaning we dont have tonnes of images for each commit).
I also modified the dockerfile to use nodejs 18 and to install the node modules in the application directory which is where they are supposed to be stored (there is no need to store them in /tmp on an image which should be static).
This is a draft PR as these changes need further testing and reviewing.

fixed docker hub login (turns out usernames are case sensitive outside of the website) - build now failing and depends on #13 #14

to install the node modules in the application directory which is where they are supposed to be stored (there is no need to store them in /tmp on an image which should be static).

The reason it's put into /tmp is so that docker will cache things and won't try to yarn install when nothing has changed https://medium.com/hackernoon/using-yarn-with-docker-c116ad289d56
Don't worry about changing the dockerfile for now, otherwise we could get some horrible merge conflicts


Possibility of porting entire capabilities of libvips into sharp

I was trying to get some pixel-by-pixel manipulation done using Node and came across this library. I asked a doubt regarding what I wanted to get done and he sent me a snippet for Python which used the bandsplit() and bandjoin() functions . I looked at the sharp documentation for the JS equivalent, but it seems that sharp only has a subset of the capabilities offered by libvips.
Is there a chance that sharp might grow to include all the features of libvips or is this intended to be a lightweight library?

Hello, did you see #241, a discussion of how this might be achieved?

Hi @lovell,
I read the discussion as well as the discussion on libvips on the same(https://github.com/jcupitt/libvips/issues/103). The last comment on these were made in September and I wonder what happened to those projects.

#241 is still open and therefore under active consideration. Shall we close this question and continue any discussion there?


Devcontainer

This pull request adds the files needed to use devcontainers.
The devcontainer generates a container with java 8 and maven 3.5.4. The base image uses node.js to integrate the SonarCloud extension. Other usefull features already presents in the image are act, git, github cli and the docker-outside-docker extension to connect to the host's docker daemon socket.
It also starts a container with a mysql (v5.7) database with the correct number of users and schemas. To do so and to allow the customization of the related environment variables, at container start up, a bash script executes a set of sql commands applying the environment variables values. The sql commands creates 2 databases and 2 users (each can access only one schema). Each user has all privileges.

Note: To override .devcontainer/compose.yml env var default values developers can create a .devcontainer/.env file.

Note: Since mysql v8.0, to execute the XA RECOVER command, each user must have admin rights; so, they need the XA_RECOVER_ADMIN grant type on all databases tables.

To easy application start up, this PR provides a launch.json file to start the application. In order to track this file this PR changes the .gitignore file.
The .gitignore file has been also modified to ignore the security.yml files (which should be generated only in development mode, use application.yml in production) and the ignite folder which is generated when launching the application.

Rebase branch on master. Previously, it started from release 2.8.0 and had merge conflicts.


Apply redesign to sign page

[x] Overall page style (#305)
[x] Design updates for the signature list (#307)
[x] Add the mobile sign button and modal form (#322)
[x] Working share buttons (#336)
[x] "Thank you" page style (#333)
[x] replace modal with inline form (#384 )
[x]  petition messages (#383)
[x] Thanks redirect message (#383)

Related issue for mobile signing: https://github.com/MoveOnOrg/giraffe/issues/76

The basic work has been done. We can file new issues if we find anything else to do.


Remove ImportPublicKey from the crypto interface

RELEASE_NOTES=n/a
Signed-off-by: Dominik Schulz<EMAIL_ADDRESS>

Codecov Report

Merging #1726 (09064b7) into master (78aaad1) will decrease coverage by 0.04%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1726      +/-   ##
==========================================
- Coverage   58.11%   58.07%   -0.04%
==========================================
  Files         189      189
  Lines        9035     9041       +6
==========================================
  Hits         5250     5250
- Misses       3193     3199       +6
  Partials      592      592

Impacted Files
Coverage Δ

internal/backend/crypto.go
70.83% <ø> (ø)

internal/backend/crypto/age/unsupported.go
0.00% <ø> (ø)

internal/store/leaf/crypto.go
35.38% <0.00%> (-2.32%)
:arrow_down:

internal/backend/crypto/age/askpass.go
6.90% <0.00%> (-0.80%)
:arrow_down:

Continue to review full report at Codecov.

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

Codecov Report

Merging #1726 (09064b7) into master (78aaad1) will decrease coverage by 0.04%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1726      +/-   ##
==========================================
- Coverage   58.11%   58.07%   -0.04%
==========================================
  Files         189      189
  Lines        9035     9041       +6
==========================================
  Hits         5250     5250
- Misses       3193     3199       +6
  Partials      592      592

Impacted Files
Coverage Δ

internal/backend/crypto.go
70.83% <ø> (ø)

internal/backend/crypto/age/unsupported.go
0.00% <ø> (ø)

internal/store/leaf/crypto.go
35.38% <0.00%> (-2.32%)
:arrow_down:

internal/backend/crypto/age/askpass.go
6.90% <0.00%> (-0.80%)
:arrow_down:

Continue to review full report at Codecov.

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


fix global key error

Description
This is a draft to fix global key error.
Previously we reserve global key and instantly through error if we detect the global key has been reserved before. However, there is cases where the previous reserve global key is not valid and will eventually be removed.
This pr change the way we throw global key error that we allow every global key reservations and record them. We only verify the global key reservations at the end of build stage when every thing is finalized.
Related Issues
https://github.com/flutter/flutter/issues/43780
Tests
I added the following tests:
Replace this with a list of the tests that you added as part of this PR. A change in behaviour with no test covering it
will likely get reverted accidentally sooner or later. PRs must include tests for all changed/updated/fixed behaviors. See Test Coverage.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

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

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[ ] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: Replace with a link to your migration guide

@goderbauer @Hixie
This is a draft. Some of the changes are on the part of code i am not familiar with. Let me know what do you think about this approach
also cc @krisgiesing @HansMuller  in case you are interested

Can you verify that we have tests for all the cases that Ian mentioned on the other PR? If not, please add them.

The suggested test list is at: https://github.com/flutter/flutter/issues/43780#issuecomment-561900614

We are missing

A widget with key Z is in the tree. Its parent A and an unrelated widget B are both marked dirty. B is a layout builder. A rebuilds and removes its child, B, in a different build scope in the same frame, rebuilds and adds a child with key Z of the same type. We must not report any duplicates.
A widget with key Z is in the tree. Its parent A and an unrelated widget B are both marked dirty. A is a layout builder. B rebuilds and adds a child with key Z of the same type, then A, in a different build scope in the same frame, rebuilds and removes its child. We must not report any duplicates.
A widget with key X is in the tree. Later, an unrelated widget is marked dirty, rebuilds, and adds a new widget with key X (not the same type as the original X). Even though only one widget was added that frame, we must detect that there are two Xs in the tree (without a global tree walk which is prohibitively expensive).
A widget with key Y is in the tree. An unrelated widget is marked dirty, and it adds a child with key Y, having the same type as the original widget with key Y, causing the original Y's element to be reparented. The original parent of Y is not dirtied. We must detect that there are now logically two Ys in the tree (even though actually there's only one, because it was reparented).

I don't think our code can detect the last one prior to my current change, too. That is something we should fix.

added all the relevant tests

cc @HansMuller

Assuming you've added all the tests, can you reply to my comment in the issue and point to the test for each bullet point in my list? I wasn't able to quickly find each one.

@Hixie  thanks for reviewing. I addressed all comments and this is ready for review

Also: Cirrus seems unhappy.

This looks pretty good. However, Cirrus seems pretty unhappy.

I think i found the real issue, we should not have one child attached to two place even if there is global key duplication, it should always detach from parent and move to a new place.
The issue is with MultiChildRenderObjectElement.update.
https://github.com/flutter/flutter/blob/a1bf03f87ae3953f51be2e6d3e0421e44cc55e47/packages/flutter/lib/src/widgets/framework.dart#L5641
It is possible forgetchild is called during updateChildren, and it will cause a problem if forgetchild is called on child that has been already finished updating in updateChildren. What would happen is that the forgotten child won't gets update again and _forgottenChildren will be clear after updateChildren. This cause a child that is supposed to be removed but does not actually gets removed, so we are left with one child in two places.

I think i found the real issue, we should not have one child attached to two place even if there is global key duplication, it should always detach from parent and move to a new place.
The issue is with MultiChildRenderObjectElement.update.
https://github.com/flutter/flutter/blob/a1bf03f87ae3953f51be2e6d3e0421e44cc55e47/packages/flutter/lib/src/widgets/framework.dart#L5641
It is possible forgetchild is called during updateChildren, and it will cause a problem if forgetchild is called on child that has been already finished updating in updateChildren. What would happen is that the forgotten child won't gets update again and _forgottenChildren will be clear after updateChildren. This cause a child that is supposed to be removed but does not actually gets removed, so we are left with one child in two places.

Fascinating! Just to make sure I understand, you are saying this is the real root cause of the original issue? (As opposed to the reason that Cirrus is unhappy with this PR.)
If so that seems to suggest a very different direction for the fix - although adding tests for all the cases we've enumerated still seems useful.

@krisgiesing
Oh sorry for the confusion, I meant the issue where element tree become broken during test after this pr. The original https://github.com/flutter/flutter/issues/43780 still requires refactoring to global key duplication detection.

Looks like some tests are failing now (see Cirrus).

It is possible forgetchild is called during updateChildren, and it will cause a problem if forgetchild is called on child that has already finished updating in updateChildren. What would happen is that the forgotten child won't gets update again and _forgottenChildren will be clear after updateChildren. This cause a child that is supposed to be removed but does not actually gets removed, so we are left with one child in two places.

I don't fully understand how this explains why we need the try/catch in the global key verification logic. That verification now happens after the tree is updated, no? So updateChildren is not on the stack anymore?

@goderbauer this is ready for another review


Give Admins Ability to Create SL Course from Course Management Page

In the Service Learning Course Proposal Management page, Admins need the ability to add a course through the button below.  Right now it does nothing.  We'd like it to SL course creation interface.

There is no link to this page in the sidebar.  The route is: :8080/courseManagement/
(Whoever picks this issue up should link this page in the sidebar in this same issue)

 CELTS #231: Give Admins Ability to Create SL Course from Course Management Page


[BUG] First node chain modify time point

Type
Bug
Kapacitor version 1.4
I used the stable helm charts for the installation.
docker is kapacitor:1.4-alpine
Description
After applying the first node to an influx node, the first point time has been modified to today date.
Example
Given the following ticks script and graph

ts=2018-08-30T03:30:47.259Z lvl=debug msg="listing dot" service=kapacitor task_master=main dot="digraph prophet-logistick {\nquery1 -> prophet2;\nprophet2 -> influxdb_out3;\nprophet2 -> where4;\nwhere4 -> log5;\nlog5 -> first6;\nfirst6 -> log7;\nlog7 -> alert8;\n}"

dbrp "foo_telegraf"."autogen"

var data = batch
    |query('SELECT mean("gauge") AS "value" FROM "db"."autogen"."measurement" WHERE ...omited')
        .align()
        .period(25d)
        .every(5m)
        .offset(0d)
        .groupBy(time(1h))
    @prophet()
        .periods(1000)
        .field('value')
        .freq('H')
        .cap(350000000000.0)
        .floor(0.0)
        .growth('logistic')

data
    |influxDBOut()
        .database('db')
        .retentionPolicy('autogen')
        .measurement('measurement_2')
        .precision('ns')

data
    |where(lambda: "yhat" <<PHONE_NUMBER>0)
    |log()
        .prefix('where')
    |first('yhat')
    |log()
        .prefix('first')
    |alert()
        .id('test')
        .message('{{ .ID }}-{{ .Level }} at {{ .Time }} value: {{ index .Fields "first" }} for {{ .Duration }} ')
        .info(lambda: "first" ><PHONE_NUMBER>0)
        .crit(lambda: "first" <<PHONE_NUMBER>0)
        .log('/tmp/test.log')

The first two line of log after the where node give this with time 2018-09-18T05:00:00Z for the first point

ts=2018-08-30T03:35:47.265Z lvl=info msg="begin batch" service=kapacitor task_master=main task=prophet-logistick node=log5 prefix=where name=... group=  time=2018-08-30T03:00:00Z

ts=2018-08-30T03:35:47.265Z lvl=info msg="batch point" service=kapacitor task_master=main task=prophet-logistick node=log5 prefix=where name=.. group=  field_yhat=49535670531.66772 field_yhat_lower=23879677224.39699 field_yhat_upper=94602373800.68195 time=2018-09-18T05:00:00Z
...

After the first node the log node with prefix first output this.

ts=2018-08-30T03:35:47.348Z lvl=info msg=point service=kapacitor task_master=main task=prophet-logistick node=log7 prefix=first name=... db= rp= group=   field_yhat_lower=23879677224.39699 field_yhat_upper=94602373800.68195 field_first=49535670531.66772 time=2018-08-30T03:00:00Z

The time should be 2018-09-18T05:00:00Z, but it's seems it took the batch time instead 2018-08-30T03:00:00Z.
Therefore i'm unable to use the time given by this point in the alert node.

Nevermind, my bad there is an option for that.
I close this issue.


Move RenderCoordinateSystem into flutter/rendering package

@Hixie says this would be generally useful and we should move it out of the Game:
https://github.com/flutter/game/blob/master/lib/render_coordinate_system.dart
@vlidholt
Ian mentioned this to me yesterday, so writing it down for posterity.

We haven't had customers request this, and that codebase is no longer one we maintain, so closing.


docs: github PR template

Describe your changes
Github PR template to have a better format for PRs (similar to BO repo). Would be useful to see ticket numbers straight from PR instead of looking at messages or branch names. Plus it would encourage us to add more information on how to reproduce and test the changes when reviewing the PR.
Useful information to review or test
Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[x] I have performed a self-review of my own code
[x] I have double checked this work does not include any hardcoded secrets or passwords
[x] I have made corresponding changes to the documentation
[x] I have provided details on how I have tested my code
[x] I have referenced the ticket number above
[x] I have provided a description of the ticket
[x] I have included unit tests to cover any testable code changes

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

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

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


llm can only use OpenAI?

Issue you'd like to raise.
when I use langchain.agents,the parameter llm can only use OpenAI or other large language model ?
Suggestion:
No response

It would be nice to have a unified interface that offers a fallback to a secondary model, say OpenAI as primary and then others if OpenAI is down. I am not sure if someone has found an elegant way to do this.

I think reliableGPT by Ishaan does this @aligajani


Feature request: Add support for, and make use of, GPS receivers

(feature request)
Some users may have a GPS receiver attached to their ADSB tracking Pi, typically via serial port, so in addition to providing assistance with the tools and config needed for this to work it would be great if the resulting location information can be used ;)
I notice that piaware detects and connects to gpsd (if running) but in order to take full advantage of this capability I would suggest considering:

Making an option in the install script to attempt to configure GPSD, if so then packages such as gpsd gpsd-clients python-gps pps-tools, and perhaps even ntp... as per the following guide aimed at using the Pi as an NTP server there are some other steps such as updating the /boot/config.txt that may also benefit from being done here:

http://www.satsignal.eu/ntp/Raspberry-Pi-quickstart.html

Attempt to start gpsd and if it aquires a location then prompt the user to use this, or a manual correction, at any subsequent steps in the installation which currently prompt the user to enter LAT/LON/ELEVATION

display the output of cgps on the 'system information' tab of the web interface

graphs the various information provided by gpsd on the 'performance graphs' tab of the web interface, ideally one each for the LAT/LON/ELEVATION with the value, reported error rate and trending if possible to make it easy to spot if these values are drifting...  the time offset may also be useful...

if we wanted to make the most out of a a GPS receiver attached to a Pi then setting up NTP to use this, and a PPS signal wired from the GPS to a GPIO pin, would be awesome.. but given the number of different approached taken by the various guides this is probably at least as much work as making use of the positioning information :)

While it may be some time before we have a Raspberry Pi with built in GPS receiver, I would hope im not the only user who has added one of these to their Pi for other purposes...
I think that ensuring NTP is running is particularly important since MLAT depends on accurate time signals so I will split that out into a separate feature request; however in the mean time I am interested to know if anyone else would find it beneficial to have the option to configure GPSd and use the hopefully accurate position of the receiver for any/all elements of the adsb-reciever distribution?

There are not enough devices and not enough demand to justify adding a feature such as this at this time.


Provide a setting parameter to keep all dates in ISO format (2020-01-01)

What should I do if I want to keep dates in ISO format (2020-01-01). I don't want to convert them into human-friendly strings ("Jan 2020").

Have a look at locale_catalog.date_style field of the YAML file.


Migrate to the latest Android Gradle Plugin

we need to migrate to AGP 3.2.0

It appears this project already uses gradle 3.2 per the [build.gradle](https://github.com/yshrsmz/simple-preferences/blob/master/build.gradle), am I missing something?

This library is using beta version of the plugin, and stable 3.2 was released already.


Add finetuning streaming dataset conversion

Changes:

add a JSONL IFT dataset
modified scripts/data_prep/convert_finetuning_dataset.py, adding tokenizer args. If it's set, it will run the tokenizer, and save token ids, instead of raw text.

In a separate PR, we will add an example yaml to use streaming dataset for finetuning.
test:
python convert_finetuning_dataset.py --dataset "json" --splits "train"    --out_root "example_data" --data_files "./dolly_hhrlhf_train_small.jsonl" --tokenizer=gpt2 --skip-preprocessing --max_seq_len=512

You might want to run linting locally and also pytest using pytest -vv -s . command to ensure those passes locally.

LGTM, but can you please include evidence of manual testing in the PR description?

Thanks very much for the review! Added the screenshot of the run. Please let me know if more information is needed.

@bigning i'd suggest also just loading the dataset manually and checking that the first sample looks as you expect it to


is there a way to browse Twigls ? all / per user ?

is there a way to browse Twigls ? all / per user ?

sorted by date, likes, etc.

@FabriceNeyret
Some code edited on twigl remains on the back end of the system.
But not all.
There are no plans to implement so-called sign-up or sign-in functions in the future, and we do not intend to make the service like Shadertoy, where data is tied to individual users.
For various reasons, my own unchanging feeling is that I want to provide twigl as a simple and easy-to-use application as possible.

I do see an author name at the bottom right of twigls ( at least the ones I checked )...
Oh, I get it : it means you, not the author of the given twigl !
Still, having a gallery of existing twigls would be cool ( + even more attracting ).
( And you do have a "like" count that could allow sort by like or date, but ok it is easy to fake likes since no registration ).

As you pointed out, it is possible to increase the number of Likes if one wants to do so illegally.
The twigl Like function was initially implemented as a dedicated function for real-time distribution. Since we went to the trouble of creating it, we are able to give a Like when we generate a link to a work, and this is just a bonus feature.
I do not plan to make any changes that are likely to bloat the system, such as managing users or listing submitted shaders, at least not in the future myself.
However, many of the shader creations that have been uploaded to the web can be found on Twitter by searching for twigl or #つぶやきGLSL.
https://twitter.com/search?q=(つぶやきGLSL OR twigl)&src=recent_search_click&f=live

@baodinhaaa
Thanks for the suggestion.
I'm of the opinion that twigl should be simple and I don't want to make it more complicated, especially when it comes to the interface.
The idea of displaying the FPS is a good one, but I don't see the point of it beyond being somewhat useful on each editor's local environment, since WebGL's performance is always variable depending on the platform it runs on.

Currently it is possible to click the Like button multiple times repeatedly.
Is it possible to prevent this by referencing the IP address or something?

@Kamoshika-vrc
Hi Kamoshika!
Thanks for always using twigl.
Like in twigl was originally implemented with the intention of conveying the excitement of the audience to the editor by having them hit the Like button repeatedly during broadcast mode delivery.
Therefore, the current specification of being able to hit the Like button multiple times is intentional.
What is your reason for wanting to suppress it?

@doxas
The reason is that many of the users who opened twigl's link probably recognize "Like count" as "the number of people" in the same way as twitter, Shadertoy, NEORT, etc.
At first I thought I would be able to click the Like button only once.
Twigl doesn't have user accounts, but I think the users' intuition is that they can click the Like button only once.
That is just my personal opinion.
And I cannot imagine the time, financial and human cost of this change.
So, please make your own decision.
If you will not change the behavior of the Like button, how about adding the description to the "information" or mouseover　text of Like button that users can click Like button as many times as they want?

... or maybe to have no "like" feature at all, as it is has no real significance, while being deceiving, and it doesn't help me to find again the shader I once liked ;-)

@doxas
I don't think you should hide the Likes.
I respect your thoughts.


Pasture - Grace Days is missing explanation (info dot and in plan text)

Need info dot re. what grace days means (use text from iPad if you can get to it

@LisaMoore1 This is for the grace days input in the pasture box itself, correct? Not in the grazing schedule row? As well, can you expand on what you mean by "missing explanation in plan text"? I don't quite follow.
@micheal-w-wells Could you please get the help text from the iPad for grace days? Thanks!

@calebissharp
If pasture: grace days field is empty there is placeholder text that explains what grace days are (the +/-... text)
Staff do not see that placeholder text because there is a default entry in the grace days field
Unless they mess around and delete the content in that field they can’t get at any explanation of what the field is for
Some explanation should go in one of those little question/info options so that the users can tell what it means.
I’d actually like to look at that text before it gets entered as I think we could add some clarity there. Please put text here or slack me with it before working on this. This is not a high priority — dropdown is what is holding us up right now.

@LisaMoore1 The help text form the iPad:

Grace Days/Straggler clause language should be updated and implemented as the understanding of how things would work practically has improved since this was originally implemented.

It seems a bit weird from my perspective.

It is strange and I will update before this is actioned -- just have to head out right now.

@LisaMoore1 Pinging you on this in case you've lost it :)

This is the text for the little info dot visible to both staff and agreement holders.
“The number of days flexibility on either side of the date(s) shown in the schedule for livestock movement. Example: for a grace day of 1 a compliant move would be one that occurs the day before, day of or day after the date indicated in the schedule.”


Object Store API improvements

Describe the bug
So recently we started seeing two issues:

multiple shutdowns of the same writer will cause an issue, related to [this](https://github.com/apache/arrow-rs/blob/50e9e4927ed4d763c76227c588aa324aa173032e/object_store/src/buffered.rs#L220
partition size issue, related to this

Multiple Shutdown
First of all, I want to note that multiple shutdown calls to the same writer are the issue by itself, but I think we can make the situation better with minimum effort.
Here is the code:
             BufWriterState::Write(x) => {
                    let upload = x.take().ok_or_else(|| {
                        std::io::Error::new(
                            ErrorKind::InvalidInput,
                            "Cannot shutdown a writer that has already been shut down",
                        )
                    })?;
                    self.state = BufWriterState::Flush(
                        async move {
                            upload.finish().await?;
                            Ok(())
                        }
                        .boxed(),
                    )
                }

I think we can change it to something more friendly like this:
             BufWriterState::Write(x) => {
                    if let Some(upload) = x.take() {
                        self.state = BufWriterState::Flush(
                            async move { upload.finish().await.map(|_| ()) }.boxed(),
                        )
                    } else {
                        return Poll::Ready(Ok(()));
                    }
                }

This way on a second shutdown call we just immediately return Ok(())
Upload part size issue
Something leftover during the shutdown, complete before the previous upload, in this case, we're getting:
Your proposed upload is smaller than the minimum allowed size

To mitigate this issue we probably should wait for all previous part uploads to complete and then upload the final part which may be smaller than the minimum size of the last one.
Here is the original code I propose to change:
 pub async fn finish(mut self) -> Result<PutResult> {
        if !self.buffer.is_empty() {
            let part = std::mem::take(&mut self.buffer);
            self.put_part(part.into())
        }

        self.wait_for_capacity(0).await?;

        match self.upload.complete().await {
            Err(e) => {
                self.tasks.shutdown().await;
                self.upload.abort().await?;
                Err(e)
            }
            Ok(result) => Ok(result),
        }
    }

by injecting self.wait_for_capacity(0).await?; before actually putting the last chunk we can mitigate this issue.
 pub async fn finish(mut self) -> Result<PutResult> {
        if !self.buffer.is_empty() {
            self.wait_for_capacity(0).await?;  // here

            let part = std::mem::take(&mut self.buffer);
            self.put_part(part.into())
        }

        self.wait_for_capacity(0).await?;

        match self.upload.complete().await {
            Err(e) => {
                self.tasks.shutdown().await;
                self.upload.abort().await?;
                Err(e)
            }
            Ok(result) => Ok(result),
        }
    }

This way we wait for all ongoing uploads before submitting the last part

I think it's more an enhancement

What is the use-case for multiple shutdowns, this feels like a bug in the calling code.
A similar argument could be made for calling shutdown before the parts have been uploaded, this I think implies the caller is waiting on the returned futures?

Yes, calling multiple shutdowns it's a bug on the caller side for sure. Changes proposed by me should help mitigate this issue a bit by making shutdown calls relaxed
For the second one, we're using an s3 object store and for some reason, it (s3) doesn't take into account the part number during the multipart upload and return error mentioned above. We managed to solve this issue by calling self.wait_for_capacity(0).await? before calling finish()

Changes proposed by me should help mitigate this issue a bit by making shutdown calls relaxed

Your proposed change is racy, the first close will wait on the upload to complete, with subsequent calls "completing" instantly.

For the second one, we're using an s3 object store and for some reason, it (s3) doesn't take into account the part number during the multipart upload and return error mentioned above. We managed to solve this issue by calling self.wait_for_capacity(0).await? before calling finish()

Perhaps you could write a simple reproducer for this, I'm not saying S3 doesn't do this but I want to be sure we've correctly identified the issue. Your proposed fix will serialize a round-trip which is unfortunate when many stores are not exactly low-latency.

I will try to provide an example of the second issue, but meanwhile, I thought maybe we can change the flush method of BufWriter:
fn poll_flush(mut self: Pin<&mut Self>, cx: &mut Context<'_>) -> Poll<Result<(), Error>> {
        loop {
            return match &mut self.state {
                BufWriterState::Write(write) => {
                    if let Some(write) = write {
                        write.poll_for_capacity(0);
                    }
                },
                BufWriterState::Buffer(_, _) => Poll::Ready(Ok(())),
                BufWriterState::Flush(_) => panic!("Already shut down"),
                BufWriterState::Prepare(f) => {
                    self.state = BufWriterState::Write(ready!(f.poll_unpin(cx)?).into());
                    continue;
                }
            };
        }
    }

By actually waiting for all downloads to complete we can give a user and ability to use flush() + shutdown(), wdyt?

What would be the benefit of this? It wouldn't be able to guarantee that there isn't any data still in flight as it can't upload the final data until shutdown is called. It is a valid point that we're taking a somewhat dubious interpretation of the AsyncWrite trait, but its a necessary evil. We could probably add further documentation to discourage the use of AsyncWrite

yes, but flush will ensure that ongoing writes are flushed which is generally aligned with "flush". And after that, you're okay to finalize your upload in case of shutdown

will ensure that ongoing writes are flushed which is generally aligned with "flush"

Only those it has actually started writing, I think the proposed behaviour is more confusing. We should just make shutdown do the right thing

@tustvold Sorry for the late response, I was trying to find a reproducer for this issue unfortunately without success so far. If you think it will be okay to just update the shutdown, that would be great

So the proposed change would be oneliner here:
 pub async fn finish(mut self) -> Result<PutResult> {
        if !self.buffer.is_empty() {
            self.wait_for_capacity(0).await?;  // here

            let part = std::mem::take(&mut self.buffer);
            self.put_part(part.into())
        }

        self.wait_for_capacity(0).await?;

        match self.upload.complete().await {
            Err(e) => {
                self.tasks.shutdown().await;
                self.upload.abort().await?;
                Err(e)
            }
            Ok(result) => Ok(result),
        }
    }

This will serialize a round-trip adding latency to callers of finish, I would therefore be apprehensive about making this change without a reproducer of the issue it is seeking to fix.

@tustvold makes sense

I managed to reproduce the issue on our staging environment and find a problem that was causing it, even so I can't explain it fully.
We have a code to upload data to the s3 store in chunks, we're using a combination of the MultipartUpload + WriteMultipart.
Here is the code for MultipartUpload for S3:
fn put_part(&mut self, data: PutPayload) -> UploadPart {
        let idx = self.part_idx;
        self.part_idx += 1;
        let state = Arc::clone(&self.state);
        Box::pin(async move {
            let part = state
                .client
                .put_part(&state.location, &state.upload_id, idx, data)
                .await?;
            state.parts.put(idx, part);
            Ok(())
        })
    }

In short, we synchronously increment the index for a writer using (&mut ref) which should protect us from races, and then create a future to write a part.
We call this method here in WriteMultipart when we have a chunk of the data to write.
  pub(crate) fn put_part(&mut self, part: PutPayload) {
        self.tasks.spawn(self.upload.put_part(part));
    }

We're spawning a new task to upload part to S3 and also additionally assigning idx for this partition, everything looks correct and safe as we are protected by &mut ref, in my understanding synchronous part of the put_part will be the executed immediately, without waiting for future polling.
During investigation I added a lot of "logging" to our fork of object-store. And found out a very weird thing. From time to time (I would even use work very often) I observed such things:
(last -1) -><PHONE_NUMBER>539115 before span;<PHONE_NUMBER>655545 after span
last        -><PHONE_NUMBER>539834 before span;<PHONE_NUMBER>539847 after span

In short, even so last write before calling complete method was scheduled in the correct order immediate execution of the spawned task for the uploading part was scheduled in a different order, which is okay in general as we giving it to the runtime scheduler. But weirdly enough same applies to the sync part of the put_part code, meaning that the last partition with a size less than needed for S3 was assigned the last - 1 index causing the whole upload to fail during completion.
I don't know why it's happening like that, I will probably spend some more time trying to coin it out, but the solution for this problem is quite simple:
pub(crate) fn put_part(&mut self, part: PutPayload) {
        let task = self.upload.put_part(part);
        self.tasks.spawn(task);
    }

create a task future outside of the spawn call to guarantee that we assigned a proper index to the part and then submit a task
Please let me know what you think @tustvold 🙇

This is the same proposal as before can you please articulate what problem you are trying to fix, with a reproducer.


Auto-update the extension

Add check on startup if a new version is available in the marketplace and notify the user if necessary.

Fixed https://github.com/NativeScript/nativescript-vscode-extension/commit/799ef06ad62e68a440f81bf23b6f30ac045c0a45


gosec: 2.9.6 -> 2.10.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/securego/gosec/releases.
meta.description for gosec is: "Golang security checker"
meta.homepage for gosec is: "https://github.com/securego/gosec"
meta.changelog for gosec is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/n95wjlsp2dhm7crfbfqalwp3anr6j1xd-gosec-2.10.0/bin/gosec had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 2.10.0 with grep in /nix/store/n95wjlsp2dhm7crfbfqalwp3anr6j1xd-gosec-2.10.0
found 2.10.0 in filename of file in /nix/store/n95wjlsp2dhm7crfbfqalwp3anr6j1xd-gosec-2.10.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
gosec

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/n95wjlsp2dhm7crfbfqalwp3anr6j1xd-gosec-2.10.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gosec https://github.com/r-ryantm/nixpkgs/archive/2d6990bec6674cd9bca228fedce3b422d66090bc.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n95wjlsp2dhm7crfbfqalwp3anr6j1xd-gosec-2.10.0
ls -la /nix/store/n95wjlsp2dhm7crfbfqalwp3anr6j1xd-gosec-2.10.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

gosec

Maintainer pings
cc @kalbasit @nilp0inter @kalbasit for testing.

@ofborg eval


[#123] Provide jump api for the workflow object to jump to a specific future state

Coverage remained the same at ?% when pulling 3ff27711e650017c485fde4d03a66c86133c3e28 on issue-123-jump-to-a-state into 4afa45e70e1cb6c9951cee5e821f03641d2a05d6 on master.

Coverage remained the same at ?% when pulling 3ff27711e650017c485fde4d03a66c86133c3e28 on issue-123-jump-to-a-state into 4afa45e70e1cb6c9951cee5e821f03641d2a05d6 on master.

Coverage remained the same at ?% when pulling 3ff27711e650017c485fde4d03a66c86133c3e28 on issue-123-jump-to-a-state into 4afa45e70e1cb6c9951cee5e821f03641d2a05d6 on master.

Coverage remained the same at ?% when pulling 3ff27711e650017c485fde4d03a66c86133c3e28 on issue-123-jump-to-a-state into 4afa45e70e1cb6c9951cee5e821f03641d2a05d6 on master.

Coverage remained the same at ?% when pulling 3ff27711e650017c485fde4d03a66c86133c3e28 on issue-123-jump-to-a-state into 4afa45e70e1cb6c9951cee5e821f03641d2a05d6 on master.

Coverage remained the same at ?% when pulling 3ff27711e650017c485fde4d03a66c86133c3e28 on issue-123-jump-to-a-state into 4afa45e70e1cb6c9951cee5e821f03641d2a05d6 on master.


stuff to add please

Sort by file type
way to change everything in settings and a way to hide menu bar.

It'd also be great to be able to:

Select what columns to show/hide (e.g. hide the "Size" column)
Choose a Date format (e.g. Month, Day)


Random numbers showing up as extract names

Looking here: https://mapzen-odes-extracts-staging.herokuapp.com/odes/extracts/

(I remember editing the default names for some of them in the text box before creating the custom extract)

What if you look at https://mapzen.com/data/metro-extracts-alt/odes/extracts/ ?

Still there but they might be the ones I made in staging. Also, that link doesn't have all the latest changes, right?

This is due to our development process being spread across a few different instances of the database, so it's not a bug. Closing!


type assertions

i am doing something like this in flow
type NotificationAction =
  | 'ScheduleCreated'
  | 'ScheduleStarttimeUpdated'
  | 'ScheduleCancelled'
  | 'DiagnosisPublished'
  | 'PatientCaseFinished'
  | 'MydocGreeted'

type NotificationBase = {|
  +id: string,
  +created_at: string
|}

type Notification = {|
  ...NotificationBase,
  +action: NotificationAction,
  +entity_id: string,
|}

export type NotificationExpanded =
  | {|
      ...NotificationBase,
      +action: 'ScheduleCreated' | 'ScheduleStarttimeUpdated' | 'ScheduleCancelled',
      +schedule: {...}
    |}
  | {|
      ...NotificationBase,
      +action: 'PatientCaseFinished',
      +patientCase: {...}
    |}
  | {|
      ...NotificationBase,
      +action: 'MydocGreeted' | 'DiagnosisPublished'
    |}

// -- EXHAUSTIVE CHECKING --

declare var _asrt01: $PropertyType<NotificationExpanded, 'action'>
/*:: (_asrt01: NotificationAction) */

declare var _asrt02: NotificationAction
/*:: (_asrt02: $PropertyType<NotificationExpanded, 'action'> ) */

// -- END OF EXHAUSTIVE CHECKING --

try
i am checking that object union has all actions from NotificationAction and nothing extra
in flow this is very hacky but in hegel i think it's impossible to achieve same result because i can't declare var and i can't use type casting (type casting can be replaced with variable declaration but then i have reference of undefined variable in code)

Good point. I need to think about it, especially about the syntax. Thank you for your contribution ^_^.


YouTube Livestream Support

Could we possibly add YouTube livestream support to this plugin? The new Live videojs state could be used (in vjs 4.6.0) as using the default player is really, really buggy. For example, the progress bar escapes the defined video area.

Sorry for dragging this old thread out of the mud, but testing with this live stream video:
https://www.youtube.com/watch?v=oI3pxPBYLfo
I get an error message saying "A network error caused the video download to fail part-way"
Are you sure that live stream youtube videos work?

Sorry please disregard. problem was resolved by updating to latest version.


Implement usage check for Expect in Request and Websocket

Fixes #162.

[X] Add documentation for Expect in Request
[X] Add usage checks for Expect and WithXXX in Request
[X] Add unit tests for Expect and WithXXX in Request

Coverage: 95.729% (+0.08%) from 95.648% when pulling ff6121ba34af038ec971e60a6835059a8a373894 on chunweii:expect-usage-check into 29fd41d071c4cb748d7fe5cd4e155bc94d8ea6cb on gavv:master.

Checks are missing in:

WithRedirectPolicy
WithMaxRedirects

Also, I just noticed that WithName and Expect are missing this check:
	if r.chain.failed() {
		return r
	}

Could you please add it as well?

Hi, please rebase your PR on fresh master. It has reworked chain interface.
Instead of:
	r.chain.enter("XXX()")
	defer r.leave()

	if r.failed() {
		return r
	}

we should now use:
	opChain := r.chain.enter("Decode()")
	defer opChain.leave()

	if opChain.failed() {
		return r
	}

In other words, chain.enter() now returns a new chain instance, and we should use it for all other operations with chain. This change is part of making this lib thread-safe.
Related commits:

a96122195174a5b9df2804e41c8abe92a90fc52b
90675e11729f5dfa5121bbf41a1e071dbf9e52e7

Thanks you!!


Psql migration

new

@sammohdnak I like some of the changes you made here.  With that being said, I want to keep this repo as general as possible and accessible to a wide range of users.  So I want to keep the project using Sqlite and the default markdown editor. Since it is something that is maintained by Strapi and not a third party plugin.
I am going to keep this PR open for anyone wanting to make the changes in there own project.
But what I would recommend, is you can fork it, and create your own version of the Starter.  And I will pin it in this repo as another option.
Let me know if you have any questions.


operator.yaml - update so it deploys the latest grafana image as set by the operator by default

The latest release of this operator says it deploys Grafana 6.5.1 but with the current defaults in the operator.yml 6.2.something gets deployed. suggest removing the args in the operatyor.yml so by default the default image set in the operator gets picked up

FYI, i tested this operator with setting image value to 6.5.2 and it seems to work.

Ok, seems reasonable to not override the default image with an older version.


found a mistake in function router.use()

file located at ./lib/router/index.js
proto.use = function use(fn) {
  var offset = 0;
  var path = '/';

  // default path to '/'
  // disambiguate router.use([fn])
  if (typeof fn !== 'function') {
    var arg = fn;

    while (Array.isArray(arg) && arg.length !== 0) {
      arg = arg[0];
    }

    // first arg is the path
    if (typeof arg !== 'function') {
      offset = 1;
      path = fn;
    }
  }

 ...

I think the keyword while shoud be replaced with if , though this situation is raley used. Found it by accident……FYI

@dougwilson got it when I read it again, terribly sorry……my apology

It's no problem at all. Nothing to apologize for :)


[SPARK-18409][ML][FOLLOWUP] LSH approxNearestNeighbors optimization 2

What changes were proposed in this pull request?
simplify the aggregation by get count via summary.count
Why are the changes needed?
simplify the aggregation
Does this PR introduce any user-facing change?
No
How was this patch tested?
existing testsuites

Test build #128790 has started for PR 29778 at commit 78121a1.

Merged build finished. Test PASSed.

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

Test build #128790 has finished for PR 29778 at commit 78121a1.

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

Merged build finished. Test PASSed.

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

ping @huaxingao

my changes in https://github.com/apache/spark/pull/26990  fogot to ignore nan values like the old impl, in this PR I ignore nan value.
also ping @srowen

merged to master. thanks all!


Review: ChangePasswordUser.jsx and EditProfile.jsx

Overview
The focus for this code review will be centered around the ChangePasswordUser and EditProfile pages.
Review Branch
review-4
Files to review

ChangePasswordUser.jsx
EditProfile.jsx

Checklists

Architecture
Design
JS
React

Due date
10/4/2022
For more information
The review process is documented at: http://courses.ics.hawaii.edu/ics414s21/morea/review/reading-idpm-review.html

ChangePasswordUser.jsx:
L73-79, 82-88: DE-01: Same lines of code, can refractor
L111, 112: JS-01: Same IDs, make a new ID for SIGN_UP_FORM_NEW_PASSWORD and SIGN_UP_FORM_CONFIRM_PASSWORD
EditProfile.jsx:
L118-122, 125-129: DE-01: Same lines of code, can refractor

ChangePasswordUser.jsx
DE-01: L73-79, L82-88, Exact same code, refractor please
DE-02: L52-64, L66-93, Deeply nested if/else statements here, is it possible to reorganize this?
JS-01: L111, 112, Please make a new ID for the SIGN_UP_FORM_CONFIRM_PASSWORD and SIGN_UP_FORM_NEW_PASSWORD text fields
EditProfile.jsx
DE-01: L118-122, 125-129: Exact same code, refractor if possible
ES-01: L39-58: ESLint warning: "Duplicated code fragment (20 lines long)"

ChangePasswordUser.jsx
DE-01: L71 - 88: Can be refactored, the if/else can decide the CollectionName and then the updateMethod can come after the if/else statement.
DE-02: L55 - 88: Contains many nested if/else statements, is it possible to reduce lines of code by using a ternary operator?
DE-06: L75 & L84: Since the usual "err" is being used already, for the swal (SweetAlert) parameters the var "errr" is used. For readability is it possible to change errr -> "swalErr" (or something similar) to make sure that the reader doesn't get the error from the Meteor.call mixed up with the error from swal.
EditProfile.jsx
JS-05: L73: Avoid using underscore if possible.
DE-01: L80 - 92, L118 - 130: Refactor the blocks of code that use transferMethod and defineMethod to be similar to how updateMethod is used on this page. (Use the if/else to change the collectionName and then use the method afterwards.

ChangePasswordUser.jsx
DE-01: L73-79, 82-88: Both sections contains exact same code. Possible to refractor.
EditProfile.jsx
ES-01: L39-58: ESLint warning: "Duplicated code fragment (20 lines long)" Exact same code as L15-34 in Profile.jsx.

ChangePasswordUser.jsx
L74-79, L83-88: similar blocks of code
L66-93: deeply nested if/else block
Console warning: Found 2 elements with non-unique id #sign-up-form-password
EditProfile.jsx
L81-85, L89-93: similar blocks of code
L73: avoid lodash functions
L39: warning: duplicated code fragment (20 lines long)
Console warning: Each child in a list should have a unique "key" prop

ChangePasswordUser.jsx:
L73-79 & L82-88 DE-01: Same block of code that can be reduced
EditProfile.jsx:
L81-83 & L89-91, L118-122 & L125-129 DE-01: Same block of code that can be reduced

ChangePasswordUser.jsx
DE-02:  L66-80 nested conditionals, multiple if/else blocks
DE-01: L73-79 & 81-87 Duplicate code, refactor to reduce duplication
EditProfile.jsx
DE-02: L61-106,  L114-129 nested conditionals, multiple if/else blocks
DE-01: Duplicate code per admin/user functions

ChangePasswordUser.jsx
Console warning: Found 2 elements with non-unique id #sign-up-form-password
L73-79 & 81-87 duplicated code, can be reduced
EditProfile.jsx
Console warning: Each child in a list should have a unique "key" prop
L114-129 duplicated code, can be reduced


ViroVideo is not working

Requirements:
Please go through this checklist before opening a new issue

[x] Review the documentation
[x] Search for existing issues in: viromedia/viro & ViroCommunity/viro
[x] Use the latest ViroReact release

Environment
Please provide the following information about your environment:

Macbook Pro
Device OS & Version: iPhone11 iOS 15.3
ViroReact: 2.22.0
React Native: 0.65.1

Description

[ ] ViroVideo crashes with invariant violation: Unrecognized selector sent to instance

Interestingly, Viro360Video works.
Reproducible Demo

⚠ NOTE: I've installed viro react from a local download of the viro react to make changes to the viro react source code. All of these issues have been replicated with<EMAIL_ADDRESS>
ViroVideo
https://github.com/NS-BOBBY-C/starter-kit/blob/4d93e7dd3ae05d089573f07f20964e2258a1933d/screens/viro_tests/ViroVideo.tsx#L1-L45

Update: @doranteseduardo was not able to reproduce. I'll be double-checking that this is an issue within the next day or so!

Closing since I was not able to reproduce in my starter kit on ios or android. https://github.com/NS-BOBBY-C/starter-kit/blob/e79051a6c9d4f0182e20bda872c15430ee0393b8/screens/github_issues/Issue75.tsx

Still able to reproduce on latest version.
 <ViroARScene onTrackingUpdated={onInitialized}>           <ViroAmbientLight color="#ffffff" intensity={2500} />           <ViroNode             position={[0, 0, 0]}             rotation={[0, 0, 0]}             scale={[2.0, 2.0, 2.0]}>             <ViroVideo               source={require('../../../assets/animation/wizard.mp4')}               loop={true}               position={[0, 2, -5]}               scale={[2, 2, 0]}             />           </ViroNode>         </ViroARScene>

You can close it since my previous comment is now invalid. Devs were using not latest but previous version.


Library is still reaching to window.localstorage even after custom implementation is provided for Storage API

I have provided a custom implemetnation for the storage API by passing it as a prop to , but even so, the component is reaching out to window.localstorage which causes errors.
<PanelGroup storage={sessionStorage} direction="vertical">
          <Panel defaultSize={25}>
          </Panel>
          <PanelResizeHandle />
          <Panel>
          </Panel>
</PanelGroup>

caught DOMException: Failed to read the 'localStorage' property from 'Window': The document is sandboxed and lacks the 'allow-same-origin' flag.
    at eval (webpack-internal:///./node_modules/react-resizable-panels/dist/react-resizable-panels.module.js:639:14)

It would be nice to have an option to disable persistance all together.

The only place localStorage is referenced in this project is here:
https://github.com/bvaughn/react-resizable-panels/blob/4242b04ba628622e9f215a8e58615c325e69b84d/packages/react-resizable-panels/src/PanelGroup.ts#L56-L65
The localStorage API is not used if a custom storage prop is provided, and this typeof check should never be executed either.
I'm afraid this is going to require a repro case.

Thank you. In order to test this out, you'll need to open this CodePen URL that has a sandboxed Iframe and then run this repo or any repo that has react-resizable-panels component locally. You can run this example locally: https://github.com/roshaans/react-panels

Thank you. In order to test this out, you'll need to open this CodePen URL that has a sandboxed Iframe and then run this repo or any repo that has react-resizable-panels component locally. You can run this example locally: https://github.com/roshaans/react-panels

You should see this in the console window of the CodePen:

You can run this example locally: https://github.com/roshaans/react-panels

The repository you linked me to runs without any errors for me.
It also does not pass a storage prop, so the default storage API (localStorage) is used.


Cars despawning

Unfortunately I’m unable to use this on my RP server because people’s vehicles keep on despawning. Since removing this trainer we haven’t had the problem since.
I’d love to see this fixed because I would use this trainer above the lambda menu, as you can actually restrict the features.

There is some code somewhere in the spawning of the cars where it turns them off as a mission entity (mission entities basically never despawn), you could edit that part of the code to find what is happening...


ID collisions in astro

the same problem as described in #188 but for astro
I suppose handleSVGId should be used in the compiler for astro too?

I just realized that handleSVGId is not a generic fix but for vue only..


document difference between this fork and the original version

Both this and the  jbtule/cdto are available in Homebrew on Mac for example. It is entirely unclear which one to choose and what is the difference between the two.

Right, I need to check latest updates in jbtule/cdto and compare to this repo.
Initially I created this fork just to merge outstanding PRs and have built release ready for use. Now since original author is active again there may be less need to maintain a fork.

Yea, the huge advantage of Github, it's so easy to create forks. The huge disadvantage of Github, it's so easy to create forks... :)
From what I understand from the README, you added support for iTerm and Hyper?

iTerm was supported by original author, but removed in v3.0 rewrite. This fork was created before removal.
Hyper support added in https://github.com/ealeksandrov/cdto/pull/1.

Ah, ok, that might make it more difficult to merge this with upstream.
I use Terminal, so I installed version 3.

Here is list of initial changes - https://github.com/jbtule/cdto/issues/25.
Main differences from current jbtule/cdto:

new icon in this fork
support for iTerm and Hyper in this fork
some new settings in original
code refactoring applied in original

I've tried original 3.1 vs fork 2.8 on Big Sur just now and both work fine, I can't spot any significant difference in performance.
Also I recommend looking at https://github.com/Ji4n1ng/OpenInTerminal - many more integrations and features.


fix(security): tar vulnerability

This PR is based off of https://github.com/cdr/code-server/pull/4071 and fixes a tar vulnerability.

@jsjoeio I believe this may be outdated as we no longer need to tar for extensions

@jsjoeio I believe this may be outdated as we no longer need tar for extensions in an upcoming fork clean up PR

Sweet! I wonder when that will land though? If we have PRs coming in before that, should we fix this sooner?
(though looks like something is still failing)

Maybe I need to re-run yarn? I'll check this
https://github.com/cdr/code-server/pull/4085/checks?check_run_id=3489226386


Update discord.ts

very minor
Please describe the changes this PR makes and why it should be merged:
Update a comment in discord.ts
Status

[x] Code changes have been tested against the Discord API, or there are no code changes

Semantic versioning classification:

[ ] This PR changes the library's interface (methods or parameters added)

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[x] This PR only includes non-code changes, like changes to documentation, README, etc.(I guess it counts?)

Hmmm, i think we could possibly just remove this entirely, the API version being changed to used new apis will no longer work. Discord is stopping that and we will not be able to use v9 before its officially released. I have to think about this

@Suyashtnt I've rebased this to the next branch so it can include breaking changes which we merge in the next major release. I believe the best way to handle this is to just remove this entire variable. Discord is no longer going to allow us to customize which version we can use. After the v7 headaches that other libs caused Discord is preventing libraries from using other versions that are not released which makes this variable pretty useless.

Remove the API_VERSION variable
Hardcode the v8 into the URL

Done, changed accoding to that


Ignore env_win.cc on non Windows platforms

Building on non-Windows platforms emits this warning:
ar: creating archive libleveldb.a
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: libleveldb.a(env_win.o) has no symbols

The env_win.cc file should probably be moved to port/port_win_platform.cc or something like that, because the upstream logic to list files to compile doesn't work properly with files in util directory...
The submitted change tries to workaround it.

@theuni please have a look, thanks.

I guess this is no longer necessary now that leveldb is integrated into our build system

Current master:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: leveldb/libleveldb.a(leveldb_libleveldb_a-env_win.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: leveldb/libleveldb.a(leveldb_libleveldb_a-env_win.o) has no symbols

Please reopen.

The point is, we don't use leveldb's build system anymore, so patching it won't solve .

Also this shows as changing 40 files, that can't be right.

A rebase should fix the 40 files.

Rebased.

But yes, I think this is now bug in our src/Makefile.leveldb.include. Will try to fix it there...

Fixed by https://github.com/bitcoin/bitcoin/pull/8826.


Bootstrap v3.3.4

Has anyone tested the bootstrap-rtl with bootstrap 3.3.2 ?!
I have upgraded, made a quick look and did not find any issues.
Any idea ?!

There is not much to change, only one issue to match the new version, and it's changing the selector of last and first children of button groups (to set respective left or right border radius).
Here is list of changes, mostly unrelated to the right-to-left representation:

New WOFF2 Glyphicon font.
Some new icons.
Striped table uses nth-of-type instead of nth-child for odd rows.
Line heights of input-group-sm and input-group-lg for data, time, datatime-local, and month inputs.
input-lg and input-sm improvements for selects and textareas.
form-control-static.
drop-ups (it's just just like dropdown, speaking of stylings).
Bottom margin for dropdown and dropup menus.
New selector for right border radius for last child of btn-groups.
New selector for left border radius for first child of btn-group.
Bottom margin for dropdowns menus of fixed bottom navbars.
media-body and media-object display.
Color of smalls inside panel-tilte.
Line height for next and prev carousel icons.

Bootstrap 3.3.4 is out.
I suggest to skip the release of a 3.3.2 version and work directly on that.
if agreed, withou opening a new ticket name of this should be changed and so the milestone name.

I've run a diff on 3.3.4 vs 3.3.2, and fortunately it does not seem to have any impact on rtl rendering. Let me know if there is any bug.
.
This issue and the milestone are both changed to match latest version.

hi morteza, is there any update on this release?

@evilali3 Nothing new. There is a 3.3.4-rc1 tag now, but it might need some minor updates. Rather than that, you can  just bump the version.

to keep in mind before closing this ticket: https://github.com/morteza/bootstrap-rtl/issues/70


Types > Color.bf > ToString function causes error

https://github.com/M0n7y5/raylib-beef/blob/0fe15bcb664ac3e58a1369a75fbe1d518d4ee9be/src/Types/Color.bf#L52
Beef version 0.42.4 raises error on this line: Expected '(' or '['
Downloaded and installed latest release of raylib-beef but the error persists.

Oh yeah ... dont use this... i forgot to delete this

Fix relesed ...


Cherry-pick: Add option to force TCP_QUICKACK.

It is well known that Nagle's algorithm (the absence of TCP_NODELAY)
and delayed acknowledgements (the absence of TCP_QUICKACK) cause
performance issues on TCP; see for example:

https://eklitzke.org/the-caveats-of-tcp-nodelay
http://jvns.ca/blog/2015/11/21/why-you-should-understand-a-little-about-tcp/

TCP_NODELAY was already implemented; this commit adds TCP_QUICKACK.
This change breaks the external API, because socketToEndPoint
(for reasons not obvious to me) takes all socket options as individual
arguments, instead of as a settings object.

Upstream PR: https://github.com/haskell-distributed/network-transport-tcp/pull/67

This change breaks the external API, because socketToEndPoint
(for reasons not obvious to me) takes all socket options as individual
arguments, instead of as a settings object.

Feel free to correct this! I'm sure it would be warmly welcomed upstream.

Feel free to correct this! I'm sure it would be warmly welcomed upstream.

OK, I've just asked on https://github.com/haskell-distributed/network-transport-tcp/pull/67#issuecomment-299516170


Determine which Docker image tags we should push for each release

Currently, the release GH Action will push tags named "latest" and the release's git tag on each release. Most projects strip the leading "v" from a tag if it exists for their container image tags and push other floating tags like MAJOR.MINOR and MAJOR in addition to MAJOR.MINOR.PATCH. We should determine if those are things we'd like to also implement for OSM.

The release process has gone through several iterations since this issue was filed ~10 months ago.
Documentation: https://github.com/openservicemesh/osm/blob/main/docs/release_guide.md


fix: schemathesis.from_pytest_fixture: Display each failure if Hypothesis found multiple of them

I remember it was reported somewhere, but can't find it :(

Codecov Report

Merging #1500 (3e527d4) into master (5f9084e) will decrease coverage by 0.19%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1500      +/-   ##
==========================================
- Coverage   99.28%   99.08%   -0.20%
==========================================
  Files          91       91
  Lines        6945     6901      -44
  Branches     1225     1194      -31
==========================================
- Hits         6895     6838      -57
- Misses         26       34       +8
- Partials       24       29       +5

Impacted Files
Coverage Δ

src/schemathesis/lazy.py
96.35% <100.00%> (+0.41%)
:arrow_up:

src/schemathesis/specs/openapi/validation.py
76.47% <0.00%> (-11.77%)
:arrow_down:

src/schemathesis/extra/pytest_plugin.py
95.55% <0.00%> (-4.45%)
:arrow_down:

src/schemathesis/cli/callbacks.py
98.62% <0.00%> (-1.38%)
:arrow_down:

src/schemathesis/utils.py
97.78% <0.00%> (-0.89%)
:arrow_down:

src/schemathesis/specs/openapi/loaders.py
98.31% <0.00%> (-0.85%)
:arrow_down:

...rc/schemathesis/specs/openapi/negative/__init__.py
94.11% <0.00%> (-0.17%)
:arrow_down:

src/schemathesis/serializers.py
98.18% <0.00%> (-0.11%)
:arrow_down:

src/schemathesis/runner/serialization.py
97.91% <0.00%> (-0.11%)
:arrow_down:

... and 19 more

Continue to review full report at Codecov.

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


Use the public KCP image for local development

Now that KCP provides a public image, it has become unnecessary
for the users to build and upload their own images.
@fgiloux, @bnallapeta This PR is a first step to bring a development environment that's easy to setup for users, and cleaning up the repo from deprecated files.
I plan on working on the following items once the deployment on our KCP staging is completed:

Remove most of the code in ckcp/deploy.sh and keep only the ckcp and argocd deployment, then use kcp/deploy.sh to setup the cluster as if it was a staging cluster.
Rewrite/move ckcp/test.sh to kcp/.
Deprecate the local/ folder.

Re @bnallapeta comment. I think it makes sense to validate that it is working. One thing is that I quickly checked and did not see any release tag added to the kcp images. It would be trivial to amend their GitHub action for that. I may open a pull request for that when I have some time.
We could then follow a release version, which would provide some level of stability and avoid breaking. We can then bump the version when a new kcp release is provided and we have generally moved to it and when we want to pick specific bug fixes

I agree that those changes should be validated before being merged. I submitted the PR so you had an idea of the direction I was taking.

Closing this PR as @psturc will be having a look at it.


for energy_dist_20.pkl, how to use it in test?

when I test the t1_test.yaml after I python 3 t1_val.yaml, it's saying "Energy distribution is not found at ./output/temp_3/energy_dist_20.pkl",but it's also can test. What's more , I think it's may be that i am not place it right，but if I put it，the AP50  be down , but the and Absolute OSE is up, can you tell me why?

Please run these commands as is. If you still face the issue, please reopen.


Fix refresh tokens.

          1 Warning

:warning:
Please provide a linked tracker story for this PR in the description

  Generated by :no_entry_sign: Danger


Way to disable auth completely?

We have put operate behind an auth proxy that uses OIDC, therefore we have no use for the internal operate auth. Is there any way we can disable it?

Hi @CodechCFA i will check with the Operate team, I am not sure if that can be done now, @sdorokhova can you share some details about that?

Hi, @CodechCFA , no, unfortunately it's not possible currently in Operate to disable authentication.

@sdorokhova gotcha and there's no way to use Okta for, only Auth0 right?

Exactly. Currently we support only Auth0 for Single Sign-on case.


multiprocessing error?

Amazing job !!! I got an error when I run "dial-mpc-plan --example unitree_go2_seq_jump_deploy":
jaxlib.xla_extension.XlaRuntimeError: FAILED_PRECONDITION: cuSolver has not been initialized
/root/miniforge3/lib/python3.10/multiprocessing/resource_tracker.py:224: UserWarning: resource_tracker: There appear to be 6 leaked shared_memory objects to clean up at shutdown
  warnings.warn('resource_tracker: There appear to be %d

The reason is I used too much gpu ?

I've encountered the same issue. It appears that after running the command:
dial-mpc-sim --example unitree_go2_seq_jump_deploy

a significant amount of memory is occupied on the GPU (nvidia-smi reports 6 GB of VRAM usage). Is this amount of memory intended? This is unexpected, as I understood this should just be a MuJoCo simulation running in parallel. Consequently, there isn't enough memory available for:
dial-mpc-plan --example unitree_go2_seq_jump_deploy

Could you let me know if there are any recommended solutions or workarounds for this?
By the way, thank you for this excellent library! I'm eager to contribute some examples if that's alright with you.

Thanks for your interest in our project!

Why am I getting an "out of resource" error?

DIAL-MPC needs to be run on a GPU, and the error cuSolver has not been initialized suggests that your GPU is not properly initialized due to a CUDA issue. Please check your JAX installation and ensure that the CUDA-enabled version of JAX is set up correctly.

Why is so much memory being used?

JAX preallocates GPU memory to optimize computational speed. You can read more about this feature here: JAX GPU Memory Allocation.
Let me know if you need further assistance!

@jc-bao I am using nvidia 4090 to run these program, before this error happened, almost all gpu(24g) has been used.

@kassasin If that's the case, make sure you have a entire GPU for DIAL-MPC. As a online algorithm, it need a whole GPU to make it perform the best.

@jc-bao how much should I prepare for it? Because I have only 24g (4090) and there are no other program use gpu .
dial-mpc-sim --example unitree_go2_seq_jump_deploy
dial-mpc-plan --example unitree_go2_seq_jump_deploy

oh i see. a single 4090 should be more than enough. Just make sure you don't have other programs that consumes the computation power of the GPU.

I just taken another try .
After i run first command:
dial-mpc-sim --example unitree_go2_seq_jump_deploy
19g gpu occupied.
After i run second command:
dial-mpc-plan --example unitree_go2_seq_jump_deploy
almost all gpu occupied. and error happend soon .
Is this normal?

I also noticed some warning:
The NVIDIA driver's CUDA version is 12.0 which is older than the PTX compiler version 12.6.68. Because the driver is older than the PTX compiler version, XLA is disabling parallel compilation, which may slow down compilation. You should update your NVIDIA driver or use the NVIDIA-provided CUDA forward compatibility packages.
Is this a problem?

More infomation:
I just
export XLA_PYTHON_CLIENT_PREALLOCATE=false to all terminal .
It only use 2g gpu. All things are normal except "[WRAN] real overtime 24.0 ms"

export XLA_PYTHON_CLIENT_MEM_FRACTION=0.5
This command can also solve this problem on 4090 but also have overtime problem .

Thanks for reporting the issue! We just updated the code to fix a memory issue on the simulation code
@kassasin could you pull the latest code and try again?

Thank you very much, I just take a test. It is perfect !!!

By the way, overtime problem still have, Is this normal?

By the way, overtime problem still have, Is this normal?

Yeah it happens. For the stability of the examples we tuned up some horizon and sample settings to make the examples more stable. Feel free to change the settings a little in the example folder.
When overtime happens, DIAL-MPC will continue to execute action from the solution buffer. We don't see a significant downgrade in performance, but certainlly we are working on more optimized settings to prevent overtime from happening.


added NERutils to daisybell

Can you revise commit 9d921f1538846518bc77f23e67f5c56ad393e53d to not include the data?

Closed for archiving.


Issues with Linux-x86_64-qjsc: Permission denied

I had issues with Linux-x86_64-qjsc during npm run build on Centos 7, Nodejs 14.7:
Error: Command failed: ./node_modules/near-sdk-js/res/Linux-x86_64-qjsc -c -m -o build/status-message.h -N code build/status-message.js
/bin/sh: ./node_modules/near-sdk-js/res/Linux-x86_64-qjsc: Permission denied

    at ChildProcess.exithandler (child_process.js:390:12)
    at ChildProcess.emit (events.js:400:28)
    at maybeClose (internal/child_process.js:1055:16)
    at Socket.<anonymous> (internal/child_process.js:441:11)
    at Socket.emit (events.js:400:28)
    at Pipe.<anonymous> (net.js:675:12) {
  killed: false,
  code: 126,
  signal: null,
  cmd: './node_modules/near-sdk-js/res/Linux-x86_64-qjsc -c -m -o build/status-message.h -N code build/status-message.js',
  stdout: '',
  stderr: '/bin/sh: ./node_modules/near-sdk-js/res/Linux-x86_64-qjsc: Permission denied\n'
}

chmod +x ./node_modules/near-sdk-js/res/Linux-x86_64-qjsc resolved my problem.

It's not reproducible to me, maybe it's fixed? Do you check the latest 0.3 version

I was this issue should be fixed now. @zavodil please, check the latest version of JS SDK. (0.4.0+).


How to call diagnosticsForApplicationWithBundleID from fbsimctl?

I'm trying to get the data/Containers/Data/Application/<app_id> path using the diagnose command.
$ fbsimctl --state=booted diagnose bundle.id
xcrun works.

$ xcrun simctl get_app_container booted bundle.id

[diagnose] Action: Diagnose
===========================

	diagnose {{ --current-format | --path | --content }} [diagnose/query]

	--content
	--current-format
	--path

[diagnose/query] Diagnose: Query
================================

	{{ <application> | <bundle-id> }} <string>+

get_app_container in simctl will only return the location that the Application Bundle is installed into and not the "Home Directory" of an Application that is used at runtime. These are different directories and there is know currently known API for obtaining this directory.  You can see the install path for an application by using list_apps, but not for the Application's Documents Jail.
This can currently be inferred from a running Application, but not for an Application that is not running. We could expose this in list_apps instead, which might make more sense.

We could persist this data by writing to a file that maps bundle_id to Application Documents jail every time FBSimulatorControl launches an Application. This means that the directory could be inferred assuming there was a prior launch of the Application.

I'm currently using this approach. I calculate the data application path:
def app_path(bundle_id)
    path = `xcrun simctl get_app_container booted #{bundle_id}`.strip
    raise 'get_app_container command failed' unless $CHILD_STATUS.success?
    path = join(path, '../' * 4, 'Data/Application')
    raise "path doesn't exit: #{path}" unless File.exist? path
    path
  end

then parse the plists until I find a match:
def metadata_id(plist)
    result = `/usr/libexec/PlistBuddy -c 'Print MCMMetadataIdentifier' "#{plist}"`.strip
    raise 'PlistBuddy command failed' unless $CHILD_STATUS.success?
    result
  end

This can currently be inferred from a running Application, but not for an Application that is not running

I think exposing this info for the current app is sufficient for my use case. EarlGrey writes data to this directory and I'm trying to copy the results to a new folder after the tests finish executing.

We could persist this data by writing to a file that maps bundle_id to Application Documents jail every time FBSimulatorControl launches an Application.

If there was a fbsimctl command to list all the currently known bundle_id mappings then I think that'd work as well.

I wasn't aware that it was possible to get the App Container in that way, but I suppose that makes sense given iOS has to know the path of the Application container in any case.
With that knowledge it should absolutely be possible to add this as an API in FBSimulatorControl, we just need to get the path to the same plist parse it and then combine this data with the list of installed Applications.

This is how we have been finding the data container in Calabash iOS and in Xamarin UITest.


Only copy rootfs /registry dir to master0

Now we copy /registry to all nodes.

@fanux I guess this problem could be solved by not sending registry files?

What if execution machine is not master0?

What if execution machine is not master0?

and is it good to send registry to master0 only?

Remote mount it on master0 and copy it locally.


publish with 3.19.8

while i am publishing with 3.19.8 iis server return 404.but no problem in localhost. problem disappears when I just downgrade.

I'm afraid that we cannot reproduce such issue.