labofsahil/github-event-dataset-2012 huggingface dataset:
True. good catch. Did think about it when I first saw the code to mention, but thought FSM would mean more dependencies, but now I see it is  in akka-actor.
The problem is not related to locks, but a finite number of threads in ZooKeeper.
Remove line @param coordinate, or describe what the coordinate is.
It's a placeholder in case we ever have to support multiple trades occurring simultaneously.
This does, but it is bounded on the next line specifically for this purpose... maybe some day I'll come up with a version that doesn't use slope.
Yeah, its probably best to not use an all-or-nothing approach to overrides. Will rework.
Looking good anson!
I suggest to speak about the iOS Simulator first and then encourage to test on a real device.
Change the vairble name to $permissions please
Please save the temporal file on shared folder (PATH_DATA), because this folder always has write permissions
Note that this pull request is more urgent in that it fixes a problem in DataSet statistics upload and should be deployed before uploading more sets, if possible.
I'd suggest using a separate variable to indicate error conditions.
as above, change this to addon flyout or somesuch.
Do we not want commands to have timestamps?
See issue #218
That seems like it makes the code harder to read without any particular gain; would the JSON content type - which is API - ever vary in the real world?  If not, why not just hard-code it?
The request should have the User object, not the user id string
I'd still like us to fetch the comments after each failed create, just to make sure that nothing has been created.
I renamed `getFullConfig` to `getConfig`, removed `getCached` and created an internal function `getConfigFromCassandra` to fetch config values form Cassandra if needed.
The documentation for this is a bit out of date. I'll fix.
I wonder if we really need this function. We could just pass in all the errors all the time.
Once issue #64 is addressed, we'll be able to dramatically simplify the admin checking to
`if (context.user().id === principal_id || context.isAdmin) {`
The idea of roles v.s. permissions is that all roles operations are always direct. There should be no notion of "give me a role that I have by virtue of group membership" (`getAllRoles` was a mistake that I made, it should have been called `getPermissions`).

Any part in the code where you are wanting to get a role indirectly, or check if someone has a role indirectly, it's probably better considered a permission operation. Using `hasRole`'s new implementation as an example, it now does an indirect check, but it's actually identical operation to what `isAllowed` used to be. When I check "Does this user have the manager role?", what I'm probably **actually** asking is "Can this user manage this resource". It makes more sense when you consider an editor role in the future. You will want to ask "Can this user edit this resource?", instead of "Does this user have manager role or editor role?". You'll especially want to be asking the former if you take into consideration potentially more roles being added in the future, and the potential of configuring the actions a particular role can do on a resource, like you can do in CLE.
IMO, not a good idea to have a ``var`` here. I think it would make much more sense to implement it as follow:

```scala
private def name: String = getName()

def getName(): String = {
    try {
      thread.name
    } catch {
      case e: ObjectCollectedException => "<garbage collected>"
      case e: VMDisconnectedException  => "<disconnected>"
    }
  }
```
I wonder if it wouldn't be nicer to refactor the following 5 lines into a method. They seem to appear in almost the same form in all tests.
I would add the following words:

These are a small number of component-based fixes **delivered by Liferay's support team** that address **specific** customers' **issues**.

I've changed from "needs" to "issues" to avoid giving the impression that it is used for improvements.
There is an error on this line ... has **'DEFAULT COMMENT ...'** which is incorrect because COMMENT can't be a DEFAULT.
did you forget the "i" ? :)
This is presumably why the segment and rsegment accessors exist? So the n - 1 calculation can be hidden away in that method and all one needs to know it that access through those methods is 1-based.
Спасибо за комментарии. ) А вы можете посоветовать что-нибудь почитать по objective-c( начального уровня)?
Просто из вредности :)
Отладочные принты в финальной версии приложения желательно убирать.
Thank you. It is Interesting point of view regarding Cell and it DNA. I agree with you, but I am not sure about crash.
Для значния длины массива вместо цифры 100 лучше создать отдельную переменную с понятным именем и комментарием. В случае если с вашим кодом будет работать кто-то другой это значительно упростит ему жизнь.
We should be providing an example of this after "hours" (e.g re-fetching after 7 days = 7 * 24 = 168)
Do you want to internalize this feedback and try another pull request?

