'Preview' option does but update when changing files.

Description
When changing files via the sidebar, the 'Preview' button does not update based on the currently viewed file.
How to replicate the issue + URL

Visit https://github.com/refined-github/refined-github/blob/main/source/options.html

Verify the 'Preview' button is there, and if not, reload

Use the sidebar to navigate to any other file
Notice that the 'Preview' button remains linked to the options.html file.

Extension version
24.4.1
Browser(s) used
Google Chrome 123.0.6312.86 (Official Build) (64-bit)

Duplicate of https://github.com/refined-github/refined-github/issues/6554

Yes unfortunately it's:

https://github.com/refined-github/refined-github/issues/6554


Add preview for pull requests

This PR updates the docs.yml job to upload doc previews to S3.

cc: @PaulZhang12


display current version

resolves #143

kubectl apply -f https://raw.githubusercontent.com/cyclops-ui/cyclops/v0.0.2-rc.2/install/cyclops-install.yaml

Did you have something like this in mind @pmig ?
Petar pasted the kubectl command for this version of Cyclops in the convo above for easy testing.

@petar-cvit indeed looks super nice!


Extension issue

Issue Type: Bug
Extension Name: intellicode-api-usage-examples
Extension Version: 0.1.1
OS Version: Windows_NT x64 10.0.19042
VS Code version: 1.68.0

