@ryanbr You mean integrated in the tab itself?

If so, I tried this on Chromium and this ended up being not portable across browsers, without adding complexity to the code. In the end I picked the portable/simple solution. But the logger is really an `iframe`, so it can be embedded wherever, but I don't know enough about Firefox API to know if it's trivial or not.

If you mean feature-wise, like providing the filter list containing the filter, toggling on/off filters, uBlock is not there yet, I am still thinking about how best to get there code-wise.

@harshanvn It doesn't? What does not work?


Что значит domain axis ? Какой-то устоявшийся термин ? Если нет, тогда просто axis.


Any specific reason why we shouldn't touch it and do it the other way ?
I looked at the code and it seems more readable to simply touch the file.
I'd agree to run the touch through a library though


Can we change the flag to ```-f``` or ```-file``` or both.


all tests pass:
success: http://build.servo.org/builders/linux1/builds/927
success: http://build.servo.org/builders/linux2/builds/925
success: http://build.servo.org/builders/android/builds/963
success: http://build.servo.org/builders/mac1/builds/1142
success: http://build.servo.org/builders/mac2/builds/1142
success: http://build.servo.org/builders/gonk/builds/113


Bad idea, initialize static variable pointer with heap memory allocation (because order of this action isn't determined and realization and linkage type depended)


>Uhm, these changes clearly break ABI, as many AVS_CACHE_* constants got new values. So basically, people either need to check if their plugins used any of these, or the lazy way is to just recompile all C plugins for 2.6RC1. Duuuh.

Aren't those the same cache breakages that occurred in the C++ side during the move to 2.6a4?  The reason masktools2 had to be recompiled and whatnot.  Since I know of only a couple regularly-used C plugins (FFMS2's C interface and AssRender), I doubt it'll impact them much.  I've not seen any breaking in FFMS2 with RC1, so I don't think it uses them (but I haven't checked); dunno about AssRender.

One time that the C interface not being used much is actually something of a silver lining, I guess.

>The AVS_CACHE_THREAD_* stuff is interesting. Is this an indication that Ianb is planning to add threading in future versions?

As far as I ever knew, MT was always a vague possibility in classic but it wasn't growing past the stubs.  Something about the SetMTMode/GetMTMode actually having been in 2.6 but disabled/gone for public releases.  That's probably a remnant of it somehow.


fast-forwarding master to auto = 373a720d


Can you make sure there's a unit test for this on your branch then?


I smell Mr Pointer meddling in here


Леша, давай будет делать сразу хорошо. Основное предназначение кукбуки нфс или вордпресс?


The issue number in the commit message refers to the repository this code used to be in, toolness/mozilla-learning-html#4.


The issue number in the commit message refers to the repository this code used to be in, toolness/mozilla-learning-html#6.


Booth has switched to raft algrorithm:
http://en.wikipedia.org/wiki/Raft_%28computer_science%29


#bug
garbage on the log


/CC @sindresorhus


Exercicio 4.1


The issue number in the commit message refers to the repository this code used to be in, toolness/mozilla-learning-html#11.


This commit should be tag as stable version and 1.0.0 remove since without php 5.4 requirement in composer.json, it wont work on 5.3.


@repsac  Just want to note that I am not able to export BufferGeometry using the dev branch. I am getting:

```
Traceback (most recent call last):
  File "/Applications/blender.app/Contents/Resources/2.73/scripts/addons/io_three/__init__.py", line 715, in execute
    exporter.export_scene(filepath, settings)
  File "/Applications/blender.app/Contents/Resources/2.73/scripts/addons/io_three/exporter/__init__.py", line 19, in inner
    func(filepath, options, *args, **kwargs)
  File "/Applications/blender.app/Contents/Resources/2.73/scripts/addons/io_three/exporter/__init__.py", line 51, in export_scene
    scene_.write()
  File "/Applications/blender.app/Contents/Resources/2.73/scripts/addons/io_three/exporter/scene.py", line 131, in write
    geom_data = geom.copy()
  File "/Applications/blender.app/Contents/Resources/2.73/scripts/addons/io_three/exporter/geometry.py", line 129, in copy
    data = dispatch[scene]()
  File "/Applications/blender.app/Contents/Resources/2.73/scripts/addons/io_three/exporter/geometry.py", line 338, in _scene_format
    if self.options[constants.EMBED_GEOMETRY]:
KeyError: 'embedGeometry'
```

However, uncommenting all embed_geometry lines solve it for now.

Btw, thanks you very much for your work on the blender exporter!


Whoops, good catch; ended up on autopilot for the second half of that fix somehow :)


I discovered it because I was failing a unit test that already existed.
Sorry, I should have said that =) Good job unit test writer of the past!

On Wed, Mar 4, 2015, 8:24 AM Sam Tobin-Hochstadt <notifications@github.com>
wrote:

> Can you make sure there's a unit test for this on your branch then?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/racket/typed-racket/commit/ea942c2110d857fe7091609813094b726069d7b7#commitcomment-10029276>
> .
>


Generally if the kernel driver need create 'debug fs', the code should check whether `CONFIG_DEBUG_FS` is defined or not. So the code here should be modified.


#bug found


1: M111 unrecognized component name: general


@gorhill html5 datalist element does not work in safari as per w3schools


I have set the Default value a instance variable. Why do i need to set the value here specfically?


Will do.


Where can we find this theme Qawork - Theme


The game is misbehaving. Protect memory seemed to help with some of the random oddness such as textures disappearing. But it may have been a placebo affect.

The game has some major issues even with the fix for broken camera and missing terrain. The jeep handles wrong with CF2, but the game freezes on boot with CF1. Plus there's a persistent audio crackle. I couldn't get the sound to synch properly. AI=220 got the intro synching in the PAL version, but that didn't work for the NTSC version.

Also, the game needs Physical Lookup rather than Virtual Lookup - at least when using recompiler, which is extremely unstable anyway.


1: M111 unrecognized component name: BibKnowledge


1: M111 unrecognized component name: bibcatalog


22:1: E402 module level import not at top of file
23:1: E402 module level import not at top of file
24:1: E402 module level import not at top of file


1: D400 First line should end with '.', not 'y'
1: D205 Blank line missing between one-line summary and description
4: L102 copyright year is outdated, expected 2015 but got 2014
25:1: I101 Imported names are in the wrong order. Should be CFG_SITE_LANG, CFG_SITE_URL
25:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.modules.search.services
27:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.config
30:1: I100 Imports statements are in the wrong order. from urllib should be before from invenio.legacy.webuser
30:1: I201 Missing newline before sections or imports.
31:1: I100 Imports statements are in the wrong order. import re should be before from urllib
100:14: E128 continuation line under-indented for visual indent


1: M100 needs more reviewers
1: M101 signature is missing
1: M111 unrecognized component name: bibcheck


1: D100 Docstring missing


1: D400 First line should end with '.', not 'e'
1: D200 One-line docstring should not occupy 3 lines
28: D103 Docstring missing


1: D100 Docstring missing
21:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibedit.utils should be before from .backend
21:1: I201 Missing newline before sections or imports.
22:1: I101 Imported names are in the wrong order. Should be create_record, record_get_field_value
25:1: I101 Imported names are in the wrong order. Should be get_record, perform_request_search
26:1: I101 Imported names are in the wrong order. Should be field_get_subfield_values, print_rec, record_add_field, record_get_field_instances
26:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.legacy.search_engine
27:31: E126 continuation line over-indented for hanging indent
29:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.bibrecord
30:1: I101 Imported names are in the wrong order. Should be task_init, task_low_level_submission, task_sleep_now_if_required, task_update_progress, write_message
35:1: I100 Imports statements are in the wrong order. import string should be before from invenio.legacy.dbquery
36:1: I100 Imports statements are in the wrong order. import random should be before import string
38:1: I100 Imports statements are in the wrong order. import os should be before import time
39:1: I201 Missing newline before sections or imports.
40:1: I100 Imports statements are in the wrong order. from tempfile should be before from unidecode
40:1: I201 Missing newline before sections or imports.
57: D290 White spaces around docstring should be trimmed.
57: D203 Expected 1 blank line *before* class docstring, found 0
57: D204 Expected 1 blank line *after* class docstring, found 0
57: D400 First line should end with '.', not 'a'
57: D205 Blank line missing between one-line summary and description
64: D290 White spaces around docstring should be trimmed.
64: D203 Expected 1 blank line *before* class docstring, found 0
64: D204 Expected 1 blank line *after* class docstring, found 0
64: D400 First line should end with '.', not 'd'
64: D200 One-line docstring should not occupy 2 lines
70: D290 White spaces around docstring should be trimmed.
70: D400 First line should end with '.', not 'y'
75:29: E126 continuation line over-indented for hanging indent
86: D203 Expected 1 blank line *before* class docstring, found 0
86: D204 Expected 1 blank line *after* class docstring, found 0
86: D400 First line should end with '.', not 'r'
86: D200 One-line docstring should not occupy 3 lines
92: D401 First line should be imperative: 'Return', not 'Returns'
92: D400 First line should end with '.', not 'd'
114:45: E128 continuation line under-indented for visual indent
115:45: E128 continuation line under-indented for visual indent
116:45: E128 continuation line under-indented for visual indent
117:45: E128 continuation line under-indented for visual indent
122:45: E128 continuation line under-indented for visual indent
123:45: E128 continuation line under-indented for visual indent
124:45: E128 continuation line under-indented for visual indent
125:45: E128 continuation line under-indented for visual indent
127:33: E128 continuation line under-indented for visual indent
132:45: E128 continuation line under-indented for visual indent
133:45: E128 continuation line under-indented for visual indent
134:45: E128 continuation line under-indented for visual indent
135:45: E128 continuation line under-indented for visual indent
147:41: E127 continuation line over-indented for visual indent
148:41: E127 continuation line over-indented for visual indent
149:41: E127 continuation line over-indented for visual indent
150:41: E127 continuation line over-indented for visual indent
153:37: E128 continuation line under-indented for visual indent
154:37: E128 continuation line under-indented for visual indent
155:37: E128 continuation line under-indented for visual indent
156:37: E128 continuation line under-indented for visual indent
159:37: E128 continuation line under-indented for visual indent
160:37: E128 continuation line under-indented for visual indent
161:37: E128 continuation line under-indented for visual indent
162:37: E128 continuation line under-indented for visual indent
165:37: E128 continuation line under-indented for visual indent
166:37: E128 continuation line under-indented for visual indent
167:37: E128 continuation line under-indented for visual indent
168:37: E128 continuation line under-indented for visual indent
192:1: E266 too many leading '#' for block comment
194: D401 First line should be imperative: 'call', not 'calls'
194: D290 White spaces around docstring should be trimmed.
194: D400 First line should end with '.', not 'd'
222: D401 First line should be imperative: 'submit', not 'submits'
222: D290 White spaces around docstring should be trimmed.
222: D400 First line should end with '.', not 's'
235:39: E127 continuation line over-indented for visual indent
236:39: E127 continuation line over-indented for visual indent
239: D103 Docstring missing
245:1: E302 expected 2 blank lines, found 1
245: D290 White spaces around docstring should be trimmed.
245: D400 First line should end with '.', not 'h'
255: D290 White spaces around docstring should be trimmed.
255: D400 First line should end with '.', not 'y'
273: D401 First line should be imperative: 'Perform', not 'Performs'
273: D290 White spaces around docstring should be trimmed.
273: D209 Put multi-line docstring closing quotes on separate line
273: D400 First line should end with '.', not 'w'
273: D205 Blank line missing between one-line summary and description
336: D401 First line should be imperative: 'Construct', not 'Constructs'
340:9: E128 continuation line under-indented for visual indent
341:9: E128 continuation line under-indented for visual indent
342:9: E128 continuation line under-indented for visual indent
343:9: E128 continuation line under-indented for visual indent
344:9: E128 continuation line under-indented for visual indent
345:9: E128 continuation line under-indented for visual indent
346:9: E128 continuation line under-indented for visual indent
347:9: E128 continuation line under-indented for visual indent
348:5: E124 closing bracket does not match visual indentation


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not 's'
4: L102 copyright year is outdated, expected 2015 but got 2013
23:1: I101 Imported names are in the wrong order. Should be TexkeyNoAuthorError, TexkeySeq
25:1: E302 expected 2 blank lines, found 1
25: D200 One-line docstring should not occupy 3 lines
36:23: E261 at least two spaces before inline comment
40:21: E222 multiple spaces after operator
46:17: E128 continuation line under-indented for visual indent
48:1: W391 blank line at end of file


