labofsahil/github-event-dataset-2012 huggingface dataset:
Do you recommend patching up this Reachability or using KSReachability?

On Aug 16, 2012, at 11:21 AM, Karl Stenerud wrote:

> In Zinc/ZincRepo.m:
> 
> > @@ -992,6 +1040,16 @@ - (void) resumeBundleActions
> >      }];
> >  }
> >  
> > +- (BOOL) doesPolicyAllowDownloadForBundleID:(NSString*)bundleID
> > +{
> > +    ZincConnectionType requiredConnectionType = [self.downloadPolicy requiredConnectionTypeForBundleID:bundleID];
> > +
> > +    if (requiredConnectionType == ZincConnectionTypeWiFiOnly && ![self.reachability isReachableViaWiFi]) {
> You have to cache the reachability flags, but the standard Reachability implementation doesn't do that, unfortunately. You could hack it a bit to have it send a dictionary containing the reachability object and flags in the notification, and then cache the flag values in Zinc somewhere. There's no real clean solution the way it stands now, which is why I rewrote it...
> 
> If we keep Zinc from updating while a game is playing, the hiccups might not be too noticeable. Or maybe have it check the WIFI status on a background queue?
> 
> —
> Reply to this email directly or view it on GitHub.
> 
>
Isn't `(page.rgt != page.lft + 1)` equivalent to `page.leaf?` or something like that?

Also what's with calling `method`? Seems bad. :goat:
You should add a note sayign that the shell cannot be used to clear the cache (at least not without process isolation) as the old cached classes would continue being used)
@stealth35 yes you are right. I had bookmarked the standards long time ago.
See the new commit. 

On Jul 27, 2012, at 9:05 AM, Mike Burns wrote:

>> @@ -137,8 +137,8 @@ def sanitize_hash(hash)
>>           end
>> 
>>           @s3_headers[:storage_class] = @options[:s3_storage_class] if @options[:s3_storage_class]
>> -
>> -          @s3_server_side_encryption = @options[:s3_server_side_encryption]
>> +          @s3_headers['x-amz-server-side-encryption'] = @options[:s3_server_side_encryption].to_s.upcase if
>> +            @options[:s3_server_side_encryption]
> 
> This would be easier to read without the `if` surprise.
> 
> This is a bit of a change, right? Previously the user could set `s3_server_side_encryption` to `''` (the empty string) to disable it. Now, they have to use either `nil` or `false` to disable it, and they can use a symbol instead of a string now too.
> 
> That's not a problem, just verifying that this was intentional and desired.
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/thoughtbot/paperclip/pull/973/files#r1252296
I don't think you need the attribution, here or below.

I think that having quotes makes it a little too informal (might just be me) but I'd definitely remove the " -you "
You're exactly right.  I'll fix it.
that's what i was leaving up to you in terms of cleanup of that section. the camino and mrtrix workflows have exactly the same names for the workflows and have multiple workflows. it's really something i haven't used or worked on and i don't know which workflows are relevant to a package level import. i suggest doing that in a separate PR.
In these and other cases where it makes sense to leave "3D" in the name, I think we should capitalize the "D" as I just did.
it might get confusing having this method with the same name as the string.strip() -- would clear() be better, perhaps?
Ну что за пипец, почему бы не написать это на предыдущей строке?
А иконку установить?
Переносы! :3
I also agree I think `require "foo" . (true ? "1" : "2") . ".php";` should be valid. Because it doesn't appear to be a function call. Currently, the rule will allow this behavior.

However return (); does look like a function call and shouldn't. Personally, I think it's dirty looking and shouldn't be an exception to the rule.

Anybody else wanna break the tie?
//TODO: habría que quitar los estilos de acá. Nada importante.
`<font>` tags are frowned upon. You could wrap the text in `<span>` tags, give it a class, and add the `font-size` you want to the CSS.
Why the s in front of {$db_prefix}?
You could also do this using attr_accessor.  One of Ruby's magic features :)
replace status with state
left space
what about namespacing by `phraseanet` instead of `pref` ?
"copy" changed back to "move"
This must not be there!
It's on the next line. Notice how GitHub only shows the three lines surrounding each changed chunk of the file.
ok i will make the necessary change
This file was renamed to player.html.
Have you tested the case of not having a branch specified?
@jspahrsummers yeah it's relative. :+1: to going the extra yard and making it an absolute `NSURL`.
We should first check that `head` is not `nil`.
Hi, can you tell me what is meant by matrixSize. What values are in there? Where and How do I get the right values for my WMTS Layers?
is this class part of the CrashReportList?
It should have a different indent if true
Do we have an associative smoke-test on MozTrap we can reference?
well empty doc?
Hm, are we preferring 5.4? So far we haven't had much test coverage on it (apart from Simon W.)
Sorry. I'm idiot. :)) Need to sleep more I guess :)) Just realized that logical_path is not a relative path....
Is this the right way to communicate how a for loop works in Python?  Traditionally in many of the earlier programming languages, a `for` loop operated by incrementing an index, and performing the same block of code with the incremented index.  In Python/MATLAB, a `for` loop works by taking the next item in a sequence, and performing the same block of code with the current item from the sequence "standing in" as the declared loop variable.
Nit: see above about not using units when using `0`; also you shouldn't mix units in a single declaration.
comment to make a comment :)
add a line break in here
Ah, yes, I like the `alive` check.

