How can I set collapseRequests in my buildbot master.cfg - buildbot

I try to set collapseRequests in my buildbot master.cfg, but when I add
c['collapseRequests'] = True
Error shows that "Unknown BuildmasterConfig key collapseRequests";
When I try to add collapseRequests in BuilderConfig, using
c['builders'].append(BuilderConfig(..., collapseRequests=True))
Error shows that "__init__() got an unexpected keyword argument 'collapseRequests' (traceback in logfile)"
Any suggestions?
Thanks.

Probably you are not using a version of Buildbot that supports collapseRequests. If I Google for it, I can only find references in the documentation for the development version of Buildbot. If you check that page, you'll see at the top there's a warning that the documentation is for the development version of Buildbot and there's a link to the documentation of the latest released version.
The latest released version (at the time of writing this answer) is 0.8.12 and does not support collapseRequests. What it does support is mergeRequests.

Related

Moodle - Using "Old code" when I am actually using the newest version

I have had too many problems with my ubuntu moodle server, so now tried to do a factory resetting of my server and install everything anew. Even though I checked out with the newest git repo available, I am still getting the following error message:
https://imgur.com/a/raAd7VB
The branch I checked out with was 'origin/MOODLE_400_STABLE'.
Thanks in advance.
Check the value for version in your database
SELECT value
FROM mdl_config
WHERE name = 'version'
Then search for the value in the releases, this will tell you which version the database is using
https://docs.moodle.org/dev/Releases
You might need to do a git pull for the latest version of Moodle 4

apostrophe cms version 2.65.0 giving error on running project

I am upgrading the apostrophe version from 2.62.0 to 2.65.0. While upgrading I have added the mongo driver-3 into setting also still running the project, I am getting the error :
(node:116248) Warning: a promise was created in a handler at project/node_modules/async/lib/async.js:167:37 but was not returned from it, see xxxx
Thanks for the help in advance!
This is only a warning. bluebird thinks we might be unintentionally ending a promise chain, but it is intentional and nothing is wrong. It was addressed in Apostrophe 2.68.0 according to bluebird's instructions for silencing it where appropriate, so update to the latest with npm update and it will stop.

Getting "Error: Failed to connect to OmniSharp"

I'm trying to get VSCode working with my Unity projects, and every time I select the Project icon (the little fire at the bottom) I get the following error:
Error: Failed to connect to OmniSharp
Is anyone else getting this?
You need to download the most recent version of "mono". Open up terminal and pass in brew install mono. Then "Pick a project" and select the ..-csharp.sln file and you should be up and running.
Ok, made some progress and gotten a few Unity projects working. It seems that you need some prerequisites installed, a clean up of your Unity project folder, and possibly some hand editing of your .sln and .csproj files.
I posted a (possibly) better answer over on Reddit. Hope that's not breaking stack etiquitte.
http://www.reddit.com/r/Unity3D/comments/34d6gc/visual_studio_for_mac_help_us_vote_for_unity/
i get this on windows when my project directory has a space in it
i removed the space and removed the error
i expect it will be fixed soom
I have a completely different answer: it's the runtime that VSCode is using. It doesn't match up with what it thinks it needs. I have to remember that we're still in beta and that things are changing rapidly. I had my dnvm running beta 7, but VSCode (and OmniSharp, by extension) is looking for beta 6, so it was failing. I updated my runtime using this this post as a clue. Now I have VSCode 0.7.0 using the beta 6 runtime. I have no idea how to tell what it's looking for...I just guessed based on when they were both released. HTH

Upgrade N2CMS to latest version collected from github trunk

I am upgrading an old N2CMS website to the newest version released in the trunk (2.2.5 or something like that), following these instructions https://github.com/n2cms/n2cms/blob/master/docs/releases/upgrade_2.2.1.txt but i am getting an error when tring to compile the project:
Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
Has anyone done this before and know if there's anything else i should be doing appart from just copying files?
Thanks
Complete text of this error contains the name of DLL you are missing. Read it carefully and you will find out what DLL you need to add. It could be something like Lucene.dll which was introduced recently (it depends how old your project is).

syntax error before '^' token in UIView.h - not fixed by changing compiler setting

I installed the latest official iphone sdk and now my personal project is getting the same compiler error in UIView.h as described in this question:
Syntax error before '^' token
syntax error before '^' token
The solution is apparently to change compiler settings to use GCC 4.2 or LLVM.
I've tried using every compiler setting available in Xcode that but am still getting the errors.
Is there something else I should be doing to support the (^) block syntax in my project. The project was building fine with the previous official sdk release (pre OS4)
Another strange detail, I only get the error in debug config, not release.
I tried comparing the build settings between debug and release but didnt see any major differences. Where there were differences I tried setting the debug config to use the release config values but still getting those errors.
thanks in advance for any help
ok so I just found my problem.
I was changing build settings by right click -> Get Info on the project but I should have been doing it on the target (which was still using GCC 4.0 even though the project was set to 4.2)
Make sure you have the right configuration or configurations picked when you change compile settings. It's easy to overlook this, for example: picking the Release build when you meant the Debug, or vice versa; or by using other custom build configurations.