On Tue, Dec 18, 2012 at 11:46 AM, adam <notifications@github.com> wrote:

> In lib/src/runtime.dart:
>
> > @@ -0,0 +1,242 @@
> > +// http://developer.chrome.com/trunk/apps/runtime.html
>
> > +library chrome_runtime;
> > +
> > +import 'package:js/js.dart' as js;
> > +import 'package:logging/logging.dart';
> > +
> > +class Runtime {
> > +
> > +  /// Properties
> > +
> > +  /**
> > +   * This will be defined during an API method callback if there was an error.
> > +   */
> > +  Future get lastError {
> > +    Completer completer = new Completer();
>
> Personal habit of pre-editor type inference :) Will change.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/dart-gde/chrome.dart/pull/2/files#r2451112>.
>
>
nit: line length.  dart style is 80 col max
I'm not sure if it will be a problem.

Bugsnag is using this approach: https://github.com/bugsnag/bugsnag-ruby/blob/master/lib/bugsnag/sidekiq.rb
Suuuuuuuuuure
Could you change the `help` description to describe the `api` command here?
Could you please use `metashare.storage.models.MASTER` here and in similar places?
if the future if we have problems we will use that the coil type FIFFV_COIL_NONE
instead of rng use random_state, like in generate_sparse_stc()
`editor.editor.panes.preview` is super weird, but it worked. Is there a more direct way to grab the right object?
"[...] is to show how are you" isn't grammatical English
Could you please add tests for mergePatients showing your changes fix issues from TRUNK-3351?
The superclass OrderValiador already checks this
This should be logged at debug, not info.
Yes, sounds much better.
First, thanks for taking the time to submit this patch!

In the appropriate case (e.g. an el5 or el6 builder) this is a huge improvement. However, it will only work if lsb_release is installed, which is not guaranteed on minimal installs of fedora or centos. Perhaps try lsb_release if present and fall back to parsing /etc/redhat-release if not?

Also, with this use of lsb_release would give undesired results if building on fedora (which is what our main Puppet Labs rpm builder is), e.g. returning el16. We'd probably want to check for fedora and prefix with 'f' instead of 'el' in that case.
Looks like it's a dependency for `rails-observers`. If I remove `journey`, then I get a dependency error:  

> Could not find gem 'journey (~> 2.0.0) ruby', which is required by gem 'rails-observers (>= 0) ruby', in any of the sources
This format can be pulled out to an initializer and given an name.
Can you refactor how you're quoting in here?  We tend to avoid backslashed double quotes now.
This method doesn't do anything, what is it for?
¿Por qué se quitó este Partial del proyecto? ¿Ya no se usa?
Ooops ;-)
FreeNode doesn't want this kind of crap on their network...
That would work too - I was just copying the way posts were created in other tests above this one.  I'll update.
This won't work with diablo, this uses instance_uuid.
whats wrong with prefixing the name with rd when we have nova exceptions as well?
I guess I skipped the 'node' part when reading... I think 'Infinispan node' would be a tiny bit clearer, but feel free to ignore that part of the comment.
this should also be placed in Log.warn...
Ahhh I see, that makes sense.
Apologies if this seems really basic, but wouldn't this be better as;

If(self =[super init])
 Then having the return value as an else clause.

This would cut out a number of potential unexpected behaviours, 

If for instance the expected return from super init is that it returns its receiver, but with inherited values returned, then the function will still work as expected. 

If the return from super init is nil, indicating an error, the return value will still be nil.

If the return from super init is anything else then this will be handled as a nil return indicating an error.  This will he handled as a nil return.  This would make the code more robust. 