:warning: We have written the needed data into your clipboard. Please paste! :warning:```json
{
"messages": [],
"activationTimes": {
"codeLoadingTime": 1851,
"activateCallTime": 10,
"activateResolvedTime": 1575,
"activationReason": {
"startup": false,
"extensionId": {
"value": "VisualStudioExptTeam.intellicode-api-usage-examples",
"_lower": "visualstudioexptteam.intellicode-api-usage-examples"
},
"activationEvent": "onLanguage:python"
}
},
"runtimeErrors": [],
"runningLocation": {
"affinity": 0,
"kind": 1
}
}

hi @sprinteroz can I get more details about the issue you are having or trying to report with this issue?
Thanks!

We are unable to act further without more description on the problem you encountered - if you can provide some more details on the issue you saw, for instance the contents of your Output window in VSCode's IntelliCode section, and some details of what you were doing when you saw the problem, please feel free to reactivate.


Update to the latest solidus_dev_support defaults

A long overdue update to the extension in order to get rid of the boilerplate in favor of more usage solidus_dev_support helpers.
All changes not strictly coming from running solidus extension . are listed in separate commits.
Among them are:

adding a linter job to the CI
standardizing by increased usage of the solidus_auth_devise namespace (vs. spree/auth)

@jarednorman it's intended to be completely transparent, with all the older files still supported, but to also open up to a future deprecation of spree/auth in favor of the namespace matching the gem name. After all adding it to the Gemfile already triggered a require 'solidus_auth_devise'.


[feature] Touch controller: more touch events

The touch controller in the Pinetime is a I2C device based on the CST816S touch controller.
There is very few documentation but the Wiki page gives us some hints about how to get it to work.
WIKI
The prooject already integrate a driver and get the tap event on and ISR.
We will need the other event if we want to implement some kind of navigation system.
supported touch event :

[ ] 0x00: no gesture
[ ] 0x01: Slide down
[ ] 0x02: Slide up
[ ] 0x03: Slide left
[ ] 0x04: Slide right
[ ] 0x05: Single click
[ ] 0x0B: Double click
[ ] 0x0C: Long press

It would be really nice to have a proper Zephyr driver that could be upstreamed. For this to be possible we can't copy from existing  "source available" non-Apache 2.0 licensed drivers however. :/


#1220 cleanup downloads folder before every $.download() call

NB! We can do it only for folders created by Selenide (aka "unique"). In case of folders provided by user, we cannot cleanup them.

Probably will be overseeded by https://github.com/selenide/selenide/pull/1252


Configure base year floor areas with Mastermap and Adresspoint data for virtual building stock

As with #45 - see nismod/arc-floor-area


fix(rest): Allow disabling maxRedirects. Closes #1181

fix #1181

Hey @yunwu-cn! Many thanks for your contribution.
Serenity/JS uses conventional commits to automate the release process. Would you mind renaming the commit message so that the pipeline can pick up your change and include it in the release notes?
You can generate a commit message that matches the conventional commits template using npm run commit as per the contributing guide, or simply rename it to something along the lines of:
git commit --amend -m "fix(rest): Allow disabling maxRedirects. Closes #1181"
git push --force

Updated, thank you.

Hey @yunwu-cn! Many thanks for your contribution.
Serenity/JS uses conventional commits to automate the release process. Would you mind renaming the commit message so that the pipeline can pick up your change and include it in the release notes?
You can generate a commit message that matches the conventional commits template using npm run commit as per the contributing guide, or simply rename it to something along the lines of:
git commit --amend -m "fix(rest): Allow disabling maxRedirects. Closes #1181"
git push --force

It might be also good to add a test to prevent regressions in the future. Since the change you propose is for HTTPRequest, which is an abstract class, we could at the very least add a new test to GetRequest.spec.ts and make sure that when maxRedirects is set to 0, that's the value that Axios receives.
Ps. I've raised #1183 to start looking into improving the contributors' experience. Please feel free to comment with any feedback and suggestions!

I've merged it, thanks! Looks like GitHub doesn't automatically close PRs that are force-pushed so I'll close it manually.


Wrong pytorch-cuda version installation with pip

Describe the bug
It seems that this line:
https://github.com/grimoire/mmdetection-to-tensorrt/blob/master/docker/Dockerfile#L21
It is not working as intended since it is installing pytorch with cuda=10.2.
I am working with a RTX3060 and I am getting the following error:
NVIDIA GeForce RTX 3060 Laptop GPU with CUDA capability sm_86 is not compatible with the current PyTorch installation.
The current PyTorch install supports CUDA capabilities sm_37 sm_50 sm_60 sm_70 sm_75.
If you want to use the NVIDIA GeForce RTX 3060 Laptop GPU GPU with PyTorch, please check the instructions at https://pytorch.org/get-started/locally/

This is related with a wrong installation of pytorch (more info in this thread)
Basically we are using a base tensorrt image that contains cuda 11.1,1:
https://docs.nvidia.com/deeplearning/tensorrt/container-release-notes/rel_20-12.html#rel_20-12
But it seems pytorch installation is installing cuda 10.2 binaries. You can check this in the official documentation:
https://pytorch.org/get-started/locally/ where basically if you choose pip and cuda 10.2 they return the following command:
pip3 install torch torchvision torchaudio
We should modify torch installation to add cuda specific version.
I am willing to send a PR that modifies this!

Actually note that it does not seem to exist binaries for cuda 11.1 for pytorch<1.8
See full list here:
https://pytorch.org/get-started/previous-versions/

Thank you! PRs are welcome!
You can update the base image if there the cuda version and pytorch can not match.


Remove useless user and login

This PR removes the useless login and user from the script below. Both login and user are useless as the endpoint authentication is done using the shared certificate.
For a security perspective is best to avoid creating useless principals in a production server (particularly is the the same password is replicated many times).
Also the script is shorter and cleaner this way.
Tested on Microsoft SQL Server 2017 (RTM-CU8) (KB4338363) - 14.0.3029.16 (X64)   Jun 13 2018 13:35:56   Copyright (C) 2017 Microsoft Corporation  Developer Edition (64-bit) on Linux (Ubuntu 16.04.4 LTS)

@MikeRayMSFT - Would you review the proposed changes? Thanks

Thank you @MindFlavor for the submission! #sign-off


⚠ Bofrost.be has degraded performance

In f9fa753, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1501 ms

Resolved: Bofrost.be performance has improved in 9617761.


Check if empty server list is obtained and display a proper message

Contains
Fixes #3069
How to test
I am not sure if there is a way of testing this, I couldn't re-create the error myself. On changing just the masterServer in config.cfg, the downloader tries to download from defaultAddress which has been set to meta.terasology.org in NetworkConfig.java and successfully downloads it. However when I changed that as well, as proper message saying "Error Downloading Server List!" was displayed. However I understand that the error caused was due to the empty list returned by the server, so I have added a simple check for that.

Hooray Jenkins reported success with all tests good!

Finally had a chance to check this out and validated that the list still works - merged, thanks! :-)


Add support for Java array parameters

The Hotspot JVM has an undocumented feature called Critical Natives, details here. It makes Java primitive arrays a viable alternative to NIO buffers and is a good match for LWJGL (virtually all JNI methods qualify, by design).
Pros:

Normal object lifecycle vs malloc/free or sun.misc.Cleaner
array[i] = array[j] vs buffer.put(i, buffer.get(j))
Computation on array -> pass to JNI vs computation on POJO -> copy to buffer -> pass to JNI

Cons:

Bigger natives
Bigger JAR
Hotspot only

Questions:

How does AutoSize work with arrays?

I would love to have this as it would make the java and c look basically identical though it is undocumented and for internal use from what I see so it could change at any time especially with jigsaw coming in 9.
Another con you forgot is that its a JDK 7 feature.

Maybe it could be a secondary artifact, for those who know users will run on Hotspot JDK 7+ (e.g. they provide it) and want to get more speed. I could see that being very interesting for video games that bundle the JDK.

This looks like an awesome feature to have and would really clean up the LWJGL API.
Maybe LWJGL could have methods (or a utility class) that accept primitive arrays and where not supported (pretty rare situation IMO) it could automatically copy to a buffer and use the normal buffer version of that API. Would allow users to use standard java arrays everywhere without worrying too much about compatibility.

I think it would also be good to see if they actually do speed anything up so a benchmark with a few functions first or something.

I've actually been testing it for the last couple of days. Got incredibly excited at first, because it sounded like it would improve all JNI methods, even methods that don't use arrays. Results:

There is indeed a benefit when doing Java-side computations and passing the array to JNI without a copy. We tested JOML code for this. The alternatives, calc on FloatBuffer or calc on POJO+copy to FloatBuffer, were slower.
There is absolutely no benefit to primitive-only JNI methods. Critical Natives do indeed skip some setup overhead in the JNI wrapper, but it's no more than 1-2 CPU cycles (measured with JMH).
Critical Natives are only used in a few crypto methods in the JDK, so they have been tuned for exactly that use-case (passing Java arrays). I figured it could get better, so I hacked JDK 9 and produced a build that removes even more stuff from the JNI wrappers. That gave real benefits even for the primitive-only case (for a no-arg method: 9.1ns down to 5.6ns per call). That was just an experiment, I don't think it's worth pushing for something like it, since Project Panama is coming in JDK 10.

Another con you forgot is that its a JDK 7 feature.

Maybe it could be a secondary artifact, for those who know users will run on Hotspot JDK 7+

Honestly, I still hate it that LWJGL needs to be Java 6 compatible. If it were up to me, it would support Java 8 and up. Even Android supports Java 8 now. Maybe open this discussion again before the 3.0.0 release?

Maybe LWJGL could have methods (or a utility class) that accept primitive arrays and where not supported (pretty rare situation IMO), automatically copying it to a buffer and using the buffer version of that API. Would allow users to use standard java arrays everywhere without worrying too much about compatibility.

Technically possible, but would be too much code for very few (if any) users.

I am quite interested in this, too. Just to make sure that I would not invest time needlessly into JOML redesigning/extending it to make use of Java arrays, I would like to gather some benchmark results from users interested in using JOML with LWJGL 3.
I created a small JMH benchmark project here: https://github.com/JOML-CI/joml-bench
I would request for anyone interested to just download the prebuilt jar file and either post their results into this GitHub issue.
You don't have to mention your hardware stats, and also not the exact numbers if you don't want to. Just which test performed better (higher numbers 'ops/s') are better).

I don't think it's worth pushing for something like it, since Project Panama is coming in JDK 10

If you're worried about JNI wrappers and performance, have you looked into depending on JNA.  It looks like what Panama is going to be based around, and it would provide a compatible solution for older JVMs even after 10 comes out.

JNA is slower than using handwritten/generated JNI. JNA just allows bridging Java and native without writing native code ourselves. That's because the lowest denominator is just JNI. Everything wanting to bridge between Java and native has to use JNI. JNA simply has its own "hub" dispatcher function and we pay the price for having JNA to store the call arguments in its own data structure. Yes, it uses FFI, but that also adds to runtime.

Ah, so does Panama's goal more or less provide what JNA's interface does, but skips the JNI step?  If that's the case that'd be amazing.
Bundling a JRE with your app on desktop isn't uncommon, and is more than not recommended, especially if your app is distributed on Steam.  I wonder how these changes would effect people who are trying to release apps on PS4/Xbox.  I don't know what the distribution requirements are and if they have a specific requirement of what JVM to use or package.  I'm afraid something like this could prevent developers from pushing their apps to those platforms if this is a change that can't be optional.

but skips the JNI step? If that's the case that'd be amazing.

Yes and a lot more. The current prototype can even generate inline assembly using pure Java.

I'm afraid something like this could prevent developers from pushing their apps to those platforms if this is a change that can't be optional.

Using array parameters will work on any JVM. If a JVM doesn't support Critical Natives, the only difference will be a performance penalty when using such methods.

An initial implementation is available in the array-params branch.

Support for Hotspot Critical Natives is now available in LWJGL 3.0.0 build 77.
The current implementation does not include byte[] array overloads. They would have low usefulness and would result in a massive number of new overloads. If you have an interesting use-case for byte arrays, please post here. It would be possible to generate byte[] overloads for specific functions only.


APPLICS-77: Welsh translation - have your say guide

Describe your changes
https://pins-ds.atlassian.net/browse/APPLICS-77?atlOrigin=eyJpIjoiYzBiN2JiNWQ5ZTQxNGJkZGJmM2JmMjM5MmEwZDU3ZWQiLCJwIjoiaiJ9
Type of change 🧩

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

Checklist before requesting a review

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

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

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

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


Implement a Blacklist for Games

With Steam's new feature to mark games as private, it would be nice, if we can also hide specific games from Discord's RPC.
Blacklisted games can be set in the config.json file, and once a new RPC object is supposed to be created, it first checks if a game is in the blacklist, and ignores it if that's the case.
This is my first pull request, so I hope I haven't forgotten anything. But feel free to mention or edit any issues you have with it. :)

This looks great! I can't see any issues with it, but I'll play around with it a bit later today to make sure everything's good before i merge it.
Thanks for the PR!

works great - sorry for the delay :sweat_smile:

Thanks, and no worries!


Document what we will support/maintain

We should document what we will be supporting/maintaining so this is clearly defined.

I will create draft and Craig will review.

Closing - not needed.


Remove duplicate condition check

Hello,
While reviewing the code, just fix a small duplicated condition check.
Please review 🙏

Hi @djKooks, thanks for this! All looks fine to me :) I'll be going through these codes a bit later in the week looking for similar issues, so I appreciate you helping out in this regard!

@andrewtavis okay~I'll make some updates if I found something 🙏


Emit Span RED metrics for Sleuth

Emit Span RED metrics and JVM metrics when using Sleuth
Add new property wavefront.include-jvm-metrics to enable users not emitting JVM metrics (emitting by default)
Add new property wavefront.trace-derived-custom-tag-keys to support custom RED metrics keys

@sushantdewan123 @haosong can you please have a look to #35 and see if there is something in there that we haven't covered yet?


Problem running the demos themselves

Hello! I'm trying to run the demos for the bolt biped robot and the solo12 quadruped but I am running into some strange issues (this is all done on a freshly nuked and re-installed computer with Ubuntu 20.04).
here is my output for when I build with: colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release

Starting >>> googletest-distribution
Starting >>> mpi_cmake_modules
Starting >>> pybind11
Finished <<< mpi_cmake_modules [0.24s]
Starting >>> bullet_utils
Finished <<< pybind11 [0.66s]
Finished <<< googletest-distribution [0.72s]
Starting >>> yaml_utils
Starting >>> real_time_tools
Finished <<< yaml_utils [0.24s]
Finished <<< real_time_tools [0.43s]
Starting >>> reactive_planners
Finished <<< reactive_planners [0.38s]
--- stderr: bullet_utils
pybullet build time: Oct 11 2021 20:59:39
/home/roy/.local/lib/python3.8/site-packages/recommonmark/parser.py:75: UserWarning: Container node skipped: type=document
warn("Container node skipped: type={0}".format(mdnode.t))
/home/roy/odri_dev/workspace/build/bullet_utils/build/lib/bullet_utils/doc/readme.md: WARNING: document isn't included in any toctree

Finished <<< bullet_utils [2.92s]
Starting >>> robot_properties_bolt
Starting >>> robot_properties_solo
resources =  ['resources/impedance_ctrl.yaml', 'resources/dynamic_graph_manager/dgm_parameters_bolt.yaml', 'resources/odri_control_interface/bolt_driver.yaml', 'resources/pycache/init.cpython-38.pyc', 'resources/xacro/bolt_passive_ankle.urdf.xacro', 'resources/xacro/bolt.urdf.xacro', 'resources/xacro/plane_with_restitution.urdf.xacro', 'resources/xacro/bolt.xacro', 'resources/xacro/leg.xacro', 'resources/meshes/checker_blue.png', 'resources/meshes/plane.obj', 'resources/meshes/plane.mtl', 'resources/meshes/obj/bolt_upper_leg_right_side.obj', 'resources/meshes/obj/bolt_hip_fe_left_side.obj', 'resources/meshes/obj/bolt_upper_leg_left_side.obj', 'resources/meshes/obj/bolt_lower_leg_right_side.obj', 'resources/meshes/obj/bolt_hip_fe_right_side.obj', 'resources/meshes/obj/bolt_body.obj', 'resources/meshes/obj/bolt_foot.obj', 'resources/meshes/obj/bolt_lower_leg_left_side.obj', 'resources/meshes/stl/lower_leg_200mm_right_side.stl', 'resources/meshes/stl/bolt_upper_leg_left_side.stl', 'resources/meshes/stl/upper_leg_200mm_right_side.stl', 'resources/meshes/stl/upper_leg_200mm_left_side.stl', 'resources/meshes/stl/bolt_hip_fe_right_side.stl', 'resources/meshes/stl/bolt_lower_leg_left_side.stl', 'resources/meshes/stl/bolt_foot.stl', 'resources/meshes/stl/lower_leg_200mm_left_side.stl', 'resources/meshes/stl/bolt_hip_fe_left_side.stl', 'resources/meshes/stl/bolt_lower_leg_right_side.stl', 'resources/meshes/stl/bolt_upper_leg_right_side.stl', 'resources/meshes/stl/bolt_body.stl']
resources =  ['resources/impedance_ctrl.yaml', 'resources/dynamic_graph_manager/dgm_parameters_solo12_wireless_mpi_is.yaml', 'resources/dynamic_graph_manager/dgm_parameters_solo12_mpi_is.yaml', 'resources/dynamic_graph_manager/dgm_parameters_solo8.yaml', 'resources/dynamic_graph_manager/dgm_parameters_solo12_nyu.yaml', 'resources/dynamic_graph_manager/dgm_parameters_solo12.yaml', 'resources/dynamic_graph_manager/dgm_parameters_solo8ti.yaml', 'resources/odri_control_interface/solo12_driver.yaml', 'resources/launch/visual_rviz.launch', 'resources/launch/dashboard.launch', 'resources/launch/bringup.launch', 'resources/launch/rviz.launch', 'resources/rviz/display.rviz', 'resources/rviz/solo.rviz', 'resources/rviz/dgbullet_vs_pybullet.rviz', 'resources/pycache/init.cpython-38.pyc', 'resources/srdf/solo.srdf', 'resources/pre_generated_urdf/readme.md', 'resources/xacro/solo8.urdf.xacro', 'resources/xacro/solo12.urdf.xacro', 'resources/xacro/plane_with_restitution.urdf.xacro', 'resources/xacro/leg.xacro', 'resources/rqt/solo.perspective.in', 'resources/meshes/cylinder.obj', 'resources/meshes/checker_blue.png', 'resources/meshes/cube.obj', 'resources/meshes/plane.obj', 'resources/meshes/sphere.obj', 'resources/meshes/plane.mtl', 'resources/meshes/obj/without_foot/solo_body.obj', 'resources/meshes/obj/without_foot/solo_lower_leg_left_side.mtl', 'resources/meshes/obj/without_foot/solo_upper_leg_right_side.obj', 'resources/meshes/obj/without_foot/solo_upper_leg_right_side.mtl', 'resources/meshes/obj/without_foot/solo_lower_leg_right_side.obj', 'resources/meshes/obj/without_foot/solo_lower_leg_right_side.mtl', 'resources/meshes/obj/without_foot/solo_upper_leg_left_side.mtl', 'resources/meshes/obj/without_foot/solo_body.mtl', 'resources/meshes/obj/without_foot/solo_lower_leg_left_side.obj', 'resources/meshes/obj/without_foot/solo_upper_leg_left_side.obj', 'resources/meshes/obj/with_foot/solo_body.obj', 'resources/meshes/obj/with_foot/solo_lower_leg_left_side.mtl', 'resources/meshes/obj/with_foot/solo_upper_leg_right_side.obj', 'resources/meshes/obj/with_foot/solo_foot.obj', 'resources/meshes/obj/with_foot/solo_upper_leg_right_side.mtl', 'resources/meshes/obj/with_foot/solo_lower_leg_right_side.obj', 'resources/meshes/obj/with_foot/solo_lower_leg_right_side.mtl', 'resources/meshes/obj/with_foot/solo_upper_leg_left_side.mtl', 'resources/meshes/obj/with_foot/solo_foot.mtl', 'resources/meshes/obj/with_foot/solo_body.mtl', 'resources/meshes/obj/with_foot/solo_lower_leg_left_side.obj', 'resources/meshes/obj/with_foot/solo_upper_leg_left_side.obj', 'resources/meshes/stl/without_foot/solo_body.stl', 'resources/meshes/stl/without_foot/solo_lower_leg_left_side.stl', 'resources/meshes/stl/without_foot/solo_upper_leg_left_side.stl', 'resources/meshes/stl/without_foot/solo_lower_leg_right_side.stl', 'resources/meshes/stl/without_foot/solo_upper_leg_right_side.stl', 'resources/meshes/stl/solo12/solo12_lower_leg_left_side.stl', 'resources/meshes/stl/solo12/_solo12_visualisation_model.PDF', 'resources/meshes/stl/solo12/solo_12_base.stl', 'resources/meshes/stl/solo12/solo12_hip_fe_hl.stl', 'resources/meshes/stl/solo12/solo12_hip_fe_fr.stl', 'resources/meshes/stl/solo12/solo12_upper_leg_left_side.stl', 'resources/meshes/stl/solo12/solo12_upper_leg_right_side.stl', 'resources/meshes/stl/solo12/solo12_hip_fe_fl.stl', 'resources/meshes/stl/solo12/solo12_hip_fe_hr.stl', 'resources/meshes/stl/solo12/solo12_coordinate_systems_4.png', 'resources/meshes/stl/solo12/solo12_lower_leg_right_side.stl', 'resources/meshes/stl/solo12/solo12_coordinate_systems_2.png', 'resources/meshes/stl/solo12/solo12_coordinate_systems.png', 'resources/meshes/stl/solo12/solo12_coordinate_systems_3.png', 'resources/meshes/stl/with_foot/solo_body.stl', 'resources/meshes/stl/with_foot/solo_lower_leg_left_side.stl', 'resources/meshes/stl/with_foot/solo_upper_leg_left_side.stl', 'resources/meshes/stl/with_foot/solo_lower_leg_right_side.stl', 'resources/meshes/stl/with_foot/solo_foot.stl', 'resources/meshes/stl/with_foot/solo_upper_leg_right_side.stl']
--- stderr: robot_properties_bolt
resources =  ['resources/impedance_ctrl.yaml', 'resources/dynamic_graph_manager/dgm_parameters_bolt.yaml', 'resources/odri_control_interface/bolt_driver.yaml', 'resources/pycache/init.cpython-38.pyc', 'resources/xacro/bolt_passive_ankle.urdf.xacro', 'resources/xacro/bolt.urdf.xacro', 'resources/xacro/plane_with_restitution.urdf.xacro', 'resources/xacro/bolt.xacro', 'resources/xacro/leg.xacro', 'resources/meshes/checker_blue.png', 'resources/meshes/plane.obj', 'resources/meshes/plane.mtl', 'resources/meshes/obj/bolt_upper_leg_right_side.obj', 'resources/meshes/obj/bolt_hip_fe_left_side.obj', 'resources/meshes/obj/bolt_upper_leg_left_side.obj', 'resources/meshes/obj/bolt_lower_leg_right_side.obj', 'resources/meshes/obj/bolt_hip_fe_right_side.obj', 'resources/meshes/obj/bolt_body.obj', 'resources/meshes/obj/bolt_foot.obj', 'resources/meshes/obj/bolt_lower_leg_left_side.obj', 'resources/meshes/stl/lower_leg_200mm_right_side.stl', 'resources/meshes/stl/bolt_upper_leg_left_side.stl', 'resources/meshes/stl/upper_leg_200mm_right_side.stl', 'resources/meshes/stl/upper_leg_200mm_left_side.stl', 'resources/meshes/stl/bolt_hip_fe_right_side.stl', 'resources/meshes/stl/bolt_lower_leg_left_side.stl', 'resources/meshes/stl/bolt_foot.stl', 'resources/meshes/stl/lower_leg_200mm_left_side.stl', 'resources/meshes/stl/bolt_hip_fe_left_side.stl', 'resources/meshes/stl/bolt_lower_leg_right_side.stl', 'resources/meshes/stl/bolt_upper_leg_right_side.stl', 'resources/meshes/stl/bolt_body.stl']
/home/roy/.local/lib/python3.8/site-packages/recommonmark/parser.py:75: UserWarning: Container node skipped: type=document
warn("Container node skipped: type={0}".format(mdnode.t))
pybullet build time: Oct 11 2021 20:59:39
WARNING: autodoc: failed to import module 'bolt_wrapper' from module 'robot_properties_bolt'; the following exception was raised:
cannot import name 'Resources' from 'robot_properties_bolt.resources' (/home/roy/odri_dev/workspace/src/robot_properties_bolt/src/robot_properties_bolt/resources/init.py)
WARNING: autodoc: failed to import module 'config' from module 'robot_properties_bolt'; the following exception was raised:
cannot import name 'Resources' from 'robot_properties_bolt.resources' (/home/roy/odri_dev/workspace/src/robot_properties_bolt/src/robot_properties_bolt/resources/init.py)
WARNING: autodoc: failed to import module 'gepetto_gui_loader' from module 'robot_properties_bolt'; the following exception was raised:
No module named 'config'
/home/roy/odri_dev/workspace/src/robot_properties_bolt/src/robot_properties_bolt/resources/init.py:docstring of robot_properties_bolt.resources:1: WARNING: duplicate object description of robot_properties_bolt.resources, other instance in robot_properties_bolt, use :noindex: for one of them
/home/roy/odri_dev/workspace/build/robot_properties_bolt/build/lib/robot_properties_bolt/doc/readme.md: WARNING: document isn't included in any toctree
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_bolt/src/robot_properties_bolt/resources/xacro/bolt_passive_ankle.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_bolt/build/lib/robot_properties_bolt/resources/urdf/bolt_passive_ankle.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_bolt/src/robot_properties_bolt/resources/xacro/bolt.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_bolt/build/lib/robot_properties_bolt/resources/urdf/bolt.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_bolt/src/robot_properties_bolt/resources/xacro/plane_with_restitution.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_bolt/build/lib/robot_properties_bolt/resources/urdf/plane_with_restitution.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_bolt/src/robot_properties_bolt/resources/xacro/bolt_passive_ankle.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_bolt/build/lib/robot_properties_bolt/resources/urdf/bolt_passive_ankle.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_bolt/src/robot_properties_bolt/resources/xacro/bolt.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_bolt/build/lib/robot_properties_bolt/resources/urdf/bolt.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_bolt/src/robot_properties_bolt/resources/xacro/plane_with_restitution.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_bolt/build/lib/robot_properties_bolt/resources/urdf/plane_with_restitution.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_bolt/src/robot_properties_bolt/resources/xacro/bolt_passive_ankle.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_bolt/build/lib/robot_properties_bolt/resources/urdf/bolt_passive_ankle.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_bolt/src/robot_properties_bolt/resources/xacro/bolt.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_bolt/build/lib/robot_properties_bolt/resources/urdf/bolt.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_bolt/src/robot_properties_bolt/resources/xacro/plane_with_restitution.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_bolt/build/lib/robot_properties_bolt/resources/urdf/plane_with_restitution.urdf )

Finished <<< robot_properties_bolt [3.32s]
--- stderr: robot_properties_solo
resources =  ['resources/impedance_ctrl.yaml', 'resources/dynamic_graph_manager/dgm_parameters_solo12_wireless_mpi_is.yaml', 'resources/dynamic_graph_manager/dgm_parameters_solo12_mpi_is.yaml', 'resources/dynamic_graph_manager/dgm_parameters_solo8.yaml', 'resources/dynamic_graph_manager/dgm_parameters_solo12_nyu.yaml', 'resources/dynamic_graph_manager/dgm_parameters_solo12.yaml', 'resources/dynamic_graph_manager/dgm_parameters_solo8ti.yaml', 'resources/odri_control_interface/solo12_driver.yaml', 'resources/launch/visual_rviz.launch', 'resources/launch/dashboard.launch', 'resources/launch/bringup.launch', 'resources/launch/rviz.launch', 'resources/rviz/display.rviz', 'resources/rviz/solo.rviz', 'resources/rviz/dgbullet_vs_pybullet.rviz', 'resources/pycache/init.cpython-38.pyc', 'resources/srdf/solo.srdf', 'resources/pre_generated_urdf/readme.md', 'resources/xacro/solo8.urdf.xacro', 'resources/xacro/solo12.urdf.xacro', 'resources/xacro/plane_with_restitution.urdf.xacro', 'resources/xacro/leg.xacro', 'resources/rqt/solo.perspective.in', 'resources/meshes/cylinder.obj', 'resources/meshes/checker_blue.png', 'resources/meshes/cube.obj', 'resources/meshes/plane.obj', 'resources/meshes/sphere.obj', 'resources/meshes/plane.mtl', 'resources/meshes/obj/without_foot/solo_body.obj', 'resources/meshes/obj/without_foot/solo_lower_leg_left_side.mtl', 'resources/meshes/obj/without_foot/solo_upper_leg_right_side.obj', 'resources/meshes/obj/without_foot/solo_upper_leg_right_side.mtl', 'resources/meshes/obj/without_foot/solo_lower_leg_right_side.obj', 'resources/meshes/obj/without_foot/solo_lower_leg_right_side.mtl', 'resources/meshes/obj/without_foot/solo_upper_leg_left_side.mtl', 'resources/meshes/obj/without_foot/solo_body.mtl', 'resources/meshes/obj/without_foot/solo_lower_leg_left_side.obj', 'resources/meshes/obj/without_foot/solo_upper_leg_left_side.obj', 'resources/meshes/obj/with_foot/solo_body.obj', 'resources/meshes/obj/with_foot/solo_lower_leg_left_side.mtl', 'resources/meshes/obj/with_foot/solo_upper_leg_right_side.obj', 'resources/meshes/obj/with_foot/solo_foot.obj', 'resources/meshes/obj/with_foot/solo_upper_leg_right_side.mtl', 'resources/meshes/obj/with_foot/solo_lower_leg_right_side.obj', 'resources/meshes/obj/with_foot/solo_lower_leg_right_side.mtl', 'resources/meshes/obj/with_foot/solo_upper_leg_left_side.mtl', 'resources/meshes/obj/with_foot/solo_foot.mtl', 'resources/meshes/obj/with_foot/solo_body.mtl', 'resources/meshes/obj/with_foot/solo_lower_leg_left_side.obj', 'resources/meshes/obj/with_foot/solo_upper_leg_left_side.obj', 'resources/meshes/stl/without_foot/solo_body.stl', 'resources/meshes/stl/without_foot/solo_lower_leg_left_side.stl', 'resources/meshes/stl/without_foot/solo_upper_leg_left_side.stl', 'resources/meshes/stl/without_foot/solo_lower_leg_right_side.stl', 'resources/meshes/stl/without_foot/solo_upper_leg_right_side.stl', 'resources/meshes/stl/solo12/solo12_lower_leg_left_side.stl', 'resources/meshes/stl/solo12/_solo12_visualisation_model.PDF', 'resources/meshes/stl/solo12/solo_12_base.stl', 'resources/meshes/stl/solo12/solo12_hip_fe_hl.stl', 'resources/meshes/stl/solo12/solo12_hip_fe_fr.stl', 'resources/meshes/stl/solo12/solo12_upper_leg_left_side.stl', 'resources/meshes/stl/solo12/solo12_upper_leg_right_side.stl', 'resources/meshes/stl/solo12/solo12_hip_fe_fl.stl', 'resources/meshes/stl/solo12/solo12_hip_fe_hr.stl', 'resources/meshes/stl/solo12/solo12_coordinate_systems_4.png', 'resources/meshes/stl/solo12/solo12_lower_leg_right_side.stl', 'resources/meshes/stl/solo12/solo12_coordinate_systems_2.png', 'resources/meshes/stl/solo12/solo12_coordinate_systems.png', 'resources/meshes/stl/solo12/solo12_coordinate_systems_3.png', 'resources/meshes/stl/with_foot/solo_body.stl', 'resources/meshes/stl/with_foot/solo_lower_leg_left_side.stl', 'resources/meshes/stl/with_foot/solo_upper_leg_left_side.stl', 'resources/meshes/stl/with_foot/solo_lower_leg_right_side.stl', 'resources/meshes/stl/with_foot/solo_foot.stl', 'resources/meshes/stl/with_foot/solo_upper_leg_right_side.stl']
/home/roy/.local/lib/python3.8/site-packages/recommonmark/parser.py:75: UserWarning: Container node skipped: type=document
warn("Container node skipped: type={0}".format(mdnode.t))
pybullet build time: Oct 11 2021 20:59:39
WARNING: autodoc: failed to import module 'config' from module 'robot_properties_solo'; the following exception was raised:
cannot import name 'Resources' from 'robot_properties_solo.resources' (/home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/init.py)
WARNING: autodoc: failed to import module 'gepetto_gui_loader' from module 'robot_properties_solo'; the following exception was raised:
No module named 'config'
WARNING: autodoc: failed to import module 'quadruped12wrapper' from module 'robot_properties_solo'; the following exception was raised:
cannot import name 'Resources' from 'robot_properties_solo.resources' (/home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/init.py)
WARNING: autodoc: failed to import module 'solo12wrapper' from module 'robot_properties_solo'; the following exception was raised:
cannot import name 'Resources' from 'robot_properties_solo.resources' (/home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/init.py)
WARNING: autodoc: failed to import module 'solo8wrapper' from module 'robot_properties_solo'; the following exception was raised:
cannot import name 'Resources' from 'robot_properties_solo.resources' (/home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/init.py)
/home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/init.py:docstring of robot_properties_solo.resources:1: WARNING: duplicate object description of robot_properties_solo.resources, other instance in robot_properties_solo, use :noindex: for one of them
/home/roy/odri_dev/workspace/build/robot_properties_solo/build/lib/robot_properties_solo/doc/readme.md: WARNING: document isn't included in any toctree
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/xacro/solo8.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_solo/build/lib/robot_properties_solo/resources/urdf/solo8.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/xacro/solo12.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_solo/build/lib/robot_properties_solo/resources/urdf/solo12.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/xacro/plane_with_restitution.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_solo/build/lib/robot_properties_solo/resources/urdf/plane_with_restitution.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/xacro/solo8.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_solo/build/lib/robot_properties_solo/resources/urdf/solo8.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/xacro/solo12.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_solo/build/lib/robot_properties_solo/resources/urdf/solo12.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/xacro/plane_with_restitution.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_solo/build/lib/robot_properties_solo/resources/urdf/plane_with_restitution.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/xacro/solo8.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_solo/build/lib/robot_properties_solo/resources/urdf/solo8.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/xacro/solo12.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_solo/build/lib/robot_properties_solo/resources/urdf/solo12.urdf )
building xacro file ( /home/roy/odri_dev/workspace/src/robot_properties_solo/src/robot_properties_solo/resources/xacro/plane_with_restitution.urdf.xacro ) into ( /home/roy/odri_dev/workspace/build/robot_properties_solo/build/lib/robot_properties_solo/resources/urdf/plane_with_restitution.urdf )

Finished <<< robot_properties_solo [3.45s]
Starting >>> mim_control
Finished <<< mim_control [0.36s]

Summary: 10 packages finished [7.73s]
3 packages had stderr output: bullet_utils robot_properties_bolt robot_properties_solo

I then source with source install/setup.bash with no output results.
Finally I run python3 src/reactive_planners/demos/demo_reactive_planners_bolt_step_adjustment.py and I encounter this error that I'm stuck on:

pybullet build time: Oct 11 2021 20:59:39
/opt/openrobots/lib/python3.8/site-packages/pinocchio/shortcuts.py:45: UserWarning: You passed package dir(s) via argument geometry_model and provided package_dirs.
geom_model = pin.buildGeomFromUrdf(model, filename, geometry_type, package_dirs)
Traceback (most recent call last):
File "src/reactive_planners/demos/demo_reactive_planners_bolt_step_adjustment.py", line 15, in
from reactive_planners_cpp import DcmReactiveStepper
ImportError: /home/roy/odri_dev/workspace/install/reactive_planners/lib/libreactive_planners.so: undefined symbol: _ZN5Eigen13QuadProgDense5solveERKNS_3RefIKNS_6MatrixIdLin1ELin1ELi0ELin1ELin1EEELi0ENS_11OuterStrideILin1EEEEERKNS1_IKNS2_IdLin1ELi1ELi0ELin1ELi1EEELi0ENS_11InnerStrideILi1EEEEES9_SG_S9_SG_b

Regarding this error I have no clue left as to what to do next. Thank you so much for your time and help!

Hello,
Sorry for my late response. Could you share with us which commit of each repository you are using?
Currently, reactive_planner doesn't support Ubuntu 20, but we are working on it.

Hello! No worries about the late response, I myself am also giving a late response after the winter holidays :) Hope you guys had a good break!
As for the commit of each repository:
For reactive_planner:

commit d6d72a71ab6d71836eb5700b81f7071fac668ec5 (HEAD -> master, origin/master, origin/HEAD)
Author: majidkhadiv<EMAIL_ADDRESS>Date:   Fri Sep 24 12:00:35 2021 +0200

For robot_properties_bolt

commit 8f5ecca8b91ca5c3596716b9162e8da36e8df823 (HEAD -> master, origin/master, origin/HEAD)
Author: Elham Daneshmand<EMAIL_ADDRESS>Date:   Sun Aug 29 15:21:36 2021 +0200

For the near future would you recommend trying reactive_planner only on an Ubuntu 18 machine? Thank you very much!

Ok, so I'm not sure what the heck happened, but I recompiled the workspace today and suddenly everything worked! Not sure why though, were there some changes recently pushed to apt relating to robotpkg? That's the only change I can think of.

Great. So, I close this issue because the problem is solved.
Currently, reactive_planner is only tested on Ubuntu 18.

I would also like to make a quick note for future people. I was able to get reactive_planner to work on another laptop that was a fresh Ubuntu 20 installation too. So it's definitely possible, but as @Lhumd said be careful!
Thanks :)


Safari 16: Permissions API

Same as https://github.com/Fyrd/caniuse/pull/6230; understandably given the support, only geolocation worked:

Thanks!


[Enhancement] Specify fskey of builtin storage volume

Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 9 / 10 (90.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/server/SharedDataStorageVolumeMgr.java
9
10
90.00%
[404]

[FE PR Coverage Check]
:heart_eyes: pass : 9 / 10 (90.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/server/SharedDataStorageVolumeMgr.java
9
10
90.00%
[404]

@Mergifyio backport branch-3.1


Setup step does not work

I tried to follow your setup instructions several times but my chrome browser doesn't recognize navigator.webcard
OS: MacOS Catalina
Browser: Chrome
Problem: Missing webcard object in navigator

same


Is there a way to turn off 'Loading' and flash effect?

Hi,
I'm testing out https://github.com/Rebilly/generator-openapi-repo#generator-openapi-repo live editing locally. Is there a way to turn off "Loading" and flash effect on refresh? Relatively small docs should render pretty fast.
Thanks,
Moon

Hey @moon0326,
Great suggestion!
I will add new option for ReDoc to disable Loading


Linking react-navie-vector-icons

If I add nachos-ui to my project by:
yarn add nachos-ui
and try to use some icons (ex.: setting state of Input to 'error') I got an error: Unrecognized font family 'Ionicons'. The obvious solution is to link react-native-vector-icons like this:
react-native link react-native-vector-icons
Can you, please, mention it in documentation or force it somehow automatically?

Good point, I'll add it.

Hey folks, I've got the same issue here.

Running react-native link react-native-vector-icons not fixed my problem. Since I didn't have react-native-vector-icons as a dependency.
I'd suggest put on documentation how to link fonts into your project, I don't think everyone wants to use nachos-ui with  react-native-vector-icons.
We could follow RNPM approach EXAMPLE 1
or EXAMPLE 2 and put fonts assets on npm package.
@petrbrzek, what do you think? Just linking fonts after the npm install nachos-ui will solve the problem?

my nightmare


refactor(buildimages): Move and rename get-gitlab-config-image-tag

What does this PR do?

Move the get-gitlab-config-image-tag from pipelines.py to buildimages.py
Rename in get-image-tag
Replace occurrences of GitlabYamlLoader by ReferenceTag

Motivation
Refactoring
Describe how to test/QA your changes
Invoke unit tests + manually ran the new task
Possible Drawbacks / Trade-offs
Additional Notes
Based on #30365

/merge


TODO LIST

macOS support
AI Ads filtering
Gallery download (archive)
Sync with CloudKit
Gallery download (parsing) #5

It doesn't mean I'm not going to do it if your feature request isn't on my todo list.
It's just what I personally want to do.

@chihchy pin this plz.


nbSPI do not work on esp8266 arduino sdk 3.0.1 and 3.1.2

hello,bro,i am diy my espboy, When I was compiling the Arduino project, I found that nbSPI was not working.
gpio16 as reverse tft cs pin, when high level .cs pin is active.
gpio 12(the spi miso pin) as tft dc pin .high level as tft display data , low level as tft display data. i do not konw  the reason.
maybe:

gpio 12 is spi miso pin,so nbspi do not work
2.nbspi spi speed is too fast
I hope to receive your assistance.
Here is my test code

// TFT_eSPI setup ST7735
#define TFT_MISO  PIN_D6  // D6 not connect,Automatically assigned with ESP8266 if not defined
#define TFT_MOSI  PIN_D7  // Automatically assigned with ESP8266 if not defined
#define TFT_SCLK  PIN_D5  // Automatically assigned with ESP8266 if not defined

//#define TFT_CS    -1  // Chip select control pin D8
#define TFT_DC    12  // Data Command control pin
#define TFT_RST   -1

// nbspi setup
// Set an IO to measure timing
#define NBSPI_TDBG_IO 12
#define NBSPI_TDBG_HIGH GPOS = (1<<NBSPI_TDBG_IO) // 0.1 ?s
#define NBSPI_TDBG_LOW GPOC = (1<<NBSPI_TDBG_IO) // 0.1 ?s

#include <TFT_eSPI.h>
#include <SPI.h>
#include "nbSPI.h"
TFT_eSPI tft;
extern SPIClass spi;
uint8_t sBuffer[50][50];
void setup() {
  int i;
  Serial.begin(115200);
  Serial.println("hello 1");
  pinMode(16, OUTPUT);  // select
  digitalWrite(16, 1);  // cs active
  tft.begin();
  tft.fillScreen(TFT_RED);
  delay(1000);
  memset(sBuffer, 0xff, 2500);
  tft.setAddrWindow(10, 10, 50, 50);
  NBSPI_TDBG_HIGH;
  spi.transfer((uint8_t *)sBuffer, 2500);
  NBSPI_TDBG_LOW;
  memset(sBuffer, 0, 2500);
  while (nbSPI_isBusy())
    ;
  Serial.println("hello 1");
  NBSPI_TDBG_HIGH;
  //spi.transfer((uint8_t *)sBuffer, 2500);
  nbSPI_writeBytes((uint8_t *)sBuffer, 1600);
  NBSPI_TDBG_LOW;
  Serial.println("hello 2");
  while (nbSPI_isBusy()) {
    delayMicroseconds(2);
  };
  Serial.println("hello end3");
}

void loop() {
  delay(1000);
  // put your main code here, to run repeatedly:
}

Hello.
Are you using the standard ESPboy circuit?
https://www.instructables.com/ESPboy-DIY-Retro-Gaming-and-Software-Development-M/
Because the standard ESPboy
GPIO12 (D6) is not used
GPIO16 (D0) is used for DC display
CS display is controlled by MCP23017
I would like to point out that if you use the standard ESPboy circuit and the recommended components (in particular the display model), then nbSPI should work fine.
If you have changed the schematic, it is no longer ESPboy and there may be problems that need to be dealt with separately.

hi,Thank you for your reply.
yes,I didn't use MCP23017.Just consider it as a game console.
so i changed the schematic.
gpio 16 14 13 12 as tft spi pin
spiflash use dout mode  to frree up gpio 9,10.
other pin 0 1 2 3 4 9 10 15 as button pins
io5 as buzzer pin,not use rgb led
I have a idea , because i use 160x128 tft,so i can use (160-128) X 128 range as virtual RGB LED.
or 14 13 12 as tft pin,cs pin is gnd.
other pin 0 1 2 3 16 9 10 15 as button pins
and pin 4 is led,pin 5 is buzzer
fortunately , i can use nbspi work on my diy espboy by change the nbSPI.h.
I Deleted " "NBSPI_TDBG_HIGH NBSPI_TDBG_LOW" in  the function void nbSPI_writeBytes() and void nbSPI_ISR();
instead of
while (nbSPI_isBusy());
NBSPI_TDBG_HIGH;
nbSPI_writeBytes((uint8_t *)sBuffer, size);
while (nbSPI_isBusy());  //  maybe delete to improve performance in espboy arduboy2 lib
NBSPI_TDBG_LOW;
it work well.
I think this will be helpful.

ESPboy is not a game console ) You can read more at www.espboy.com.
You have built a device of your own design and it is not an ESPboy.
That's why ESPboy has official circuitry, official modules and software and support. I spent many months to debug hardware and software to make everything work more or less stably.
Of course anyone can build any device they want, but debugging will take a long time.
I can advise you to build a real ESPboy and I will help you in this case if necessary.
Translated with DeepL.com (free version)

Not related to the ESPboy project


Add k8s recommended label app.kubernetes.io/version

Additional to labels given with https://github.com/keptn/examples/issues/91
and according to https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/ the label app.kubernetes.io/version should also be added.
"The current version of the application (e.g., a semantic version, revision hash, etc.)"

Definition of Done

[ ] Add the version label to our carts and carts-db example (e.g., use the docker image tag)
[ ] Try out the updated carts / carts-db example with Keptn 0.6.2 and manually check the pods/deployments on those labels
[ ] If possible, also update the unleash-server example (or create a follow-up issue)
[ ] If possible, also update the simplenodeservice example (or create a follow-up issue)

It would be great if the keptn CLI can check during onboarding if the labels are set in the Helm chart. It does not necessarily have to block the chart to be onboard but give the user a warning that it should be included.

This is a great idea for the cli. We should also document this.
Let's focus on updating our examples in this issue. For the implementation part in the CLI I have created a separate issue in the keptn/keptn repo: https://github.com/keptn/keptn/issues/1958

Implemented this with #106
The way it was done is to look at the version part of the image, e.g: carts:0.1.2 becomes 0.1.2
I've done this with the split function and then also use default in case there is no version information in tag:
app.kubernetes.io/version: {{ (split ":" .Values.image)._1 | default "latest" }}
Dynatrace is succesfully showing this label. And - once Dynatrace uses these labels for true version awareness we should see these 3 versions in 3 separate dynatrace service instances. right now these labels show up accumulated on a single service

Closed via #106


checks doesn't work for autocompleters

Summary
checks doesn't work for autocompleters, they works only after I selected something from the list
Reproduction Steps
I run the command

Minimal Reproducible Code
import disnake
from disnake.ext import commands

LANGUAGES = ["python", "javascript", "typescript", "java", "rust", "lisp", "elixir"]

def test_check():
    async def predicate(inter: disnake.ApplicationCommandInteraction):
        if inter.user.id ==<PHONE_NUMBER>18389249:
            return True
        return False

    return commands.check(predicate)  # type: ignore

class DisnakeIssue(commands.Cog):
    def __init__(self, bot):
        self.bot = bot

    @commands.slash_command()
    @commands.has_permissions(manage_guild=True)
    @test_check()
    async def languages(
        self, inter: disnake.ApplicationCommandInteraction, language: str
    ):
        pass

    @languages.autocomplete("language")
    async def language_autocomp(
        self, inter: disnake.ApplicationCommandInteraction, string: str
    ):
        string = string.lower()
        return [lang for lang in LANGUAGES if string in lang.lower()]

def setup(bot):
    bot.add_cog(DisnakeIssue(bot))
    print("DisnakeIssue is loaded.")

Expected Results
I should get error before I select something from this list, before I ran the command
Actual Results
I get an error only after I select something from the list
Intents
disnake.Intents.all()
System Information
- Python v3.8.10-final                                                                                - disnake v2.5.1-final                                                                                - disnake pkg_resources: v2.5.1                                                                                - aiohttp v3.7.4.post0                                                                                - system info: Windows 10 10.0.17763

Checklist

[X] I have searched the open issues for duplicates.
[X] I have shown the entire traceback, if possible.
[X] I have removed my token from display, if visible.

Additional Context
https://discord.com/channels/808030843078836254/883342278280745030/984787279530848307

Confirmed this is a bug, thanks for reporting!


'Rename' refactoring can cause incorrect indentation

In the following snippet:
let circle = { shape = Circle(64. * 0.75)
               lineStyle = lineStyle
               fillStyle = fillStyle }

using the Rename refactoring on circle and renaming to a different length string will mean that the indented properties below it are incorrectly offset. It would be cool if the refactoring automatically adjusted indentation too!

probably need https://github.com/Microsoft/visualfsharp/pull/3542

I don't think it's possible to implement given the current state of F# Compiler Services, FSAC, and state of art in code formatting/code generation with F#.


How to train the same model for custom data

Hello, thanx for the help.
Now, I am trying to train the model for my own images.
I put my images in the data/demo folder and also change number of iterations in the cfg.
Can you please suggest what more changes that I should do and also the command to train the model.
Thanks in advance.

Hi, unfortunally we did not provide explicit functionality for training on custom datasets.
Please see one of the previous replies for advice how to do this: https://github.com/aosokin/os2d/issues/24#issuecomment-1056713414
Best,
Anton


Sublime - Align JSON formatting

Doesn't seem to work for me... Ctrl + Alt + J to "Align JSON formatting"
input:
{a:1,b:[2,3.4], z:function(){}}

sublime v3 build 3083

Are you perhaps posting this in the wrong project? All cheater does is show you a cheat sheet of commands. It doesn't actually implement any of those commands.


advise to add AddWithLifetimeIfAbsent and AddIfAbsent func for SharedLRU

because in Concurrent scene, when i call contains and then call add , there will be some unexpected situation happened which will cause the condition race problem

Makes sense


Failed to connect error potentially due to double '/' when redirected to Mesos task page.

In Marathon 0.11, when clicking on the Mesos details link, I am sent to
http://daldevmesos01:5050//#/slaves/2015[......]
This results in a "Failed to connect to daldevmesos01:5050!" error on the Mesos page.
Removing the double // after the port 5050 and replacing it with a single / makes everything happy.
This is with Mesos 0.24.1.

Hi @jordmoz ,
yes, this is a known issue and is fixed in the nearly upcoming Marathon 0.12, because this behavior changed in Mesos 0.24.
https://github.com/mesosphere/marathon/issues/2266

Thanks!  Sorry for the double entry.


Feat: move HMAC verification into enclave

add gen_hmac_safe() function in functions.js and use it for verifying signature of incoming request
add EH_GEN_HMAC action and ffi_generateHmac() handler
add enclave_generate_hmac() function to enclave part of core app for handling HMAC generation in enclave
the original gen_hmac() function is still kept since verifyQuote() depends on this function

close #274

Integrate into one commit.


[app/dispatcher] Correctly implement QUIC sniffer

Current QUIC sniffer can work with curl's --http3 option, but is basically unusable when using chromium browser to browse HTTP3 websites.
Current QUIC sniffer is problematic for following three reasons:

Packet Number. Although some spec mentioned initial packet will use packet number 0, but actually chromium will always start with packet number 1.
So following check blocks all QUIC sniffing for chromium HTTP3 payload:
https://github.com/v2fly/v2ray-core/blob/83ea1ba3ba94c944d99cb063bc6c5f42d6cf2fff/common/protocol/quic/sniff.go#L145-L147

Frames. The payload of QUIC packets consists of a sequence of complete frames. Current QUIC sniffer assumes that there's only 1 frame in initial packet:
https://github.com/v2fly/v2ray-core/blob/83ea1ba3ba94c944d99cb063bc6c5f42d6cf2fff/common/protocol/quic/sniff.go#L162-L170
Above check blocks sniffing if the first frame is not crypto frame. In chromium's QUIC payload, this is often not the case. The first frame can be PADDING frame or PING frame.
Therefore, we need to parse multiple frames in QUIC packet to find a crypto frame with ClientHello payload.

CRYPTO Frames. Even if the first frame in initial packet is crypto frame, it may not contain full data for a ClientHello payload. In QUIC spec, all crypto frames make up a stream of bytes, where each crypto frame is just a slice of the stream with offset and length information in.
Therefore, we need to parse all frames in initial QUIC packet, to compose a complete CRYPTO data stream buffer, so as to fetch the complete ClientHello payload.

This PR fixes all above three issues, to provide a basically usable QUIC sniffer for browsing HTTP3 websites in chromium browser.

隔壁v2ray的quic sniffing实现是近期才修复的 https://github.com/v2fly/v2ray-core/pull/2335 ，实施于 v5.4.0（pre-release）。也许是因为xray-core存在同样的bug？你可以先去试试隔壁修复后的quic sniffing好不好使。
v2ray v5.4.0版本的 quic sniffing我测试了，没有问题，这个修复有效，sing-box目前还没有测试
2023/03/19 08:50:54 [Info] app/dns: DOH//<IP_ADDRESS> got answer: quic.nginx.org. TypeA -> [<IP_ADDRESS>] 417.026704ms
2023/03/19 08:50:54 [Debug] app/dns: domain quic.nginx.org matches following rules: [nginx.org(DNS idx:0)]
2023/03/19 08:50:54 [Debug] app/dns: domain quic.nginx.org will use DNS in order: [DOH//<IP_ADDRESS>] [TypeA]
2023/03/19 08:50:54 [Debug] app/dns: domain quic.nginx.org will use DNS in order: [DOH//<IP_ADDRESS>] [TypeAAAA]
2023/03/19 08:50:54 [Info] app/dns: DOH//<IP_ADDRESS> querying: quic.nginx.org.
2023/03/19 08:50:54 [Info] app/dns: DOH//<IP_ADDRESS> got answer: quic.nginx.org. TypeAAAA -> [] 416.473492ms
2023/03/19 08:50:56 [Info] [3127533985] app/dispatcher: sniffed domain: quic.nginx.org for tcp:<IP_ADDRESS>:443
2023/03/19 08:50:56 [Info] [3127533985] app/dispatcher: taking detour [proxy] for [tcp:quic.nginx.org:443]
2023/03/19 08:50:57 [Info] [3127533985] proxy/vmess/outbound: tunneling request to tcp:quic.nginx.org:443 via cf:443
2023/03/19 08:51:01 [Info] [3818921917] app/dispatcher: sniffed domain: quic.nginx.org for udp:<IP_ADDRESS>:443
2023/03/19 08:51:01 [Info] [3818921917] app/dispatcher: taking detour [proxy] for [udp:quic.nginx.org:443]
2023/03/19 08:51:01 [Info] [3818921917] proxy/vmess/outbound: tunneling request to udp:quic.nginx.org:443 via cf:443
2023/03/19 08:50:56 <IP_ADDRESS>:12622 accepted tcp:<IP_ADDRESS>:443 [proxy]
2023/03/19 08:50:56 <IP_ADDRESS>:12622 accepted tcp:<IP_ADDRESS>:443 [proxy]
2023/03/19 08:51:01 [Debug] transport/internet/udp: UDP original destination: udp:<IP_ADDRESS>:443
2023/03/19 08:51:01 <IP_ADDRESS>:54406 accepted udp:<IP_ADDRESS>:443 [proxy]


nbe in code

Hello. In the related paper, a neural bearing estimator is proposed, but I cannot find that network in this source code. Is that structure deprecated?

Hi, we plan to release this later on when all issues with SLD are addressed.


fixes chef/chef-provisioning-aws#82

@lynchc I admit to confusion here.  I'm assuming we merged this in chef-provisioning somewhere?

Oh, never mind.  I get it.

Merged as 912a595


intimidate application visible and immediate

Also squashed the bug everyone's been talking about where you intimidate a mon with competitive and it gets a special attack boost, but no attack fall

please find it in your heart to forgive the gross negligence allowing the competitive bug to exist


Add support for other blog engines

We curently only support Blogger blogs. We could conceivably scrape from other blog engines, such as:

Wordpress
Medium
Substack

Added support for Wordpress in af4fb48

Neither Medium nor Substack provide a suitable API for discovering posts on hosted blogs. For other blogging engines, we'll open a separate issue for each.


Can GhostFaceNets be fine tuned for facial landmark detection?

I am novice and would appreciate some advice.  I want to fine tune GhostFaceNets to detect these x and y coordinates. My question are:

Is this possible and will it be difficult?
Would you recommend that I try doing it with a different model instead of GhostFaceNets?

Any help is deeply appreciated.

I am novice and would appreciate some advice.  I want to fine tune GhostFaceNets to detect these x and y coordinates. My question are:

Is this possible and will it be difficult?
Would you recommend that I try doing it with a different model instead of GhostFaceNets?

Any help is deeply appreciated.

Hi,
GhostFaceNets is a face recognition model, that is built for recognition, verification, or feature extraction purposes to identify people.
To use it as a face detector, or object detector, you need to change the recognition head to a detection head such as YOLO, or DETR and train it on the corresponding data (e.g., WiderFACE for face detection).
Check this github link:
https://github.com/open-mmlab/mmdetection

Let me know if you have any other questions

I am novice and would appreciate some advice.  I want to fine tune GhostFaceNets to detect these x and y coordinates. My question are:

Is this possible and will it be difficult?
Would you recommend that I try doing it with a different model instead of GhostFaceNets?

Any help is deeply appreciated.

Thanks for the information. I will look into MMDetection.


Submit a Cloud Definition

word [REQUIRED]: High availability
content [REQUIRED]: Is one of the benefits of the cloud that help maintain availability due to network outages, app failure, power outages and more
learn more URL [REQUIRED]: https://www.techtarget.com/searchdatacenter/definition/high-availability.
tag [REQUIRED, select one]: service
abbreviation [OPTIONAL]: HA
author name [REQUIRED]: Alexandros Kourtis
author link [REQUIRED]: https://github.com/alexkourtis98

all good :)


Refactor code

Refactor code to implement new enhancements and fix problems:
1 - PEP compliance
2 - New and fast way to instance classes to run checks
3 - General method to parse and analyze most of checks

It would be good to have common way of error handling. If a single resource analysis/generation fails, the whole process of network discovery should not be aborted.
I think it would be also good for the code to be split into three parts:

Resource generation
Report printing
Other data exports e.g. #16

We could create a new class e.g. Resource, which would store details like type, id, name, perhaps relations to other resources

Hmmm ok.. Let me know more about your idea of a Resource class....
Other itens I agree totally.. We maybe focus now on finish all resources that use VPC, and in each release refactor a piece of code...

Maybe something like below would be working for us:
class Resource(NamedTuple):
    id: str # we could stick with Terraform id approach for identification of resources to ensure uniqueness within same type
    name: str
    type: str # we could stick to Terraform names e.g. aws_nat_gateway
    details: str # to keep e.g. path that leads to a VPC, later we could add more graph-like fields to define eges

class NATGATEWAY: # or any other resource detection class
    def run(self) -> List[Resource]:
        resources = []
        ... # add resources there
        return resources

class ReportGenerator:
    def process(self, resources):
        ... group resources by type and print them

class DiagramGenerator:
    def process(self, resources):
        ... draw diagram

Ok @meshuga. Get it!.. I'll create a separate branch to implement a prototype and validate the idea...
It really is a simpler way to store and reuse all discovered resources in report / diagram / export classes.

Agree, that's more or less how Terraformer works :)

Code refactor to implement a new kind of check. Now is much cleaner and allows to process new kind of reports, outputs, diagrams, whatever.
78cb09e

[ ] Resource generation
[ ] Report printing
[ ] Other data exports e.g. #16
[ ] PEP-8 rules
[ ] New and fast way to instance classes to run checks
[ ] General method to parse and analyze most of checks


Move variable declaration to start of function.

Fixes https://github.com/VirusTotal/yara-python/issues/143

@wxsBSD do you know if there were any other changes like this in the 4.0 release?

There might be, I haven't swept the tree for all of them. Best I can suggest is to apply the patch and test the build using your toolchain.


[HUDI-2970] Add test for archiving partition delete commit

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@xushiyan : Can we also parametrize the test for delete partitions.


Support Welsh practices

I have done some work on supporting Welsh data from Primary Care Services from the NHS Wales Shared Services Partnership (NWSSP) in my wales branch and a version of the OpenPrescribing site populated with this data can be found at http://prescribing.stupidpupil.co.uk/.
I'm afraid that I haven't used Python much, let alone Django, and this might be obvious even in the little code that I've written. You can also see that I've ended up mixing fixes to Python 3 compatibility with that branch, which I know is rather unclean.
Outstanding issues with the Welsh data are described below. I'd appreciate any criticisms or warnings of things to watch out for. Thank you for producing this tool.
Immediate issues
Registered populations
I don't believe that there are any sources of regular information on Welsh practice's list sizes/registered populations broken down by gender and 10-year age-bands, as required to calculate STAR-PUs and ASTRO-PUs. (The only information I've turned up can be found on the Welsh Government website, and it's this that I've tortured to provide data for the site linked above.) I have begun to pursue this.
Practice setting/Type of Practice
The HSCIC's epraccur.csv file has the setting of all Welsh practices as 'Other'. For now, I've simply marked any practice listed in WG's QOF Practice Lookup file as a 'GP Practice'.
Smoke tests, and other validation
I haven't had the chance to investigate the smoke tests and construct Welsh equivalents, nor to validate the outputs of the tool against anything else.
Next steps
Compatibility with HSCIC data
The only areas that I believe there's a risk of conflict are:

Deleting prescribing data when importing either NWSSP or HSCIC data. I've tried to prevent this for HSCIC data in da4513a6484afbf5e649a94730d4ccfc74e44694 and avoided it in the NWSSP import command.
The 'chemicals' that HSCIC groups under 4-character codes I believe that NWSSP provides full 9-character codes for. (My guess is that it's probably entirely unnecessary to use both sets of Chemicals data, and that a preference for or against these 4-character codes could be fixed or made available as an option for the import...prescribing commands.)
Determining practice settings, for the reasons described above. Currently determining the setting of Welsh practices would have to take place after doing so for English practices. (Although there's plenty of management commands that are order-sensitive, this is still little irritating.)

However, I have not checked there aren't other problems yet by actually trying to run a site with both sets of data.
Replacing Localities with GP Clusters?
I'm not sure that 'Localities' are a very useful way to group practices, and I've only done so because the NWSSP prescribing data extracts imply that it's the preferred one. Welsh GP Clusters might be more useful in Wales and more useful in the context of comparisons with English CCGs.
On the other hand, Clusters don't have a defined catchment area and so any geographical representation of them is probably going to depend on the distribution of practices' population. It's possible that the Public Health Wales Observatory might be able to provide something useful.

@MalwenGoch has turned up what I think might be a coding issue between the two countries.

BNF/Chem
England
Wales

041002, Nicotine Dependence
~100k items
~90 items

0410020B0
~50k items
~75 items

0410000P0
'Unknown', ~100k items
'Nicotine', ~4k items

Numbers of registered patients by GP practice, 2004-14: http://gov.wales/docs/statistics/adhocrequests/2015/151214-number-registered-patients-gp-practice-2004-2014-en.xlsx

Unfortunately we need registered populations broken down by age and gender, not just the total list size.

Figures for 2014 here: https://t.co/FSbJD0pDyz Any good?

Better! It is those figures that I have used so far and that I have linked to in the issue above. (Similar data can be found for 2013 also, by looking at the related ad-hoc statistical requests.
Unfortunately, even these one-off releases are not detailed enough to calculate STAR-PUs (etc.) correctly (as described in the HSCIC's Prescribing Measures document). I've tortured the data to produce STAR-PUs by making (silly) assumptions like the number of male 15-44 year olds is split evenly across the three 10-year age-bands.
I'm afraid that this data is simply currently publicly unavailable. I believe that it will be possible to get this data made a regular public release, and I have made some contact with people in Welsh Government and the NHS Wales Shared Services Partnership about this. (At this point in the year, I'm reluctant to badger them about this issue - I don't want them to experience OpenPrescribing as just another demand on their time.)

I've met with someone from Primary Care Services here - they were quite enthusiastic about OpenPrescribing and I'll be working with them to make the information available. However it looks like it's going to be a few months before we can get a reliable feed of the practice demographics available - I'm hoping that this can happen by June.

Closing as a very old issue.
We have written about supporting other countries on our blog but it isn't a priority at the moment due to OpenSAFELY.
https://www.bennett.ox.ac.uk/blog/2020/02/openprescribing.yourcountry/


[c++ grpc] Make io_manager_tag non-copyable

Built on top of #888.

@chwarr, I've reverted the rest and merged with master.


[Core][Distributed] add cleanup code for model parallel

I did a quick search and find that only test code calls destroy_model_parallel:
https://github.com/vllm-project/vllm/blob/d627a3d837976a23f89ba808f5ef6908fdb65bfa/tests/lora/conftest.py#L26
https://github.com/vllm-project/vllm/blob/d627a3d837976a23f89ba808f5ef6908fdb65bfa/tests/conftest.py#L50
This means user's code never called destroy_model_parallel.

I met some strange cleanup bugs today, and find the bug is in the cleanup logic.
I think the problem is, user's code never called destroy_model_parallel , so the resource of model parallel group is never released, leading to strange errors like https://github.com/vllm-project/vllm/pull/3829#issuecomment-2037224229 (which is "fixed" in https://github.com/vllm-project/vllm/pull/3702 ).
However, I admit that I'm not confident with this. The bug is unstable and difficult to reproduce.

but this is called?
https://github.com/vllm-project/vllm/blob/fa32207842f1ed5a966372ed0513914bff8426c4/vllm/distributed/device_communicators/pynccl.py#L282-L285

close in favor of https://github.com/vllm-project/vllm/pull/4508 .


Module does not support for_each

Describe the Bug
The module is unable to support for_each since it contains provider configuration:
Module "foo" cannot be used with for_each because it contains a
nested provider configuration for "aws.requester", at
.terraform/modules/foo/requester.tf:60,10-15.

Expected Behavior
The module should support for_each loops.
Additional Context
I believe passing the providers into the module (instead of configuring the providers w/in the module) would do the trick. I labeled this as bug but it may be a feature request instead.

Hi all, any update in this feature?

I think this would be a good extension to this module. Since this would be a breaking change, we'd require a migration doc, updated examples, and move to the next major version of 1.x. We would also try to close as many open issues as possible with prs for that release.
I'd like to work on this when I find the time. Feel free to contribhte the change too and we will review.


HUE-9368. Documentation changes (sree)

Added instructions to setup a Hive 2.3.2 demo instance locally using docker, and connect Hue to the new instance.

Excellent one! Just a comment on the indentation

Sweet!


ModuleNotFoundError:  Modules not loading in new home assistant?

Not sure if this is a "them" issue or not but in the newest HA that I believe I upgraded to the other day, I am getting
ModuleNotFoundError: No module named 'bluepy'
This worked fine before the upgrade...
Home Assistant 2022.7.3
Supervisor 2022.07.0
Operating System 8.2
Frontend 20220707.0 - latest

Look in the Bluetooth breaking changes here in the 2022.7 release notes:
https://www.home-assistant.io/blog/2022/07/06/release-20227/#breaking-changes
bluepy is no longer supported.

Thanks


CAMEL-17574: Test module for camel-main applications

Fix for https://issues.apache.org/jira/browse/CAMEL-17574

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] If you're unsure, you can format the pull request title like [CAMEL-XXX] Fixes bug in camel-file component, where you replace CAMEL-XXX with the appropriate JIRA issue.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean install -Psourcecheck in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/main/CONTRIBUTING.md

Motivation
The Camel Main mode is more frequently used and proposed features that are not available from the well known base class CamelTestSupport such that it is hard to test as it is. The goal of this PR is to propose a new base class for all the test classes for Camel Main applications.
Modifications

Propose the new base class  CamelMainTestSupport
Propose a way to replace beans automatically created and bound by Camel
Propose a simple way to specify a custom property placeholder location based on the name of the file by assuming that it is located in the same package as the test class
Fix the formatting issues in the code snippet embedded in the Javadoc

Once merged, I will modify the tests of the examples to leverage it

Great work this is a good start, and while you migrate the examples you may find ideas for things to improve more, then feel free to send more PRs


Extract init-script contents out of 'develocity-gradle.yml'

Previously, init-script content was inlined directly into 'develocity-gradle.yml'
To facilitate sharing and ease maintenance, these contents have been extracted into separate files.

Raw init-script content in src/gradle/init-scripts
Template for yml file in `src/gradle/develocity-gradle.template.yml'
Build script to regenerate final yml is build.sh
The build-verification workflow verifies that the develocity-gradle.yml file in the repo is up-to-date with respect to source inputs

