text:
RQT Python plugin exception on signal receipt

System Information

ROS2 Humble on Ubuntu 22.04
Xorg
Python 3.10.4

Problem Description
All RQT Python plugins throw an exception on receipt of an interrupt signal (SIGINT).
rqt -v
...
^C[INFO] [1662392294.509266142] [rclcpp]: signal_handler(signum=2)
rclpy.shutdown() was called before QThread.quit()

sigint_handler()
MainWindow.closeEvent()
PluginManager.save_settings()
PluginManager.save_settings() completed
PluginManager.close_application() completed
Shutting down RosPyPluginProvider
Quit called on RclpySpinner
Traceback (most recent call last):
  File "/opt/ros/humble/local/lib/python3.10/dist-packages/qt_gui/plugin_manager.py", line 456, in close_application
    self._save_settings(
  File "/opt/ros/humble/local/lib/python3.10/dist-packages/qt_gui/plugin_manager.py", line 434, in _save_settings
    callback()
  File "/opt/ros/humble/local/lib/python3.10/dist-packages/qt_gui/plugin_manager.py", line 462, in _close_application_save_callback
    self._close_application_shutdown_plugins()
  File "/opt/ros/humble/local/lib/python3.10/dist-packages/qt_gui/plugin_manager.py", line 472, in _close_application_shutdown_plugins
    self._close_application_shutdown_callback()
  File "/opt/ros/humble/local/lib/python3.10/dist-packages/qt_gui/plugin_manager.py", line 480, in _close_application_shutdown_callback
    self._close_application_signal()
  File "/opt/ros/humble/local/lib/python3.10/dist-packages/qt_gui/plugin_manager.py", line 483, in _close_application_signal
    self._plugin_provider.shutdown()
  File "/opt/ros/humble/local/lib/python3.10/dist-packages/qt_gui/composite_plugin_provider.py", line 87, in shutdown
    plugin_provider.shutdown()
  File "/opt/ros/humble/local/lib/python3.10/dist-packages/qt_gui/composite_plugin_provider.py", line 87, in shutdown
    plugin_provider.shutdown()
  File "/opt/ros/humble/lib/python3.10/site-packages/rqt_gui_py/ros_py_plugin_provider.py", line 62, in shutdown
    self._destroy_node()
  File "/opt/ros/humble/lib/python3.10/site-packages/rqt_gui_py/ros_py_plugin_provider.py", line 89, in _destroy_node
    rclpy.shutdown()
  File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/__init__.py", line 126, in shutdown
    _shutdown(context=context)
  File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/utilities.py", line 58, in shutdown
    return context.shutdown()
  File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/context.py", line 102, in shutdown
    self.__context.shutdown()
rclpy._rclpy_pybind11.RCLError: failed to shutdown: rcl_shutdown already called on the given context, at ./src/rcl/init.c:241
Aborted (core dumped)

This behavior can not be reproduced on ROS2 Foxy, and seems to be a regression introduced in either Galactic or Humble.
Seemingly the code handling the RQT plugin calls rclpy.shutdown(), despite the fact that this function will also always be called later by RQT, where it then complains that the function has already been called.
rclpy.shutdown() was called before QThread.quit()
The above line also suggests that the order in which the node is torn down is incorrect when handling signals in respect to QT. Interestingly that warning isn't thrown when an RQT plugin is closed through its desktop window close button.
https://github.com/ros-visualization/rqt/blob/6cf57076b8501264497fd7355997335b3d05d511/rqt_gui_py/src/rqt_gui_py/ros_py_plugin_provider.py#L89
Removing this line prevents rclpy.shutdown() from being called twice and crashing, however it stills complains about being called before QThread.quit()

This only happens with Python and not C++ plugins, and only when the Python plugin is loaded in RQT. With RQT running and no plugin loaded, it responds to a SIGINT correctly.
However, RQT alone, or with either Python or C++ plugins loaded, will never respond to a SIGTERM, but will log it.
[INFO] [1662406460.729305639] [rclcpp]: signal_handler(signum=15)

I think it has already been fixed in #291.

Yes, you are right.  I'm going to go ahead and close this one out, thanks!

authors: ciandonovan clalancette ymd-stella

repo: ros-visualization/rqt


text:
Global Shutter (Time-synchronized global update of tf info etc.)

Currently, displays in RViz are asynchronous, which is the most straigtforward and general way.
In some applications, you might want a different behaviour, in that everything should be synced to a particular message, e.g. an image or a point cloud. This would be very useful in order to

check if timestamps and tf information of different subsystems align well (e.g. a camera image and the robot model)
go towards implementing #89
have a better visualization in teleoperation apps / interactive manipulation

This would however indicate API changes. The current definition of Display::update is virtual void update( float wall_dt, float ros_dt ). This would be changed to virtual void update( ros::Time time ). 'time' is either ros::Time(0), which would result in the exact same behaviour as the current RViz, or a particular timestamp. For backwards compatibility, the default implementation of this would call the legacy function definition and maybe print a one-time deprecation warning.
Next, inside a display you could call a function void emitTimestep( ros::Time ), which would emit a signal that is connected to the visualization manager, and can be used as global timestamp and trigger a call to the update function of all Displays.
In the RViz GUI, you would have a drop-down menu where you can select to either to run in asynchronous mode or to sync to one of the time-emitting displays (and maybe a pause button).
A question would be if that can be released into Groovy (would be nice, and also it's not exactly api-breaking).

I think this is actually part of the "experimental" time panel

source: gharchive/issue

repo: ros-visualization/rviz

license_type: permissive

license_source: bigquery


text:
Adding package meta-data to distribution.yaml?

Greetings,
I'm supporting an effort to update ROS on arch. The distribution.yaml is quite helpful, but I noticed a few things when trying to parse it for our package builds:

inconsistent data: some packages only have a release url, some have source, sometimes when both are missing, the doc url still points to git (which implies there is a source url)
sub-packages don't have xml entries: we link to the ROS wiki as the upstream URL in PKGBUILDs; because sub-packages (like tf2_eigen) don't have entries in the release_package_xmls, I'm not able to know their wiki directly. Currently I'm using a script which sees if https://wiki.ros.org/pkg_name exists
empty data: I'm using ET to find the wiki if it does exist:

wiki = ET.fromstring(xmls[pkg]).findall('url[@type="website"]')

Sometimes this returns a hit, but it turns out the tag is empty. The ff package is an example, and there is a ros wiki page for it...
<?xml version="1.0" ?><package><name>ff</name><version>2.1.12</version><description>ff: pddl planner. see http://www.loria.fr/~hoffmanj/ff.html</description><maintainer email="k-okada@jsk.t.u-tokyo.ac.jp">Kei Okada</maintainer><license>GPL</license><url type="website"/><author>J.Hoffmann</author><buildtool_depend>catkin</buildtool_depend><build_depend>mk</build_depend><build_depend>flex</build_depend><build_depend>bison</build_depend><build_depend>unzip</build_depend><build_depend>mk</build_depend><build_depend>rosbuild</build_depend><build_depend>rosbash</build_depend><build_depend>rospack</build_depend><build_depend>roslib</build_depend><build_depend>ca-certificates</build_depend><build_depend>openssl</build_depend><export/></package>

Maybe my use-case is kind of fringe, but in principle it would seem to advantageous to have this complete. Any guidance on filling in blanks, standardizing? Interest in tracking sub-packages (e.g. what the package parent is and the wiki page, if it exists)?

* inconsistent data: some packages only have a release url, some have source, sometimes when both are missing, the doc url still points to git (which implies there is a source url)

This is a feature; sometimes our contributors only want to do one part of the "release" process.  There are separate uses for the documentation, source, and release (binary), and some packages only want parts of it.  So I don't think that we really want to change the flexibility this gives the contributors.

* sub-packages don't have xml entries: we link to the ROS wiki as the upstream URL in PKGBUILDs; because sub-packages (like `tf2_eigen`) don't have entries in the `release_package_xmls`, I'm not able to know their wiki directly. Currently I'm using a script which sees if `https://wiki.ros.org/pkg_name` exists

Sorry, can you point more directly where you are fetching the release_package_xmls from?

* empty data: I'm using ET to find the wiki if it does exist:

Sometimes this returns a hit, but it turns out the tag is empty. The ff package is an example, and there is a ros wiki page for it...

Oh, I see.  This is a case of the contributor not adding in a <url> tag to their package.xml.  In principle, I agree that all packages should have this, but I also don't think we should really enforce it at the rosdistro level.  My suggestion for these packages is to submit a PR to their upstream repository adding the <url> tag.

Interest in tracking sub-packages (e.g. what the package parent is and the wiki page, if it exists)?

Tracking the sub-packages back to the parent is a nice thing.  I would think it would be possible, since our buildfarm/infrastructure code has to do this.  @nuclearsandwich might have some tips on how to achieve this.

Thanks for the reply.

This is a feature; sometimes our contributors only want to do one part of the "release" process.

I might now know what all these get used for, but it seems kind of arbitrary? Take bagger as an example. What benefit is there in not listing source, or more particularly listing that page for at least the doc url? I think the wiki might rely on some of this, so you get ghost pages as a result. This isn't helpful, in my opinion.

can you point more directly where you are fetching the release_package_xmls from?

Whoops! I actually go that from here: http://repositories.ros.org/rosdistro_cache/ (I pulled melodic), which looks to contain distribution.yaml, but indeed has what looks like extracted package.xml data.

I also don't think we should really enforce it at the rosdistro level.

Good point... I assumed this was maintained, but stupidly should have read contributing.md... now I see the community generates this. Since my script is trying various ways to get the url (is it in the wiki page in the xml data? is there a doc site? does the wiki exist?), I could compile the list of packages that are missing.

Tracking the sub-packages back to the parent is a nice thing.

I'd be happy to help with that as well. My solutions is certainly low-tech. Do you mean you already have a master index of wiki pages or similar? That's where I ran into trouble. Even with some time.sleep() delays, I ran into surge protection checking for package pages...
Thanks for the dialog!

Followup: I now have the list of wiki pages for sub-packages, assuming the pkg_name matched up directly with wiki.ros.org/pck_name. This was manually scraped and takes some time to not overload the wiki. If there is a better way to get this data, or you have existing code and would like help implementing a more granular listing, I'm game to help!
In addition, I can create a list of missing data for reference and suggest to upstream folks that they add this info to their listings.

In general there should be a wiki page for each package name. The wiki pages are not autogenerated but require the maintainer to create them so we don't end up spamming the wiki.
You'll find that our new site https://index.ros.org does automatically create content for anything indexed. eg search for ff
You're right that it's much more helpful for maintainers to submit doc and source entries. But there are cases when it's not appropriate. Doc is not useful if the repository cannot be crawled by our documentation engine. And sometimes the source is not hosted in a format that we support indexing. So we cannot require them. If there are packages which you'd like to see have more content listed please file a ticket with the upstream package to get the attention of the maintainer.

Tracking the sub-packages back to the parent is a nice thing.

I'd be happy to help with that as well. My solutions is certainly low-tech. Do you mean you already have a master index of wiki pages or similar? That's where I ran into trouble. Even with some time.sleep() delays, I ran into surge protection checking for package pages...

Assuming you're referrring to packages and repositories, (instead of subpackages and packages) index.ros.org already has the associations between those documented.
If a website url is not declared the wiki page is what we use as the default. It's ok to create a link to it even if it doesn't exist. If someone creates it and there is a documentation job when it's created the header will be populated.

You'll find that our new site https://index.ros.org does automatically create content for anything indexed. eg search for ff

I have seen that and assumed it was based on distribution.yaml, risdistro cache, or similar, or that both distribution.yam, and index.ros.org are based on the same thing.

wiki pages are still missing for some (like ff even thought it exists)
index.ros.org indeed tracks parent/child (or repo/packages), but so does distribution.yaml, but it doesn't seem to track child wiki pages, e.g. tf2_eigen.

This was initially just a neurotic inquiry as I'm helping update the ROS packages for arch linux. We list a url per package in our PKGBUILD (example), and while we were migrating to ROS sources (vs. ros-gbp), I figured I'd update them. That's when I found there appears to be no master list, and many packages listing links.
I think part of the problem is that from an outsider view, I can't tell the difference between accidentally missing (like ff having an empty website tag in the distro_cache) and any of the cases you mention above where some link doesn't make sense.
I don't know what other uses having such an index has, but given that I've now built it, it would seem there is no downside in adding that data where possible? Again, happy to help, and I would think it's in everyone's best interest to have these wiki pages listed in various places if they exist...
What if I use the github api to post an issue suggesting a review of the distribution.yaml entry for any packages who had errors? This wouldn't seem to correct the pacakges issue (e.g. tf2_eigen), would it? That would seem to require a new structure and intentionally adding those wiki pages somewhere to the index.

index.ros.org indeed tracks parent/child (or repo/packages), but so does distribution.yaml, but it doesn't seem to track child wiki pages, e.g. tf2_eigen.

I don't understand this there's a link at the right to the wiki page.

What if I use the github api to post an issue suggesting a review of the distribution.yaml entry for any packages who had errors?

Can you explain this a little more? Opening a mass of tickets is not going to be helpful. Opening PRs that fix things could be.

This wouldn't seem to correct the pacakges issue (e.g. tf2_eigen), would it? That would seem to require a new structure and intentionally adding those wiki pages somewhere to the index.

What do you consider wrong with tf2_eigen that needs fixing and could be ticketed? Actually to that matter, what do you want to fix with ff. I see the wiki page has been there since 2015: http://wiki.ros.org/action/info/ff?action=info but you said it's missing above.

I don't understand this there's a link at the right to the wiki page.

Hmm. Consider me losing my mind. I swear I looked upon the last reply and saw no website link. Now I do. What originally got me on ff specifically was the package xml in the distro cache (posted above):
<?xml version="1.0" ?><package><name>ff</name><version>2.1.12</version>
...
<url type="website"/>

Opening a mass of tickets is not going to be helpful. Opening PRs that fix things could be.

Agreed.

What do you consider wrong with tf2_eigen that needs fixing and could be ticketed?

I actually did not see the wiki link on any packages until you pointed it out, and I thought links to a website, wiki, sources, etc. would live in the main info section.

Taking a step back, let me restate how we got here:

I'm trying to help maintain ROS packages for arch linux
to do this, we're updating our build files
to do that, I need to know all the packages, their sources, and their repos
I found this repo, which I believed would contain that
in parsing the file and the rosdistro_cache, I found things I believed to be missing
I'm here asking how I can help

I feel friction in asking to do this, so perhaps we should just keep it simple:

what data source is ros index based on? (if that's the gold standard, I could use that for my aim)
same question for distribution.yaml and rosdistro_cache
are all those data sources in agreement with each other? (I believe at least the cache and index do not, based on the missing ff url tag)
if not, do you care?
if so, would you like any help aligning them?

With some slight generalizations this is how the indexing works.
Everything starts with the rosdistro. The distribution.yaml lists all the indexed repositories. To find all the packages you go to those repositories and browse for package.xml files. All data for any given package is pulled from the package.xml. It's expensive to do this walk, so to save most people the cost there's a caching mechanism the rosdistro cache where we store the results of the walk.
This information feeds the wiki, this information feeds the rosindex etc.
In general there's no duplication of the data except for several layers of caching which can cause temporary inconsistencies, but that's not what you're seeing. You mention that it doesn't seem that all the "sources" are in agreement. However they all are derived from the same source and appear to be in agreement, accurately reproducing the invalid url.
I definitely do care about the data being correct, but I'm mostly resisting your suggestions about adding or extending the data in the rosdistro which will make things more complicated and cause data redundancy that then could then become inconsistent. In general we rely on the maintainers to keep their package.xml up to date. Looking closer at ff itself, I now see that it's not a missing tag, but an empty tag in ff.  And that's an obvious bug with the package and should be ticketed as such on the upstream repository. Once that's updated there it will propagate to all the different places you're seeing like the rosdistro cache, and then the wiki and index.
I'm generally glossing over a lot of details about the exact mechanisms and different paths for different build types, and different paths for different versions. But the main point is that the primary source for all of this information is from the upstream repositories. If there's data that's missing or inaccurate tickets should be opened on the upstream repositories for the attention of the maintainers. If you'd like to suggest better ways to render or display things that are collected by the rosdistro indexing I can point you to the relevant repositories to make suggestions. (Such as the wiki or rosindex )
You mention that you don't know if the omissions are purposeful or intentional, and I don't either for any given package. It's a federated community and we delegate that judgement to the package maintainers.
You are right that the rosdistro is your source as the authority for finding the list of packages. I think you'll find that basically everything you need for generating every ROS package is available from the rosdistro library and the rosdep database(also in the rosdistro repo). We generate debian packages, ubuntu packages, fedora packages automatically with bloom and have support for Gentoo and OpenEmbedded using superflore. With those tools you should be able to extend the functionality to generate Arch packages fully automatically as well.
These are also the tools that use the wiki page by default unless the optional website url is set as the package "Homepage" in the debian parlance. in the future we will likely switch that over to use rosindex as the default. The packages that have explicitly declared the default website url will likely need to all be touched. And if you look around you can find ones that are still using our deprecated wiki urls like bond core and they're already out of date. This is why we like to use default values and not type it out every time in all the packages. But if the maintainer wants they can declare a non-standard website like frame_editor and we add that in parallel since as this example shows the wiki link is still more useful.

With those tools you should be able to extend the functionality to generate Arch packages fully automatically as well.

Work has also been done in the past to support adding an Archlinux generator to Bloom and work is ongoing to reduce the friction and maintenance burden of supporting additional generators with the hope that Superflore's separate generators are someday merged into Bloom so that Superflore uses Bloom under the hood.

@tfoote Thanks for the in-depth explanation! Forgive the delay. I had some vacation, house work, and also just ran out of time to work on this for a bit. I appreciate the understanding of package details as well as the mention of bloom and superflore, which are definitely of interest re. building arch binaries.
I asked that they add a website to ff (which will likely point to the ROS wiki from looking at their other package.xml files).
Re. bloom and superflore, I'll have to look into these more and they seem above my head at the moment. Bloom tells me how to add a package (which presumably builds for supported ROS distros), but I think what we need is that existing packages be build for arch, specifically.
superflore looks like the equivalent of an AUR package manager, namely "grab all the required source files for packages x, y, and z, then build and install them on my system." If so, I think that's basically what arch users already do. I think we're hung up on finding a build farm to do this (and then creating the infrastructure/config required for arch). I'm just helping out the lead of this effort who sounds to have more experience on that front.
Thanks again!

authors: clalancette jwhendy nuclearsandwich tfoote

repo: ros/rosdistro

license_source: github-api


text:
Added software-properties-common to rosdep

Added software-properties-common key for micro-ROS project

Ubuntu: https://packages.ubuntu.com/search?suite=all&section=all&arch=any&keywords=software-properties-common&searchon=names
Debian: https://packages.debian.org/search?searchon=names&keywords=software-properties-common

In the context of micro-ROS we need software-properties-common in order to install the last CMake version (3.13.1 or higher), which is not available by default on Debian/Ubuntu and it is needed by the Zephyr RTOS toolchain:
https://docs.zephyrproject.org/latest/getting_started/index.html#install-dependencies
Here you have the Zephyr + micro-ROS build system:
https://github.com/micro-ROS/micro-ros-build/tree/feature/zephyr/micro_ros_setup

I agree with @clalancette that this isn't really a great "dependency" for a software package. This is really an installation prerequisite. And although we don't want to be judging the usefulness of packages that we add to the rosdep rules we can add the rule. It would be reasonable to make a package that has the scripts to help setup the environment. So I don't think that we should block this.
Circling back though, I would strongly suggest that the use of this tool is less generic than just piping the contents to the file like most installation instructions do. Ala: http://wiki.ros.org/kinetic/Installation/Ubuntu
The command has a lot of dependencies for doing something that's one line of bash and is the same level of complexity as the previous line of the installation above in the installation tutorials for the keys. As such it is only adding complexity not reducing it. Thus I'd ask do you really need this for this use case when
sudo sh -c 'echo "deb https://apt.kitware.com/ubuntu/ bionic main" > /etc/apt/sources.list.d/kitware.list'

Ok undestood, thanks!

source: gharchive/pull-request


text:
realsense2_camera: 2.2.22-1 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository realsense2_camera to 2.2.22-1:

upstream repository: https://github.com/IntelRealSense/realsense-ros.git
release repository: https://github.com/IntelRealSense/realsense-ros-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.10.1
previous version for package: 2.2.21-1

realsense2_camera
* Add reset service.
* fix timestamp domain issues
  - Add offset to ros_time only if device uses hardware-clock. Otherwise use device time - either system_time or global_time.
  - Warn of a hardware timestamp possible loop.
* Choose the default profile in case of an invalid request.
* Avoid aligning confidence image.
* Add an option for an Ordered PointCloud.
* Contributors: Isaac I.Y. Saito, Itamar Eliakim, Marc Alban, doronhi

realsense2_description
* Fix mass of d415
* Consistent add_plug in xacros and launch files
* Contributors: Manuel Stahl, Tim Übelhör, doronhi

Depends on #28341


text:
gscam: 2.0.0-1 in 'galactic/distribution.yaml' [bloom]

Increasing version of package(s) in repository gscam to 2.0.0-1:

upstream repository: https://github.com/ros-drivers/gscam.git
release repository: https://github.com/ros2-gbp/gscam-release.git
distro file: galactic/distribution.yaml
bloom version: 0.10.7
previous version for package: null

gscam
* fix: fix test dependency in package.xml
* Add note on testing and examples
* Update README
* chore: fix for uncrustify
* fix: fix smoke test
* chore: fix copyright
* chore: fix flake8
* chore: fix pep257
* chore: fix lint_cmake
* chore: fix cpplint
* chore: change license
* chore: apply uncrustify
* chore: add linter dependencies
* chore: simplify parameter declaration
* adding explicit parameter types to string parameters
* Add smoke test
* Break deadlock for a clean exit
* fix: fix legacy group namespace
* chore: install examples directory
* fix: fix launch extension
* fix: fix launch executable name
* feat: create node exe from rclcpp components
* Update README
* Remove extra files, rename .h to .hpp
* Configure once, avoids re-declaring parameters
* Port launch files to ros2
* Remove support for gstreamer-0.10
* Use Github Actions and ros-tooling for CI
* Remove deprecation warnings, clean up includes
* Fixed crash in GStreamer 1.16.2, works on Foxy
* Minimal ROS2 port, works in Eloquent
* Contributors: Clyde McQueen, Jonathan Bohren, wep21

FYI @jbohren @clydemcqueen


text:
Docs Fail to Generate on Docs.rs

https://docs.rs/crate/rclrs/0.3.1

From checking the build log its obvious they failed because no ROS_DISTRO was installed, but I think it should be possible to work around this with feature flags and get documentation to generate without needed ROS.
Docs.rs is pretty central in the Rust community so would be good to support.

That's a really good idea. From what I gathered, if we add a feature flag that avoid dependening on ROS_DISTRO and add it to [package.metadata.docs.rs] (https://docs.rs/about/metadata), we could make it work, right? What do you think @Carter12s ?

Yup that is exactly what I was thinking. I'm not sure how extensive that feature flag is going to need to be and unfortunately there isn't a great way to test other than releasing versions and seeing if doc.rs picks them up.
When I was getting this figured out for roslibrust I had to release and then yank several versions just to test if docs.rs would parse them correctly.

Hmmm, it could be tricky, because we depend on bindgen for a significant part of the API, which depends on having a ROS distro installed. Anyway, I'm sure we can figure out a way.


text:
Fix basic request reply mapping for ConnextDDS Pro

There are two fixes:

one conversion from int64 to SequenceNumber_t was wrong.
If basic request reply mapping is used with ConnextDDS Pro (e.g. in order to interact with ConnextDDS Micro), the old version overwrites the sequence number passed out to RCL. This makes it impossible for the client libraries to associate any response with its corresponding request.

Re-running CI to validate Windows failure (running Linux again as a baseline):

Linux:
Windows:

This PR seems to be ready to merge, right?

@cwecht
CC: @asorbini
this has been merged, thanks for the contribution.

authors: asorbini cwecht fujitatomoya


text:
Throttle controlled by companion computer when in Manual mode

MAV type: fixedwing
With the auto/manual switch in the manual position, the companion computer was still able to control the throttle.

The attitude and throttle overrides can be mapped to different switches by setting the RC_ATT_OVRD_CHN and RC_THR_OVRD_CHN parameters. The first thing to check is if your parameter configuration has these set to different channels, and if so set them to the same channel to get the behavior you want. If they were set to different channels and you were still seeing this behavior, then this is a bug.
For reference, this is documented here, and referenced here. If we can improve the documentation to make this more obvious, that would be great too.

I am just following up on this.  Was this actually the issue with the switch being twisted upside down?  @BillThePlatypus

Yes, it was

So this was an issue with the actual transmitter hardware, not the firmware. Can we close this issue then?

Yes, that would be fine
On Nov 8, 2018 5:31 PM, "Daniel Koch" notifications@github.com wrote:
So this was an issue with the actual transmitter hardware, not the
firmware. Can we close this issue then?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rosflight/firmware/issues/312#issuecomment-437207032,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbpJ-ThuScjNE9tjLBkgIjvxjyqbCvXNks5utMz6gaJpZM4XkWtF
.

authors: BillThePlatypus dpkoch drinkdhmo superjax

repo: rosflight/firmware


text:
ارور هنگام استفاده از «استخراج کلمات کلیدی»

سلام، من از نسخه 0.10.0 هضم و 3.11.4 پایتون روی Ubuntu 23.04 استفاده میکنم
هنگامی که میخواستم از این لینک، از کد استخراج کلمات کلیدی استفاده کنم، در قسمت from hazm.Embedding import SentEmbedding به این ارور خوردم:
>>> from hazm.Embedding import SentEmbedding
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'hazm.Embedding'

با این که هنگام نصب هضم به هیچ مشکلی بر نخوردم و تمام ماژول های دیگر را نیز نصب کردم، به این ارور خوردم

سلام
حرف اول به اشتباه داخل مستندا بزرگ نوشته شده. این‌طور بنویسید:
from hazm.embedding import SentEmbedding
لطفا این بخش رو در مستندات اصلاح کنید. @sir-kokabi

سلام، من از نسخه 0.10.0 هضم و 3.11.4 پایتون روی Ubuntu 23.04 استفاده میکنم هنگامی که میخواستم از این لینک، از کد استخراج کلمات کلیدی استفاده کنم، در قسمت from hazm.Embedding import SentEmbedding به این ارور خوردم:
>>> from hazm.Embedding import SentEmbedding
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'hazm.Embedding'

با این که هنگام نصب هضم به هیچ مشکلی بر نخوردم و تمام ماژول های دیگر را نیز نصب کردم، به این ارور خوردم

repo: roshan-research/hazm

license: MIT


text:
Can I generated from latents that moved along 19th eigenvector with size/degree +-5 for appoint samples

Can I generated from latents that moved along 19th eigenvector with size/degree +-5 for appoint samples

Input an image and use closed form factorization to output the potential generation of this image

如何得到具体一张图片的 latent

Sorry, I didn't see it projector.py

Project image into latent spaces (there are many methods for it) and use eigenvectors.

@rosinality
All of these methods need to train the model, right？For example, this project projector.py


text:
Add pre-commit hooks for code style

I think that it's a good idea to have pre-commit hooks which will check code style.
Of course, we must add information about it to README.

I know about useless of pre-commit hook from my experience. It is much smarter to use pre-push. So you may commit with errors, but not push with errors.

authors: Piterden lk-geimfari

repo: roskomsvoboda/censortracker


text:
Update 100_Numpy_exercises_with_hints.md

np.show_config() is a function, can create confusion, so updated it

Thanks. Can you update the exercises100.ktx instead of the md file (that is generated from the ktx file)?

Thanks. Can you update the exercises100.ktx instead of the md file (that is generated from the ktx file)?

authors: hackerpain rougier


text:
chore: release main

:robot: I have created a release beep boop
node-versions: 1.0.4
1.0.4 (2024-08-23)
Bug Fixes

update available Node.js versions (8254a5b)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

node-versions-v1.0.4
:sunflower:

repo: rowanmanning/repo-tools


text:
Add an rp2040 specific #[entry] macro.

This macro extends the one from cortex-m-rt by code to unlock all spinlocks on boot.
I wonder if this should be part of the HAL, or if it belongs to rp2040-pac.
Closes #292

One thing that might be nice is to be able to call the spinlock init (and any future required init if this gets extended) from outside a macro context.  Mostly I'm looking at RTIC, which does it own codegen for main, so it'd be nice to have an easy way to call whatever the HAL needs to init easily from there.
That might be out of scope for this, though, since it's probably safe to assume that if you're not using cortex-m-rt you can figure out what needs to be done.

Is this still in draft due to that question?

Not only because of that question. I just wasn't sure if this was a good approach in general, and wanted to wait for some feedback.
Now that there have been a few reviews, I'm confident that I didn't propose something stupid.
I rebased the PR because there were conflicts with changes on main.

authors: Sizurka jannic

repo: rp-rs/rp-hal


text:
🛑 Jay Industries is down

In 7fcea2c, Jay Industries (https://jaybrassindustries.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jay Industries is back up in 4077b90 after 6 minutes.

repo: rpharaniya/websites-uptime-monitor


text:
#195 Dispatcher::dispatch: check whether "this._items" exist before access "this._items.length"

Fix for https://github.com/rpominov/kefir/issues/195

Closing it because of https://github.com/rpominov/kefir/issues/195#issuecomment-212432472.

repo: rpominov/kefir

license: mit


text:
Update Contributing.md

Hi! I would like to add few things in contributing.md apart from the one mentioned

Squash commits of an issue under a single commit
Update your forked and local repo as and when changes are made in the upstream

Hi @khareyash05, There is no need of first point. I can squash and commit while merging a PR if it is needed. You can add second point.

Can I also contribute to this?

If this is still open I would like to contribute to this issue under GSSoc'21. Can you assign it to me?

Sorry @soumik2012 @anushree71199  I have already finished it and just waiting for merging

Thank You!
@rpotter12 Could you please add a level label to the same as under the GSSOC guidelines? As easy labels aren't being evaluated in GSSOC


text:
[Question]: Visual Studio challenges

Team - Anyone else facing issues with Visual Studio when you this package ?

When we load this project we see this notification.
if we accept net4.8 Visual studio adds a bunch of sqlproj files any insights on this
do we need to still do this ? https://github.com/rr-wfm/MSBuild.Sdk.SqlProj/issues/41

Here are some example files what visual studio adds

That is not a.project related to this SDK. This project type targets .netstandard 2.0 - and you are not sharing any info about the project.

To leverage Visual Studio publish ability do we need to have a side loaded project with a sqlproj ?

Yes, or you can use "dotnet publish" for inner loop or sqlpackage

authors: ErikEJ bheemvennapureddy


text:
Duplicate word

line 93, 94
The sentence "sera recalculé." is written twise
"sera recalculé." est écrit deux fois
Merci pour le super doc
Thank you

Thanks :)

authors: MoezAyadiDev rrousselGit

repo: rrousselGit/riverpod


text:
http://www.deftserver.org/ seems down

The address http://www.deftserver.org/ is not working for me, yet linked in the README.

Closing due to no activity.

repo: rschildmeijer/deft


text:
Using Minimum Risk Training (MRT)

Hi Rico,
We are trying to use the MRT feature of Nematus but somehow unable to train it properly. PFA the attached configuration of the model. Please suggest if any issue in the configuration.
config.py.txt
The trained model is not even able to translate properly (translation output is "." only ).

Hello Raj,
the recommended way to use MRT is to first train a model with
cross-entropy loss, and when this has converged, continue training with
MRT. So far, our experience with MRT has been mixed, and we welcome more
empirical data on good hyperparameters (so far, SGD with small learning
rates seems the most robust) and effectiveness on different datasets.
best wishes,
Rico
On 30/05/17 07:40, Raj Nath Patel wrote:

Hi Rico,
We are trying to use the MRT feature of Nematus but somehow unable to
train it properly. PFA the attached configuration of the model. Please
suggest if any issue in the configuration.
config.py.txt
https://github.com/rsennrich/nematus/files/1037429/config.py.txt
The trained model is not even able to translate properly (translation
output is "." only ).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rsennrich/nematus/issues/40, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYry48joHpmgVu5Yz7sLjOscxY2MZ7lks5r-7nkgaJpZM4Np4b6.

authors: patelrajnath rsennrich

repo: rsennrich/nematus


text:
Worlds and Universes: MPI_FINALIZE

The Universe type calls MPI_FINALIZE() upon being dropped, but it is possible to hold a universe.world() after dropping a Universe and the internode communications methods are impl'd on the world. This is a problem.
I recently wrote a program that dropped a universe (unintentionally) and then tried to used the world but ran into issues since MPI_FINALIZE had been called. I wonder if it is possible to enforce that a universe outlive world through the lifetime system by, for example, requiring that world hold some reference to a dummy field on a universe.

Another solution would be to have some unit struct type Finalize which is held in an Arc<T> and held by the Universe and SystemCommunicator::world(). You could have the special Drop impl for Finalize which calls MPI_FINALIZE. Then, the final drop of Arc<Finalize> would call this whether it is Universe or the SystemCommunicator::world().

MPI doesn't have a concept of a universe as an object, and even the size (MPI_UNIVERSE_SIZE) is just an optional attribute (need not be present) on MPI_COMM_WORLD. I think we should handle this with PhantomData lifetimes so that communicators can't outlive the universe. Could you make a pull request that adds a reproducer in which your communicator outlives universe (and thus errors)?

Yea I’ll submit one later this week. I have a busy schedule these next three days.

Cool. There's also relevant discussion in #32.

Are there any updates on this?

authors: SolidTux cavemanloverboy jedbrown

repo: rsmpi/rsmpi


text:
Passing setup parameters to RSocketClient

this allows client application code to pass setup parameters to the RSocketClient as well as other parameters. All of them have a default value so the client doesn't have to specify them.

merging to unblock myself in another PR. Still interested in feedback.

repo: rsocket/rsocket-cpp


text:
QUIC transport reconnect support

Current QUIC trnasport doesn't work with reconnection flow.
Expected Behavior
Ability to reconnect rsocket with quic transport
Actual Behavior
reconnection request doesn't reach the rsocket flow.
Steps to Reproduce
add reconnect to client_quic.py and server_quic.py and close server_quic after a while

done

repo: rsocket/rsocket-py


text:
add example on how to use raise_error with block

I had to do some digging on google to find that, having on the official docs might help some people :)

Thank you! It's a very useful feature for those who use advanced exception features.

authors: glaucocustodio pirj

repo: rspec/rspec-expectations


text:
ESPSomfy-RTS losing track of blind if "Step Up" is sent after "Down" or "Step Down" after "Up"

Hardware
Olimex ESP32-PoE/EVB
Firmware version
v2.3.3
Application version
v2.3.3
What happened? What did you expect to happen?
I have a Somfy blind with tilt. If I send (from the virtual remote or from HA) a "Down" command followed by "Step Up", the blind stops, but the ESPSomfy-RTS thinks that it continues travelling down all the way to fully closed. The same happens when sending an "Up" command followd by "Step Down". The blind stops, but ESPSomfy reports that it keeps moving all the way to fully open.
How to reproduce it (step by step)
1. Press Down on the virtual remote
2. Press "Step Up" on the virtual remote

or

1. Press Up on the virtual remote
2. Press "Step Down" on the virtual remote

Logs
No response

Do you have this set to 80 bits?

Do you have this set to 80 bits?

Yes. The same thing happens if I set it to 56 bit (tested that as well now).

The same thing happens if I set it to 56 bit (tested that as well now).

Sorry, incorrect. If I change the settings for the blind to 56 bits, the "StepUp" and "StepDown" commands have no effect.

It needs to be set to 80 bits for the step up/down to work.  I do not have a blind with this capability.  So it sending a step command stops all movement if the blind is in motion?

@011V32 has this been your experience with this as well?  Just checking to see if there are differences with functionality on the motors.

Could it ever make sense that the movement continues after a step command?
The tracking of the movement is correct if the step command is in the same direction as the preceding Up/Down command. In that case ESPSomfy-RTS correctly understands that the movement has stopped.

Does it track correctly if you are using a tilt wheel on a remote?  Is this only when using the virtual remote?

Install the v2.4.0 pre-release and see if the issue is solved for you.

Does it track correctly if you are using a tilt wheel on a remote? Is this only when using the virtual remote?

It is the same behaviour with the physical remote with tilt wheel, with the virtual remote, and when controlled from HA.

Install the v2.4.0 pre-release and see if the issue is solved for you.

Yes, seems completely solved now! Thanks for this - and especially for turning it around so quickly!

@011V32 has this been your experience with this as well? Just checking to see if there are differences with functionality on the motors.

I've never tested this case because I would always end it with a Stop/My command...
I'm still traveling at the moment and couldn't test it until the evening, if that's still relevant?

authors: 011V32 perfrankling rstrouse

repo: rstrouse/ESPSomfy-RTS

license: Unlicense


text:
Workbench for GCW session calls intermittently return 405 Method Not Found errors

Recently @jthomasmock noticed that calls to retrieve, create, or modify sessions in RStudio on Workbench for GCW were returning 405 Method Not Found errors. After further investigation, we found multiple calls similar to the following in rserver.log:
2023-07-07T15:36:00.089430Z [rserver] ERROR Invalid method OST requested for uri: /events/get_events; LOGGED FROM: bool rstudio::core::http::AsyncServerImpl<ProtocolType>::onHeadersParsed(rstudio_boost::shared_ptr<rstudio::core::http::AsyncConnectionImpl<typename ProtocolType::socket> >, rstudio::core::http::Request*) [with ProtocolType = rstudio_boost::asio::local::stream_protocol  typename ProtocolType::socket = rstudio_boost::asio::basic_stream_socket<rstudio_boost::asio::local::stream_protocol>] src/cpp/server/ServerInitLocalStream.cpp:466

For some reason, requests reaching Workbench are partially cut off, yielding calls to methods such as OST, ET, or ST. Since these are not valid methods, the server does as expected and returns 405 Method Not Found errors.
We are unsure why client requests are being cut off as they are sent correctly from the client, but sometimes reach the Workbench server as fragments. This issue has been escalated to Google to further investigate the Workstation intermediary networking and servers for a cause.

There is more troubleshooting we can do on our side to ensure that the issue is with Google's upstream proxy, but their development team said they were looking into this.
If they don't get back with us soon and do not respond, we should look into running tshark within the development container to ensure that the incoming traffic is truncated - if it isn't, that would imply a Workbench issue.

This was identified as a bug on the Google side and they report to have rolled out a fix last week. We need to verify the fix and then we can close the issue.

authors: blairj09 ianpittwood kfeinauer

repo: rstudio/rstudio-docker-products


text:
Support ROS 2 Foxy

What does this implement/fix?

ROS 2 Foxyに対応させるPRです。

ros2_wsやfoxy-develのようなブランチにマージしたいです
CMakeLists.txt

ROS 2用に書き換えています

launch/config/urdf.rviz

rviz2を起動した際のコンフィグファイルで上書き保存してます

launch/display_urdf.launch, launch/display_xacro.launch

ROS 2で動作しないため削除しました

launch/display_xacro.launch.py

※display.launch.pyに改名します
model、rvizconfig、guiの引数は需要が無さそうなので削除しました
lidar引数は追加します

package.xml

ROS 2用に書き換えています

urdf/raspimouse.urdf

urdfとxacroの両方あるとユーザが混乱するので、urdfファイルを削除します

Does this close any currently open issues?

いいえ
How has this been tested?

Ubuntu 20.04 & ROS 2 Foxy環境で下記の項目を確認しました。

display.launchでrviz上にモデルを表示できる
gazebo上でモデルを表示できる

Any other comments?

ros2_controlに対応させる場合、xacroプラグインの書き換えが必要です。
別PRで対応します。
その際、raspimosue_simの方も修正します。
Checklists

[x]  I have read the CONTRIBUTING guidelines.
[x]  I have checked to ensure there aren't other open Pull Requests for the same change.

ROS 2のメインブランチ名について
以下のリポジトリではros2ブランチが使われているようです。

https://github.com/ros/xacro
https://github.com/ros/robot_state_publisher

以下のリポジトリではros2-develとros2（対応するROS 1のブランチはdevelopとmaster）が使われているようです。

https://github.com/ROBOTIS-GIT/turtlebot3_simulations

ros2ブランチにしましょうか。

mkdir -p ~/ros/foxy/src
cd ~/ros/foxy/src
git clone -b support_ros2 https://github.com/rt-net/raspimouse_description
cd ~/ros/foxy
colcon build --symlink-install
# URGなし
ros2 launch raspimouse_description display.launch.py
# URGあり
ros2 launch raspimouse_description display.launch.py lidar:=urg

動作確認しました

authors: ShotaAk Tiryoh


text:
android permission

some devices refused permission by user, PermissionsAndroid.request always return 'granted'.in fact ,it is denied.

This issue was reported in an application I am working on as well.  On Android, whether the permission was granted or not, it always comes back as PermissionsAndroid.RESULTS.GRANTED.
react-native-contacts@2.2.0

@jmfirth not sure either, maybe resolve the conflicts and try out the PR


text:
Fix #317: Add styling to block quotes

Before:

After:

Take note of the comment in the code:
  // For the most part, its safe to assume that sphinx wants you to use a blockquote as an indent. It gets
  // used in many different ways, so don't assume you can apply some fancy style, just leave it be.

Looking at our demo files the only effects it has is on block quotes and line blocks. I can make it only apply to block quotes. AFAIK this currently would cause issues on my website but would like to get some feedback on this.

My personal preference would be to not add the styling to line blocks

13°48 39.3"N  100°29"48.7

eqnyte connect pong22077file Serve your trial ended please subseribe online or call us at 1.877.734.6983

There may be cases where blockquote is used for layout purposes, e.g. sphinxcontrib-httpdomain. This is of course a wrong use of blockquote, but it demonstrates that changing the rendering may have unintended side effects in specific cases.
I like the look though.

authors: Apus21 Blendify jessetan


text:
Fixes, add polling to svelte example

Alright, clean diff from the original one from yesterday. I'll see if I get a little time to fix this later.
If you just check the example, you'll see some fun behavior happen with the polls and subscriptions that sit in state :) (will remove this if i get to fix it)

Closing as it's wrapped into #16

repo: rtk-incubator/simple-query


text:
Keywords for network statistics and metrics

In particular, performance timings of content/file downloads, uploads, etc. along with viewing HTTP headers sent/received in browser.
Selenium RC had a captureNetworkTraffic option on startup of browser session to enable such functionality, though the user of course had to manually parse the desired data (or look for third party Selenium tools that did that).
WebDriver unfortunately doesn't natively support this, so just opening up a tracking issue for discussion and consideration of adding such functionality perhaps with third party tools.
See following for references:
Matching SeleniumLibrary issue 206
http://code.google.com/p/robotframework-seleniumlibrary/issues/detail?id=206
Request for such functionality at RF user group
http://groups.google.com/group/robotframework-users/browse_thread/thread/c44178c9edb4febe
Third party solutions to desired feature:
http://deanhume.com/Home/BlogPost/measuring-web-page-performance-with-selenium-2-and-the-web-timings-api/56
http://www.theautomatedtester.co.uk/blog/2010/selenium-webtimings-api.html
http://sevenseconds.wordpress.com/2011/06/28/velocity-conference-2011-workshop-on-automated-web-performance-testing/
http://www.supermind.org/blog/968/howto-collect-webdriver-http-request-and-response-headers

emanlove, yes, I've heard of that library, but didn't check out the forks. Nevertheless, it doesn't quite fit with the issue here. This issue is about doing testing with WebDriver and at the same time being able to query for the browser data such as HTTP headers and as a result of that also extrapolate timing statistics.
This was possible as part of Selenium RC via captureNetworkTraffic option. It isn't available to WebDriver and must be extended via third party tools unless it is somehow incorporated in future WebDriver releases.
But you are right that if I just wanted pure HTTP request/response testing, I could use the mentioned library or similar.
While the use case of this issue is not a widely requested or needed feature, it does have its uses. Same as how developers can check HTTP headers, cookies, and related data via browser extensions like Firebug, we would want same functionality exposed via Selenium to extract out with our tests for debugging or performance analysis, etc. rather than do it via separate tools in separate tests/scripts, etc.

There is a reason I think we need this feature:
On a webpage, a javascript execution trigger a http request. This happens typically when the webpage need send logging information to server. Such as following scenarios:

When user stay on one page for more than 3 seconds, it will send log to server
When user open a open a drop down menu and select a item, it will send log to server
And so on.

For this kind of scenarios, I can got two reason why robotframework-httplibrary is not suitable here.

The thing we need test is the behavior of javascript execution.
We need check if it works well in all kinds of browser.

I would like to share the following link:
https://github.com/Work4Labs/selenium-simple-test/blob/72569ee775425273859b36c201508a973ce2db00/src/sst/actions.py.
I came across browser mob some days back from this link and was not aware of its requirement at that time. From the glimpse, the snippet appears to use webdriver

That would be a good reference for a BrowserMob Proxy library. They're using BrowserMob's restful api. Thanks for the resource @rama-bornfree, I might do something with this!

Welcome, I will try to understand the snippet

I'm working on a BrowserMob Proxy library that would be more appropriate for this. As far as I'm concerned this is outside of the scope of S2L so I'm going to close it.

authors: daluu lsjuanny rama-bornfree zephraph


text:
RuntimeError

When I ran this code, I encountered the following problem: RuntimeError: The ffmpeg plugin does not work on Python 2.x,but when I input: python then: import ffmpeg,there is no problem,I can't figure out the reason, can someone help me?thx~

The whole error message is:
Traceback (most recent call last):
File "train_kth.py", line 180, in
main(**vars(args))
File "train_kth.py", line 98, in main
for f,p,img_sze,k,t in zip(tfiles,paths,shapes,Ks, Ts))
File "/usr/lib/python2.7/dist-packages/joblib/parallel.py", line 810, in call
self.retrieve()
File "/usr/lib/python2.7/dist-packages/joblib/parallel.py", line 757, in retrieve
raise exception
joblib.my_exceptions.JoblibRuntimeError: JoblibRuntimeError

Multiprocessing exception:
...........................................................................
/home/lab226/Desktop/iclr2017mcnet-master/src/train_kth.py in ()
175                       default=100000, help="Number of iterations")
176   parser.add_argument("--gpu", type=int, nargs="+", dest="gpu", required=True,
177                       help="GPU device id")
178
179   args = parser.parse_args()
--> 180   main(**vars(args))
181
182
183
184
...........................................................................
/home/lab226/Desktop/iclr2017mcnet-master/src/train_kth.py in main(lr=0.0001, batch_size=8, alpha=1.0, beta=0.02, image_size=128, K=10, T=10, num_iter=100000, gpu=[3])
93             Ks = np.repeat(np.array([K]),batch_size,axis=0)
94             paths = np.repeat(data_path, batch_size,axis=0)
95             tfiles = np.array(trainfiles)[batchidx]
96             shapes = np.repeat(np.array([image_size]),batch_size,axis=0)
97             output = parallel(delayed(load_kth_data)(f, p,img_sze, k, t)
---> 98                                                  for f,p,img_sze,k,t in zip(tfiles,paths,shapes,Ks, Ts))
f = <open file '../data/KTH/train_data_list_trimmed.txt', mode 'r'>
tfiles = array(['person01_walking_d4 282 362\n', 'person0...son01_walking_d4 171 247\n'],
dtype='|S33')
paths = array(['../data/KTH/', '../data/KTH/', '../data/.../data/KTH/', '../data/KTH/'],
dtype='|S12')
shapes = array([128, 128, 128, 128, 128, 128, 128, 128])
Ks = array([10, 10, 10, 10, 10, 10, 10, 10])
Ts = array([10, 10, 10, 10, 10, 10, 10, 10])
99             for i in xrange(batch_size):
100               seq_batch[i] = output[i][0]
101               diff_batch[i] = output[i][1]
102
...........................................................................
/usr/lib/python2.7/dist-packages/joblib/parallel.py in call(self=Parallel(n_jobs=8), iterable=<generator object >)
805             if pre_dispatch == "all" or n_jobs == 1:
806                 # The iterable was consumed all at once by the above for loop.
807                 # No need to wait for async callbacks to trigger to
808                 # consumption.
809                 self._iterating = False
--> 810             self.retrieve()
self.retrieve = <bound method Parallel.retrieve of Parallel(n_jobs=8)>
811             # Make sure that we get a last message telling us we are done
812             elapsed_time = time.time() - self._start_time
813             self._print('Done %3i out of %3i | elapsed: %s finished',
814                         (len(self._output), len(self._output),

Sub-process traceback:
RuntimeError                                       Tue Feb 26 13:15:35 2019
PID: 6435                                   Python 2.7.12: /usr/bin/python2
...........................................................................
/usr/lib/python2.7/dist-packages/joblib/parallel.py in call(self=<joblib.parallel.BatchedCalls object>)
67     def init(self, iterator_slice):
68         self.items = list(iterator_slice)
69         self._size = len(self.items)
70
71     def call(self):
---> 72         return [func(*args, **kwargs) for func, args, kwargs in self.items]
func =
args = ('person01_walking_d4 282 362\n', '../data/KTH/', 128, 10, 10)
kwargs = {}
self.items = [(, ('person01_walking_d4 282 362\n', '../data/KTH/', 128, 10, 10), {})]
73
74     def len(self):
75         return self._size
76
...........................................................................
/home/lab226/Desktop/iclr2017mcnet-master/src/utils.py in load_kth_data(f_name='person01_walking_d4 282 362\n', data_path='../data/KTH/', image_size=128, K=10, T=10)
88
89 def load_kth_data(f_name, data_path, image_size, K, T):
90   flip = np.random.binomial(1,.5,1)[0]
91   tokens = f_name.split()
92   vid_path = data_path + tokens[0] + "_uncomp.avi"
---> 93   vid = imageio.get_reader(vid_path,"ffmpeg")
vid = undefined
vid_path = '../data/KTH/person01_walking_d4_uncomp.avi'
94   low = int(tokens[1])
95   high = np.min([int(tokens[2]),vid.get_length()])-K-T+1
96   if low == high:
97     stidx = 0
...........................................................................
/home/lab226/.local/lib/python2.7/site-packages/imageio/core/functions.py in get_reader(uri='../data/KTH/person01_walking_d4_uncomp.avi', format=<Format FFMPEG - Many video formats and cameras (via ffmpeg)>, mode='?', **kwargs={})
138         raise ValueError(
139             "Could not find a format to read the specified file " "in mode %r" % mode
140         )
141
142     # Return its reader object
--> 143     return format.get_reader(request)
format.get_reader = <bound method FfmpegFormat.get_reader of <Format...G - Many video formats and cameras (via ffmpeg)>>
request = <imageio.core.request.Request object>
144
145
146 def get_writer(uri, format=None, mode="?", **kwargs):
147     """ get_writer(uri, format=None, mode='?', **kwargs)
...........................................................................
/home/lab226/.local/lib/python2.7/site-packages/imageio/core/format.py in get_reader(self=<Format FFMPEG - Many video formats and cameras (via ffmpeg)>, request=<imageio.core.request.Request object>)
159         select_mode = request.mode[1] if request.mode[1] in "iIvV" else ""
160         if select_mode not in self.modes:
161             raise RuntimeError(
162                 "Format %s cannot read in mode %r" % (self.name, select_mode)
163             )
--> 164         return self.Reader(self, request)
self.Reader = <class 'imageio.plugins.ffmpeg.Reader'>
self = <Format FFMPEG - Many video formats and cameras (via ffmpeg)>
request = <imageio.core.request.Request object>
165
166     def get_writer(self, request):
167         """ get_writer(request)
168
...........................................................................
/home/lab226/.local/lib/python2.7/site-packages/imageio/core/format.py in init(self=<imageio.plugins.ffmpeg.Reader object>, format=<Format FFMPEG - Many video formats and cameras (via ffmpeg)>, request=<imageio.core.request.Request object>)
209             self.__closed = False
210             self._BaseReaderWriter_last_index = -1
211             self._format = format
212             self._request = request
213             # Open the reader/writer
--> 214             self._open(**self.request.kwargs.copy())
self._open = <bound method Reader._open of <imageio.plugins.ffmpeg.Reader object>>
self.request.kwargs.copy =
215
216         @property
217         def format(self):
218             """ The :class:.Format object corresponding to the current
...........................................................................
/home/lab226/.local/lib/python2.7/site-packages/imageio/plugins/ffmpeg.py in _open(self=<imageio.plugins.ffmpeg.Reader object>, loop=False, size=None, dtype=None, pixelformat=None, print_info=False, ffmpeg_params=None, input_params=None, output_params=None, fps=None)
255             input_params=None,
256             output_params=None,
257             fps=None,
258         ):
259             # Get generator functions
--> 260             self._ffmpeg_api = _get_ffmpeg_api()
self._ffmpeg_api = undefined
261             # Process input args
262             self._arg_loop = bool(loop)
263             if size is None:
264                 self._arg_size = None
...........................................................................
/home/lab226/.local/lib/python2.7/site-packages/imageio/plugins/ffmpeg.py in _get_ffmpeg_api()
56
57 def _get_ffmpeg_api():
58     global _ffmpeg_api
59     if _ffmpeg_api is None:
60         if sys.version_info < (3,):
---> 61             raise RuntimeError("The ffmpeg plugin does not work on Python 2.x")
62         try:
63             import imageio_ffmpeg
64         except ImportError:
65             raise ImportError(
RuntimeError: The ffmpeg plugin does not work on Python 2.x

When I ran this code, I encountered the following problem: RuntimeError: The ffmpeg plugin does not work on Python 2.x,but when I input: python then: import ffmpeg,there is no problem,I can't figure out the reason, can someone help me?thx~

Do you have multiple versions of python installed on your machine? If so, the 'python' command may be linked to python 3.x, thus the ffmpeg can be successfully imported.

I will go ahead and close the issue since it was related to your machine setup, and it seems @u112358 helped. Thanks @u112358!!

Hello. I also faced this problem. My python is 2.7.12 which is run under a virtual environment. I installed all requirements including ffmpeg installed with conda. And I cannot pip install imageio-ffmpeg because it only supports python 3.4+. How did you resolve it ? Thank you very much !

i just can't figure out how @u112358 's method, run python2 and link python3?
so i just gave up.
I try to use Python 3 instead, and some tweaks.
xrange->range
def deconv2d
output_shape=np.int32(out_shape),  ---> add np.int32()
and it seems it can run smoothly
(test on test_ucf101.py only, results seems ok)
btw, i also need, conda install -c conda-forge imageio-ffmpeg
no matter python2 or python3


text:
Auto correct should not automatically remove trailing whitespace in heredoc

Back in 2017 https://github.com/rubocop-hq/rubocop/issues/4517 raised the issue that trailing whitespaces should not be marked as offences in heredoc strings.
This resulted in https://github.com/rubocop-hq/rubocop/pull/5777 which added a new config option to prevent the cop from complaining.
Whilst this seems like a good fix, it still means that when running auto correct, it will remove trailing spaces automatically, which could result in a change in logic.
Take the below for example:
require 'digest'

my_string = <<~END
Whitespace here:
END

sha = Digest::SHA2.new(256).hexdigest my_string
expected_sha = "74788f79010cd7a165e6df2e91013ce72903696bca4d42989de97c3150b89db2"

puts "authenticated" if expected_sha == sha

This will print "authenticated" before running rubocop --auto-correct, but will fail after.
I've had a similar issue in production where we had to verify a signed string and to test I used an example provided string, which had trailing whitespace. Running rubocop --auto-correct broke the tests.

Expected behavior
Running rubocop --auto-correct should not remove the trailing whitespace.
Actual behavior
The whitespace is removed
Steps to reproduce the problem
See the script above
RuboCop version
0.81.0

I agree. I think we chose the wrong default in #5777. It should be
Layout/TrailingWhitespace:
  AllowInHeredoc: true

AllowInHeredoc: true looks good default value to me. I opened #7883.

authors: KNejad jonas054 koic

repo: rubocop-hq/rubocop


text:
Improve Rails/Pluck cop

Reference: https://rails.rubystyle.guide/#pluck
Actual behavior
I have the code:
# frozen_string_literal: true

class User < ApplicationRecord
  def method
    User.all.map(&:name)
  end
end

I will run rubocop and not get any offences:
ydakuka@yauhenid:~/Work/project$ bin/rails_docker rubocop app/models/user.rb
Inspecting 1 file
.

1 file inspected, no offenses detected

Rubocop
ydakuka@yauhenid:~/Work/project$ bin/rails_docker rubocop -V
1.55.1 (using Parser 3.2.2.3, rubocop-ast 1.29.0, running on ruby 2.7.8) [x86_64-linux]
  - rubocop-capybara 2.18.0
  - rubocop-factory_bot 2.23.1
  - rubocop-performance 1.18.0
  - rubocop-rails 2.20.2
  - rubocop-rake 0.6.0
  - rubocop-rspec 2.23.0
  - rubocop-thread_safety 0.5.1

This cannot be supported for the same reason as https://github.com/rubocop/rubocop-rails/issues/1087#issuecomment-1694426530.

authors: koic ydakuka

repo: rubocop/rubocop-rails


text:
[Fix #10273] Fix a false positive for InternalAffairs/UndefinedConfig

Fixes #10273.
This PR fixes a false positive for InternalAffairs/UndefinedConfig when inheriting a Base class other than RuboCop's Base class.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

🙇♂

@tubaxenor You are welcome!

authors: koic tubaxenor

repo: rubocop/rubocop


text:
Fix a method name for Style/RedundantLineContinuation

This PR is a follow-up of #11694.
Wrong method name was used in the cop.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[-] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[-] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[-] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

I'm going to close this PR. Unfortunately this request is not an essential solution. I will try to solve that.
https://github.com/rubocop/rubocop/pull/11694#issuecomment-1494003899

I think this will probably resolve the issue. We need to check whether the syntax is valid by including the parent node if there is one.

https://github.com/rubocop/rubocop/pull/11754

authors: koic ydah


text:
Need a ruby-debug 0.11.0 release

Recently we got a fix out in ruby-debug-base 0.11.0 for JRuby, but because ruby-debug has not had a release it's not possible to resolve both in a Gemfile.
See https://github.com/jruby/jruby/issues/6018#issuecomment-584660437

+1 ...

What would be necessary in order for this release to happen? Is there any work you need done that an outsider could do?

@ViugiNick are you able to release this as well?  Looks like just releasing base does not line up numberwise.

I believe this can be closed with the latest ruby-debug release by @ViugiNick: https://github.com/jruby/jruby/issues/6018#issuecomment-600452838

Specifying version '0.11.0' in my gemfile causes a failure to install:
Bundler could not find compatible versions for gem "ruby-debug-base":
  In Gemfile:
    ruby-debug (= 0.11.0) was resolved to 0.11.0, which depends on
      ruby-debug-base (~> 0.11.0.0)

Could not find gem 'ruby-debug-base (~> 0.11.0.0)', which is required by gem
'ruby-debug (= 0.11.0)', in any of the sources.

Does  ruby-debug-base (~> 0.11.0.0) even make any sense? Am I doing something wrong?

looks like it's asking for 0.11.0.0 because of this line in the gemspec:
https://github.com/ruby-debug/ruby-debug/blob/ecc865ac9373cb9ec4975b2433fffd79915d9e93/ruby-debug.gemspec#L34
Wondering why this ever worked, given that this line has been unchanged for several years.

It seems that the dependency on ruby-debug-base is very narrow, requiring an exact match, which in turn means that all gems must be released in lock-step.
We need to get a ruby-debug-base release of 0.11.0 and in the future we need a way to guarantee that these gems are all being released at the same time.
Alternatively, if ruby-debug can go with a softer dependency and still work that might mean we don't have to force a release of ruby-debug-base for every ruby-debug release.
I would really like to get this resolve... we get periodic reports about debugging not working and we can't do much about it when the gems are not getting released.
@ViugiNick Are you still the point of contact on this? How can we help maintain this gem, including getting releases out as needed?

It seems that the dependency on ruby-debug-base is very narrow, requiring an exact match, which in turn means that all gems must be released in lock-step.
We need to get a ruby-debug-base release of 0.11.0 and in the future we need a way to guarantee that these gems are all being released at the same time.
Alternatively, if ruby-debug can go with a softer dependency and still work that might mean we don't have to force a release of ruby-debug-base for every ruby-debug release.
I would really like to get this resolve... we get periodic reports about debugging not working and we can't do much about it when the gems are not getting released.
@ViugiNick Are you still the point of contact on this? How can we help maintain this gem, including getting releases out as needed?

So I was doing some fighting against this today on jruby-9.2.14.0 and ran into differing behavior based on bundler version.
On bundler version 2.1.2, I can happily install ruby-debug 0.11.0. But once it's installed and the Gemfile.lock updated, trying to do bundler install yields this error:
Bundler could not find compatible versions for gem "ruby-debug-base":
  In snapshot (Gemfile.lock):
    ruby-debug-base (= 0.11.0)

  In Gemfile:
    ruby-debug java was resolved to 0.11.0, which depends on
      ruby-debug-base (~> 0.11.0.0)

and in order to make updates to other gems in the Gemfile, I have to run bundle update ruby-debug ruby-debug-base (which is pretty annoying).
On bundler version 2.2.4 (which is included with jruby-9.2.14.0 for example), I couldn't install ruby-debug 0.11.0 or 0.10.6 at all. Instead it installs 0.10.4. Looking at rubygems, I can't see any reason for this to happen, my only guess was that bundler was being stricter about installing ruby-debug-base version 0.11.0 as fulfilling the gemspec requirement for ~> 0.11.0.0 but nothing actually jumps out at me among the published versions. I scanned the gemspecs for the two versions too, but nothing jumped out at me there either.

So I was doing some fighting against this today on jruby-9.2.14.0 and ran into differing behavior based on bundler version.
On bundler version 2.1.2, I can happily install ruby-debug 0.11.0. But once it's installed and the Gemfile.lock updated, trying to do bundler install yields this error:
Bundler could not find compatible versions for gem "ruby-debug-base":
  In snapshot (Gemfile.lock):
    ruby-debug-base (= 0.11.0)

  In Gemfile:
    ruby-debug java was resolved to 0.11.0, which depends on
      ruby-debug-base (~> 0.11.0.0)

and in order to make updates to other gems in the Gemfile, I have to run bundle update ruby-debug ruby-debug-base (which is pretty annoying).
On bundler version 2.2.4 (which is included with jruby-9.2.14.0 for example), I couldn't install ruby-debug 0.11.0 or 0.10.6 at all. Instead it installs 0.10.4. Looking at rubygems, I can't see any reason for this to happen, my only guess was that bundler was being stricter about installing ruby-debug-base version 0.11.0 as fulfilling the gemspec requirement for ~> 0.11.0.0 but nothing actually jumps out at me among the published versions. I scanned the gemspecs for the two versions too, but nothing jumped out at me there either.

authors: Confusion bblack enebo headius keegangroth rdp stewi2

repo: ruby-debug/ruby-debug


text:
Add Ruby 2.4.0 support.

Fixnum is deprecated in Ruby 2.4 so it should be replaced with Integer

Tried to upgrade an app to Ruby 2.4 today and got bit by this. Any idea when you might be able to get a 2.4-compatible version pushed out?

It's the highest priority issue right now but unfortunately this PR needs some work before we can safely merge it. I can't give any timelines because it will depend on when myself of one of the other maintainers can spend some time on it. Sorry I can't be more precise but we are aware of the issue and are looking into it

I've split this into two separate commits and merged manually (one to remove references to Fixnum and one to make error messages consistently refer to json-schema types rather than ruby types), and I have released these changes under json-schema 2.8.0
Thanks for your contributions @marshall-lee

authors: iainbeeston lleger marshall-lee

repo: ruby-json-schema/json-schema


text:
Add types for minimagick

Adds types that follows the basic use case described in the README.
https://github.com/minimagick/minimagick/tree/v4.13.1
The following types will be added after this PR merge.

MiniMagick.configure
Methods hacked with method_missing

mogrify, identify, etc...

/merge


text:
Document MultiTargetNode fields

This should check off another box in #2123.
According to https://en.wikipedia.org/wiki/Bracket#Parentheses the singular form of parentheses in EN-US is parenthesis, I'm not sure if this is the form we should standardi{s,z}e. I tried looking for other examples with the name of ( or ), but couldn't find anything except for paren.
I think the example code covers all use cases.

This looks really great, thanks!

authors: herwinw kddnewton

repo: ruby/prism


text:
Merge specs of UNIXSocket.pair and UNIXSocket.socketpair into a shared spec

The methods are aliases, so we probably shouldn't have two separate specs hanging around.

This is a second attempt at  #1131, because I've had commit permissions for 1 day and I already screwed things up by merging the wrong branch

I'm confused, this seems to have the same commits as #1131 which is merged (and looks alright and CI passed).

It seems commits in #1131 were removed from the master branch.

Thank you!

authors: andrykonchin eregon herwinw

repo: ruby/spec


text:
Remove check for unicode_normalize to be required from v2.5 (second try)

The check is no longer needed for Ruby v2.5 and later, because the relevant functionality has been moved to C code in string.c. This check blocks the removal of enc/prelude from the list of files used in the prelude.
(see https://svn.ruby-lang.org/cgi-bin/viewvc.cgi?view=revision&revision=58559 and https://travis-ci.org/ruby/ruby/builds/228602567)
This is a revised version of #433, see there for additional discussion.
This is a revised version of #434, to hopefully get the number of ends correct.

Thank you!
I committed manually in 41176ead68b14011658c8abd0ebd67df2ae632fb with the chagned version on the spec above so it only applies from 2.3 to < 2.5.

authors: duerst eregon


text:
Add Diaperbase Logo to Distribution PDF

We need to update our prawn pdf template we are using to create distribution pdfs to add in the diaperbase logo at the bottom with some text.
I was thinking: Lovingly Created With <diaperbaselogo.png> (the logo is obviously an image.)

FYI (for anyone else checking in) it looks like this has in-flight work in #110

Woo hoo! @cattywampus's PR completed this! :)

Fixed by #110

authors: armahillo seanmarcia

repo: rubyforgood/diaper


text:
[BUG] A bank users are unable to make a edit/correction to a purchase, donations, or distributions

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Attempting to make a correction on a distribution, donation, or purchase will result in a 500 error that looks like this:
undefined local variable or method `id' for {"item_id"=>4828, "name"=>"Wipes (Baby)", "quantity"=>1000, "active"=>true}:ActiveSupport::HashWithIndifferentAccess

Expected Behavior
I expect that the editing works without the error.
Steps To Reproduce
In local (development), go to a purchase, donation, or distribution and attempt to make a edit or correction. It would result in the error mentioned.
Environment
- OS:  macOS 12.4

Anything else?

shannon@starkcountydiaperbank.org reported that they are unable to edit a purchase. I tried it out and got this error:
undefined local variable or method `id' for {"item_id"=>4828, "name"=>"Wipes (Baby)", "quantity"=>1000, "active"=>true}:ActiveSupport::HashWithIndifferentAccess

shannon@starkcountydiaperbank.org also reported the same issue with donations:
undefined local variable or method `id' for {"item_id"=>406, "name"=>"Kids (Newborn)", "quantity"=>175, "active"=>true}:ActiveSupport::HashWithIndifferentAccess

I don't see this in production bug monitoring tools so I'd like to see if someone can verify if anyone else is experiencing this issue.

@dorner thank goodness bullet isn't on in deployed environments! Wanna take a swing at fixing this?

I'm getting it 🚀

So it looks like the issue is here: https://github.com/flyerhzm/bullet/blob/master/lib/bullet/detector/n_plus_one_query.rb#L36
combined with this: https://github.com/rubyforgood/human-essentials/blob/main/app/models/concerns/itemizable.rb#L92
Itemizable defines a to_a method which returns a list of items. I don't know why it behaves this way since to_a is a "special" method used by Ruby to allow a class to define a method that returns an array. For example, the following:
{foo: "bar"}.to_a
returns [[:foo, "bar"]].
Apparently @seanmarcia loves them for it though 😛 https://github.com/rubyforgood/human-essentials/pull/718#discussion_r284282261
Long story short we have a few options here:

Figure out all the places where to_a is used in our code and rip them out. Unfortunately this is nigh-on impossible, since to_a is used implicitly, such as in exactly this case.
Add a PR to bullet changing the Array call to Array.wrap, which only uses to_ary and does not drop down to to_a. I think that's really what's meant to happen here in any case - I don't think Bullet really wants us to call a transformation function.

For now I'll add in the PR and see what the response is.

PR has been created! https://github.com/flyerhzm/bullet/pull/621

authors: dorner edwinthinks italomatos

repo: rubyforgood/human-essentials


text:
Remove copy link function from the staff pets index table elipses

Remove the copy link from here

Can I pick this up?

@pshong79 all yours

repo: rubyforgood/pet-rescue


text:
Makes yank understand the --key paramter to use different API keys

This enables the user to specify a `--key KEY_NAMEoption. This will look for a key namedKEY_NAMEin your.gem/credentialsfile (just like it is already possible withgem push``).

Looks good to me. @qrush any objections to merging?

authors: sferik walski

repo: rubygems/gemcutter


text:
change image upload to only allow jpg, png, gif #1064

change to only allow jpg, png and gif as profile pictures, because otherwise if someone wants to upload webp for example an error occured (picture is uploaded but can not shown)

In the second commit I remove the centering in the faq text and make it left aligned.

I added a validation for no empty file upload, because this error happened so we should prevent this :)

Cool, thanks @sabrina-ulbrich! I only updated the info section below the picture and added .gif as possible format.

authors: sabrina-ulbrich zaziemo


text:
Added Kaggle links and fixed typos

Added Kaggle.com links and fixed a typos throughout the file.
Hopefully this goes through! Let me know if I buggered anything up and I'll try and fix it.

The changes made to the resourcelist.md are all great!
I merged the commit, but in the future are you be able to delete the json, sqlite and suo files before you pull request? They are find to stay on your local machine (I think they are from Visual Studio?), but I don't want to add those extra files to the main repository. For this time I will just delete the files after merge!
Thanks so much for your contributions, feel free to add more later!

Ah! I knew I'd mess something up! I'll keep those extras out next time
round.
Thanks again!
On Thu, Jul 1, 2021 at 3:30 PM rubyspch @.***> wrote:

The changes made to the resourcelist.md are all great!
I merged the commit, but in the future are you be able to delete the json,
sqlite and suo files before you pull request? They are find to stay on your
local machine (I think they are from Visual Studio?), but I don't want to
add those extra files to the main repository. For this time I will just
delete the files after merge!
Thanks so much for your contributions, feel free to add more later!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rubyspch/Resources-for-Your-100-Days/pull/5#issuecomment-872563169,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASG5G6TNQTYUB7XE7NIM2KLTVTM5TANCNFSM47VKWX7Q
.

No worries, experiencing this stuff is what this project is for!

authors: KrisAirdancer rubyspch


text:
Requesting clarification in documentation

Thanks @ruffsl for this helpful extension! I am using this to speed up CI for feature branches and would like to seek some clarification to what is described in the README. (Also, much thanks to providing a nice readme instead of just a mostly empty file only containing the package name!)
Can you please explain the purpose of the --packages-select-cache-key? For example, where would I look to see what the default key is and why would I need to override it?
Also, the lock workflow is not intuitive to me. In the quick start example, why do I need to lock the workspace before the first colcon build and also after the minor source file changes? When colcon build --packages-skip-cache-valid is run, does it re-hash the package and compare to what is cached? Or does the hashing only happen when colcon lock is called? Also, it appears that lockfiles are also updated/created after the build and test verbs too (as described by the sentence "Upon successful task completion for a package job, as when evoking colcon verbs like build, test, etc, these lockfiles are updated for the evoked verb, thereby delineating the provenance of the job’s results"). To my understanding, the verb lock is a bit strong because it sounds like other actions would not be permitted to make changes to lockfiles, but that is not the case. To me, the verb is closer to hash or maybe update to manually trigger an update to the lock files.
I think that a more detailed explanation (maybe annotating the example) of what creates and or modifies which lock files and what checks against the lock files are performed would be helpful. Also, an example of using --packages-select-cache-key would be helpful.
Overall, I think that  understanding that there are some "automatic" updates to lock files depending on using verbs like build and test is an important concept that a new user may not be aware of based on the current example and explanation.

Hey @zflat , neat to hear your use of this extension to speed up CI. If you like to see a real world example using this extension, we've been using it rather heavily for the Nav2 project for over a year or so:

https://github.com/ros-planning/navigation2/pull/2343

Can you please explain the purpose of the --packages-select-cache-key? For example, where would I look to see what the default key is and why would I need to override it?

The purpose of the --packages-select-cache-key is to override the default cache key selected by the verb handler. For example, the verb handler for the "colcon list", it uses the same verb handler for "colcon cache", which defines what lockfiles are to be used for comparison or reference. When used with package selection, this can be helpful when listing what caches are still valid for other colcon verbs (e.g. not just for "colcon list").

https://github.com/ruffsl/colcon-cache/blob/0a23776c5d30e3e2611d64c828c500a5a9fdcca8/setup.cfg#L94
https://github.com/ruffsl/colcon-cache/blob/0a23776c5d30e3e2611d64c828c500a5a9fdcca8/colcon_cache/package_selection/valid.py#L56-L58
https://github.com/ruffsl/colcon-cache/blob/0a23776c5d30e3e2611d64c828c500a5a9fdcca8/colcon_cache/package_selection/valid.py#L82-L85

In Nav2 for example, we do this to list packages with invalidated caches for specifically the "colcon build" verb, so that we can determine the package builds that must be subsequently cleaned:
https://github.com/ros-planning/navigation2/blob/5547a20ae711417af90768d9d594a4524064e1ca/.circleci/config.yml#L163-L169

Also, the lock workflow is not intuitive to me.

The level of abstraction with caching results for colcon verbs, verbs that transitively depend on other verbs, makes this difficult to describe. The hashing of source files (or query to detected revision control) is only invoked with the "colcon cache lock" subverb. I suppose this could have been abbreviated to the root verb "colcon cache", but I suspected I may want to add more extension subverbs in the future, so I pushed that hashing funatilty into a "lock" subverb, as "colcon cache cache" seemed too peculiar.
The updating of lockfiles is currently simply a copy operation upon a successful task for the package, where the invoked colcon verb triggers an event handler that copies the lockfile from the verb it transitively depends upon. E.g. the build verb depends upon the cache verb, and the test verb depends upon the build verb. This pattern could be extended for any other verbs via more registered event handlers.

I think that a more detailed explanation (maybe annotating the example) of what creates and or modifies which lock files and what checks against the lock files are performed would be helpful.

I can add a "How does it work" section to the readme, but I'd first like to finish refactoring where the lockfiles are written and read from in the colcon workspace, as to store the lockfiles closer to the artifacts they claim to represent:

https://github.com/ruffsl/colcon-cache/pull/42

Thanks @ruffsl  for the explanation! The example of using a different --packages-select-cache-key makes it more clear to me now.
It is helpful to know that the build verb lock file is just copied from the cache verb. And I think that a "how it works" section would be very helpful.

authors: ruffsl zflat

repo: ruffsl/colcon-cache


text:
@fortune-sheet/react 没有打印功能吗

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@fortune-sheet/react can't print ?

repo: ruilisi/fortune-sheet


text:
change_path = area + '/change.bmp'     un_path = area + '/unchange.bmp'

do you have change.bmp and unchange.bmp?the change_ref is the same as unchange.bmp?

The value changed regions of change.bmp is 1, while the other regions' value is 0 (undefined and unchanged regions). Value of unchange.bmp is the opposite.

Which data sets are your training data set and validation data set? How many images are there in the training data?
Must we use mat files for training? I want to use JPG file as training set. Is that OK?
can you speak chinese?
------------------ 原始邮件 ------------------
发件人: "LixiangRu"notifications@github.com;
发送时间: 2019年8月2日(星期五) 上午9:08
收件人: "rulixiang/DSFANet"DSFANet@noreply.github.com;
抄送: "1227482510"1227482510@qq.com;"Author"author@noreply.github.com;
主题: Re: [rulixiang/DSFANet]     change_path = area + '/change.bmp'    un_path = area + '/unchange.bmp' (#1)
The value changed regions of change.bmp is 1, while the other regions' value is 0 (undefined and unchanged regions). Value of unchange.bmp is the opposite.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

训练数据不是一整张的图像，而是从图像中选取的像素点；
用的数据集之一是从这下载的
mat只是我用来存储数据的，任何能读成numpy矩阵（高x宽x波段）的数据格式都可以的。

可能是groundtruth.mat里面变化区域值是255，而我的cva_ind变化区域像素值是1，你可以试试把groundtruth除以255

这个问题我已经想到了，并且已经将groundtruth.mat的[0,255]转换成[0,1]格式了，但是还是出现NAN的问题。
在调试过程中，我发现我的change.bmp  unchange.bmp是二维图像，请问你的change.bmp是二维图像还是三维图像？会不会是我的change.bmp有错误。
如果可以的话，能不能请您把您的ind.mat数据和change.bmp发我一份......
谢谢您！
------------------ 原始邮件 ------------------
发件人: "LixiangRu"notifications@github.com;
发送时间: 2019年8月2日(星期五) 晚上9:38
收件人: "rulixiang/DSFANet"DSFANet@noreply.github.com;
抄送: "1227482510"1227482510@qq.com;"Author"author@noreply.github.com;
主题: Re: [rulixiang/DSFANet]     change_path = area + '/change.bmp'    un_path = area + '/unchange.bmp' (#1)
可能是groundtruth.mat里面变化区域值是255，而我的cva_ind变化区域像素值是1，你可以试试把groundtruth除以255
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

river.zip

收到了！非常感谢您的耐心！
------------------ 原始邮件 ------------------
发件人: "LixiangRu"notifications@github.com;
发送时间: 2019年8月2日(星期五) 晚上10:37
收件人: "rulixiang/DSFANet"DSFANet@noreply.github.com;
抄送: "1227482510"1227482510@qq.com;"Author"author@noreply.github.com;
主题: Re: [rulixiang/DSFANet]     change_path = area + '/change.bmp'    un_path = area + '/unchange.bmp' (#1)
river.zip
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

我在使用了你的原数据之后，训练能顺利完成，精度还可以达到94%左右。非常理想！感谢大佬倾力相助，在此谢过
但是在变换了自己的数据集之后就出现了新的问题。
这个模型对于数据的格式有什么要求吗？
我的数据是我自己将9609603的tif文件转换成9609603的mat文件，为何会出现这种错误呢？
------------------ 原始邮件 ------------------
发件人: "LixiangRu"notifications@github.com;
发送时间: 2019年8月2日(星期五) 晚上10:37
收件人: "rulixiang/DSFANet"DSFANet@noreply.github.com;
抄送: "1227482510"1227482510@qq.com;"Author"author@noreply.github.com;
主题: Re: [rulixiang/DSFANet]     change_path = area + '/change.bmp'    un_path = area + '/unchange.bmp' (#1)
river.zip
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

这个代码还是像素级的变化检测，对中低分辨率效果还不错，但是高分辨率的影像不行；3个波段的数据我没测试过，不过我想多波段数据的结果会比3个波段的更好

大佬，我又来了~~~
想知道在训练结束后，网络测试怎么做？对于无标签的数据，我们该怎么做呢？
------------------ 原始邮件 ------------------
发件人: "LixiangRu"notifications@github.com;
发送时间: 2019年8月3日(星期六) 中午12:32
收件人: "rulixiang/DSFANet"DSFANet@noreply.github.com;
抄送: "1227482510"1227482510@qq.com;"Author"author@noreply.github.com;
主题: Re: [rulixiang/DSFANet]     change_path = area + '/change.bmp'    un_path = area + '/unchange.bmp' (#1)
这个代码还是像素级的变化检测，对中低分辨率效果还不错，但是高分辨率的影像不行；3个波段的数据我没测试过，不过我想多波段数据的结果会比3个波段的更好
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

就是先用CVA预处理得到训练样本，之后运行代码，在dsfa.py里面，change_map就是整张图像的变化检测结果
    change_map = np.reshape(utils.kmeans(np.reshape(all_magnitude, [-1])), img_shape[0:-1])

    logging.info('Max value of change magnitude: %.4f'%(np.max(all_magnitude)))
    logging.info('Min value of change magnitude: %.4f'%(np.min(all_magnitude)))

    # magnitude
    acc_un, acc_chg, acc_all2, acc_tp = utils.metric(1-change_map, chg_map, un_map)
    acc_un, acc_chg, acc_all3, acc_tp = utils.metric(change_map, chg_map, un_map)
    plt.imshow(all_magnitude, cmap='gray')
    plt.show()

因为没有测试样本的标签，所以要把utils.metric注释掉

authors: rulixiang xautdestiny

repo: rulixiang/DSFANet


text:
Using Multiple StorageContexts with VectorStoreIndex for Different Users ?

I'm looking into using multiple storage contexts for initializing VectorStoreIndex.
My dataset includes 20 documents, each relevant to particular users.
For instance, I'd like to set up a storage context with Documents A, B, and D for one user query, and Documents A, B, and F for another.
Is this feasible?
Should I generate all document vectors first and then apply metadata filters?
Additionally, how would I go about filtering these in ChatEngine?

@leoz2007 I think you can add metadata to the documents that can be used to relate the user to the document and then query using that metadata. In the simplest case, that would be adding the userId to the metadata.
Here's an example of filtering by metadata: https://github.com/run-llama/LlamaIndexTS/blob/main/examples/chromadb/preFilters.ts

hey @marcusschiesser ! but in @leoz2007 scenario, we should have multiple userIds added to metadata, because Documents A and B should be available for both users. is it possible to filter documents in the way that the metadata field is a list of values and it must contain a specific value to satisfy the filter condition?
or maybe vice-versa: each user has a list of accessible documenIds and is it possible to set up filters in a way that a specific metadata field value must be IN a list passed to filters?

Yes, I agree working with doc IDs sounds like a better solution to me too. We're working to integrate something similar into create-llama, should be available next week

that's great! just to clarify: are you planning to introduce new types of MetadataFilters other than ExactMatchFilter, right?

@dimatill yes there are now in release 0.5.5, see https://ts.llamaindex.ai/modules/query_engines/metadata_filtering - does that fit your needs? if not please reopen the ticket

@marcusschiesser yes, it theoretically fits, but I'm using pgvector, and it looks like it's still not implemented for pgvector 🥲
https://github.com/run-llama/LlamaIndexTS/blob/main/packages/llamaindex/src/storage/vectorStore/PGVectorStore.ts#L275

@dimatill yes, that's true. Would you mind sending a PR adding that support? I guess it would be similar to Milvus which we just added

yes, I'll take a look

authors: dimatill leoz2007 marcusschiesser

repo: run-llama/LlamaIndexTS


text:
Update easy-arceuus-runecrafting

Super small change; just lowers default config settings for flashing speed.
(Someone brought up epilepsy concerns.)

converting to draft until build failures are resolved

closing as the above comments have not been resolved yet. feel free to resubmit when they are

authors: Alexsuperfly LlemonDuck poi56iop

repo: runelite/plugin-hub


text:
Zoom bug

If inner zoom is enabled it pops to the middle when click and has zoomed in if outer enabled then pops middle if u zoomed out!

https://gyazo.com/27195b6a9cd1ce8160239ccf98e23a24

Fixed in #1416

authors: deathbeam kulershk

repo: runelite/runelite


text:
Medium clue - Jump for joy in Yanille bank

For the medium clue scroll:
"Jump for joy in Yanille bank. Dance a jig before you talk to me. Equip a brown apron, adamantite medium helmet and snakeskin chaps."
There is no marker showing up in the Yanille bank.

Added fix into #2030

authors: MarcJtk Roughsketch


text:
Thieving Chest timers

Is your feature request related to a problem? Please describe.
When a thieving chest is looted a timer starts (time depends on chest), when the timer has expired the chest can be looted again. It's kind of annoying you can't actively see when the chest is available for thieving again.
Describe the solution you'd like
It would be nice to have an overlay on the chest which shows the cooldown period visually.
Describe alternatives you've considered
There is a similar timer for hunter traps. This is what I think would be the best.

Additional context
N/A

Bump.

What's the status on this feature?

Status please?

Still nonexistent ??

This was added to the plugin hub in runelite/plugin-hub#181

authors: Mr-Vexy Nightfirecat SolveSoul dhharris th3oryofch4os zivc


text:
xp-tracker: Add Time-To-Level to Canvas And XP Tracker

closes #10888, #8373
This PR makes the XP tracker panel (and Overlay Canvas) labels configurable for different metrics.
TTL in Progress bar:

Customizable XpInfoBox

Config menu

ready for review :)

Bro - this is straight up awesome. I love you and I hope they merge this soon!

50d13a3 and 8310f17 should be rebased and squashed as needed

@Nightfirecat those commits have been squashed, and your change/suggestion was also included.

Your last commit is a bit messy @while-loop . It contains changes to license headers while that commit is not modifying those files at all, previous commits are so the change should be included there. Same with @Nightfirecat 's change, it should be in the original change and not changed in last commit.

@deathbeam I've amended the previous commits so they contain the scoped changes and copyright additions.
3rd time's a charm :)

(latest push amended my commit email to my personal address)

Travis build is failing

I think that was a CI issue. Could you rerun it?
$ ./travis/build.sh
+wget -O/tmp/glslang.zip https://github.com/KhronosGroup/glslang/releases/download/8.13.3559/glslang-master-linux-Release.zip
--2020-04-30 15:58:14--  https://github.com/KhronosGroup/glslang/releases/download/8.13.3559/glslang-master-linux-Release.zip
Resolving github.com (github.com)... 140.82.112.3
Connecting to github.com (github.com)|140.82.112.3|:443... connected.
HTTP request sent, awaiting response... 429 too many requests
2020-04-30 15:58:14 ERROR 429: too many requests.
The command "./travis/build.sh" exited with 8.

Looks like a Travis issue. I tried re-running the job a few times, but it's running into a issue we've seen before. Try rebasing so your branch includes 0b6dabd9a32583c6505be995843ff82827221bac.

(rebased and now passing)

authors: Nightfirecat deathbeam larkable while-loop