I'm quite new to objective-C, and I apologise I'm making a noob error.
Ok, I moved the redundant grayscales into their own section and discouraged them, and added a note to the qualitative section.
Style police: No backslash line continuations, please.  You may use parentheses here instead.
Look at `test_lockscreen` to see an example.
the only issue there is that default behavior would be broken on app servers, maybe pull out *request* into a separate namespace and reference from both?
this needs to be the same license as the rest of logmagic.

CC @mgutz
Can this just be `.hover(hoverIn, hoverOut)`?
Can you use `` ! empty()`` here?
Hmhmh has it been discussed? I think we should provide an option to do some kind of precomputing there in the model selection use case.
If we want support in future another formats, then no. If no, then it can look like this

@Route("/articles-lists")

and format will be allways json.
test case fix for IE9.
Complying with the general style of vanity here.
Well, imho, I prefer to force privilege escalation when you're doing an admin task:
First it ensures people are aware of the hazardous nature of the command their issuing since they have to do additional work for the command to run.
Second, privilege escalation most of the time implies re-authentication, which avoid the problem of hijacked session (terminal left open without anybody in front of it, etc.)

But that may just be me being paranoid ;)... Anyway, I hope the new version is more explicit regarding this point.
Private would be good if everyone used the getter to use uuid. But they don't. Let's fix this in another pass.
what does the color have todo with anything?
Are you sure ``$numBytes`` has the correct type as "double" is not a sub-type of "integer"?
headerTitle is in both TableView and TableViewSection.  Having the KS code reference that is not present in the docs is an issue.  It should be run by appcel, but first it would be good to sync our KS branch with the latest from appcel, in case this code has already been changed.
I like the description of the gaffer too.
and I know it is the same syntax than the previous filter (added by myself following a discussion in the Twig issue tracker). But I find these names quite unreadable, which is why I suggest renaming them
По запарке забыли убрать! Исправим
Seems the enclosing window should be responsible for verifying the UA is able to handle postMessages.  So this guard is just there to avoid  triggering errors when reporting the results to windows on the same origin using the current system.
and did that professional js-coder also explain to you why it is suposed to be _"better"_?
It's DOM Level1, granted, but that's about it :)
Not only will this save a variable, a loop, and memory, `innerHTML` is also much faster which is why virtually any JS lib is using it internally to speed up these kind of "mass" DOM manipulation.
**+1 that you ripped off the dependency to MooTools from renderMessage!**
That looks like a file encoding error.  Can you fix that?
@erwinwinder Is this a good idea ? I don't know if renaming test to testng will break something for people ???
no, good point. It started as something else, than became this...
Your scheme definition could demand the presence of the attribute but not define a value.  Sorry, I won't accept this feature without a stronger argument.
One reason: I had forgotten Java's default behavior. Fixed.
>And I wanted that you argument why they might not be good. :-)

I did :).

>allows us to same serialization as we are using for REST protocol

I also pointed this out in my first comment when i changed to signals defined in mongoengine.

Signals are now fixed, serialized as we are using for REST protocol and have all the objects that might need in the future.
How no? Each user has its own list of panels:

```
class PanelState(mongoengine.EmbeddedDocument):
    collapsed = mongoengine.BooleanField()
    column = mongoengine.IntField()
    order = mongoengine.IntField()

class Panel(mongoengine.EmbeddedDocument):
    layout = mongoengine.MapField(mongoengine.EmbeddedDocumentField(PanelState))
    some_property = mongoengine.StringField()

class User(auth.User):
    panels = mongoengine.MapField(mongoengine.EmbeddedDocumentField(Panel))
```

You can then even have panels define their own custom document:

```
class MyPanel(Panel):
    some_additional_property_just_for_this_type = mongoengine.StringField()
```

And `User`'s `panels` field then maps between ids of panels and those documents. For now we have just default Panel document, so it is easy. But later on each of them can be also custom documents, as defined above, inheriting from the common document.

