text:
1.3.0

Signed-off-by: Audrow Nash audrow@openrobotics.org

It seems that the jobs are hanging. I'm going to merge anyway.

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
add python-tk to Wily/Xenial

Links:

http://packages.ubuntu.com/xenial/python-tk
http://packages.ubuntu.com/xenial/python3-tk

Sorry, that was originally submitted as pyside stuff.

repo: ros/rosdistro


text:
demos: 0.25.0-1 in 'rolling/distribution.yaml' [bloom]

Increasing version of package(s) in repository demos to 0.25.0-1:

upstream repository: https://github.com/ros2/demos.git
release repository: https://github.com/ros2-gbp/demos-release.git
distro file: rolling/distribution.yaml
bloom version: 0.11.2
previous version for package: 0.24.1-1

action_tutorials_cpp

No changes

action_tutorials_interfaces

No changes

action_tutorials_py

No changes

composition

No changes

demo_nodes_cpp
* Service introspection (#602 <https://github.com/ros2/demos/issues/602>)
  * Add in a rclcpp and rclpy demo of introspection.
* Contributors: Chris Lalancette

demo_nodes_cpp_native

No changes

demo_nodes_py
* Service introspection (#602 <https://github.com/ros2/demos/issues/602>)
* Contributors: Chris Lalancette

dummy_map_server

No changes

dummy_robot_bringup

No changes

dummy_sensors

No changes

image_tools

No changes

intra_process_demo

No changes

lifecycle

No changes

lifecycle_py
* Cleanup lifecycle_py to conform to ROS 2 standards. (#604 <https://github.com/ros2/demos/issues/604>)
* Contributors: Chris Lalancette

logging_demo

No changes

pendulum_control

No changes

pendulum_msgs

No changes

quality_of_service_demo_cpp

No changes

quality_of_service_demo_py

No changes

topic_monitor

No changes

topic_statistics_demo

No changes

Please hold for coordinated release.


text:
compass: 1.0.1-1 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository compass to 1.0.1-1:

upstream repository: https://github.com/ctu-vras/compass.git
release repository: https://gitlab.fel.cvut.cz/cras/ros-release/compass.git
distro file: noetic/distribution.yaml
bloom version: 0.11.2
previous version for package: null

compass
* Made use of cras_cpp_common's node_from_nodelet CMake macro.
* Removed imu_transformer workaround
* Added option to force magnetic declination value.
* Added visualization of azimuth.
* Fixed IMU orientation covariance transformation.
* Renamed magnetometer_compass package to compass.
* Added variance to magnetometer compass outputs. It now also outputs fully valid georeferenced IMU messages instead of just writing the orientation into them.
* Contributors: Martin Pecka

compass_msgs
* Added variance to Azimuth message.
* Added improved version of compass.
* Contributors: Martin Pecka

See my comments in https://github.com/ros/rosdistro/pull/37712#pullrequestreview-1488682468 about this package.

Reproducing the comment thread in #37712:
clalancette:
This name seems pretty generic to me, and thus I think it probably violates https://www.ros.org/reps/rep-0144.html#global-guidelines point 1 or 4. It's kind of subjective, as this is a generic package, but it isn't clearly used by large parts of the community. Thus I think this package would be a candidate for prefixing the name of the entity.

peci1:
What about keeping compass_msgs and renaming compass to magnetometer_compass?

There's really no need for org prefix as the package just implements a generic algorithm anybody would use when trying to get azimuth readings from a magnetometer.

I guess I could buy that, though I would appreciate an opinion from @mjcarroll and @adityapande-1995 on this.

compass_msgs seems fine to me

Specific enough for me to identify this package has messages for working with a compass
Doesn't have catch-all names like "utils" or "common"
Doesn't redundantly contain "ros"
Describes what it does (this guideline seems very similar to the first).
Doesn't use a name that's already taken
Not in the guidelines, but we've allowed "vision_msgs" and this is about as specific: https://index.ros.org/p/vision_msgs/

compass on it's own doesn't seem specific enough to tell me what it does. magnetometer_compass seems a lot better though.

Okay, I'll do the rename of compass to magnetometer_compass ;)

The rename is complete and this PR has been updated with the changes.

@clalancette mind having a second look?

authors: clalancette peci1 sloretz


text:
On windows (via robostack) can't find connext implementation

I'm trying to setup the rmw_connextdds on windows (64bit) and during compilation of a CPP package it complains that it can't find the implementation
 CMake Error at C:/bh_test/.pixi/env/Library/share/rmw_implementation_cmake/cmake/get_default_rmw_implementation.cmake:60 (message):
[4.454s]   Could not find ROS middleware implementation 'rmw_connextdds'.  Choose one
[4.454s]   of the following: rmw_fastrtps_cpp, rmw_fastrtps_dynamic_cpp

I am using a conda pre-compiled rmw_connextdds version provided by robostack. I installed this using pixi tooling (https://prefix.dev/docs/pixi/overview)
Pixi will set up a virtual environment and automatically runs prescribed activation scripts. A minimal pixi.toml to set up the environment with connextdds.
[project]
name = "connextdds"
version = "0.1.0"
description = "test"
authors = []
channels = ["conda-forge", "robostack-staging"]
platforms = ["win-64"]

[target.win-64.activation]
scripts = ["connext_dds.bat", ".pixi/install/setup.bat"]

[tasks]
build = {cmd="colcon build --merge-install --build-base .pixi/build --install-base .pixi/install --cmake-args -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DPython_EXECUTABLE=$CONDA_PREFIX/python -DPython3_EXECUTABLE=$CONDA_PREFIX/python" }
test = {cmd="colcon test --merge-install --build-base .pixi/build --install-base .pixi/install"}

[dependencies]
# Base
python = "3.10.*"
# ROS
ros-humble-desktop = "0.10.*"
ros-humble-rmw-connextdds = "*"
ros-humble-rmw-connextdds-common = "*"
ros-humble-rti-connext-dds-cmake-module = "*"

# Build Tools
cmake = "*"
pkg-config = "*"
make = "*"
ninja = "*"
colcon-common-extensions = "*"
catkin_tools = "*"

# Platform dependent build chain
[target.win-64.dependencies]
vs2022_win-64 = "19.*"

Where the connextdds.bat is
call "c:\Program Files\rti_connext_dds-6.0.1\resource\scripts\rtisetenv_x64Win64VS2017.bat"
set RMW_IMPLEMENTATION=rmw_connextdds
set CONNEXTDDS_DIR=${NDDSHOME}

Sorry, I'm not super familiar with Robostack or Pixie.  I'll suggest you open up an issue using the guidelines at https://robostack.github.io/support.html

I have asked on the gitter from robostack, but seems nobody there has experience with the connextdds.
robostack is just a set of precompiled binaries to work in a virtual environment. Pixi is just a tool to manage that virtual environment.
What could be the cause for the implementation not being found? Does c:\Program Files\rti_connext_dds-6.0.1\resource\scripts\rtisetenv_x64Win64VS2017.bat expect a system wide path and not limited to a virtual environment? Do certain ROS packages need to be rebuilt? is it sensitive to MSVC version?
All the environment variables set by rtisetenv_x64Win64VS2017.bat are set inside the virtual environment

@mjcarroll would you be willing to try this on a windows machine? 🧇

source: gharchive/issue

authors: clalancette sloretz tony-p


text:
Cross-Distro/Vendor communication in ROS 2

There has been some questions and discussion related to cross-vendor and cross-distro communication support in ROS 2.

https://answers.ros.org/question/341372/can-nodes-from-different-ros-2-distributions-communicate-compatibly/
https://discourse.ros.org/t/ros-cross-distribution-communication/27335

And the answer is NO for both cases. currently ROS 2 does not support any cross-distro or cross-vendor communication officially. (which is my understanding, if i am mistaken, let me know) some of these cases are implemented in test code, but that does not mean that we support these compatibility.
No matter this is being current limitation or specification, it would be probably nice to describe clearly that is not supported in ROS 2 documentation officially? So that we can avoid potential unexpected problems and questions in the future.
Adding documentation would not be good enough to guarantee to avoid these cases, maybe we can add warning if the communication takes place with different distro or vendor implementation at runtime.
This topic was from today's MW WG meeting. (CC: @wjwwood @alsora @asorbini @ros2/middleware_working_group )
Related but out of scope from this issue:

Service Interoperability with different RMW implementation

CC: @MiguelCompany @clalancette @eboasson

And the answer is NO for both cases. currently ROS 2 does not support any cross-distro or cross-vendor communication officially. (which is my understanding, if i am mistaken, let me know) some of these cases are implemented in test code, but that does not mean that we support these compatibility.

So I guess it depends on what we mean by "support".  We know (and test) that we can publish topics between all 3 of our in-core DDS vendors (Fast-DDS, Connext, and CycloneDDS).  I also happened to test today that we can call services between Fast-DDS and Connext (but not with CycloneDDS) (this also implies that actions should work between Fast-DDS and Connext, though I did not test that).
So with the two exceptions of services Fast-DDS <-> CycloneDDS and services Connext <-> CycloneDDS, all of the rest of it should work.  The question is whether we want to officially call that supported or not.

FYI, as of ROS 2 Galactic sending a service request using CycloneDDS to a Fast-DDS application results in a crash during deserialization of the packet.
I think that @MiguelCompany is working on making it reject the data, rather than crash.
IMO unless we guarantee that everything works between all Tier 1 middlewares, we should discourage users to not even try to mix middlewares.
The same applies for communication between distributions.
For example, by default we could print very loud warnings if someone is mixing stuff.
An environment variable could be set by advanced users who are explicitly looking for cross-communication.
Trying to use different versions of ROS or different middlewares (by mistake!) are some of the most common causes of the issues reported by Create 3 (and Turtlebot 4) users.

So for the service interoperability, there is another issue open. I've understood from @gavanderhoorn (who BTW has rightfully been bugging me about it) that it really is necessary because of some devices only supporting middleware 1 and the other only middleware 2, and yet they have to be combined into a single system. The only way forward is therefore to agree on a portable way of doing service invocations.
I promised him that I'd try to come up with a proposal that might be agreeable to both @MiguelCompany and myself — the idea being that open source tier 1 parties ought to band together, and not let the commercial people try to bully us into something we don't want.
To me, the only sensible path forward is to do something that builds on top of the (spec'd) DDS API and respects the layering at the DDS level. Cyclone's RMW implementation currently meets this requirement, the only trickery it requires is encapsulating the ROS service payload in a slightly larger message. I believe the separate service type support exists precisely to make this possible — and doing it in a cleaner way than what the Cyclone RMW layer does.
The downside on the higher levels of the stack of doing the layering properly is (or might be) that the transformation between application data and DDS data becomes more involved and that zero-copy becomes impossible. I don't think that additional overhead would be a big deal for service invocations.
On the lower level of the stack, it adds some wire overhead in that it means you can't re-use the sequence number used by the reliable protocol for the request, and that you may decide to also add a unique client identifier to the header. For the reply, I don't think there is a material wire overhead.
About the identifier: you can basically chose to reuse the identifier of, e.g., the client's writer, or you can create a new unique id for that. Reusing means you already know the GUID from the low-level protocol machinery and it is accessible from the API, so it meets my layering constraint while avoiding a few bytes of overhead. Nonetheless, adding a new unique id is, in my view, a solution that more cleanly separates the concerns and avoids some order dependencies on creating the reader/writer pair for a client.
Since I have failed to do as I promised @gavanderhoorn ... perhaps we can just use this latest trigger to finally do something about it. Of course I'd be happiest if @MiguelCompany would be happy to rework the rmw_fastrtps_cpp implementation to match Cyclone's, but that's probably a stretch and the way forward is to share the pain a bit.
I don't think this ticket is necessarily the place for that discussion. I did feel it unacceptable to not at least do something to make good on that promise of mine ...

it really is necessary because of some devices only supporting middleware 1 and the other only middleware 2, and yet they have to be combined into a single system.

@eboasson totally agree.

For example, by default we could print very loud warnings if someone is mixing stuff.

@alsora yeah, that was the idea. and i think documentation and warning would do some work, we user still can try with warning message if we want to.

So I guess it depends on what we mean by "support".

@clalancette i take support is if issue happens that is the bug we must fix? i think that it still makes sense to add doc like cross-distro and cross-vendor communication is not supported officially. some might work but it is anti-pattern and not recommended.
I do not have detailed implementation idea how to add the warning though...

@clalancette i take support is if issue happens that is the bug we must fix? i think that it still makes sense to add doc like cross-distro and cross-vendor communication is not supported officially. some might work but it is anti-pattern and not recommended.

See, I think that is the wrong way to go.  We are essentially taking current bugs (inter-service operability between CycloneDDS and our other RMWs), and upgrading them to policy.  I think we should be going the opposite way; attempting to make these interoperable (with tests), so that we can officially claim that cross-vendor compatibility is supported.  If we don't allow this, then we are making it difficult to produce a robot running ROS 2 that can be communicated from outside the robot.
With that in mind, my proposal for this would be the following:

Re-enable tests in https://github.com/ros2/system_tests/tree/rolling/test_communication that test cross-vendor service calls between Fast-DDS and Connext.
In the special case of CycloneDDS, add a warning in rmw_cyclonedds_cpp when connecting to it from a non-CycloneDDS peer.  That warning would say something like "services don't currently interoperate, this may or may not work".
Update our documentation to point out that the special case of CycloneDDS doesn't work.

We are essentially taking current bugs (inter-service operability between CycloneDDS and our other RMWs), and upgrading them to policy.

ah, that is true, there is already issue and discussion taking place.

I think we should be going the opposite way; attempting to make these interoperable (with tests), so that we can officially claim that cross-vendor compatibility is supported.

totally good to go for cross-vendor communication. and your proposal makes sense to me to support cross-vender communication.
what about cross-distribution communication? according to current API/ABI management, i do not think this can be supported?

@clalancette i take support is if issue happens that is the bug we must fix? i think that it still makes sense to add doc like cross-distro and cross-vendor communication is not supported officially. some might work but it is anti-pattern and not recommended.

See, I think that is the wrong way to go. We are essentially taking current bugs (inter-service operability between CycloneDDS and our other RMWs), and upgrading them to policy. I think we should be going the opposite way; attempting to make these interoperable (with tests), so that we can officially claim that cross-vendor compatibility is supported. If we don't allow this, then we are making it difficult to produce a robot running ROS 2 that can be communicated from outside the robot.
With that in mind, my proposal for this would be the following:

Re-enable tests in https://github.com/ros2/system_tests/tree/rolling/test_communication that test cross-vendor service calls between Fast-DDS and Connext.
In the special case of CycloneDDS, add a warning in rmw_cyclonedds_cpp when connecting to it from a non-CycloneDDS peer.  That warning would say something like "services don't currently interoperate, this may or may not work".
Update our documentation to point out that the special case of CycloneDDS doesn't work.

I do need to point out here that we (the Eclipse Cyclone DDS project) do not consider it a bug. There never was any expectation of service interoperability in the past, there never was a concrete proposal on how to implement it in an interoperable manner (other than some handwaving in some call that I recall), and we are the only ones who do it without requiring support for yet another bad specification (RPC over DDS). When all the pros and cons are considered of the various options, you'll find that that bad specification adds exactly nothing to the end result.
What we do consider a bug is that service interoperability was ignored in ROS 2 from day one. A proper path to addressing that is something we're happy to be involved in, but simply expecting us to abide by the technical choices of others where we strongly believe those choices to be bad is not the way.
If you wish to pin it on Cyclone DDS and state that it doesn’t work, i.e., “is broken”, that is your good right. It is not an attitude that would motivate us to “fix” things.

If you wish to pin it on Cyclone DDS and state that it doesn’t work, i.e., “is broken”, that is your good right. It is not an attitude that would motivate us to “fix” things.

Apologies, my intention was not to call out Cyclone DDS.  From my perspective, I didn't really know that DDS didn't have a standard for a long time, and that there was contention about the standard that exists.
I'm honestly not sure of a way forward (which I guess is why we've been in this situation for a long time).  It seems like Fast-DDS and Connext both implement the standard that exists (as flawed as it may be).  Cyclone implements something potentially better, but which is not standardized.  Some ways forward I see are:

Have ROS 2 define the standard (as you suggest), and then implement it in the all of the RMWs.
Have Cyclone implement the (contentious) standard as an option, either in the RMW layer or in Cyclone itself.

I take it that Erik is in favor of 1.  @eboasson just for my information, is there any potential for 2?  Also do you have any other ideas on a way forward here?

we are the only ones who do it without requiring support for yet another bad specification (RPC over DDS). When all the pros and cons are considered of the various options, you'll find that that bad specification adds exactly nothing to the end result.

@eboasson I am trying to catch up with this. this has been explained in https://github.com/ros2/rmw_cyclonedds/issues/184? (which is almost 3 years old...) specifically on this comment https://github.com/ros2/rmw_cyclonedds/issues/184#issuecomment-630679396?

This issue has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/ros-2-tsc-meeting-minutes-2023-02-16/29927/1

https://github.com/ros2/ros2_documentation/pull/4736 is merged, i will close this issue.

authors: alsora clalancette eboasson fujitatomoya ros-discourse


text:
[ROS2] "no such command" for using "colcon build --merge-install" on Windows 10

Hi guys,
I am learning about ROS2 on Windows 10 today.
I tried using the command "colcon build --merge-install", as the tutorial said

But the terminal showed "no such command" for colcon.
Any answer or idea will be appreciated!

Please ask these kinds of questions on https://answers.ros.org.  That way they are all in one place and are easily searchable later.  Thanks.  I'll close this out for now.

Hi @clalancette , I have asked this question in https://answers.ros.org, but until now, there has been no one who answered my question.

@songyuc you have to wait more than two hours most of the time.

@christianrauch , thanks for your tip.
I will check the ROS Answers tomorrow.

I have asked this question in https://answers.ros.org

@songyuc If you make a statement like this then also use a link to point to your question and don't expect readers to go and search for your question.

authors: christophebedard clalancette dirk-thomas songyuc


text:
feat: make markdown headings distinguishable with treesitter

Might fix #228
This pr simply defines the treesitter highlight groups @markup.heading.*.markdown and @markup.heading.*.marker.markdown to make different levels of markdown headings distinguishable when treesitter is enabled on markdown files.

Thank you 💜

authors: TinusgragLin mvllow

repo: rose-pine/neovim

license: MIT


text:
Binder information could be added to docs

The binder link can be added to examples/tutorials section of the docs. The binder link is quite useful as an introduction.
Also, it would be great if the notebooks are named numerically, so as to give the user an idea about how to progress in the examples.
These are not blocking acceptance of the journal, just my suggestions. Fell free to ignore/implement them.

Hi there @srmnitc !
We have added this line to the docs webpage:

I have also renamed the examples:

authors: raphaeltimbo srmnitc

repo: ross-rotordynamics/ross


text:
for iOS device generated this issue

MissingPluginException(No implementation found for method init on channel plugins.flutter.io/flutter_facebook_login)

Two things here:

plugins.flutter.io/flutter_facebook_login is not part of my namespace. the proper one is com.roughike/flutter_facebook_login, did you change the code around?
you have to do a full restart after adding the dependency - hot reload is not enough for plugins.

authors: Pratiksol roughike


text:
🛑 Fossil based IRC Log is down

In 453589a, Fossil based IRC Log (https://rouilj.dynamic-dns.net/fossil/roundup_irc_logs/doc/trunk/log/roundup/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Fossil based IRC Log is back up in 65f7ea1.

repo: rouilj/RoundupAssets


text:
🛑 Silico Rubber Polymers is down

In de2d8c5, Silico Rubber Polymers (https://silicorubberpolymers.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Silico Rubber Polymers is back up in 968193b after 6 minutes.

repo: rpharaniya/websites-uptime-monitor


text:
Segfault on 4.2.4

With version 4.2.4 python scripts segfault after creating an Adafruit_NeoPixel instance.
Python 3.7.5 (default, Nov  7 2019, 10:50:52)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import rpi_ws281x
>>> rpi_ws281x.Adafruit_NeoPixel(0, 0)
<rpi_ws281x.rpi_ws281x.Adafruit_NeoPixel object at 0x7f2fff132110>
>>> exit()
zsh: segmentation fault (core dumped)  python

Same behavior in the python:3 container from dockerhub (python version 3.8.2).

Try using PixelStrip object (in examples/strandtest.py) instead of Adafruit_NeoPixel.
If that doesn't work for you, check #47

PixelStrip gives me the same behavior. Not very surprising, as they are both pretty much the same class.
Python 3.7.5 (default, Nov  7 2019, 10:50:52)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import rpi_ws281x
>>> rpi_ws281x.PixelStrip(0,0)
<rpi_ws281x.rpi_ws281x.PixelStrip object at 0x7f2dfa8012d0>
>>> exit()

Building the library myself did not fix the issue either.
Currently I am simply using 4.2.3.

Try supplying more parameters to the object's construcor then?
Dumb suggestion but may work

import rpi_ws281x

LED_COUNT = 16  # Number of LED pixels.
LED_PIN = 10  # GPIO pin used. 10: SPI, 18: PWM (used for sound)
LED_FREQ_HZ = 800000  # LED signal frequency in hertz (usually 800khz)
LED_DMA = 10  # DMA channel to use for generating signal (try 10)
LED_BRIGHTNESS = 255  # Set to 0 for darkest and 255 for brightest
LED_INVERT = False  # True inverts the signal (when using NPN level shift)
LED_CHANNEL = 0  # set to '1' for GPIOs 13, 19, 41, 45 or 53

rpi_ws281x.Adafruit_NeoPixel(
    LED_COUNT, LED_PIN, LED_FREQ_HZ, LED_DMA, LED_INVERT, LED_BRIGHTNESS, LED_CHANNEL,
)

This is how I'm using it. Still same behavior on 4.2.4.

Weird... Maybe specifying your hardware may help?

I'm having the exact same issue on a raspberry pi zero.
`Fatal Python error: Segmentation fault
Current thread 0xb6f04010  (most recent call first):
File "/usr/local/lib/python2.7/dist-packages/rpi_ws281x/rpi_ws281x.py", line 54 in setitem
File "/usr/local/lib/python2.7/dist-packages/rpi_ws281x/rpi_ws281x.py", line 143 in setPixelColor
File "/root/rpi_ws281x/python/lightstest/lights.py", line 40 in rainbowCycle
File "lightstest/server.py", line 13 in
Segmentation fault`

Following up on this, I've examined @jonathanhacker 's code and it looks like I was missing the following method call on my strip:

Closed as stale and (hopefully?) solved.

authors: Gadgetoid jonathanhacker jrknight storca


text:
🛑 dm.vern.cc is down

In 3c28a24, dm.vern.cc (https://dm.vern.cc) was down:

HTTP code: 0
Response time: 0 ms

Resolved: dm.vern.cc is back up in 90f3194 after 7 hours, 2 minutes.

repo: rramiachraf/dumb-instances


text:
how to watch provider with hooks_riverpod package?

Hi.
I'm using the below versions:
flutter_hooks: ^0.17.0
hooks_riverpod: ^0.14.0+4

I know with the flutter_riverpod package:

I can extends my class from ConsumerWidget to have a ScopedReader watch argument in the build(context, watch) mehod.
I can wrap my widget by the Consumer widget to have watch object in its builder.

Questions:
why there is not any HookConsumerWidget class at the hooks_riverpod package?
So how can I watch a provider with the hooks_riverpod?
Do I have to use Consumer widget again?
I think documentation is not updated.

There is a HookConsumerWidget
https://github.com/rrousselGit/river_pod/blob/master/packages/hooks_riverpod/lib/src/consumer.dart#L10

You can use useProvider instead of watch:
https://pub.dev/documentation/hooks_riverpod/latest/hooks_riverpod/useProvider.html

The documentation is using the version 1.0.0-dev.7, which changed the syntax by removing useProvider in favour of HookConsumerWidget.
You used the version 0.14.x, hence the problem. So this is expected :)

authors: BigGitWorld jeanbatm rrousselGit smiLLe

license: mit

license_source: bigquery


text:
Include multiple arguments for heading, fov, and pitch

Include multiple arguments for Command Line Interface (CLI) to accept all combinations of heading, fov, and pitch.
For example:
google_streetview --location=46.414382,10.013988;46.414382,10.013988;40.720032,-73.988354 --heading=0;90;180;270 --fov=0;90;120 --pitch -90;0;90

Given 2 locations, 4 headings, 3 fovs, and 3 pitches, the number of images returned from all possible combinations is:
2 x 4 x 3 x 3 = 72 images

The multiple heading parameter is useful for creating panoramic imagery (with rotations from 0 to 270 degrees assuming a fov of 90).

Now implemented in v1.1.0


text:
Need to add test cases for helping.

@yw662 增加一些测试用例会很有帮助～

我是和ngx_http_lua_module一起用的，测试都是在lua里面写的subrequest
https://gitlab.com/yw662/openresty_with_sqlite
如果要用travis测试的话，就要开一个服务器，然后让测试脚本发请求了吧

@yw662
我增加测试用例，可以帮助验证问题，下面链接是一个例子
https://github.com/rryqszq4/ngx_sqlite/blob/master/t/001-database.t

@yw662 使用的测试库 https://github.com/openresty/test-nginx


text:
Check if provider is set first, then disconnect

Fixes an issue where the modal will not close when the provider is undefined.

Pull Request Test Coverage Report for Build 921219925

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.0%

Totals

Change from base Build 895515318:
0.0%

Covered Lines:
0

Relevant Lines:
39

💛  - Coveralls

authors: coveralls jessgusclark

repo: rsksmart/rLogin


text:
Add RIF Faucet as a known address in testnet.

This should work for both the EOA and Relay versions as the address is the same.
Example:

Merging into us-2005

@jormelCoin I can rebase again, but what you are seeing is not caused by this PR, that was done elsewhere.

repo: rsksmart/rif-wallet


text:
rename S0006 "emergency state" to "emergency route"

The S0006 status is intended to  provide the emergency routes set with M0005.

this is only a change in the docs, not in the message itself, so not a breaking change.

The draft has been updated with this PR: https://github.com/rsmp-nordic/rsmp_schema/pull/78
Closing this issue

authors: emiltin otterdahl


text:
err test node

No robot footprint model specified for trajectory optimization. Using point-shaped model.
0x2c7f230 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x20d7fb0) ): Attempt to set a screen on a child window.
0x2c7f6b0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x20d7fb0) ): Attempt to set a screen on a child window.
0x2c7b020 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x20d7fb0) ): Attempt to set a screen on a child window.
0x2c7a4c0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x20d7fb0) ): Attempt to set a screen on a child window.
[rviz-3] process has died [pid 4901, exit code -11, cmd /opt/ros/kinetic/lib/rviz/rviz -d /home/a/zxy/catkin_ws/src/teb_local_planner-kinetic-devel/cfg/rviz_test_optim.rviz __name:=rviz __log:=/home/a/.ros/log/e5b15ba8-6037-11e9-8427-88b11143c0c4/rviz-3.log].
log file: /home/a/.ros/log/e5b15ba8-6037-11e9-8427-88b11143c0c4/rviz-3*.log

