Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Internal server error prevents from posting question to answers.ros.org #177

Closed
ogallagher opened this issue Oct 23, 2018 · 14 comments
Closed

Internal server error prevents from posting question to answers.ros.org #177

ogallagher opened this issue Oct 23, 2018 · 14 comments

Comments

@ogallagher
Copy link

ogallagher commented Oct 23, 2018 •
edited

I didn’t do anything special. I’m using MacOS Mojave and the Safari browser. I tried to post a question to the Q&A forum multiple times and was told an “internal server error” occurred. I recently made an account to be able to post at ros.org. Below is the text of the question:

Title: RosAria not receiving messages
#Resources
Macbook Air with Ubuntu virtual machine via VMWare

Pioneer3 AT robot

ROS

RosAria

#Context
I have at least most of the setup for Ros+RosAria already working:

  1. The master ROS node running on a laptop at 192.168.1.112 via roscore
  2. The RosAria node running on the robot’s built-in computer at 192.168.1.108 via rosrun rosaria RosAria, the port set accordingly to access the robot's motors and sensors via rosparam set..., ROS_MASTER_URI=192.168.1.112:11311, and ROS_IP=192.168.1.112.
  3. Another terminal window on the laptop running rostopic pub /RosAria/cmd_vel geometry_msgs/Twist “linear:... angular:...”

The RosAria node running on the robot confirms it’s able to connect to the master, and if I run the command rostopic list on the laptop I can see /RosAria/cmd_vel as one of the available topics.

In the terminal window where I try to publish to /RosAria/cmd_vel I’m told that the message is sending but the robot shows no signs of having received it, neither console message nor movement of the wheels.

However, if I quit the RosAria node on the robot and restart it while leaving the rostopic pub command running on my laptop, the robot registers the message once upon startup, moves accordingly for a bit, and then does nothing.

I’ve also tried to rostopic echo other topics like battery state, motors status and pose, but I don’t receive any messages from the robot.

I already tried changing the parameters /RosAria/TicksMM and /RosAria/RevCount according to this case.

#Question
Why is the Pioneer robot with RosAria running not receiving the cmd_vel commands from my client if it’s apparently able to communicate with the master node successfully?

Help's much appreciated!

Tags: melodic rosaria Pioneer3-AT
@ogallagher
Copy link
Author

I just tried using Firefox, but got the same error.

@tfoote
Copy link
Member

tfoote commented Oct 23, 2018

I got another similar report that it it might related to special characters in the title or text.

still does not work - chrome on mac, incognito window

but i tried remove the ° character and that helped. Seems like it cannot be used in titles or texts. Should I file an issue for this?

tried to post this:

Spinning Lidar tilted 25°forward - Experiences?

I plan to use an ydlidar tilted forward by 25° to

  1. detect obstacles and holes in the path
  2. understand where the side of the path (forest roads or farm tracks) is to drive along the side of the path

For navigation I plan to use GPS, open street maps and a Magnetometer to get the general heading of the path and compare it to my actual heading and to the constraints imposed by the side of the path or any rocks or holes in the path.

The Idea is that the forward tilted lidar would show where the path is even and where not. I would loose forward range but I would be able to look down (to discover holes or water which would look like a hole as it reflects) and I would be able to see things sticking up from the ground (distance and known height). Things, that are only a few centimeters high I would want to ignore anyway.

Yes, I understand that objects hanging over the path I would see rather late or not at all just before they knock off the sensor. And yes, I would loose seeing something meanigful "in the back". But I plan to have a robot that drives forward only and if needed turns on the spot.

My experience so far is that the "path" shows up as a line in front and the curbs or grass standing at the side and also buildings or trees show up to the left and to the right (albeit not scanned horizontally but at an angle. angled slopes up or down on the side will show up with an angle too.

Does anyone have experience with such angled laser scans? I have seen some people work with tilting lasers that scan let and right and up and down and typically they would remove the ground from the scene. In my case I would also want to remove the ground and leave all else there as potential obstacles (both deep and high).

@gavanderhoorn
Copy link

I've received multiple similar emails, direct msgs (on ROS Discourse) and questions on ROS Answers about this.

Can this be looked at?

@evgenyfadeev
Copy link
Collaborator

evgenyfadeev commented Oct 25, 2018 via email

@SlopeSurfer
Copy link

I have thought of two additional bits of information that might be relevant for the case I submitted (Internal Server Error trying to ask a question.) 1) I was using Chrome. 2) Since the wrapping around was all messed up (which you can see is the case in the email that you copied me on), I had gone through and put a lot of carriage returns. I felt doing that was particularly important for the cases where I was copy pasting Linux input/output. Before adding the carriage returns, the output lines were not on the appropriate separate lines. Which I think would have made it hard for anyone to follow. If you like, I could try doing the same thing with a different browser and let you know how that goes.

@evgenyfadeev
Copy link
Collaborator

Could you give it a shot please? Hopefully it's fixed now.

@gavanderhoorn
Copy link

@SlopeSurfer wrote:

Since the wrapping around was all messed up (which you can see is the case in the email that you copied me on), I had gone through and put a lot of carriage returns. I felt doing that was particularly important for the cases where I was copy pasting Linux input/output.

offtopic, but: manually inserting line breaks is not needed: select the preformatted text that you pasted into your question and press ctrl+k or press the Preformatted Text button (the one with 101010 on it).

@SlopeSurfer
Copy link

SlopeSurfer commented Oct 26, 2018 via email

@130s
Copy link

130s commented Oct 27, 2018 •
edited

I just got the same error. After removing some texts now I was able to post this. What I had to remove was the following (which clearly includes some symbols that might look suspicious):

    $ tree -L 3
    .
    ├── baa
    │   ├── CMakeLists.txt
    │   ├── config
    │   │   └── rsc.yaml
    │   └── package.xml
    └── foo
        ├── a.launch
        ├── CMakeLists.txt
        ├── config
        │   └── rsc.yaml
        ├── package.xml
        └── test
            ├── baa.test
            └── foo.test

UPDATE: Once the thread was created, I was able to update the content with the texts I had to remove when initially posting, and saved.

@gavanderhoorn
Copy link

@evgenyfadeev: has some sort of content filtering been put in place recently?

@evgenyfadeev
Copy link
Collaborator

evgenyfadeev commented Oct 28, 2018 •
edited

@gavanderhoorn now it should be fixed, sorry there was an issue with unicode handling.

Yes there was an update in the spam filter and it caused this issue.

@SlopeSurfer
Copy link

SlopeSurfer commented Oct 29, 2018 via email

@SlopeSurfer
Copy link

SlopeSurfer commented Oct 29, 2018 via email

@ogallagher
Copy link
Author

ogallagher commented Oct 29, 2018 •
edited

I was also able to post my question as it was originally written (even though now I don’t really need the answer since I’m not working in the same context anymore on that project).

Thanks to @evgenyfadeev it seems the original issue is now fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@evgenyfadeev @tfoote @130s @gavanderhoorn @SlopeSurfer @ogallagher