Hello Joseph,

let me quote [an answer] (http://stackoverflow.com/a/2739476/1944216) from StackOverflow:

>In terms of source control, you're downstream when you copy (clone, checkout, etc) from a repository. Information flowed "downstream" to you.
>
When you make changes, you usually want to send them back "upstream" so they make it into that repository so that everyone pulling from the same source is working with all the same changes. This is mostly a social issue of how everyone can coordinate their work rather than a technical requirement of source control. You want to get your changes into the main project so you're not tracking divergent lines of development.

> Sometimes you'll read about package or release managers (the people, not the tool) talking about submitting changes to "upstream". That usually means they had to adjust the original sources so they could create a package for their system. They don't want to keep making those changes, so if they send them "upstream" to the original source, they shouldn't have to deal with the same issue in the next release.

In this notation, you would be the package manager, and the main PsychoPy repsository would be "upstream".

If you have followed the [Fork A Repo] (https://help.github.com/articles/fork-a-repo/) guide from Github to get a local copy of the PsychoPy sources to do development on, in [Step 3] (https://help.github.com/articles/fork-a-repo/#step-3-configure-git-to-sync-your-fork-with-the-original-spoon-knife-repository), point 6, you have added the main PsychoPy github repository as a remote.

Merging (i.e. applying) upstream changes into your local repository is described in [Syncing a fork] (https://help.github.com/articles/syncing-a-fork/).

The operation of rebasing, which is, like Jon pointed out, a neater, yet more dangerous way of applying upstream changes (actually, it re-writes history!) is described in [How to Rebase a Pull Request] (https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request) and (imho even better), as part of the tutorial [Rewriting history] (https://www.atlassian.com/git/tutorials/rewriting-history/).

One thing I really love about rebasing is that you can, at a later point, "squash" previous commits into a single one (for example, "Add Feature X", "Fix Problem of Feature X", "Fix a Fix in the Problem of Feature X" could all be squashed into a single commit "Add Feature X"); it allows you to change commit messages; to re-order commits; to remove commits; to amend previous commits; and probably some more things.

Git is extremely powerful, flexible, and -- imho -- very complex and complicated for beginners. That said, I didn't mean to scare you off. Jon already said he'd try to solve the merge conflicts and do the merge on his own. If you want to get some hands-on experience with merge and rebase, though, I would suggest trying to start with some merge operations first.


the proper idiom for opening a file in python that will be read from and immediately closed


There is still a ownCloud in there.. you can get a full string via the SHARE_MENU_TITLE that is sent now to the overlays.


... and if the file doesn't exists, let's hand react a sane default.


Fait !

On Fri, Jan 23, 2015 at 11:50 AM, Ophir LOJKINE <notifications@github.com>
wrote:

> On pourrait simplement mettre return false ici...
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/les-champions/Jeudego/commit/c299a46cb05b5d1f46e32ff6b4279c2e5e7e52bc#commitcomment-9413831>
> .
>


با سلام من فارس زبان هستم


“除非你可以得益于 xxx 和 xxx，否则”


Oh didn't see this in the first place. If its prefilled, ignore my comment about simplicity below. But maybe we should change the term "mount name" in the localization file to "drive name".


lel lest make this page mother fucker


Thanks, great color scheme!! Can you recommend me some vim plugins?


Hi @timrwood,

okay i am sorry. I somehow missed that ``moment/momentjs.com`` is not versioned at all. Sorry for the complaints.


Just some sample data (written by the server)


as I said I think your version is better. We need a source to confirm that
and then we can make a commit that changes that. Btw. if you have problems
you could file a bug :(

2015-01-23 11:48 GMT+01:00 Fabian Neuschmidt <notifications@github.com>:

> uh yeah I forgot to take that out afterwards. /bin/python3 is not working
> for me so i needed to change this to pass the coverage param
>
> --
> Reply to this email directly or view it on GitHub
> <https://github.com/coala-analyzer/coala/commit/a8a468f800f99e98fd1e28c2f17e4926c59d9d74#commitcomment-9413804>
> .
>


This file was in the wrong place for the server to save to. I think you had it in the scripts directory to make dev on the front end easier


27:1: I101 Imported names are in the wrong order. Should be CFG_BIBFORMAT_FORMAT_TEMPLATE_EXTENSION, CFG_BIBFORMAT_TEMPLATES_PATH
28:6: E126 continuation line over-indented for hanging indent
30:1: I100 Imports statements are in the wrong order. from invenio.modules.formatter should be before from invenio.modules.formatter.config
57:52: E231 missing whitespace after ':'
58:49: E231 missing whitespace after ':'
59:48: E231 missing whitespace after ':'
65:43: E261 at least two spaces before inline comment
65:44: E262 inline comment should start with '# '
70:52: E231 missing whitespace after ':'
71:49: E231 missing whitespace after ':'
72:48: E231 missing whitespace after ':'
76:5: E303 too many blank lines (3)
80:1: E302 expected 2 blank lines, found 1
80: D401 First line should be imperative: 'Return', not 'Returns'
80: D205 Blank line missing between one-line summary and description
110:16: E127 continuation line over-indented for visual indent
114:57: E231 missing whitespace after ':'
115:61: E231 missing whitespace after ':'
116:57: E231 missing whitespace after ':'
122:57: E231 missing whitespace after ':'
123:61: E231 missing whitespace after ':'
124:57: E231 missing whitespace after ':'
132:24: E713 test for membership should be 'not in'
144: D401 First line should be imperative: 'Return', not 'Returns'
144: D400 First line should end with '.', not 't'
162:32: E225 missing whitespace around operator
204:5: F841 local variable 'tags' is assigned to but never used
205:53: E261 at least two spaces before inline comment
205:54: E262 inline comment should start with '# '
208:79: E261 at least two spaces before inline comment
208:80: E262 inline comment should start with '# '
210:17: E261 at least two spaces before inline comment
210:18: E262 inline comment should start with '# '
211:52: E261 at least two spaces before inline comment
211:53: E262 inline comment should start with '# '
215:58: E231 missing whitespace after ':'
216:62: E231 missing whitespace after ':'
217:13: B901 blind except: statement
227:1: E302 expected 2 blank lines, found 1
254:41: E231 missing whitespace after ':'
255:45: E231 missing whitespace after ':'
256:45: E231 missing whitespace after ':'
259:5: E303 too many blank lines (2)


43:1: E302 expected 2 blank lines, found 1
43: D401 First line should be imperative: 'Return', not 'Returns'
59:1: E302 expected 2 blank lines, found 1
59: D401 First line should be imperative: 'Return', not 'Returns'
59: D400 First line should end with '.', not 'e'
67:16: E225 missing whitespace around operator
72:1: E302 expected 2 blank lines, found 1
72: D401 First line should be imperative: 'Return', not 'Returns'
72: D400 First line should end with '.', not ','
72: D205 Blank line missing between one-line summary and description
81:16: E225 missing whitespace around operator
86:1: E302 expected 2 blank lines, found 1
86: D401 First line should be imperative: 'Return', not 'Returns'
98:1: E302 expected 2 blank lines, found 1
98: D401 First line should be imperative: 'Return', not 'Returns'
98: D400 First line should end with '.', not 'e'
106:16: E225 missing whitespace around operator
111:1: E302 expected 2 blank lines, found 1
111: D401 First line should be imperative: 'Return', not 'Returns'
123:1: E302 expected 2 blank lines, found 1
143: D401 First line should be imperative: 'Return', not 'Returns'
153:17: E225 missing whitespace around operator
156:16: E225 missing whitespace around operator
161:1: E302 expected 2 blank lines, found 1
181:1: E302 expected 2 blank lines, found 1
181: D401 First line should be imperative: 'Remove', not 'Removes'
181: D400 First line should end with '.', not "'"
200:1: E302 expected 2 blank lines, found 1
200: D202 No blank lines allowed *after* function docstring, found 1
216:1: E302 expected 2 blank lines, found 1
216: D401 First line should be imperative: 'Set', not 'Sets'
216: D400 First line should end with '.', not 'e'
234:1: E302 expected 2 blank lines, found 1
234: D401 First line should be imperative: 'Return', not 'Returns'
234: D400 First line should end with '.', not 'e'
250:1: E302 expected 2 blank lines, found 1
250: D401 First line should be imperative: 'Set', not 'Sets'
250: D400 First line should end with '.', not 'e'
269: D401 First line should be imperative: 'Set', not 'Sets'
269: D400 First line should end with '.', not 'e'
289: D202 No blank lines allowed *after* function docstring, found 1
315:54: E261 at least two spaces before inline comment
317:15: E225 missing whitespace around operator
317:41: E225 missing whitespace around operator
327:1: E302 expected 2 blank lines, found 1
342:1: E302 expected 2 blank lines, found 1
356:29: E261 at least two spaces before inline comment
358:28: E261 at least two spaces before inline comment


1: D400 First line should end with '.', not 'n'
23: D203 Expected 1 blank line *before* class docstring, found 0
23: D400 First line should end with '.', not 'l'
26: D401 First line should be imperative: 'Print', not 'Prints'
26: D202 No blank lines allowed *after* method docstring, found 1
26: D400 First line should end with '.', not 's'


26:1: I100 Imports statements are in the wrong order. from invenio.ext.sqlalchemy should be before from sqlalchemy.exc
31:1: I101 Imported names are in the wrong order. Should be Bibfmt, Format, Formatname
34: D401 First line should be imperative: 'Return', not 'Returns'
51: D401 First line should be imperative: 'Return', not 'Returns'
69: D401 First line should be imperative: 'Return', not 'Returns'
69: D400 First line should end with '.', not 'e'
83: D401 First line should be imperative: 'Return', not 'Returns'
83: D400 First line should end with '.', not ','
83: D205 Blank line missing between one-line summary and description
100: D401 First line should be imperative: 'Return', not 'Returns'
110: D401 First line should be imperative: 'Return', not 'Returns'
110: D400 First line should end with '.', not 'e'
124: D401 First line should be imperative: 'Return', not 'Returns'
153: D401 First line should be imperative: 'Return', not 'Returns'
173: D401 First line should be imperative: 'Return', not 'Returns'
187: D401 First line should be imperative: 'Set', not 'Sets'
187: D400 First line should end with '.', not 'e'
210: D401 First line should be imperative: 'Return', not 'Returns'
251: D401 First line should be imperative: 'Remove', not 'Removes'
251: D400 First line should end with '.', not "'"
270: D401 First line should be imperative: 'Return', not 'Returns'
270: D400 First line should end with '.', not 'e'
282: D401 First line should be imperative: 'Set', not 'Sets'
282: D400 First line should end with '.', not 'e'
295: D401 First line should be imperative: 'Return', not 'Returns'
295: D400 First line should end with '.', not 'e'
312: D401 First line should be imperative: 'Set', not 'Sets'
312: D400 First line should end with '.', not 'e'
326:1: E303 too many blank lines (3)
326: D401 First line should be imperative: 'Return', not 'Returns'
326: D400 First line should end with '.', not 'e'
338: D401 First line should be imperative: 'Set', not 'Sets'
338: D400 First line should end with '.', not 'e'
352:1: E303 too many blank lines (3)
352: D401 First line should be imperative: 'Set', not 'Sets'
382: D400 First line should end with '.', not 't'
393: D401 First line should be imperative: 'Return', not 'Returns'
393: D400 First line should end with '.', not "'"
423: D401 First line should be imperative: 'Return', not 'Returns'
423: D400 First line should end with '.', not 'd'
423: D205 Blank line missing between one-line summary and description


41:1: I100 Imports statements are in the wrong order. import os should be before import sys
42:1: I100 Imports statements are in the wrong order. import inspect should be before import os
44:1: I100 Imports statements are in the wrong order. import cgi should be before import traceback
47:1: I101 Imported names are in the wrong order. Should be current_app, has_app_context
48:1: I100 Imports statements are in the wrong order. from operator should be before from flask
48:1: I201 Missing newline before sections or imports.
49:1: I201 Missing newline before sections or imports.
50:1: I201 Missing newline before sections or imports.
52:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from werkzeug.utils
53:1: I101 Imported names are in the wrong order. Should be CFG_BIBFORMAT_CACHED_FORMATS, CFG_BIBFORMAT_DISABLE_I18N_FOR_CACHED_FORMATS, CFG_BIBFORMAT_HIDDEN_TAGS, CFG_SITE_LANG
53:1: F401 'CFG_BIBFORMAT_CACHED_FORMATS' imported but unused
53:1: F401 'CFG_BIBFORMAT_HIDDEN_TAGS' imported but unused
54:6: E126 continuation line over-indented for hanging indent
59:6: E126 continuation line over-indented for hanging indent
60:1: I101 Imported names are in the wrong order. Should be create_record, record_empty, record_get_field_instances, record_get_field_value, record_get_field_values, record_xml_output
61:6: E126 continuation line over-indented for hanging indent
70:1: I101 Imported names are in the wrong order. Should be gettext_set_language, language_list_long, wash_language
70:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from .models
70:1: I201 Missing newline before sections or imports.
71:6: E126 continuation line over-indented for hanging indent
75:1: I101 Imported names are in the wrong order. Should be CFG_BIBFORMAT_FORMAT_JINJA_TEMPLATE_EXTENSION, CFG_BIBFORMAT_FORMAT_OUTPUT_EXTENSION, CFG_BIBFORMAT_FORMAT_TEMPLATE_EXTENSION, CFG_BIBFORMAT_OUTPUTS_PATH, CFG_BIBFORMAT_TEMPLATES_DIR, InvenioBibFormatError
75:1: I201 Missing newline before sections or imports.
75:1: F401 'CFG_BIBFORMAT_TEMPLATES_DIR' imported but unused
75:1: F401 'CFG_BIBFORMAT_OUTPUTS_PATH' imported but unused
76:6: E126 continuation line over-indented for hanging indent
82:1: I101 Imported names are in the wrong order. Should be parse_tag, record_get_xml
82:1: I100 Imports statements are in the wrong order. from invenio.modules.formatter.utils should be before from .config
83:6: E126 continuation line over-indented for hanging indent
85:1: I101 Imported names are in the wrong order. Should be CFG_HTML_BUFFER_ALLOWED_ATTRIBUTE_WHITELIST, CFG_HTML_BUFFER_ALLOWED_TAG_WHITELIST, HTMLWasher
86:6: E126 continuation line over-indented for hanging indent
89:1: I100 Imports statements are in the wrong order. from invenio.modules.knowledge.api should be before from invenio.utils.html
90:1: I100 Imports statements are in the wrong order. from invenio.ext.template should be before from invenio.modules.knowledge.api
91:1: I100 Imports statements are in the wrong order. from HTMLParser should be before from invenio.ext.template
91:1: I201 Missing newline before sections or imports.
92:1: I201 Missing newline before sections or imports.
100:27: E261 at least two spaces before inline comment
101:28: E111 indentation is not a multiple of four
101:28: E113 unexpected indentation
102:28: E111 indentation is not a multiple of four
102:28: E113 unexpected indentation
103:28: E111 indentation is not a multiple of four
103:28: E113 unexpected indentation
106:28: E111 indentation is not a multiple of four
106:28: E113 unexpected indentation
120:33: E225 missing whitespace around operator
211: D203 Expected 1 blank line *before* class docstring, found 0
215: D401 First line should be imperative: 'Return', not 'Returns'
215: D400 First line should end with '.', not 's'
227: D401 First line should be imperative: 'Return', not 'Returns'
252: D102 Docstring missing
291: D103 Docstring missing
297: D401 First line should be imperative: 'Format', not 'Formats'
297: D400 First line should end with '.', not 'f'
297: D205 Blank line missing between one-line summary and description
344:45: E127 continuation line over-indented for visual indent
487:27: E225 missing whitespace around operator
490:5: E303 too many blank lines (2)
508:82: E225 missing whitespace around operator
550: D103 Docstring missing
566: D401 First line should be imperative: 'Return', not 'Returns'
566: D202 No blank lines allowed *after* function docstring, found 1
566: D400 First line should end with '.', not 'g'
566: D205 Blank line missing between one-line summary and description
587:64: E261 at least two spaces before inline comment
587:65: E262 inline comment should start with '# '
594:38: E261 at least two spaces before inline comment
594:39: E262 inline comment should start with '# '
595:48: E261 at least two spaces before inline comment
595:49: E262 inline comment should start with '# '
598:24: E127 continuation line over-indented for visual indent
607: D103 Docstring missing
610: D400 First line should end with '.', not 's'
610: D200 One-line docstring should not occupy 3 lines
623: D290 White spaces around docstring should be trimmed.
623: D400 First line should end with '.', not 'a'
623: D205 Blank line missing between one-line summary and description
655:57: E126 continuation line over-indented for hanging indent
662:5: E303 too many blank lines (2)
721: D401 First line should be imperative: 'Evalute', not 'Evalutes'
741: D401 First line should be imperative: 'Analyse', not 'Analyses'
741: D202 No blank lines allowed *after* function docstring, found 1
810: D401 First line should be imperative: 'Return', not 'Returns'
810: D400 First line should end with '.', not 't'
810: D205 Blank line missing between one-line summary and description
909:13: B901 blind except: statement
940:78: E225 missing whitespace around operator
941:54: E225 missing whitespace around operator
973:47: E261 at least two spaces before inline comment
988:27: E225 missing whitespace around operator
1048: D401 First line should be imperative: 'Filter', not 'Filters'
1058: D401 First line should be imperative: 'Searche', not 'Searches'
1058: D400 First line should end with '.', not 's'
1058: D205 Blank line missing between one-line summary and description
1084:9: E303 too many blank lines (2)
1098:5: E303 too many blank lines (2)
1101:1: E302 expected 2 blank lines, found 1
1101: D401 First line should be imperative: 'Return', not 'Returns'
1115:5: F841 local variable '_' is assigned to but never used
1118:12: E127 continuation line over-indented for visual indent
1127:16: E126 continuation line over-indented for hanging indent
1149:5: B901 blind except: statement
1161: D401 First line should be imperative: 'Return', not 'Returns'
1161: D400 First line should end with '.', not 's'
1181:16: E126 continuation line over-indented for hanging indent
1188:1: E302 expected 2 blank lines, found 1
1188: D401 First line should be imperative: 'Return', not 'Returns'
1188: D400 First line should end with '.', not 'e'
1220:13: E303 too many blank lines (2)
1234: D401 First line should be imperative: 'Return', not 'Returns'
1268:16: E127 continuation line over-indented for visual indent
1278:31: E126 continuation line over-indented for hanging indent
1305:9: B901 blind except: statement
1317:17: E126 continuation line over-indented for hanging indent
1324:1: E302 expected 2 blank lines, found 1
1324: D401 First line should be imperative: 'Return', not 'Returns'
1324: D400 First line should end with '.', not 'e'
1368:1: E302 expected 2 blank lines, found 1
1368: D401 First line should be imperative: 'Return', not 'Returns'
1368: D202 No blank lines allowed *after* function docstring, found 1
1495:1: E302 expected 2 blank lines, found 1
1495: D401 First line should be imperative: 'Return', not 'Returns'
1495: D202 No blank lines allowed *after* function docstring, found 1
1522:17: E225 missing whitespace around operator
1590:1: E302 expected 2 blank lines, found 1
1590: D401 First line should be imperative: 'Return', not 'Returns'
1590: D400 First line should end with '.', not 't'
1634:28: E261 at least two spaces before inline comment
1634:29: E262 inline comment should start with '# '
1682:5: B901 blind except: statement
1788:1: E302 expected 2 blank lines, found 1
1788: D401 First line should be imperative: 'Return', not 'Returns'
1788: D202 No blank lines allowed *after* function docstring, found 1
1788: D400 First line should end with '.', not '}'
1805:56: E225 missing whitespace around operator
1829:1: E302 expected 2 blank lines, found 1
1829: D401 First line should be imperative: 'Return', not 'Returns'
1829: D400 First line should end with '.', not 'e'
1858:26: F821 undefined name 'exc'
1860:22: F821 undefined name 'exc'
1863:1: E302 expected 2 blank lines, found 1
1863: D401 First line should be imperative: 'Return', not 'Returns'
1896:1: E302 expected 2 blank lines, found 1
1896: D401 First line should be imperative: 'Return', not 'Returns'
1940:1: E302 expected 2 blank lines, found 1
1951:1: E302 expected 2 blank lines, found 1
1951: D203 Expected 1 blank line *before* class docstring, found 0
1951: D204 Expected 1 blank line *after* class docstring, found 0
1951: D400 First line should end with '.', not 'n'
1951: D205 Blank line missing between one-line summary and description
1982:15: E261 at least two spaces before inline comment
1984: D401 First line should be imperative: 'Create', not 'Creates'
2016:31: E261 at least two spaces before inline comment
2040: D401 First line should be imperative: 'Return', not 'Returns'
2040: D400 First line should end with '.', not 'e'
2055: D401 First line should be imperative: 'Return', not 'Returns'
2055: D400 First line should end with '.', not 'd'
2078: D401 First line should be imperative: 'Return', not 'Returns'
2078: D400 First line should end with '.', not 'e'
2078: D205 Blank line missing between one-line summary and description
2116: D401 First line should be imperative: 'Return', not 'Returns'
2116: D202 No blank lines allowed *after* method docstring, found 1
2225:36: E127 continuation line over-indented for visual indent
2228: D401 First line should be imperative: 'Return', not 'Returns'
2285:33: E127 continuation line over-indented for visual indent
2296:60: E251 unexpected spaces around keyword / parameter equals
2298:54: E251 unexpected spaces around keyword / parameter equals
2308:37: E127 continuation line over-indented for visual indent
2319:64: E251 unexpected spaces around keyword / parameter equals
2321:58: E251 unexpected spaces around keyword / parameter equals


So FB recent updated (in Nov) the server files so that they would all write to disk for you. That being said, it seems that these were just js guys because the python is rather poor.


Why?


twig is needed


You know whats a good idea? Checking to see if a file exists before you try to read from it... yeah, let's do that.


@Lenchik, готово.


And now, the proper python idiom for brief opening of files. Doing this in the with clause guards against one forgetting to close the file after it's done being used (this is done automatically after you leave the with clause).


... and if the file isn't there, let's give react something sane to work with (better than an error)


Apparantly not. It fails without this.


@fernandog
Change this to
logNameFilters = {'<NONE>': u'<No Filter>',

That way, the box will display <No Filter>, which is more descriptive of the fact there is no filter applied than 'None'.
Secondly, this will sort the list starting with <NONE>, so that it is always at the top (which is where you'd expect to find the 'no filter' option).


highlightion strikes again.


You were using the `/list.json` in your js as the target url for the get/post methods but the server was looking for paths to `/comments.json` -- this is why nothing was saving (and I bet you were seeing a ton of errors spewing out of the server too).


yea name would be redundant in most cases imo. I have no problems with using the popover


checked flag; values -1,0,1; Not all the checked child nodes, 0:unchecked 1:checked


iBeacons 这种专有名词直接这么放着就好了吧，如果说室内定位可能都不知道是什么东西。


Note: This custom Copy Ctor is necessary, since CLR provides  no synthesized  copy constructors nor assignment operators.This is quite different from C++.


checked childnode


Works smooth :) +1


I think the reload here is required because you've changed the body within the rails application - your `pb` copy has no way of being updated with those changes unless you reload it.


Troop#CanEnter


process parent nodes


呃，这个地方，还真是不好用中文说。。。


checked node


uncheck node


Why do you consider this addition? I see same check on Underscore.js but can't see the benefit.


lol


There is OverloadedStrings enabled, just `… /= "\n"` should work.


Yes.


Could we rewrite the commit message here a bit? I think a more accurate description of the problem is 'Fix submission of form containing both existing and new translations'. As it turns out, I think the '>=3' indicator is not relevant. I believe you can add >=3 translations with the old code as long as they were all added at the same time.


this is the biggest problem -- even if you had been using `/comments.json` STILL nothing would have been saved unless you had been using fields of the name `author` or `text` in your js code. The react POST sends the json data according to the names you used in your react class: `number` & `label` specifically (line 99 in your example.js file).

So when the server sees the POST it was hard-coded to only save the `author` and `text` fields of the post request... which is rather dumb. I mean, it's less characters to do the fully generalized solution...


TESTS PASSED
 Mr.Roboto url : http://jenkins.plone.org/roboto/get_info?push=0ced0b341368463c98f258dd10e1c90d
 plone-5.0-python-2.7 [SUCCESS]


Matt;
We haven't validated with bowtie2 so I'm not sure. It would be an interesting experiment if you prefer using bowtie2 for mapping. Practically bwa-mem has been reliable and performant for us so we haven't done a lot of work validating other aligners.


Usually I will create a non-general object to start with, then break it apart later on as the problem set becomes more clear.  But I agree with you that we already know we will want to be able to do overrides based on texture at a minimum, so it's a good idea to make that now.

With that in mind, I checked in a first pass at an Override object where we can encapsulate that logic.  Not functional yet, just something to poke at.


Here's the fully general version. From now on, any field in the from that you send to the server as a POST will be saved to disk. This should help you in extending your example app


I believe it was an glitch in Coffeescript compilation. Don’t worry, the array annotation will be there with next release.

—
Sent from Mailbox

On Thu, Jan 22, 2015 at 6:17 PM, Jay Thomas <notifications@github.com>
wrote:

> What's the reason for removing the inline array annotation?
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/fragaria/angular-daterangepicker/commit/30ecf9f6a0664cb425f2613b073b25df89df259d#commitcomment-9401164


Again, the proper idiom for this sort of thing...


IMO, the fewer exceptions, the more reliable.


Är detta verkligen ända fixen för problemet. En delay i mainloopen känns inte bra


Integro Angular


Esqueça esse commit besta, o tr aceita o \t nativamente... Veja 77880f1


Fix brace position.


checked Example


Any chance we can a bugfix release in NPM to include these changes? Last version published was in Sept 2014


Preferi adicionar um único data-attribute com um array, em vez de um para cada item, por ser mais conciso.
Mas ainda me incomodo com a sintaxe de inicialização de arrays do Ruby. Será que não existe forma mais elegante? Preciso de todas essas linhas?


Why do u use 3 different names:
- ```$this->eventData```
- ```$actionEventData```
- ```setUserEventData(```


This is just unforgivable! It's completely wrong and will confuse those not used to python :bomb:

What's worse is that it was definitely throwing errors at you... only the `/comments.json` route was covered. Any other route came here and :boom:

:shit:


PHPUnit shoud not have to use RecursionContext directly. Can the method that uses it be moved to Exporter?


At least this was correct... :cry:


Nice work! Thanks! I haven't had much time to continue with my PR.

Are you sure this works? Since `toFields` does not receive `props` (the return value of `_categorizeProperties`) and simply works with the original `data`. So you get more `SET column=?` than values being given.


```c++
Msg::Msg()
{
}
```
So I like. And if objectively, the two different format of the same.
If there was only one line...
```c++
Msg::Msg() {}
```


Care to elaborate?


the "defaultValue" conflicts somehow with the dclickValue1 dclickValue2 in slider.h. Th dclick values should probably be moved to the baseclass AbstractSlider and used instead of defaultValue


yay!!!!


Nä verkligen inte. Problemet är bara att vi måste hitta orsaken då, om det
är bouncing issues eller nåt flödet, att den hinner ikapp sig själv
nånstans. Eller att pressed kanske ändras på fler ställen. Känner att det
kan bli svårt att hinna fixa det på ett bra sätt. Alternativet är att ha
kvar buggen och ta bort delayn vilket kanske ses som ett mindre fel?
Dunno! Men jag har inte märkt några problem av att lägga till delayn än
sålänge iaf. Vi får kolla på det på lördag.

On Fri, Jan 23, 2015, 12:26 PM danned <notifications@github.com> wrote:

> Är detta verkligen ända fixen för problemet. En delay i mainloopen känns
> inte bra
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/danned/projekt/commit/78ed644547716e78fc215ff293d80c5876a0c7ab#commitcomment-9414257>
> .
>


Yup, I see that.  But isn't it more clear just to say:
  `return (GetAsyncKeyState(vkey) != 0);`
?


"tool for chang"


Boa pergunta, não lembro de ter visto nada do tipo


Remind, please, default constructors are required for QVector?


du är ju efterbliven


js should be a keyed list, like this:

js:
  fallback_formatter.admin.js: {}


Should you re-add the map method for Score.class


TeamCity OsmSharp :: GitHub - OsmSharp - PullRequests [Build 105](http://build.osmsharp.com:8080/viewLog.html?buildId=4173&buildTypeId=OsmSharp_GitHubOsmSharpPullrequests) is now running


It looks as though `baseurl` was overwritten by another PR. I'll have look at putting it back in.


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 49](http://192.168.44.2:8111/viewLog.html?buildId=120&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


Since the plural is now handled properly by ngettext, translators won't care. Removing the comment will also safeguard against future code changes where the number might be used for e.g. 2 as well - gettext won't pick up on a changed comment.


I think this "body" argument is necessary.


tearDown is not user-specific, so to avoid repeating things over and over again it would make sense only after dealing with all the users, i.e. in the cli call. But that's also basically the end of the script. So i think it is not necessary.


这是啥？


Not a bug - it is a good practice to store versions of your libs in <properties> block.


Well, at least my tests for 'database default values' PR pass after this fix. :) Should have run full test suite, though.. Will do that soon!


Selection needs to be limited to the ACGTs  (i.e. numbers should not be copied...)

> On 23 Jan 2015, at 10:48, Anurag Priyam <notifications@github.com> wrote:
>
> I took a look before commenting.
>
> The commit only says "modern look". This is anything but modern look:
>
>
>
> And from your email I was expecting to see the numbers on left and right to be dimmed out.
>
> —
> Reply to this email directly or view it on GitHub.
>


Hola


@gabizou "unregsiters" => "unregisters"


Ah my bad, didn't even think about the overhead of that call.


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 49](http://192.168.44.2:8111/viewLog.html?buildId=120&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **FAILURE**
Summary: Tests passed: 12; exit code 1 (new) Build time: 00:06:31


you can actually use `classList.toggle`


Mendelian fruit: You need to specify the allele frequencies, right?


Not a bug - it is a good practice to store libraries versions in <properties> block.


I think we can just use a `else` clause to catch everything else.


TeamCity OsmSharp :: GitHub - OsmSharp - PullRequests [Build 4.3.0.105](http://build.osmsharp.com:8080/viewLog.html?buildId=4173&buildTypeId=OsmSharp_GitHubOsmSharpPullrequests) outcome was **FAILURE**
Summary: Tests failed: 3, passed: 461 Build time: 0:0:0
### Failed tests
```
OsmSharp.Test.Unittests.dll: OsmSharp.Test.Unittests.Routing.Instructions.InstructionRegressionTestsCH.InstructionRegressionCHTest2: Test(s) failed.   Expected: 2
  But was:  4
   at NUnit.Framework.Assert.That(Object actual, IResolveConstraint expression, String message, Object[] args)

OsmSharp.Test.Unittests.dll: OsmSharp.Test.Unittests.Routing.Instructions.InstructionRegressionTestsCH.InstructionRegressionCHTest3: Test(s) failed.   Expected: 2
  But was:  4
   at NUnit.Framework.Assert.That(Object actual, IResolveConstraint expression, String message, Object[] args)

OsmSharp.Test.Unittests.dll: OsmSharp.Test.Unittests.Routing.Instructions.InstructionRegressionTestsCH.InstructionRegressionCHTest4: Test(s) failed.   Expected: 2
  But was:  4
   at NUnit.Framework.Assert.That(Object actual, IResolveConstraint expression, String message, Object[] args)

```


Harshad numbers: I don't like this one, we should only do biological questions IMO.


Arash use bootstrap ! <br/> is not ok! ;) look my code! pull the last code and change ur code!


Not working for me.
Windows 7 64bit
Ruby 1.9.3p545 (2014-02-24) [i386-mingw32]
Gem 2.4.5
Compass 0.12.6 (Alnilam)


and this is the reason why do you need work with a dev branch first ;)


How about FacilityComponent and FacilityManager


yeah, sorry about the commit message


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 50](http://192.168.44.2:8111/viewLog.html?buildId=122&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 50](http://192.168.44.2:8111/viewLog.html?buildId=122&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:01


Might be helpful to also point people at the new form - presumably the case where this would affect them would be where they created their own custom admin templates from ours and now need to update them. Given that I changed this method name, we should also leave a wrapper with the old method name. We also should clean up (not in this hotfix but before we make the next release) the other places where this pattern has been replicated - in the forms for [PublicBodyHeadings](https://github.com/mysociety/alaveteli/blob/rails-3-develop/app/views/admin_public_body_headings/_form.html.erb#L12) and [PublicBodyCategories](https://github.com/mysociety/alaveteli/blob/rails-3-develop/app/views/admin_public_body_categories/_form.html.erb#L12). I've ticketed that [here](https://github.com/mysociety/alaveteli/issues/2113).


I advise against this. It won't install Mongo automatically, but just fail if it can't be found.
There's no value in that.


don't you need to unregister here as well?


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 51](http://192.168.44.2:8111/viewLog.html?buildId=124&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 51](http://192.168.44.2:8111/viewLog.html?buildId=124&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **SUCCESS**
Summary: Running Build time: 00:00:01


There was two javascript refresh. I removed one.


TeamCity Ylab :: zmactep/ylab [Build 183](http://192.168.30.225:8111/viewLog.html?buildId=634&buildTypeId=Ylab_ZmactepYlab&guest=1) is now running


TeamCity Ybackend :: AnnaPonomareva/ybackend [Build 142](http://192.168.30.225:8111/viewLog.html?buildId=635&buildTypeId=Ybackend_AnnaPonomarevaYbackend&guest=1) is now running


TeamCity Ybackend :: AnnaPonomareva/ybackend [Build 142](http://192.168.30.225:8111/viewLog.html?buildId=635&buildTypeId=Ybackend_AnnaPonomarevaYbackend&guest=1) outcome was **FAILURE**
Summary: Exit code 127 Build time: 00:00:01


is it possible to change this commit instead of close this one? I new to git.


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 52](http://192.168.44.2:8111/viewLog.html?buildId=126&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 52](http://192.168.44.2:8111/viewLog.html?buildId=126&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **SUCCESS**
Summary: Running Build time: 00:00:01


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 53](http://192.168.44.2:8111/viewLog.html?buildId=128&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 53](http://192.168.44.2:8111/viewLog.html?buildId=128&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **SUCCESS**
Summary: Running Build time: 00:00:01


@teh-jazzman vielleicht interessant, damit nutze ich mopidy und kann mit verschiedenen mdp und webclients spotify hören. Bis jetzt habe ich aber nur die x86_64 version testen können.


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 54](http://192.168.44.2:8111/viewLog.html?buildId=130&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 54](http://192.168.44.2:8111/viewLog.html?buildId=130&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **SUCCESS**
Summary: Running Build time: 00:00:01


Edit: we want to avoid executing the same block of code in different threads.


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 55](http://192.168.44.2:8111/viewLog.html?buildId=132&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 55](http://192.168.44.2:8111/viewLog.html?buildId=132&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **SUCCESS**
Summary: Running Build time: 00:00:01


setFilterNativeExpression is a bit late before feature freeze.
And as it looks now as if there's support for the expression compiler, we should rather aim for that for next after 2.8.

For me the question is if it's better to stick to setSubsetString or instead switch to setFilterExpression in 2.8?


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 56](http://192.168.44.2:8111/viewLog.html?buildId=134&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 56](http://192.168.44.2:8111/viewLog.html?buildId=134&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **SUCCESS**
Summary: Running Build time: 00:00:01


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 57](http://192.168.44.2:8111/viewLog.html?buildId=136&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 57](http://192.168.44.2:8111/viewLog.html?buildId=136&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **SUCCESS**
Summary: Running Build time: 00:00:01


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 58](http://192.168.44.2:8111/viewLog.html?buildId=138&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 58](http://192.168.44.2:8111/viewLog.html?buildId=138&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **FAILURE**
Summary: Exit code 2 (new) Build time: 00:00:01


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 59](http://192.168.44.2:8111/viewLog.html?buildId=140&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 59](http://192.168.44.2:8111/viewLog.html?buildId=140&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **FAILURE**
Summary: Exit code 2 Build time: 00:00:01


Yeah, probably. It's just a custom export format that we're using for printing data sets from providers.


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 60](http://192.168.44.2:8111/viewLog.html?buildId=142&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 60](http://192.168.44.2:8111/viewLog.html?buildId=142&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **SUCCESS**
Summary: Running Build time: 00:00:01


yeah i know...i cleaned it :(


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 61](http://192.168.44.2:8111/viewLog.html?buildId=144&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 61](http://192.168.44.2:8111/viewLog.html?buildId=144&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **UNKNOWN**
Summary: Canceled (Exit code 137 (new)) Build time: 00:00:18


Maybe I'm wrong, but the delete dialog should be clean+removed when it is closed. So in any case this.delete_confirmation variable will be null when dialog is hidden.


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 62](http://192.168.44.2:8111/viewLog.html?buildId=146&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 62](http://192.168.44.2:8111/viewLog.html?buildId=146&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **SUCCESS**
Summary: Running Build time: 00:00:01


remover novos métodos da unidade e "implementar" onde a chamada é feita (em java8 código é minimo)


In that case it doesn't matter to put ' if(nsamples>0) ' because if it happens that wtemp(1:0)=something then it just doesn't do nothing to the array.


As we're losing the helper spec here, it might be worth adding one more spec to the integration file demonstrating that the default locale fields are applied directly to the public body - with something like:

    @admin.fill_in 'public_body_name__en"', :with => 'New Quango EN'


Seriously: How are these names telling you, what those classes do? Names like "DataProcessor" or "CalculationManager" don't serve this purpose.

In this case, the whole idea is about deferred closing of Closables, so the name should somehow reflect that.


Looks like my patch ended up with LF and not CRLF for the changes. It wasn't that way when I made it, Git must have screw it up during a rebase (I've seen that happen before with this very file but caught it in time). The proper fix is to drop all CRLF from the file in the repo and be done with it. There are config options for telling Git whether you want CRLF or LF when you check something out (and it will then be handled accordingly when you check things in), but this all seem to rely on thing having LF only within the repo so I haven't been able to use them.

BTW CRLF is sooo 1980's.


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 63](http://192.168.44.2:8111/viewLog.html?buildId=148&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 63](http://192.168.44.2:8111/viewLog.html?buildId=148&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **SUCCESS**
Summary: Running Build time: 00:00:01


Might want to move the check for an image existing before `if @lead_campaign.full_bleed` since it relies on an image being present?


TeamCity Ylab :: zmactep/ylab [Build 183](http://192.168.30.225:8111/viewLog.html?buildId=634&buildTypeId=Ylab_ZmactepYlab&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 130 Build time: 00:11:19


I would probably go with setFilterExpression(). The direct joins without cache are very slow for anything else than small layers anyway. The change to setFilterExression() will at least make it less prone to data corruption / crashes.


This is a test of hello there


Incorrrectly formatted headers will cause this to raise an error. We should really fail gracefully.


@wilson0x4d I'm not sure what you mean.


We are loggin only rootResource.getId() in other messages, but here the whole rootResource is logged.
Wouldn't it be better to use same approach in all log messages?


Actually, XOF currency is duplicated. Fixed with 6d37ff1


@wilson0x4d You'd have to take that up with V8 because the patch landed upstream earlier today. :-)  I wouldn't worry about ARMv8 support for now, though.  It's easy enough to fix when the time comes.


When database columns are boolean types, there's an idiomatic way of checking their existence. Boolean columns/methods can be called with `?` so `if @lead_campaign.full_bleed?`


Closed Visual Studio Online Task [vso#4345](https://azurecom.visualstudio.com/DefaultCollection/ACOM/_workitems#_a=edit&id=4345): 'This is a test usersnap task submission'

VSO State: Done


headで 再帰する必要がある


Yo además pondría el Simulator::Run() y Simulator::Stop xD
pero tiene buena pinta el código :)


They're not. It was a joke. I thought that was pretty clear.

On Fri, Jan 23, 2015 at 1:00 PM, Sebastian Stenzel <notifications@github.com
> wrote:

> Seriously: How are these names telling you, what those classes do? Names
> like "DataProcessor" or "CalculationManager" don't serve this purpose.
>
> In this case, the whole idea is about deferred closing of Closables, so
> the name should somehow reflect that.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Tillerino/cryptomator/commit/a6e2548f32c399fb09563130ffe4b14f6ca13f87#commitcomment-9414651>
> .
>


TESTS FAILED
 Mr.roboto url : http://jenkins.plone.org/roboto/get_info?push=986b4e4e2ff24ed7895e07bf09c4c15b
 plone-4.3-python-2.6 [FAILURE]
plone-4.3-python-2.7 [FAILURE]
plone-5.0-python-2.7 [SUCCESS]


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 64](http://192.168.44.2:8111/viewLog.html?buildId=150&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


Hello,

Excuse my ignorance, is it a good practise to explicite the keyword "private"?

Regards,
Maher


Hey, really good point!


https://packagist.org/packages/kraksoft/nivo-slider is pointing at kraksoft/nivo-slider which makes composer semi-fail.
```
  - Installing kraksoft/nivo-slider (3.2-patch1)
    Downloading: connection...    Failed to download kraksoft/nivo-slider from dist: The "https://api.github.com/repos/kraksoft/nivo-slider/zipball/66f6d554a421042a24f931c3332c842921f635e6" file could not be downloaded (HTTP/1.1 404 Not Found)
    Now trying to download from source
  - Installing kraksoft/nivo-slider (3.2-patch1)
    Cloning 66f6d554a421042a24f931c3332c842921f635e6
Enter passphrase for key '/home/**/.ssh/id_rsa':
```

It would be nicer if the first worked, which I think it will if you point packagist to kedrap instead of kraksoft.


@dustalov, а можешь добавить инструкцию по поводу того, как в XeLaTeX правильно собирать шаблон под Linux?

Под Kubuntu 14.04 после установки
```
$ sudo apt-get install msttcorefonts
$ sudo fc-cache -fv
```

имею проблему:

```
! Package polyglossia Error: The current roman font does not contain the Cyrill
ic script!
(polyglossia)                Please define \cyrillicfont with \newfontfamily.
```


Only the 5.6 version of PHP can override a method that can receive one or more arguments.


Oh ok, wasn't sure and didn't want to insult you, if you were serious about it. :wink:

How about ClosablePool and PooledClosable?


我是觉得，我们添加了 iBeacons 新功能，反而不好理解，可以 添加了定内定位（iBeacons）新功能


We are loggin only slice.getResource.getId() in other messages, but here the whole slice is logged.
Wouldn't it be better to use same approach in all log messages?


@MaherJendoubi it's the [coding style](https://github.com/dotnet/corefx/wiki/Contributing#c-coding-style) they picked, I don't think you'll get a clear answer whether it's a good or bad practise (e.g. there are people who don't like it) :smile:

> 5.We always specify the visibility, even if it's the default (i.e.  `private string _foo ` not  `string _foo`).


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 64](http://192.168.44.2:8111/viewLog.html?buildId=150&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **SUCCESS**
Summary: Tests passed: 12 Build time: 00:08:21


Used the JObject for parameter as Asp.Net Web api does not allows multiple parameter; i.e if the parameter are not of primitive types.


Same here. Or maybe you want details of the slice being logged?


Same here.


lol


Oh my


test


I am very interested in seeing this work for bowtie2. We've found that in tumor samples, bwa (and particularly bwa mem) makes an inordinate number of split reads; in many cases, bowtie2 reports a nice paired end alignment with 2-3 mismatches and bwa mem puts one read at a perfect match and splits the other read into two or more bits, separated by unreasonable gaps, to achieve an alignment that has 1-2 mismatches. Comparing variant calls from the two aligners is difficult (and depressing) but I am willing to do side by side tests.


@tonkonogov, не думаю, что в этом особый смысл есть. По поводу LaTeX vs XeTeX у каждого свои предпочтения, а PSCyr явно лучше, чем vanilla. Так что такое сравнение не особо людям нужно будет.


Can you show me widget that implements the method `run()` with arguments?


Предыдущий вариант был правильный :)


@Urigo Did you check what happens when you call remove directly on the collection and not through the watch? I think that will happen is the watch will get called and then the remove will get called again, expect the second time there will be nothing to remove. Is will also happen when adding through save. I think this won't cause bugs but it will affect performance...


I thought about pool, but I feel like pools are conventionally more about
having several objects of a common type and sharing them.

Since you mentioned "deferred", how about simply DeferredClosable and
DeferredCloser? Although "Closer" sounds weird. Or does it?

On Fri, Jan 23, 2015 at 1:15 PM, Sebastian Stenzel <notifications@github.com
> wrote:

> Oh ok, wasn't sure and didn't want to insult you, if you were serious
> about it. [image: :wink:]
>
> How about ClosablePool and PooledClosable?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Tillerino/cryptomator/commit/a6e2548f32c399fb09563130ffe4b14f6ca13f87#commitcomment-9414820>
> .
>


Not `"Expression"` but rather `"Pattern"` here.


DWand, you make a good point. We will need to make the table merging code aware of priority as well.


I heard you like puns, so I put a pun in your pun...


Whoops, copy and pasted from the `SpreadElement` definition. Doesn't matter too much since `ast-types` is only monkey patched here for regenerator.


В этом файле ты использовал теги спринговые, а в других нет. Есть ли в этом какой-то скрытый смысл? :)


Why not change the default to `DefaultValue = "2e-3"` that should not give any problems independent on the locale.


Oh, you are also checking:
```javascript
var bool = new Boolean(true);
is.boolean(bool);
```
I'll add this. Thanks for pointing that.


@akoeplinger thank you for the answer :+1: and personaly I like this style of coding :) . Many kudos to the whole team and awesome contributors!


嗯...同意


Ah, ok then. Noticed just in case you're using it for something (or regenerator does).


Why do you expect this check should return true for functions?


It has advantages and disadvantages I guess. For example, if you use https://github.com/mongofill/mongofill you don't need the extension.


@yellowled please backport to 2.0 branch if you want this in the 2.0 release


better using "null" string:
log.info("Removing resource " + (resource == null ? "null" : resource.getId()));
notice the quotes!

But that's being nit picking :D


Oh really, have you registered it with who?????


Thanks @Mortimer2013 , can you please file this issue separately at:
https://github.com/googlei18n/libphonenumber/issues/new

And please mention how you encountered this (in what demo / implementation, e.g. JavaScript vs. Java ...).
Thanks!


As the new options require an argument, we need an additional `case` block checking whether the previous word is `-t|--timeout`, see `_docker-compose_kill()` for an example. Otherwise completion would suggest service names right after `--timeout` and `-t`.


@Duncaen Sieht interessant aus, muss ich mir auf jeden Fall mal ansehen. Der "große" Client ist im Grunde ziemlicher Mist und Ich wusste bisher nicht, dass es auch eine offizielle Schnittstelle gibt. Funktioniert die auch mit freien Accounts?


Why don't you use @mlocati 's Punic/Calendar ?
http://punic.github.io/#Calendar-class


Turns out the format does not matter as it is parsed anyway :) ... see [5a88c6b]


Is there a clearer way to do this? As noted, `COALESCE(landuse, 'forest')` is actually equivalent, but I view that as less clear.


Okay, except I was thinking isVirtualPath would be equivalent to your previous isRelativePath, i.e. "NOT isAbsolutePath".

Therefore, isVirtualPath defaults to true, etc.

I'm happy to do the changes if that makes sense.


Pessoal, o hotsite vai ter back-end?
Em 23/01/2015 08:07, "vieiragabriel" <notifications@github.com> escreveu:

> Vou ajustar no próximo commit. Faltou css específico, ai ele pegou do
> "body > *"
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/agile-alliance-brazil/agile-brazil-2015-hotsite/commit/32d02ad43d3064d3356b78243b9040fc3c0124e5#commitcomment-9413216>
> .
>


Ok


__API Blueprint syntax error on line 3075__: Undefined symbol DocumentLine Resource (Autogenerated message from apiary.io)


@pmdeazeta, I'm considering pulling this in. It would be great if you could confirm that you have not run into issues putting this to use.

Also, do you have a use case for setting a universal MWS_AUTH_TOKEN environment variable? I'm assuming the typical use case of tokens is when you more than one user.


This is more a general D question than a comment. I general use the following style for templates:
```D
bool hasValueAnnotation(alias f, Attr)()
{
 foreach (attr; __traits(getAttributes, f))
   static if (is(typeof(attr) == Attr))
     return true;
 return false;
}
```
because I find it easier to read. Most docs seem to use your style, which I find quite dense (not to mention you have to type hasValueAnnotation twice :). Any idea about the pros and cons?


This is Adebola's information


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 65](http://192.168.44.2:8111/viewLog.html?buildId=152&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


Shouldn't it be > instead of >= ?


It seems to work for me:
```
$ nix-shell -p

[nix-shell:~]$ echo $commonStripFlags
--enable-deterministic-archives
```

Where do you see it going wrong?

Also, we shouldn't pass `--enable-deterministic-archives` on all platforms. For instance, it won't work on Darwin.


Just checking... "pageId":"uk/culture"  shouldn't show weather.  isNetworkFront would be more accurate description.


Is there an use case for the parameter `applicationPathValue`?


So am I... I don't think you can change a commit once it's been published on Github. I usually make the needed changes. Copy the changed files somewhere else. Reset the repo to whatever base I was using (usually upstream/develop) using git reset --hard upsteam/develop, then force push it to my repo using git push origin +branchname, and then copy the files back and push it as a new commit.


@teh-jazzman so weit ich weiß leider nur mit premium accounts. Es gibt noch https://www.tomahawk-player.org/ aber so wie es aussieht wird dort auch libspotify verwendet und kann auch nicht mit einem freien account werdendet werden.


:+1:

Hm you're right about Pools: While it contains multiple resources and passes through the close call, it doesn't recycle and provide the resources to other objects.

Imo the name "Closer" represents its semantics quite well. It doesn't announce the factory characteristics, but thats ok.


What happens with multi-map transporters when both maps (continents) are loaded?
I see no check such that only the first map is used when loaded.


Ah.. OK. I am mostly a C programmer. Local variables do not get initialized in Java, but instance variables do. Still it would have been more clear if you had set it to zero like in the Corrupted Cannon case. But it is fine, as you said.


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 65](http://192.168.44.2:8111/viewLog.html?buildId=152&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **SUCCESS**
Summary: Tests passed: 13 Build time: 00:07:59


`base_report_designer` actually includes the OOo extension (can be dowloaded via a wizard), and installs the server-side plumbing to support it. The word "plugin"  was confusing in this context but it really designates the OpenOffice `extension`/`plugin`, not a `module`.

How about simply "OpenOffice extension for editing reports"?


Odoo -> "the system" ?


I happen to use hvvm just to run composer, and that requirement makes it fail big time.

My take is this: there may be a value to require extensions like mcrypt, because it's not obvious you need it to run a particular package. I see no value in requiring ext-mongo for laravel-mongodb, because it's pretty obvious you need to have a working extension or replacement, so there are only disadvantages.

I encourage you to remove the requirement.


Boa garoto! @ravishi


Didnt know how to, used Index.html temporarily for testing purposes.
Used your code and have made the changes.


Fixed in: https://github.com/Wikia/app/commit/0457da1cea4af621f75ee3d5b4f622b0cf7886b9


Well. I much <img src="https://cloud.githubusercontent.com/assets/5584865/5874880/af939996-a317-11e4-8664-ac853f71a655.png" alt="doge" width=17 height=20> not sure what ESP do I need to load.


On Fri, Jan 23, 2015 at 02:44:32AM -0800, pbrunet wrote:
> Je dirais qu'on ne s'est pas compris. Ici, la condition est vrai pour : t =
> np.array([int]) Du coup, il y a une inclusion dans tous les cas.

Yup, I fixed this :-)


I have prepared everything in the jenkins job and once this here hits mainline we will be able to switch sdk and ndk by either selecting them from the dropdown in the job (when building manually) or by altering our defaults in tools/buildsteps/defaultenv ... as i used complete new defines this is also 100% compatible to helix - i just need to ensure to make symlinks on the slave to the old ndk and sdk locations. see for reference:

https://github.com/Memphiz/xbmc/commit/a278863f81944437504b17922def0a8c3c6d28be

As you can see i have the arch hardcoded in the scripts for arm/x86 (as the jobs already decide which arch to build).


I think it's fine like this. The current code is more robust against changes in the WHERE clause.


Good catch @karan259


> The header element represents introductory content for its nearest ancestor sectioning content or sectioning root element. A header typically contains a group of introductory or navigational aids. When the nearest ancestor sectioning content or sectioning root element is the body element, then it applies to the whole page.

1. Sectioning roots - body, blockquote, details, dialog, figure, td, fieldset
2. Sectioning content - article, nav, section, aside


The enums are sorted alphabetically. You should do the same with this new one, not place it at the end.


....only i was a bit confused while reading how to update on node... confused enough to suggest the change anyway....

i don't know better, am i missing something?


I bet this should be done 10 ticks later (as above).


I see a space before the semicolon :smile_cat:


Thanks for the pointer. I don't figure it would make much sense to suggest arbitrary numbers for the timeout, so it's not nothing at all for the timeout flag.


This could probably also be in the abstract VolumeDriver ;)

How would this impact the performance? Because it would create local copies everytime it's asked.. How often is it called, an how important is it?


Hey Mike,
Can you update the changes that you had made  in the firmware here:
https://github.com/DexterInd/GrovePi/blob/master/Firmware/change_log.txt.

Thanks,
Karan Nayan

On Fri, Jan 23, 2015 at 6:24 PM, Mike Causer <notifications@github.com>
wrote:

> Good catch @karan259 <https://github.com/karan259>
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/DexterInd/GrovePi/commit/59452a8ec0d301c366ae1c12cb0974c5163935c8#commitcomment-9415270>
> .
>


Could you add a @property function with multiple variables. To make sure it is not called
```D
void @property bar( double a, double b )
{
    writeln("Functions annotated with @property and more than one variable should not be called");
    assert( 0 );
}
```


Looking good! It's now much more informative.
However Power should probably not have a capital "P"?


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 66](http://192.168.44.2:8111/viewLog.html?buildId=154&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) is now running


I don't think mr. author is particularly active :P


I only corected the things that git apply patch told me


Right, sorry, Done in 0a7c38a68533c858dbfefa3e0beda692828b96e9


Display names contain color codes on MassiveCraft. You should add `<i>` after `%s's`. Letting the `'s` be colored with the display name color looks good.

This message should be converted to be more like the message below. What was the power before the change? This information is relevant to the command sender as well is it not?


I agree with this placement. Placing this new command below the CmdFactionsPowerBoost is a good idea. However there should be a space added before the =.


waiting


there is no page class. This should probably be removed. cc: @dmandrioli


The worst that would happen is if one thread thinks a block is APPENDABLE, but it's actually not. However, the chances of this actually causing a problem are very low (it would have to match whatever is in the "used" data in terms of the block length). But there is a chance, which means it would happen -- very infrequently.

I don't see there being an issue with this if a block is unshared. The array append code already assumes it's thread local based on the type.


What version of Python were you using?  I found that Raspbian required a similar code change on Python 3.2(?) while Python 3.4.1 on Arch Linux worked with the current code base


Hello !
Thanks  a lot for the update, the folder works like a charm ! :)  ( i'm still using my own downloader from put.io to avoir any issues.  )


Seems to be broken. Cannot find any blocks.


TeamCity CI Experimen :: PHP Symfony2 project :: Symfony Project Test [Build 66](http://192.168.44.2:8111/viewLog.html?buildId=154&buildTypeId=CiExperimen_PhpSymfony2project_SymfonyProjectBuild) outcome was **SUCCESS**
Summary: Tests passed: 13 Build time: 00:06:41


yes

2015-01-23 14:05 GMT+01:00 sp-hash <notifications@github.com>:

> Seems to be broken. Cannot find any blocks.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/tpruvot/ccminer/commit/8e383fa1a4d0cde71eafb3f9f6352021755ad92a#commitcomment-9415394>
> .
>


TESTS FAILED
 Mr.roboto url : http://jenkins.plone.org/roboto/get_info?push=373d819656a24a8f8417284ec9f9be66
 plone-4.3-python-2.6 [FAILURE]
plone-4.3-python-2.7 [SUCCESS]


hola


Actually maybe in GWT it will be compiled to the same javascript code, so maybe it's not an issue. I suggest to investigate and change if necessary.


Looks good.


@TitanNano PR: https://github.com/mozillahispano/coseme/pull/11


@eea03 method getFiles shall be renamed to getTables or similar.


Why you disable it?


Again, why don't you take the value of check box in menu? You are still toggling it, which still looks weird. I mean if you have a check box in UI, and corresponding setting in data model, then on event from check box you should just take it's value (i.e. selected/not selected).


Cannot check strings like this -> "((()()()))"
Instead, learn about what classes can do. There's always an easier way, than shitty code.


Cool looking forward to testing this :).


Still looks weird with toggling, added more detailed comment to that commit.


German habits ^^ but yeah :)


toimii


test comment on commit


Very cool :)


@fbrnc

Thank you for your feedback. I will test your minimal composer installer in my next project as the Magento Hackathon Installer seems to be a bit buggy recently


typeof this.userConfig.center != 'undefined'
=>
 this.userConfig.center !== undefined


another comment on commit


Is that correct? Wouldn't the "or" run when save is nil?


line comment


Fixed


This expression is not broken, last I checked. In fact I use it all the time. :) That said, it's probably something I should keep as a private package anyway, since nobody else is likely to use it.


> The commit only says "modern look". This is anything but modern look ..
Okay.

> And from your email I was expecting to see the numbers on left and right to be dimmed out.
I couldn't find a way of doing that unless we hack into biojs sequence viewer plugin itself.


Étonnant que tu ai eu A+ !
https://lut.im/6A1ZU7n5/8MocqOMM


Not your code, but shouldn't the ampersand be encoded as an XML entity in this context?


return position


And the same is probably true in all the other `*/static/description/index.html`?


1. The workaround suggested there is for us to implement, but we're not sure whether it fixes the issue.
2. We don't plan to look at it, we'll look at it when we can.

I prefer to keep this as it is.


hmm, this seems wrong to me.
My understanding was that all levels were optional before?


This appears not to have been merged yet: https://github.com/adhearsion/voicemail/pull/36


The indentation in `config/routes.rb` could do with tweaking so it's easier to read how the routes are nested. Refer to the same file in the relevant commit in the bloccit-with-tdd repo if needed.


TESTS FAILED
 Mr.roboto url : http://jenkins.plone.org/roboto/get_info?push=459602b9104a4ed98e0204331d2d4c47
 plone-5.0-python-2.7 [FAILURE]


With OpenJDK. We can't test OpenJDK, the OpenJDK developers test OpenJDK. We test our services WITH different JDK implementations, no?


這個```是什麼啊？


Well, apart from the top-level if the field itself was required....of course
I can see value in being able to specify that we need to make a lower-level required, but doing it this way is very backwards-incompatible...


indentation !


Why?


Ah got ya, you mean the dots...


Without this 'meta', default charset for the page is 'Windows-1252'.
And when it is not Unicode, I cannot add Cyrillic characters to js-files, e.g. to specify 'я'-char in regex.


What the fuck is happening to me, I cannot write a single line of code without something going wrong anymore.


Rewording it to this:
"We don't offer evaluation licenses and trials at the moment. If you want to evaluate the engine, please contact sales@ontotext.com to get credentials for the Maven repository where the artifacts are stored."


Nice!


Changed format of tag.
It was: 'My description (c)'
Now: 'My description #c'


nice!


I cannot find any Issues page in this repository so I am posting here since it's relevant. More changes into the Conformal btc* repositories are about to happen: https://gist.github.com/davecgh/9bfbcc18fc6a59366939


It's a page from the Getting Started section, isn't it? It's a web page and even has its own url - http://ontotext-ad.github.io/recommend-pub-docs/docs/installation/.


Why the change to `cl-destructuring-bind`?


Witziger Dienst :smile:


+1, remove, ore replace with "that was originally written for, but is not limited to the Wikidata project".


Contextual, based on content context :)

All recommendations are content recommendations, since we recommend content. They can be either based on user behavior + contextual similarity or simply on contextual similarity.

Not really sure how this should be phrased...


Hey Eric, referring to the question on `topic_params`, try these in order and see if that sheds any light on what's causing the `NoMethodError` issue.

Startup the app and try updating a topic with the current code. Check it works without error.

Next try changing [line 37 in `TopicsController`](https://github.com/Ewiseman/bloccit/commit/7db1e1851abbda5cf84b336893d5ea7a255b0422#diff-8e904d13bca5807aec0e6f61c67f1c96R37) to use `topic_params`:

```ruby
if @topic.update_attributes(topic_params)
```

Does an error happen now when doing a topic update? If yes, read the error message and check the line number it refers to. Try to debug and fix the error and send me an update with how you get on, and include any error messages and their stack traces.


It's tagged but I forgot to push tags. Done now, sorry. :)


Was wondering about this, I know the layout can change... and it actually changes on smaller devices (which I recall just now). Was thinking it will improve user friendliness. Removed it.


@scribetw 簡體中文的語言翻譯。因為在大陸地區這邊見到不少匿名揭示板也使用了Pixmicat系統，所以就想做一份簡體中文的語言文件來優化體驗。


It's not strictly necessary for the code to work, and I wanted to be explicit that the `flypkg-errors` modifications happen via dynamic binding rather than lexical. Omitting `lexical-binding` informs the user that there is no lexical binding happening, which can be helpful for comprehension. :-)


Typo `variable` and `overridden`.


It was what I wanted but after more testing it appears it was a mistake. The only usable require to achieve https://github.com/clmath/requirejs-dplugins/commit/47acc6ff623971f365641a932da8747058967195#commitcomment-9308317 is the module require.


> Why the change to cl-destructuring-bind?

Syntax is a little less noisy, but I don't care much either way, and I didn't go to the trouble of changing most of the `pcase-let` occurrences.


Typo `overridden`.


Pages :)


27:1: I101 Imported names are in the wrong order. Should be CFG_BIBFORMAT_FORMAT_TEMPLATE_EXTENSION, CFG_BIBFORMAT_TEMPLATES_PATH
28:6: E126 continuation line over-indented for hanging indent
30:1: I100 Imports statements are in the wrong order. from invenio.modules.formatter should be before from invenio.modules.formatter.config
57:52: E231 missing whitespace after ':'
58:49: E231 missing whitespace after ':'
59:48: E231 missing whitespace after ':'
65:43: E261 at least two spaces before inline comment
65:44: E262 inline comment should start with '# '
70:52: E231 missing whitespace after ':'
71:49: E231 missing whitespace after ':'
72:48: E231 missing whitespace after ':'
76:5: E303 too many blank lines (3)
80:1: E302 expected 2 blank lines, found 1
80: D401 First line should be imperative: 'Return', not 'Returns'
80: D205 Blank line missing between one-line summary and description
110:16: E127 continuation line over-indented for visual indent
114:57: E231 missing whitespace after ':'
115:61: E231 missing whitespace after ':'
116:57: E231 missing whitespace after ':'
122:57: E231 missing whitespace after ':'
123:61: E231 missing whitespace after ':'
124:57: E231 missing whitespace after ':'
132:24: E713 test for membership should be 'not in'
144: D401 First line should be imperative: 'Return', not 'Returns'
144: D400 First line should end with '.', not 't'
162:32: E225 missing whitespace around operator
204:5: F841 local variable 'tags' is assigned to but never used
205:53: E261 at least two spaces before inline comment
205:54: E262 inline comment should start with '# '
208:79: E261 at least two spaces before inline comment
208:80: E262 inline comment should start with '# '
210:17: E261 at least two spaces before inline comment
210:18: E262 inline comment should start with '# '
211:52: E261 at least two spaces before inline comment
211:53: E262 inline comment should start with '# '
215:58: E231 missing whitespace after ':'
216:62: E231 missing whitespace after ':'
217:13: B901 blind except: statement
227:1: E302 expected 2 blank lines, found 1
254:41: E231 missing whitespace after ':'
255:45: E231 missing whitespace after ':'
256:45: E231 missing whitespace after ':'
259:5: E303 too many blank lines (2)


43:1: E302 expected 2 blank lines, found 1
43: D401 First line should be imperative: 'Return', not 'Returns'
59:1: E302 expected 2 blank lines, found 1
59: D401 First line should be imperative: 'Return', not 'Returns'
59: D400 First line should end with '.', not 'e'
67:16: E225 missing whitespace around operator
72:1: E302 expected 2 blank lines, found 1
72: D401 First line should be imperative: 'Return', not 'Returns'
72: D400 First line should end with '.', not ','
72: D205 Blank line missing between one-line summary and description
81:16: E225 missing whitespace around operator
86:1: E302 expected 2 blank lines, found 1
86: D401 First line should be imperative: 'Return', not 'Returns'
98:1: E302 expected 2 blank lines, found 1
98: D401 First line should be imperative: 'Return', not 'Returns'
98: D400 First line should end with '.', not 'e'
106:16: E225 missing whitespace around operator
111:1: E302 expected 2 blank lines, found 1
111: D401 First line should be imperative: 'Return', not 'Returns'
123:1: E302 expected 2 blank lines, found 1
143: D401 First line should be imperative: 'Return', not 'Returns'
153:17: E225 missing whitespace around operator
156:16: E225 missing whitespace around operator
161:1: E302 expected 2 blank lines, found 1
181:1: E302 expected 2 blank lines, found 1
181: D401 First line should be imperative: 'Remove', not 'Removes'
181: D400 First line should end with '.', not "'"
200:1: E302 expected 2 blank lines, found 1
200: D202 No blank lines allowed *after* function docstring, found 1
216:1: E302 expected 2 blank lines, found 1
216: D401 First line should be imperative: 'Set', not 'Sets'
216: D400 First line should end with '.', not 'e'
234:1: E302 expected 2 blank lines, found 1
234: D401 First line should be imperative: 'Return', not 'Returns'
234: D400 First line should end with '.', not 'e'
250:1: E302 expected 2 blank lines, found 1
250: D401 First line should be imperative: 'Set', not 'Sets'
250: D400 First line should end with '.', not 'e'
269: D401 First line should be imperative: 'Set', not 'Sets'
269: D400 First line should end with '.', not 'e'
289: D202 No blank lines allowed *after* function docstring, found 1
315:54: E261 at least two spaces before inline comment
317:15: E225 missing whitespace around operator
317:41: E225 missing whitespace around operator
327:1: E302 expected 2 blank lines, found 1
342:1: E302 expected 2 blank lines, found 1
356:29: E261 at least two spaces before inline comment
358:28: E261 at least two spaces before inline comment


1: D400 First line should end with '.', not 'n'
23: D203 Expected 1 blank line *before* class docstring, found 0
23: D400 First line should end with '.', not 'l'
26: D401 First line should be imperative: 'Print', not 'Prints'
26: D202 No blank lines allowed *after* method docstring, found 1
26: D400 First line should end with '.', not 's'


26:1: I100 Imports statements are in the wrong order. from invenio.ext.sqlalchemy should be before from sqlalchemy.exc
31:1: I101 Imported names are in the wrong order. Should be Bibfmt, Format, Formatname
34: D401 First line should be imperative: 'Return', not 'Returns'
51: D401 First line should be imperative: 'Return', not 'Returns'
69: D401 First line should be imperative: 'Return', not 'Returns'
69: D400 First line should end with '.', not 'e'
83: D401 First line should be imperative: 'Return', not 'Returns'
83: D400 First line should end with '.', not ','
83: D205 Blank line missing between one-line summary and description
100: D401 First line should be imperative: 'Return', not 'Returns'
110: D401 First line should be imperative: 'Return', not 'Returns'
110: D400 First line should end with '.', not 'e'
124: D401 First line should be imperative: 'Return', not 'Returns'
153: D401 First line should be imperative: 'Return', not 'Returns'
173: D401 First line should be imperative: 'Return', not 'Returns'
187: D401 First line should be imperative: 'Set', not 'Sets'
187: D400 First line should end with '.', not 'e'
210: D401 First line should be imperative: 'Return', not 'Returns'
251: D401 First line should be imperative: 'Remove', not 'Removes'
251: D400 First line should end with '.', not "'"
270: D401 First line should be imperative: 'Return', not 'Returns'
270: D400 First line should end with '.', not 'e'
282: D401 First line should be imperative: 'Set', not 'Sets'
282: D400 First line should end with '.', not 'e'
295: D401 First line should be imperative: 'Return', not 'Returns'
295: D400 First line should end with '.', not 'e'
312: D401 First line should be imperative: 'Set', not 'Sets'
312: D400 First line should end with '.', not 'e'
326:1: E303 too many blank lines (3)
326: D401 First line should be imperative: 'Return', not 'Returns'
326: D400 First line should end with '.', not 'e'
338: D401 First line should be imperative: 'Set', not 'Sets'
338: D400 First line should end with '.', not 'e'
352:1: E303 too many blank lines (3)
352: D401 First line should be imperative: 'Set', not 'Sets'
382: D400 First line should end with '.', not 't'
393: D401 First line should be imperative: 'Return', not 'Returns'
393: D400 First line should end with '.', not "'"
423: D401 First line should be imperative: 'Return', not 'Returns'
423: D400 First line should end with '.', not 'd'
423: D205 Blank line missing between one-line summary and description


41:1: I100 Imports statements are in the wrong order. import os should be before import sys
42:1: I100 Imports statements are in the wrong order. import inspect should be before import os
44:1: I100 Imports statements are in the wrong order. import cgi should be before import traceback
47:1: I101 Imported names are in the wrong order. Should be current_app, has_app_context
48:1: I100 Imports statements are in the wrong order. from operator should be before from flask
48:1: I201 Missing newline before sections or imports.
49:1: I201 Missing newline before sections or imports.
50:1: I201 Missing newline before sections or imports.
52:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from werkzeug.utils
53:1: I101 Imported names are in the wrong order. Should be CFG_BIBFORMAT_CACHED_FORMATS, CFG_BIBFORMAT_DISABLE_I18N_FOR_CACHED_FORMATS, CFG_BIBFORMAT_HIDDEN_TAGS, CFG_SITE_LANG
53:1: F401 'CFG_BIBFORMAT_CACHED_FORMATS' imported but unused
53:1: F401 'CFG_BIBFORMAT_HIDDEN_TAGS' imported but unused
54:6: E126 continuation line over-indented for hanging indent
59:6: E126 continuation line over-indented for hanging indent
60:1: I101 Imported names are in the wrong order. Should be create_record, record_empty, record_get_field_instances, record_get_field_value, record_get_field_values, record_xml_output
61:6: E126 continuation line over-indented for hanging indent
70:1: I101 Imported names are in the wrong order. Should be gettext_set_language, language_list_long, wash_language
70:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from .models
70:1: I201 Missing newline before sections or imports.
71:6: E126 continuation line over-indented for hanging indent
75:1: I101 Imported names are in the wrong order. Should be CFG_BIBFORMAT_FORMAT_JINJA_TEMPLATE_EXTENSION, CFG_BIBFORMAT_FORMAT_OUTPUT_EXTENSION, CFG_BIBFORMAT_FORMAT_TEMPLATE_EXTENSION, CFG_BIBFORMAT_OUTPUTS_PATH, CFG_BIBFORMAT_TEMPLATES_DIR, InvenioBibFormatError
75:1: I201 Missing newline before sections or imports.
75:1: F401 'CFG_BIBFORMAT_TEMPLATES_DIR' imported but unused
75:1: F401 'CFG_BIBFORMAT_OUTPUTS_PATH' imported but unused
76:6: E126 continuation line over-indented for hanging indent
82:1: I101 Imported names are in the wrong order. Should be parse_tag, record_get_xml
82:1: I100 Imports statements are in the wrong order. from invenio.modules.formatter.utils should be before from .config
83:6: E126 continuation line over-indented for hanging indent
85:1: I101 Imported names are in the wrong order. Should be CFG_HTML_BUFFER_ALLOWED_ATTRIBUTE_WHITELIST, CFG_HTML_BUFFER_ALLOWED_TAG_WHITELIST, HTMLWasher
86:6: E126 continuation line over-indented for hanging indent
89:1: I100 Imports statements are in the wrong order. from invenio.modules.knowledge.api should be before from invenio.utils.html
90:1: I100 Imports statements are in the wrong order. from invenio.ext.template should be before from invenio.modules.knowledge.api
91:1: I100 Imports statements are in the wrong order. from HTMLParser should be before from invenio.ext.template
91:1: I201 Missing newline before sections or imports.
92:1: I201 Missing newline before sections or imports.
100:27: E261 at least two spaces before inline comment
101:28: E111 indentation is not a multiple of four
101:28: E113 unexpected indentation
102:28: E111 indentation is not a multiple of four
102:28: E113 unexpected indentation
103:28: E111 indentation is not a multiple of four
103:28: E113 unexpected indentation
106:28: E111 indentation is not a multiple of four
106:28: E113 unexpected indentation
120:33: E225 missing whitespace around operator
211: D203 Expected 1 blank line *before* class docstring, found 0
215: D401 First line should be imperative: 'Return', not 'Returns'
215: D400 First line should end with '.', not 's'
227: D401 First line should be imperative: 'Return', not 'Returns'
252: D102 Docstring missing
291: D103 Docstring missing
297: D401 First line should be imperative: 'Format', not 'Formats'
297: D400 First line should end with '.', not 'f'
297: D205 Blank line missing between one-line summary and description
344:45: E127 continuation line over-indented for visual indent
487:27: E225 missing whitespace around operator
490:5: E303 too many blank lines (2)
508:82: E225 missing whitespace around operator
550: D103 Docstring missing
566: D401 First line should be imperative: 'Return', not 'Returns'
566: D202 No blank lines allowed *after* function docstring, found 1
566: D400 First line should end with '.', not 'g'
566: D205 Blank line missing between one-line summary and description
587:64: E261 at least two spaces before inline comment
587:65: E262 inline comment should start with '# '
594:38: E261 at least two spaces before inline comment
594:39: E262 inline comment should start with '# '
595:48: E261 at least two spaces before inline comment
595:49: E262 inline comment should start with '# '
598:24: E127 continuation line over-indented for visual indent
607: D103 Docstring missing
610: D400 First line should end with '.', not 's'
610: D200 One-line docstring should not occupy 3 lines
623: D290 White spaces around docstring should be trimmed.
623: D400 First line should end with '.', not 'a'
623: D205 Blank line missing between one-line summary and description
655:57: E126 continuation line over-indented for hanging indent
662:5: E303 too many blank lines (2)
721: D401 First line should be imperative: 'Evalute', not 'Evalutes'
741: D401 First line should be imperative: 'Analyse', not 'Analyses'
741: D202 No blank lines allowed *after* function docstring, found 1
810: D401 First line should be imperative: 'Return', not 'Returns'
810: D400 First line should end with '.', not 't'
810: D205 Blank line missing between one-line summary and description
909:13: B901 blind except: statement
940:78: E225 missing whitespace around operator
941:54: E225 missing whitespace around operator
973:47: E261 at least two spaces before inline comment
988:27: E225 missing whitespace around operator
1048: D401 First line should be imperative: 'Filter', not 'Filters'
1058: D401 First line should be imperative: 'Searche', not 'Searches'
1058: D400 First line should end with '.', not 's'
1058: D205 Blank line missing between one-line summary and description
1084:9: E303 too many blank lines (2)
1098:5: E303 too many blank lines (2)
1101:1: E302 expected 2 blank lines, found 1
1101: D401 First line should be imperative: 'Return', not 'Returns'
1115:5: F841 local variable '_' is assigned to but never used
1118:12: E127 continuation line over-indented for visual indent
1127:16: E126 continuation line over-indented for hanging indent
1149:5: B901 blind except: statement
1161: D401 First line should be imperative: 'Return', not 'Returns'
1161: D400 First line should end with '.', not 's'
1181:16: E126 continuation line over-indented for hanging indent
1188:1: E302 expected 2 blank lines, found 1
1188: D401 First line should be imperative: 'Return', not 'Returns'
1188: D400 First line should end with '.', not 'e'
1220:13: E303 too many blank lines (2)
1234: D401 First line should be imperative: 'Return', not 'Returns'
1268:16: E127 continuation line over-indented for visual indent
1278:31: E126 continuation line over-indented for hanging indent
1305:9: B901 blind except: statement
1317:17: E126 continuation line over-indented for hanging indent
1324:1: E302 expected 2 blank lines, found 1
1324: D401 First line should be imperative: 'Return', not 'Returns'
1324: D400 First line should end with '.', not 'e'
1368:1: E302 expected 2 blank lines, found 1
1368: D401 First line should be imperative: 'Return', not 'Returns'
1368: D202 No blank lines allowed *after* function docstring, found 1
1495:1: E302 expected 2 blank lines, found 1
1495: D401 First line should be imperative: 'Return', not 'Returns'
1495: D202 No blank lines allowed *after* function docstring, found 1
1522:17: E225 missing whitespace around operator
1590:1: E302 expected 2 blank lines, found 1
1590: D401 First line should be imperative: 'Return', not 'Returns'
1590: D400 First line should end with '.', not 't'
1634:28: E261 at least two spaces before inline comment
1634:29: E262 inline comment should start with '# '
1682:5: B901 blind except: statement
1788:1: E302 expected 2 blank lines, found 1
1788: D401 First line should be imperative: 'Return', not 'Returns'
1788: D202 No blank lines allowed *after* function docstring, found 1
1788: D400 First line should end with '.', not '}'
1805:56: E225 missing whitespace around operator
1829:1: E302 expected 2 blank lines, found 1
1829: D401 First line should be imperative: 'Return', not 'Returns'
1829: D400 First line should end with '.', not 'e'
1858:26: F821 undefined name 'exc'
1860:22: F821 undefined name 'exc'
1863:1: E302 expected 2 blank lines, found 1
1863: D401 First line should be imperative: 'Return', not 'Returns'
1896:1: E302 expected 2 blank lines, found 1
1896: D401 First line should be imperative: 'Return', not 'Returns'
1940:1: E302 expected 2 blank lines, found 1
1951:1: E302 expected 2 blank lines, found 1
1951: D203 Expected 1 blank line *before* class docstring, found 0
1951: D204 Expected 1 blank line *after* class docstring, found 0
1951: D400 First line should end with '.', not 'n'
1951: D205 Blank line missing between one-line summary and description
1982:15: E261 at least two spaces before inline comment
1984: D401 First line should be imperative: 'Create', not 'Creates'
2016:31: E261 at least two spaces before inline comment
2040: D401 First line should be imperative: 'Return', not 'Returns'
2040: D400 First line should end with '.', not 'e'
2055: D401 First line should be imperative: 'Return', not 'Returns'
2055: D400 First line should end with '.', not 'd'
2078: D401 First line should be imperative: 'Return', not 'Returns'
2078: D400 First line should end with '.', not 'e'
2078: D205 Blank line missing between one-line summary and description
2116: D401 First line should be imperative: 'Return', not 'Returns'
2116: D202 No blank lines allowed *after* method docstring, found 1
2225:36: E127 continuation line over-indented for visual indent
2228: D401 First line should be imperative: 'Return', not 'Returns'
2285:33: E127 continuation line over-indented for visual indent
2296:60: E251 unexpected spaces around keyword / parameter equals
2298:54: E251 unexpected spaces around keyword / parameter equals
2308:37: E127 continuation line over-indented for visual indent
2319:64: E251 unexpected spaces around keyword / parameter equals
2321:58: E251 unexpected spaces around keyword / parameter equals


Typo: ~~with~~ by


There may be more effective code:
q = (p == vp->strvalue)?strchr(vp->strvalue,':'):NULL;


Typo: ~~This~~ These


各ウィジェットには閉じるボタンは付けないほうがいいかなあと思います。
ユーザ的にはここでウィジェットが消えるようになっていると復活できなくて困りそう。
ウィジェットの表示/非表示はメニューバーの「表示」からいじらせたい。


Bon même en lisant https://www.ssllabs.com/downloads/SSL_Server_Rating_Guide.pdf
Je n'arrive pas à avoir un A+.
https://lut.im/EfePoN7H/BmHUOBWd
As-tu une idée ?


I changed it back, because the code uses lots of `pcase` anyway.


hello world


Right. Don't worry about that. I am in touch with biojs-vis-sequence devs and have gone through the internals.


I think I'm correct here. Couldn't find the exact rule, but think it's something like Rule 4 here - http://www.grammarbook.com/grammar/subjectVerbAgree.asp


Thank you, Vitalij! Originally I used $items to store rows and then I wanted to rename it to $data because of the index of the array. I forgot to rename it everywhere. $items = array() would better then isset+unset so I will change it but really thank you for your help..


@sonarcloud check


This commit also addresses issue #60


separateIsX のbool値が逆な気がします


cc @whyrusleeping


I corrected 'variable' but what do you mean with 'overridden'?


response?


format right after the server returns the data.


I pretty sure that 'overritten' is correct. It is the third form of 'overwrite'


 Moi aussi j'ai commit des trucs.
 Je parie que tu ne comprendras jamais le code Ophir !


Overwrite and override have a different meanings. Here we need override. The particip is overridden.


Aha - but the original implementation (unchanged from S3LocationSelectorWidget2) made all selectable levels required if the location was required. I was always struggling with that, but I had no other source of requirements than the original implementation and didn't want to change it even /because/ I didn't want to break backwards-compatibility :D

If you though had a different understanding, then obviously that implementation was wrong (despite I assumed it was correct), and needs to be turned around. Makes a lot more sense that way.

In this case, we should turn this around and make the "optional" parameter a "required" parameter.

Don't merge just yet - I'll change that.


done


:+1:  would appreciate to see this fixed/merged soon...


@benkaiser Nah, I just wanted to open this for discussion before submitting a PR. Landed in a8eed355276dd4e5c93d98cfe493696e0c2f23f4 anyway, so all good :)


Would probably be (+have been) useful to have a comment somewhere explaining that.


At this point the error should happen at the very beginning, in  mapping.load(is) and there is no way we can work without loading this properties files. I think a throwing a runtime error is more appropriate.


@briantigerchow isn't this enough? do i have to change anything else?


Cheers! :smile:


uppercase F in csarfile


NB I'm not sure we need a 'required' parameter yet?
I've never seen that requriement.

I am sure you are mistaken as to the behaviour of the old selector


note to self, we need:

```
              if (callsCounter > 0) {
                subscription.value().request(Long.MAX_VALUE - 1);
                callsCounter--;
              } else {
                // we don't want to keep this test running forever so we cancel after `callsCounter` spins
                subscription.value().cancel();
              }

```


> I wanted to be explicit that the `flypkg-errors` modifications happen via dynamic binding

It's already very explicit: it's a `defvar` and therefore a special variable. Do we really need to worry about people who don't know Emacs Lisp? I'd take unused variable warnings over them any day.


Rephrase to 'built-in points for extending and tuning'... or 'built-in customization points'


I think the passed uri should be already properly escaped in `links.rb`.


Found some issues with this in the ingame alt-f2 cheat menu. Items in the unit list often spam the log with this error:

WARNING: Warning: Unable to find file: /icons/units/opc2001_icon.dds
WARNING: stack traceback:
WARNING:         c:\github\fa\lua\ui\uiutil.lua(345): in function `UIFile'
WARNING:         ...iance\gamedata\lua.scd\lua\ui\dialogs\createunit.lua(451): in function <...iance\gamedata\lua.scd\lua\ui\dialogs\createunit.lua:442>
WARNING:         ...iance\gamedata\lua.scd\lua\ui\dialogs\createunit.lua(499): in function <...iance\gamedata\lua.scd\lua\ui\dialogs\createunit.lua:497>

Additionally, the checkboxes for filtering by faction/unit type etc are squished together and not labelled properly.


Please can you revert this? I want everything from `flypkg/check-all` to know nothing about flycheck.


Thank you.I do not have time to change it. Sorry :(
Alheimerjung


We had been string appending "(" ")" around the input and passing it off to eval.  At some point I trimmed that so that the files would be saved as a sequence of top-level expressions and then I call ev with (list input), so it verified a list of strings -- always safe.

Switched to use read and pass a list of exprs now.


Indeed - https://github.com/yeban/sequenceserver/blob/master/lib/sequenceserver/links.rb#L48. The entire fragment (after get_sequence/?) should be escaped and not just `sequence_ids`.


So the user of the API has to now provide a HttpClient to the API?


Thanks for this.


This can be _very_ problematic when the script is called in a pipelines.

It results in the same file being sorted multiple times - which is slow and consumes > 30G !!!! (I got bored and killed the script at this point) of /tmp per sort - this took down my server in a routine pipeline_mapping run by consuming all my /tmp space !!!

Can we please make this sorting optional, and off by default?

In pipelines I think we should add a proceeding task to sort the bed file or ideally sort the file in pipeline annotations.py? (I'm a bit surprised that it isn't already sorted?)


行末 ?> 也可以刪掉，比較推薦


whoop, nope - we'll move the `cancel` below the timeout-ed verify no async errors. It must be in a `finally` block.


You can't use import-from-derivation in Nixpkgs because it causes stuff to be built during evaluation (e.g. when doing `nix-env -qa`).


Hi,
I can't rembemer, I wrote that 3 months ago.
May I suggest a more robust way of parsing links, like the json module?


It would be unnecessary had you not been doing multiple changes in one commit.


I'm still thinking it is overwrite:
https://english.stackexchange.com/questions/88400/when-to-use-override-and-overwrite

In this case there is one information in the environmentvariable (e. g. 'foo') and after the command is run, there is another information in it (e. g. 'settings'). So the environmentvariable is rewritten, or overwritten.


lgtm


I can't revert it, as Flycheck is dumb and requires us to pass the checker name back to `flycheck-error-new-at`, but I can reorganize it. Is ed2ee0906fd4 better?


objects
            Object is Object
            Object.prototype is object
            Function.prototype is object
            Array.prototype is object
            Object.create(null) is object

    function checkObject1(val) {
        return val instanceof Object;
    }

    alert(Object instanceof Object);
    alert("isObject(Object) :"+ checkObject1(Object));
    alert("isObject(Object.create(null)) :"+ checkObject1(Object.create(null)));
    alert("isObject(Object.prototype) :"+ checkObject1(Object.prototype));

    //checkObject2(Object) -> false
    function checkObject2(val) {
        return (typeof val === 'object');
    }

    alert("isObject(Object) :"+ checkObject2(Object));
    alert("isObject(Object.create(null)) :"+ checkObject2(Object.create(null)));
    alert("isObject(Object.prototype) :"+ checkObject2(Object.prototype));

    function checkObject3(val) {
        var type = typeof val;
        return type === 'function' || type === 'object' && !!val
    }

    alert("isObject(Object) :"+ checkObject3(Object));
    alert("isObject(Object.create(null)) :"+ checkObject3(Object.create(null)));
    alert("isObject(Object.prototype) :"+ checkObject3(Object.prototype));


At the very least can we please be gzipping the sorted file here?


I don't know why I thought it would be easier to use number to select shapes, much easier to just use the letter of the block instead of memorizing the code for each shape


This doesn't do anything, it's under #ifdef SECURE_MM_HEAP which we have disabled (TARGET_DISPLAY_INSECURE_MM_HEAP)


cc: @rschmukler  - :+1:


Yeah, that's perfect. Thanks.


I am sure I'm not mistaken - since I have copied it 1:1 ;) not changed anything.
It's a typo (a "+" instead of a "-"), so simply a bug - though I of course assumed it was correct.


@tezyn I have tested my power function with negative exponents and in its current form it will not compute roots.  The function will just blow up.  So, yes, it only works with positive exponents.  The primitive (expt) will accept negative exponents.


TeamCity Ybackend :: Feodorov/ybackend [Build 75](http://192.168.30.225:8111/viewLog.html?buildId=636&buildTypeId=Ybackend_FeodorovYbackend&guest=1) is now running


TeamCity Ybackend :: AnnaPonomareva/ybackend [Build 143](http://192.168.30.225:8111/viewLog.html?buildId=637&buildTypeId=Ybackend_AnnaPonomarevaYbackend&guest=1) is now running


> It would've been be unnecessary had you not been doing multiple changes in one commit.

Maybe. We've both broken stuff along the way. :-)