1: D100 Docstring missing
27: D103 Docstring missing


1: D400 First line should end with '.', not 'e'
1: D200 One-line docstring should not occupy 3 lines
4: L102 copyright year is outdated, expected 2015 but got 2013
24:1: I101 Imported names are in the wrong order. Should be record_get_field_value, record_get_field_values
27:1: I101 Imported names are in the wrong order. Should be BibCatalogTagNotFound, load_tag_code_from_name, record_get_value_with_provenence, record_id_from_record, record_in_collection, split_tag_code
27:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibcatalog.utils should be before from invenio.legacy.bibrecord
36: D401 First line should be imperative: 'Check', not 'Checks'
53: D401 First line should be imperative: 'Generate', not 'Generates'
53: D400 First line should end with '.', not 's'
53: D205 Blank line missing between one-line summary and description
125:15: E127 continuation line over-indented for visual indent
165: D401 First line should be imperative: 'Return', not 'Returns'
165: D205 Blank line missing between one-line summary and description


1: D400 First line should end with '.', not 'I'
4: L102 copyright year is outdated, expected 2015 but got 2013
28:1: E302 expected 2 blank lines, found 1
56:1: W391 blank line at end of file


1: D400 First line should end with '.', not 'a'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
37: D103 Docstring missing


1: D400 First line should end with '.', not 'k'
4: L102 copyright year is outdated, expected 2015 but got 2014
26:1: I100 Imports statements are in the wrong order. import getopt should be before import sys
29:1: I100 Imports statements are in the wrong order. import time should be before import traceback
30:1: I100 Imports statements are in the wrong order. import inspect should be before import time
34:1: I100 Imports statements are in the wrong order. from ConfigParser should be before from collections
37:1: I101 Imported names are in the wrong order. Should be get_modified_records_since, task_get_option, task_get_task_param, task_has_option, task_init, task_low_level_submission, task_set_option, task_sleep_now_if_required, task_update_progress, write_message
37:1: I201 Missing newline before sections or imports.
47:1: I101 Imported names are in the wrong order. Should be CFG_CERN_SITE, CFG_ETCDIR, CFG_PYLIBDIR, CFG_SITE_URL, CFG_TMPSHAREDDIR, CFG_VERSION
47:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.bibsched.bibtask
54:1: I101 Imported names are in the wrong order. Should be perform_request_search, search_pattern, search_unit_in_bibxxx
58:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibedit.utils should be before from invenio.legacy.search_engine
59:1: I101 Imported names are in the wrong order. Should be record_add_field, record_xml_output
60:1: I100 Imports statements are in the wrong order. from intbitset should be before from invenio.legacy.bibrecord
60:1: I201 Missing newline before sections or imports.
61:1: I201 Missing newline before sections or imports.
62:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibcatalog.api should be before from invenio.legacy.dbquery
64:1: I100 Imports statements are in the wrong order. from invenio.utils.json should be before from invenio.utils.shell
68:1: E302 expected 2 blank lines, found 1
68: D290 White spaces around docstring should be trimmed.
68: D203 Expected 1 blank line *before* class docstring, found 0
68: D204 Expected 1 blank line *after* class docstring, found 0
68: D400 First line should end with '.', not 'n'
70: D102 Docstring missing
72:13: E128 continuation line under-indented for visual indent
75: D290 White spaces around docstring should be trimmed.
75: D203 Expected 1 blank line *before* class docstring, found 0
75: D204 Expected 1 blank line *after* class docstring, found 0
75: D400 First line should end with '.', not 'n'
77: D102 Docstring missing
88: D401 First line should be imperative: 'Iterate', not 'Iterates'
149:55: E261 at least two spaces before inline comment
163: D290 White spaces around docstring should be trimmed.
163: D400 First line should end with '.', not 'n'
169:57: E261 at least two spaces before inline comment
175: D290 White spaces around docstring should be trimmed.
175: D400 First line should end with '.', not 'e'
182: D401 First line should be imperative: 'Change', not 'Changes'
182: D400 First line should end with '.', not 'e'
182: D205 Blank line missing between one-line summary and description
201:25: E128 continuation line under-indented for visual indent
204: D400 First line should end with '.', not 'd'
204: D200 One-line docstring should not occupy 3 lines
216: D290 White spaces around docstring should be trimmed.
216: D400 First line should end with '.', not 'd'
222: D290 White spaces around docstring should be trimmed.
222: D400 First line should end with '.', not 'd'
226:13: E128 continuation line under-indented for visual indent
228: D290 White spaces around docstring should be trimmed.
228: D400 First line should end with '.', not 'd'
231:17: E128 continuation line under-indented for visual indent
237: D290 White spaces around docstring should be trimmed.
237: D400 First line should end with '.', not 'd'
240:17: E128 continuation line under-indented for visual indent
244: D290 White spaces around docstring should be trimmed.
244: D400 First line should end with '.', not 'd'
248:17: E128 continuation line under-indented for visual indent
250: D290 White spaces around docstring should be trimmed.
250: D400 First line should end with '.', not 't'
254: D401 First line should be imperative: 'Yield', not 'Yields'
254: D400 First line should end with '.', not 'g'
265:5: E129 visually indented line with same indent as next logical line
271: D102 Docstring missing
276: D290 White spaces around docstring should be trimmed.
276: D202 No blank lines allowed *after* function docstring, found 1
276: D400 First line should end with '.', not 'k'
301:1: E302 expected 2 blank lines, found 1
341:25: E128 continuation line under-indented for visual indent
367:5: E266 too many leading '#' for block comment
379:1: E302 expected 2 blank lines, found 1
379: D290 White spaces around docstring should be trimmed.
379: D202 No blank lines allowed *after* function docstring, found 1
379: D400 First line should end with '.', not 'g'
422: D290 White spaces around docstring should be trimmed.
422: D202 No blank lines allowed *after* function docstring, found 1
422: D400 First line should end with '.', not 'd'
448:1: E302 expected 2 blank lines, found 1
448: D400 First line should end with '.', not 'e'
448: D200 One-line docstring should not occupy 3 lines
458:1: E302 expected 2 blank lines, found 1
458: D400 First line should end with '.', not 'e'
458: D200 One-line docstring should not occupy 3 lines
468:1: E302 expected 2 blank lines, found 1
468: D400 First line should end with '.', not 'e'
468: D205 Blank line missing between one-line summary and description
481: D202 No blank lines allowed *after* function docstring, found 1
481: D400 First line should end with '.', not 'd'
481: D205 Blank line missing between one-line summary and description
493:20: E261 at least two spaces before inline comment
498: D400 First line should end with '.', not 'e'
498: D205 Blank line missing between one-line summary and description
505:1: E302 expected 2 blank lines, found 1
528:1: E302 expected 2 blank lines, found 1
528: D290 White spaces around docstring should be trimmed.
528: D400 First line should end with '.', not 'e'
537: D290 White spaces around docstring should be trimmed.
537: D400 First line should end with '.', not 's'
554:47: E127 continuation line over-indented for visual indent
587: D400 First line should end with '.', not 's'
587: D200 One-line docstring should not occupy 3 lines
611: D401 First line should be imperative: 'Generate', not 'Generates'
652:16: E713 test for membership should be 'not in'
662: D400 First line should end with '.', not 'e'
662: D205 Blank line missing between one-line summary and description
675:1: E302 expected 2 blank lines, found 1
675: D400 First line should end with '.', not 'a'
675: D205 Blank line missing between one-line summary and description
730: D401 First line should be imperative: 'Print', not 'Prints'
730: D400 First line should end with '.', not 't'
732:12: E221 multiple spaces before operator
748: D401 First line should be imperative: 'Print', not 'Prints'
748: D400 First line should end with '.', not 't'
762: D401 First line should be imperative: 'Construct', not 'Constructs'
801:36: E127 continuation line over-indented for visual indent
820:19: E128 continuation line under-indented for visual indent
821:19: E128 continuation line under-indented for visual indent
824:1: W391 blank line at end of file