Nice ! So if understood correctly, the dev flow should look like this:

make change to an init script locally
run build.sh locally
push
the workflow will run build.sh as well, compare the commited develocity-gradle.yml with the generated one and fail if different (right ?)

Yes, this is what I've implemented. It requires a manual process to update develocity-gradle.yml, with a workflow that will ensure this has been done. Since we don't expect frequent updates to the reference init-script, this seemed suitable.
Another option is to have a workflow that runs build.sh and auto-commits any change. We do this now in gradle/actions to generate the output, but it has some drawbacks:

Tests would need to be updated so that we run build.sh locally before testing: otherwise for any PRs you could be testing the old develocity-gradle.yml file.
It's not possible to trigger another workflow from an auto-generated commit

Nice ! So if understood correctly, the dev flow should look like this:

make change to an init script locally
run build.sh locally
push
the workflow will run build.sh as well, compare the commited develocity-gradle.yml with the generated one and fail if different (right ?)

Yes, this is what I've implemented. It requires a manual process to update develocity-gradle.yml, with a workflow that will ensure this has been done. Since we don't expect frequent updates to the reference init-script, this seemed suitable.
Another option is to have a workflow that runs build.sh and auto-commits any change. We do this now in gradle/actions to generate the output, but it has some drawbacks:

Tests would need to be updated so that we run build.sh locally before testing: otherwise for any PRs you could be testing the old develocity-gradle.yml file.
It's not possible to trigger another workflow from an auto-generated commit