I made the changes and pushed the commits. Any further changes, or does everything look good now?
How about making the return type a bit more specific; maybe use ``array<array>``?
Can we simply make sure that any unhanded exception in Symfony ends up sending an email, either because we wrap the airbrake call, or because we track them in splunk, etc.?
you need to skip the test when the Couchbase class is not available instead of making it fail with an exception
Also, I've left 30px for the content padding, so that's why 720px and not 750px.
All changes made to files in the skins-directory need to be applied to collecive/tinymce (3.4.7-plone branch) otherwise they will be overridden on the next development build. See https://productstinymce.readthedocs.org/en/latest/
Would be nice to have this one as false too. Good to prevent possible linebreaks causing errors.
Initial value should be set here, but I'm not sure how to create constructor with arguments (so that request can be passed). What am I doing wrong:

    def __init__(self, request):
        locationChoices = [("%s_%s" % (backend.get_full_name(), node.id), node.name) for backend, node in nodes.get_all_nodes_with_backends()]
        locationChoices.insert(0, ('-1', 'None'))
        init = get_initial_value_from_request
        locations = forms.ChoiceField(choices=locationChoices, initial=init, label=None, required=False)
        forms.Form.__init__(self)
Good idea. :-)
Doens't know how to create this with subclass
Should maybe also English version be: *Password (repeat)*?
No. This is not independent feature or feature which would build upon this one, but is requirement for good implementation of this feature. You can create different ticket, but then you will have to do it first, and then come back here. :-)
Why not `/confirmation/{{ token }}/` and `/confirmation/`?
Fine with me. :) It's fixed anyway...
Why the CamelCase?
why change? did it not work before?
Fixed (bad merge). Github hasn't flagged this comment has outdated.
Not sure about these changes. I hit a similar issue in other work, but not sure this is correct.
You should comment about why it's USE_TEMP and not CACHE_PATH...
from what MIB?
add something like:

TODO: consider subclassing ThreeCom to avoid code duplication

but we won't do it now, later is fine.
I guess I'd be happy with an error counter of some sort to keep track of enum mapping failures. This would avoid behavioral change while still exposing errors more immediately to clients.
I don't quite understand what is meant by Jose's comment about staying true to the sources data. To the non-RDF world, Wikipedia is the authoritative source for the content that is current stored inside of DBpedia. We are unique in referencing "DBpedia" as the center of the known universe, as others refer to "Wikipedia" in the same way.

Linking from dbpedia resources to wikipedia pages is good, whether using rdfs:seeAlso or another slightly more semantically meaningful predicate. 

However, I am essentially arguing that we change the preferred namespace for the dataset from "dbpedia" to "wikipedia", as Wikipedia is the original source of information, and the authoritative source of the identifiers. The reason I bring it up is that in future someone else may republish parts of Wikipedia in RDF forms that differ from the DBpedia method, possibly using different predicates and type structures. It would look a little strange to refer to their resources as dbpedia, even if they are only reusing Wikipedia identifiers, in their view, and their organisation has a different identity.
The label has to be base64 encoded, that's REST API restriction
The properties of the hosted service?
Is this still needed?  Doesn't seem like it.
This is the fallback content of the `object`. I guess I can leave this to the browser and skip my fallback altogether.
Are exception messages like these intended for end user consumtion? If so, we should externalize them.
This is useless. You're not likely to encounter it, and even if you checkout a tag, once you're done playing with it and still not on a branch, describe will give you nothing.
I think we should swap the min and the max, i.e.:
    end_pts[0] = min(end_pts[0])
    end_pts[1] = max(end_pts[1])

