Host machine: OSX Mojave
Virtualbox: 6.0.4
Tails: 3.12
Where I download virtualbox: brew cask install virtualbox. NOTE: I had virutalbox installed quite awhile and using it with vagrant and ansible to test playbook and stuff, and did make sure everything was clean when trying to run tails.
Where I download the image file: from tails site download using torrent
How I attempted to run tails from ISO image in virtual box: steps follow from tails documentation, it was straightforward and tried it more than five times
Error occurred at: steps 7, from the tails doc at configuring virtual machine to start from an ISO image, and below are the detail error:
The medium '/my-path/tails-amd64-3.12.iso'
can't be used as the requested device type.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Callee: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Expectation: No error popup at steps 7, which at the adding tails ISO image, and the rest of the step and could successfully start tails up
Attemps to get it work:
Attempt one: I watched one video from youtube that was about 7 months ago running tails in virtualbox, the process was pretty straightforward but I still get the same error.
Attemp two: I googled about the issue and only found simliar error. Those are conflicting Disk ID, which I applied the solution but got no luck.
I don't really use virtualbox much so are there anyway I can know more about the error message or anyone knows how to do with this? Thanks beforehand and appreciate for your precious time and help.
It is working now, the weird thing is that I have to directly open the .iso image instead of clicking on the folder that contains the .iso.
Related
No matter how I import my audio file (through uploading it on google colab, importing it through google drive), I keep getting the same error. Could it be a path issue, and if so, how could I go about fixing it? When I run an "iPython.display", it displays the audio and I'm able to play it, but I'm not sure why torchaudio cannot load it.
Thanks in advance :)
waveform, sample_rate = torchaudio.load("Default-20220816-113844.mp3")
waveform = waveform.to(device)
if sample_rate != bundle.sample_rate:
waveform = torchaudio.functional.resample(waveform, sample_rate, bundle.sample_rate)
Assuming ("Default-20220816-113844.mp3") is not being found because of the path
On Colab to find the path click on the "..." (that appears on the right hand side of objects in the file browser when you hover over them) and choose COPY PATH to copy the complete path, the value will be copied without quotation marks.
At the time of the question is posted, Google Colab has pytorch==1.12 and torchaudio==0.12 pre-installed, so I assume you are getting the error with these versions.
Starting from TorchAudio 0.12, mp3 decoding requires FFmpeg.
When "sox_io" backend is used, first it tries to load audio using libsox, and when it fails, it further tries to load it with FFmpeg.
In Google Colab, you can run the following command to install the supported version.
!add-apt-repository -y ppa:savoury1/ffmpeg4
!apt-get -qq install -y ffmpeg
See also: https://pytorch.org/audio/0.12.1/tutorials/streaming_api_tutorial.html
So, I'm working on a robotframework test project, and the goal is to run several test suites in parallel. For this purpose, pabot was chosen as the solution. I am trying to implement it, but with little success.
My issue is: after installing Pabot (which, I might say, I did by cloning the project and running "setup.py install", instead of using pip, since the corporate proxy I'm behind has proven an obstacle I can't overcome), I created a new directory in the project tree, moved some suites there, and ran:
pabot --processes 2 --outputdir pabot_results Login*.robot
Doing so results in the following error message:
2018-10-10 10:27:30.449000 [PID:9676] [0] EXECUTING Suites.LoginAdmin
2018-10-10 10:27:30.449000 PID:400 EXECUTING Suites.LoginUser
2018-10-10 10:27:30.777000 PID:400 FAILED Suites.LoginUser
2018-10-10 10:27:30.777000 [PID:9676] [0] FAILED Suites.LoginAdmin
WARN: No output files in "pabot_results\pabot_results"
Output:
[ ERROR ] Reading XML source '' failed: invalid mode ('rb') or filename
Try --help for usage information.
Elapsed time: 0 minutes 0.578 seconds
Upon inspecting the stderr file that was generated, I have this message:
Traceback (most recent call last):
File "C:\Python27\Lib\site-packages\robotframework-3.1a2.dev1-py2.7.egg\robot\running\runner.py", line 22, in
from .context import EXECUTION_CONTEXTS
ValueError: Attempted relative import in non-package
Apparently, this has to do with something from the runner.py script, which, if I'm not mistaken, came with the installation of robotframework. Since manually modifying that script does not seem to me the optimal solution, my question is, what am I missing here? Did I forget to do anything while setting this up? Or is this an issue of compatibility between versions?
This project is using Maven as the tool to manage dependencies. The version I am running is 3.5.4. I am using a Windows 10, 64bit system; I have Python 2.7.14, and Robot Framework 3.1a2.dev1. The Pabot version is 0.44. Obviously, I added C:\Python27 and C:\Python27\Scripts to the PATH environment variable.
Edit: I am also using robotframework-maven-plugin version 1.4.0.8, if that happens to be relevant.
Edit 2: added the error messages in text format.
I believe I've come across an issue similar when setting up parallel execution on my machine. Firstly I would confirm that pabot is installed using pip show robotframework-pabot.
Then you should define the directory your results are going to using -d.
I then modified the name of the -o to Output.xml to make it easy to identify.
This is a copy of the code I use. Runs optimally with 8 processes
pabot --processes 8 -d results -o Output.xml Tests
Seems that you stumbled on a bug in the prerelease version of robot framework (3.1a2.dev1).
Please install a release version of robot framework. For example 3.0.4.
Just in case anyone happens to stumble upon this issue in the future:
Since I can't use pip, and I tried a good deal of workarounds that eventually made things more unstable, I ended up saving my project and removing everything Python-related from my system, so as to allow me to install everything from scratch. In a Windows 10, 64bit system, I used:
Python 2.7.14
wxPython 2.8.12.1, win64, unicode, for py27
setuptools 40.2.0 (to allow me to use the easy_install command)
Robot Framework 3.0.4
robotremoteserver 1.1
Selenium2Library 3.0.0
and Pabot version 0.45.
I might add that, when installing the Selenium2Library the way I described above, it eventually tries to download some things from the pip repositories - which, if you have a proxy, will cause you trouble. I solved this problem by browsing https://pypi.org/simple/selenium/, manually downloading the 2.53.6 .tar.gz file, then extracting it and running setup.py install on the command line.
PS: Ideally, though, anyone should be able to use proxy settings from the command line (--proxy http://user:password#server:port) to get pip and then use it; however, for some reason, probably related to network security configurations that I didn't want to lose time with, this didn't work in my case.
I am trying to create a pre-render server for my ember app.
I installed ember-prerender (https://github.com/zipfworks/ember-prerender), used the initializers provided in the /example, deployed it on one of my servers.
But when I try to launch it:
[Renderer 0] Engine starting up (phantom)
[Renderer 0] Restarting rendering engine in 25000 seconds after it failed
with error: Phantom encountered an error: TypeError:
'undefined' is not a function (evaluating 'u.bind(e)')
I'm unsure where to look. I tried:
Deleting all third-party SDK (Facebook, Google Analytics)
Logging different parts of the code (the event XContentReady seems to be fired)
Launching with the engine jsdom instead of phantom (gives: [Renderer 0] Restarting renderer, timed out while initializing)
Trying in production
I don't know where too look at now. The worse part is that I had it working a few days ago (see: Ember pre-render: timed out while initializing)
EDIT:
I don't think that the problem has anything to do with the code, since I did a hard reset to a version that used to work.
Maybe some version changed (bower, npm, phantom)? I tried to update bower to 1.6, no success.
Maybe I have new dependencies that cause the problem? I don't see exactly how though
EDIT2: I started fresh on a new server, now I get Phantom crashing with this error message:
[Renderer 0] Restarting rendering engine in 25000 seconds
after it failed with error: Erroneous exit code: null SIGSEGV
If I use JSDOM I still get the Restarting renderer, timed out while initializing
EDIT 3: I tried to include a polyfill in my app. Using:
github.com/es-shims/es5-shim
then as an addon: github.com/pixelhandler/ember-cli-es5-shim
With no success
EDIT 4: I'm having the same error with a brand new project, containing only ember-prerender, so I'm thinking it's either linked to my particular build (version: 1.13.13, node: 0.12.3, npm: 2.14.10, os: linux x64), or my computer packages/configuration.
I don't have experience with jsdom, but Function.prototype.bind is not supported with phantomjs#1.9 and lower. Have you tried phantomjs#2.0?
I have trouble on updating tizen-2.1 on my test device
I follow manual step by step, but some errors when I use lthor tool.
Can you give me some insight?
my environment
current tizen version on test device => 2.0
ubuntu 13.04 (on vmware 9)
modemmanager off
Error Message:
line 345: failed to read signature bytes
line 629: handshake failed
line 958: failed to open port (null)
Unfortunatelly, sometimes it's needed to uninstall modemmanger at all:
sudo apt-get purge modemmanager
Also VMWare may be at the bottom of your problem.
please follow these steps
I updated my device by following these steps.
https://wiki.tizen.org/wiki/Flash_Tizen_2.1_Image_to_Reference_Device
I am trying to capture outgoing packets (i.e., from my localhost) by using Scapy capturing function sniff, then parse them as they get captured but I keep getting the following warning:
WARNING: fileno: pcapy API does not permit to get capure file descriptor. Bugs ahead! Press
Enter to trigger packet reading
Is there a fix for this issue? I need the process to be fully automatic without the user interaction.
Any help is greatly appreciated.
p.s. my system setup is:
OS: Mac OS X 10.7.5
python: 2.7.1
scapy: 2.2.0
Thanks
Just in case somebody else ran into the same issue, I managed to solve it by installing pypcap module to replace pcapy. I referred to http://comments.gmane.org/gmane.comp.security.scapy.general/4026
you will need to have the following dependencies installed:
C compiler + make (Xcode will have these settled)
libpcap
pyrex ( can be installed by package manager e.g., pip ).
you might run into an issue when you install pypcap after the dependencies are installed, refer to this patch http://code.google.com/p/pypcap/issues/detail?id=13, it worked for me!