Closing this since it is obviously related to #127. Please add a comment if I am wrong ;-)

authors: croesmann xiaoyuanzh


text:
Modal Form closes when pressing enter key on Search Box

Hi,
When trying to input some text in search box of the bootgrid and press enter. The entire modal form closes.
How can enter key be disabled when searching.
Thanks,
/gmr

Got it!
$("input:text").keypress(function(event) {
if (event.keyCode == 13) {
event.preventDefault();
return false;
}
});

repo: rstaib/jquery-bootgrid


text:
move add/remove Autoload to enable/disable plugin

Hi!
I made it so the Autoload is being added when the plugin is enabled and removed when disabled instead of every time Godot opens/closes.
This fixes the error messages printed in the console every time Godot starts (unfortunately, the errors still remain if the plugin is disabled) and stops the Autoload from moving to the bottom of the list by itself
Side effect: users who update from a previous version will have to disable and re-enable the plugin once.

Hi, thank you for your contribution! I didn't know of those two entrypoints for plugins, but indeed the changes seems sensible.
However, I'm not seeing any "error messages printed in the console every time Godot starts", nor do I see the ControllerIcons autoload "moving to the bottom of the list by itself" either. Could you provide more details on such errors and/or show this issue ocurring in your setup?
I think the changes make sense and I'm happy to merge them as-is, but I'd like to confirm such issues and ensure this does properly fix them, more as a precaution :slightly_smiling_face:

I'll happily share a video of those happening as well as the exact text printed on the console once I get back home from my day job. For now all I can do is let you know the behavior only happens if you close Godot and reopen it, not if you simply reload the project.

So, I did some further investigation, and it only seems to happen on my project and only if I also have Dialogic enabled. I tried to copy both plugins to a new project and everything works as expected.
As promised, here's the video:
https://github.com/rsubtil/controller_icons/assets/75632714/f0fd0499-af21-41dc-a0b1-c9025e28019b
(ignore the black square in the top left, it's from another plugin)
and the output of the console:
Godot Engine v4.2.2.stable.official (c) 2007-present Juan Linietsky, Ariel Manzur & Godot Contributors.
--- Debug adapter server started ---
--- GDScript language server started on port 6005 ---
  res://addons/controller_icons/objects/path_selection/InputActionSelector.gd:68 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/path_selection/InputActionSelector.gd:71 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/path_selection/InputActionSelector.gd:71 - Parse Error: Cannot infer the type of "default_actions" variable because the value doesn't have a set type.
  res://addons/controller_icons/objects/path_selection/InputActionSelector.gd:78 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  modules/gdscript/gdscript.cpp:2726 - Failed to load script "res://addons/controller_icons/objects/path_selection/InputActionSelector.gd" with error "Parse error". (User)
  res://addons/controller_icons/objects/path_selection/SpecificPathSelector.gd:81 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  modules/gdscript/gdscript.cpp:2726 - Failed to load script "res://addons/controller_icons/objects/path_selection/SpecificPathSelector.gd" with error "Parse error". (User)
  res://addons/controller_icons/objects/ControllerIconTexture.gd:107 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:109 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:114 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:114 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:116 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:116 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:137 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:165 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:166 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:167 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:167 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:168 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:168 - Parse Error: Cannot infer the type of "event" variable because the value doesn't have a set type.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:169 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:170 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:175 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:321 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconTexture.gd:324 - Parse Error: Identifier "ControllerIcons" not declared in the current scope.
  res://addons/controller_icons/objects/ControllerIconEditorInspector.gd:-1 - Compile Error:
  res://addons/controller_icons/plugin.gd:-1 - Compile Error:
  modules/gdscript/gdscript.cpp:2726 - Failed to load script "res://addons/controller_icons/plugin.gd" with error "Compilation failed". (User)
  Parent node is busy setting up children, `add_child()` failed. Consider using `add_child.call_deferred(child)` instead.
Add Autoload
Remove Autoload
Add Autoload
Add Autoload


text:
Support large numbers and large sizes of changesets

Does this project support migration of large amounts of changesets, and large sizes of changesets? (we have changesets that contain hundreds of files)
Can I somehow fine-tune this process and improve running time? maybe by changing migration.properties parameters?

In principal this should be no problem. The way it works is that we create a git repo in a working folder, then checkout one change set at the time into this directory, then we add the changed files to the git repo and commit it using the time and committer informations of the RTC changeset

I understand the process, but could there be a scale issue?
I see there are few parameters in migration.properties regarding heap / cache / windows size, but couldn't find instruction of how to define them. Could you maybe elaborate?

As far as I remember our migration we increased the packedgitlimit from the default 10m to about 500m as suggested in the following stackoverflow article. That's also the only tuning hint I know about. I hope this helps a bit...

Thanks!

Hi, I have a very big project with large number of files and also changed the packagedlimit to 500m, but getting java.lang.outofmemoryerror java heap space. Any pointers here would be appreciated.

@himmakam Java OOM can be sorted by ensuring that JVM (Java Virtual Machine) arguments increasing the memory limit are passed to the JVM that's running the RTC CLI.
It'll be something like setting JAVA_OPTS=-Xmx4g or editing the "scm" script to include the argument "-Xmx4g" to do that.
Adjust "4g" (four gigs) to whatever is necessary - the default is pretty small.
FYI https://stackoverflow.com/questions/14763079/what-are-the-xms-and-xmx-parameters-when-starting-jvms has more info on what the argument means.  The rest is just "plumbing" to ensure that the parameter gets passed to Java when the command "java   " gets run.
I hope it works for you - I suspect I'm going to have to use this tool pretty soon myself...


text:
Delete profile or group flows

Problem

In order to respect GDPR we need the ability for users to remove all data we have stored on them

Solution
Add flows for deleting profiles & groups including email confirmations etc

@Manoj-nathwani Done.

Yes i'll deff do it BEFORE launch

Thanks for sorting out the front-end :)