31:1: I100 Imports statements are in the wrong order. import getopt should be before import sys
34:1: I201 Missing newline before sections or imports.
37:1: I101 Imported names are in the wrong order. Should be CFG_OAI_FAILED_HARVESTING_EMAILS_ADMIN, CFG_OAI_FAILED_HARVESTING_STOP_QUEUE, CFG_SITE_SUPPORT_EMAIL
37:1: I100 Imports statements are in the wrong order. from invenio.config should be before from sqlalchemy
37:1: I201 Missing newline before sections or imports.
43:1: I101 Imported names are in the wrong order. Should be task_get_option, task_get_task_param, task_init, task_set_option, write_message
43:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibsched.bibtask should be before from invenio.modules.oaiharvester.models
49:1: I100 Imports statements are in the wrong order. from invenio.legacy.oaiharvest should be before from invenio.legacy.oaiharvest.config
50:1: I100 Imports statements are in the wrong order. from invenio.ext.logging should be before from invenio.legacy.oaiharvest
52:1: I100 Imports statements are in the wrong order. from invenio.base.factory should be before from invenio.ext.logging
54:1: I101 Imported names are in the wrong order. Should be compare_timestamps_with_tolerance, create_ticket, generate_harvest_report
59:1: I100 Imports statements are in the wrong order. from invenio.ext.email should be before from invenio.legacy.webuser
61:1: I101 Imported names are in the wrong order. Should be BibWorkflowEngineLog, BibWorkflowObjectLog, Workflow
64:1: I100 Imports statements are in the wrong order. from invenio.modules.workflows.api should be before from invenio.modules.workflows.registry
66:1: I100 Imports statements are in the wrong order. import invenio.legacy.template should be before from invenio.modules.workflows.errors
241:17: E266 too many leading '#' for block comment
258:21: E266 too many leading '#' for block comment
274: D290 White spaces around docstring should be trimmed.
280:13: E266 too many leading '#' for block comment
281:13: E266 too many leading '#' for block comment
388:27: F821 undefined name '__revision__'


1: D400 First line should end with '.', not 'e'
1: D205 Blank line missing between one-line summary and description
4: L102 copyright year is outdated, expected 2015 but got 2013
26:1: I100 Imports statements are in the wrong order. from invenio.bibknowledge should be before from invenio.utils.crossref
27:1: I100 Imports statements are in the wrong order. import difflib should be before from invenio.bibknowledge
27:1: I201 Missing newline before sections or imports.
30:1: E302 expected 2 blank lines, found 1
30: D290 White spaces around docstring should be trimmed.
30: D400 First line should end with '.', not 's'
34:1: E302 expected 2 blank lines, found 1
34: D290 White spaces around docstring should be trimmed.
34: D400 First line should end with '.', not 'y'
41:1: E302 expected 2 blank lines, found 1
41: D290 White spaces around docstring should be trimmed.
41: D400 First line should end with '.', not 'l'
48:1: E302 expected 2 blank lines, found 1
48: D400 First line should end with '.', not 'f'
48: D205 Blank line missing between one-line summary and description
109:5: E303 too many blank lines (2)
130: D400 First line should end with '.', not 'e'
130: D205 Blank line missing between one-line summary and description
146:1: W391 blank line at end of file


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not 's'
4: L102 copyright year is outdated, expected 2015 but got 2013
30:1: E302 expected 2 blank lines, found 1
30: D401 First line should be imperative: 'Correct', not 'Corrects'
30: D400 First line should end with '.', not 's'
31:9: E128 continuation line under-indented for visual indent
32:9: E128 continuation line under-indented for visual indent
32:35: E231 missing whitespace after ','
32:37: E231 missing whitespace after ','
76:21: E261 at least two spaces before inline comment
80:1: W391 blank line at end of file


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not ')'
4: L102 copyright year is outdated, expected 2015 but got 2013
24:1: I100 Imports statements are in the wrong order. from invenio.bibupload should be before from invenio.utils.crossref
27: D400 First line should end with '.', not 'd'
27: D205 Blank line missing between one-line summary and description
53:17: E128 continuation line under-indented for visual indent


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not 's'
4: L102 copyright year is outdated, expected 2015 but got 2013
22:1: E302 expected 2 blank lines, found 1
22: D401 First line should be imperative: 'Check', not 'Checks'
22: D205 Blank line missing between one-line summary and description
31:1: W391 blank line at end of file


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not 's'
4: L102 copyright year is outdated, expected 2015 but got 2013
23:1: I100 Imports statements are in the wrong order. import os should be before from invenio.legacy.bibdocfile.api
23:1: I201 Missing newline before sections or imports.
36:1: E302 expected 2 blank lines, found 1
36: D401 First line should be imperative: 'Validate', not 'Validates'
36: D400 First line should end with '.', not 'd'
36: D200 One-line docstring should not occupy 3 lines
52:13: E303 too many blank lines (2)
65:1: W391 blank line at end of file


现在你又多了一个新的 bug。。。 😂


Added here: 5713f8ee43d6f699b27809012054d8adeec563e0 and here: https://github.com/netguru/devise-ios-rails-example/commit/048ba60532cc9585e19a52779eb08a510b9bbe0c


Done


The cmake Makefile target is used. I guess latest LLVM means upgrading XCode. That would not be possible with Snow Leopard (OS X SL).


This existing class implementation in jsp file is identified and public jira[1] is created to move this to java code base in next release.

[1]https://wso2.org/jira/browse/REGISTRY-2434


typo error: lien should be line


Yes


Dat pakyu tho


Why was spl_ubc_umount removed?


This test is failing, it seems like some code is missing between `Y.Assert.isFalse(edited)` and `Y.Assert.isTrue(edited)`?


I think it is good to use getProperty(String key, String defaultValue) of  java.util.properties, if you want to enforce a default value.


This variable is not being used, can it be removed?


I copied those javafx classes and pasted them on eclipse in the same way but it shows loads of errors.....please help !


Why is this specific case not causing undefined behavior?


Does the form builder need to be created twice?


neighmovetrack.py is well-organized and the code quality is definitely at or above CellProfiler standards. Minor point here in CellFeatures and similarly in NeighbourMovementTracking - the parameters are static, bound to the class, and they do look like they depend on the scales within the image, so I am guessing that they are modified depending on the context in which they are used. Technically, it's possible that a pipeline could have two TrackObjects modules that would require that these parameters were set differently and that would fail.
I'd move these into an object that could be used to initialize the CellFeatures and NeighbourMovementTracking with module-specific values for the parameters.


This github - but the commits still get ported over to bitbucket - you just cursed @nsoranzo.


I think it'd be best to have all events have the same name for the field key, instead of each having its own key (`createdField`, `editedField` and `removedField`). It'll be simpler and easier to memorize how the events work.


Time to disable bitbucket notifications completely :)


This is against gitflow process, you shall not merge one feature branch into another feature branch. Only develop branch can be merged into feature branch.

If you need to test different features together, then a temporary branch shall be created, later is deleted without any finalisation (merge into develop branch or another feature branch).


"Directory" is the preferable rather than "folder", which is used in Microsoft Windows.


Should we use just a single colon for identifier? I do not think it's convenient for user to type in the command like this, e.g., "name: do revision duedate: tomorrow........"

And, we do not have description attribute for task for V0.1 We only have taskname, duedate, status. Please modify accordingly. You can also refer to Task class to see the attributes we have of a Task.


Complete this.


That looks suspiciously like all the config stuff for whatever IDE @samwilson93 is using! :disappointed: I'll add it to .gitignore and remove it from the repo in a new commit. Hopefully, next time you pull it should be gone! Sam... sorry if that buggers up your IDE config...


@zcbenz is this the right way of handling buffer data ?


@dkayiwa I now understood the problem which you were trying to explain :) can we add this this line to concept.java
 as a fix to this : descriptions = Collections.emptySet();


Not really. This happens only once per page load, so it's not something I have been worried about. If you want to measure how this help, just wrap up the code into a `quickProfiler` block and see the result.


right now the code downloads all files, regardless if they are defined or not in the extraFiles. Since this is the current feature, it's better to spec it like that.


This branch will be deleted in few days, this code is not part of Core repo. Use another repository for backup.


None of the ``ApplicationResources_*.properties`` have the license header because, as I mentioned on the commit log, l10n doesn't add it. See the [core translations](https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwiki-platform-oldcore/src/main/resources) for instance. It's failing now because we didn't had translation files in the rendering module before. I just added the first ones taken from l10n. Commons and platform are not failing because, unlike rendering which uses excludes as shown above, they use includes, and the ``ApplicationResources.properties`` file is included without its translations. The configuration of the ``license-maven-plugin`` is not consistent across top level modules.


1: M101 signature is missing
3: M102 unrecognized bullet/signature
1: M110 missing component name
1: M190 line is too long (62 > 50)


@zcbenz should i handling buffer response using `GetData` or should i implement a streaming interface like how `asarjob` does ? if not should the response be a node buffer ?


Please... This spawn a new process every time a key is pressed...


Maybe precise in the notice that your taking the default value?


I know what you mean.  I've been wrestling with it.

Use of core.async means that events are handled asynchronously which has a number of nice properties and is actually quite key to re-frame.  BUT I do understand the need to take away that async nature when testing.

And, yes, stack traces are a pain.  I've just checked in a change which will print them out BEFORE the exception makes it back into the core.async state machine.  But not ideal yet.

And I'm about to reinstate a way of removing aysnc from the testing process.


Con Ant si, pero la idea es con maven, este proyecto es muy ancestral :(


On pourra faire un helper qui prend en argument une liste de commentaires et un Id, mais il faut d'abord savoir quels seront les chaps des comments.


MySQL 5.6.21 on Linux @ UnoEuro hosting with case sensitivity enabled.

While installing it throws an Exception in Visual Studio and in the stack trace it can be seen

```
Exception:Thrown: "Table 'mysql_db.UMBRACONODE' doesn't exist" (MySql.Data.MySqlClient.MySqlException)
A MySql.Data.MySqlClient.MySqlException was thrown: "Table 'mysql_db.UMBRACONODE' doesn't exist"
```

After continuing from the exception it throws a Server Error because "Object reference not set to an instance of an object"

Stack Trace:

```
[NullReferenceException: Object reference not set to an instance of an object.]
   umbraco.library.GetXmlNodeByXPath(String xpathQuery) +51

[TargetInvocationException: Exception has been thrown by the target of an invocation.]
   System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) +0
   System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) +92
   System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) +155
   System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters) +19
   UmbracoExamine.LegacyLibrary.GetXmlNodeByXPath(String xpathQuery) +150
   UmbracoExamine.DataServices.UmbracoContentService.GetPublishedContentByXPath(String xpath) +42
   UmbracoExamine.BaseUmbracoIndexer.GetXDocument(String xPath, String type) +168
   UmbracoExamine.BaseUmbracoIndexer.AddNodesToIndex(String xPath, String type) +66
   UmbracoExamine.BaseUmbracoIndexer.PerformIndexAll(String type) +1505
   UmbracoExamine.UmbracoContentIndexer.PerformIndexAll(String type) +275
   Examine.LuceneEngine.Providers.LuceneIndexer.IndexAll(String type) in x:\Projects\Examine\Examine\Projects\Examine\LuceneEngine\Providers\LuceneIndexer.cs:749
   UmbracoExamine.BaseUmbracoIndexer.IndexAll(String type) +54
   UmbracoExamine.BaseUmbracoIndexer.PerformIndexRebuild() +117
   Examine.LuceneEngine.Providers.LuceneIndexer.RebuildIndex() in x:\Projects\Examine\Examine\Projects\Examine\LuceneEngine\Providers\LuceneIndexer.cs:704
   UmbracoExamine.BaseUmbracoIndexer.RebuildIndex() +48
   UmbracoExamine.UmbracoContentIndexer.RebuildIndex() +80
   Umbraco.Web.WebBootManager.Complete(Action`1 afterComplete) +251
   Umbraco.Core.UmbracoApplicationBase.StartApplication(Object sender, EventArgs e) +242
   Umbraco.Core.UmbracoApplicationBase.Application_Start(Object sender, EventArgs e) +40