So, what exactly is not possible to do here and why would your solution be superior to mine?

(Just to be sure, I like that you argue and are not giving up, so please continue and provide arguments. It might be that I am really not seeing something, but I do not like the idea of one more level of indirection if it is not necessary.)
You should wait for it to finish.
Don't include JavaScript file, add it to the HTML header.
Don't reveal the reason. Just write something like "The confirmation code is invalid or has expired. Please retry."

Also, I would use this in form validation. Not here. This is the idea. Form validates that confirmation key is OK and if it is not, it is a form error. Then here you just set `email_confirmed` to true and this is it. ;-)
I removed userlist.html all-together. Is it still present?
Or (I don't remember if string should be in one backticks or two, sometimes you can make it link to Python documentation then):

```
:param dict layout: mapping of count of displayed columns(`string`) to PanelState() objects for that count
```
Be a bit more precise with style. So here is one unnecessary line. Ant there is not an empty line between blocks.
```c++
int32 spellId -> uint32 spellId
```
&lt;/li&gt;
this change seems to affect non-keystone codepaths, too, and possibly result in an out of bounds memory access?
Hi, sorry, what are the coding standards? Symfony2, Doctrine2 or Twig? Thanks :)
Ok, sorry, not 100% sure of what the test wanted to validate, I'll fix it ASAP.
I'm just curious, why do you put these here, in the non-platform specific CSS file?
Sorry for this bad stuff... I did not clean the pom before pushing it... 
You are totaly right about your comments.
I will correct that sorry.
You can re-bind the callback function (`function(results, status)` to the current `this` (only relevant if this were part of `Heater` or something else) by changing this to:

```javascript
}.bind(this));
```

The shortened form being:

```javascript
elevator.getElevationForLocations(positionalRequest, function(results, status) {
  if (status != google.maps.ElevationStatus.OK) {
    $('#elev_info`).html(status);

    return;
  }

  // do stuff with the result

  // this != elevator, which it would be without bind()
}.bind(this));
```
"Create a pair of observers that invoke `onResolve`/`onReject` and propagate the results to `deferred.promise`."
Leaked on the error paths.
shape handling is outsourced ?
``_GenericKDE`` is now also a base class for the regression class, which doesn't have ``loo_likelihood`` or ``imse``. So remove ``loo_likelihood`` here instead?
но в рамках библиотеки я бы это сделал не так, а через передачу `data=""` в `make_request`, а там - установкой хедеров в случае PUT

и комментарий сделал бы не про `nginx` а про стандарт http
actually it won't survive server restarts. If this is copy pasted from the other examples let me know so I can fix the examples
+Whitespace
This line is not needed, I think.
hum, then maybe put this method in TNLibvirtEntity, rename it to something_esle

Then implement in TNArchipelVirtualMachine and TNHypervisor:

```python
def on_xmpp_loop_tick(self):
   self.something_esle();