This will ensure the the 45-deg line will always start and terminate in the corners of the figure's axis. This is purely as style/aesthetic preference, so I haven't modified anything yet.
Why separate module/app for Facebook? I would move this into account app.
Right. The configuration reference will be up to date still. You don't need to recheck the file every time.
The string constant CLIENT_KEY_ALIAS is already present in CertificateManagerImpl.  The logic there does not fallback to 'gateway'.  Two recommendations:

1 - create a single string constant to hold this alias.  Include a brief description in the javadoc about what the constant controls
2 - Have a single method that does the logic here used by both places.
Probably written in FrontPage. 97.
I would accept up to a couple minutes I think, but I just timed a 100x100 run with the new Moffat code, and it still takes 17 minutes on my laptop, which is better than the 40 minutes it had been taking, but still too long for just a demo script I think.  I'll officially change it to 10x10 and put a comment that the real Great08 images were 100x100.
OK, will do this.
It seems that neither of these two are mandatory given the stuff below, maybe an an `, if provided` clause after each?
I moved your comment to the first time we use CCDNoise in this file.  Then here, I just have a brief reminder that gain=1, read_noise=0.
Two points here:
1. This might be worth switching to `e=ellip` with a comment that "e" can be used rather than "g" for regular e1/e2 kinds of shapes, rather than g1/g2 reduced shears.
2. beta = 2*theta.
I get a KeyError on this line, originating from riak_object.py L251.
People have been predicting that shift since K&R got it wrong.. .a *long* time ago. Unfortunately, I don't hold out much faith. I'll make the change myself (and even evangelise it), but I don't see the "average" programmer adopting it.
What if dsClosure is None?
Vamos manter um padrao. todos as verificacoes antes do teste (como esta consulta pra ver como a entidade esta atualmente, chame-a de ```antes```).
E o resultado chame-a de ```res```. da uma olhada no TesteDeAtualizarVoo
If the right_agent change fixes it, that is fine with me. Here is the test
program I was running from the right_agent repo to verify it.

Lee

#!/usr/bin/env ruby

require 'right_support'
require 'right_agent'

module LogTest
  include RightSupport::Log::Mixin

  def self.included(base)
    base.extend(RightSupport::Log::Mixin::ClassMethods)
  end

  def self.init_log
    RightScale::Log.program_name = "log_test"
    RightScale::Log.log_to_file_only(true)
    RightScale::Log.init("log_test",
RightScale::Platform.filesystem.temp_dir, :print => true)
    RightScale::Log.level = :debug
    RightSupport::Log::Mixin.default_logger = RightScale::Log
    true
  end

  def self.log_test
    RightScale::Log.debug("DEBUG Log")
    RightScale::Log.info("INFO Log")
    RightScale::Log.warning("WARNING Log")
    RightScale::Log.warn("WARN Log")
    RightScale::Log.error("ERROR Log")
    RightScale::Log.fatal("FATAL Log")
  end

  def self.logger_test
    logger.debug("DEBUG logger")
    logger.info("INFO logger")
    logger.warn("WARN logger")
    logger.error("ERROR logger")
    logger.fatal("FATAL logger")
  end
end

puts "Initialize Log"
LogTest.init_log
puts "Log test"
LogTest.log_test
puts "Logger test"
LogTest.logger_test
puts "Done"
exit


On Fri, Apr 13, 2012 at 4:36 PM, Tony Spataro <
reply@reply.github.com
> wrote:

> > @@ -88,7 +88,13 @@ def warn(message = nil, &block)
> >        severity, message = filter(WARN, message)
> >        meth = SEVERITY_TO_METHOD[severity]
> >        raise ArgumentError, "Filter emitted unknown severity
> #{severity.inspect}" unless meth
> > -      @actual_logger.__send__(meth, message, &block)
> > +      if @actual_logger.respond_to?(meth)
> > +        @actual_logger.__send__(meth, message, &block)
> > +      elsif @actual_logger.respond_to?(:instance) &&
> @actual_logger.instance.respond_to?(meth)
>
> Rather than doing this (encoding into RightSupport the knowledge of our
> busted SingletonPatch implementation), why not make the following change to
> right_agent:
>
> https://github.com/rightscale/right_agent/pull/35
>
> This is consistent with RightSupport's own version of the same idea
> (EasySingleton), with which we hope to replace the right_agent
> SingletonPatch someday:
>
>
> https://github.com/rightscale/right_support/blob/master/lib/right_support/ruby/easy_singleton.rb
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/rightscale/right_support/pull/34/files#r684593
>
I'm not sure if I prefer this over catching method missing. Thoughts?
Fixed this not linking to inbox,.
whis is this *.ls and not *.js?
This file is now defer-seq-both.js
Fixed, but pull req already closed. New request opened.
StringFormatterTester.class.getName()
This is very nice work :)