I think the current "manual" approach is best


Locale-dependent assets

We currently adopted a workaround to localize JavaScript assets.
For instance, we have
'core/locale' => array(
    array(
        'javascript',
        REL_DIR_FILES_TOOLS_REQUIRED . '/i18n_js',
        array('combine' => false, 'minify' => false, 'local' => false)
    )
)

The options combine, minify and local are set to false because the file is locale-dependent, so we can't currently cache it and combine it with the other JavaScript files.
What about adding an option locale-dependent instead of  combine, minify and local?
We could cache and combine these assets, and save/retrieve the items from the cache by using a locale-dependent key. Obviously, since these assets are not plain JavaScript files but are php files that generate JavaScript, the whole process is not very straightforward...
Please remark that we could have also .css assets that could be locale-dependent.
For instance, we could have a localized background-image or a localized contentproperty.

Could you give me a little bit more information on how this might work? Like how it might look from the asset and in the outputted HTML?

First of all, as discussed in #2049, I'd move all the current (and future) language-dependent assets to routes.
Analyzing View::postProcessAssets(), JavascriptAsset::process() and CssAsset::process():

I'd change from

$filename = sha1($filename);

to
$filename = sha1(Localization::activeLocale().$filename);

so that we have a cached file for every locale. We could optionally do this change only for asset groups that contain at lease one asset with locale-dependent set to true.