[HttpException (0x80004005): Exception has been thrown by the target of an invocation.]
   System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +9903113
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +118
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +172
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +336
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +296

[HttpException (0x80004005): Exception has been thrown by the target of an invocation.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +9882460
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +101
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +254
```

Its exactly the same as the problem stated here (google cache because Umbraco site is currently down):

http://webcache.googleusercontent.com/search?q=cache:Jn0V5_vxKmAJ:https://our.umbraco.org/forum/getting-started/installing-umbraco/60775-Server-Error-during-installation+&cd=1&hl=en&ct=clnk

The answer there is to use SQL server and not MySQL. Then we come back to the initial question if MySQL is supported now in 7.2.2. and if not when do you plan to merge the changes to support case sensitivity.


It's a shame, because it's nicely written, but it looks like you're using our Cython implementation, so you might consider removing to avoid confusion.


changelog (axelstudios) - i386-Windows-7-VisualStudio-12: OK (2188 of 2212 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-warnings-yellow.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-98.92%25-yellow.svg)


Thanks :-)


Can somebody with a good understanding of what we now allow/disallow please update https://en.opensuse.org/openSUSE:Packaging_desktop_menu_categories so the list there matches what brp-check allows?


I have tried, but it doesn't works. It returns to ForumActivity after the app paused and resumed.


<?php
>


Do you really think we should remove these dependencies?


Hello @avinashdaiict ,
This is Amr Morad from EOL. First Thank you for your interest in our profile.
I think at the beginning, you need to be familiar with how current search is working. Currently we have 2 different views for searching in EOL: first one for our taxa, collection, images and etc, this is accomplished using solr and the other one for our data (SPARQL queries).
I suggest to download the code to your machine and try to figure out both search ways for now. Solr and Sparql queries general classes are under lib/eol, then you will find folders for sparql as well as solr.
Please don't hesitate to contact us if you have any question.
Thanks


makes sense. Thank you!


Why don't we move `get-gulp-tasks.js` into its own module? It seems like a handy thing for other apps as well.


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg)


This is not related to any UV component, it is script for creation of debian repository for ODN packages (see publish-main.sh line 18)
So we have to move it into opendatanode repo.


The format we use for function params is usually one of 3 options. Either all params on the same line, like this:

    this.fire('create', {createdField: field});

Or one param per line, like this:

    this.fire(
      'create',
      {createdField: field}
    );

Or, in case of object params, since alloy's lint task won't let expanded objects be all on the same line, putting all params on the same line except for the object itself, like this:

    this.fire('create', {
      createdField: field
    });


No it's not really in meter, just a pourcentage % of difference between the two extents


Thank you for this precious feedback. The numbers of nodes in the DB are a bit higher that what is reported, but that gives me an idea of what players percieve and what is really in the game. Also, the number of nodes were previously too high (prior to 1st fix which further increased nodes in some areas), so people *will* complain when the final fix will be released because some area will have less nodes than currently and - bad luck - most of them are the most lucrative areas for high level herbs (Felwood, Burning Steppes, Blasted Lands...).

However, I understand that the second fix was a bit too much, so I'll adjust the cell size again. Thank you. :)
Expect a fix of the fix soon. ;)


@kathi-fletcher "the TEKS tags only appear on the learning objectives and NOT on any other elements" --> Another place we will add TEKS tags -- to the TEKS language used in the first Teachers Edition content of every module.

See:
[TS CONTENT]
[TEKS]
The Learning Objectives in this section will help your students master the following TEKS:
...
(4C) analyze and describe accelerated motion in two dimensions using equations, including projectile and circular examples [TEKS-112-39-C-4C]


never gisted before, sent it as a public gist.

in case there is something to change or simular tasks, you're welcome.


Accidentally pushed to staging with debug set to true
On Mar 3, 2015 9:56 PM, "Kaitlin Hipkin" <notifications@github.com> wrote:

> @RaineForest <https://github.com/RaineForest> ?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/rit-csc/CSCWebsite/commit/67b429fb1f10695dcf73f90790962c9a9da56ed8#commitcomment-10021341>
> .
>
> _______________________________________________
> System Administrator, RIT Computer Science Community
> Admin@csc.cs.rit.edu
>
>


@hybrisCole mae póngalos en el folder sloths porfa


This class shouldn't implement the CartService. Is this a service class? if it's so, where is the Cart Model class?


:+1: Thanks!


What's wrong with this file ? It is intentionally an invalid formatted XML file used in a negative unit test.


Done
isTestUrlEnabled = Boolean.parseBoolean(canvasProperties.getProperty(SectionUtilityToolFilter.PROPERTY_TEST_URL,FALSE));


Grammar NAZI!!


@cweiske Just btw, this broke multiple deployments for us as well. I don't think we should force push ever to master. ;)


I think we want the RTL stuff here.


@Lotto2 What's the url? :-)


Quando iterando sobre um dicionário é recomendado usar hasOwnProperty para checar que a propriedade é de fato do objeto e não do dicionário
```js
if (questions.hasOwnPropery(question)) {/*...*/}
```


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1140 of 1140 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


I'm not really using re-frame, I just happened to had almost identical architecture in some app and after dropping core.async in this actual point I didn't notice any downsides - and stack traces became much easier to understand, obviously.


only a cosmetic change I assume?


we are using lo01 elsewhere in this doc. this has l01. @openstaxalina let's discuss today if this is potentially a big source of error for the xml team.
<item class="ost-learning-objective-def ost-tag-lo-k12phys-ch04-s01-l01 ost-tag-teks-112-39-c-4c">


yes


True.  For that matter, the point release number should also be moved to a define so that it can be accessed too and update automatically as well.


The parameter for the add operation is the user object, or just the Id?


we can use the \copydetails doxygen command, but it will probably not work once we add code examples. It would copy the C examples to the C++ function. Also i think when I tried that it copied the parameters with it.


contrib/cell_star/yaml looks like it's taken from pyyaml (https://dxr.mozilla.org/comm-central/source/mozilla/python/pyyaml is one place where this code appears). Also, the Cython for it is missing. (see https://github.com/sstoma/CellProfiler/blob/b25e7be4cb461be33cebbc05435e82bbbc3741a6/contrib/cell_star/yaml/cyaml.py#L5 for instance), so I'm wondering if this is dead code or at least that it doesn't work without pyyaml installed.
We could consider adding pyyaml to CellProfiler's dependencies or possibly move to json as a text format for serializing the parameters, even though that means you would lose the validation that a grammar provides.


Why you pass the user object as a paramater?


Очень странный метод. А Dispose? Процесс реально продолжиться? Непонятно когда будет прибран. У Ai в методе dispose вызвается process.StandardInput.Close();. Там есть ожидание и логирование.


Not if the socket path and the message template are configurable.


Why you pass the whole Item object as a parameter?


That's maybe like your opinion, man :)

I did the force push because it reduced the size of this repository from 20MiB to < 500 kiB. This was worth it IMO.


thank you ;)


I considered it multiple times, but not worth it as it's highly specific to my use-case and can even be simplified by using a new flag to get a JSON of the tasks. Why do you think it would be handy for other apps? What kind of apps?


So what happens if you do `fromJSString` on an `undefined`? Shouldn't you get  a `Maybe`?


jRuby gets included in Apraxis framework's project.clj and thus gets included as a transitive dependency that bootstraps itself if necessary on first use.


Any reason why you did not simply overloaded `emit`? ie `emit(int, bool)`? it does not seem the `enableFeedback` has something specific to feedback enabling, right?


These changes look helpful. Is there a pull request to fix the primary project?


Try:
```
rails c
ScreeningList.importers
```


I've added TODO and removed uneeded tests please check now.


Looks helpful! Have you considered a pull request for the main project so that the correct name is automatically used for 2.6?


I think the patch is fine. But the commit message is misleading. convertTo returns a precise Decimal quantity (not a floating point number), which is then converted to a str. I guess that lvm then interprets that values as a floating point, but that is not what it gets from blivet.

How about making commit message:

"Allow passing fractional MiB values to vgcreate -s option."


Thank you.  Unfortunately, I wont be able to make any build until Monday at least.  Once I get a chance to test the code, I will start merging branches.


Yes, during `check_binop` I `check_expr` both LHS and RHS at the beginning. If I follow the route of overloaded binop then I have to type check the arguments (just the RHS), that ends up calling `check_expr` on the RHS twice which leads to unfulfilled `Copy`/`Sized` obligations - so instead of checking twice I just run the unifier. I will add a comment in th code.


Don't need to go to the effort of changing it now, but I think we shouldn't worry about sticking to 80 chars - 100 or 120 seems fine to me (in this case it would only be 89 chars). The flake8 config has the line length check disabled.


I’m unsure about this. The alternative is to use wrapping arithmetic and keep the explicit overflow check like before.


Hej

/Erik

On Mar 4, 2015, 13:08, at 13:08, Andreas <notifications@github.com> wrote:
>Nice pattern!
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/nansen/pugpig-connector/commit/618717db455938d9fa67d272da889962755cc536#commitcomment-10028034


@ChronoMonochrome
can u pls show me how to change that thing with SW / HW Decoder ? Incl. Charger plug/unplugged..


the pad leaks here. Please use a GRefPtr


Hi Árni, I'd like to merge this if that's agreeable. Feel free to rebase/squash/PR and I'll get onto merging it, or I'll have a go myself if I have the time soon. Cheers!


removing the Promise.resolve on the remote API call seems to work with the Promise map.  If it's unnecessary, can we remove it from other places in the engine API code? (I just assumed the Promise.resolve was necessary to let the promise library know the local callback was done).


develop (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1137 of 1137 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


Line is too long. [104/100]


Align the parameters of a method call if they span more than one line.


Looks good, thanks.


ここバグってる気がする


충돌 사항 수정


Hum... it's hidden in inspector ok, but it's used to lines bellow. Why don't we just use theToggle.interactable directly?


1: M111 unrecognized component name: docextract


1: D400 First line should end with '.', not 'd'
1: D205 Blank line missing between one-line summary and description
2: L102 copyright year is outdated, expected 2015 but got 2014
23:1: E402 module level import not at top of file
24:1: E402 module level import not at top of file
25:1: I101 Imported names are in the wrong order. Should be CFG_CERN_SITE, CFG_SITE_LANG, CFG_SITE_URL
25:1: I201 Missing newline before sections or imports.
25:1: E402 module level import not at top of file
26:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
28:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.utils.url
28:1: E402 module level import not at top of file
31:25: E126 continuation line over-indented for hanging indent
33:1: E302 expected 2 blank lines, found 1
33: D290 White spaces around docstring should be trimmed.
33: D203 Expected 1 blank line *before* class docstring, found 0
33: D400 First line should end with '.', not 's'
36: D400 First line should end with '.', not 'e'
36: D208 Docstring is over-indented
36: D200 One-line docstring should not occupy 3 lines
47: D209 Put multi-line docstring closing quotes on separate line
47: D400 First line should end with '.', not 'l'
47: D205 Blank line missing between one-line summary and description
47: D208 Docstring is over-indented
50:9: F841 local variable '_' is assigned to but never used
55: D401 First line should be imperative: 'Draw', not 'Draws'
55: D400 First line should end with '.', not 'r'
55: D205 Blank line missing between one-line summary and description
55: D208 Docstring is over-indented
73:5: E303 too many blank lines (2)
73: D401 First line should be imperative: 'Draw', not 'Draws'
73: D400 First line should end with '.', not 'r'
73: D205 Blank line missing between one-line summary and description
73: D208 Docstring is over-indented
87: D401 First line should be imperative: 'Draw', not 'Draws'
87: D400 First line should end with '.', not 'r'
87: D205 Blank line missing between one-line summary and description
87: D208 Docstring is over-indented
99: D209 Put multi-line docstring closing quotes on separate line
99: D400 First line should end with '.', not 'l'
99: D205 Blank line missing between one-line summary and description
99: D208 Docstring is over-indented
112: D102 Docstring missing
127: D401 First line should be imperative: 'Draw', not 'Draws'
127: D400 First line should end with '.', not 'x'
127: D205 Blank line missing between one-line summary and description
127: D208 Docstring is over-indented
146: D401 First line should be imperative: 'Draw', not 'Draws'
146: D400 First line should end with '.', not 'x'
146: D205 Blank line missing between one-line summary and description
146: D208 Docstring is over-indented
164: D401 First line should be imperative: 'Draw', not 'Draws'
164: D400 First line should end with '.', not 's'
164: D205 Blank line missing between one-line summary and description
164: D208 Docstring is over-indented
197: D401 First line should be imperative: 'Draw', not 'Draws'
197: D400 First line should end with '.', not 't'
197: D205 Blank line missing between one-line summary and description
197: D208 Docstring is over-indented
241:79: E502 the backslash is redundant between brackets
242:74: E502 the backslash is redundant between brackets
245:95: E502 the backslash is redundant between brackets
246:86: E502 the backslash is redundant between brackets
247:87: E502 the backslash is redundant between brackets
254:5: E303 too many blank lines (2)
254: D401 First line should be imperative: 'Draw', not 'Draws'
254: D209 Put multi-line docstring closing quotes on separate line
254: D400 First line should end with '.', not 'x'
254: D205 Blank line missing between one-line summary and description
254: D208 Docstring is over-indented
259:9: F841 local variable '_' is assigned to but never used
268:42: E261 at least two spaces before inline comment
268:43: E262 inline comment should start with '# '
272:31: F841 local variable 'e' is assigned to but never used
280: D401 First line should be imperative: 'Return', not 'Returns'
280: D400 First line should end with '.', not ':'
280: D205 Blank line missing between one-line summary and description
289:9: F841 local variable '_' is assigned to but never used
294:18: E225 missing whitespace around operator
296:18: E127 continuation line over-indented for visual indent
299: D401 First line should be imperative: 'Output', not 'Outputs'
299: D400 First line should end with '.', not 'o'
306: D401 First line should be imperative: 'Output', not 'Outputs'
306: D400 First line should end with '.', not 'o'
313: D401 First line should be imperative: 'Output', not 'Outputs'
313: D400 First line should end with '.', not 's'
315:9: F841 local variable '_' is assigned to but never used
322: D401 First line should be imperative: 'Print', not 'Prints'
322: D209 Put multi-line docstring closing quotes on separate line
322: D400 First line should end with '.', not 't'
322: D205 Blank line missing between one-line summary and description
322: D208 Docstring is over-indented
336: D401 First line should be imperative: 'Print', not 'Prints'
336: D400 First line should end with '.', not 'e'
338:9: F841 local variable '_' is assigned to but never used
343: D102 Docstring missing
347: D400 First line should end with '.', not 'n'
360:15: E221 multiple spaces before operator
377: D401 First line should be imperative: 'Print', not 'Prints'
377: D400 First line should end with '.', not ','
377: D205 Blank line missing between one-line summary and description
406: D102 Docstring missing
408:22: E711 comparison to None should be 'if cond is not None:'
415: D102 Docstring missing
418: D102 Docstring missing
424:21: E711 comparison to None should be 'if cond is not None:'
429: D102 Docstring missing
435:21: E711 comparison to None should be 'if cond is not None:'
440: D102 Docstring missing
443: D102 Docstring missing
446: D400 First line should end with '.', not 'y'
449:65: E502 the backslash is redundant between brackets
451:46: E231 missing whitespace after ':'
457:34: E127 continuation line over-indented for visual indent
459: D102 Docstring missing
467: D102 Docstring missing
471: D102 Docstring missing
474: D102 Docstring missing
477: D102 Docstring missing
483: D102 Docstring missing
489: D401 First line should be imperative: 'construct', not 'constructs'
489: D400 First line should end with '.', not 'r'
492:26: E711 comparison to None should be 'if cond is None:'
508:68: E502 the backslash is redundant between brackets
510:49: E231 missing whitespace after ':'
515:68: E502 the backslash is redundant between brackets
517:49: E231 missing whitespace after ':'
527: D102 Docstring missing
534: D401 First line should be imperative: 'Write', not 'Writes'
534: D400 First line should end with '.', not 's'
578: D401 First line should be imperative: 'Create', not 'Creates'
578: D205 Blank line missing between one-line summary and description
603: D102 Docstring missing
607: D400 First line should end with '.', not 'u'
607: D208 Docstring is over-indented
607: D200 One-line docstring should not occupy 3 lines
620:70: E502 the backslash is redundant between brackets
624:72: E502 the backslash is redundant between brackets
625:38: E128 continuation line under-indented for visual indent
626:38: E128 continuation line under-indented for visual indent
627:38: E128 continuation line under-indented for visual indent
628:70: E502 the backslash is redundant between brackets
632:70: E502 the backslash is redundant between brackets
636:73: E502 the backslash is redundant between brackets
641:63: E203 whitespace before ','
644:23: E711 comparison to None should be 'if cond is not None:'
646:23: E126 continuation line over-indented for hanging indent
654: D401 First line should be imperative: 'Convert', not 'Converts'
654: D400 First line should end with '.', not 's'
654: D205 Blank line missing between one-line summary and description
665: D401 First line should be imperative: 'format', not 'formats'
665: D400 First line should end with '.', not 't'
665: D205 Blank line missing between one-line summary and description
671:17: E711 comparison to None should be 'if cond is None:'
675: D102 Docstring missing
676:17: E711 comparison to None should be 'if cond is None:'
680: D102 Docstring missing
681:25: E711 comparison to None should be 'if cond is None:'
684:16: E127 continuation line over-indented for visual indent
685:16: E127 continuation line over-indented for visual indent
687: D102 Docstring missing
698: D400 First line should end with '.', not 'w'
698: D205 Blank line missing between one-line summary and description
698: D208 Docstring is over-indented
710:21: E126 continuation line over-indented for hanging indent
711:28: E203 whitespace before ':'
712:17: E121 continuation line under-indented for hanging indent
725:22: E203 whitespace before ':'
726:28: E203 whitespace before ':'
727:8: E122 continuation line missing indentation or outdented
729: D400 First line should end with '.', not 'e'
729: D205 Blank line missing between one-line summary and description
750:16: E713 test for membership should be 'not in'


2: L101 copyright is missing


3: L102 copyright year is outdated, expected 2015 but got 2014


3: L102 copyright year is outdated, expected 2015 but got 2011


1: D100 Docstring missing
4: L102 copyright year is outdated, expected 2015 but got 2013
26:1: I100 Imports statements are in the wrong order. from invenio.legacy.docextract.text should be before from invenio.legacy.refextract.kbs
45: D103 Docstring missing
57: D103 Docstring missing
66:1: E302 expected 2 blank lines, found 1
66: D103 Docstring missing
74: D103 Docstring missing
78: D400 First line should end with '.', not 'e'
101: D400 First line should end with '.', not 'd'
101: D205 Blank line missing between one-line summary and description
101: D208 Docstring is over-indented
117: D103 Docstring missing
142: D400 First line should end with '.', not 'e'
142: D205 Blank line missing between one-line summary and description
142: D208 Docstring is over-indented


1: D100 Docstring missing
24: D103 Docstring missing


4: L102 copyright year is outdated, expected 2015 but got 2014
28:1: E402 module level import not at top of file
29:1: E402 module level import not at top of file
30:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
37:1: I100 Imports statements are in the wrong order. import cgi should be before import time
37:1: E402 module level import not at top of file
38:1: E402 module level import not at top of file
39:1: I100 Imports statements are in the wrong order. import binascii should be before import subprocess
39:1: E402 module level import not at top of file
40:1: I100 Imports statements are in the wrong order. import StringIO should be before import binascii
40:1: E402 module level import not at top of file
42:1: E402 module level import not at top of file
43:1: I100 Imports statements are in the wrong order. from functools should be before from flask
43:1: I201 Missing newline before sections or imports.
43:1: E402 module level import not at top of file
44:1: E402 module level import not at top of file
45:1: I201 Missing newline before sections or imports.
45:1: E402 module level import not at top of file
46:1: E402 module level import not at top of file
47:1: I100 Imports statements are in the wrong order. from urllib should be before from six.moves.urllib.parse
47:1: I201 Missing newline before sections or imports.
47:1: E402 module level import not at top of file
48:1: I100 Imports statements are in the wrong order. from itertools should be before from urllib
48:1: E402 module level import not at top of file
49:1: E402 module level import not at top of file
133:1: E402 module level import not at top of file
136:1: F401 'pyparsing' imported but unused
136:1: E402 module level import not at top of file
137:1: I100 Imports statements are in the wrong order. from flask.ext.testing should be before import pyparsing
137:1: I201 Missing newline before sections or imports.
137:1: E402 module level import not at top of file
215: D101 Docstring missing
216: D102 Docstring missing
251:5: E731 do not assign a lambda expression, use a def
371:5: B901 blind except: statement
792:9: B901 blind except: statement
813:9: B901 blind except: statement
837:9: B901 blind except: statement
869:9: B901 blind except: statement
880:13: B901 blind except: statement
903:9: B901 blind except: statement
924:9: B901 blind except: statement
941:9: B901 blind except: statement
1191:9: B901 blind except: statement


1: D200 One-line docstring should not occupy 3 lines
2: L102 copyright year is outdated, expected 2015 but got 2013
28:1: E402 module level import not at top of file
29:1: E402 module level import not at top of file
30:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
32:1: I100 Imports statements are in the wrong order. import cgi should be before import unittest
32:1: E402 module level import not at top of file
33:1: E402 module level import not at top of file
35:1: E402 module level import not at top of file
36:1: I100 Imports statements are in the wrong order. from functools should be before from warnings
36:1: E402 module level import not at top of file
37:1: E402 module level import not at top of file
38:1: I100 Imports statements are in the wrong order. from urllib should be before from urlparse
38:1: E402 module level import not at top of file
39:1: I100 Imports statements are in the wrong order. from itertools should be before from urllib
39:1: E402 module level import not at top of file
48:1: I101 Imported names are in the wrong order. Should be CFG_BASE_URL, CFG_JSTESTDRIVER_PORT, CFG_LOGDIR, CFG_PREFIX, CFG_PYLIBDIR, CFG_SITE_NAME_INTL, CFG_SITE_SECURE_URL, CFG_SITE_URL, CFG_WEBDIR
48:1: E402 module level import not at top of file
57:1: I101 Imported names are in the wrong order. Should be CFG_TESTS_REQUIRE_HTML_VALIDATION, w3c_errors_to_str, w3c_validate
57:1: E402 module level import not at top of file
58:36: E128 continuation line under-indented for visual indent
59:36: E128 continuation line under-indented for visual indent
69:1: E302 expected 2 blank lines, found 1
70: D202 No blank lines allowed *after* function docstring, found 1
70: D400 First line should end with '.', not 'y'
70: D205 Blank line missing between one-line summary and description
126:1: E302 expected 2 blank lines, found 1
127: D290 White spaces around docstring should be trimmed.
127: D400 First line should end with '.', not 's'
132:1: E302 expected 2 blank lines, found 1
133: D400 First line should end with '.', not 'e'
133: D205 Blank line missing between one-line summary and description
143:1: E302 expected 2 blank lines, found 1
143: D290 White spaces around docstring should be trimmed.
143: D209 Put multi-line docstring closing quotes on separate line
143: D202 No blank lines allowed *after* function docstring, found 1
143: D400 First line should end with '.', not 'y'
143: D205 Blank line missing between one-line summary and description
154:1: E302 expected 2 blank lines, found 1
154: D290 White spaces around docstring should be trimmed.
154: D209 Put multi-line docstring closing quotes on separate line
154: D202 No blank lines allowed *after* function docstring, found 1
154: D400 First line should end with '.', not 'y'
154: D205 Blank line missing between one-line summary and description
165:1: E302 expected 2 blank lines, found 1
165: D290 White spaces around docstring should be trimmed.
165: D209 Put multi-line docstring closing quotes on separate line
165: D202 No blank lines allowed *after* function docstring, found 1
165: D400 First line should end with '.', not 'y'
165: D205 Blank line missing between one-line summary and description
176:1: E302 expected 2 blank lines, found 1
176: D203 Expected 1 blank line *before* class docstring, found 0
176: D204 Expected 1 blank line *after* class docstring, found 0
180:1: E302 expected 2 blank lines, found 1
181: D205 Blank line missing between one-line summary and description
190:5: B901 blind except: statement
194:1: E302 expected 2 blank lines, found 1
194: D400 First line should end with '.', not 'd'
194: D205 Blank line missing between one-line summary and description
204:37: E261 at least two spaces before inline comment
219:1: E302 expected 2 blank lines, found 1
220: D400 First line should end with '.', not 's'
220: D205 Blank line missing between one-line summary and description
220: D208 Docstring is over-indented
272:55: W602 deprecated form of raising exception
273:23: E126 continuation line over-indented for hanging indent
289:55: W602 deprecated form of raising exception
290:23: E127 continuation line over-indented for visual indent
299:20: E126 continuation line over-indented for hanging indent
304:20: E127 continuation line over-indented for visual indent
319:59: W602 deprecated form of raising exception
320:27: E126 continuation line over-indented for hanging indent
328:35: E126 continuation line over-indented for hanging indent
330:55: W602 deprecated form of raising exception
333:5: E303 too many blank lines (2)
334:80: E502 the backslash is redundant between brackets
337:82: E502 the backslash is redundant between brackets
356:1: E302 expected 2 blank lines, found 1
356: D400 First line should end with '.', not 'y'
356: D205 Blank line missing between one-line summary and description
356: D208 Docstring is over-indented
366:1: E302 expected 2 blank lines, found 1
367: D202 No blank lines allowed *after* function docstring, found 1
367: D400 First line should end with '.', not 'd'
367: D205 Blank line missing between one-line summary and description
390:1: E302 expected 2 blank lines, found 1
391: D400 First line should end with '.', not 'h'
391: D205 Blank line missing between one-line summary and description
397: D400 First line should end with '.', not 'd'
397: D200 One-line docstring should not occupy 3 lines
418: D400 First line should end with '.', not 'n'
418: D205 Blank line missing between one-line summary and description
432:145: E502 the backslash is redundant between brackets
442:9: E128 continuation line under-indented for visual indent
464:1: E302 expected 2 blank lines, found 1
465: D202 No blank lines allowed *after* function docstring, found 1
465: D400 First line should end with '.', not 'y'
465: D205 Blank line missing between one-line summary and description
490:1: E302 expected 2 blank lines, found 1
491: D202 No blank lines allowed *after* function docstring, found 1
491: D400 First line should end with '.', not 'y'
491: D205 Blank line missing between one-line summary and description
517: D203 Expected 1 blank line *before* class docstring, found 0
517: D204 Expected 1 blank line *after* class docstring, found 0
517: D300 Expected """-quotes, got '-quotes
528: D290 White spaces around docstring should be trimmed.
528: D203 Expected 1 blank line *before* class docstring, found 0
528: D400 First line should end with '.', not 's'
528: D205 Blank line missing between one-line summary and description
533: D202 No blank lines allowed *after* method docstring, found 1
536:9: E266 too many leading '#' for block comment
547: D202 No blank lines allowed *after* method docstring, found 1
553: D290 White spaces around docstring should be trimmed.
553: D202 No blank lines allowed *after* method docstring, found 1
553: D400 First line should end with '.', not 's'
553: D205 Blank line missing between one-line summary and description
566:9: B901 blind except: statement
569: D290 White spaces around docstring should be trimmed.
569: D202 No blank lines allowed *after* method docstring, found 1
569: D400 First line should end with '.', not 's'
569: D205 Blank line missing between one-line summary and description
582:9: B901 blind except: statement
585: D290 White spaces around docstring should be trimmed.
585: D202 No blank lines allowed *after* method docstring, found 1
585: D400 First line should end with '.', not 's'
585: D205 Blank line missing between one-line summary and description
598:9: B901 blind except: statement
601: D290 White spaces around docstring should be trimmed.
601: D202 No blank lines allowed *after* method docstring, found 1
601: D400 First line should end with '.', not 's'
601: D205 Blank line missing between one-line summary and description
622:9: B901 blind except: statement
629:123: E225 missing whitespace around operator
630:13: B901 blind except: statement
637: D290 White spaces around docstring should be trimmed.
637: D202 No blank lines allowed *after* method docstring, found 1
637: D400 First line should end with '.', not 's'
637: D205 Blank line missing between one-line summary and description
650:9: B901 blind except: statement
653: D290 White spaces around docstring should be trimmed.
653: D202 No blank lines allowed *after* method docstring, found 1
653: D400 First line should end with '.', not 's'
653: D205 Blank line missing between one-line summary and description
666:9: B901 blind except: statement
669: D290 White spaces around docstring should be trimmed.
669: D202 No blank lines allowed *after* method docstring, found 1
669: D400 First line should end with '.', not 's'
669: D205 Blank line missing between one-line summary and description
682:9: B901 blind except: statement
685: D290 White spaces around docstring should be trimmed.
685: D202 No blank lines allowed *after* method docstring, found 1
685: D400 First line should end with '.', not 's'
685: D205 Blank line missing between one-line summary and description
697:9: B901 blind except: statement
700: D290 White spaces around docstring should be trimmed.
700: D400 First line should end with '.', not 'd'
700: D205 Blank line missing between one-line summary and description
710:9: B901 blind except: statement
713: D290 White spaces around docstring should be trimmed.
713: D400 First line should end with '.', not 'd'
713: D205 Blank line missing between one-line summary and description
723:9: B901 blind except: statement
726: D290 White spaces around docstring should be trimmed.
726: D400 First line should end with '.', not 'n'
726: D205 Blank line missing between one-line summary and description
741:16: E713 test for membership should be 'not in'
765: D290 White spaces around docstring should be trimmed.
765: D202 No blank lines allowed *after* method docstring, found 1
765: D400 First line should end with '.', not 'n'
765: D200 One-line docstring should not occupy 2 lines
773:66: E502 the backslash is redundant between brackets
773: D290 White spaces around docstring should be trimmed.
773: D202 No blank lines allowed *after* method docstring, found 1
773: D400 First line should end with '.', not 'n'
773: D205 Blank line missing between one-line summary and description
823: D290 White spaces around docstring should be trimmed.
823: D202 No blank lines allowed *after* method docstring, found 1
823: D400 First line should end with '.', not 's'
823: D205 Blank line missing between one-line summary and description
861: D290 White spaces around docstring should be trimmed.
861: D202 No blank lines allowed *after* method docstring, found 1
861: D400 First line should end with '.', not 'n'
861: D205 Blank line missing between one-line summary and description
887: D290 White spaces around docstring should be trimmed.
887: D202 No blank lines allowed *after* method docstring, found 1
887: D400 First line should end with '.', not 'n'
887: D205 Blank line missing between one-line summary and description
910: D290 White spaces around docstring should be trimmed.
910: D202 No blank lines allowed *after* method docstring, found 1
910: D400 First line should end with '.', not 'n'
910: D205 Blank line missing between one-line summary and description
936: D290 White spaces around docstring should be trimmed.
936: D202 No blank lines allowed *after* method docstring, found 1
936: D400 First line should end with '.', not 't'
936: D205 Blank line missing between one-line summary and description
957: D290 White spaces around docstring should be trimmed.
957: D209 Put multi-line docstring closing quotes on separate line
957: D202 No blank lines allowed *after* method docstring, found 1
957: D400 First line should end with '.', not 'n'
957: D205 Blank line missing between one-line summary and description
964:9: B901 blind except: statement
968: D203 Expected 1 blank line *before* class docstring, found 0
968: D400 First line should end with '.', not 't'
968: D205 Blank line missing between one-line summary and description
995: D103 Docstring missing
1003: D401 First line should be imperative: 'Make', not 'Makes'
1003: D400 First line should end with '.', not 'r'


86:40: E128 continuation line under-indented for visual indent


199:1: E303 too many blank lines (3)


If they always exist, shouldn't this be caught earlier? I.e. why is this method ever called for a variable that is found?


No, but I can make one right now :)


No need for a PR, I am going to fix this.

Too many releases to test them all (13+dev). I don't think it's possible to do that in parallel, and to test just one already takes 8-10 minutes.


Alrighty.


Das kommt dabei raus wenn man seine Änderungen einer anderen repo aus dem Kopf heraus in den fork schreibt :D


WHAT?!


Hi Guys,

I don't get anything in the .cpp part, but if you can let me know what the dimensions of the resulting R object output is I can at least write the posterior summary and MCMC diagnostic part


This commit is excellent! Though I'm pretty sure I did terrible things in a few places in GregorioTeX code, such as relying on \gretempdim value totally outside the scope of where it was set... I'm quite sure I did that at least in one place...


Oh nooooooo! I hate you now ;)


@l3pp4rd thx for reply
I am working currently to fix my project after this commit
are you sure that new entity created in onFlush event will get onCreate datetime set? I am receiving plenty of nulls in entities created onFlush event...


A promise is resolved by either returning another promise, or a value (any value, even null/undefined). In this case, we're returning nothing (null/undefined), which resolves the promise for us. We can return nothing because we don't care about the eventual value. Promise.resolve() as you have it, is just creating a new promise, which resolves (essentially, returns) to no value (essentially null/undefined). So you are creating an extra promise that is not needed when using it.


わかりました。
リファレンスも拝見しました、ありがとうございます！


Don't know why Win does this. But looking at that link, I don't have these options, my reg doesn't have disable thumbnail cache. (Win 7) thanks for removing, I hate that garbage too


What about env param composer options?


Wow I didn't know that you could do that.


Sure


"temp"

![](http://www.reactiongifs.com/r/gger.gif)


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (632 of 632 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-4.06%25-green.svg)


That's enormous! :D But after fast scanning it looks nice ;)


Often what I do in these situations is to use numpy.random.RandomState seeded with some of the image data. For instance, rand_seeds could take a RandomState as an input (or it could use the Seeder's random state if not static) and the random state could be seeded using the snake's points or a hash of the images (for example, sum(map(numpy.sum, images)). The seeder will use the same randomizer each time it is called with the same images, but will use different randomizers on different images.
If you need multiple different seedings per image, perhaps the seeder should take a RandomState as a parameter and the module should create a random state at its outset using the images being processed.


Why dont put the normalized path directly here ? To avoid duplication


Hi **uriel-frankel**,

Currently it must work as follows: when user touches the button and makes the swype gesture without taking the finger - button must remain in **PRESSED** state. If the user then takes the finger - button must change its state to **NORMAL**

If the actual behavior differs from the above please give me the API version and describe the actual behavior

Thank you


I won't setup maven only for one jar that I'm probably going to drop anyway

On Wed, Mar 4, 2015, 07:45 Louis Dion-Marcil <notifications@github.com>
wrote:

> You should setup maven for proper build requirements instead of using
> precompiled jars.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ldionmarcil/blindr/commit/befaccfc24be339d78b2212fb40d63cd3e4f1729#commitcomment-10028587>
> .
>


I am not 100% sure if you are really correcting or changing something. From my understanding, commit 4de2e8a0 says,
```Markdown
Add support the more recent syslog protocol **and make it default**.
[...]
Protocols are meaningful only when messages are sent to remote syslog
server.
```
For me it seems like you are judging from the last sentence that RFC5424 should only be default for remote logging.

Another fix based on another interpretion:
Make `logger` without `-u` option use RFC5424 per default like `logger -u /dev/log`. That's what I read from the original commit message.

In other words: The problem is, that `logger` don't use RFC5424 format everywhere per default like it should do.


So I had to add 'nickname' to this model - it's your github username and we need it for the github api. Ember might want to display it as well.


First of all, sorry for misusing the comments to get in contact with you. Google revealed that there was a repo "samsieber/bodyweight-skill-tree". If it contained what I would expect from the name, I would like to share some thought on this topic with you. Was there already something committed?


:8ball:

I just learned emoji. Thanks for cleaning up this garbage.


Doh, copy & paste error, sorry about that!


Esses métodos deveriam retornar algo. Chamar um método que vai alterar um parâmetro que eu passei deixa a API meio confusa, e costuma ser considerado má prática também.

Ao invés de
doStuff(x) //mudando o valor de x

Faça
x = doStuff(x)


@Gama11 i haven't tested it actually. but will continue investigations in this direction


Oh wait - I now see you did this in a subsequent commit. Cool. :camel:


Shouldn't this say "same as visual cp"?


This sounds pretty good, but I was kind of wondering what sort of information we would want to avoid having in templates? or this is just in case?
If it is a string that we don't want to be rendering in templates, does it make sense to have an array of strings that we don't want in templates?


:thought_balloon:
Acho que eu chamaria de PontuacaoResolver


I think we don't need integrated tests. And if yes, just one.

If you look at test suite for domite, there are only unit tests. SUnit is unit test framework.

If some interplay causes bugs, more "integrated tests" won't probbaly catch it either, if the one with all things tested before did not catch. Only use in the wild catches it - in which case the regression test should be added, but minimal again.


nice, could we cherry-pick to `release-14.12`?


Shouldn't this be "same as visual bh"?


develop (Myoldmopar) - i386-Windows-7-VisualStudio-12: OK (1140 of 1140 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


Ок, поставила класс.


Сделала список.


Could we use `highlightjs-theme` to be consistent with asciidoctor-backends? https://github.com/asciidoctor/asciidoctor-backends/search?utf8=%E2%9C%93&q=highlightjs-theme


Damn, that is one heck of a bug fix!


Actually, when I think about this... I added compilation of tools (they use go so they were missing), but I also removed all of the debian package stuff... I don't know who much you like the stuff I removed ...


Stop, and the reaper structs it uses, looks to only exist within kubectl.

I'm also not sure using stop will solve the problem.  The problem I've seen is that the replication controller is removed and there are no pods from this test known to kubernetes, but there are still pods running from the test on hosts and they never die.   That should never happen.  I logged issue #5020 about this problem


This seems to be the wrong commit. I'm guessing someone force-pushed and the actual commit should be 93199d837a493fe2b6f7e5d4186d271ae3eae08e


Not sure about the impact on other uses of `nxdrive_home`: `os.mkdir(self.nxdrive_home)` and callers of `get_configuration_folder()`, for ex the `PidLockFile` constructor, as these don't complain about non normalized path under WIndows, they might complain if we normalize it.


Why?


Сделала обертку. Размеры будут в css. 100%


:+1: Curious how this will impact Ruby version managers, if at all.


=D


still need to verify if ip address has changed.


add ";" to stream_url so that /web and CC can access them


Done. Given a new label and used the label to break out


given that this method is now in the `PublishingApi` module, do you think that it still needs this longer name? Perhaps `content_item_for_base_path` would be sufficient given the context.


'rtl' should be 'ltr'. Yay 9:30!...


Travis,
This all looks great to me. I originally thought we would just have a 'users' serializer and get at commits and goals thought the associations... but this looks cool too. I'll need to look at the ember side next.

2 things we will need to add at some point:
1) a create method on the goals api, so the user cna enter goals in ember and get them into our db
2) tests :telescope:


> I can't quite tell what the is_builtin_binop will do in that case, but I suspect return false

Yes, it returns false for any op. And that case will likely go through the overloaded op/trait dispatch route.

> regardless it is not valid to be doing if-style testing on things that are not yet inferred.

IIRC, asking for fully resolved types at this point breaks type cheking of some (valid) expressions (I'll fetch some examples). And to know if this is a built-in operation we need to know at least the "category" of *both* LHS and RHS - so we need some type information on both sides.


``---`` 必须比标题要长，否则标题的格式化就会出现问题。


may be re installing windows and it left from XP ?
in W7 it on the one file
%userprofile%\AppData\Local\IconCache.db


les coms en HTML s'écrivent <!-- commentaire -->, c'est en PHP qu'on a des //comm [return] et des /*Comm*/


I think your current way of returning data is already good.


Yes.

You can create a pull request in atom-shell which will have a better interface for code review.


Just wanted to volunteer the effort since you seem awfully busy.

Hmm, fair enough, but maybe one or two past releases would make sense? Point was mostly that automatic testing should've caught something like this, rather than you having to go over each PR with a fine toothed comb looking for possible regressions.


I'll do that.


а что делает эта штука? зачем отправлять данные валидации для нового коммента?


hmmm... why would we get rid of the goals/new route? I think we need that for the add goals form?


@ace2nutzer, did youmean this https://github.com/ChronoMonochrome/Chrono_Kernel/commit/d07fd891886df15d079edaeeaafc59ba3f9a1c54 ?
P.s. after some testing it turned out that even this fix didn't help. Probably connected charger messes GPU stability and it produces bug above (like after overclocking to some unstable freq). But I can live with it. As I said, only HW decoder affected to this, so I change it to SW and everything is ok then.


We'll need to do more investigation on this, preferably within container environments at first but:

- All Ruby invocations are done through JRuby embed rather than commandline invocation (https://github.com/jruby/jruby/wiki/RedBridge)
- Bootstrapping sets GEM_HOME to target under the Apraxis project in question so it should not pollute a local JRuby install with the bundler install it does. (https://github.com/apraxis/apraxis/blob/master/src/apraxis/util/jruby.clj#L58)
- The bundle path is explicitly set to vendor all middleman gems into target under the project so that they will also not clobber the ruby env (https://github.com/apraxis/apraxis/blob/master/src/apraxis/util/jruby.clj#L86)


Thanks, I see your point now but I think the code is not affected cause the type promotion (and sign extension) is done after computing the result of

(mpaData[i] << 8 ) | mpaData[i + 1]

and the next line in the code

if ((syncBits & 0xFFF0) == 0xFFF0) {

discards the sign extension bits, isn´t it?


Please read this to write down better GIT commit messages: https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message


Shouldn't that be cultural localization for Roman cultures ?
What's with all the other lines changes in the diff ? Maybe different line endings ?


corrected in the next commit already


Changing in the next PR.


Also this entire domain of how we tie in Ruby for middleman is really important to get right and to think about carefully so that it doesn't end up a noose around Apraxis' neck so please do take the time to review what we're doing here and liberally criticize what we do.


hej hej min vän!


Good point. However,
1. Piping is more flexible because it launches a program. If you just write to a socket, there must already be a program listening on that socket.
2. You'd need an entirely new syntax for specifying the format/socket to be unambiguous to the reader.


@Mumfrey Do you want to fix it? Right now I can't checkout the latest version because of this


Maybe add the `kb_tenant_id` in the exception message.


They are not always set by the runtime. It is much more complicated to actually make them part of the tables with names to value mapping as it is not known if they will be set or not and variables are immutable. Therefor it is much easier to just not raise an error - it also happens to be implemented right next to where they get their nil value if not set and --strict_variables is not on (all variables are nil by default when --strict_variables is not on).

Does that explain the implementation decision?


To be honest there's no need for `SYMFONY_ENV` in the common recipe, as symfony apps would use the `symfony` recipe.

Alternatively, there could be an `env()` var for composer. e.g.:
```php
set('composer_env', 'SYMFONY_ENV={env}');
```


For performance, I would consider adding an index on `[:dependable_id, :dependable_type]` as well. The most common use case for this table will be "please give me a list of all the editions which depend on X", and that will require such an index.


@scotty0100 Here we go!
I adjusted the cell size, increasing the number of nodes and I added a new parameter to the system so zones like Searing Gorge should have a better nodes density.

Like the previous one, you have to run a fresh install to remove the previous fix (applying only that update file may result in a error message).

Due to the complaint in the feedback you posted (basically: "farming herbs is now meaningless"), I made this fix as quickly as I could: this is untested, so tweaks are probably needed (and will be done), but at least you should see an immediat improvement over the previous patch.

Any feedback on this will be appreciated. :)


Yes, sounds good.


And by "fully resolved" I mean calling `structurally_resolved` on both sides which errors if *one* of them is a tyvar. I guess you meant that we should error here if *both* lhs and rhs are tyvars.


Thanks @wluyima.  Sorry for missing this myself--Adam Yates had been trying to use Appt Scheduling with 1.10 without success, and I assume this was the problem.


Found a bug in the `version_ref` implementation which is now solved on master https://github.com/cloudfoundry-incubator/bosh-workspace/blob/master/lib/bosh/workspace/release.rb#L62-L66


[Praveen 3/4] Have Reverted Unwanted code, which was used for testing purpose


changed the flag to NDP_OPT_TLLAO_TYPE bacause the target link-layer address should be send (ICMPv6 Option field)


Would you be able to tell me which version of Zenoss you are currently using for this script? I have tried to follow your walkthrough/instructions to the letter and am getting a few syntax errors. The current version of Zenoss that I am on is 4.2.4. I can paste the syntax error that I am getting if this commit is acknowledged.

What I did instead was make a curlslack.sh bash script and used your curl command at the bottom of your python script as follows:

curl -X POST --data "payload={\"text\": \"*$1*\n*Action*\n <$2|Acknowledge>\n <$3|Close>\n <$4|View Device Events>\", \"channel\": \"#alerts\", \"username\": \"Zenoss-bot\"}" <WebHook>


по идеи это получение поля у объекта, в строку парсить тут не обязательно, можно в таких случаях @category.name просто писать :)


Could you update the generator too (https://github.com/killbill/killbill-plugin-framework-ruby/blob/master/generators/active_merchant/templates/spec/integration_spec.rb#L14)?


set correct header length


@sminnee yes, I think adding this as part of our style guide and encouraging people to adopt it and IDE plugins that support it would be a great idea.


It's `<textarea>value</textarea>`, but `<input value="value">`. Historic reasons, not much logic.


It is essential for the testing gitter integration purposes.


default_scope лучше не использовать, очень не явный метод, проще сделать обычный scope и явно вызывать


Just wanted to test if it worked, technology is amazing!

/Erik

On Mar 4, 2015, 15:35, at 15:35, Arnold Macauley <notifications@github.com> wrote:
>hej hej min vän!
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/nansen/pugpig-connector/commit/618717db455938d9fa67d272da889962755cc536#commitcomment-10030555


Добавям: #1


Tesssste de commit


@wluyima I believe we also want to add the scheduling app to the ref app home page, as well as the administrative features.   I believe everything necessary is defined in scheduling_app.json within the appointmentschedulingui module.


return res;


This test doesn't seem Stripe specific. We should put it in https://github.com/killbill/killbill-plugin-framework-ruby instead .


So no worries then :) as it turned out, ext3 wasn't reason for bootloop - it's just installing kernel on unsupported ROM (4.1.2 kyrillos).


Thanks a million!


It's OK to use parallelization in the GUI, for instance when computing the parameters, but during an analysis, the work is split up into one worker per CPU (and on a cluster, one per allocated node) and the assumption is that CellProfiler uses one CPU per image set. Parallelizing an algorithm that operates during an analysis breaks this assumption and will slow the analysis by creating NxN processes where N is the number of CPUs.

Alternatives are to operate on numpy arrays (for instance, compute euclidean distances from x1,y1 to x2,y2 using arrays of x1,y1 and x2,y2 rather than individual values) or moving algorithms to C, Cython or even Java using the Java bridge. Using numpy arrays is preferred.


Would be nice to extend the method docstring to include this "sorted by id" part of the specification.


Is this a leftover comment from before config was set for mailer?


If there's a reason scheduling_app.json isn't correctly adding the apps to the home page, it can probably be modified/fixed without worrying about breaking the PIH implementation as we do a custom configuration anyway.


@l3pp4rd: I have the same problem just like @Venzon. Sometimes i create entities inside onFlush event and all fields with annotation createdAt are omitted. It's because TimestampableListener.php is triggered before all my OnFlushListeners.


QwtUpdate (macumber) - Win64-Windows-7-VisualStudio-12: OK (2172 of 2201 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-warnings-yellow.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-98.68%25-yellow.svg)


No idea how or why it would work as intended, so I have adopted it as specified in RFC4861 and tested with linux host.


How does sample_mail_preview 'preview all emails' when it takes only User.first?


`@@gateway_name` is the name of the key in the `yml` file (e.g. `:stripe`). We want the plugin name instead (`killbill-stripe`).


changed the flag to NDP_OPT_TLLAO_TYPE bacause the target link-layer address should be send (ICMPv6 Option field)


@nfeske: please review above commit. I would like to integrate the regular remote resource check into the buildbot


Мда, смотрю сейчас сам и думаю "А правда, нафига?". Перетрудился :)
Сегодня исправлю.
Спасибо, что заметили и сообщили.


Calculate t statistic only


Properly speaking, this method doesn't show anything. Maybe get_subtree would be better.


Calculate t statistic only

Call result `permutationStatistics`


don't need this


use `mean(permutationStatistics > tstat)`


So we have a next webinar topic after the Swift one :P I'm refactoring.


In fact, yes, because int conversion is taking place just before the OR operation. For example, if you execute the following lines:

byte a=(byte)0x10;
byte b=(byte)0xf0;
int c = (a << 8) | b;

You would expect c to be 0x10f0, right? However, if you debug it you will see that c == 0xfffffff0, so false positive for your code.


This looks good to me.


Perfect :)


Hi Matt,

No worries. I learned a lot more about git in the process of figuring this out. I think this commit was probably the culprit, and not your merge, because rebasing without this seemed to fix everything. In my experience, git is usually pretty great about smartly merging conflicting changes, so that even if you merged based an older copy of the repo, git should understand that, say, version `ABC` with change `C->D`, when merged with version `BBC`, rightly becomes version `BBD`. The mysterious thing with this commit was that the diff above doesn't show all the changes, so my best guess is that it was pushed with a `--force` flag. That would also explain why the merge cruft above ended up in the commit, since git usually won't let unmerged files be committed. That having been said, any number of things probably could've happened, and it wasn't too difficult to straighten everything out, anyway.

I find all of this to be super interesting as an editorial workflow, and I think when this project is stable, it'd be really fun to all co-author a blog post about it. Collaboratively written on GitHub, of course!


develop (Myoldmopar) - Win64-Windows-7-VisualStudio-12: OK (1140 of 1140 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


@bors: retry
* #5142


Why not just <meta charset="UTF-8">? For compatibility with pre-HTML5?
http://www.w3schools.com/tags/att_meta_http_equiv.asp


why is it pipeline.Pipline? shouldnt it be deploydb.models.Pipeline?


Will cherry-pick it to `release-14.12` as soon as I've tested USB support properly.


Already done. Look at master.


Why pipeline.pipeline?


wefwefee


weferrferger


ergergverbgv


ergverbvrb


qfwefwe


saw approval from jdm
at https://github.com/Adenilson/servo/commit/463f03826fb2e5459f8ce4e438f10b0b553fc62d


merging Adenilson/servo/cleanupWarning02 = 463f0382 into auto


Adenilson/servo/cleanupWarning02 = 463f0382 merged ok, testing candidate = 761f7f05


wololo


Awesome :+1:


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"htttp://www.w3.org/TR/xhtml1/DTD/xhtml1-transtitional.dtd">
<xhtml xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

     <meta http-equiv="content-type"
     content="text/html; charset=utf-8" />
     <title>Welcome to this Page!</title>

This is a basic XHTML page!

Even with some decoration, it's still not very exciting.


This method name is not too informative what is a "sub"? There is no class or known object type with that name.
What is the method actually returning? Please pick a better name, such as "getMatchingSubCommandAliases".

Another suggestion could be to create two versions of this command. In the new one you would be able to specify the LEVENSHTEIN_MAX_DISTANCE as a method parameter.


Quite a long label, isn't it? :/
'Trainer Log' perhaps? (I'd really like 'Trainings Conducted' but way too long & I like the distinction of Trainer vs Trainings)
I know that i18n can easily make both longer anyway :/


Hmm, what was it putting in here?


Thanks, Jonathan! That's helpful, and I'm learning a lot through this process, too.

> and I think when this project is stable, it'd be really fun to all co-author a blog post about it. Collaboratively written on GitHub, of course!

Indeed! Our editorial team has been discussing this very possibility, though we've been thinking more along the lines of an article for Digital Humanities Quarterly. It would be fun to discuss a collaboration of this kind.


If I understand this, index = np.column_stack((py - .5).astype(int), (px - .5).astype(int)) which performs all operations using numpy.