I try to set up cocoa pods in my MacBook Pro El Capitan.
pod setup command will stuck on Cloning into 'master'...
Even I waited for 2 hours with 1GB download of git-remote-https.
It is never completed.
I also tried lots of time on Google for last 15 days.
I also tried following commands:
pod repo remove master
It says master repository not found.
That bypass / workaround solution works just to Virtual Machines
When you try to install cocoa pod, there is no network activity after it gets stuck.
According to hagge's comment on March 8, 2016 (https://github.com/cocoapods/cocoapods/issues/4989), this kind of problem can be caused by automatic limitation of transfer rate on servers, which is done to make sure that extremely high levels of load do not bring problems.
If you are using VMware or Virtualized Machines, you can proceed as below.
Change the configuration of Virtual Machine:
Select Network Adapter
Go to Advanced Settings
Incoming Transfer, set to Cable Mbps (4000 Kbps)
Outgoing Transfer, set to Cable Mbps (4000 Kbps)
Click OK
You may have to make the command install more than once. It'll take time but may work. Worked for me!
Its not a cloning problem. Your Internet connection problem. To solve this issue, you have to go to VM(virtual machine) settings to Bridge the physical connection.
VMware Player-->Removable Devices-->Network Adapter-->settings
You will find Network connection and check both
choose the option Bridged: Connected directly to the physical network
if you are using a laptop
Enable Replicate physical network connection state.
99% will be work
Related
I'm trying to setup nektos/act locally so I can test my github workflows. When I run act -l I'm receving the follow working.
⚠ You are using Apple M1 chip and you have not specified container architecture, you might encounter issues while running act. If so, try running it with '--container-architecture linux/amd64'. ⚠
Do you know how can why and how I can get rid of this warning?
Not sure if this is true, but it seems that I need to configure something in docker?
Here's what happens:
Using a Macbook Pro, I use the Microsoft Remote Desktop Connection application to connect to my work computer, which is a Windows 10 machine
If I try to launch Spyder on my work computer, I get this error:
Load Library Error
However:
If I am at my work computer (i.e. physically at work instead of logging in remotely), I can launch Spyder successfully
If I leave Spyder open on my work computer, then go home and do a remote log-in to my work computer, I can use Spyder without issue. The problem/error described above arises only if I try to open Spyder through the remote connection.
This error only seems to affect Spyder and I can use all other programs without issue through a remote connection. As a workaround I've been using other IDEs and successfully running scripts, but I strongly prefer Spyder.
What I have tried so far (without success):
The 4 troubleshooting steps posted by Fazil M. to this Microsoft thread
Uninstalling/reinstalling Spyder using Conda
Restarting my work computer
System Information:
Work Computer OS: Windows 10, 64-bit
OS of computer through which I'm logging in to work computer: Mac OS X El Capitan 10.11.6
Spyder version: 4.1.1
Any thoughts as to what could be going on?
Update--More information and trials:
I checked out Issue #3736 on Spyder's GitHub. It says to download and add a file called opengl32sw.dll to the folder ~\Lib\site-packages\PyQt5\Qt\bin. But when I go to the PyQt5 folder, I do not see a subfolder for Qt. I tried placing it into the PyQt5 main folder, but that did not fix the problem.
I've heard this can be a graphics card issue too. On my machine I have two graphics cards: AMD RadeonT R5 430 and Intel(R) HD Graphics 630.
Darren's answer did not work for me. What did work was to:
First option: go into the device manager and disable the Intel HD Graphics card under "display adapters."
Second option:
run "Gpedit.msc"
navigate to Computer Configuration->Administrative
Templates->Windows Components->Remote Desktop Services->Remote
Desktop Session Host->Remote Session Environment
Disable "use WDDM graphics display driver for remote desktop
connections"
Restart the computer
See https://answers.microsoft.com/en-us/windows/forum/all/windows-10-1903-may-update-black-screen-with/23c8a740-0c79-4042-851e-9d98d0efb539
It took help from my organization's IT contractor, but I fixed the issue by doing the following:
Run a file called "gpedit.msc", which will open up a window for Local Group Policy Editor
In the tree menu on the left, navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment, and open the Remote Session Environment folder (not the subfolder within it)
Make sure the following are set to "Enabled":
"Use hardware graphics adapters for all Remote Desktop Services"
"Prioritize H.265/AVC444 graphics mode for Remote Desktop Connections"
"Configure H.264/AVC hardware encoding for Remote Desktop Connections"
Then restart the computer.
Since I was unable to get pass LoadLibrary 126 error using the solutions provided online and on here, I stepped back and realized the obvious workaround. The errors occurs when you open the program while you're using a remote session, right? The obvious solution is to launch the program while a remote session is not in progress. To do this while you're remoting, you should create a batch script to launch the program but make sure to include to a time delay before that (I used 'timeout 10 /nobreak' to do so). Run the batch script and, before your program launchs, disconnect from RDP. After enough time passes for the program to launch, you can reconnect to RDP and your program will be up and ready
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:
The master ROS node running on a laptop at 192.168.1.112 via roscore
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.
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?
Disclaimer
The project I was working on where this problem came up isn’t using the same equipment anymore, so now this question is not so urgent for me. I’m also not able to test proposed solutions in the near future since I no longer have access to that Pioneer robot. However, I’ll keep this topic unanswered in case someone else encounters this problem too.
You need To Set ROS_IP On Robot side too to let the ROS System Knows What IP To Use as It's Network Interface
I myself Set This Environments Inside .bashrc Like This:
export ROS_IP=192.168.1.108
and then source .bashrc.
I think You can use rosparam Too But I never tested.
Google has changed and removed the i2c device from the /dev/ path.
They add/remove the device I you are using this:
I2cDevice dev = pService.openI2cDevice("I2C1", 0x68)
And the /dev/i2c-1 is gone if you disconnect the I2C device: dev.close();
This is the reason why you do not have access via:
open("/dev/i2c-1", O_RDWR);
(this was possible in the Version 4.1 without issues)
So, now google made it complicated... and the question is, how I can bring back the device i2c-1 after boot?
#Kyle what you're doing may work, but it definitely isn't supported by Android Things. When Android Things leaves developer preview, you may no longer be able to directly access device files at all (due to the device being in SELinux enforcing mode).
In the meantime, you can probably execute the following to recreate the device node. At best this is a temporary solution, since you'll have to run these commands every boot (unless you add them to one of the init scripts).
$ adb shell
rpi3:/ $ su
rpi3:/ # mknod /dev/i2c-1 c 89 1
We have a vm windows 10 machine jenkins slave that keeps rebooting although we have turned off windows auto update. When it restarts it tries to restart Jenkins which throws this error:
> java.lang.exception the server rejected the connection: none of the protocols were accepted at
> hudson.remoting.engine.onConnectionRejected(Engine.java:286)
> at hudson.remoting.Engine.run(Engine.java:262)
We then have to go in and manually start jenkins agent. This is not good for our automated tests that require this machine.
As an additional side note: Edge won't open. You can click on it all day and nothing appears to occur.
Any ideas on what is causing the windows reboot and how to stop it?
We wound up having our lab team create a new vm and deleting this one.
This sounds like a cause of malware, try downloading a free anti virus {have some help with this, alot contain malwate}.
Best Regards
Shadow
Thanks!
additional notes! Ive had this problem many times with windows 8 in a virtual box!