If an asset has that locale-dependent property set to true, IMHO it's safe to assume that the asset URL is a route to a PHP method that generates the translated content (javascript/css code). So, instead of file_get_contents we could somehow call that method and catch the output (with something like output buffer).

That's an interesting idea. I think it could actually be pretty easy. You
could assume that the locale dependent JavaScript src were actually a
specific route. You could get it's contents by simply execute the default
route function and returning the content.
On Mon, Mar 16, 2015 at 4:19 AM, Michele Locati<EMAIL_ADDRESS>wrote:

First of all, as discussed in #2049
https://github.com/concrete5/concrete5-5.7.0/pull/2049, I'd move all
the current (and future) language-dependent assets to routes.
Analyzing View::postProcessAssets()
https://github.com/concrete5/concrete5-5.7.0/blob/5682a06cffe84318bbd9d43e3e796f6cca4ab07e/web/concrete/src/View/View.php#L205-L262,
JavascriptAsset::process()
https://github.com/concrete5/concrete5-5.7.0/blob/5682a06cffe84318bbd9d43e3e796f6cca4ab07e/web/concrete/src/Asset/JavascriptAsset.php#L58-L86
and CssAsset::process()
https://github.com/concrete5/concrete5-5.7.0/blob/5682a06cffe84318bbd9d43e3e796f6cca4ab07e/web/concrete/src/Asset/CssAsset.php#L131-L161
:

I'd change from

$filename = sha1($filename);
to
$filename = sha1(Localization::activeLocale().$filename);
so that we have a cached file for every locale. We could optionally do
this change only for asset groups that contain at lease one asset with
locale-dependent set to true.

If an asset has that locale-dependent property set to true, IMHO it's
safe to assume that the asset URL is a route to a PHP method that generates
the translated content (javascript/css code). So, instead of
file_get_contents we could somehow call that method and catch the output
(with something like output buffer).

—
Reply to this email directly or view it on GitHub
https://github.com/concrete5/concrete5-5.7.0/issues/2050#issuecomment-81588577
.

See #2076

Fixed in #2136


Modal "onClosed" handler doesn't called

components: Modal
reactstrap version #9.0.0
import method import {Modal, ModalBody, ModalFooter, ModalHeader} from "reactstrap";
react version #17.0.2
bootstrap version 5.1.3

What is happening?
onClosed handler doesn't called after modal closed. With onOpened all fine.
What should be happening?
onClosed handler called and print "onCLosed" in console.
Steps to reproduce issue

Open modal
Close modal and see console.

Code

          <Modal isOpen={shown}
                  toggle={toggle}
                  centered
                  onOpened={() => {
                     console.log('onOpened');
                  }}
                  onClosed={() => {
                      console.log('onClosed');
                  }}>

               ...

           </Modal>

