Adds fully-functioning breadcrumb

Motivation

APPDUX-185
What
 As stated in the linked Jira ticked above, this PR adds " an additional leaf in the breadcrumbs for 'Solution Patterns' ... a hyperlink to the home page with the Solution Patterns tab selected."
Why

This link did not exist previously.
How
 Tried several methods for using an`href` together with an `onClick` method on the `Tab` component. After doing a lot of research, I removed the `TabContent` refs which were the source of the problem, since the correct content for the active tab was not rendering.
Verification Steps

Checklist:

[ ] Code has been tested locally by PR requester
[ ] Changes have been successfully verified by another team member

Progress

[x] Finished task
[ ] TODO

Additional Notes

Note the new "Solution Patterns" link in the breadcrumb.

That link takes you here:

@tiffanynolan @mfrances17 opened https://issues.redhat.com/browse/APPDUX-214 to address your comments here -- thank you!


Add tauri files.

Now can launch application with Tauri.
TODO:

[x] : Add save window position mechanism
[x] : application info check
[x] : Add publish GitHub workflow

@sheepla
Please check application information.

https://github.com/sheepla/csv-grid-viewer/blob/8bde469ea34e6e1736723c0cb5e0a204c790cba8/src-tauri/Cargo.toml#L2-L5
https://github.com/sheepla/csv-grid-viewer/blob/8bde469ea34e6e1736723c0cb5e0a204c790cba8/src-tauri/tauri.conf.json#L9
https://github.com/sheepla/csv-grid-viewer/blob/8bde469ea34e6e1736723c0cb5e0a204c790cba8/src-tauri/tauri.conf.json#L22
https://github.com/sheepla/csv-grid-viewer/blob/8bde469ea34e6e1736723c0cb5e0a204c790cba8/src-tauri/tauri.conf.json#L33

@sheepla
I added publish workflow in f26b1574aa07f04eb98fde47b2d8869d44b92623.
tauri-action use src-tauri/tauri.conf.json's version.
You need fix src-tauri/tauri.conf.json's version when release.

Tauri environment info:

https://tauri.app/v1/guides/getting-started/prerequisites
https://github.com/mikoto2000/docker-images/blob/master/tauri/Dockerfile

Thank you for your PR! ✨ I'm now verifying that your fork works well.

I was able to confirm the operation. Thank you, I'll merge!


add user guide docs for kubectl exec, proxy, and port-forward

user guide for kubectl exec, proxy and port-forward
@ncdc @bgrant0607 @nikhiljindal

Please run hack/run-gendocs.sh

cc @mikedanese

Why does this require three files? Why not one with an index on top. That would be more navigable. If there is a reason, the file names should describe the context instead of {1,2,3}. e.g. onnecting-to-applications-with-kubectl-proxy

Thanks @mikedanese. I'll change the name of the files. We can merge them later if we have to.

LGTM as is. Feel free to fixup in follow ups.

one of the shippable runs passed, integration flaked in the other one (waiting for pod to come up)
merging


Feature Request: set own id for task.

Currently the id is created in tasks.py
    tag = uuid()
    # build the task package
    task = {
        "id": tag[1],
        "name": keywords.pop("task_name", None)
        or q_options.pop("task_name", None)
        or tag[0],
        "func": func,
        "args": args,
    }

For me it would be easier to set the task id like:
    tag = uuid()
    # build the task package
    task = {
        "id": kewords.get("id", None) or tag[1],
        "name": keywords.pop("task_name", None)
        or q_options.pop("task_name", None)
        or tag[0],
        "func": func,
        "args": args,
    }

Is it possible to have this?

Thanks for the suggestion. Could you elaborate on the usecase for this a bit more?
I am a little hesitant about implementing this. The id should always be unique as it's used to lookup the task in the database. We can be fairly certain that a normal uuid is unique. By implementing this, we would be shifting that responsibility to the developer.

My problem is: that i want to track the status in my own database (also the signals).
Now i have a timing problem. The signal from the queue can be faster then the update of database entry with the queue id.
If i can set the id by myself, the entry in the database will be there and i can easy update it.

Oh, interesting use case. Thanks for elaborating. I will think about it.
For now, I think you should be able to get away with setting the task_name instead. https://django-q2.readthedocs.io/en/master/tasks.html#task-name
You should be able to get tasks with that as well. For example:
task_name = "test1123"
async_task(do_something, 1, task_name=task_name)
Task.objects.get(name=task_name)

Just make sure that the task_name is a maximum of 100 characters, is unique, and is preferably not 32 characters. The database does not check on that, so you will have to do that yourself.

Question: Why are these limitations, what is the source of this.

maximum of 100 characters, is unique, and is preferably not exactly 32 character

The name field in the Task model has a max_length of 100 characters. It needs to be unique, because if it's not, you won't be able to get the correct task (it will likely error because there would be multiple tasks with the same name). The name field doesn't check on uniqueness, unlike the id field.
A normal id is always 32 characters long. You could end up with a conflict with a generated id if you make them 32 characters long. It first tries to fetch the result based on id and then on name. See this part:
https://github.com/django-q2/django-q2/blob/68af2ae13e6eefbfa740e6730b8ea9ffdb7d6ad2/django_q/models.py#L43-L48


Migrate the Travis configuration to travis-ci.com

Description
Fix #5041
Related issue and scope