But there's one thing I 'd like to see different:
Take a look at PlanningEntityDifficultyWeightFactory, a difficultyComparator, PlanningValueStrengthWeightFactory and a strengthComparator. It's a very similar, but a different API.

So I propose we:
- rename BenchmarkRanker to SolverBenchmarkRankingWeightFactory (better suggestions welcome)
- replace rank(...) and getRanking(...) by:
Comparable createRankingWeight(List<SolverBenchmark> solverBenchmarkList)
- Just like the others mentioned above: using the Comparator or the RankingWeightFactory are XOR: it's either one or the other. I see no use cases to actually compare them.
- We should rename solverBenchmarkComparator into SolverBenchmarkRankingComperator?

What do you think? I am happy to merge as-is now too, it's good work.
Done. Added check
Did this get taken care of?
Do we need to keep the same package? [Split packages](http://nirmalsasidharan.wordpress.com/2010/09/02/split-packages-an-osgi-nightmare/) are a huge source of problems in OSGi, so I'd stay away from them if possible.
the reference should appear outside of the main doc block of text.

```
"""Returns the Kendall's tau correlation coefficient

The Kendall's tau correlation is used to evaluate the quality of a
ranking prediction. It compares the ordering predicted by the model to a
given ordering.

Reference
T. Joachims, Optimizing Search Engines using Clickthrough Data, KDD 2002
```
Sorry, it is not. This one computes sample weights, not class  weights.
core::string ?
Add some comment that clarifies what the @ does
I meant the text xD.
Have you tested it?  'g' stand for global replace, meaning not just the first.  It's typically a single pass over the whole input string, not repeated passes over the same parts of the input string.  As an example, s/aa/a/g on "aaaa" results in "aa", not "a".  That said, I haven't tested it either, so it's entirely possible I'm wrong, again.
Can we use the PropertyPath here, as we do in [AbstractElasticaToModelTransformer](https://github.com/Exercise/FOQElasticaBundle/blob/master/Doctrine/AbstractElasticaToModelTransformer.php#L90)? I think that's only available in Symfony 2.1+, so we'd probably want this solution for your PR and then patch it in the master branch shortly after merging.
As a general note, you'll have to update the apidoc to match the state of the api implementation relative to this work.

For instance it's important to note that the iOS anchorPoint (0.5, 0.5) is the center while for BB  (0.0, 0.0) is the center of a widget.  It is also not clear from the current BB docs wether what the unit is on BB.  It's also one case where it may be desirable to emulate the existing behaviour by doing the translation under the cover.  We'll need appcel's input on this one.
please move getZIndex higher to keep alphabetical order
matchは使っちゃ駄目だな。get,post,put,deleteのいずれかで。
You don't need that. I already modifed the DoctrineEntity so that it extends from Select (this was needed prior to some modifications that was made to the Select element).
Yes, ignore prev. comment here
yes.  The other branch looks correct.
What about supporting ``__toString`` as well ?
YOu should really rebase this so the history is clean.
I missed the question because you edited your comment. Would prefer additional comments instead so I get notifications of them.
Ok for the 1/, it was the only choice before, but it's *not* the redis-py way of accessing hmget and hmset... so it's not consistent with your previous comment "And so the closer to redis-py it is, the lighter it will be."

PS: i don't understand what you said about insistence :(
`if($connection && $connection->getFieldValue() ==  'close') `
@ctweney can probably remove misc_catalogid from the ignore up here now.
@raydavis So far we've been using lowercase canvas or bspace for the emitter names, but I actually prefer your approach here since we can use the strings directly in templates where needed.
@ctweney Good suggestion, will do
I thought so too, but I checked, it seemed to line up with the other lines before.
Did you copy the slogan from Mondator instead of Mandango? :p
What I'm doing Is creating a new service with cmd.exe and the paramaters of that service are the user provided windows command via /C
Agreed, have removed lines 79 and 80.
Weren't we going to disable this?
我的sublime text里面装了一个plugin，会把不符合规范的js code抓出来，这种写法就被重点抓出来了。运行上应该没啥问题，不过单纯看js code的话，之前我看到的还是行尾写逗号的比较多，可读性感觉也好一些哈
Yes, object literal is the way to go.  Don't worry that it is a break change, but make sure to mention it in CHANGES.md.
Good point, I'll move it to Ellipsoid.
This should use the seelalso tag instead of the text "See also:"
they do belong there. They are helper objects that are not used anywhere else. If other objects outside the LayoutHandler scope needs them, then refactoring will be needed and these objects will be promoted to model objects.
Should closing comments be on by default?

I think once comments are closed, there should be an easy link to mark the post unresolved again and add another comment, or create a new post stemming from the original post.
bubble-wrapをrequireしなかった場合、rakeでずっこけてしまいました。 https://gist.github.com/3992338
More of a question for @mstepanov .  I'm fine with it.
can you create a new variable instead of casting topActivity twice in line 42 and 43.
We can actually remove all of these individual "deprecated" tags... We don't need them if the overall object is deprecated.
That's true. That check was there for an old code.  Not needed.
We only use this path when isAsset==true. So it should be moved to line 93.
Can this be written more simply, such as new Directory(webFolder)? Why are you using a type instead of var, whereas you are using var up above? I'd probably stick with var since it's obvious from the code that you're creating a new Directory.
This was intended to be a list of resources for developers, not a list of developers.
I know. I am suspecting that the rebase broke some parts of the Source Formatting.
We should consider extending [AbstractHandlerExceptionResolver](https://github.com/SpringSource/spring-framework/blob/master/spring-webmvc/src/main/java/org/springframework/web/servlet/handler/AbstractHandlerExceptionResolver.java) which provides common functionalities.
Я имею ввиду, сделать функцию, которая будет каррировать @service в конструктор.
Not 100% sure. I put this in as a warning in case someone didn't use the logging system correctly so they'd notice it before their program died. I'm not sure how useful it'll be long-term and it causes confusing output to get written to the tests. Overall I lean towards "lets keep it" but not by much.
No need for a semicolon here.
This was loosely based on GC / runtime code, hence the use of the runtime function. I figured it should be the fastest way to zero memory, but I haven't tested it.
Would be better to read this path from a config file.
And by the way, remove trailing spaces in the function call.
ah ok, that was it :-) fair enough
I'll add it to use statements, thanks
I believe this logic can be rewritten using string.join with more compact code.
Does really Page Fragment need one? I though there could be one or zero. Zero in case you don't need to use root for controlling fragment code.
@brianchandotcom Since the programmatic behavior is not turned on in the properties (i.e. via blogs.entry.context.url.title.regexp=regexp) and/or the context attrib's urlTitle value does not match the regexp, use the default behavior of setting the URL title based on the enrtry title.
Redundant newline character?
This is useless. ``getManagerForClass`` will already return ``null`` if the class is not managed by a manager
Rechnet die Preis für eine gewisse Anzahl Worte

(Hier könnte noch ein Chack eingebaut werden, dass die Anzahl Worte $maxWort nicht überschreiten darf....)
нет не знаю. Потому что мне это не надо
ok, removed that stuff.
А нафига?
What is this sleep used for?
Are we _really_ debating the relative ugliness of a comment who's entire purpose in life is to be removed?  Really?
(and dereferencing, not deferencing)
QUERY: Encapsulation required?
~~the~~ an existing
I don't want to be a PITA, but how about...

````

	@Test
	public void compatibleConversionService() throws Exception {
		HttpRequestExecutingMessageHandler handler =
				new HttpRequestExecutingMessageHandler("http://www.springsource.org/spring-integration");
		ConfigurableListableBeanFactory bf = new DefaultListableBeanFactory();
		ProxyFactory pf = new ProxyFactory(new Class[] {ConversionService.class, ConverterRegistry.class});
		final AtomicInteger converterCount = new AtomicInteger();
		pf.addAdvice(new MethodInterceptor() {

			public Object invoke(MethodInvocation invocation) throws Throwable {
				if (invocation.getMethod().getName().equals("addConverter")) {
					converterCount.incrementAndGet();
				}
				return null;
			}
		});
		ConversionService mockConversionService = (ConversionService) pf.getProxy();
		bf.registerSingleton("integrationConversionService", mockConversionService);
		handler.setBeanFactory(bf);
		handler.afterPropertiesSet();
		assertEquals(2, converterCount.get());
		assertSame(mockConversionService, TestUtils.getPropertyValue(handler, "conversionService"));
	}
````
It's definitely a corner case but I agree with Gary - not specifically related to a non-standard server. The alternative is to allow temporary-file-prefix="" as a literal value, but that is inconsistent with every other SI component. The boolean flag seems like the better choice.
Does .each guarantee iteration over sorted values?

On 29. 09. 12, at 12:52, Mitar <notifications@github.com> wrote:

> In tests/test_project/test_app/static/test_app/js/datastream.js:
> 
> > +            plot.setData(new_data);
> > +            xaxes_options.min = o.from;
> > +            xaxes_options.max = o.to;
> > +            plot.setupGrid();
> > +            plot.draw();
> > +        }
> > +
> > +        plot.addMetric = function(metric) {
> > +            var i,
> > +                o = plot.getOptions(),
> > +                gr = granularity[o.granularity].key,
> > +                span = (o.to - o.from);
> > +
> > +            if (mode === 1) {
> > +                // if alternative mode, find the best granularity
> > +                for (i = 0; i < granularity.length; i++) {
> .each.
> 
> —
> Reply to this email directly or view it on GitHub.
> 
>
Yes, ostype and tested in the metadata.txt file are supposed to be CFEngine class names. I will clarify this in the guidelines document.

On Feb 29, 2012, at 9:38 PM, Nick Anderson wrote:

>> @@ -0,0 +1,3 @@
>> +author: Neil H Watson <neil@watson-wilson.ca>
>> +ostype: Linux, Solaris 10, AIX
> 
> On 02/29/2012 09:35 PM, Neil H Watson wrote:
> 
>> Are they supposed to be human or machine readable?
> 
> I think in the metadata file they are supposed to be machine readable
> probably the same classes that cfengine defines so that tools (not yet
> built) can search for things or warn when installing if your
> installing on a machine that classes dont match.
> 
> In the Readme.md I would guess either machine readable or human readable.
> 
> 
> -- 
> Nick Anderson <nick@cmdln.org>
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/cfengine/design-center/pull/14/files#r505508
IMO, the ArraySubscriber should have a negative priority if we start allowing passing arrays of elements+deps like this so that it is really the last one
the changes in this file appear to think they are overwriting / changing antony's commits ... but that is not what you want to do correct?  Perhaps you should rewrite this with a copy of antony's commits at the top.  The result should be yours in all green and nothing in red.  :-)
This should work. However, jQuery ajax also has a `beforeSend` callback function.

http://api.jquery.com/jQuery.ajax/
@hoffi 

If you click on the line number when viewing a file on github, it'll give you a link to that line. Makes it easier for others.
I keep going back and forth, should we enforce request pattern for everything?  Seems like overkill for one parameter.
If you do that's it's easy to see that the first `if` statement is alone and can easily be commented out or removed without breaking things.
If not provided with the constructor, it would be required to check for the existing `$session` on each call - are you sure, you want this?

`SessionInterface` will be changed :)
You should check `ARGV.build_devel?` as well, I think.
Call this function something like `wprp_get_incompatible_plugins` as that is what it is actually doing.
Is it worth mentioning here that orientation of the window and device are always the same on mobileweb?
What if the value is a string like the comment mentions?
gibt's keinen tag den du verwenden kannst?
Do you need to check that $module is what you think it is before you call ->delete ?
Лучше подключай зависимости, используя git submodule. Чтобы любой разработчик смог без открытия кода запустить твой код. Сейчас же будет следующее:

```
$ git clone your_repo dir
$ cd dir
$ git submodule init && git submodule update
```
Он скачает репозиторий заустит этот файл и получит 404 на `../dz-2-basics/event.js`
Затем он полезет искать проблему в код
Потом скачает твой dz-2-basics исправит путь подключения `../dz-2-basics/event.js`
И только тогда все заработает
Space after comma:
`$(snCB.dialogID).dialog('option', {`
Yes, to remote the first `/` in the pathname.
You can write this better using 

var BlobBuilder = BlobBuilder || WebkitBlobBuilder ;
Then you can remove the elseIf
I think this comment is no longer accurate since the refactor
This is a helper but not commented as such!
Onnistuu myös helpommin näin: `(not (teen? age))`
Yep, that should have been more explicit. For the future, exercises with function names starting with my- are supposet to be implemented without using the built-in function of the same name.
`(= 0 (mod n divisor))` retuns a boolean by it self, so the `if` is not needed. You also got the arguments the wrong way around. Remember to run the tests with `lein midje`.
should be:

   $(V2 override)

because the same docs are used for D1, and D1 doesn't have 'override'.