Duplicate of #304

authors: Manoj-nathwani sebgrebe taymonbeal

repo: rtcharity/hubreboot


text:
Unspecified error in building docs

Issue
I have the same problem with two repositories, namely, that the builds will not complete and only show the error message "Build failed: an unexpected error occured". Here is an example from the Tiko'n repository:
https://readthedocs.org/projects/tikon/builds/5945523/
Interestingly, occasionally the builds will work on a translation of the same project (but not replicably so-- a few days ago the "Urdu" translation (actually still in Spanish) was working, but now the Tamil translation is working instead):
Tamil version logs:
https://readthedocs.org/projects/tikon-ta/builds/
Urdu version logs:
https://readthedocs.org/projects/tikon-ur/builds/

Project URL: see above
Build URL (if applicable): see above
Read the Docs username (if applicable): julien.malard

Expected Result
Built documentation.
Actual Result
Unspecified error.

Addressed this in #3073. I'll close this one as a duplicate issue.

authors: agjohnson julienmalard


text:
Replicate does not seem to work with Rails 4.2.3 and Ruby 2.2.2

Hi,  Replicate gem looks awesome and seems the right thing for selectively copying data from prod to my devel db. However, either I am not following the steps correctly or replicate does not work with Rails 4.2.3. In either case, will appreciate your help. Here is what I did:

Added gem 'replicate' to my Gemfile
Added a config/replicate/dump.rb file that requires 'config/environment' and added simple code to dump Company.find(16)
Ran the following command on my production DB machine:
RAILS_ENV=prod replicate -r ./config/environment -d config/replicate/dump.rb > dumped_data

When I do this, I get the following error:
/var/www/fbdash/releases/20151124123929/config/application.rb:47:in <class:Application>': undefined method []' for nil:NilClass (NoMethodError)
from /var/www/fbdash/releases/20151124123929/config/application.rb:17:in <module:AdIQ>' 	from /var/www/fbdash/releases/20151124123929/config/application.rb:16:in <top (required)>'
from /var/www/fbdash/releases/20151124123929/config/environment.rb:2:in `require'
My application.rb snippet looks like this:
...
LIne 46: redis_config = YAML.load_file(Rails.root + 'config/redis.yml')[Rails.env]
Line 47: url_prefix = redis_config['url_prefix']
db = redis_config['cache_db']
I am not sure why it is not picking redis_config as the prod app works just fine.

Any update on this? @rtomayko can you please help ?

Hmm, yeah it looks like redis_config is nil. Maybe try RAILS_ENV=production instead of "prod"? This smells like a general environment loading issue.

Thanks @rtomayko for the quick response. My bad for the typo. After giving RAILS_ENV=production, I get the following error. Do I need to explicitly need to give dump_replicants for each AR class? I thought replicate gem handles that automatically?
/var/www/fbdash/shared/bundle/ruby/2.2.0/gems/replicate-1.5.1/lib/replicate/dumper.rb:85:in block in dump': Company must respond to #dump_replicant (NoMethodError) 	from /var/www/fbdash/shared/bundle/ruby/2.2.0/gems/replicate-1.5.1/lib/replicate/dumper.rb:78:in each'
from /var/www/fbdash/shared/bundle/ruby/2.2.0/gems/replicate-1.5.1/lib/replicate/dumper.rb:78:in dump' 	from /var/www/fbdash/shared/bundle/ruby/2.2.0/gems/replicate-1.5.1/lib/replicate/dumper.rb:60:in block in load_script'
from config/replicate/dump.rb:4:in load_script' 	from /var/www/fbdash/shared/bundle/ruby/2.2.0/gems/replicate-1.5.1/lib/replicate/dumper.rb:61:in instance_eval'
from /var/www/fbdash/shared/bundle/ruby/2.2.0/gems/replicate-1.5.1/lib/replicate/dumper.rb:61:in load_script' 	from /var/www/fbdash/shared/bundle/ruby/2.2.0/gems/replicate-1.5.1/bin/replicate:77:in block in <top (required)>'
from /var/www/fbdash/shared/bundle/ruby/2.2.0/gems/replicate-1.5.1/lib/replicate/dumper.rb:28:in block in initialize' 	from /var/www/fbdash/shared/bundle/ruby/2.2.0/gems/replicate-1.5.1/lib/replicate/emitter.rb:9:in initialize'
from /var/www/fbdash/shared/bundle/ruby/2.2.0/gems/replicate-1.5.1/lib/replicate/dumper.rb:26:in initialize' 	from /var/www/fbdash/shared/bundle/ruby/2.2.0/gems/replicate-1.5.1/bin/replicate:70:in new'
from /var/www/fbdash/shared/bundle/ruby/2.2.0/gems/replicate-1.5.1/bin/replicate:70:in <top (required)>' 	from /home/deploy/.rvm/gems/ruby-2.2.2/bin/replicate:23:in load'
from /home/deploy/.rvm/gems/ruby-2.2.2/bin/replicate:23:in <main>' 	from /home/deploy/.rvm/gems/ruby-2.2.2/bin/ruby_executable_hooks:15:in eval'
from /home/deploy/.rvm/gems/ruby-2.2.2/bin/ruby_executable_hooks:15:in `'