```

That would remove code duplication
Does this need to get built every call?
Thread safety problem here.
what if we donate a negative amount? Stripe doesn't allow donations under .50, 

we should handle this more gracefully, at least do @donation.amount < 1
Great, thanks so much. I'll be keeping the backers updated, and will probably solicit feedback at times.
Can you think of a stdlib method that yields with multiple args?  I was trying to write these based on ruby built-ins rather than defining my own methods for these examples.
i agree .. no tags at all would be best .. then one can safely use it in titles etc ..
It still looks like it does touch the DB — `.save()` is still there. Or is it mocked out to do something else?
@habibvirji By the way, we sould also include a way to know programmatically if we are running on pzp or pzh.
There is really no need to create a one-line code here. :-)

Please split this into a simple for loop which goes over values, filling one temporary dict on the way, and then calling `datetime.datetime` with that.
Закрытие System.in.
Откатил pull request. Зачем коммитишь мне format2?
Ага, я понял, файлы поддерживаются. Тогда вот такой вопрос - почему в main() разбираются параметры, но файлы не передаются в ParallelSort? Можно ведь было разделить полностью разбор командной строки и, собственно, сортировку.
Его не нужно экранировать. '/' - такой символ есть.
This assert is failing, <code>payment_settings_page.header_title</code> is returning 'Basic Info'.  I suspect the page hasn't had time to load and is grabbing the old title value - setting a breakpoint shows that the page title does correctly update when the settings page loads.
This was a holdover from the Matlab implementation.  Without any conversion and scaling, the output will be a uint16 of full range for grayscale and scalar images, and a color image will be a float (0, 1).    I can standardize to one of these if desired.
>  >  ZEROLOGPROB = -1e200

>    This constant (and the lines below) seem to me to be for internal use, do
>    you think they should be exposed in __all__?

No
So I see you are of the optimist persuasion ;)
I'll add it.
I was also thinking of the multi-layer perceptron, if @amueller feels motivated :)
More commented out code?
iend += istart?
Was this supposed to be `0x80`?
Don't hard code these values. Use:

  bb::device::DisplayManager displayManager;
  bb::device::Display& display = displayManager.getDisplay(displayManager.primaryDisplayId());
  QSize size = display.pixelSize();

  dCapsObject->Set(String::NewSymbol("platformWidth"), Number::New(size.width())); 
  dCapsObject->Set(String::NewSymbol("platformHeight"), Number::New(size.height())); 

  QSizeF physicalSize = display.physicalSize();
  float physicalWidth = (physicalSize.width() == 0.0f) ? 229.0f : ((float)size.width() / ((float)physicalSize.width() * 25.4f));
  float physicalHeight = (physicalSize.height() == 0.0f) ? 256.0f : ((float)size.height() / ((float)physicalSize.height() * 25.4f));

  dCapsObject->Set(String::NewSymbol("xdpi"), Number::New(physicalWidth));
  dCapsObject->Set(String::NewSymbol("ydpi"), Number::New(physicalHeight));
Should be TI_DEBUG, but since that's probably already taken I would suggest you get rid of this enum in favour of passing around the tag to prepend in toSystemLog. Then you won't need the switch in toSystemLog either. The tags should go in TiMessageStrings.h.
Can you provide reasons why they should be there.
This insert will cause a memory leak if an event with the same name has already been defined. An example of this is the 'click' event will be created in the base class (NativeControlObject). Create a method for detecting existing event containers with the same name and destroying the old objects that are to be replaced.
It'd be more idiomatic to use 'unless' than 'if not'
Should possibly protect against memorySpillAt = 0 (and pass 0)
But assert is in debug mode only, which is known to be slower.

Anyway, if that macro can be turned on by a wider "paranoid" or "extended_debug" macro, than I see the value. Otherwise, it'll just be lost in the sea of unused macros, and people will rarely (if ever) turn it on to debug related (but not direct) problems.
Our implementation of find for regular expressions will locate the first instance of the expression.  For example 'mysash!' would still be true, which is not what we want. To achieve the syntax and behavior that is desired I had to use the boost regex library.
We're theoretically meant to be moving away from .ipp files (see <HPCC>/sourcedoc.xml), but that hasn't really been happening.
I'm confused again... ;)

```useINotify``` is still recurring one time only. Isn't it something that ```monitorDirectory``` should care about?

Either way, ```useINotify``` should recur all the way through, or nothing at all. If the former, all ```inotify_add_watch``` calls should be in a separate, private recurring method. If the latter, this block should be removed.
Can we just remove the `user` field completely or does that totally break the frontend? We can update the front-end code of hypothesis/h so that it doesn't assume the acct: uri format.
you should remove the extra empty lines
I can understand the filtering of values that are `None`. But not those that are `''`. That's a perfectly good value. Just very short and unpractical in general. However, it's value. 

What if I want want `?name=` in the query string? 

If you pass the value as `''` into the template and don't want it in play, then that should change it to `None` instead.
"valid" is not a great word. To me, the opposite of valid is "invalid". But they're not invalid, they're just without data. 

How about `has_data_versions` or `featured_versions`?

ExtremeNits LLC.
This is an area I want to do a bit more thinking. I am fairly sure we can use a conditional around this when we can guarantee email uniqueness (something I am looking at adding better support for.) For now leave it in and it can be modified later.
@jkff shouldn't this be added to the nova::api class? Do these settings need to be configured for all nova roles?
Can `self["multiple"]` ever return `"multiple"` instead of `true` given the above modification to `[]`?
Well I thought that it might be required to ensure that it is indeed selected instead of the original one. For example if 1.0.0 exists, and you want to override it with a feature branch, you'd say  `dev-feature as 1.0.0`, then you have two 1.0.0 in the same repository, and I don't know what happens. I guess we could adjust the policy so it selects aliased packages first?
Having Watir as a dependency is no go. Why not just reuse the existing test application which opens already automatically?
nit: this test would make more sense in the begining of the method. i.e. before `let listeners = observers(target, type);`
What would you say about $additionalInstalledRepository?
Added the methods to interface.
override further down
I mostly agree with the concerns. Returning raw pointers is always a bit tricky.
Mobile Web doesn't have proxies, so this doesn't apply to us.
This should be the correct behavior.  If the activity in question is the root activity then the app should exit.  The problem in the test case is likely an issue with the test itself where the tab group is being opened as the root activity rather than the rootWindow.

Based on the test case, I don't feel that the ticket or PR is required.  Please provide further clarification / justification.
Will be fixed later today, thanks @dawsontoth
Did you improve this section? It looks better.
The rest of the code in set_form_fields would be more readable to say `value['widget']` instead of 0
see comment about unittests
default arguments are already readonly=true and propagation=required.
This approach will affect base class (e.i. `Model`). You should use instance variables instead.
It's an internal module; the docs won't show up anywhere either way.
should this version be private?
Didn't know there was a hard rule about 120 characters. Will keep it in main, thanks.
@shoo I have experimented a bit with this and explored spec more and still not sure what to do about this. writeln(typeid(typeof(dg))) just ignores almost anything so is hardly a reference and I wonder if shared and nothrow are part of a type, as those are function attributes and generally belong to symbol.

Also current dmd prohibits me from declaring delegate variable of such type: "Error: const/immutable/shared/inout attributes are only valid for non-static member functions", sounds like a bug?

tl;dr: implementing is not a problem but I need someone to guide me here on theoretical language-related side.
I'll roll this back
And one last step :) Revert this change (just remove "  and sargis")
No need to restate stuff that is already in the parent.
Move this into test code. It's static, so that should be really easy.
*slap*

On a more serious note though, @unknownbliss wouldn't allow me because I **must** work on this :p
"3 days"
Can we do something like set the variable `@all_patients` in `Given the following patients exist` and then using that in steps like

`Then I should see all of the patients`

and

`Then I should see all of the patients except ....`

Low-priority.
you should add another ``@author`` annotation for Matthias
Try to use consistent code style and formatting across the project, as it makes things easier to read. (Spaces before and after the = sign. Space after the if a few lines down.)
Not sure why - I did not edit this file. Also, this line presents in my repo. so it will be restored with the next checkin.
This cannot be right
If you have other keys/values, they just won't be editable (until a solution is found).

Concerning the controller, if you have a specific value, it will re-shown when editing (as well as locale and template).
А вторую часть-то зачем так формировать? Там же вообще всегда будет `%2!%3@%4`, не? Так что поставь %2, а строку формируй уже плюсиками.
I see what you mean.  I tried a different tack on this, actually.  Shortened it a bit.  Is this any clearer?  Seems like a more standard way to output, too.
Even thought his is only currently one line, maybe we should make it a separate function in case we need to add more to it?
create the hash set lazily, as this object doesn not need to be created in the case there's no collision between the transactions.
MINOR: Missing parameter comment.
Is it not possible to avoid suppressing `rowtype` and `unchecked` warnings here?
This looks great. I forget I use a private maven repository.
Ah. :P
Getting used to this comment style still.

I don't know if its an imperative key or not. There's little to no documentation on it at all.
I'll do some testing with it absent.
On Wed, Feb 29, 2012 at 07:29:20PM -0800, Nick Anderson wrote:
>> +ostype: Linux, Solaris 10, AIX
>
>I think these need to be valid class names as well.

Are they supposed to be human or machine readable?

-- 
Neil Watson
Linux/UNIX Consultant
http://watson-wilson.ca
It's not a clear cut case for either, case insensitive works for me.

It looks like "inherit and extend" is a common use case for `@inheritdoc` ... It shows up in DI, Validator and Translation components, various Doctrine projects, etc, and is important when adding additional annotations. I'd say we err on the side of flexibility and go with your current implementation.
here i just rename the parameter to be consistent
This should be the three letter currency code.
extensionRegistry is used to get extension field descriptors with the containing message descriptor. Then the returned extension field descriptors are merged with the normal field descriptors to form the complete schema.
fix the placeholder
haha dork :P

On Apr 3, 2012, at 9:02 PM, Craig wrote:

>> @@ -378,6 +378,7 @@ function cmd_install() {
>>     run_devstack
>>     ensure_local_sources
>>     install_packages_2
>> +    exclaim "FINISHED INSTALL"
> 
> i thought it was important. :)
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/hub-cap/reddwarf_lite-integration/pull/36/files#r642898
I was thinking `result = [%s]` % instance.status[:1]`
you dont want the screens to start up here any longer?
Hmm. Can `related_resource` object/class be shared among different instances of resources? In this case you are overriding here some value which could break something else?
The word order seems strange: One must not mark a given method return value for cascaded validation more than once in a class hierarchy
Isn't this a *list* of custom bucket *names* rather than a single name?
otherwise, this is perfect for an inject :D
count is a bit of a vague variable name; want to make this processedConversations or something more descriptive?
you reverted them the wrong way
I don't think we are showing the /api/v1 component elsewhere.
I think you are right, it is correct.  But I just noticed we aren't consistent throughout the API...

