I am trying to setup an IBM Block Chain setup in my local environment.
I am referring to the below manual for setup :
https://console.ng.bluemix.net/docs/services/blockchain/ibmblockchain_tutorials.html
When following these steps:
1) Setup the environment
Install GoLang
SETUP GOROOT & GOPATH
2) SETUP GITHUB
Under GITHUB setup, at point 6, When I try to run the command go build ./
It should give No errors/text. But it is giving an exception. Please have a look at below screenshot for an exact exception.
Exception-screenshot.
Can anyone help me, how can I solve this error, Ideally build should be successful.
The error is pretty obvious.
Replace
stub *shim.ChaincodeStub with stub shim.ChaincodeStubInterface everywhere in your chaincode_start.go file.
Furthermore, read the following issue on github as it will really help,
https://github.com/IBM-Blockchain/ibm-blockchain-issues/issues/29
Related
I wanted to create a patchbaseline which passes the alternative repo for ubuntu. I followed the info here. I set all other options as default in the ui and change the configuration to below:
[main]
name=ubuntutest
baseurl=http://security.ubuntu.com/ubuntu
enabled=1
But, I am getting the below error :
ValidationException: Source test did not contain a repository
specification, Source test configuration blob has an error in line 1.
I tried similarly for RHEL patch baseline (with different repo) and got the same errors.I could not find much examples to try online to confirm if i am giving the correct configuration. Can you please help me on how i can create patch baselines with alternative repositories?
I have installed a local instance of Readthedocs server, but anytime I try to build a github repository the app gets stuck in the Triggered state!.
There is no errors or exceptions, just regular info messages:
[25/Apr/2017 14:21:11] INFO [readthedocs.projects.utils:81] Running: 'ln -nsf /var/www/my-project/user_builds/test1/rtd-builds/latest /var/www/my-project/public_web_root/test1/en/latest' [/var/www/my-project]
[25/Apr/2017 14:21:11] INFO [readthedocs.projects.tasks:844] (Build) [test1:] Updating static metadata
Any idea what could be causing this issue?
so I had this problem, and there seems to be a lot of different things that could cause it, because I've seen various postings about it on different forums however none of the solutions posted helped me. The only posting i have book marked is this github issue.
for me I found that the documentation would build if I ran the command python manage.py runserver 0.0.0.0:8000, but would be stuck in a triggered state if I used my computers ip address; the solution was to use the above command but to add the following to readthedocs/settings/local_settings.py :
import os
# Set this to the root domain where this RTD installation will be running
PRODUCTION_DOMAIN = os.getenv('RTD_PRODUCTION_DOMAIN', '10.x.x.x:8000')
# Enable private Git doc repositories
ALLOW_PRIVATE_REPOS = True
best of luck.
I have an open source project that I'd like to test using travis-ci. Sadly it is rather flaky and I'd like to know the reason. The tests write very verbose log files, so I'd like to export these, upon failure to Github Gist. There are command line tools that allow me to do that, gist-paste for instance, however I don't know how to run them only upon failure and without overriding the return code of the unittests, i.e., I'd still like travis-ci to notice the failure.
Great idea. Travis CI has a step in the build lifecycle called after_failure which will be fired after your testing script step has run and failed, as outlined on the "customizing the build" documentation page here.
In your .travis.yml file, you would add an after_failure step with a call to your gist-paste command, after setting the relevant Git tokens as encrypted environment variables I assume. You can then access plenty of information about the build from the many environment variables set by Travis during the build.
I have a web project written in Sitecore 8/uCommerce. I am using Teamcity to compile and package the project and Octopus deploy to push it out. When I commit to SVN Teamcity picks up the changes, compiles and packages it up and Octopus deploys it to the Dev environment. All works well. However when I try to promote to test I get an error...
Error running conventions; running failure conventions... Fatal
10:24:19 Deployment on the Tentacle failed.
In the project I have a post deploy script (PostDeploy.ps1) to remove unwanted config files. There is only one line...
.\DeleteConfig.exe $OctopusEnvironmentName
I changed it to this from..
.\DeleteConfig.exe $OctopusParameters['Octopus.Environment.Name']
Due to an article I read, but this hasn't changed the error. I have also tried..
.\DeleteConfig.exe $OctopusParameters['OctopusEnvironmentName']
Again no effect. If I comment out the line of code I no longer get the error.
I have been trying to fix this for sometime now, read and followed the articles and post I can find on the problem but cannot find the fix.
A slight curveball is that this is the second project we deploy in this way. The first is also Sitecore/uCommerce and in the PostDeploy.ps1 the line
.\DeleteConfig.exe $OctopusParameters['Octopus.Environment.Name']
works perfectly.
Any help or pointers would be appreciated.
You don't need a post deploy script as there is a community task that cleans up any extra configuration files. It's at https://library.octopusdeploy.com/step-templates/9a2b84db-2940-4d9a-b61f-c82df35cee6c/actiontemplate-file-system-clean-configuration-transforms.
If you want to do it your way, I would simply use Poweshell like this:
Get-ChildItem -Filter Web.*.config l Remove-Item
I am using Opensuse and whenever i am going to install any software on it, It Shows me the error "linux-7gyx:~ # zypper in python-oauthlib Retrieving repository 'New' metadata --------------------------------------------------[] File '/repodata/repomd.xml' not found on medium 'http://download.opensuse.org/repositories/SUSE:/SLE-11:/SP3:/Update/standard/'" What should i do to get rid of this type of error ,Please Help Me . Thanks In Advance
I don't have the full stack trace of your error, hence apologies - I cannot provide a custom resolution.
I struggled with this issue for some time as well. Managed to resolve it just now. In my case, the error was -
repodata/repomd.xml from stackdriver: [Errno 256] No more mirrors to try.
This happened when I tried to install stackdriver using a chef cookbook.
I started troubleshooting with the routine options of a 'yum clean all' and 'yum clean metadata'. Didn't help.
In due course I checked the yum repo file under '/etc/yum.repos.d'. The one related to the pack which I was trying to install (stackdriver) was the cause of the issue. Renamed that file and the issue was resolved - at least temporarily.
Of course, now I am trying to fix that repo file - but that is a secondary problem.
Hope this helps!