The Oracle Always Free plan is an excellent option, but I found myself struggling with their firewall settings while attempting to run an Nginx web server. Despite enabling port 80 in both the network security groups and security lists, it was still being blocked for unknown reasons.
Firstly I checked the ufw settings and it was disabled definitely. However, when I looked at the iptable rules by executing
sudo iptables-L, I was surprised by lots of existing rules there.
Sometimes we need to add new objects to Gazebo to build a dynamic environment, particularly in some manipulation tasks. Suppose we test if the robot can pick up items from the floor. Thus, we may need a program to spawn models in a random position in the environment to verify our manipulation algorithms’ robustness. Like the top picture, a new cylinder is created in TIAGO’s gripper. Then TIAGO can deliver the cylinder to a free container.
Some PCIe GPU fans spin uncontrollably on macOS computers, and it is very annoying to hear these fans’ buzzing. My computer is built with a Radeon RX 570 and sometimes has the above fan issue, especially after booting.
I searched the internet and found a tricky solution (source) that to install a benchmark software called LuxMark. After opening this software and running for a few seconds, the graphics card fan will magically return to the normal speed.
Sometimes we have to run background tasks with a quite long duration time. However, the RabbitMQ has a default time limitation for waiting the ack. If the execution time is exceed, you will got an error message like “Delivery acknowledgement timeouts” and your channel will be broken.
When using a Socks proxy, you must have written a string like
socks5://127.0.0.1:8000 to represent the proxy protocol and address. Strings in this format are widely used in CURL based components such as Guzzle, pip, and urllib3. We often want these programs to use a Socks proxy to connect to the internet but get weird connection failures. An interesting part of these strange failures is that accessing some websites works fine, while others cannot. These failures persist even if you have confirmed that there is no failure of the proxy connection itself. At this time, I suggest you consider that these failures are caused by DNS issues, especially when you are in some special network environment, such as the network affected by DNS pollution, the Great Firewall of China or a public WIFI.
We know that the Socks proxy works at the session layer and can forward TCP connections. Furthermore, Socks4a and Socks5 support DNS forwarding. Now, the most commonly used version is Socks5. Let’s take a careful look at the proxy protocol string. The reason for the DNS resolution error is that when we use addresses starting with
socks5://, which means the hostname will be resolved locally and get unexpected results. The local resolving is not an actual error or bug. It is a critical feature in some cases. But when you are in a restricted network, your local DNS may be polluted or unavailable. You need to change your protocol prefix to
socks5h://, which means the hostname will be resolved by the proxy server.
This is a problem can be solved by a simple answer and in fact well-defined in the CURL documentation. But most tutorials usually only provide a string like
socks5://127.0.0.1:8000 to tell the user how to apply a Socks5 proxy. And access failures caused by DNS are often difficult to recognize and locate. Even if users know that the failure is related to DNS, it is more difficult to search for relevant answers in Google. You can find some discussions like https://github.com/urllib3/urllib3/pull/1036 and https://stackoverflow.com/a/61980997/5616769
Overall, try to use
socks4a:// in your proxy settings when you face some strange access failures. Hope that is helpful for you!
osrf/rocker is a lovely docker project which make building ROS environment rapidly. It supports Ubuntu 20 and the latest Nvidia driver. ROS GUI applications and tools work properly with hardware acceleration.
However, when I tried to run Gazebo 7 under Ubuntu 20, there is no title bar on the top and I cannot resize this window.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
Set by Google to distinguish users.
Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.