I've tried it and everything is working as expected. You can check this example to ensure - https://codesandbox.io/s/nifty-lake-696i1


feat(otelcol/exporter/datadog) Add Datadog exporter wrapper

PR Description
This PR adds a wrapper around the Datadog Exporter from the opentelemetry-collector-contrib repo. It enables use of the Datadog exporter, which allows Alloy to send telemetry (metrics and traces at this point) to Datadog.
This is useful in migrating a Datadog setup towards a more OSS architecture. By allowing Alloy to talk to Datadog, Alloy can serve a new wedge of users using this proprietary platform and embrace OTel more.
Documentation and more tests need to be added, as well as more scrutiny; I intend on continuing work on this branch to address these over the next few days. This MR has dependency on #711 , hence the large diff 😅
Which issue(s) this PR fixes
Fixes #714
Notes to the Reviewer
PR Checklist

[ ] CHANGELOG.md updated
[ ] Documentation added
[ ] Tests updated
[ ] Config converters updated

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.7 out of 8 committers have signed the CLA.:white_check_mark: simonswine:white_check_mark: wildum:white_check_mark: jcreixell:white_check_mark: rfratto:white_check_mark: rlankfo:white_check_mark: clayton-cornell:white_check_mark: ptodev:x: polyrainYou have signed the CLA already but the status is still pending? Let us recheck it.