it requires to declare this method on all models,
so ive added to my base model
def dump_replicant(dumper, opts={})
fields = attribute_names
dumper.write self.class, id, fields, self
end
but for some reason, the data being exported and imported without values.
ive many rows without values in most of the fields

authors: ankuriitk rtomayko u007

repo: rtomayko/replicate


text:
No output

Hi,
Thanks for this project! I successfully compiled the code and executed as mentioned, but there is no output at all. What kind of output is expected?
Tried to look with strace whats happening, but I could not find any output file written
Thanks for advice :)

Did you provide the executable the path to a valid Skype LevelDB path? It should be a the path to a directory that ends with: ".indexeddb.leveldb". By default the program should display all Skype contacts that are found in the LevelDB argument.

yes, did that. In those files I see some kind of json format, so there is data - maybe new format? thanks

I was not able to replicate this issue.
I know that the databases might contain confidential data, however, if you have a database that is safe to share can you please make an archive and provide it as a web download?

repo: rtravis/SkypeCacheViewer


text:
it can't extract .tmpl file

		nggettext_extract:{
			pot:{
				options:{
					startDelim:'##',
					endDelim:'##'
				},
				files:{
					'./lang/language.pot':['<%= config.src %>/web/**/*.html','<%= config.src %>/web/**/*.tmpl']
				}
			}
		},

i rename all template file in project with .tmpl,it can't trim it

You'll need to use the extensions option to map .tmpl files to html: https://github.com/rubenv/angular-gettext-tools/blob/a509df9d0d5d1c6ce4975d5f80b950cc95075463/lib/extract.js#L70-L79

Note that we can add it by default, but to do that, we need a sample file + unit test. Pull request in https://github.com/rubenv/angular-gettext-tools welcome!

so fast!with great thanks

and sorry...i dont konw how to write a unit test now

Closing this since it seems like you solved your issue.

authors: gabegorelick joebnb rubenv

repo: rubenv/angular-gettext


text:
add git describe task

Hi @rubenv ,
I added the git describe task.
https://git-scm.com/docs/git-describe
I hope you can merge this soon and publish an update on npm ;-)
If you have any remarks don't hesitate.
Kind regards,
Robin

Looks good, will roll release!

Released to NPM as v1.0.11. Thanks!

authors: RobinHerbots rubenv

repo: rubenv/grunt-git