[x] I opened an issue to propose and discuss this change (#5041)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[x] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

I pushed a new commit 3 hours ago, but the CI has not yet started..
It would severely degrade productivity.
If this is because of other jobs running and my job is waiting for it to be finished, we may need to find a way to deal with this.

I pushed a new commit 3 hours ago, but the CI has not yet started..
It would severely degrade productivity.
If this is because of other jobs running and my job is waiting for it to be finished, we may need to find a way to deal with this.

Codecov Report

Merging #5042 (28bef76) into master (4babe39) will decrease coverage by 54.72%.
The diff coverage is n/a.

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

Codecov Report

Merging #5042 (28bef76) into master (4babe39) will decrease coverage by 54.72%.
The diff coverage is n/a.

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

Can we use GitHub actions at all to speed some things up?
I'm surprised old job don't get replaced by new ones - can you cancel them manually?

Can we use GitHub actions at all to speed some things up?
I'm surprised old job don't get replaced by new ones - can you cancel them manually?

@rabbah I reported the issue to the Travis team and they are investigating now.
I tried restarting the build by manual intervention but nothing changed.

@rabbah I reported the issue to the Travis team and they are investigating now.
I tried restarting the build by manual intervention but nothing changed.

maybe try with github actions is a good option? I did tried with them and it worked well, additionally they are much faster than travis

maybe try with github actions is a good option? I did tried with them and it worked well, additionally they are much faster than travis

Now I only have this test.

Now I only have this test.

There's some discussion of GitHub Actions over on builds@apache recently (http://mail-archives.us.apache.org/mod_mbox/www-builds/).  It seems like the backlog to execute GHA is fairly long for repos in the Apache org, so not clear they will be any better than travis.

There's some discussion of GitHub Actions over on builds@apache recently (http://mail-archives.us.apache.org/mod_mbox/www-builds/).  It seems like the backlog to execute GHA is fairly long for repos in the Apache org, so not clear they will be any better than travis.

It's possible to run GHA "on prem" (some other cloud). Would we be able to do that? I can arrange for us to have some compute cycles.

It's possible to run GHA "on prem" (some other cloud). Would we be able to do that? I can arrange for us to have some compute cycles.

Tests are failed again due to the rate limit on the Docker hub.
4.0: Pulling from library/redis, stderr: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit [marker:invoker_docker.pull_error:52736:52535]
    [2021-01-14T20:05:34.817Z] [ERROR] [#tid_sid_apiMgmt] [StandaloneOpenWhisk] Error starting Api Gatewayorg.apache.openwhisk.core.containerpool.docker.ProcessUnsuccessfulException: info: command was unsuccessful, code: 1 (unsuccessful), stdout: 4.0: Pulling from library/redis

IIRC, @rabbah requested an exemption to Docker, and seems it's not yet applied.
Regarding the GHA "on prem", it's essential to have a stable CI environment as it's not easy for contributors to debug an issue with his change if the reason for CI test failures varies every time.
With the indeterministic behavior of Travis CI, I am pro to GHA with the reliable underlying infrastructure.
And as @jiangpengcheng said, Travis CI is generally very slow due to limited resources.

Tests are failed again due to the rate limit on the Docker hub.
4.0: Pulling from library/redis, stderr: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit [marker:invoker_docker.pull_error:52736:52535]
    [2021-01-14T20:05:34.817Z] [ERROR] [#tid_sid_apiMgmt] [StandaloneOpenWhisk] Error starting Api Gatewayorg.apache.openwhisk.core.containerpool.docker.ProcessUnsuccessfulException: info: command was unsuccessful, code: 1 (unsuccessful), stdout: 4.0: Pulling from library/redis

IIRC, @rabbah requested an exemption to Docker, and seems it's not yet applied.
Regarding the GHA "on prem", it's essential to have a stable CI environment as it's not easy for contributors to debug an issue with his change if the reason for CI test failures varies every time.
With the indeterministic behavior of Travis CI, I am pro to GHA with the reliable underlying infrastructure.
And as @jiangpengcheng said, Travis CI is generally very slow due to limited resources.

Finally, it passed all tests.
But I had to rerun some jobs manually and repeatedly to pass tests.
I observed many different reasons:

Docker rate limiting
CI tests heisenbug
Unexpected behavior of Travis's environment.

All of these should be addressed for better productivity.
Also, it relies on python2, we need to migrate to python3 as soon as possible.
Since there is some compatibility issue with python3, @jiangpengcheng `s work https://github.com/apache/openwhisk/pull/5036 is also very important.

Finally, it passed all tests.
But I had to rerun some jobs manually and repeatedly to pass tests.
I observed many different reasons:

Docker rate limiting
CI tests heisenbug
Unexpected behavior of Travis's environment.

All of these should be addressed for better productivity.
Also, it relies on python2, we need to migrate to python3 as soon as possible.
Since there is some compatibility issue with python3, @jiangpengcheng `s work https://github.com/apache/openwhisk/pull/5036 is also very important.


Make the crates buildable with only rustls

It would be very nice if all the crates could be built without native TLS. This could be done either via a feature flag or just make sure that all dependencies are configured to use rustls.
E.g. the azure_core package currently has reqwest as a dependency but is not configured to use rustls.

It's a good idea.  👍
We'll have to delay this until we have completed the crates rewrite and the core crate reorg though.
Let's keep this open to track it.

rustls has been supported for a while now.
https://github.com/Azure/azure-sdk-for-rust/blob/06f56a422c6c3ef3ff0332525d991cc550df4a11/sdk/core/Cargo.toml#L51

Is there a way to build azure_security_keyvault with only rustls? I can't seem to make it happen.

Yes, use it with default-features = false and the feature enable_reqwest_rustls

I see; it just hasn't been released yet. Thanks. (Turns out rustls still has a C dependency that doesn't build out of the box for me, so I went back to openssl, but I'll see if I can get that working once this makes it to crates.io.)

Yes, use it with default-features = false and the feature enable_reqwest_rustls

Where are the crate features documented? Had to find this via searching github closed issues


Active record PoC

Life is too short for writing SQL queries
Closes #3

➜  tepatitlan git:(active-record-poc) ruby test/test_doc.rb
Run options: --seed 63422

# Running:

......

Finished in 0.226878s, 26.4459 runs/s, 35.2612 assertions/s.

6 runs, 8 assertions, 0 failures, 0 errors, 0 skips


Update program-list.json

Summary
< a quick summary of the associated pull request >
Quality Assurance Checklist
< confirmation of this pull request meeting the following requirements, prior to merge >

Review Items
Y/N

Site has a publicly known bug bounty
Y

Disclosure terms are publicly available
Y

Public URL
Y

Single Source, or all sources appended
Y

Hey,
The policy_url isn't public


Unable to compile code with pinocchio::computeCollisions() with ROS 2 Humble binary install

Bug description
I've installed ros-humble-pinocchio package (it's version 2.6.21) which claims to have HPP-FCL support. However, I don't seem to be able to use collision checking functions.
Expected behavior
Compiling code that calls computeCollisions() should work.
Reproduction steps
I've successfully written a good deal of code, that loads models and computes forward kinematics and Jacobians... but when I try to bring in the computeCollisions() functions I get a build error:
error: ‘computeCollisions’ is not a member of ‘pinocchio’

I have included the header: #include "pinocchio/algorithm/geometry.hpp", which appears to be the right one for 2.6.21.
Am I missing something obvious, or is there an issue with HPP-FCL support in the installed version?
I also tried to build Pinocchio 2.6.21 from source, and even after hard-coding the CMake option to build with collision support, this issue still persists. Seems none of the unit tests / examples involving collisions were compiled regardless... but I'm also very bad at understanding CMake, so it's likely user error.
System

OS: Ubuntu 22.04
Pinocchio version: 2.6.21 (from binaries)

@wxmerkt @nim65s Any clue on this issue?

I'll be able to look into this next week, if @wxmerkt doesn't have any spare time before that

@scastro-bdai Could you provide reproducible command lines to try quickly in a docker image?

Switching to my personal account, but it's still me!
I've made a simple repo here: https://github.com/sea-bass/pinocchio_ros_cpp_example
As stated in the repo README, you should be able to do:
docker compose build
docker compose run base

Once you're in the container, you can do colcon build to build the package, which should work fine.
Now go into the file pinocchio_ros_example/src/pinocchio_example.cpp and uncomment the line that calls computeCollisions() and you'll find my error:
/workspace/src/pinocchio_ros_example/src/pinocchio_example.cpp:16:28: error: ‘computeCollisions’ is not a member of ‘pinocchio’
   16 |   auto result = pinocchio::computeCollisions(model, data, collision_model, collision_data, q);

Checking the binary build log shows that it compiles with PINOCCHIO_WITH_HPP_FCL and also runs the collision tests successfully: https://build.ros2.org/job/Hbin_uJ64__pinocchio__ubuntu_jammy_amd64__binary/95/consoleFull
Debug notes:
Running the standard Docker image, installing Pinocchio from binaries shows HPP_FCL is included:
docker run -it --rm ros:humble /bin/bash
apt update && apt install -y ros-humble-pinocchio
python3 -c "import pinocchio ; print(pinocchio.WITH_HPP_FCL)"

When using the repro example (thank you!), it shows that it cannot find hpp-fcl during configuration. This is because it's not included in the exported dependencies, e.g. adding
message (WARNING ${pinocchio_LIBRARIES})

shows that we are not linking to or exporting the dependency to hpp-fcl.
However, we can see that the pinocchioTargets.cmake includes hpp-fcl for the pinocchio::pinocchio target.
So with this workaround, it compiles and runs:
ament_target_dependencies(pinocchio_example Eigen3 eigen3_cmake_module)
target_link_libraries(pinocchio_example PUBLIC pinocchio::pinocchio)

I.e. linking directly using CMake rather than using ament. I am not too familiar with ament so cannot say where exactly the packaging issue comes in.
I fixed your example with this workaround and now it works fine: https://github.com/wxmerkt/pinocchio_ros_cpp_example/commit/d000ca64c1b7f44838ee48357f6de4d6da3935b4

Brilliant, thank you for looking into this!
I also don't know much about the inner workings of ament, but this workaround will for sure let us carry on with our work, without the need to build Pinocchio from source.

Thanks @wxmerkt !

By the way... I fleshed out the example in https://github.com/sea-bass/pinocchio_ros_cpp_example, so now it runs and hopefully serves as an example for people using ROS 2 with Pinocchio.
If there is any interest in this going in the regular documentation here, I'm happy to donate this example so it doesn't live on my personal account.

Hi @wxmerkt -- not sure if you prefer a new issue, but I just got sent this (https://github.com/sea-bass/pinocchio_ros_cpp_example/issues/1), and can also reproduce it locally.
So it seems like on Ubuntu 24.04, the same problem still persists even when we do target_link_libraries?


New images

Adding more index images.  Also changing link for the contribution in shape classifier to source.

Beautiful work!!


Fix #819

If the result value is extracted and guarded by a throw in send then the value should be passed directly to postInitSend.
I think it would be good to set up some fixtures that can run in a separate node.js test suite to verify that ports are working okay to avoid regressions like this in the future, but that's a discussion for the ML.
#819

Thanks for the quick fix @lukewestby! This is released as 5.1.1 now. Sorry to folk who ran into this!

👍 any time! setupIncomingPort() is near to my heart


Copy hang(s) with tilelive-copy + omnivore + stdout

In testing @dnomadb ran into a situation where this combination of things hangs:

tilelive-copy
omnivore source
stdout (serialtiles) destination

Example command:
tilelive-copy omnivore:///path/to/data.geojson

My hunch is that there's multiple things causing tilelive-copy hangs in this scenario.

source/sink in omnivore need to be closed for node to exit properly. We're getting around this with an explicit process.exit(0) here and this works https://github.com/mapbox/tilelive.js/commit/5f0aab00a376c03f09f0b7d60e6eaf09ee93d78f
tilelive.copy() will never call the callback when the dst passed in is process.stdout because this is a special node stream that never emits finish (per https://nodejs.org/api/process.html#process_process_stdout)

Proposal

[ ] let's prove no 2 by adding a copy test like this outstream test (https://github.com/mapbox/tilelive.js/blob/master/test/copy.test.js#L148-L163) but with process.stdout as the outstream
[ ] can/does this need to be the finish event? or could it listen for stop which is managed by tilelive itself? https://github.com/mapbox/tilelive.js/blob/master/lib/tilelive.js#L389 -- it seems like if we can this would address the issue

cc @dnomadb @GretaCB @rclark

Listening to a read-stream event (stop, in this case) is a little dubious because, potentially, the write stream has not yet had a chance to perform all its writing. But then, like you say, process.stdout is special, and .writes() to stdout might be synchronous / guaranteed, my understanding is just fuzzy here.

Hrm, the stop event happens on the put stream no? https://github.com/mapbox/tilelive.js/blob/master/lib/tilelive.js#L374

Sorry, my bad -- there is no tilelive writable stream in the process.stdout case though.
Instead the caller has passed in an output stream and "put" is simply that stream. In the bin/tilelive-copy case that is process.stdout.

We could consider adjusting bin/tilelive-copy such that it doesn't allow stdout, but accepts an output file argument.
bin/tilelive-copy could provide tilelive.copy with a custom writable stream that writes to stdout and emits a finish event, e.g.

var customWritable = new stream.Writable();
customWritable._write = function(chunk, enc, callback) {
  process.stdout.write(chunk);
  callback();
});

Any issue with replacing stdout with a tmp file of some kind? I also like the idea of creating a custom writestream function. I can jump on this.

Small note: I hope process.exit(0) can be only a temporary stopgap as this will cause node to crash if any work is being done in the threadpool when it is called (usually not the case but can happen). You would think that process.exit would wait for libuv to finish any work, but this is not what I've observed.

@springmeyer only temporary. About to create a new branch with a more permanent fix.

Merged and deployed https://github.com/mapbox/unpacker/pull/478


Update P2114.apln

Before opening a pull request to add your solutions to this repository,
please go over the following checklist:

[x] I tested my solutions with the respective test cases from the LeetCode.com website;
[x] I added a couple of comments with an overview of how my solutions work;

[ ] I included my GitHub nickname (optional);

[x] My solutions were added at the bottom of the solutions that already existed;
[x] I added my solutions to the runtime comparison tradfns, when such tradfns were present.

Nice solution! Wanting to sum things up plays nicely with the fact that, when we mix, we get trailing 0s in the shorter sentences. Thanks for your contribution!


clarify nodes only update labels upon registration

A simple update to the nodes doc, which I thought might clarify that labels are only updated upon registration with the API server.

@kubernetes/sig-node-pr-reviews is this update technically accurate? Any provisos?
Feel free to unhold this once it has tech signoff from SIG Node.

      --node-labels mapStringString                              <Warning: Alpha feature> Labels to add when registering the node in the cluster.  Labels must be key=value pairs separated by ','. Labels in the 'kubernetes.io' namespace must begin with an allowed prefix (kubelet.kubernetes.io, node.kubernetes.io) or be in the specifically allowed set (beta.kubernetes.io/arch, beta.kubernetes.io/instance-type, beta.kubernetes.io/os, failure-domain.beta.kubernetes.io/region, failure-domain.beta.kubernetes.io/zone, kubernetes.io/arch, kubernetes.io/hostname, kubernetes.io/os, node.kubernetes.io/instance-type, topology.kubernetes.io/region, topology.kubernetes.io/zone)

This flag is for Labels to add when registering the node in the cluster.  IMO, this is technically accurate.
Only one nil is commented above about the reset.

Hi @pacoxu
I saw https://github.com/kubernetes/website/pull/44689#issuecomment-1886809526 but am unsure if that is signoff or a request to revise the PR. Can you clarify?

@pacoxu Please can you advise on Tim's comments above?

Agree with Tim's comments https://github.com/kubernetes/website/pull/44689#discussion_r1506219498.

Hello @kurtado , could you please address the PR per this comment?

Hello @kurtado , could you please address the PR per this comment?

@divya-mohan0209 @sftim done

/hold cancel
/lgtm
/approve


Controller Spawner couldn‘t find the expected controller_manager ROS interface.

Hello!
When I run the command "roslaunch nav_gym start_nav_gym.launch", warning "Controller Spawner couldn‘t find the expected controller_manager ROS interface." appears.
I have confirmed that 'controller_manager' has been installed.
I have google this problem and try some possible solutions but none of them work.
The answer int the following page mentions the problem of the namespace.
https://answers.ros.org/question/214712/gazebo-controller-spawner-warning/
Does this problem result from it?
Hope you can help me.

Hi!,
Does above warning result in problem in simulation?
And did you suceed in visualizing with RViz?
roslaunch nav_gym view_robot.launch

Hi!,
Does above warning result in problem in simulation?
And did you suceed in visualizing with RViz?
roslaunch nav_gym view_robot.launch

In fact, error occurs when I try to visualize with RViz.

And I guess this waring in "start_nav_gym.launch" may be the reason.

I guess the error is related to some third party ROS packages.
Which version of ROS are you using now?

I guess the error is related to some third party ROS packages.
Which version of ROS are you using now?

Kinetic.


Suport Fan Control

Version of the moonraker integration
1.2.0
Describe your setup
Creality K1 Printer with Klipper, Moonraker, Fluidd, Mainsail
Describe the bug
I have 4 numbers in my integration, one for the light, and 3 for the fans (hotend, side and rear). The light works fine, but the fans don´t, when i set the fans to some value, they do nothing on the machine, and a few seconds later, they values are updated in home assistant to a really low value:

On the mainsail or fluidd interface, i can control them correctly, so it must be a problem in the integration.
Moonraker Logs
logs.log

From what I noticed on my K1Max, the printer recognizes the fan speed as a range 0-255.  The integration appears to pull the data from the printer as a percentage of that range, but when you set the fan speed in Home Assistant using the integration, it sends the fan speed as a number instead of a percentage of the range.  For example, if you set the fan speed at 70% in Home Assistant, it sets the fan speed in the printer as 0.70 (which is 0.70 in a range of 0-255).
The LED works correctly because the printer has a range of 0-1 for the LED, so the percentages work correctly.

Fan should not be controlable just yet. We thought they would be excluded. We don't have adjustable fans so we can't test it

suplicate of #229


Temporal Information

Hi,
I am interested in your project and I would like to go in detail for an aspect related to temporal information. Are you training your model on video datasets? Are you getting temporal information from the dataset? or your model has been trained on single images considering only spatial information?
Thank you so much.
Best,
Francesca

We trained it on DAVIS, YouTubeVOS, and BL30K which are all video datasets. Static images are used for pre-training only.

Thank you so much. So if I would likes ti re-train tour model what do you suggest? To apply the Same methodology of pre-training with static images and then with videos? What was the advantage of the pre-training with static images?

Unless you have more data that you would like to include, I would suggest training it in the same way.
For the benefits of pre-training, you can check STM out: https://arxiv.org/abs/1904.00607.


Linking react-native-smart-splash-screen fails because str.replace is not a function

Description
Debugging some build issues with my project, I tried doing a react-native link and got
rnpm-install info Android module react-native-smart-splash-screen is already linked
rnpm-install info Linking react-native-smart-splash-screen ios dependency
rnpm-install ERR! It seems something went wrong while linking. Error: str.replace is not a function
Please file an issue here: https://github.com/facebook/react-native/issues

str.replace is not a function

Reproduction
I am not able to reproduce this in a fresh project (version 0.42.0), where I tried
react-native init Test
rnpm install react-native-smart-splash-screen
react-native link

Solution
?
But the linker told me to file this bug, so I did.
Additional Information

React Native version: 0.40.0
Platform: iOS
Operating System: MacOS

Turns out it was because I was installing in a nonstandard way.


PXP-511: [CLI] Develop the connect-instance command

Summary

Ticket: PXP-511
What's Changed

Added

[x] add instances connect command

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jk-gan
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jk-gan, mfauzaan, onimsha
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Change channels, input/output, length integers all to usize

Some of them were u32 still.
Fixes #122

cool, this removes a lot of casting!


FIX:  qt5 macOS 11 compatibility

Reference issue
Fixes #8525 by setting the environment variable before launching GUIs.
TODO

[x] test on macOS 10

There might be other places that we want something like this -- for example in matplotlib code -- so I think we probably want a FAQ entry or so. And PyQt5 5.12.2 will have this on by default. But this already seems like a step in the right direction so I'll merge. Thanks @christianbrodbeck


Improve log_softmax performance by OneDNN library

The original request:
https://github.com/apache/incubator-mxnet/pull/18001#issuecomment-613666611
The related code:
https://oneapi-src.github.io/oneDNN/dev_guide_logsoftmax.html
https://github.com/apache/incubator-mxnet/blob/681cfc4205a568d3bfc35da1a601489abdd44074/src/operator/nn/log_softmax.cc

@pengzhao-intel Can we close this issue? Link to PR https://github.com/apache/incubator-mxnet/pull/18320

closing since PR is merged.


Ambassador v1.14.1 not splitting the traffic properly in Knative

Describe the bug
We installed Knative following this docs : https://knative.dev/docs/admin/install/knative-with-operators/#installing-with-different-networking-layers where we used Ambassador as our Ingress network layer.
We followed this docs to test the traffic split feature : https://knative.dev/development/getting-started/first-traffic-split/.
We observed that the traffic always is going to the  latest service revision all the time so traffic splitting is not working as expected.
We did a little analysis and it seems that the issue come from : https://github.com/emissary-ingress/emissary/blob/master/python/ambassador/fetch/knative.py#L73 where the global_headers is overriding the headers causing a bad Ambassador envoy configuration.
To Reproduce
Steps to reproduce the behavior:

Follow this tutorial: https://knative.dev/development/getting-started/first-traffic-split/.
Check the Knative Service configuration: Traffic splitted 50/50 in both revisions.

NAME             SERVICE   TRAFFIC   TAGS   GENERATION   AGE     CONDITIONS   READY   REASON
hello-world-v2   hello     50%              2            2d19h   3 OK / 4     True
hello-world      hello     50%              1            2d19h   3 OK / 4     True

Check the Knative serving ingress rule: kubectl describe kingress hello

 Name:         hello
Namespace:    default
Labels:       serving.knative.dev/route=hello
              serving.knative.dev/routeNamespace=default
              serving.knative.dev/service=hello
Annotations:  networking.internal.knative.dev/rollout:
                {"configurations":[{"configurationName":"hello","percent":50,"revisions":[{"revisionName":"hello-world-v2","percent":50}],"stepParams":{}}...
              networking.knative.dev/ingress.class: ambassador.ingress.networking.knative.dev
              serving.knative.dev/creator: minikube-user
              serving.knative.dev/lastModifier: minikube-user
API Version:  networking.internal.knative.dev/v1alpha1
Kind:         Ingress
Metadata:
  Creation Timestamp:  2021-09-03T12:36:57Z
  Generation:          3
  Managed Fields:
    API Version:  networking.internal.knative.dev/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:networking.internal.knative.dev/rollout:
          f:networking.knative.dev/ingress.class:
          f:serving.knative.dev/creator:
          f:serving.knative.dev/lastModifier:
        f:labels:
          .:
          f:serving.knative.dev/route:
          f:serving.knative.dev/routeNamespace:
          f:serving.knative.dev/service:
        f:ownerReferences:
          .:
          k:{"uid":"48c5f4a0-d7be-41af-85f4-30ec71b0547d"}:
            .:
            f:apiVersion:
            f:blockOwnerDeletion:
            f:controller:
            f:kind:
            f:name:
            f:uid:
      f:spec:
        .:
        f:httpOption:
        f:rules:
    Manager:      controller
    Operation:    Update
    Time:         2021-09-03T12:36:57Z
    API Version:  networking.internal.knative.dev/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        .:
        f:conditions:
        f:loadBalancer:
          .:
          f:ingress:
        f:observedGeneration:
        f:privateLoadBalancer:
          .:
          f:ingress:
    Manager:    kubestatus
    Operation:  Update
    Time:       2021-09-03T12:36:57Z
  Owner References:
    API Version:           serving.knative.dev/v1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  Route
    Name:                  hello
    UID:                   48c5f4a0-d7be-41af-85f4-30ec71b0547d
  Resource Version:        49273
  UID:                     6109b01f-d91e-4bee-abb8-ae59c419d8c8
Spec:
  Http Option:  Enabled
  Rules:
    Hosts:
      hello.default
      hello.default.svc
      hello.default.svc.cluster.local
    Http:
      Paths:
        Splits:
          Append Headers:
            Knative - Serving - Namespace:  default
            Knative - Serving - Revision:   hello-world-v2
          Percent:                          50
          Service Name:                     hello-world-v2
          Service Namespace:                default
          Service Port:                     80
          Append Headers:
            Knative - Serving - Namespace:  default
            Knative - Serving - Revision:   hello-world
          Percent:                          50
          Service Name:                     hello-world
          Service Namespace:                default
          Service Port:                     80
    Visibility:                             ClusterLocal
    Hosts:
      hello.default.example.com
    Http:
      Paths:
        Splits:
          Append Headers:
            Knative - Serving - Namespace:  default
            Knative - Serving - Revision:   hello-world-v2
          Percent:                          50
          Service Name:                     hello-world-v2
          Service Namespace:                default
          Service Port:                     80
          Append Headers:
            Knative - Serving - Namespace:  default
            Knative - Serving - Revision:   hello-world
          Percent:                          50
          Service Name:                     hello-world
          Service Namespace:                default
          Service Port:                     80
    Visibility:                             ExternalIP
Status:
  Conditions:
    Last Transition Time:  2021-09-03T12:58:30Z
    Status:                True
    Type:                  LoadBalancerReady
    Last Transition Time:  2021-09-03T12:58:30Z
    Status:                True
    Type:                  NetworkConfigured
    Last Transition Time:  2021-09-03T12:58:30Z
    Status:                True
    Type:                  Ready
  Load Balancer:
    Ingress:
      Domain Internal:  ambassador.default.svc.cluster.local
  Observed Generation:  3
  Private Load Balancer:
    Ingress:
      Domain Internal:  ambassador.default.svc.cluster.local
Events:                 <none>

Check the Ambassador envoy configuration generated base on the previous Ingress rule. You can see that there is an inconsistency.

    "request_headers_to_add": [
        {
        "append": true,
        "header": {
            "key": "Knative-Serving-Namespace",
            "value": "default"
        }
        },
        {
        "append": true,
        "header": {
            "key": "Knative-Serving-Revision",
            "value": "hello-world" # hello-world-v2 was expected, We had to change it manually to make it work.
        }
        }
    ],

All the traffic is sent to revision hello-world so it doesn't work as expected.

#!/bin/bash

for i in {1..10}; do
 curl http://<IP_ADDRESS>:49419 -H 'Host: hello.default.example.com'
done

Hello World!
Hello World!
Hello World!
Hello World!
Hello World!
Hello World!
Hello World!
Hello World!
Hello World!
Hello World!

Expected behavior
So we expected that the traffic is split between both revisions "hello-world" and "hello-world-v2" but it isn't the case.
All the traffic is going to the revision "hello-world" without taking in account the traffic configuration applied on this Knative service.
After to change the Ambassador envoy configuration, you can see that it works fine.

#!/bin/bash

for i in {1..10}; do
 curl http://<IP_ADDRESS>:49419 -H 'Host: hello.default.example.com'
done

Hello World!
Hello WorldV2!
Hello WorldV2!
Hello World!
Hello World!
Hello World!
Hello WorldV2!
Hello WorldV2!
Hello World!
Hello WorldV2!

Versions:

Ambassador: v1.14.1
Amazon EKS platform version: eks.1
Kubernetes v1.21
Knative: v0.25.0

Hello @impl
I've tested with the release https://github.com/emissary-ingress/emissary/releases/tag/v2.0.5 of Emissary Ingress and the problem persist.
Using knative-serving   1.0.0.
Do you have a ETA about when the fix will be ship ?
Thanks a lot.


Links not underlined when zoomed out in Chrome

Just FYI, I browse the web at 90% by default, and the links don't show up in Chrome. They show up at 100+% and seem to work fine in Firefox/Safari, though.

Confirmed—thanks for the report. Strange.

One option is to only apply our custom underline CSS when a browser zoom of 1 is detected:
Detection can be done with something like this:
var getBrowserZoom = function() {
  return window.outerWidth / (document.body.clientWidth + parseInt(getComputedStyle(document.body)['margin-left'], 10) + parseInt(getComputedStyle(document.body)['margin-left'], 10))
};

document.documentElement.setAttribute('data-browser-zoom', getBrowserZoom());

Then these lines would be prefixed with html[data-browser-zoom="1"]:
html[data-browser-zoom="1"] a:link {
  /* ... */
}

As Tufte CSS is a pure-CSS project, a JavaScript solution is not in-scope for this project. I like Adam's JS trick and it's a good answer for this problem in general, but we'll need to find a different answer within the context of "base" Tufte CSS.
Might it be possible to switch all the px declarations within a:link to em? Or would that lead to other problems?

Definitely worth a shot!

An alternative might be to add to the existing webkit media query, to allow for how webkit does sub-pixel rounding, something like:
@media screen and (-webkit-min-device-pixel-ratio: 0) { a:link { background-size: 0.05em 1px, 0.05em 1px, 2px 1.5px; background-position-y: 87%, 87%, 87%; } }

Or to use to top in the linear-gradient, something like:
a:link { background: linear-gradient(to top, transparent 1px, #333 1px, transparent 2px);
...}

and remove all the other background-* properties. Though this will also likely need to go into a media query so that the stops can be tailored for the different browser behaviours.

Likely an old Chrome bug that was fixed in previous releases. Links work fine at 90% on Chrome 74.0.3729.131. Issue should be safe to close.

Thanks for the report! I was able to replicate the OK behavior so closing.


Added support for Mandrill templated emails.  Added tests and did a litt...

...le refactoring.

Just looked this over and ran the tests and it looks good. I'll merge it into master, update a few things then push it up to pypi. Thanks!


Improved scopes for model parts

Each model part's VariableScope is stored in self._variable_scope and invoked using self.use_scope().
The above is used to make sure that @tensor properties use the right scope.

@jindrahelcl ping


fix: Fix getting stuck on "Loading terrain" since 1.20.4

This PR fixes an issue where the Limbo server does not send a PacketPlayOutGameEvent that tells the client to wait for the chunks, which is required since 1.20.4 for the client to get out of the "Loading terrain..." screen. (see wiki.vg/Protocol_FAQ).
While packet dumping to figure out the issue, I saw the server sends empty chunk packets forever, wasting bandwidth.
I fixed that by:

first, check if the player is in adventure mode, and if so, remove all chunks from chunksInRange that have already been sent
secondly, if chunksInRange is empty, return and don't send any chunk update packets

So then... I fixed the issue, but then I spent another 4 hours figuring out why the PacketPlayOutGameEvent is not being mapped. I then realized it was because the mappings.json file is only written once and never updated and because I only ever updated the jar, my addition to the mapping list never applied. This doesn't make sense to me whatsoever (and reading from a jar that's already in memory is much faster than from a file...), so I changed this to instead just read it from the jar.
Lastly, some stuff was incorrectly formatted, so I ran IntelliJ's formatter on the files I modified to fix that.

Hi, cool that you made this PR, I had this problem for a while now and it was really annoying me. (I hope LOOHP merges it soon)
I might have found a bug in the PR though (I wanted to see if it worked for me so I compiled a version of your PR).
For some reason, I'm not able to place or break any blocks (only client-side of course) in the limbo server anymore, which was possible before.
Could this maybe have something to do with the server sending empty chunk packets forever?

Hmm, I explicitly made it so that it doesn't send any already sent chunks if you're in adventure mode.
Not being able to place or break anything does sound like a chunk issue.
And sure enough, while writing this, I do believe I found an issue:
https://github.com/LOOHP/Limbo/blob/342404f58607544b738d453eefb862f0a7f2a1ee/src/main/java/com/loohp/limbo/player/PlayerInteractManager.java#L129-L134
chunksInRange and currentViewing should be swapped. In adventure, chunks cannot be modified, so if a chunk is already sent (which is the case if it's in currentViewing), it should be removed from chunksInRange.
However... I also realize now that this is wrong as well because now we're going to send the chunks we just removed in the next tick anyway. After all, they're no longer in currentViewing due to the currentViewing = chunksInRange assignment below:
https://github.com/LOOHP/Limbo/blob/342404f58607544b738d453eefb862f0a7f2a1ee/src/main/java/com/loohp/limbo/player/PlayerInteractManager.java#L168

I believe that should do the trick. Of course, the ideal solution would be to have some way to know if a chunk is updated.
But for now, this should keep the server from spamming empty chunk packets and optimize bandwidth usage for people running the server in adventure mode (that is, chunk updates are no longer being sent because blocks can't be modified anyway).

Thank you for the PR. I've cleaned up and formatted the code a bit. Right now, I've only included the PacketPlayOutGameEvent (I've renamed it to PacketPlayOutGameStateChange) and using the JSON files directly in the jar instead of the internal_data folder.
As for the adventure gamemode optimizations, it looks like more is needed to be tested and probably should be made as a separate change.


TypeError: Cannot read properties of undefined (reading 'config')

When inspecting a state machine that is defined in React via useMachine, I'm getting a crash of the inspector:
Looks like you've ended up in an invalid state. Refresh the page to retry.
The stack error and stack trace are:
_app-a1433d7431381a0c.js:647 TypeError: Cannot read properties of undefined (reading 'config')
    at 2471-4f879e2487bb6b05.js:1:16681
    at uU (framework-22003fc7e17fa3a0.js:9:84107)
    at o$ (framework-22003fc7e17fa3a0.js:9:113157)
    at framework-22003fc7e17fa3a0.js:9:111543
    at oU (framework-22003fc7e17fa3a0.js:9:111609)
    at oP (framework-22003fc7e17fa3a0.js:9:96238)
    at r8 (framework-22003fc7e17fa3a0.js:9:44812)
    at framework-22003fc7e17fa3a0.js:9:93602

Here's the minified code that is crashing:
    function ed(e) {
      var t;
      let {machine: s, state: r, isSelected: i} = e
        , l = er.S.machines.getDigraphConfigs.useMutation();
      (0,
      C.useEffect)( () => {
        l.mutate({
          // Crashes on this tRPC call because s isn't defined.
          definition: "createMachine(".concat(JSON.stringify(s.config), ")")
        })
      }
      , []);

I believe what's happening is a race condition. As I stepped through the XState Inspector window with breakpoints, I was able to get the inspector past this moment in the code without error. Then the inspect app rendered fine, until I reloaded the parent page.
I don't have a minimal reproduction right now, but I can stop this from happening immediately if I delay the initial events sent to the machine from the React component.

Can you provide a CodeSandbox reproduction?


Fixed typo in utils/functional.py

Thanks to @kai3n !

See https://en.wikipedia.org/wiki/Memoization


line break for comments

add line break in comments, is able to be compiled
but the line break is not correct or same as autorest.csharp.
Mainly because the way ejs template writes file is different from autorest.csharp (which has a dedicated write method which can detect current indentation)
and content of comments are not exactly the same.

/azp run autorest.powershell - PR Validation via azure-powershell-generation-m4 (Service: Elastic)

autorest.powershell - PR Validation via azure-powershell-generation-m4 (Service: HanaOnAzure)

/azp run


Change ontology term identifier

Ontology terms had an ambigious 'id' field and description. This PR renames the field to term_id to remove the confusion over the role of the field, as well as improves the comment for its proper use. A field 'term_uri' has been added that allows one to specify the full URI for a term if it is available.
Closes #621 #165

+1 Clear improvement.

+1

@david4096 (pls. don't forget the docs)

Thanks @mbaudis updated with some minor tweaks to the ontology documentation.

Related to discussion in #165

+1 with small modification (with input from @cmungall): "if no CURIE are available." -> "if no URI available".

Thanks @mcourtot! Updated!

Please check termId => term_id (if I understand the proto snake_case correctly); same for termUri => term_uri. I usually do things like that with serarch/replace over the whole tree; but don't tell anybody, please.
If fixed -> merge.

Thanks @mbaudis good to go!

Thanks everyone for your input @jmcmurry @mcourtot @drseb ! I'll be happy to integrate any further work on this data model as consensus is reached.
For now, I'd like to see if we can move ahead and take further discussion to another issue. This PR was designed to improve the situation from id to term_id and improve the comments, which it has done. To continue the discussion check out the below links:
Ontology Source Identification
Multiple Ontology Term URIs
OntologyTerm.id definition

That sounds good to me; thanks @david4096

And -10 to any date scheme that is not ISO-8601!

@cmungall  @drseb ... but reminding me of https://github.com/phenopackets/phenopacket-format/issues/75

@mcourtot @cmungall @david4096 This should now be updated to reflect the Vancouver discussions.

Hm - I tried and push a commit to the pr/694 branch to reflect the Vancouver changes but don't see them here. Hadn't tried and commit over a PR before, so maybe i'm looking at the wrong place?

@mbaudis @mcourtot I've incorporated your changes from https://github.com/ga4gh/schemas/pull/726 .
Since we have removed the URLs, I believe we need a way to manage them, or at least specify a place where they might be looked up. What do you think @cmungall ?

Thanks @david4096! We're planning on using OLS, http://www.ebi.ac.uk/ols/index to bind prefixes to their URIs. @simonjupp, @tburdett, do you have a specific link?

Implemented in the server here.


how to set default value for print ?

how to set default value for print?
i dont know set there value

paper is landscape (842 * 595)
contents size is 74%
text font size 10 pt

how to set value that is necessary for 1page print  ?

General print settings are a feature of our Pro builds. It may be added here at some point.


pytest with datafile

This is a first attempt. I would like to NOT include the datafile in the repo and instead download the file on demand. We can put the (small) datafile in a GitHub release, otherwise we need to host them somewhere.
@tstenner , how do you think we should get azure to download our test data? Within a script? Or within a pytest fixture? Something else?

Would git-lfs or git-annex be a viable option? Why don't you want to include (small) test files directly in this repo? If they are small, I don't see the problem (the test files should not be packaged of course).
In MNE, we have a separate repository just for our testing data, but the main problem is that downloading is super slow. Maybe this is faster when you attach files to a release, but isn't this difficult to manage? Do we have to move/copy all testing files for each new release then?

Why don't you want to include (small) test files directly in this repo?

(1) The way the package is structured currently, the tests travel with the python package to pypi. We could probably put the test data in a different folder, or manually remove them from the packages before uploading (seems like silly over-engineering to do it that way). This is also exactly the same test file that's in the parent repo.
(2) I don't want to inflate the git history with binaries. Seems not so bad right now, but it can become a problem quickly, especially because...
(3) there are plans (SCCN/Intheon) to add many more test files to the test suite, especially 'problematic' files.
Attaching to a release feels like the wrong solution. The main reason I want the test files in there at all is to automatically test file loading whenever someone makes a PR. If a new feature requires a new test file, how does one verify the feature before the test file is in a release?

I totally agree that we need a test suite that automatically runs with a PR. The more files we have in there the better. I think git-lfs should work pretty well for our purposes.

I would like to NOT include the datafile in the repo and instead download the file on demand.
Seconded. It's not always practical to clone a shallow copy and processing any data file every present in the repository slows everything down (or, as Clemens put it: "super slow") . With Git LFS it would be reasonable, but I think it's overkill. Also, once a big file gets pushed it's in the repository practically forever.

Also, once we isolate the broken part of a file it should be possible to create a synthetic test file that triggers the bug, but is much shorter.
For the benchmarks, we need huge files so I have small scripts that generate big files to test the different code paths on the fly and then delete them after. Those could stay in the repository.

@tstenner , how do you think we should get azure to download our test data?

It all depends what the CI should test. For one job (i.e., only one operating system), it doesn't really matter. For parallel jobs on Azure, I'd create one stage to download the files and then copy them to each job so the files get downloaded (and possibly cached) once per run and copying them to the CI workers is fast.

Within a script? Or within a pytest fixture? Something else?

I'd suggest in a script unless pytest handles downloading changed/new files efficiently. rsync would do this, but it'd need a dedicated host. Or a simple folder listing served via HTTP and wget.

but it'd still be nice to also test with real-world large files

Not with CI systems though. If you want to include some tests in the repo that are only run on your local computer (e.g., after checking for the presence of a specific folder and/or only invoked with a special argument to pytest) then that's fine. If you want the tests to be run on the CI servers then the files should be small or generated on the fly.

Yes, obviously we can't test large files with CIs, so I'm fine with only using small files for CIs. We should still try to run our tests on large files, because these might reveal issues that are not found in small files. We could run our tests on all files (small and large) manually before a new release. I'm open to the implementation details of how we want to make this work, and we also still need to solve the question where we store our large files (since I assume that you all seem to be OK with including small files in either this repo or a separate xdf-testdata repo - I'd prefer the separate repo because that way other repos can re-use the same test files).

Agreed, not within this repo. I don't have enough experience with git-lfs, does it have better performance with large binary files than normal git?

Does it have better performance with large binary files than normal git?

It basically uploads the files separately and replaces them with links, so it's a lot faster than normal git but only as fast as the place where the files get uploaded to.

Exactly. And we still don't know where to host the large files.

@cboulay could you go ahead and create an xdf-testdata repo within the xdf-modules organization?

Re how to do the actual testing, I think pytest-datafiles is not even required. This package's main purpose is to copy files to a temp dir in order to avoid modifying the original files. We don't need to do this, because (1) we're pulling our test files from a git repo (and we don't push), and (2) we don't modify our test files anyway.
I'd clone the example-files repo in an Azure script, and we can then use the test files with the @pytest.mark.parametrize decorator.


Laravel 11.x Compatibility

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 11.x.
Before merging, you need to:

Checkout the l11-compatibility branch
Review all comments for additional changes
Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.

:warning: The latest version of Laravel has a dependency for phpunit/phpunit of ^10.5. If you would like to also upgrade your tests, you may run the PHPUnit 10 Shift for free.

:information_source: Shift detected you do not have a CI workflow using GitHub Actions. If you would like, Shift can help you get started with the CI Generator. Although the Shift is paid, GitHub Actions is free and having a CI workflow will improve the stability and review process for your package.

:alembic: Using this package? If you would like to help test these changes or believe them to be compatible, you may update your project to reference this branch.
To do so, temporarily add Shift's fork to the repositories property of your composer.json:
{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/laravel-shift/livewire-status-board.git"
        }
    ]
}

Then update your dependency constraint to reference this branch:
{
    "require": {
        "asantibanez/livewire-status-board": "dev-l11-compatibility",
    }
}

Finally, run: composer update


Better error displaying

Basic information about errors should be displayed to players who have the permission permissify.admin.

This has been finished


LaneChange manoeuvre unstable

Hi, first of all thanks for all the effort input into make the scenario runner, I personally find it is very useful for my research. I would like to report an issue I have while running a scenario using python file.  I have pasted the sequence for one of the actors in my scenario. From the second lane change, it starts losing control and oscillating with an increasing amplitude, which causes not able to complete the third lane change.
Expected behavior
The expected behaviour will be DriveForward (using a timer of 5s) --> LaneChange left (for 1 lane) --> DrivieForward (using a timer for 5s) --> LaneChange right (for 1 lane) --> LaneChange right (for 1 lane) --> DriveForward (for 5s) --> LaneChange left --> DriveForward. However after the second lane change it lost control. I suspect it might be due to the previous waypoint follower not terminated? i have also attached a py_trees debuging image.
Screenshots, code

`sequence_1 = py_trees.composites.Sequence("1")
    sequence_1.add_child(ActorTransformSetter(self.other_actors[0], self._transform_visible1))
    just_drive = py_trees.composites.Parallel("DrivingForward", policy=py_trees.common.ParallelPolicy.SUCCESS_ON_ONE)
    v1_drive_forward = WaypointFollower(self.other_actors[0], 20)
    just_drive.add_child(v1_drive_forward)
    just_drive.add_child(LocalTimer(self.other_actors[0], 5))
    sequence_1.add_child(just_drive)
    sequence_1.add_child(LaneChange(self.other_actors[0], direction='left', speed=20.11675, distance_other_lane=40.2335))
    just_drive = py_trees.composites.Parallel("DrivingForward", policy=py_trees.common.ParallelPolicy.SUCCESS_ON_ONE)
    v1_drive_forward = WaypointFollower(self.other_actors[0], 24)
    just_drive.add_child(v1_drive_forward)
    just_drive.add_child(LocalTimer(self.other_actors[0], 5))
    sequence_1.add_child(just_drive)
    sequence_1.add_child(LaneChange(self.other_actors[0], direction='right', speed=20, distance_other_lane=40))
    sequence_1.add_child(LaneChange(self.other_actors[0], direction='right', speed=20, distance_other_lane=40))
    just_drive = py_trees.composites.Parallel("DrivingForward", policy=py_trees.common.ParallelPolicy.SUCCESS_ON_ONE)
    v1_drive_forward = WaypointFollower(self.other_actors[0], 20)
    just_drive.add_child(v1_drive_forward)
    just_drive.add_child(LocalTimer(self.other_actors[0], 5))
    sequence_1.add_child(just_drive)
    sequence_1.add_child(LaneChange(self.other_actors[0], direction='left', speed=20, distance_other_lane=40))
    v1_drive_forward = WaypointFollower(self.other_actors[0], 20)
    sequence_1.add_child( v1_drive_forward)`

Desktop (please complete the following information):

OS: [Ubuntu 20.04]
CARLA Version [<IP_ADDRESS>]
Python version [3.7]

Depending on the speed this oscillation is normal.

As @fabianoboril said, this might have been due the controllers, causing lane changes to not be done smoothly. We have been updating them quite a bit recently, so is this still happening? I'm preemptively closing this issue as this is quite an old post, but feel free to reopen it if needed


Data cleaning

Changes in this branch

Cleaned the script data
Created columns for season and episode
Removed punctuations
Added narrator to script data

@swarali-desai looking good, can you remove .DS_Store file from the repo and update the .gitignore if it isn't already there?


XMLHttpRequest cannot load. Origin is not allowed by Access-Control-Allow-Origin.

I have followed this guide
for every class loading I get this error:
XMLHttpRequest cannot load. Origin is not allowed by Access-Control-Allow-Origin.
I am trying to create a standalone parse server, keeping the website that accesses it separate, they have separate domains, both are https.
I have tried modifying the nginx "/etc/nginx/sites-enabled/default" file.  under location I have tried
   location /parse/ {                 proxy_set_header 'Access-Control-Allow-Origin' '*';                 proxy_set_header X-Real-IP $remote_addr;                 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;                 proxy_set_header X-NginX-Proxy true;                 proxy_pass http://localhost:1337/;                 proxy_ssl_session_reuse off;                 proxy_set_header Host $http_host;                 proxy_redirect off;         }
Have also tried
   location /parse/ {                 add_header 'Access-Control-Allow-Origin' '*';                 proxy_set_header X-Real-IP $remote_addr;                 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;                 proxy_set_header X-NginX-Proxy true;                 proxy_pass http://localhost:1337/;                 proxy_ssl_session_reuse off;                 proxy_set_header Host $http_host;                 proxy_redirect off;         }
I have also tried adding this entire script
It seems to be an issue with the express server in parse-server that nginx is proxying to.  I have been unable to figure out how to modify this.  Help is appreciated.

Thanks for the response, using this post: cors_heroku_parse-server I was able to fix the issue by forking the server and adding cors


Make Eq with negative float zero compat with other engines

Describe the bug
DF returns false below and is not compliant with major engines:
DataFusion CLI v39.0.0
> select 0.0 == -0.0;
+--------------------------+
| Float64(0) = Float64(-0) |
+--------------------------+
| false                    |
+--------------------------+

Similar issue #11051
To Reproduce
No response
Expected behavior
No response
Additional context
No response

I think this can be a good issue?

Isn't this done in Arrow? Because Binary Eq calls arrow::compute::kernels::cmp::eq

So I think we should do exactly what the docs say and normalize zeros?


Tidy up Docker compose volumes

🚀 Feature Request
Is your feature request related to a problem? Please describe.

The docker compose files (https://github.com/astrophpeter/blast/tree/main/docker) have lots of repeating code where the volumes are defined.

Describe the solution you'd like

Define the volumes once in the docker compose files, or across all docker compose files.

In #191, we replaced the bind-mounted Docker volumes with three named volumes: blast-db, blast-data, django-static. This approach simplifies data management and minimizes the gap between the local dev environment and the production deployment in Kubernetes. The disadvantage is that working manually with astro data files is more cumbersome; instead of manipulating files directly on the host machine, you must interact via containers. For example, to browse and manually modify astro data files, you could use the following method:
# Run temporary container to access astro data
$ docker run --rm --name=blast-data --hostname=blast-data -it \
    -v blast_blast-data:/mnt/data \
    -v /tmp/blast-data:/data-stage \
    ubuntu:jammy bash

root@blast-data:/# ls /mnt/data/
cutout_cdn  dustmaps  fsps  ghost_output ...

# Copy data to the directory shared with the host
root@blast-data:/# cp -r /mnt/data/dustmaps /data-stage/
root@blast-data:/# exit
exit

# View copied data on the host
$ ls /tmp/blast-data/
dustmaps

@djones I recommend closing this issue.


🚀 [REQUEST] - SEO work

Describe
setting SEO works to search Open-Set-Go
Reasons
We get our page by searching the whole url, "www.open-set-go.com" only.
How to Implement Features
No response
Additional Explanation
This Indian bro explains about SEO for react app insanely well.
Connection

[X] Have no effect on other functions
[ ] Other functions need to be changed

The situation will be way better by just changing title from "React App" to "Open-Set-Go". #65


Disable cyclewidth, cycleheight wrap

I do love moving between fixed proportions of the screen over the tedium of resizeactive. As reasoned in #9,
plugin:scroller:cyclewidth_wrap = no
plugin:scrolleri:cycleheight_wrap = no
—would be appreciated greatly

This is something that I can add, no problem. However, the name cycle already implies sizing is cyclical :-)

Love this @Acumane and agree @dawsers. Perhaps just "next" and "prev" or "increase" and "decrease" if ordered?

This is implemented in f09abfe73bee1143533a34983227bf8967d6d160
The new option is cyclesize_wrap and affects both columns and windows.

Two issues:

There are cases where the focused window is centered as if center_row_if_space_available was enabled. I can be more specific if you're unable to repro.
The cycleheight bounds are off by one ([0 1 2] is actually 0 1 ][ 2), so the smallest size is actually the largest.

I haven't been able to reproduce this. If you can, give me some steps to reproduce it, please.
I think you are probably using the default column_widths when enabling cyclesize_wrap. I may need to write a clearer explanation of how this works in the README-cyclesize_wrap.

Basically, there is no ordering for sizes. you set them in whichever order you want in column_widths and window_heights, and then hyprscroller cycles through them, The default one is onehalf twothirds onethird, which would create a similar pattern to what you are seeing. Change the order to onethird onehalf twothirds if you want cycling to be by size. The README hints at that, but maybe it is not clear enough.

Here's what's happening: if I have a column_widths list of onethird onehalf twothirds one, and I dispatch scroller:setwidth 3, our position in the list is updated. But if we resize by mouse, use resizeactive or fitsize, it is not. Since these methods don't transform windows to a preset length/width, we should find which size we're closest to in the list and set that as our index.
imo, this will make scroller:cyclewidth's behavior less jarring

Implemented in f477e656dd37c3fba77ca1d88e27575f26a9c2fa
Option is cyclesize_closest, true by default.

I love you


Fix binary protocols

Currently only text based protocols can be transmitted.
It is hard to measure whether any progress is being made on binary protocols when it seems MessagePack has its own issues running on Blazor. It would be helpful if anyone knew any other binary protocols.

I noticed there's been some work happening on 'BlazorPack'

I'm currently working on a custom hubprotocol based on Hyperion
https://github.com/akkadotnet/Hyperion
There do seem to be more problems to binary protocols other than the underlying serialisation, when I have the hyperionhubprotocol implemented and working outside of blazor we can perhaps start tackling with the general problems involving binary messages over websockets for blazorsignalr

I think it has to do with the base64 encoding en decoding of message payloads https://developer.mozilla.org/en-US/docs/Web/API/WindowBase64/Base64_encoding_and_decoding

I've published a nuget package with the hyperion protocol, it's based on a fork of Hyperion available on my github.
https://nuget.nickyheuperman.nl/packages/CeFintech.AspNetCore.SignalR.Protocols.Hyperion
I have had no luck yet fixing binary protocols for BlazorSignalR


Default Behaviour of Enact InputField is identifying as a bug by LG Webos QA Team.

Category

[ ] Other

Description
My application can't pass the quality check of the LG Webos QA Team because of the default behavior of Enact InputField. When the input is focused and the cursor is at the beginning of the value text and you press the left arrow on the keyboard spotlight leaves the input and when the cursor is at the end of the value text and you press the right arrow on the keyboard spotlight leaves this time as well. It's the built-in, default behavior of Enact InputField but the QA Team identifies this behavior as a bug and rejects my application. I added two videos below which the QA Team provided.
Environment
Doesn't make a difference
Enact version: 4.7.8
Videos
https://youtu.be/UskSpnxDGSw
https://youtu.be/NnGF15uSXg0

Dear @javadsalman,
I'm so sorry that your application got rejected by the default behavior of Enact InputField. I'm not sure why QA Team did that but as long as I know, the current behavior is expected behavior. You could see the same behavior from Settings > Support > TV Information > Device Name. Why don't you record the built-in app (Settings) behavior and report that this is the expected behavior?
Thank you.

Thanks for your consideration @MikyungKim. I informed them at the first attempt but they identified this feature as a bug again. That's why I provided two videos. I already bypassed this feature from the code side but it'd be better if you'd inform the QA team if you have a connection with them. Because I think this feature is useful and mustn't be removed

@javadsalman, I'm sorry that I have no contact information at this point. Would you be able to provide me an e-mail address or anything?

@MikyungKim, I can't access our sent feedback right now but I share an email from the QA team that sends results to us below.
<EMAIL_ADDRESS>

@MikyungKim They expect the spotlight not to leave input focus by right or left direction keys even if the cursor is at the borderline.

@javadsalman, Sorry for the delayed reply since I was out of office. Let me contact the person you mentioned and get back to you as soon as I get the answer.

Hello @javadsalman, I contacted the QA team and he will see if he can close the issue. I think it could close soon.
But the issue related the InputField is P3 issue which is not a blocker for acceptance of your app. He said you need to fix P2 bug. I'm closing this issue since the current behavior is the expecting behavior. Thank you!


fix(problem-report): proper string interpolation

Signed-off-by: blu3beri<EMAIL_ADDRESS>

Codecov Report

Merging #1120 (bcd2e46) into main (c68145a) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main    #1120   +/-   ##
=======================================
  Coverage   88.25%   88.25%
=======================================
  Files         706      706
  Lines       16450    16450
  Branches     2666     2666
=======================================
  Hits        14518    14518
  Misses       1925     1925
  Partials        7        7

Impacted Files
Coverage Δ

packages/core/src/agent/MessageReceiver.ts
81.81% <0.00%> (ø)

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


chore(package): pin and update dev dependencies

Description
pin and update dev dependencies
npx yarn-deduplicate. Reduces node_modules from 361MB to 237MB.
Motivation and Context

How has this been tested?

CI

Types of changes

[ ] 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)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Coverage remained the same at 98.86% when pulling eee5f8927f38735d0a18569764842acbd1e5bc3a on devDeps into a21c0dcbc9beeaf131dfe7efb32da156ec7e3a2b on master.


Report issues

My latest version (v1.1.0) in theory should work well. But I can't test for while if update.art is working as expected.
In case of some bug, or error, please, report me an issue! :wink:

Tested, and working well! 🚀


LGTM.com - false positive for py/redundant-comparison

The following post contains a link to the false positive.
https://discuss.lgtm.com/t/wrong-warning-test-is-always-true-because-of-this-condition/2422

I misread the alert. This is not a false positive after all.


Crash application when transcoding m4v file.

Hi @ypresto ,
Thanks you because created a library very useful .
I've tested your library on some devices :  Galaxy S3 (4.3), Nexus 5 (4.4.2) ... but when i try transcode a video has format .m4v or 3gp on Galaxy S3 (4.3) , an error appearing and crash this test application.
It's logcat :
03-17 09:43:22.380: D/dalvikvm(13507): GC_FOR_ALLOC freed 1144K, 35% free 14266K/21724K, paused 63ms, total 63ms
03-17 09:43:24.470: V/MediaExtractor(13507): Autodetected media content as 'video/mp4' with confidence 0.40
03-17 09:43:24.485: D/MediaTranscoderEngine(13507): Duration (us): 60127000
03-17 09:43:24.495: I/OMXClient(13507): Using client-side OMX mux.
03-17 09:43:24.520: I/ACodec(13507): setupVideoEncoder succeeded
03-17 09:43:24.555: I/OMXClient(13507): Using client-side OMX mux.
03-17 09:43:24.925: E/ACodec(13507): ## 3d, eNativeColorFormat 0x15
03-17 09:43:24.925: E/ACodec(13507): ## 3d, eNativeColorFormat 0x105
03-17 09:43:25.070: V/VideoTrackTranscoder(13507): Added track #0 with video/avc to muxer
03-17 09:43:25.100: D/dalvikvm(13507): GC_FOR_ALLOC freed 289K, 35% free 14255K/21724K, paused 29ms, total 29ms
03-17 09:43:25.100: I/MPEG4Writer(13507): setStartTimestampUs: 200200
03-17 09:43:25.100: I/MPEG4Writer(13507): Earliest track starting time: 200200
03-17 09:43:25.105: I/MPEG4Writer(13507): setStartTimestampUs: 0
03-17 09:43:25.105: I/MPEG4Writer(13507): Earliest track starting time: 0
03-17 09:43:25.160: A/MPEG4Writer(13507): frameworks/av/media/libstagefright/MPEG4Writer.cpp:2517 CHECK_GE( timestampUs,0ll) failed: -200200 vs. 0
03-17 09:43:25.160: A/libc(13507): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 13995 (VideoTrackEncod)

But when I try transcode this video on Nexus 5, it transcode completed.
Thanks you :)

Thanks for reporting issue!

Earliest track starting time: 200200

It seems problem around detecting presentation time (offset).
Can you share failing video files for investigation?
Metadata (profile, level, resolution, etc...) is also welcomed.
Note that Android only (officially) supports "baseline profile" mp4 files.

@CuongSmile
FYI: I recently fixed bug that library hangs in native layer when incompatible video file is passed.
It just throws Exception in such situation before start transcoding. :)

Hi @ozyozyo
Thanks form caring my issue.
I'm really sorry you because I don't remember rely you about this issue, util I received a email nofification from github send to my email.
About this issue, I remembered when I debug I found the problem occur when decoce video, it related to presentation time, I must re-calculated the presentation time when transcode video.

Please reopen if similar issue happens. Thanks..!


[occm] add load-balancer-address annotation doc

What this PR does / why we need it:
feature were added https://github.com/kubernetes/cloud-provider-openstack/pull/2097 but we are missing docs
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

/lgtm
/approve


Fix playground snippets

Fixes #31624

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

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

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

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @tvalentyn

Thank you! Do you have any ideas about how we can find if any other examples are still broken in an automated way? or better in a test suite? Feel free to chime in on the issue.

LGTM, Thank you! Do you have any ideas about how we can find if any other examples are still broken in an automated way? or better in a test suite? Feel free to chime in on the issue.

I'll think how to do it


Add support for the Postgres interval type

This PR also includes a commit to remove unused imports that the compiler warned about.
This requires the changes in https://github.com/SeaQL/sea-query/pull/169 in order to compile.
I was a bit lost in how to update the test code for this change.

Thank you for the contribution! What's your use case. I assume you also want to generate an ORM entity at the end? Or it can fulfil all your needs now?


[fix] Lazy load Svelte components to reenable no-ssr use cases

Fixes #5909
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[x] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

I feared this would happen - this CSS tests are failing, I guess because they are no longer eagerly imported so it's a FOUC in some cases.


Web App is showing an error instead of document list

Describe the bug
When opening the web app and for example the disovery page, the error "Something went wrong, please refresh the page to try again." is shown instead of the document list (see screenshot). The demo worked without problems and showing the document list three days before. There are no errors shown in the network console of the browser.
To Reproduce

Open DUS Demo Start page in Browser
click on "Discovery"
after a few secons of loading error message is shown

Expected behavior

After Opening the DUS Demo Discovery Page, the document list should be shown

Please complete the following information about the solution:

[ ] Version: v1.0.13
[ ] Region: eu-west-1
[ ] Was the solution modified from the version published on this repository? - no
[ ] Have you checked your service quotas for the sevices this solution uses? yes
[ ] Were there any errors in the CloudWatch Logs? no errors

Screenshots

Hi @SIR1BE
Thanks for reporting this behavior.
Could you please confirm if you see any error in "apiprocessor" lambda logs ?
Also can you please also verify if GET  /documents API is working fine. You can test it by following below steps -

Go to API Gateway
Go to Resources
Click on /documents GET method
Click on Test from Client sidebar
On Test page, click on Test again
The API should return document response with 200 response code

Hi @SIR1BE
We cannot reproduce the issue and as we have not heard back, we are closing this issue.
Please reopen it if you have more info.
Thanks
Fabien


Cannot set a gradient on a style fill color

For example, the circle style has code which assumes the fill color is not colorLike:
ol.color.asString(this.fill_.getColor());

Being able to do this would facilitate heatmap like functionality using styling alone and would also expand the already amazing styling options by providing all kinds of textures to represent point features.

Did you mean to close this @ca0v?

Yes, I was using 3.12, works great in 3.17.


New 3MF serializer

I had this sitting around since early V2, so decided to bring the code up to date, and publish. I've been using PrusaSlicer for testing the 3MF files, which seem to work really well.
Also, the compression of the 3MF package is completed by a small package called fflate, which @hrgdavor introduced. It worked first time. :)
All Submissions:

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[X] Does your submission pass tests?


Caching on branches and pull requests

Hello, I read an article on how caching  worked for Drone 0.4 http://readme.drone.io/0.4/usage/caching/
Does this plugin work the same? I am particularly interested in the below:

Branches and Matrix
Drone keeps a separate cache for each Branch and Matrix combination. Let’s say, for example, you are using matrix builds to test node 0.11.x and node 0.12.x and you are caching node_modules. Drone will separately cache node_modules for each version of node.
Pull Requests
Pull requests have read-only access to the cache. This means pull requests are not permitted to re-build the cache. This is done for security and stability purposes, to prevent a pull request from corrupting your cache.

Technically speaking, this plugin is very similar to the caching in Drone 0.4. The plugin caches folder on a mounted host directory, meaning it works well for single machine situations.
The plugin has a separate cache for Matrix jobs, but not for branches. This has been requested in #12.
I like the idea of making Pull Request access read only. I will add it to the list.

https://github.com/Drillster/drone-volume-cache/pull/16 - not sure if this is what you planned but I don't mind pull requests having write access to cache.
One thing to keep in mind though is that some sort of cache cleanup needs to happen periodically. Maybe this cleanup should be added to the plugin itself. For example limiting cache size and cleaning oldest caches when a threshold is reached.

My branch can be tested with rushpl/drone-volume-cache, same config, should work automatically

The cache cleanup function is actually already present. You can set a cache TTL like so: https://github.com/Drillster/drone-volume-cache/blob/master/DOCS.md#using-cache-lifetime


shell-conduit-4.6.1 build failure with conduit-1.3

Seen on the Stackage build server; I was able to reproduce locally like so:
stack unpack shell-conduit-4.6.1 && cd shell-conduit-4.6.1
edit stack.yaml # add the following stack.yaml
stack build

# stack.yaml
resolver: nightly-2018-03-10
extra-deps:
- conduit-1.3.0
- resourcet-1.2.0
- conduit-extra-1.3.0

The build failures were as follows:
[3 of 7] Compiling Data.Conduit.Shell.Types ( src/Data/Conduit/Shell/Types.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/Data/Conduit/Shell/Types.o )

/Users/dan/scratch/shell-conduit-4.6.1/src/Data/Conduit/Shell/Types.hs:33:1: error:
    • Could not deduce (MonadBase IO (ResourceT m))
        arising from a use of ‘liftBase’
      from the context: MonadResourceBase m
        bound by the instance declaration
        at src/Data/Conduit/Shell/Types.hs:33:1-66
    • In the third argument of ‘ghc-prim-<IP_ADDRESS>:GHC.Prim.coerce’, namely
        ‘liftBase’
      In the expression:
        ghc-prim-<IP_ADDRESS>:GHC.Prim.coerce
          @(forall (α :: TYPE ghc-prim-<IP_ADDRESS>:GHC.Types.LiftedRep).
            IO α -> ResourceT m α)
          @(forall (α :: TYPE ghc-prim-<IP_ADDRESS>:GHC.Types.LiftedRep).
            IO α -> ShellT m α)
          liftBase
      In an equation for ‘liftBase’:
          liftBase
            = ghc-prim-<IP_ADDRESS>:GHC.Prim.coerce
                @(forall (α :: TYPE ghc-prim-<IP_ADDRESS>:GHC.Types.LiftedRep).
                  IO α -> ResourceT m α)
                @(forall (α :: TYPE ghc-prim-<IP_ADDRESS>:GHC.Types.LiftedRep).
                  IO α -> ShellT m α)
                liftBase
      When typechecking the code for ‘liftBase’
        in a derived instance for ‘MonadBase IO (ShellT m)’:
        To see the code I am typechecking, use -ddump-deriv
   |
33 | deriving instance (MonadResourceBase m) => MonadBase IO (ShellT m)
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/Users/dan/scratch/shell-conduit-4.6.1/src/Data/Conduit/Shell/Types.hs:41:10: error:
    • Could not deduce (MonadUnliftIO m)
        arising from the superclasses of an instance declaration
      from the context: (MonadThrow m, MonadIO m, MonadBaseControl IO m)
        bound by the instance declaration
        at src/Data/Conduit/Shell/Types.hs:41:10-89
      Possible fix:
        add (MonadUnliftIO m) to the context of the instance declaration
    • In the instance declaration for ‘MonadBaseControl IO (ShellT m)’
   |
41 | instance (MonadThrow m,MonadIO m,MonadBaseControl IO m) => MonadBaseControl IO (ShellT m) where
   |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/Users/dan/scratch/shell-conduit-4.6.1/src/Data/Conduit/Shell/Types.hs:49:13: error:
    • Could not deduce (MonadBaseControl IO (ResourceT m))
        arising from a use of ‘liftBaseWith’
      from the context: (MonadThrow m, MonadIO m, MonadBaseControl IO m)
        bound by the instance declaration
        at src/Data/Conduit/Shell/Types.hs:41:10-89
    • In the first argument of ‘ShellT’, namely
        ‘(liftBaseWith (\ run -> f (liftM StMShell . run . runShellT)))’
      In the expression:
        ShellT
          (liftBaseWith (\ run -> f (liftM StMShell . run . runShellT)))
      In an equation for ‘liftBaseWith’:
          liftBaseWith f
            = ShellT
                (liftBaseWith (\ run -> f (liftM StMShell . run . runShellT)))
   |
49 |     ShellT (liftBaseWith
   |             ^^^^^^^^^^^^...

/Users/dan/scratch/shell-conduit-4.6.1/src/Data/Conduit/Shell/Types.hs:54:23: error:
    • Could not deduce (MonadBaseControl b0 (ResourceT m))
        arising from a use of ‘restoreM’
      from the context: (MonadThrow m, MonadIO m, MonadBaseControl IO m)
        bound by the instance declaration
        at src/Data/Conduit/Shell/Types.hs:41:10-89
      The type variable ‘b0’ is ambiguous
      Relevant bindings include
        restoreM :: StM (ShellT m) a -> ShellT m a
          (bound at src/Data/Conduit/Shell/Types.hs:54:3)
    • In the first argument of ‘(.)’, namely ‘restoreM’
      In the second argument of ‘(.)’, namely ‘restoreM . unStMGeoServer’
      In the expression: ShellT . restoreM . unStMGeoServer
   |
54 |   restoreM = ShellT . restoreM . unStMGeoServer
   |                       ^^^^^^^^

/Users/dan/scratch/shell-conduit-4.6.1/src/Data/Conduit/Shell/Types.hs:59:11: error:
    Variable not in scope:
      monadThrow :: ShellException -> ConduitM i o (ShellT m) a
   |
59 |   empty = monadThrow ShellEmpty
   |           ^^^^^^^^^^

shell-conduit-1.7.0 released which contains the fix.

Thank you @psibi


presentproof command: unable to provide a friendly name when accepting request-presentation

https://github.com/hyperledger/aries-framework-go/blob/8509b7ff523badf2755b9d930912a90fccb2f806/pkg/controller/command/presentproof/models.go#L91-L96

Note: the presentproof SavePresentation() middleware assumes the id is always present which does not seem right: https://www.w3.org/TR/vc-data-model/#presentations-0

@llorllale We do not need a friendly name when accepting request-presentation. A friendly name is needed on the Verifier side. When Verifier wants to save it. What is the purpose of having a friendly name on the Issuer side while accepting a request?
middleware assumes the id is always present which does not seem right - current logic works in the following way: if the name was not provided we rely on ID. If ID is empty then the protocol will fail due to the following errorpresentation name is mandatory.
To prevent protocol failure we can check the ID, if it is empty we will generate random name e.g uuid.New().String(). Does it make sense?

@soluchok

We do not need a friendly name when accepting request-presentation. A friendly name is needed on the Verifier side. When Verifier wants to save it. What is the purpose of having a friendly name on the Issuer side while accepting a request?

Right. I got confused. It seems I need to action.Continue(presentproofsvc.WithFriendlyNames(<myName>)).

To prevent protocol failure we can check the ID, if it is empty we will generate random name e.g uuid.New().String(). Does it make sense?

Sounds right.


fabs -> fabsl

Fixes two calls that were using fabs on a long double argument rather than fabsl, which looks like it is doing an unintentional truncation to double precision.

Looks like there are similar usages in rotg.c, symv.c, zrotg.c, zsbmv.c, zhemv.c, rotmg.c, ...

I was surprised to see that "long double" variables are being used anywhere in OpenBLAS.  Although gcc on x86_64 uses 80 bit Intel extended precision for these, the performance is slow in comparison to AVX2 or AVX512 SIMD.  Other x86_64 compilers might just use IEEE double precision for long double. On many other architectures there's no hardware support for an extended precision long double (and the compiler often turns long double into double precision.)  It's also possible that some compiler implement a quadruple precision long double in software, but that would be far slower than the x86_64 80 bit extended precision.
Thus there's no real way count on this helping with precision, and furthermore, if you do get some kind of extended precision using long double it might have poor performance.  A final concern is that users of BLAS/LAPACK routines don't expect extended precision and might be surprised by results which are too accurate.
Which of the BLAS/LAPACK functions in OpenBLAS make use of long double?

At least some of these - most likely all - are unchanged from GotoBLAS2 (which predates AVX2).

Also if you are concerned about excess precision on x86, you will probably want to set the FPU control word to use internal rounding to double precision (0x27 I think it was) if your operating system does not already default to that mode (*BSD does I believe). I have not tried what effect enforcing fpmath=sse would have, possibly this would be sufficient to demote the "long double" to "double" already.

Perhaps the discussion could be moved to an issue ticket, if nobody actually questions the validity of the PR ? (Unfortunately I am not aware of a github function that would do this while keeping individual messages and attributions intact)

I opened a separate issue for this with a reference to the pull request.

If people agree that this PR is correct, it should probably be expanded to include the other calls to fabs that I mentioned before it is merged.

The only instances of "long double" that I can find appear to be in interface/rotg.c and interface/zrotg.c, not sure why you think symv.c and others are affected ?

As I understand it, the previous code took long double values, rounded them to double, took the absolute value and then converted back to long double at the end, losing any extended precision.  The new version should actually keep the extended precision.

@martin-frbg, I haven't looked at the other files in detail — I just listed the files for which I saw a similar compiler warning about fabsl.  I would have to recompile to see the warnings again in detail.

I did not see any other warnings with clang, nor any other uses of "long double".
@brianborchers the code is something like
void rotg(double *DA,...
long double da = *DA;
long double ada = fabsl(da);

@martin-frbg, if all the code using fabs(long double) is like that, i.e. operating on a value just converted from double, then fabs should be safe since (long double) ((double) ((long double) somedouble)) is the identity, and fabs may even be faster.


Thumbnail pictures show up in 'Image picker'

Is there a possibility that the folders with the thumbnails (.thumbnails) are not shown during image selection? Actually, these files are hidden, but strangely they are still displayed and of course completely unusable.
The code used was exactly the same as in the sample.
Many thanks for the help

Sorry for the late reply.
Working on that, will be fixed soon.

From version 1.2.0 you can hide hidden files using following methods.

Methods
Default value
Uses

setIgnorePaths(String... ignorePaths)
null
Regex patterns of paths to ignore

setIgnoreNoMedia(boolean)
true
Whether to ignore .nomedia file

setIgnoreHiddenFile(boolean)
true
Whether to ignore hidden file

See if this works for you.


Cpu: make getNumCores constant

getNumConst doesn't change Cpu state but is not marked const.

Thank you for the good patch.


Units in dendrogram plots

The dendrogram functionality of NeuroM should generate plots with units on the axes (or scale bars)

Added the labels of the units which were in micrometers. You can also put custom labels or a title for example by passing as kwargs a dict with the following:
kwargs['title'] = 'title'
kwargs['xlabel'] = 'favorite xlabel'
kwargs['ylabel'] = 'favorite ylabel'


Design - Validation Service UI

Problem statement
As a sender or an O&O team member, I want to be able to test my data file in CSV, HL7 or RADx-MARS format and get user friendly responses to understand, identify and fix issues with my data.
What you need to know

Existing Figma mockup for CSV upload
Mural board for Validation Service Deep Dive with Options
Provide user-interface that allows file drag&drop or upload feature and display of response to the file
There is an expectation of reusing CSV Uploader components and features and not a full new page
Supporting HL7, CSV, RADx MARS formats
-Example: https://validator.aimsplatform.org/

Acceptance criteria

[ ] IA for the Validation Service Page
[ ] Design/wireframe for the Validation Service Page
[ ] Reviewed with the Product and Experience team

To do

[ ] Review example HL7 and RADx MARS files, how do they differ from our existing CSV format?
[ ] ...

Work in progress for this is located at: https://www.figma.com/file/b2Zd1xzmp4cdwFO8O7edcI/CSV-Uploader-%26-Validation?node-id=2288%3A1127

Updates - UI can be used as in the Figma file for MVP; but as we learn more about different “types” of messaging and errors that could get thrown from HL7, we might want to circle back around and see if adjustments need to be made to how they are displayed or communicated back.


nano: 2.5.3 -> 2.6.0

Motivation for this change
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Good morning @vrthra.
Please see the situation with nano 2.6.0 in #16423.
Regards.

@mimadrid Ah, sorry, did not see that. I will close my PR.


Rye doesn't respect the chosen toolchain version during installation

Steps to Reproduce
When running the installation script, choose a different Python version for the default toolchain, e.g<EMAIL_ADDRESS>Expected Result
For rye to install<EMAIL_ADDRESS>Actual Result
Rye still installs the latest Python, only to realize later than it's missing it:
ams002@host:~$ curl -sSf https://rye-up.com/get | bash
This script will automatically download and install rye (latest) for you.
######################################################################## 100.0%
Welcome to Rye!

This installer will install rye to /home/ams002/.rye
This path can be changed by exporting the RYE_HOME environment variable.

Details:
  Rye Version: 0.32.0
  Platform: linux (x86_64)

✔ Continue? · yes
✔ Select the preferred package installer · uv (fast, recommended)
✔ What should running `python` or `python3` do when you are not inside a Rye managed project? · Run a Python installed and managed by Rye
✔ Which version of Python should be used as default toolchain? ·<EMAIL_ADDRESS>Installed binary to /home/ams002/.rye/shims/rye
Bootstrapping rye internals
Downloading<EMAIL_ADDRESS>Checking checksum
Unpacking
Downloaded<EMAIL_ADDRESS>Updated self-python installation at /home/ams002/.rye/self

The rye directory /home/ams002/.rye/shims was not detected on PATH.
It is highly recommended that you add it.
✔ Should the installer add Rye to PATH via .profile? · yes
Added to PATH.
note: for this to take effect you will need to restart your shell or run this manually:

    source "$HOME/.rye/env"

For more information read https://rye-up.com/guide/installation/

All done!
ams002@host:~$ source "$HOME/.rye/env"
ams002@host:~$ rye^C
ams002@host:~$ which python
/home/ams002/.rye/shims/python
ams002@host:~$ python
error: Requested Python version<EMAIL_ADDRESS>is not installed. Install with `rye fetch`
ams002@host:~$ rye fetch
Downloading<EMAIL_ADDRESS>Checking checksum
Unpacking
Downloaded<EMAIL_ADDRESS>
Version Info
rye 0.32.0
commit: 0.32.0 (e1b4f2a29 2024-03-29)
platform: linux (x86_64)
self-python<EMAIL_ADDRESS>symlink support: true
uv enabled: true

Stacktrace
No response

Example of this happening in action