@wildum I've tested this locally and it works. I'll get onto some documentation tomorrow, but can you look over the code as it is now so I can get some feedback?

I've addressed the PR comments and rebased on main, testing locally seems to be working :+1: @wildum can I get another look?

I've triggered a rebase to pull in the newly added shared community notifcation.


The replacement of an unknown node with the correct one is not handled

Current Behavior
If I start Node-RED with a missing config-node type, the editor shows me the unknown type for that config-node. Normal so far.
If I import this same config-node with the correct type (which exists), and replace it, the editor seems to have done its job but when I deploy with Modified Nodes, I get the following error:
27 Jan 19:05:02 - [info] En attente d'enregistrement des types manquants :
27 Jan 19:05:02 - [info]  - database-config
27 Jan 19:05:02 - [info] Le serveur est disponible à l'adresse http://<IP_ADDRESS>:1880/
27 Jan 19:05:55 - [info] Arrêt des noeuds modifiés
27 Jan 19:05:55 - [info] Noeuds modifiés arrêtés
27 Jan 19:05:55 - [info] Flux mis à jour
27 Jan 19:06:08 - [info] Démarrage des noeuds modifiés
27 Jan 19:06:54 - [red] Uncaught Exception:
27 Jan 19:06:54 - [error] TypeError: Cannot read properties of undefined (reading 'update')
    at start (/usr/local/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/index.js:377:31)

If I look in the runtime, activeFlows is an empty object, so:
activeFlows['global'].update(activeFlowConfig,activeFlowConfig);

throws the error.
Note: I didn't notice this error with a full deploy but activeFlows is empty when setFlows is called.
I also notice that if I import directly the wrong config-node (without modifying the file) then replace it with the correct one and deploy, I have no problems.
But if I try with a node, the editor does not handle it: the editor shows me the unknown type for this node and when I import this node with the right type, I cannot replace it (even if I force it from the console).
Expected Behavior
Handle the replacement of an unknown node with the correct one.
Whether it's a node or a config-node.
Note: number of users in config-node is not updated after import.
Steps To Reproduce
For config-node:

Stop NR
Modify the flows.json file by changing the type of a config-node
Start NR
Import this node with it's original type
Replace it
Deploy with Modified Nodes

For node:

Stop NR
Modify the flows.json file by changing the type of a node
Start NR
Import this node with it's original type

Example flow
Add this fake mqtt-broker config-node to your flows.json file:
[
    {
        "id": "1deb012b34859b46",
        "type": "bad-mqtt-broker",
        "name": "Config Node Test",
        "broker": "localhost",
        "port": "1883",
        "clientid": "",
        "autoConnect": true,
        "usetls": false,
        "protocolVersion": "4",
        "keepalive": "60",
        "cleansession": true,
        "autoUnsubscribe": true,
        "birthTopic": "",
        "birthQos": "0",
        "birthRetain": "false",
        "birthPayload": "",
        "birthMsg": {},
        "closeTopic": "",
        "closeQos": "0",
        "closeRetain": "false",
        "closePayload": "",
        "closeMsg": {},
        "willTopic": "",
        "willQos": "0",
        "willRetain": "false",
        "willPayload": "",
        "willMsg": {},
        "userProps": "",
        "sessionExpiry": ""
    }
]

Now replace it with the correct one in the editor:
[
    {
        "id": "1deb012b34859b46",
        "type": "mqtt-broker",
        "name": "Config Node Test",
        "broker": "localhost",
        "port": "1883",
        "clientid": "",
        "autoConnect": true,
        "usetls": false,
        "protocolVersion": "4",
        "keepalive": "60",
        "cleansession": true,
        "autoUnsubscribe": true,
        "birthTopic": "",
        "birthQos": "0",
        "birthRetain": "false",
        "birthPayload": "",
        "birthMsg": {},
        "closeTopic": "",
        "closeQos": "0",
        "closeRetain": "false",
        "closePayload": "",
        "closeMsg": {},
        "willTopic": "",
        "willQos": "0",
        "willRetain": "false",
        "willPayload": "",
        "willMsg": {},
        "userProps": "",
        "sessionExpiry": ""
    }
]

Environment

Node-RED version: v3.1.3
Node.js version: v20.10.0
npm version: v10.2.3
Platform/OS: MacOS
Browser: Safari

I sometimes have this too when I uninstall and reinstall node packages that I'm developing in NR. The cause seems to be related to config nodes when redefining their type or removing them.
It's an edge case (for me) since it only happens when uninstalling/reinstalling node packages while developing the nodes. But it could also occur (perhaps) if a package developer redefines/removes a config node in a version and a user updates that package will cause NR to crash.

#4556 fixes the config node part of this.
The regular node issue is a restriction of the import dialog that only allows you to replace config nodes and subflows.


#17: toctoc testing helper module (closes #17)

Closes #17
In memory test double for supporting flow testing.
Test Plan
⚠ Untested code, use with care.

This implementation will help to write tests for the AuthenticationDomain core algebra.


Typo Visibility add in (component) readme file

The readme file for the release for ArcGIS Pro 1.4 contains a typo in the date.
Release Feburary 10, 2017:
Should be:
Release February 10, 2017:

Assigning to PEs to update this on the Download Items & Download site

@dfoll we should make sure to correct this when we release next

yes, i saw that and thought the same thing... unless management wants us to fix everything that is already out there, this is really something that just gets fixed at the very end

Fixed on \\disl\Development\Commercial\ReleaseStaging\June2017Release\Components\Visibility


Add version file for golangci-lint

I'm going to use this to variablize https://github.com/openshift/release/blob/252b8d0dc44ef61b55a20b5e151993c264bbffb3/ci-operator/config/openshift/managed-velero-operator/openshift-managed-velero-operator-master.yaml#L27

lgtm

/lgtm