text:
Fix false positive for relative file path runs with long namespaces (fixes #1091)

This is a PR that fixes the issue that is further explained at #1091.
This was broken by this commit included in the PR #869:
https://github.com/rubocop-hq/rubocop-rspec/commit/811ae08ea3a60453e18a8bcb9dfaefafd848f779#diff-5b709885b35566a0c699ad4a3200b9b7acbc28ef640fa56a8e66f6c732420a34
It turned out to be extremely difficult (at least I don't know how after multiple tries and experiments) to fix the issue described at #1091 using the file name globs. Therefore I switched to regular expression based matching which allows a more specific targeting for the case in question.
The removed specs originate from this commit in the PR #917:
https://github.com/rubocop-hq/rubocop-rspec/commit/23ad402fb3bd5149adc456ca3c54204c38fc271f#diff-5bc1941f9b92914876efec6f7fcc70b153e82194d960213a280078c6cb4b0c3a
The removed specs are no longer needed because it now uses absolute paths as it did prior to merging #869. I believe these were also issues introduced by #869.

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[ ] Squashed related commits together. - (:question: - couldn't you squash when merging?)
[x] Added tests.
[ ] Updated documentation.
[ ] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

If you have created a new cop:

[ ] Added the new cop to config/default.yml.
[ ] The cop is configured as Enabled: pending in config/default.yml.
[ ] The cop documents examples of good and bad code.
[ ] The tests assert both that bad code is reported and that good code is not reported.
[ ] Set VersionAdded in default/config.yml to the next minor version.

If you have modified an existing cop's configuration options:

[ ] Set VersionChanged in config/default.yml to the next major version.

[ ]  Squashed related commits together. - (❓ - couldn't you squash when merging?)

We don’t use GitHub’s “Squash and merge” option, since it fails to create a merge commit.

But I wonder if this PR works on Windows (do we need to split by File::SEPARATOR and join with '/' before calling #match?) or case sensitive filesystems.

Do we have any Windows users around?

Please add a Changelog entry, squash commits and I believe we're ready to merge.
Thanks once again!

@pirj Changelog added and commits are squashed.

But I wonder if this PR works on Windows (do we need to split by File::SEPARATOR and join with '/' before calling #match?) or case sensitive filesystems.

Do we have any Windows users around?

@bquorning I tested this under Windows and it seems to work fine there as is. This is because processed_source.buffer.name returns the filename with forward slashes also under Windows.

authors: ahukkanen bquorning pirj

repo: rubocop-hq/rubocop-rspec


text:
[Fix #3904] Build config & sync cop descriptions

This PR addresses #3904. It deduplicates Cop descriptions by loading the config and replacing its Descriptions with the ones held in yard. That makes the source code the single source of truth for descriptions. This was heavily inspired by @backus 's implementation in rubocop-rspec. (Thank you sir!)
There are a lot of consequences of loading and dumping YAML. Here are some of the changes you will find in config/default.yml that are noteworthy but (imo) seem ok.

Lists are not indented - ref: https://stackoverflow.com/questions/17014460/yaml-indentation-for-array-in-hash
single quotes are generally replaced with double quotes. This appears to be when the string contains special characters like * and #. They are not replaced in VersionAdded and VersionChanged settings.
Settings such as CacheRootDirectory: ~ are replaced with CacheRootDirectory: . I don't like this, but it's still valid yaml. It seems to boil down to aesthetic, though.
Descriptions include line feeds. This doesn't seem like a big deal because those line feeds are following the 80 character Metrics/LineLength setting enforced in the repo already. So comments will appear uniform in the file.

But. There is a deal breaking change here. All comments are stripped from the config. I looked around for a solution and only found ones involving adding comments in one line at a time. While searching for alternative yaml parsers besides YAML/Pysch,  I found this blog post which suggests the only comment preserving YAML parser is ruamel, which is for Python.
Possible solutions:

Move the comments into the config. Add keys such as AllowSymlinksInCacheRootDirectoryDescription and give it the associated comment as a value to save.
Don't mix these concerns. Put documentation in something else, designed for it, instead of a configuration file.
Explore trying to make all of these updates using other Ruby libraries such as File, instead of loading the config itself.
Something I haven't thought of. Have an idea?

Last note: I believe it is to our benefit to load config, make a change, and the dump it back out. After syncing descriptions, we could explore syncing any/all other values. Procedurally updating our configuration feels like a step in the right direction.
Thoughts and ideas?

Before submitting the PR make sure the following are checked:

[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] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

@Darhazer - Thanks for the comments! Any opinion on an approach to preserving the config comments? -- I'm leaning towards moving them directly into the config (option 1), but would love a thumbs up from a collaborator/owner before making such an update. -- @bbatsov , what do you think?

There are a lot of consequences of loading and dumping YAML. Here are some of the changes you will find in config/default.yml that are noteworthy but (imo) seem ok.

Why do you even load and dump it? I'd just merge the data from the config with whatever we get from the source file without actually regenerating the file itself.

@garettarrowood What's the state here?

@bbatsov -
I'm finding it difficult to update the yaml config file using Ruby File classes and not YAML libraries (because they all wipe away the code comments when the config is regenerated). It's possible to find the line in the config file to insert the cop's Description, and then insert it. But I have not yet found how to then detect the formatting/how many lines the outdated description is, and then remove it.
Perhaps there is a technique to go about this that has escaped me so far. I'm open to suggestions :).

Perhaps I could cycle through the file twice. The first time removing all the Descriptions. Then cycle through it again and add the ones from the cop files themselves.
It seems inefficient, and a lot of extra file operations than would be necessary. But I can give it a go again with that idea.

authors: bbatsov garettarrowood

repo: rubocop-hq/rubocop


text:
undefined method `size' for nil:NilClass (NoMethodError) when installing

I tried to install thread_safe version 0.3.5, but i got below error:
ERROR:  Error installing thread_safe:
	invalid gem: package is corrupt, exception while verifying: undefined method `size' for nil:NilClass (NoMethodError) in /home/vagrant/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/cache/thread_safe-0.3.5.gem

ruby version:
ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux]
gem version:
2.4.5

Hi, I've just tried install the gem on the same versions (but os x) and all seems to work. Could you try to delete the cached .gem file and reinstall again to eliminate possibility of corrupted files?

@pitr-ch Hi, Thanks for checking, I deleted cached .gem and tried again,  still got above error. but it works if i downgrade to 0.3.4

@lenage could you post here a backtrace of the error? gem install --backtrace could help.

@pitr-ch
vagrant@vagrant-ubuntu-trusty-64:~$ gem install thread_safe -v "0.3.5" --backtrace
ERROR:  Error installing thread_safe:
	invalid gem: package is corrupt, exception while verifying: undefined method `size' for nil:NilClass (NoMethodError) in /home/vagrant/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/cache/thread_safe-0.3.5.gem

Here are some informations:
$ uname -a
Linux vagrant-ubuntu-trusty-64 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:36:28 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"

$ env
XDG_SESSION_ID=5
TERM=xterm-256color
SHELL=/bin/bash
SSH_CLIENT=10.0.2.2 54044 22
SSH_TTY=/dev/pts/0
USER=vagrant
SSH_AUTH_SOCK=/tmp/ssh-ae4n9pMdHB/agent.20161
MAIL=/var/mail/vagrant
PATH=/home/vagrant/.rbenv/shims:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
PWD=/home/vagrant
LANG=en_US.UTF-8
SHLVL=1
HOME=/home/vagrant
LOGNAME=vagrant
SSH_CONNECTION=10.0.2.2 54044 10.0.2.15 22
LC_CTYPE=en_US.UTF-8
XDG_RUNTIME_DIR=/run/user/1000
_=/usr/bin/env
vagrant@vagran

@lenage Thank you for the detailed info! This is the first problem that's been reported so we'll look into this ASAP. I see that you are using Vagrant. :+1: I use Vagrant extensively at work and to build the concurrent-ruby gem. I'll setup a VM like yours to troubleshoot the error you are experiencing.

@lenage Are you using RVM or another Ruby version manager?

@lenage Thus far I have been unable to reproduce the error. I've setup an Ubuntu VM using vagrant. The version of Linux I used is:
vagrant@vagrant-ubuntu-trusty-64:~/ruby-2.2.1$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.2 LTS
Release:	14.04
Codename:	trusty

I installed MRI ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux] from source and was able to successfully install thread_safe using sudo gem install thread_safe -v "0.3.5" --backtrace. I also installed RVM rvm 1.26.11 (latest) and installed MRI ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux] under RVM. I was able to successfully install thread_safe using gem install thread_safe -v "0.3.5" --backtrace under that as well.
Can you please download the thread_safe-0.3.5.gem gem package directly from the GitHub release page and try to install it? As @pitr-ch suggested, you may have a corrupt file in your gem cache.

@jdantonio Yes, i'm using rbenv 0.4.0.
Thanks for the help, I downloaded the gem file in release page and it installed successfully.
gem i thread_safe-0.3.5.gem
Successfully installed thread_safe-0.3.5
Parsing documentation for thread_safe-0.3.5
Installing ri documentation for thread_safe-0.3.5
Done installing documentation for thread_safe after 0 seconds
1 gem installed

@lenage I just tried again with rbenv and was able to successfully install thread_safe, so I definitely think your cached gem package was corrupt. Let us know if you have any other problems.

authors: jdantonio lenage pitr-ch


text:
optional attributes are not being parsed as optional

I have the following schema:
{
  "type": "object",
  "required": ["twilio_account"],
  "properties": {
    "twilio_account" : {
      "type" : "object",
      "required" : [
        "twilio_account_id"
      ],
      "properties" : {
        "twilio_account_id": { "type": "integer" },
        "sid": { "type": ["string","null"] }
      }
    }
  }
}

My API response is as follows:
{"twilio_account":{"twilio_account_id":2}}
However when I run it through the validator it raises the error:
The property '#/twilio_account' did not contain a required property of 'sid'
I do happen to be using the validator in strict mode, however I've clearly specified which attributes are required. Are all still required?

@biznickman When you use strict mode, all properties are required, regardless of what you've specified in the required property. Perhaps you'd be better adding additionalProperties: false and not using strict mode.

authors: biznickman iainbeeston

repo: ruby-json-schema/json-schema


text:
SPARQL Grammar parsing regression on 1.1.7

A bug was introduced in sparql 1.1.7. See the script below:
require 'sparql'

query = <<-eos
  PREFIX ext:<http://ext.com/1.0#>

  CONSTRUCT {
      ?x ?prop ?obj .
      ?obj rdf:type ext:Subject .
    }
    WHERE {
      ?x rdf:type ext:Subject ;
        ?prop ?obj .
    }
eos

SPARQL::Grammar.parse(query).to_sxp

1.1.6 - OK
(prefix ((ext: <http://ext.com/1.0#>)) (construct ((triple ?x ?prop ?obj) (triple ?obj rdf:type ext:Subject)) (bgp (triple ?x rdf:type ext:Subject) (triple ?x ?prop ?obj))))
1.1.7 - KO
(prefix ((ext: <http://ext.com/1.0#>)) (construct ((triple ?x ?prop ?obj) (triple ?obj rdf:type ext:Subject)) (bgp (triple ?x rdf:type ext:Subject) (triple ?x <type[#<RDF::Query::Variable:0x1fa12b0(?prop)>]> ?obj))))

See if that fixes the issue you're seeing and I'll push out 1.1.8.

@gkellogg :+1:

authors: abrisse gkellogg

repo: ruby-rdf/sparql

license: unlicense


text:
[Diaper & Partner] Enable diaper banks to define special 'bundles' of items and send them.

Summary
Diaper banks want to define 'bundles' of items that they can use as units to send. For example, they may want to create and send  'COVID19' bundles which contain a predefined number of N95 masks and other sanitary products.
Let's build the capability to archive partners and remove the ability to delete them.
@mdworken @armahillo is there any added context or information needed here?
Criteria for Completion

[ ]  Add an interface that enables diaper bank users to create bundles
[ ]  Partners will be able to see and request bundles from diaper banks.

I am going to close this issue and leave it in our spreadsheet /w project initiatives. I'd like to get some more in-depth user research before diving into this.

repo: rubyforgood/diaper


text:
Update request feature spec to system spec

Summary:
Rails 5.1 introduced "System Tests", the brave new world of automated testing in Rails. It seems like this has been refined quite a bit and will become more prevalent in Rails 6.0. We'd like to get ahead of the curve on this.
Task:
We need to convert /spec/features/request_spec.rb from a feature spec to a system spec. There are 4 steps to this:

[ ] Create a similarly named file in the spec/system directory. For example if the file was called happy_spec.rb it would be called happy_system_spec.rb in the new directory.
[ ] Set each spec’s type as type: :System
[ ] Use RSpec.describe to define system specs, instead of RSpec.feature
[ ] Replace the scenario alias in previous feature specs with the standard it syntax

Two files have already been converted that you can use as examples -- the account_system_spec.rb spec and the adjustment_system_spec.rb spec. You can also see the original feature files at account_spec.rb spec and adjustment_spec.rb spec.
More information on system specs can be found below.
Reference

https://edgeguides.rubyonrails.org/testing.html#system-testing
https://relishapp.com/rspec/rspec-rails/docs/system-specs/system-spec
https://medium.com/table-xi/a-quick-guide-to-rails-system-tests-in-rspec-b6e9e8a8b5f6
https://dev.to/aergonaut/running-rails-5-system-tests-on-travis-ci-with-chromedriver-4nm7
http://blog.mechanicles.com/2018/03/04/gotchas-rails-system-testing.html
https://everydayrails.com/2018/01/08/rspec-3.7-system-tests.html

I'm working on this! 💖

authors: ejuten jenpen


text:
3765 disallowed request type bug

Resolves #3765
Description

Not much to report here!  The solution was already half addressed in the OrganizationUpdateService and just needed adjusted to allow for JSON input (changing conditional false to "false") and a way to add errors to the base object. I created an additional helper method to handle much of the logic that will collect any partners of the organization that may be considered edge cases given the condition of having no allowed request types.
One further thing to note is that the conditional to catch partners with all disallowed request types can handle catching and communicating errors for multiple partners at once.  For example, if you tried to turn off all request types through the organization's edit page, you'd receive an error that included every single partner name in it. (screenshots below)
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

There are tests in both spec/services/organization_update_service_spec.rb and spec/system/organization_system_spec.rb.
I made a slight adjustment in spec/services/organization_update_service_spec.rb to line 48 that would better mimic JSON format being passed from the frontend form (just adding quotation marks to false). This allowed me to correct the existing methods built to detect edge-case partners (with all disallowed requests). It was pretty easy to just add one additional expectation to that test file to ensure that there was an error message added to the organization in the case that the partner was an edge case.
As for spec/system/organization_system_spec.rb, I wanted to make sure that the error message did infact show up on the page as expected so that test is pretty self-explanatory.
Screenshots

Hey @dorner I went ahead and moved that boolean logic to a private controller method that helps out organization_params. All tests are passing.
My plan was to see if re-merging w/ main and then re-pushing would fix the lint issue before tackling... but didn't realize i needed approval for those workflows to run.
Happy to tackle the lint issue if it pops back up.

@torienyart unfortunately not only lint but a bunch of specs are failing. Can you take a look?

@dorner I'm on it!

Thanks for the patience here @dorner.  I just made a few rubocop fixes in my PR and re-ran checks on my up-to-date forked version with all passing checks. I am hoping this is good to go here now!

My hunch is this is unrelated to your PR, but here's how I got this test to pass:
          within ".modal-content" do
            fill_in "barcode_item_quantity", with: 3
            select Item.alphabetized.first.name, from: "barcode_item_barcodeable_id"
            sleep(0.1)
            click_button "Save"
          end

Adding the sleep, even for a tiny time, apparently lets the UI catch its breath and work correctly.

Alright, @dorner. Thanks for that suggestion, I implemented it for a few tests that were inconsistently passing on my end which seemed to solve the issue.
These tests include:
"User can create vendor from purchse" - purchase_system_spec.rb:111
and
"user can add items that do not yet have a barcode" - purchase_system_spec.rb:276
I tested it again against my up-to-date fork and received all passing checks. Hopefully, it translates here as well.

Nice - thanks for the hard work!

authors: dorner torienyart

repo: rubyforgood/human-essentials


text:
Apply acts_as_tenant to all appropriate models

So far it's only on the Pet model but it belongs on more models.

Closed by #69

repo: rubyforgood/pet-rescue


text:
Freshly generated --mode job app fails to send mails, missing ApplicationHelper

Checklist

[x] Upgrade Jets: Are you using the latest version of Jets? This allows Jets to fix issues fast. There's a jets upgrade command that makes this a simple task. There's also an Upgrading Guide: http://rubyonjets.com/docs/upgrading/
[x] Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a question, do so on https://community.rubyonjets.com
[x] Code sample: Have you put together a code sample to reproduce the issue and make it available?  Code samples help speed up fixes dramatically. If it's an easily reproducible issue, then code samples are not needed. If you're unsure, please include a code sample.

My Environment

Software
Version

Operating System
macOS Catalina 10.15.7

Jets
2.3.18

Ruby
2.7.0

Expected Behaviour

After generating a new project via --mode job, be able to then generate a mailer and send the mail via the console
Current Behavior
ApplicationHelper is not created with --mode job and therefor creates an error when attempting to send a mail. See the error log below for more info.

Step-by-step reproduction instructions
jets new mail_test --database=postgresql --mode job
jets generate mailer TestMailer test_mail
jets c
TestMailer::test_mail.deliver_now

Error Log
irb(main):006:0> TestMailer::test_mail.deliver_now
D, [2021-01-18T16:02:30.892923 #75972] DEBUG -- : TestMailer#test_mail: processed outbound mail in 8.5ms
Traceback (most recent call last):
       16: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/actionview-6.1.1/lib/action_view/lookup_context.rb:258:in `block in initialize_details'
       15: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/actionview-6.1.1/lib/action_view/lookup_context.rb:51:in `block in <class:LookupContext>'
       14: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/jets-3.0.2/lib/jets/core_ext/kernel.rb:11:in `require'
       13: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/zeitwerk-2.4.2/lib/zeitwerk/kernel.rb:34:in `require'
       12: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/zeitwerk-2.4.2/lib/zeitwerk/kernel.rb:34:in `require'
       11: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/actionview-6.1.1/lib/action_view/base.rb:12:in `<top (required)>'
       10: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/actionview-6.1.1/lib/action_view/base.rb:141:in `<module:ActionView>'
        9: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/actionview-6.1.1/lib/action_view/base.rb:279:in `<class:Base>'
        8: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.1.1/lib/active_support/lazy_load_hooks.rb:51:in `run_load_hooks'
        7: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.1.1/lib/active_support/lazy_load_hooks.rb:51:in `each'
        6: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.1.1/lib/active_support/lazy_load_hooks.rb:52:in `block in run_load_hooks'
        5: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.1.1/lib/active_support/lazy_load_hooks.rb:66:in `execute_hook'
        4: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.1.1/lib/active_support/lazy_load_hooks.rb:61:in `with_execution_control'
        3: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.1.1/lib/active_support/lazy_load_hooks.rb:71:in `block in execute_hook'
        2: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.1.1/lib/active_support/lazy_load_hooks.rb:71:in `class_eval'
        1: from /.../.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/jets-3.0.2/lib/jets/controller/rendering/rack_renderer.rb:220:in `block in setup!'
NameError (uninitialized constant ApplicationHelper)
Did you mean?  ApplicationMailer

Code Sample
Nothing was changed from a freshly generated app.
Solution Suggestion
Generate the ApplicationHelper when generating with --mode job

Changing to Ruby 2.5.8 fixed the issue

Changing to Ruby 2.5.8 fixed the issue

I have hit the same issue with the missing ApplicationHelper. Switching to Ruby 2.5.8 is not an option as it reached EOL. The proper solution is to generate app/helpers/application_helper.rb

Fixed in #674

authors: AlexeyDemidov tongueroo tyler-wel

repo: rubyonjets/jets


text:
feat: add custom pod labels and annotations

A small PR that adds the option to set custom pod level annotations and labels. This is helpful for some management applications or policies :)

A small PR that adds the option to set custom pod level annotations and labels. This is helpful for some management applications or policies :)

Hi @Demonsthere, LGTM thanks a lot!

authors: Demonsthere rueian

repo: rueian/gke-hubble-export


text:
open local sheet file

I got a sheet file which is json data from fortune-sheet. Is there any simple way (without writing some js code) to view it as spreadsheet not json?

Maybe you still need to use js code to change json to a specific format, and then apply it to the table.

authors: gazedreamily zhengpd

repo: ruilisi/fortune-sheet


text:
[Bug]: Import Error: cannot import name 'MessageContentText' from 'openai.types.beta.threads'

Bug Description
after importing OpenAIAssistantAgent from llama_index.agent.openai and use the class to create the agent, running the following snippet is not working:
agent = OpenAIAssistantAgent.from_new(
    name="QA bot",
    instructions="You are a bot designed to answer questions about tickets",
    openai_tools=[],
    tools=[summary_tool, vector_tool],
    verbose=True,
    run_retrieve_sleep_time=1.0,
)
response = agent.query("what is the destinations in the ticket?")
print(str(response))

this snippet giving me the following error:
ImportError: cannot import name 'MessageContentText' from 'openai.types.beta.threads' (/llm-test/pythonProject/.venv/lib/python3.12/site-packages/openai/types/beta/threads/__init__.py). Did you mean: 'MessageContentDelta'?

Version
llama-index = "^0.10.25"
Steps to Reproduce
To fix the Bug:
in the file:
/llama_index/agent/openai/openai_assistant_agent.py we can import TextContentBlock instead of MessageContentText
another error you will face is ImportError you can't import ThreadMessage so i just commented locally to fix it temporary and focusing on development.
Relevant Logs/Tracbacks
No response

You can assign this Issue to me and make it my first contribution in LlamaIndex 😜


text:
[Question]: I keep having issues when a react agent tries to use a tool

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
The question I asked it is "What's today's date"
I already created a simple function tool to answer this correctly to eliminate hallucination:
    def current_date(self) -> str:
        """
        Get current date

        args:
            None
        """
        return datetime.today().strftime('%B %d, %Y')

This is the output when I call agent.chat(...):
  Observation: Error: Could not parse output. Please follow the thought-action-input format. Try again.
  Thought: The current language of the user is: English. I need to use a tool to help me answer the question.
  Action: current_date
  Action Input: {'type': 'object', 'properties': AttributedDict()}
  Observation: Error: current_date() got an unexpected keyword argument 'type'
  Thought: The current language of the user is: English. I need to use a tool to help me answer the question.
  Action: current_date
  Action Input: {'type': 'object'}
  Observation: Error: current_date() got an unexpected keyword argument 'type'
  Thought: The current language of the user is: English. I need to use a tool to help me answer the question.
  Action: current_date
  Action Input: {}
  Observation: April 10, 2024
  Thought: Now that we know the current date, let's find out what day of the week it is.
  Action: current_date
  Action Input: {'type': 'object'}
  Observation: Error: current_date() got an unexpected keyword argument 'type'
  Thought: The current language of the user is: English. I need to use a tool to help me answer the question.
  Action: current_date
  Action Input: {}
  Observation: April 10, 2024
  Thought: Now that we know the current date, let's find out what day of the week it is.
  Action: query_tool
  Action Input: {'input': "What day is 'April 10, 2024'?"}

As you can see, sometimes it gets it, and sometimes it get's this:
  Action Input: {'type': 'object'}
  Observation: Error: current_date() got an unexpected keyword argument 'type'

it's always unstable, and sometimes it just hallucinates till it chooses the wrong tool and other times it get's to max iterations after running for a while.
Is there something I'm missing, or is this just a bug, also how can I fix it.

@brainiakk ReAct agents require an LLM to follow pretty careful instructions. Most LLMs (especially open source) are pretty bad at this. Its nothing wrong with any code, just the fact that the LLM you are using isn't capable enough to perform this type of action reliably

, **kwargs

I'm using dolphin-mistral, what would you recommend?

Also, even if I set max_iterations and it returns the right output, it just throws an error, do I need to change anything?
 agent = ReActAgent.from_tools(tools, llm=Settings.llm, verbose=True, context=self._prompt, max_iterations=2)

@logan-markewich I'm having some similar error messages as @brainiakk where it sometimes outputs:
Observation: Error: Could not parse output. Please follow the thought-action-input format. Try again.
Is this also down to the LLM choice? I've set a system prompt and am using Llama2 and it seems like the big versions of Llama2 are better at following instructions. But it feels weird to me since that error should throw an exception rather than be rolled into the LLM thought/observation process. When I see this message it just continues like nothing happened, sometimes have the same error multiple times in a row:
Observation: Error: Could not parse output. Please follow the thought-action-input format. Try again. Observation: Error: Could not parse output. Please follow the thought-action-input format. Try again. Observation: Error: Could not parse output. Please follow the thought-action-input format. Try again. Observation: Error: Could not parse output. Please follow the thought-action-input format. Try again.

I also got the same
Observation: Error: Could not parse output. Please follow the thought-action-input format. Try again.

So what fixed it for me was installing pytorch after everything else.
I'm using Pipfiles which resolves all the dependencies and I install all the packages using that first. But to not have the above error, I need to activate the virtual environment and do a manual pip install.
My steps are:
pipenv install
pipenv shell
pip install torch==2.2.1
I haven't tested if it works for 2.2.2 of pytorch and I'm unsure why this works and how it affects things but hopefully there's a clue somewhere. Maybe it's one of the dependency changes when I throw torch into my Pipfile.

Another thing I found is that having a reader package installed will cause the same problem. I'm using llama-index-readers-confluence and regardless of the version of that or pytorch I have, it results in the same issue with the error being part of the observation

Same issue. Most of the time it hallucinates and starts calling other tools even though the first tool has returned the answer which is required. Any help regarding modification of the reAct system prompt as i'm using custom functions in llama3 7b via ollama.

I'm struggling with this too and have same experience. Sometimes it answers but still tries to run another tool, which end up in a loop (Nano Mistral). Or is trying to use wrong params etc. I'm not really sure how it all corelates with model. Is it template issue, system params, parsing?
I can only tell that gemma2:9b is not bad for this. Sometimes it goes off rails. But if you can run 27b model, then go with it. It uses proper tools, answers based on it and uses proper params almost 0-shot (9b needs few tries).

I am running into this error too. I am using Llama 3.2-1b-instruct from HuggingFace (free tier) ...  Things were going great but now it's stuck here on every prompt. Did I just hit a limit with this model on HF?

authors: AdaptavistChak CashVo brainiakk kiruz-0 logan-markewich


text:
[Question]: Why doesn't response metadata capture the information always?

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I have used the basic chunking and loading the data to Postgres database with the code from the example - https://gpt-index.readthedocs.io/en/v0.8.47/examples/low_level/oss_ingestion_retrieval.html
Here is the the code
text_chunks = []
# maintain relationship with source doc index, to help inject doc metadata in (3)
doc_idxs = []
for doc_idx, doc in enumerate(documents):
    cur_text_chunks = text_splitter.split_text(doc.text)
    text_chunks.extend(cur_text_chunks)
    doc_idxs.extend([doc_idx] * len(cur_text_chunks))

text_chunks = []
# maintain relationship with source doc index, to help inject doc metadata in (3)
doc_idxs = []
for doc_idx, doc in enumerate(documents):
    cur_text_chunks = text_splitter.split_text(doc.text)
    text_chunks.extend(cur_text_chunks)
    doc_idxs.extend([doc_idx] * len(cur_text_chunks))

for node in nodes:     node_embedding = embed_model.get_text_embedding(         node.get_content(metadata_mode="all")     )     node.embedding = node_embedding vector_store.add(nodes)
Here the issue I am facing, after the retrieval of the context from the database, it is not returning the metadata or the documents name it extracted the information from
response_1.sourcenode[0].metadata =
[NodeWithScore(node=TextNode(id_='0fb55059-e6cf-403e-89f0-3a5560437afb', embedding=None, metadata={'file_name': 'covid census and mortality protocol v2.docx'},....] // has document name
response_2.sourcenode[0].metadata = [NodeWithScore(node=TextNode(id_='be4ac130-a4eb-47b6-8cac-e9c652b109ba', embedding=None, metadata={},] // no document name
both the response_1 and response_2 - contexts are chunked and stored in Postgres in with same logic
hoverever metadata is being populated for smaller datasets and it is not happening for larger datasets
is there anything I am missing?

@ram510 I am confused maybe, I don't see you setting any metadata in your nodes in the provided code samples?


text:
Readability web page reader fix playwright async api bug

Description
Playwright not working as it detects the asyncio loop in jupyter notebook.
Updated playwright and added nested asyncio loop as well as running loop sync so that it will work in scripts as well
Fixes # (issue)
New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[ ] Yes
[X] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[X] Yes
[ ] No

Type of Change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Locally in jupyter notebook as well as python interpreter

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[ ] I stared at the code and made sure it makes sense

Suggested Checklist:

[X] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[X] I ran make format; make lint to appease the lint gods

Thank you @logan-markewich


text:
Add links to each deployment name in the Conduit dashboard

I have removed the code that disabled links for a deployment based on whether it was added to the mesh. I have also added a call to action within each deployment that has not been added to the mesh. This is what it looks like now

IMO It feels a little cluttered and think it would look good if we just show the deployment name and the call to action with the greyed out upstream and downstream grapic. What does everyone think?

Nice! Let's remove some of the visual weight of the blue box and replace with regular text. There are some style updates that https://github.com/runconduit/conduit/pull/55 will help with.

Okay for us to update this in an upcoming branch though.

repo: runconduit/conduit


text:
Update polybar-integration (v1.2)

Adds more animations and idle-only mode

Does this include everything from #112?

authors: SirArchLinux abextm

repo: runelite/plugin-hub


text:
Merge ground markers plugin into tile indicators plugin

0ced501 will change the menu entry to look like this:

Needs rebase

authors: Kamielvf deathbeam

repo: runelite/runelite


text:
pull requests

With pull requests:

Open your pull request against master
Your pull request should have no more than two commits, if not you should squash them.
It should pass all tests in the available continuous integrations systems such as TravisCI.
You should add/modify tests to cover your proposed code changes.
If your pull request contains a new feature, please document it on the README.

pull

repo: runninggod/gin


text:
Update docs, add VAD option and extra format

Main changes

After #15 we should update the README to include the new inputs, added sample output too.
Modify the default format plain_text to not include \n, just like OpenAI whisper API does. If you want each segment to use a different line you can use the new formatted_text format.
Add option to enable VAD (voice activity detection) to filter parts of the audio without speech and improve speed/accuracy, by default it is disabled. #1
Added a locust file I used to generate random-length audios and test performance of the different GPUs available over Runpod, don't know where to place it or if it even belongs here, you can remove it if unsure :)

Tests

Tested enabling and disabling vad filter:

formatted_text output:

plain_text output:

Fantastic PR!
Honestly, this slipped under the radar, but I am glad to get this PR out

authors: justinmerrell leandroalbero


text:
Updating StringPattern to return its contents as Python Bytes

This PR modifies the behavior of StringPattern binding. It returns the content of kore_string_pattern as py::bytes.
The value must be encoded with raw_unicode_scape in order to get assert StringPattern(value).contents == value.
We fixed a test_pattern to reflect this behavior and added 2 new tests that show the features we're enabling with this modification, an initial Unicode support, among them.

@dwightguth I've tested it upstream with K. It breaks in some tests, which I already have a PR to fix (https://github.com/runtimeverification/k/pull/4567). With this fix I've tested KEVM as well, and everything is passing there!

repo: runtimeverification/llvm-backend


text:
Get error when evaluate meteor

hi, @ruotianluo.
when i use --language_eval 1 option to evaluate BLEU/METEOR/CIDEr scores during training, i always get this error:BrokenPipeError: [Errno 32] Broken pipe.Details are as follows:
computing METEOR score...
Traceback (most recent call last):
File "tools/train.py", line 298, in
train(opt)
File "tools/train.py", line 252, in train
dp_model, lw_model.crit, loader, eval_kwargs)
File "./captioning/utils/eval_utils.py", line 221, in eval_split
lang_stats = language_eval(dataset, predictions, n_predictions, eval_kwargs, split)
File "./captioning/utils/eval_utils.py", line 87, in language_eval
cocoEval.evaluate()
File "coco-caption/pycocoevalcap/eval.py", line 59, in evaluate
score, scores = scorer.compute_score(gts, res)
File "coco-caption/pycocoevalcap/meteor/meteor.py", line 43, in compute_score
stat = self._stat(res[i][0], gts[i])
File "coco-caption/pycocoevalcap/meteor/meteor.py", line 67, in _stat
self.meteor_p.stdin.write(score_line+'\n')
BrokenPipeError: [Errno 32] Broken pipe
Do you know how to fix it？thanks a lot！

I have never seen this before. Sorry. You might as well search on stackoverflow or so.


text:
[BUG] There is no resources present for "Testing" due to wrong configs

Description

There is no data present for the "Testing" while we have data inside database.

Screenshots

Any additional information?
No response
What browser are you seeing the problem on?
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[ ] I am a GSSoC'23 contributor

Can you elaborate on this @shreedhar37

Yes @CBID2. I am ready to contribute

Sure @CBID2 . We have data inside https://github.com/rupali-codes/LinksHub/blob/main/database/youtube/testing.json for testing resources, but due to wrong config in data.ts

I see @shreedhar37. Go ahead

repo: rupali-codes/LinksHub


text:
I suggest creating a Generator subcategory in the Frontend category to provide easy access to various tools.

Description
Here we could add all the websites which help in generating CSS.
Like for example
https://neumorphism.io/#e0e0e0
https://hype4.academy/tools/glassmorphism-generator
https://uiverse.io/switches
https://www.cssportal.com/css-generators.php
https://enjoycss.com/start#box
https://cssgenerator.org/
Screenshots
No response
Additional Information
No response

Thank you @PriyansuMaurya, will surely do that

Thank you @PriyansuMaurya, will surely do that

I want to try it first.

okay, go on

@PriyansuMaurya how's it going?

@PriyansuMaurya how's it going?

I'm out of my home place for 10 days. So sorry 😑 for this. If anyone is ready to take this please assign him.

authors: PriyansuMaurya rupali-codes


text:
[WIP] Extract signature module

This is a PR to extract the signature module, as suggested in #465. Note that this PR was created just to form a base for the suggestion, and extracts the region and param modules as well, which may not be ideal. Hence, this PR is WIP until suggestions/input from other maintainers is received.
I'm perfectly OK with closing this PR entirely if it's decided that extracting the signature crate is not ideal, but I think it's a good idea and the obvious candidate for an isolated crate, which is why I took the initiative of getting it more-or-less done right away.

This has drifted out of date quite a bit.  @indiv0 do you think you'll be able to revisit this in the near future or should we close this for now?

I can revisit this over the next week or two.

Closed in favour of #634.

repo: rusoto/rusoto