Can we add it everywhere or remove it everywhere?
The default queue must use the direct exchange pattern : so no routing key (empty one). There is no need to be able to configure the pattern, just the name of the queue... like it is in the current master branch. So the idea is all messages will go to the default queue unless a backend is specified in the queues section. This will allows to create dedicated queues to long task runs (encoding video) and leave small tasks inside the same consumers.
achteraf wordt trouwens nog gecontroleerd of de gebruiker wel degelijk een User is.
I have moved most of strings into a dedicated Constants class.
Trvial but I think you should have equals here; not endswith. the existing endsWith is for (un)?marshaller.
There seems to be many ways to do this, so my next commit may or may not be along the lines of what you're anticipating.

It also seems that this TaskListener does not go to the build console anyway (I'm not sure where it goes, actually).  That may have just been a failed test on my part, so I will check again to be sure.
s/"Scripts an stops"/"Scripts and stops"
Podminka na instalaci musi byt mimo, pak se nezobrazi v ACP v nabidce pokud je SN odinstalovane
Функция для пометки, что определённый узел и все его родители не должны удаляться. Сначала останавливает таймеры на удаление, помечает все узлы на удаление, затем помечает, какие узлы удалять не надо, затем ставит таймер на удаление ненужных узлов.
OK, a different PR then
This is initially what I wanted to do, but it didn't work.
Incorrect english
А, таки да, вы правы.
What's the failover story here? Since CleanUp only called in CheckComplete which in turn is called in a deferred task by BatchTask.Complete or by batcher Ready (which is also deferred).

This is sufficient since tasks will retry and a failover means there are surely fewer to delete?