I follow the different step of this plan :
https://www.getopenerp.com/install-odoo-11-on-ubuntu-16-04/#comment-1623
but at the 13th step I have the error :
bash: cd: /opt/odoo/odoo: no such file or directory
I don't understand why because I follow correctly each step.
Related
While running recorded simulation in Gatling.
I get an error:
"Resource /recordedsimulation/0004.request.dat"/"Resource
/recordedsimulation/0004.request.json" not found?
You have to open your simulation file, for instance: recordedsimulation.scala and replace all error occurrences of first slash in your file path.
For instance use:
.body(RawFileBody("recordedsimulation/0004.request.json"))
instead of:
.body(RawFileBody("/recordedsimulation/0004.request.json"))
And make sure, your directory recordedsimulation is in your resources directory if you are using gatling version greater than 3.
I am trying to run my existing code from one system to another and facing continue following error :
bundle format unrecognized, invalid, or unsuitableCommand
/usr/bin/codesign failed with exit code 1
How to resolve this error ? I didn't change a single line of code. However in my existing system, its working like a charm. Any hep appreciate.
This is the error you are getting because of some system settings changed. You can solve it by following below steps :
This error will say for which pod you are facing this issue. So select that pod file.
Now select Target for that Pod
Now got To General
Tap on Choose info.plist File
It will show you pods-yourprojectnae-acknowledgements.plist, so select that option
Now Build and check
you will not find this error again
This solution works for me. Try once.
I have a Travis CI setup on GitHub. I use it to check my commits for iOS app. The problem is, I very often and randomly get an error 65. I have yet to find a solution.
When I restart the job 2-3 times after it has failed it passes in 90% of times.
I previously also had a problem with logs being too verbose for Travis (>4MB) but I added xcpretty to fix that.
Errors I took from log:
...
Generating 'XYZ.app.dSYM'
❌ error: couldn't remove '/Users/travis/Library/Developer/Xcode/DerivedData/XYZ-aaltcjvmshpmlufpmzdsgbernspl/Build/Products/Debug-iphonesimulator/XYZ.app/SomeName.storyboardc' after command failed: Directory not empty
...
And then at the end of Travis log:
Testing failed:
The file “056-Jj-FAu-view-XmS-Ro-0cO.nib” couldn’t be opened because there is no such file.
error: couldn't remove '/Users/travis/Library/Developer/Xcode/DerivedData/XYZ-aaltcjvmshpmlufpmzdsgbernspl/Build/Products/Debug-iphonesimulator/XYZ.app/SomeName.storyboardc' after command failed: Directory not empty
error: lipo: can't move temporary file: /Users/travis/Library/Developer/Xcode/DerivedData/XYZ-aaltcjvmshpmlufpmzdsgbernspl/Build/Products/Debug-iphonesimulator/XYZ.app.dSYM/Contents/Resources/DWARF/XYZ to file: /Users/travis/Library/Developer/Xcode/DerivedData/XYZ-aaltcjvmshpmlufpmzdsgbernspl/Build/Products/Debug-iphonesimulator/XYZ.app.dSYM/Contents/Resources/DWARF/XYZ.lipo (No such file or directory)
Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/dsymutil emitted errors but did not return a nonzero exit code to indicate failure
** TEST FAILED **
The following build commands failed:
LinkStoryboards
LinkStoryboards
(2 failures)
The command "./scripts/build.sh" exited with 65.
I am using Xcode 8 both in Xcode and Travis settings.
Ah, good question. Occasionally, xcodebuild steps that are failing during the codesigning step can be addressed using travis_retry - Travis will retry the step 3 times for any non-zero exit status, which should reduce the need for you to restart it manually. There are some suggested code snippets in the travis-ci/travis-ci GitHub issue on this as well. Good luck!
If you're running into the error code 65 (from random failures) here's a command you can pipe on the end of your xcodebuild (assuming you're running tests) command to get back more consistent results:
(XCODEBUILD_COMMAND_HERE) | awk 'BEGIN {success=0} $0 ~ /.* tests, with 0 failures \(.*/ {success=1} {print $0} END {if(success==0){exit 1}}
This looks for tests, with 0 failures ( in your output text, thus using the text output of xcodebuild instead of the status code of xcodebuild to determine success.
Note: Keep in mind, if you do something like NSLog(' tests, with 0 failures ('); in your code you make get a false positive, it's very unlikely to happen by accident. You may have to update tests, with 0 failures ( in the awk script between updates of xcodebuild. But, having consistent results with xcodebuild is definitely worth that price.
I am trying to run cellcli on my one of the Exadata Cell Server.
When I login to the Server, I am able to see all the files as expected.
(Like: all_group all_nodelist_group cell_group all_ib_group etc)
When I issue command to start cellcli it gives me error that command not found:
# cellcli
-bash: cellcli: command not found
# which cellcli
which: no cellcli in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
Any idea what is the location of the cellclie executable on exadata?
Do I need to export any other path to get this command?
cellcli is in /opt/oracle/cell/cellsrv/bin. It should be put in path by /etc/profile.d/cell_env.sh
(from Marc Fielding)
I am new to Joomla and i have created a component folder as com_joomlabook
within that 2 files as joomlabook.php and joomlabook.html.php
But when i run it in the browser using http://localhost/joomla/Joomla_1.5.7-Stable-Full_Package/administrator/index.php?option=com_joomlabook
Fatal error: require_once() [function.require]: Failed opening required '' (include_path='.:/usr/share/php:/usr/share/pear') in /home/ntdg/public_html/joomla/Joomla_1.5.7-Stable-Full_Package/administrator/components/com_joomlabook/joomlabook.php on line 6 that is in the getPath line why so??Please suggest me.
Did you "install" the component or add a row to the components table? Joomla doesn't just see what folders are there and run scripts.
I actually just wrote a blog post last week on how to create your own components quickly, which might be useful: http://infuseddesign.co.uk/blog/7-joomla/24-building-joomla-components