It looks like this file was created by accident since /contact exists. Deleted in commit 414017405f87c1a932a996ed3b8cfbeff67f5201


Again, I'd just delete this but feel free to leave a comment explaining why we *don't* explicitly set the mesh dimension of the boundary mesh.


I tried using `IA32_sysenter_esp`. I printed `(_ESP & THREADINFO_MASK)` and `(env->sysenter_esp & THREADINFO_MASK)` side by side. The second value didn't change at all. It remained `c1396000`.

I added some printfs in `helper_wrmsr()` and `helper_rdmsr()` (inside `target-i386/op_helper.c`) but they weren't called during the replay.


xd anacondaqq =)
I just missed that do {} while() on top, don't be so mean.
But actually at flow level a tmp variable to break the do{} while(), should still be faster than 5 if at worst.
1 read + 1 cmp vs 5 cmp. But it's really doesn't matter much.

nb2 : I'm resetting my env again, both hdd broke and I lost everything that why I was *lazy*.


Awesome, although that's not quite what I thought friend would be.  I assumed friend would be per-element, not for the whole module.
Thanks, though.


括号可以去掉，直接写成Date.current.beginning_of_day


comment


Can you avoid these warnings by classifying `bcm_host.h` as a system header?


My OCD tells me to sort these ;-)


`customer` isn't needed twice, but I don't like it when methods modify their parameters' state without returning the object that was modified. When I'm looking at the code and trying to find everywhere that `customer` is modified it's not immediately obvious without looking at the method body that `customer` is passed to. With the reassignment it's obvious that those methods modify the `customer`.

The `customer.UpdateSomething(fromsource);` option would work. It's not obvious from this code snippet, but the viewmodels (variables with the VM suffix) belong to an assembly that depends on the assembly that houses the `Customer` object, so the VMs couldn't be passed directly to a method on the `Customer` object. We could use a DTO in the `Customer` assembly, or an extension method in the viewmodel assembly. I think the DTO route is probably more correct from an OO perspective, but the extension method would be easier and is probably what I would use irl.


Looks like access to splitInfo members was normally locked on .this, so do it here to


lol, sweet 7 years


这里可以抽取成一个方法，例如：visit_planning_page， 这样，代码看上去更易懂，也简洁


Overall: No "errors" apparent, mostly factoring opportunities, and may not even be appropriate given other possible project constraints.  The hard-coded values stick out as a point of fragility, though.


Oh and don't forget the period newline fix for the next release! ;)


Pérez Acosta Arturo (Directores)


I disagree—an FAQ should prioritize dispelling confusion over pedantic correctness. You may be technically correct (some say the best kind of correct) but I believe that the majority of people reading this Q&A would be software folks confused by seeing `v` prefixes in VCS but no mention of it in semantic versioning.

I wonder if this conversation moot, this repo hasn't gotten any attention in months.

:fire_engine:


でもこの状態でしたら付け加えたではなく１行目を消してそれを上書きしたってことになるから失敗でしょうか・・・。


do we have to worry at all about the `copyright` notice at the top of this file?


should B&N College be mentioned here somewhere or is that considered poor form?


这里应该可以简化，应该可以不用return，直接写 today_planning.first if today_planning.count == 1，如果没有结果，ruby会自动返回nil的


Helpful catch. Does XAPI return an error message that could be plumbed through and raised as an error? (I thought from memory it did, but I might be mistaken!).


So how do you actually persist the selected appointment combined with all the data from the form? I see a giant disconnect between the schedule and the form right now.


Probably want to get rid of this line :)


test


IDFXT (refaqtor) - i386-Windows-7-VisualStudio-12: Build Failed

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


Once Again


We should have an argument for this as it can't be changed after creation.


Thank you, I could not think of a good single word name. I originally had "Target region." I am not good an naming things.


Good catch


These should be weak private vars


Given the above, it would be worth allowing the caller to set this too.


self.eventSource


Apareceu aqui sim!


I think we can assume that if the user put the epoll transport in their classpath, they want to use it. This avoid adding yet another configuration option.
The only problem is if someone packages an artifact that they want to deploy both on Linux or other platforms without modification, but that seems super edge case to me.


Again


Yeah, autoderef in action, thanks!


You're late . {Nl} Want to save a woman?


So does this overwrite all the firebase data, or how does it work? Is there a reason to be defining this data in the client-side app vs having it filled on the server and the angular app relying on data to be returned when it queries for all the available days?


Should this be `setRealSize`?


@oesvends

I just pushed two commits to the VUnit master branch to help you out:
1. I added calling of std.env.stop in test_runner_cleanup in case of vhdl 2008 so that you do not need the "when" command in your Aldec interface. There is no point in not using 2008 with Aldec anyway I guess.
2. I added some basic infrastructure to support multiple simulators in ui.py. You can remove the "-A" flag you added and use that mechanism instead. It supports four ways to set the simulator, higher number has higher precedence:
  1. Detect available simulators and choose the first one.
  2. Check VUNIT_SIMULATOR environment variable
  3. Check method argument provided to from_argv method.
  4. Check --sim command line argument.


Thanks!


Hi,
Thanks for the feedback.  I got a response from Aldec today, they have confirmed that this behaviour is not intended, and they will look into it and com up with a patch, hopefully.


Hello @caseykuhns sorry for communicating in obscure ways, but I had a question or two regarding the VL6180 board that you wrote a tutorial on and would really appreciate your input! I messaged you on facebook, but I am thinking that the message went to your "Other messages" folder since we are not friends on there. If you would prefer email, my address is dsackett@rowetechinc.com . FYI I am trying to use these sensors for my senior design project which is an autonomous walking robot! It looked like you might be involved with some robotics, judging by your Facebook pictures... Thanks in advance!

Dustin


Nice. :+1:


bah I did it: https://github.com/scijava/scijava-common/pull/153


Nevermind.  I see this a new method in the bytelist `SNAPSHOT`.


@ShawnieBoy can you go through the above list an select the ID for the correct image. Thanks.


Gj


Gets dealt with in a later commit, but good spot :)


:beers:


79453838-AutomateSomeDocumentation (mbadams5) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1163 of 1165 tests passed)

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


Uhul, valeu David!


novatech409b uses ``-s/--serial-dev`` for specifying the serial port, and ``-s sim`` to enter simulation mode. Let's keep this consistent. Also, we may want to pick a consistent default value too (``/dev/ttyUSB0``  vs. ``hwgrep://``) - the problem of hwgrep is it also attaches to non-USB serial devices, and ``/dev/ttyUSB0`` is non portable.


Not sure what you mean.

However FYI the ServletContext is now available in Requests with Servlet 3.0 :) See https://tomcat.apache.org/tomcat-7.0-doc/servletapi/javax/servlet/ServletRequest.html#getServletContext()


Sure thing - I used thallid as an example as it's a favourite card of mine, and I can remember trying to get 4 of the same image :grinning:


This can now return values outside of {-1, 0, 1}, right?


ovo je koemntar i ne znam gde će da se pojavi!


Please explain why it's incompatible. I've checked the full code and this configuration property is used only in 1 place and at the place I'm adding the slash if it's not there...


IDFXT (refaqtor) - Win64-Windows-7-VisualStudio-12: Build Failed

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


Ends up as the below by final commit, but I'll collapse the line.
```rust
fn handler<'a>(_: &mut Request, mut res: Response<'a>) -> MiddlewareResult<'a> {
    Err(NickelError::new(res,
                         "Error Parsing JSON",
                         StatusCode::BadRequest))
}
```


fixes the group looting as well as fixing the skinning / soul shard issue


if you use the Magento feature to combine js, then the filename is a hash based on the filenames.
I don't remember right now if it adds the hash when combining is disabled.

We've improved the module, that it calculates the filename hash based on the file content (instead of filenames). And with this modification your're safe :)


Just delete it


It's great that we support edited cabal files.

However, this isn't particularly robust. I keep running into problems when there are multiple revisions of the cabal file, but nixpkgs hasn't updated to the latest yet. The problem is that
```
http://hackage.haskell.org/package/${self.fname}/${self.pname}.cabal
```
isn't a "stable" URL. It points to the *current* revision, but that can change at any time. Instead, we should use
```
http://hackage.haskell.org/package/${self.fname}/revision/${self.revision}.cabal
```
where `revision` should be a new variable that should be set in addition to `editedCabalFile`.

For programmatically determining the current revision while scanning Hackage, we can either look at the old URL and scan for `x-revision`, or we can look at the *JSON* output of
```
http://hackage.haskell.org/package/${self.fname}/revisions
```
and look for the latest revision in there.


Yes, as you say, there is definitely the risk of race conditions in the current version. I opened this branch with the idea of testing possible ideas, but this was not meant to be a final solution and I do not have plans to merge this into master anytime soon.

I also tried to adjust the conditions adding an if clause to the #pragma omp parallel for statements to limit the depth of the parallelism. This works, but the advantage is negligible over the sequential code, so I think it's not worth it. I didn't pushed these changes because I wasn't satisfied with the results.

As a side note, the variation in the amount of work between different iterations should not be a problem given that one can choose a scheduler for OpenMP so that an approach similar to list-scheduling is already implemented. I think the dynamic scheduler, for example, should be appropriate. I am not really an expert of OpenMP, so feel free to contradict me.

Anyway, thank you for the kind feedback on the issues, that's very appreciated. I started to work on your library when writing the MATLAB bindings for (part of) the code (see https://github.com/robol/h2lib-matlab). I might come up with a pull request for the master branch in the near future for other small tweaks (such as compatibility with MATLAB's LAPACK).


Really?


I actually came up with some code that would detect the vcom flavour that was invoked, but i forgot to push when I left work today.

Thanks for your help.


![noice](http://i.imgur.com/w7oBvYv.gif)

yeah, i went there


Happy to add it. I actually saw [your Gist](https://gist.github.com/adamstac/a0832ffca53a4e5eebc2) with the colors, when I was trying to find your tweet.

If you have any suggestions/improvements, they are always welcome.

Btw, thank you for the Changelog, can't keep up with it all the time but always good stuff on there.


I believe that colors themselves should move to channel as well


I notice that I also added the functionality here to timeout extractRegexR after 10 seconds for a particular file.  I observed something like that yesterday when all 32 clones were running...it just looked like the program was waiting in the extractRegexR for a long time and I suspect that it may have been exploring a looping file system...maybe?


Thanks, there will also be a few for the unimplemented scripts as well - I will add them after the playable list.


if (true) ?


This plugin is just a joke.


Interesting list -> "Ertai, the corrupted", "Tahngarth, Talruum Hero" and "To Arms!" all stand out to me.

I know Ertai had an alternate art, but we've already compensated for those. No idea about Tahngarth. "To Arms!" may be the exclamation point, but "Kaboom!" was ok...


Don't forget InstallFromDMG and Installer. In for a penny...


If you never join messages to single one you don't need this code


Gets fixed later :)


introduce lists with a complete sentence.


On Fri, Mar 20, 2015 at 12:29 PM, Brad Fitzpatrick <notifications@github.com
> wrote:

> It's gross to repeat all this methods. I would just embed the
> *http2.Framer in *framer and then add a Flush method to *framer.
>
That is not the final form because I am still doing a bunch of perf related
work. The current form allows me experiment my ideas relatively easily,
e.g., i) make some special optimization when sending a particular type of
frame and ii) try out some crazy ideas before calling
http2.Framer.WriteXXXX. Basically, framer is the central place I can try
out my ideas without changing the code in other places much.

I agree with you that it should be changed to what you proposed if the
current form is the final.

> —
> Reply to this email directly or view it on GitHub
> <https://github.com/iamqizhao/grpc-go/commit/902316edc6957bcf1530f37e22cd8f288b2780d8#commitcomment-10322972>
> .
>


Not yet tested, but managed to optimize from ~10% CPU usage down to 3% with this upgrade. Feel free to try it out.


Thanks 👍


What is the advantage of this capability-specific representation over the proposed named-tuple solution that I implemented ? @Sridhar-MS


dfhhfh


Is this generated from the Vocabulary xml or is it hand written ?


Use --> You use (?)


close up space after hyphen


Wow, nice find! You can remove the comment though, leave just the fix. The commit message is enough to carry that information.


-- > With the edX Platform Course Structure API, you can complete these tasks.


Updating to:
```rust
Err(e) => unsafe {
    Err(NickelError::without_response(format!("Failed to start response: {}", e)))
}
```

Feel like the unsafe is bit more hidden, but I can live with it.


Hi,
With this modification, you've solved the 1st of my issue:
https://tvheadend.org/issues/2716

If you have some free time, can you have a look on my issue ?
I think it will be a good opportunity to improve (again) the SAT>IP feature of Tvheadend.

Thanks


Yeah, good idea. That seems to work. Is there a nicer way I can do that in scons than

    env.Append(CXXFLAGS = [
        '-isystem='+self.user_settings.rpi_vc_path+'/include',
        '-isystem='+self.user_settings.rpi_vc_path+'/include/interface/vcos/pthreads',
        '-isystem='+self.user_settings.rpi_vc_path+'/include/interface/vmcs_host/linux'])

?


done PR #88

2015-03-20 18:13 GMT+01:00 Tom Wayson <notifications@github.com>:

> This is great! Please make the changes and PR.
>
> Thanks!
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/tsamaya/dojo-bootstrap-map-js/commit/b6fd92d994bff8ecef57fefea33dd3e043056a68#commitcomment-10320624>
> .
>


--> contains these fields.


of --> about


Ok, Ertai & Tahngarth had foil alt art versions in the actual set, not separately.


what happens? is it too bad to show this? ;-)


maybe "Identifies the time period for the course run." just to give a clue what we mean by "run"


It's the usual MIT license. We can put the words "MIT license" on top, to
make this extra clear. Please let me know if there is any issue regarding
licensing.

Sent from my mobile phone.
On Mar 20, 2015 12:54 PM, "Abinash Meher" <notifications@github.com> wrote:

> I guess this is the MIT license judging from the discussion in the mailing
> list.This is the same one CSymPy uses. @certik <https://github.com/certik>
> ?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/abinashmeher999/csympy/commit/cebc6ed66ccdce5e4d791c1bfed8a0aa90edd38a#commitcomment-10322397>
> .
>


:shipit:


Yep, this is probably a bug.


specified for --> that is sponsoring (or offering?)


wow, an empty commit. go to 64aece922a4846a2b38ffbfda81a0d6d2021d5b5


don't forget this


If lowercase true, I'd put in single quotes or reorganize/rephrase so that it isn't the first word of the sentence


...might make ^the^ ?


This is hand-written. Mainly because it does not directly map to the UpdateRestrictionType in the Vocabulary XML. Here we do not capture the list of nonupdateable navigation properties. Instead nonupdateable navigation properties are resolved to OdcmProperties and this OdcmUpdate capability is added to those OdcmProperties.


This is for the reset function. It overwrites all data that has been populated in the server with default values.


[#22](https://github.com/tres-framework/trestle/issues/22#issuecomment-84134444] Change source directory to `/src/` instead of of `/src/Trestle`?


`Thanks, there will also be a few for the unimplemented scripts as well - I will add them after the playable list.`

Ooh, be careful to not grab some of the Heralds or halves of split cards. They parse but aren't playable


Re-worked this, so it's more efficient. (No checks as opposed to 4).


Should be @Autowired and no need for `final` here.


For some weird reason GitHub thinks your commit belongs to my repository, while it should belong to the fork.

Anyway, if you could open a pull request it would be easier for me to pull out the changes and try it out.


This should be in pf::util


Agreed I made a comment.

From: lackroneluke <notifications@github.com<mailto:notifications@github.com>>
Reply-To: booz-allen-agile-delivery/dryrun-template <reply@reply.github.com<mailto:reply@reply.github.com>>
Date: Friday, March 20, 2015 at 3:24 PM
To: booz-allen-agile-delivery/dryrun-template <dryrun-template@noreply.github.com<mailto:dryrun-template@noreply.github.com>>
Cc: Martin Folkoff <Folkoff_Martin@bah.com<mailto:Folkoff_Martin@bah.com>>
Subject: [External] Re: [dryrun-template] existings tasks (4cc5c95)

Meh may be fine, but don't think we can say Sucks for something we'd hope the government would enjoy.

—
Reply to this email directly or view it on GitHub<https://github.com/booz-allen-agile-delivery/dryrun-template/commit/4cc5c956d997c050aaa9931b444d74ac4cba8025#commitcomment-10322884>.


Good suggestion, alternatively we could reduce the overlap with params and have request.format() return an option (and take into account if format fields are already taken).

I'll pull it out into a static once hyper is buildable again, so I can rebase this onto the other branch.


@randsonjs - Can you tell me about the reasoning behind this PR? Is it code style preference? I'm not sure why we'd do this but I am open to your ideas. Let us know. Thanks.


:+1: :shipit:


Will there ever be a case where there aren't any completions?


What I think I will do is add a new text file to the INPUT folder for the scripts builder which can be used to fix the invalid links above or even override the automatically generated image. Something like...
```
Abbey Matron.jpg=http://api.mtgdb.info/content/hi_res_card_images/3012.jpg
Ertai, the Corrupted.jpg=http://magiccards.info/scans/en/ps/107a.jpg
....
```


Чего конкретно?


This section is required for the proper placement of resources.


`ResourceCloser` already checks for `null`, so no need to check for it.


Wouldn't this be better as a RageTexture method?


Might be nice to log the search string used


Removed duplicated beans.


r+


Commented out, remove


пробела


please add Apache License headers.


Apache license headers.


saw approval from glennw
at https://github.com/pcwalton/servo/commit/25e434cb668a40212316d3a7570d63b0889d18a8


merging pcwalton/servo/font-group-caching = 25e434cb into auto


pcwalton/servo/font-group-caching = 25e434cb merged ok, testing candidate = bc50694c


Would make sense, save having to do this again!

Moorish Cavalry just popped up - It's actually reprinted in Timespiral Timshifted, but it's trying to fetch one of the multi-art versions from Arabian Nights


1: M110 missing component name


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not 's'
24:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
28:1: I101 Imported names are in the wrong order. Should be collect_user_info, get_email, get_user_info, isGuestUser
28:1: I100 Imports statements are in the wrong order. from invenio.legacy.webuser should be before from invenio.utils.url
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: I101 Imported names are in the wrong order. Should be CFG_BASE_URL, CFG_CERN_SITE, CFG_SITE_LANG, CFG_SITE_NAME, CFG_SITE_NAME_INTL, CFG_SITE_RECORD, CFG_SITE_SECURE_URL, CFG_SITE_SUPPORT_EMAIL, CFG_SITE_URL, CFG_WEBCOMMENT_ALLOW_COMMENTS, CFG_WEBCOMMENT_ALLOW_REVIEWS, CFG_WEBCOMMENT_AUTHOR_DELETE_COMMENT_OPTION, CFG_WEBCOMMENT_MAX_ATTACHED_FILES, CFG_WEBCOMMENT_MAX_ATTACHMENT_SIZE, CFG_WEBCOMMENT_NB_REPORTS_BEFORE_SEND_EMAIL_TO_ADMIN, CFG_WEBCOMMENT_USE_RICH_TEXT_EDITOR
31:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.utils.mail
31:1: E402 module level import not at top of file
32:28: E126 continuation line over-indented for hanging indent
47:1: I101 Imported names are in the wrong order. Should be create_html_select, get_html_text_editor
47:1: E402 module level import not at top of file
48:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.utils.html
48:1: E402 module level import not at top of file
49:1: E402 module level import not at top of file
50:1: I100 Imports statements are in the wrong order. from invenio.modules.access.engine should be before from invenio.modules.formatter
50:1: E402 module level import not at top of file
51:1: I101 Imported names are in the wrong order. Should be acc_get_role_id, acc_get_user_roles_from_user_info
51:1: I100 Imports statements are in the wrong order. from invenio.modules.access.control should be before from invenio.modules.access.engine
51:1: E402 module level import not at top of file
52:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.modules.access.control
52:1: E402 module level import not at top of file
54:1: E302 expected 2 blank lines, found 1
54: D203 Expected 1 blank line *before* class docstring, found 0
54: D400 First line should end with '.', not 'l'
57: D202 No blank lines allowed *after* method docstring, found 1
57: D400 First line should end with '.', not 'd'
57: D205 Blank line missing between one-line summary and description
92:13: F841 local variable 'last_comment_round_name' is assigned to but never used
98:139: E221 multiple spaces before operator
101:85: E231 missing whitespace after ','
101:87: E221 multiple spaces before operator
140:34: E127 continuation line over-indented for visual indent
152:13: E128 continuation line under-indented for visual indent
154:33: E203 whitespace before ':'
159:36: E225 missing whitespace around operator
160:168: E502 the backslash is redundant between brackets
160:57: E225 missing whitespace around operator
161:67: E127 continuation line over-indented for visual indent
164:13: E124 closing bracket does not match visual indentation
178:14: E127 continuation line over-indented for visual indent
180:14: E124 closing bracket does not match visual indentation
184: D401 First line should be imperative: 'Display', not 'Displays'
184: D205 Blank line missing between one-line summary and description
209: D400 First line should end with '.', not 'd'
209: D205 Blank line missing between one-line summary and description
244:26: E201 whitespace after '{'
244:45: E203 whitespace before ':'
244:22: E222 multiple spaces after operator
245:46: E203 whitespace before ':'
246:44: E203 whitespace before ':'
247:44: E203 whitespace before ':'
248:44: E203 whitespace before ':'
248:62: E261 at least two spaces before inline comment
248:63: E262 inline comment should start with '# '
249:44: E203 whitespace before ':'
249:62: E261 at least two spaces before inline comment
249:63: E262 inline comment should start with '# '
250:25: E124 closing bracket does not match visual indentation
260:13: F841 local variable 'last_comment_round_name' is assigned to but never used
294:106: E231 missing whitespace after ':'
294:143: E231 missing whitespace after ':'
295:32: E222 multiple spaces after operator
316:37: E225 missing whitespace around operator
336:13: E122 continuation line missing indentation or outdented
336:14: E201 whitespace after '{'
336:40: E203 whitespace before ':'
337:40: E203 whitespace before ':'
338:40: E203 whitespace before ':'
339:40: E203 whitespace before ':'
340:40: E203 whitespace before ':'
341:40: E203 whitespace before ':'
342:40: E203 whitespace before ':'
343:40: E203 whitespace before ':'
344:41: E203 whitespace before ':'
345:60: E225 missing whitespace around operator
346:40: E203 whitespace before ':'
347:13: E124 closing bracket does not match visual indentation
359:28: E128 continuation line under-indented for visual indent
360:28: E128 continuation line under-indented for visual indent
363: D400 First line should end with '.', not 'n'
363: D205 Blank line missing between one-line summary and description
402:35: E128 continuation line under-indented for visual indent
403:35: E126 continuation line over-indented for hanging indent
408:81: E225 missing whitespace around operator
408:100: E225 missing whitespace around operator
410:83: E225 missing whitespace around operator
433:105: E225 missing whitespace around operator
435:106: E225 missing whitespace around operator
441:110: E225 missing whitespace around operator
452:111: E271 multiple spaces after keyword
461:37: E126 continuation line over-indented for hanging indent
488:17: E127 continuation line over-indented for visual indent
488:33: E203 whitespace before ':'
489:33: E203 whitespace before ':'
490:33: E203 whitespace before ':'
500: D400 First line should end with '.', not 'n'
500: D205 Blank line missing between one-line summary and description
533:107: E231 missing whitespace after ':'
534:9: E266 too many leading '#' for block comment
568:94: E225 missing whitespace around operator
574:99: E225 missing whitespace around operator
589:31: E203 whitespace before ':'
590:16: E128 continuation line under-indented for visual indent
591:16: E128 continuation line under-indented for visual indent
591:31: E203 whitespace before ':'
592:16: E128 continuation line under-indented for visual indent
592:31: E203 whitespace before ':'
593:16: E128 continuation line under-indented for visual indent
594:16: E128 continuation line under-indented for visual indent
594:31: E203 whitespace before ':'
595:16: E128 continuation line under-indented for visual indent
595:31: E203 whitespace before ':'
596:16: E128 continuation line under-indented for visual indent
596:31: E203 whitespace before ':'
597:16: E124 closing bracket does not match visual indentation
600: D400 First line should end with '.', not 's'
600: D205 Blank line missing between one-line summary and description
609:55: E231 missing whitespace after ','
692:13: F841 local variable 'c_round_name' is assigned to but never used
693:13: F841 local variable 'c_restriction' is assigned to but never used
702:26: E201 whitespace after '{'
702:45: E203 whitespace before ':'
702:22: E222 multiple spaces after operator
703:46: E203 whitespace before ':'
704:44: E203 whitespace before ':'
705:44: E203 whitespace before ':'
706:44: E203 whitespace before ':'
707:44: E203 whitespace before ':'
708:44: E203 whitespace before ':'
709:44: E203 whitespace before ':'
710:44: E203 whitespace before ':'
711:44: E203 whitespace before ':'
712:25: E124 closing bracket does not match visual indentation
719:22: E201 whitespace after '{'
719:37: E203 whitespace before ':'
719:19: E222 multiple spaces after operator
720:42: E203 whitespace before ':'
721:36: E203 whitespace before ':'
722:36: E203 whitespace before ':'
724:36: E203 whitespace before ':'
725:36: E203 whitespace before ':'
726:36: E203 whitespace before ':'
727:36: E203 whitespace before ':'
731:9: E266 too many leading '#' for block comment
736:13: F841 local variable 'last_comment_round_name' is assigned to but never used
747:20: E127 continuation line over-indented for visual indent
754:35: E127 continuation line over-indented for visual indent
754:73: E221 multiple spaces before operator
763:132: E202 whitespace before ')'
764:33: E127 continuation line over-indented for visual indent
764:71: E221 multiple spaces before operator
765:140: E225 missing whitespace around operator
838:76: E261 at least two spaces before inline comment
846:275: E231 missing whitespace after ':'
847:163: E231 missing whitespace after ':'
880:38: E203 whitespace before ':'
880:62: E231 missing whitespace after ':'
882:38: E203 whitespace before ':'
882:61: E231 missing whitespace after ':'
883:38: E203 whitespace before ':'
883:63: E231 missing whitespace after ':'
885:35: E203 whitespace before ':'
892:9: E266 too many leading '#' for block comment
917:9: E266 too many leading '#' for block comment
1085:9: E122 continuation line missing indentation or outdented
1086:47: E203 whitespace before ','
1088:43: E225 missing whitespace around operator
1104: D401 First line should be imperative: 'print', not 'prints'
1104: D400 First line should end with '.', not 'm'
1112: D202 No blank lines allowed *after* method docstring, found 1
1112: D400 First line should end with '.', not 'n'
1112: D205 Blank line missing between one-line summary and description
1124:15: E221 multiple spaces before operator
1157: D400 First line should end with '.', not 'n'
1157: D205 Blank line missing between one-line summary and description
1175:15: E221 multiple spaces before operator
1177:9: E122 continuation line missing indentation or outdented
1178:9: E128 continuation line under-indented for visual indent
1179:9: E128 continuation line under-indented for visual indent
1196: D400 First line should end with '.', not 's'
1196: D205 Blank line missing between one-line summary and description
1216:22: E201 whitespace after '{'
1216:40: E203 whitespace before ':'
1217:40: E203 whitespace before ':'
1217:65: E202 whitespace before '}'
1222: D400 First line should end with '.', not 'r'
1222: D205 Blank line missing between one-line summary and description
1229:9: F841 local variable '_' is assigned to but never used
1238: D400 First line should end with '.', not 's'
1238: D205 Blank line missing between one-line summary and description
1257:22: E201 whitespace after '{'
1257:37: E203 whitespace before ':'
1257:19: E222 multiple spaces after operator
1258:42: E203 whitespace before ':'
1259:36: E203 whitespace before ':'
1260:36: E203 whitespace before ':'
1261:36: E203 whitespace before ':'
1262:36: E203 whitespace before ':'
1281:20: E222 multiple spaces after operator
1306:13: E122 continuation line missing indentation or outdented
1307:121: E502 the backslash is redundant between brackets
1308:28: E127 continuation line over-indented for visual indent
1309:100: E502 the backslash is redundant between brackets
1310:31: E127 continuation line over-indented for visual indent
1311:238: E271 multiple spaces after keyword
1320:50: E251 unexpected spaces around keyword / parameter equals
1320:52: E251 unexpected spaces around keyword / parameter equals
1355: D400 First line should end with '.', not 's'
1355: D205 Blank line missing between one-line summary and description
1373:22: E201 whitespace after '{'
1373:37: E203 whitespace before ':'
1373:19: E222 multiple spaces after operator
1374:42: E203 whitespace before ':'
1375:36: E203 whitespace before ':'
1376:36: E203 whitespace before ':'
1377:36: E203 whitespace before ':'
1378:36: E203 whitespace before ':'
1388:13: E128 continuation line under-indented for visual indent
1427:1: E128 continuation line under-indented for visual indent
1428:50: E251 unexpected spaces around keyword / parameter equals
1428:52: E251 unexpected spaces around keyword / parameter equals
1469:35: E203 whitespace before ':'
1469:42: E225 missing whitespace around operator
1470:35: E203 whitespace before ':'
1470:41: E225 missing whitespace around operator
1485: D400 First line should end with '.', not 'd'
1485: D205 Blank line missing between one-line summary and description
1492:22: E201 whitespace after '{'
1492:37: E203 whitespace before ':'
1492:19: E222 multiple spaces after operator
1493:42: E203 whitespace before ':'
1494:36: E203 whitespace before ':'
1495:36: E203 whitespace before ':'
1496:36: E203 whitespace before ':'
1497:36: E203 whitespace before ':'
1501:51: E221 multiple spaces before operator
1512:101: E222 multiple spaces after operator
1516: D401 First line should be imperative: 'Create', not 'Creates'
1516: D290 White spaces around docstring should be trimmed.
1516: D205 Blank line missing between one-line summary and description
1539:15: E221 multiple spaces before operator
1579: D400 First line should end with '.', not 'e'
1579: D200 One-line docstring should not occupy 3 lines
1605:19: E225 missing whitespace around operator
1609:36: E203 whitespace before ':'
1612:35: E203 whitespace before ':'
1613:35: E203 whitespace before ':'
1618:39: E225 missing whitespace around operator
1620: D400 First line should end with '.', not 'e'
1635:18: E225 missing whitespace around operator
1666: D400 First line should end with '.', not ')'
1666: D205 Blank line missing between one-line summary and description
1690:27: E127 continuation line over-indented for visual indent
1693:27: E127 continuation line over-indented for visual indent
1716:13: E201 whitespace after '{'
1716:25: E203 whitespace before ':'
1717:25: E203 whitespace before ':'
1718:25: E203 whitespace before ':'
1719:25: E203 whitespace before ':'
1721:26: E203 whitespace before ':'
1722:25: E203 whitespace before ':'
1723:25: E203 whitespace before ':'
1724:25: E203 whitespace before ':'
1754: D401 First line should be imperative: 'output', not 'outputs'
1754: D290 White spaces around docstring should be trimmed.
1754: D400 First line should end with '.', not 'd'
1758: D401 First line should be imperative: 'prepare', not 'prepares'
1758: D290 White spaces around docstring should be trimmed.
1758: D400 First line should end with '.', not 'r'
1773: D401 First line should be imperative: 'output', not 'outputs'
1773: D290 White spaces around docstring should be trimmed.
1773: D400 First line should end with '.', not 'w'
1788:34: E203 whitespace before ':'
1796: D400 First line should end with '.', not 't'
1796: D205 Blank line missing between one-line summary and description
1803:9: F841 local variable '_' is assigned to but never used
1842:17: E128 continuation line under-indented for visual indent
1842:50: E225 missing whitespace around operator
1842:69: E225 missing whitespace around operator
1843:17: E128 continuation line under-indented for visual indent
1843:36: E203 whitespace before ','
1843:23: E231 missing whitespace after ':'
1844:17: E128 continuation line under-indented for visual indent
1844:49: E203 whitespace before ','
1845:17: E128 continuation line under-indented for visual indent
1846:17: E128 continuation line under-indented for visual indent
1852:17: E128 continuation line under-indented for visual indent
1852:50: E225 missing whitespace around operator
1852:69: E225 missing whitespace around operator
1853:17: E128 continuation line under-indented for visual indent
1853:36: E203 whitespace before ','
1853:23: E231 missing whitespace after ':'
1854:17: E128 continuation line under-indented for visual indent
1855:17: E128 continuation line under-indented for visual indent
1860: D400 First line should end with '.', not 't'
1860: D205 Blank line missing between one-line summary and description
1866:9: F841 local variable '_' is assigned to but never used
1900:49: E225 missing whitespace around operator
1900:68: E225 missing whitespace around operator
1901:54: E272 multiple spaces before keyword
1903:49: E225 missing whitespace around operator
1903:68: E225 missing whitespace around operator
1904:54: E272 multiple spaces before keyword
1910:13: E128 continuation line under-indented for visual indent
1910:39: E203 whitespace before ','
1911:13: E128 continuation line under-indented for visual indent
1912:13: E128 continuation line under-indented for visual indent
1913:13: E128 continuation line under-indented for visual indent
1914:13: E128 continuation line under-indented for visual indent
1915:13: E128 continuation line under-indented for visual indent
1920: D400 First line should end with '.', not 't'
1920: D205 Blank line missing between one-line summary and description
1970:73: E261 at least two spaces before inline comment
1970:73: E262 inline comment should start with '# '
1972:81: E261 at least two spaces before inline comment
1972:81: E262 inline comment should start with '# '
1973:81: E261 at least two spaces before inline comment
1973:81: E262 inline comment should start with '# '
1974:81: E261 at least two spaces before inline comment
1974:81: E262 inline comment should start with '# '
1975:81: E261 at least two spaces before inline comment
1975:81: E262 inline comment should start with '# '
1976:81: E261 at least two spaces before inline comment
1976:81: E262 inline comment should start with '# '
1978:81: E261 at least two spaces before inline comment
1978:81: E262 inline comment should start with '# '
1979:81: E261 at least two spaces before inline comment
1979:81: E262 inline comment should start with '# '
1980:81: E261 at least two spaces before inline comment
1980:81: E262 inline comment should start with '# '
1981:81: E261 at least two spaces before inline comment
1981:81: E262 inline comment should start with '# '
1984:76: E261 at least two spaces before inline comment
1984:76: E262 inline comment should start with '# '
1986:84: E261 at least two spaces before inline comment
1986:84: E262 inline comment should start with '# '
1987:84: E261 at least two spaces before inline comment
1987:84: E262 inline comment should start with '# '
1988:84: E261 at least two spaces before inline comment
1988:84: E262 inline comment should start with '# '
1989:84: E261 at least two spaces before inline comment
1989:84: E262 inline comment should start with '# '
1990:84: E261 at least two spaces before inline comment
1990:84: E262 inline comment should start with '# '
1992:84: E262 inline comment should start with '# '
1993:84: E262 inline comment should start with '# '
1994:84: E262 inline comment should start with '# '
1995:84: E262 inline comment should start with '# '
1996:84: E262 inline comment should start with '# '
1998:84: E261 at least two spaces before inline comment
2001:65: E261 at least two spaces before inline comment
2001:66: E262 inline comment should start with '# '
2002:65: E261 at least two spaces before inline comment
2002:66: E262 inline comment should start with '# '
2003:66: E261 at least two spaces before inline comment
2003:66: E262 inline comment should start with '# '
2010:75: E261 at least two spaces before inline comment
2011:75: E261 at least two spaces before inline comment
2012:75: E261 at least two spaces before inline comment
2013:70: E261 at least two spaces before inline comment
2028:15: E128 continuation line under-indented for visual indent
2029:15: E128 continuation line under-indented for visual indent
2030:15: E128 continuation line under-indented for visual indent
2031:23: E211 whitespace before '('
2044:13: E122 continuation line missing indentation or outdented
2045:13: E122 continuation line missing indentation or outdented
2046:13: E122 continuation line missing indentation or outdented
2050:13: E122 continuation line missing indentation or outdented
2051:13: E122 continuation line missing indentation or outdented
2052:13: E122 continuation line missing indentation or outdented
2072:36: E225 missing whitespace around operator
2074:36: E225 missing whitespace around operator
2101: D400 First line should end with '.', not ','
2101: D205 Blank line missing between one-line summary and description
2113:37: E225 missing whitespace around operator
2113:86: E225 missing whitespace around operator
2125: D400 First line should end with '.', not ','
2125: D205 Blank line missing between one-line summary and description
2137:37: E225 missing whitespace around operator
2137:86: E225 missing whitespace around operator
2151:5: E303 too many blank lines (3)
2151: D400 First line should end with '.', not ','
2151: D205 Blank line missing between one-line summary and description
2163:37: E225 missing whitespace around operator
2163:86: E225 missing whitespace around operator
2175: D202 No blank lines allowed *after* method docstring, found 1
2175: D400 First line should end with '.', not ')'
2185:21: E126 continuation line over-indented for hanging indent
2188:26: E225 missing whitespace around operator
2224:9: E122 continuation line missing indentation or outdented
2225:9: E122 continuation line missing indentation or outdented
2226:9: E122 continuation line missing indentation or outdented
2227:9: E122 continuation line missing indentation or outdented
2228:9: E122 continuation line missing indentation or outdented
2229:9: E122 continuation line missing indentation or outdented
2230:9: E122 continuation line missing indentation or outdented
2231:9: E124 closing bracket does not match visual indentation
2234: D401 First line should be imperative: 'Print', not 'Prints'
2234: D400 First line should end with '.', not 'w'
2234: D205 Blank line missing between one-line summary and description
2256:15: E127 continuation line over-indented for visual indent
2256:109: E502 the backslash is redundant between brackets
2258:16: E127 continuation line over-indented for visual indent
2260:48: E225 missing whitespace around operator
2260:67: E225 missing whitespace around operator
2264: D401 First line should be imperative: 'Print', not 'Prints'
2264: D400 First line should end with '.', not 'w'
2264: D205 Blank line missing between one-line summary and description
2286:72: E221 multiple spaces before operator
2287:16: E127 continuation line over-indented for visual indent
2287:82: E502 the backslash is redundant between brackets
2287:44: E225 missing whitespace around operator
2287:63: E225 missing whitespace around operator
2291:81: E221 multiple spaces before operator
2292:20: E126 continuation line over-indented for hanging indent
2292:86: E502 the backslash is redundant between brackets
2292:48: E225 missing whitespace around operator
2292:67: E225 missing whitespace around operator
2296:79: E221 multiple spaces before operator
2297:20: E126 continuation line over-indented for hanging indent
2297:86: E502 the backslash is redundant between brackets
2297:48: E225 missing whitespace around operator
2297:67: E225 missing whitespace around operator
2301:16: E127 continuation line over-indented for visual indent
2305: D401 First line should be imperative: 'Print', not 'Prints'
2305: D400 First line should end with '.', not 'e'
2305: D205 Blank line missing between one-line summary and description
2332:15: E271 multiple spaces after keyword
2334: D202 No blank lines allowed *after* method docstring, found 1
2334: D400 First line should end with '.', not 'e'
2334: D205 Blank line missing between one-line summary and description
2372: D400 First line should end with '.', not 'r'
2414:78: E251 unexpected spaces around keyword / parameter equals
2414:80: E251 unexpected spaces around keyword / parameter equals
2415:78: E251 unexpected spaces around keyword / parameter equals
2415:80: E251 unexpected spaces around keyword / parameter equals
2416:79: E251 unexpected spaces around keyword / parameter equals
2416:81: E251 unexpected spaces around keyword / parameter equals
2417:55: E231 missing whitespace after ','
2417:78: E251 unexpected spaces around keyword / parameter equals
2417:80: E251 unexpected spaces around keyword / parameter equals
2425:22: E222 multiple spaces after operator
2460:9: E303 too many blank lines (3)
2523:34: E126 continuation line over-indented for hanging indent
2526:102: E502 the backslash is redundant between brackets
2526:77: E225 missing whitespace around operator
2526:96: E225 missing whitespace around operator
2531:98: E502 the backslash is redundant between brackets
2531:73: E225 missing whitespace around operator
2531:92: E225 missing whitespace around operator
2555:25: E127 continuation line over-indented for visual indent
2555:37: E203 whitespace before ':'
2556:37: E203 whitespace before ':'
2557:37: E203 whitespace before ':'
2558:37: E203 whitespace before ':'
2559:37: E203 whitespace before ':'
2560:37: E203 whitespace before ':'
2565:24: E261 at least two spaces before inline comment
2570:16: E127 continuation line over-indented for visual indent
2597:52: E126 continuation line over-indented for hanging indent


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


1: D400 First line should end with '.', not 's'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
30:1: I101 Imported names are in the wrong order. Should be DatabaseError, run_sql
32:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibsched.bibtask should be before from invenio.legacy.dbquery
33:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.legacy.bibsched.bibtask
34:1: I101 Imported names are in the wrong order. Should be CFG_BIBINDEX_CHARS_ALPHANUMERIC_SEPARATORS, CFG_BIBINDEX_CHARS_PUNCTUATION
34:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.bibrecord
35:6: E126 continuation line over-indented for hanging indent
55: D200 One-line docstring should not occupy 3 lines
65:9: E128 continuation line under-indented for visual indent
68:1: E302 expected 2 blank lines, found 1
68: D401 First line should be imperative: 'Return', not 'Returns'
68: D209 Put multi-line docstring closing quotes on separate line
68: D205 Blank line missing between one-line summary and description
68: D208 Docstring is over-indented
84: D401 First line should be imperative: 'Return', not 'Returns'
84: D209 Put multi-line docstring closing quotes on separate line
84: D400 First line should end with '.', not 'e'
84: D205 Blank line missing between one-line summary and description
84: D208 Docstring is over-indented
99: D401 First line should be imperative: 'Return', not 'Returns'
99: D400 First line should end with '.', not 'e'
99: D205 Blank line missing between one-line summary and description
99: D208 Docstring is over-indented
107:5: B901 blind except: statement
114: D401 First line should be imperative: 'Get', not 'Gets'
114: D290 White spaces around docstring should be trimmed.
114: D209 Put multi-line docstring closing quotes on separate line
114: D400 First line should end with '.', not 'd'
114: D205 Blank line missing between one-line summary and description
114: D208 Docstring is over-indented
120:5: B901 blind except: statement
127: D401 First line should be imperative: 'Get', not 'Gets'
127: D290 White spaces around docstring should be trimmed.
127: D209 Put multi-line docstring closing quotes on separate line
127: D400 First line should end with '.', not 'd'
127: D205 Blank line missing between one-line summary and description
127: D208 Docstring is over-indented
133:5: B901 blind except: statement
140: D205 Blank line missing between one-line summary and description
170: D400 First line should end with '.', not 's'
170: D205 Blank line missing between one-line summary and description
170: D208 Docstring is over-indented
181:11: E271 multiple spaces after keyword
187:1: F401 'get_idx_indexer' imported but unused
187:1: E402 module level import not at top of file
190: D401 First line should be imperative: 'Return', not 'Returns'
190: D209 Put multi-line docstring closing quotes on separate line
190: D205 Blank line missing between one-line summary and description
190: D208 Docstring is over-indented
212: D401 First line should be imperative: 'Return', not 'Returns'
212: D290 White spaces around docstring should be trimmed.
221: D401 First line should be imperative: 'Return', not 'Returns'
221: D209 Put multi-line docstring closing quotes on separate line
221: D400 First line should end with '.', not 'h'
221: D205 Blank line missing between one-line summary and description
221: D208 Docstring is over-indented
232: D401 First line should be imperative: 'Check', not 'Checks'
232: D400 First line should end with '.', not 'l'
241:1: E302 expected 2 blank lines, found 1
241: D400 First line should end with '.', not 's'
241: D205 Blank line missing between one-line summary and description
241: D208 Docstring is over-indented
255:1: E302 expected 2 blank lines, found 1
255: D401 First line should be imperative: 'Return', not 'Returns'
255: D205 Blank line missing between one-line summary and description
255: D208 Docstring is over-indented
268: D401 First line should be imperative: 'Return', not 'Returns'
268: D209 Put multi-line docstring closing quotes on separate line
268: D205 Blank line missing between one-line summary and description
268: D208 Docstring is over-indented
281: D401 First line should be imperative: 'Return', not 'Returns'
281: D209 Put multi-line docstring closing quotes on separate line
281: D205 Blank line missing between one-line summary and description
281: D208 Docstring is over-indented
291: D401 First line should be imperative: 'Return', not 'Returns'
291: D400 First line should end with '.', not 's'
291: D205 Blank line missing between one-line summary and description
291: D208 Docstring is over-indented
299:5: F841 local variable 'out' is assigned to but never used
321: D401 First line should be imperative: 'Return', not 'Returns'
321: D209 Put multi-line docstring closing quotes on separate line
321: D400 First line should end with '.', not 'g'
321: D205 Blank line missing between one-line summary and description
321: D208 Docstring is over-indented
326:26: E261 at least two spaces before inline comment
326:27: E262 inline comment should start with '# '
327:26: E261 at least two spaces before inline comment
327:27: E262 inline comment should start with '# '
342:25: E261 at least two spaces before inline comment
342:26: E262 inline comment should start with '# '
362: D401 First line should be imperative: 'Return', not 'Returns'
362: D209 Put multi-line docstring closing quotes on separate line
362: D400 First line should end with '.', not 'g'
362: D205 Blank line missing between one-line summary and description
362: D208 Docstring is over-indented
399: D401 First line should be imperative: 'Return', not 'Returns'
399: D205 Blank line missing between one-line summary and description
399: D208 Docstring is over-indented
437: D401 First line should be imperative: 'Return', not 'Returns'
437: D400 First line should end with '.', not ':'
437: D205 Blank line missing between one-line summary and description
437: D208 Docstring is over-indented
442:10: E225 missing whitespace around operator
450: D401 First line should be imperative: 'Remove', not 'Removes'
450: D205 Blank line missing between one-line summary and description
450: D208 Docstring is over-indented
463: D208 Docstring is over-indented
463: D200 One-line docstring should not occupy 3 lines
477: D401 First line should be imperative: 'Create', not 'Creates'
477: D400 First line should end with '.', not 'd'
477: D205 Blank line missing between one-line summary and description
477: D208 Docstring is over-indented
487: D101 Docstring missing
491: D401 First line should be imperative: 'Return', not 'Returns'
491: D300 Expected """-quotes, got '-quotes
501: D401 First line should be imperative: 'Return', not 'Returns'
501: D400 First line should end with '.', not 'y'
501: D205 Blank line missing between one-line summary and description
501: D208 Docstring is over-indented
512:47: E202 whitespace before ')'
516: D401 First line should be imperative: 'Check', not 'Checks'
516: D400 First line should end with '.', not 't'
519:25: E272 multiple spaces before keyword
526: D401 First line should be imperative: 'Check', not 'Checks'
526: D209 Put multi-line docstring closing quotes on separate line
526: D400 First line should end with '.', not ';'
526: D205 Blank line missing between one-line summary and description
526: D208 Docstring is over-indented
532: D401 First line should be imperative: 'Return', not 'Returns'
532: D209 Put multi-line docstring closing quotes on separate line
532: D400 First line should end with '.', not ';'
532: D205 Blank line missing between one-line summary and description
532: D208 Docstring is over-indented
541: D401 First line should be imperative: 'Find', not 'Finds'
541: D400 First line should end with '.', not 'n'
541: D205 Blank line missing between one-line summary and description
541: D208 Docstring is over-indented


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
32:1: E303 too many blank lines (3)
32: D203 Expected 1 blank line *before* class docstring, found 0
41:41: E251 unexpected spaces around keyword / parameter equals
41:43: E251 unexpected spaces around keyword / parameter equals
41:66: E251 unexpected spaces around keyword / parameter equals
41:68: E251 unexpected spaces around keyword / parameter equals
41:94: E251 unexpected spaces around keyword / parameter equals
41:96: E251 unexpected spaces around keyword / parameter equals
41:123: E251 unexpected spaces around keyword / parameter equals
41:125: E251 unexpected spaces around keyword / parameter equals
41: D102 Docstring missing
43:49: E127 continuation line over-indented for visual indent
44:49: E127 continuation line over-indented for visual indent
45:49: E127 continuation line over-indented for visual indent
71:35: E203 whitespace before ':'
72:35: E203 whitespace before ':'
73:35: E203 whitespace before ':'
74:35: E203 whitespace before ':'
75:35: E203 whitespace before ':'
89:25: E116 unexpected indentation (comment)
100:21: E116 unexpected indentation (comment)
106: D202 No blank lines allowed *after* method docstring, found 1
128:61: E251 unexpected spaces around keyword / parameter equals
128:63: E251 unexpected spaces around keyword / parameter equals
142:22: E711 comparison to None should be 'if cond is not None:'
159:9: F841 local variable 'raw' is assigned to but never used
180: D202 No blank lines allowed *after* method docstring, found 1
196: D401 First line should be imperative: 'List', not 'Lists'
196: D400 First line should end with '.', not ']'
198:21: E711 comparison to None should be 'if cond is None:'
202: D401 First line should be imperative: 'List', not 'Lists'
202: D400 First line should end with '.', not 'l'
212: D401 First line should be imperative: 'Bring', not 'Brings'
212: D202 No blank lines allowed *after* function docstring, found 1
212: D400 First line should end with '.', not 's'
229: D401 First line should be imperative: 'Run', not 'Runs'
229: D400 First line should end with '.', not 'l'
232:18: E272 multiple spaces before keyword
238: D401 First line should be imperative: 'Find', not 'Finds'
238: D400 First line should end with '.', not "'"
261:5: E303 too many blank lines (2)
288:5: E303 too many blank lines (2)
288: D205 Blank line missing between one-line summary and description
288: D208 Docstring is over-indented
297:5: E303 too many blank lines (2)
297: D400 First line should end with '.', not 'r'
302:5: E303 too many blank lines (2)
302: D290 White spaces around docstring should be trimmed.
326:5: E303 too many blank lines (2)
326: D205 Blank line missing between one-line summary and description
326: D208 Docstring is over-indented
336:1: W391 blank line at end of file


1: D400 First line should end with '.', not 'e'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
32: D103 Docstring missing
41: D103 Docstring missing
50: D103 Docstring missing
59: D103 Docstring missing
63: D209 Put multi-line docstring closing quotes on separate line
63: D203 Expected 1 blank line *before* class docstring, found 0
63: D302 Use u""" for docstrings with Unicode
63: D205 Blank line missing between one-line summary and description
63: D208 Docstring is over-indented
69:41: E251 unexpected spaces around keyword / parameter equals
69:43: E251 unexpected spaces around keyword / parameter equals
69:66: E251 unexpected spaces around keyword / parameter equals
69:68: E251 unexpected spaces around keyword / parameter equals
69:94: E251 unexpected spaces around keyword / parameter equals
69:96: E251 unexpected spaces around keyword / parameter equals
69:123: E251 unexpected spaces around keyword / parameter equals
69:125: E251 unexpected spaces around keyword / parameter equals
69: D400 First line should end with '.', not 'n'
72:49: E127 continuation line over-indented for visual indent
73:49: E127 continuation line over-indented for visual indent
74:49: E127 continuation line over-indented for visual indent
77:5: E303 too many blank lines (2)
77: D400 First line should end with '.', not 'r'
82:5: E303 too many blank lines (2)
82: D401 First line should be imperative: 'Split', not 'Splits'
82: D400 First line should end with '.', not 's'
82: D205 Blank line missing between one-line summary and description
104:22: E201 whitespace after '['
129:5: E303 too many blank lines (2)
129: D102 Docstring missing
132: D102 Docstring missing


1: D100 Docstring missing
22: D203 Expected 1 blank line *before* class docstring, found 0
22: D204 Expected 1 blank line *after* class docstring, found 2
22: D400 First line should end with '.', not ')'
22: D205 Blank line missing between one-line summary and description
22: D208 Docstring is over-indented
30:5: E303 too many blank lines (2)
30: D102 Docstring missing
34:5: E303 too many blank lines (2)
34: D401 First line should be imperative: 'Return', not 'Returns'
34: D400 First line should end with '.', not 'n'
38: D205 Blank line missing between one-line summary and description
45:15: F821 undefined name 'get_record'
49: D401 First line should be imperative: 'Return', not 'Returns'
49: D200 One-line docstring should not occupy 3 lines


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
25:6: E126 continuation line over-indented for hanging indent
27:1: I101 Imported names are in the wrong order. Should be strip_accents, wash_for_utf8
28:1: I101 Imported names are in the wrong order. Should be apply_stemming, length_check, lower_index_term, remove_latex_markup, remove_stopwords
28:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.engine_washer should be before from invenio.utils.text
29:6: E126 continuation line over-indented for hanging indent
31:1: I101 Imported names are in the wrong order. Should be latex_formula_re, re_arxiv, re_block_punctuation_begin, re_block_punctuation_end, re_punctuation, re_separators
31:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.engine_utils should be before from invenio.legacy.bibindex.engine_washer
32:6: E126 continuation line over-indented for hanging indent
41:1: E303 too many blank lines (3)
41: D203 Expected 1 blank line *before* class docstring, found 0
41: D205 Blank line missing between one-line summary and description
41: D208 Docstring is over-indented
47:41: E251 unexpected spaces around keyword / parameter equals
47:43: E251 unexpected spaces around keyword / parameter equals
47:66: E251 unexpected spaces around keyword / parameter equals
47:68: E251 unexpected spaces around keyword / parameter equals
47:94: E251 unexpected spaces around keyword / parameter equals
47:96: E251 unexpected spaces around keyword / parameter equals
47:123: E251 unexpected spaces around keyword / parameter equals
47:125: E251 unexpected spaces around keyword / parameter equals
47: D400 First line should end with '.', not 'n'
55:5: E303 too many blank lines (2)
55: D401 First line should be imperative: 'Pick', not 'Picks'
55: D400 First line should end with '.', not ')'
66:5: E303 too many blank lines (3)
66: D202 No blank lines allowed *after* method docstring, found 1
66: D400 First line should end with '.', not 's'
66: D205 Blank line missing between one-line summary and description
66: D208 Docstring is over-indented
117:5: E303 too many blank lines (2)
117: D202 No blank lines allowed *after* method docstring, found 1
117: D400 First line should end with '.', not 's'
117: D205 Blank line missing between one-line summary and description
117: D208 Docstring is over-indented
159:5: E303 too many blank lines (2)
159: D400 First line should end with '.', not 's'
159: D205 Blank line missing between one-line summary and description
159: D208 Docstring is over-indented
167: D401 First line should be imperative: 'Pick', not 'Picks'
167: D400 First line should end with '.', not 'n'
167: D205 Blank line missing between one-line summary and description


1: D400 First line should end with '.', not 'e'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
20:21: W291 trailing whitespace
29:1: E303 too many blank lines (4)
29: D203 Expected 1 blank line *before* class docstring, found 0
29: D204 Expected 1 blank line *after* class docstring, found 0
29: D205 Blank line missing between one-line summary and description
34:41: E251 unexpected spaces around keyword / parameter equals
34:43: E251 unexpected spaces around keyword / parameter equals
34:66: E251 unexpected spaces around keyword / parameter equals
34:68: E251 unexpected spaces around keyword / parameter equals
34:94: E251 unexpected spaces around keyword / parameter equals
34:96: E251 unexpected spaces around keyword / parameter equals
34:123: E251 unexpected spaces around keyword / parameter equals
34:125: E251 unexpected spaces around keyword / parameter equals
34: D102 Docstring missing
36:49: E127 continuation line over-indented for visual indent
37:49: E127 continuation line over-indented for visual indent
38:49: E127 continuation line over-indented for visual indent
40: D401 First line should be imperative: 'Return', not 'Returns'
40: D200 One-line docstring should not occupy 3 lines


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
27: D203 Expected 1 blank line *before* class docstring, found 0
27: D205 Blank line missing between one-line summary and description
27: D208 Docstring is over-indented
43:41: E251 unexpected spaces around keyword / parameter equals
43:43: E251 unexpected spaces around keyword / parameter equals
43: D102 Docstring missing
44:24: E127 continuation line over-indented for visual indent
44:40: E251 unexpected spaces around keyword / parameter equals
44:42: E251 unexpected spaces around keyword / parameter equals
45:24: E127 continuation line over-indented for visual indent
45:42: E251 unexpected spaces around keyword / parameter equals
45:44: E251 unexpected spaces around keyword / parameter equals
46:24: E127 continuation line over-indented for visual indent
46:43: E251 unexpected spaces around keyword / parameter equals
46:45: E251 unexpected spaces around keyword / parameter equals
50:5: E303 too many blank lines (2)
50: D208 Docstring is over-indented
68: D102 Docstring missing


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
26: D203 Expected 1 blank line *before* class docstring, found 0
26: D205 Blank line missing between one-line summary and description
26: D208 Docstring is over-indented
39:41: E251 unexpected spaces around keyword / parameter equals
39:43: E251 unexpected spaces around keyword / parameter equals
39:66: E251 unexpected spaces around keyword / parameter equals
39:68: E251 unexpected spaces around keyword / parameter equals
39:94: E251 unexpected spaces around keyword / parameter equals
39:96: E251 unexpected spaces around keyword / parameter equals
39:123: E251 unexpected spaces around keyword / parameter equals
39:125: E251 unexpected spaces around keyword / parameter equals
39: D102 Docstring missing
43:5: E303 too many blank lines (2)
43: D208 Docstring is over-indented
61: D102 Docstring missing
64: D102 Docstring missing
67: D102 Docstring missing
70: D102 Docstring missing


1: D100 Docstring missing
20:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.legacy.search_engine
23:1: E302 expected 2 blank lines, found 1
23: D203 Expected 1 blank line *before* class docstring, found 0
23: D400 First line should end with '.', not 'g'
23: D205 Blank line missing between one-line summary and description
23: D208 Docstring is over-indented
53: D102 Docstring missing
57:5: E303 too many blank lines (2)
57: D102 Docstring missing
70:60: W601 .has_key() is deprecated, use 'in'
72:39: E127 continuation line over-indented for visual indent
73:47: W601 .has_key() is deprecated, use 'in'
80: D400 First line should end with '.', not 'd'
80: D205 Blank line missing between one-line summary and description


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
25:1: I100 Imports statements are in the wrong order. import logging should be before import sys
27:1: I100 Imports statements are in the wrong order. import re should be before import urllib2
31:1: I101 Imported names are in the wrong order. Should be CFG_BIBINDEX_FULLTEXT_INDEX_LOCAL_FILES_ONLY, CFG_BIBINDEX_SPLASH_PAGES, CFG_SOLR_URL, CFG_XAPIAN_ENABLED
31:1: I100 Imports statements are in the wrong order. from invenio.config should be before from six
32:6: E126 continuation line over-indented for hanging indent
37:1: I100 Imports statements are in the wrong order. from invenio.legacy.websubmit.file_converter should be before from invenio.utils.html
38:1: I100 Imports statements are in the wrong order. from invenio.legacy.miscutil.solrutils_bibindex_indexer should be before from invenio.legacy.websubmit.file_converter
40:1: I101 Imported names are in the wrong order. Should be BibRecDocs, InvenioBibDocFileError, bibdocfile_url_p, bibdocfile_url_to_bibdoc, download_url
40:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibdocfile.api should be before from invenio.legacy.miscutil.xapianutils_bibindex_indexer
41:6: E126 continuation line over-indented for hanging indent
45:1: I100 Imports statements are in the wrong order. from invenio.ext.logging should be before from invenio.legacy.bibsched.bibtask
46:1: I100 Imports statements are in the wrong order. from intbitset should be before from invenio.ext.logging
46:1: I201 Missing newline before sections or imports.
47:1: I201 Missing newline before sections or imports.
49:29: E261 at least two spaces before inline comment
52: D203 Expected 1 blank line *before* class docstring, found 0
52: D208 Docstring is over-indented
52: D200 One-line docstring should not occupy 3 lines
57:41: E251 unexpected spaces around keyword / parameter equals
57:43: E251 unexpected spaces around keyword / parameter equals
57:66: E251 unexpected spaces around keyword / parameter equals
57:68: E251 unexpected spaces around keyword / parameter equals
57:94: E251 unexpected spaces around keyword / parameter equals
57:96: E251 unexpected spaces around keyword / parameter equals
57:123: E251 unexpected spaces around keyword / parameter equals
57:125: E251 unexpected spaces around keyword / parameter equals
57: D102 Docstring missing
60:49: E127 continuation line over-indented for visual indent
61:49: E127 continuation line over-indented for visual indent
62:49: E127 continuation line over-indented for visual indent
64: D401 First line should be imperative: 'Allow', not 'Allows'
64: D400 First line should end with '.', not 'g'
68: D400 First line should end with '.', not 'r'
73:5: E303 too many blank lines (2)
73: D401 First line should be imperative: 'Return', not 'Returns'
73: D400 First line should end with '.', not 'y'
73: D205 Blank line missing between one-line summary and description
73: D208 Docstring is over-indented
101:28: E713 test for membership should be 'not in'
158:66: E261 at least two spaces before inline comment
185:5: E303 too many blank lines (2)
185: D102 Docstring missing
189:5: E303 too many blank lines (2)
189: D102 Docstring missing
192: D102 Docstring missing
194:1: W391 blank line at end of file


1: D400 First line should end with '.', not 's'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
26: D203 Expected 1 blank line *before* class docstring, found 0
26: D208 Docstring is over-indented
26: D200 One-line docstring should not occupy 3 lines
31:41: E251 unexpected spaces around keyword / parameter equals
31:43: E251 unexpected spaces around keyword / parameter equals
31:66: E251 unexpected spaces around keyword / parameter equals
31:68: E251 unexpected spaces around keyword / parameter equals
31:94: E251 unexpected spaces around keyword / parameter equals
31:96: E251 unexpected spaces around keyword / parameter equals
31:123: E251 unexpected spaces around keyword / parameter equals
31:125: E251 unexpected spaces around keyword / parameter equals
31: D102 Docstring missing
35:5: E303 too many blank lines (2)
35: D401 First line should be imperative: 'Tokenize', not 'Tokenizes'
35: D400 First line should end with '.', not 'y'
46: D102 Docstring missing
49: D102 Docstring missing
52: D102 Docstring missing
55: D102 Docstring missing


this is the one


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
30:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.modules.indexer.tokenizers.BibIndexMultiFieldTokenizer
50: D203 Expected 1 blank line *before* class docstring, found 0
50: D205 Blank line missing between one-line summary and description
50: D208 Docstring is over-indented
60:41: E251 unexpected spaces around keyword / parameter equals
60:43: E251 unexpected spaces around keyword / parameter equals
60:66: E251 unexpected spaces around keyword / parameter equals
60:68: E251 unexpected spaces around keyword / parameter equals
60:94: E251 unexpected spaces around keyword / parameter equals
60:96: E251 unexpected spaces around keyword / parameter equals
60:123: E251 unexpected spaces around keyword / parameter equals
60:125: E251 unexpected spaces around keyword / parameter equals
60: D102 Docstring missing
67:5: E303 too many blank lines (2)
67: D400 First line should end with '.', not 's'
67: D205 Blank line missing between one-line summary and description
112: D401 First line should be imperative: 'Tokenize', not 'Tokenizes'
112: D205 Blank line missing between one-line summary and description
128: D102 Docstring missing
131: D102 Docstring missing
134: D102 Docstring missing
137: D102 Docstring missing
140: D102 Docstring missing


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
26:1: F401 'CFG_BIBINDEX_INDEX_TABLE_TYPE' imported but unused
31:1: E303 too many blank lines (3)
31: D203 Expected 1 blank line *before* class docstring, found 0
31: D205 Blank line missing between one-line summary and description
31: D208 Docstring is over-indented
59:41: E251 unexpected spaces around keyword / parameter equals
59:43: E251 unexpected spaces around keyword / parameter equals
59:66: E251 unexpected spaces around keyword / parameter equals
59:68: E251 unexpected spaces around keyword / parameter equals
59:94: E251 unexpected spaces around keyword / parameter equals
59:96: E251 unexpected spaces around keyword / parameter equals
59:123: E251 unexpected spaces around keyword / parameter equals
59:125: E251 unexpected spaces around keyword / parameter equals
59: D400 First line should end with '.', not 'y'
59: D205 Blank line missing between one-line summary and description
59: D208 Docstring is over-indented
68:5: E303 too many blank lines (2)
68: D401 First line should be imperative: 'Pick', not 'Picks'
68: D400 First line should end with '.', not ')'
73:5: E303 too many blank lines (2)
73: D102 Docstring missing
76: D102 Docstring missing
79: D102 Docstring missing
81:1: W391 blank line at end of file


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
33: D203 Expected 1 blank line *before* class docstring, found 0
33: D205 Blank line missing between one-line summary and description
33: D208 Docstring is over-indented
50:41: E251 unexpected spaces around keyword / parameter equals
50:43: E251 unexpected spaces around keyword / parameter equals
50:66: E251 unexpected spaces around keyword / parameter equals
50:68: E251 unexpected spaces around keyword / parameter equals
50:94: E251 unexpected spaces around keyword / parameter equals
50:96: E251 unexpected spaces around keyword / parameter equals
50:123: E251 unexpected spaces around keyword / parameter equals
50:125: E251 unexpected spaces around keyword / parameter equals
50: D102 Docstring missing
54:5: E303 too many blank lines (2)
54: D400 First line should end with '.', not 'e'
54: D205 Blank line missing between one-line summary and description
54: D208 Docstring is over-indented
60: D102 Docstring missing
63: D102 Docstring missing
66: D102 Docstring missing
69: D102 Docstring missing


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
29:1: E303 too many blank lines (3)
29: D203 Expected 1 blank line *before* class docstring, found 0
29: D205 Blank line missing between one-line summary and description
29: D208 Docstring is over-indented
43:41: E251 unexpected spaces around keyword / parameter equals
43:43: E251 unexpected spaces around keyword / parameter equals
43:66: E251 unexpected spaces around keyword / parameter equals
43:68: E251 unexpected spaces around keyword / parameter equals
43:94: E251 unexpected spaces around keyword / parameter equals
43:96: E251 unexpected spaces around keyword / parameter equals
43:123: E251 unexpected spaces around keyword / parameter equals
43:125: E251 unexpected spaces around keyword / parameter equals
43: D400 First line should end with '.', not 'y'
43: D205 Blank line missing between one-line summary and description
43: D208 Docstring is over-indented
52:5: E303 too many blank lines (2)
52: D401 First line should be imperative: 'Pick', not 'Picks'
52: D400 First line should end with '.', not ')'
57:5: E303 too many blank lines (2)
57: D102 Docstring missing
60: D102 Docstring missing
63: D102 Docstring missing
65:1: W391 blank line at end of file


If you extend `TestCaseWithArtifactGeneration`, you can easily generate artifacts, as it has the necessary methods.


test


Thanks!


you're absolutly right


r+


Looks like this might be worth refactoring into a general util method


This makes the later check in _validateDocument fail with the following error:  "Match error: Expected object, got string in field query"


The MahApps entry was doubled. I really love MahApps.Metro but I think that some other libraries would get mad if I mention MahApps.Metro two times :D


this might be refactored out as well, so it can be used to refresh the data for whatever reason.

2 - files

execute_parser.rb and gem install (this could also be collapsed into our bundle for the api later)


There shouldn't be such a case as there aren't any completions then the completion session won't get triggered. But I'll add a condition check just in case:)


Somehow, an account for which I completely forgot existed made this commit instead of my account. This makes no sense, as I lost the password for that account a while back. It shouldn't even have write access to this repo. What.


That sounds reasonable to me.  Maybe we could support a system property for overriding it, just in case?  I.e. if 'nio' use NIO, otherwise use native if available.


Можно писать код, Синхронизировать версии. Вот сейчас ты коммент к файлу бахнул.


:+1:  hehe  :dancers:


and by the way, cool project!


Fixed. I downloaded dependence with http://gradleplease.appspot.com/ I thought they were there to date.


А, разделитель. Глянь В истории версий как оно на деле без пробела выглядело.


It might make more sense if this were called `django-adminclassviews`, or something similar.


front end team has naming convention oNet -- may need to get on the same page with namespacing / formatting.


This could be `AdminClassBasedViewsMixin` or something.


Overall, not too bad (42 fails in total) but I got no timeouts and the quality of the images seems pretty good. I am going to remove the error threshold - it will just annoy people if they have to keep restarting the download.


hola


Ok, that is pretty nice.  Wasn't aware of `__new__`, that's pretty sweet.  I wonder if bringing the window back to focus shouldn't trigger a refresh though - or is that handled elsewhere in the background?


Yes, which is why my comment is specifically on the 263cabd1c27977aa32c849ffb334984e8d476b97 commit.


This commit causes issues when using an `ons-navigator` as the split view's main page. Specifically, when calling `pushPage()` with either of the slide animations, the overflow is visible on the secondary page.

What issue was this commit fixing?

I can work around this by using:

```css
onsen-split-view__main {
    overflow: hidden !important;
}
```

but I'm wondering if this is a bug that should be addressed?


Fixes #158


Need to find a cleaner way to add headers for generic json endpoints


If we're mainly using magiccards.info it may may sense to set the manual override to that site, especially as @melvinzhang is looking at a way of getting them all on that site anyway.


This method should probably be named `git_repository_hooks_discover`, since it does the work for all hooks and actually creates a `git_repository_hooks` object.


r+


Thanks :)


Would it be easier to use .map here?


Found the issue. These lines can't be commented inline. The assembler is trying to read the comment as part of the string.
Fixed by d71c462ec70fede42e78ca50a0a982b95a28289f


I think that's fair. I think my concern is that without some careful thinking it's easy to get a confusing/hard to reason about API if you have extension methods that express functionality that more reasonably belongs to the unit of abstraction. In this case, I'd argue that if a class has a collection of properties, either its collection of properties or the class itself should handle finding named properties.

I view some of the OData.Net apis, which are full of tag interfaces augmented with extensions, as a bit of a cautionary tale here. In my view, some of the operations on the EDM (like parsing an edm document to get its annotations) could have been radically simplified if they just put fields + properties where they belonged instead of tacking them on as an extension method. Consider evaluating expressions as a good example of this: If `IEdmValue` had a simple member of `object Value {get;}`, hundreds of lines of code could be removed.


thanks @zenorocha, meant to ping you later but I've been dragged away to other things! you're awesome! obrigada =)


may want to comment to on reasoning for indexing


invalid routine name. Fixed by 0937b7b4e9d1e1031faf0c1921547042fbef7ea8


Sorry for noticing this late. This line should be gone.


Ska vara mergat. Om inte så är fallet, fixar jag det bums.


These err_ routines don't check for the error, they simply handle errors once they occur. In essence, it looks like you're throwing these errors every time divide is called, regardless of if there is an error or not.


Line https://github.com/xwiki/xwiki-platform/commit/3d6389874d082d9f7bdca1cf10f78138a5e61fc5#diff-e0c62de31c15b17d68f4a71711fabbd7R83 does indeed take care of an extra `/` coming from an "old" configuration, so it is backwards compatible in the sense that an old configuration won't break the system. What I'm trying to say is that this changes the format of a configuration key, and one that's actually part of a set of properties. `xwiki.servletpath` and `xwiki.defaultservletpath` still require a trailing slash, which is not consistent.


since material drawer already depends on app-compat-v7 the easier way would be to use ?attr/selectableItemBackground instead of ?android:attr/selectableItemBackground


What if more rows are added to the queue while we're processing?
I think we can just expand the scope of the [count](https://github.com/LogBlock/LogBlock/blob/51fdff20a72ece44d8f36c041533cd765a034cad/src/main/java/de/diddiz/LogBlock/Consumer.java#L302) variable and use that


TLDR: this isn't a bug report, just an observation.


Okay. I really like those semantics. :+1:


This runtime-overhead of this is probably ridiculously low (compared with the necessary `stat` calls), but is there a reason this isn't a `static const char* const` array?


The result needs to be checked to see if an error actually occurred.
Also, calculate will be called with jal, so it should return to $ra when it is complete (unless an error occurred)


A autoria deste `commit` está sob o email ` andrejmfreitas@gmail.com`, e não pela sua conta, olhei e o email que vc usa no `github` é o `hotmail`. Para ganhar a autoria deste, deves adicionar teu `gmail` na tua conta


Even if you didn't change it to what I suggested, it probably would be more informative for a person reading any code which utilizes this mixin if the name of the mixin somehow tied it to admin views. For example, `ExtraAdminViewsMixin`.


shit. Okay ill fix it.

On Fri, Mar 20, 2015 at 1:37 PM, zcmoore <notifications@github.com> wrote:

> These err_ routines don't check for the error, they simply handle errors
> once they occur. In essence, it looks like you're throwing these errors
> every time divide is called, regardless of if there is an error or not.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/zcmoore/Toy-Calculator/commit/34601014cd20d87fd911581d5235a0f138379853#commitcomment-10323970>
> .
>


Yay!

I'm not sure how important it is to support 2.x style "print" statements either. For now, it should treat that style of print as "keyword identifier" sequence. So it probably will get it right be default.

Let's burn that bridge when and if we come to it.


@davehensley Creating non-functional installations when installed with composer seems bad too. We could add another fallback path that restored the old value. Would that work for you?


E ai John! Massa, deu pra vc ver a proposta de mudança... mas isso nao foi incorporado no seu projeto, só no fork do seu projeto aqui no meu github... manja?
como será que faz para incorporar no seu, se vc concordar com a mudança?


It looks like you left in the placeholder functionality. Your code below will never be reached.

Fixed by 0937b7b4e9d1e1031faf0c1921547042fbef7ea8


pls contact


> especially as @melvinzhang is looking at a way of getting them all on that site anyway.

Well I wish he would hurry up! :smile:

For now if we use a mapping file in INPUT you can enter what ever link you want and also change it at any time in future. As long as there a only a relatively small set of cards that need updating of course it should not be too onerous.


86046200_CondenserToZone_New (Nigusse) - x86_64-MacOS-10.9-clang: OK (1669 of 1674 tests passed)

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


Hey team,
Would you guys want to all hop on Skype once Justin is off the road and available this evening? Then we can iron out residual bugs in realtime instead of over email
-Frank

Date: Fri, 20 Mar 2015 13:39:39 -0700
From: notifications@github.com
To: Toy-Calculator@noreply.github.com
Subject: Re: [Toy-Calculator] Update calculator.asm (3460101)

shit. Okay ill fix it.

On Fri, Mar 20, 2015 at 1:37 PM, zcmoore <notifications@github.com> wrote:

> These err_ routines don't check for the error, they simply handle errors

> once they occur. In essence, it looks like you're throwing these errors

> every time divide is called, regardless of if there is an error or not.

>

> —

> Reply to this email directly or view it on GitHub

> <https://github.com/zcmoore/Toy-Calculator/commit/34601014cd20d87fd911581d5235a0f138379853#commitcomment-10323970>

> .

>

—
Reply to this email directly or view it on GitHub.


-> should be

    For more information about ranking functions look at the [Ranking function documentation](https://developers.coveo.com/display/SearchREST/Ranking+Function)


It is easier for the Writer to interpret a list of OdcmCapability associated with a OdcmProperty (Via OdcmProjection).
I assume by named-tuple solution you mean OdcmVocabularyAnnotation. It is just a strongly typed CLR object for an annotation. And somewhere we still need to further interpret that annotation in way that it is easier for the writers to consume.


This also addresses #244


True, hehe - Once I'm done I'll put a list together


I cant do it over skype until sunday when i get back home. I will be
available over text or email all weekend though

On Fri, Mar 20, 2015 at 1:41 PM, frankdavidson <notifications@github.com>
wrote:

> Hey team,
> Would you guys want to all hop on Skype once Justin is off the road and
> available this evening? Then we can iron out residual bugs in realtime
> instead of over email
> -Frank
>
> Date: Fri, 20 Mar 2015 13:39:39 -0700
> From: notifications@github.com
> To: Toy-Calculator@noreply.github.com
> Subject: Re: [Toy-Calculator] Update calculator.asm (3460101)
>
> shit. Okay ill fix it.
>
>
>
> On Fri, Mar 20, 2015 at 1:37 PM, zcmoore <notifications@github.com> wrote:
>
>
>
> > These err_ routines don't check for the error, they simply handle errors
>
> > once they occur. In essence, it looks like you're throwing these errors
>
> > every time divide is called, regardless of if there is an error or not.
>
> >
>
> > —
>
> > Reply to this email directly or view it on GitHub
>
> > <
> https://github.com/zcmoore/Toy-Calculator/commit/34601014cd20d87fd911581d5235a0f138379853#commitcomment-10323970
> >
>
>
> > .
>
> >
>
>
>
> —
> Reply to this email directly or view it on GitHub.
>
>
>
>
>
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/zcmoore/Toy-Calculator/commit/34601014cd20d87fd911581d5235a0f138379853#commitcomment-10324027>
> .
>


86046200_CondenserToZone_New (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1675 of 1680 tests passed)

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


@rouge8 @dcreager @mnichols  Please review


static links suck.


.each вместо for


Thanks for spotting that!


This cannot be right - there's no statbuf in scope here.


Можно в модели вычислять "случайную" фотку из галереи и отдавать ее ссылку в шаблон.


Yes, but that still depends on having a request in the first place. [`ServletContextListener`](http://docs.oracle.com/javaee/6/api/javax/servlet/ServletContextListener.html) provides access to the `ServletContext` directly, when the application is started. Since that is an interface, it can either be added to this class (`ExtendedURLURLNormalizer`), or to another helper class that can be used to keep information about the URL configuration, including all the URL configuration currently allowed in `xwiki.cfg`.

As a comment, I don't like that the URL configuration happens here, I would like to see a separate class for the configuration.


Shouldn't this be public as other programs should be able to crash BitByte.exe


.each!


This should probably be hidden as an implementation detail and a public getter method should be added. Otherwise there might be binary incompatible issues, if a hook is added / removed / reordered.


This should be a separate test (above this block) that tests if either guid or name are NULL and sets errno to EINVAL; there's no reason to mix it with the test described in this comment.


86046200_CondenserToZone_New (Nigusse) - 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)


No worries! The rest of us should hop on at some point this evening though, I'll basically be on my computer the rest of today lol.
-Frank

Date: Fri, 20 Mar 2015 13:43:15 -0700
From: notifications@github.com
To: Toy-Calculator@noreply.github.com
CC: frankdavidson@live.com
Subject: Re: [Toy-Calculator] Update calculator.asm (3460101)

I cant do it over skype until sunday when i get back home. I will be

available over text or email all weekend though

On Fri, Mar 20, 2015 at 1:41 PM, frankdavidson <notifications@github.com>

wrote:

> Hey team,

> Would you guys want to all hop on Skype once Justin is off the road and

> available this evening? Then we can iron out residual bugs in realtime

> instead of over email

> -Frank

>

> Date: Fri, 20 Mar 2015 13:39:39 -0700

> From: notifications@github.com

> To: Toy-Calculator@noreply.github.com

> Subject: Re: [Toy-Calculator] Update calculator.asm (3460101)

>

> shit. Okay ill fix it.

>

>

>

> On Fri, Mar 20, 2015 at 1:37 PM, zcmoore <notifications@github.com> wrote:

>

>

>

> > These err_ routines don't check for the error, they simply handle errors

>

> > once they occur. In essence, it looks like you're throwing these errors

>

> > every time divide is called, regardless of if there is an error or not.

>

> >

>

> > —

>

> > Reply to this email directly or view it on GitHub

>

> > <

> https://github.com/zcmoore/Toy-Calculator/commit/34601014cd20d87fd911581d5235a0f138379853#commitcomment-10323970

> >

>

>

> > .

>

> >

>

>

>

> —

> Reply to this email directly or view it on GitHub.

>

>

>

>

>

>

> —

> Reply to this email directly or view it on GitHub

> <https://github.com/zcmoore/Toy-Calculator/commit/34601014cd20d87fd911581d5235a0f138379853#commitcomment-10324027>

> .

>

—
Reply to this email directly or view it on GitHub.


TeamCity MonoGame :: Develop (Win) [Build 3.4.0.63](http://teamcity.monogame.net/viewLog.html?buildId=5831&buildTypeId=MonoGame_DevelopWin&guest=1) is now running


If there's a case where buf isn't true and rc isn't < 0, read_file should be fixed instead.


Всю папку uploads в .gitignore


Wrong name ;)


FYI if you build with `mvn -P DIST install` it will generate the source and javadoc jars


These changes are controversial, they cause a lot of changes for each edit a file.


That sounds like it would be perfect. Thanks.


This fix also contains some changes to the line endings, so the mixture of \r\n and \n EOL is removed.


This is a markdown file created


develop (macumber) - x86_64-MacOS-10.9-clang: Tests Failed

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


is debug just for sourcemaps, or something else?


82420068_GridViewMultiEdit (evanweaver) - i386-Windows-7-VisualStudio-12: OK (2169 of 2182 tests passed)

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


It would be nice if we had a jshint thing in here too, or maybe as a separate task


test comment


Also to be fixed...


Please don't. There is no good reason in wrapping a link in a `<code>` tag. Plus we lose the ability to wrap Markdown textless-links with `<>`.

I will send another PR to remove these.


Yeah, sorry about that, this is fixed now.


Maybe instead of defaults we should require these and error out if they are missing.


I believe we do not need linkType here, but if you are strong about this, we can refactor later.


should get `getConnection()`


Forgot to change these to format strings. Will fix next commit.


And another one


@dpgeorge : These options broke building with readline enabled:

~~~~
CC input.c
In file included from input.c:36:0:
./readline/readline.h:341:15: error: redundant redeclaration of ‘rl_make_bare_keymap’ [-Werror=redundant-decls]
 extern Keymap rl_make_bare_keymap PARAMS((void));
               ^
In file included from ./readline/readline.h:37:0,
                 from input.c:36:
./readline/keymaps.h:68:15: note: previous declaration of ‘rl_make_bare_keymap’ was here
...
~~~~


You broke the checker somehow with this (I believe)
It's not writing anything http://puu.sh/gIwk5/2174dce3ba.png
(Yes I'm at the correct Region)


also modelMap, metaMap


So I just realized that the navigation property semantics you mention in this comment make some amount of indirection make sense. https://github.com/Sridhar-MS/Vipr/commit/a435778a0c1a44da9590f1a2d8ca747a2ff24e19#commitcomment-10323681

I think it may make more sense to have some code that just parses the annotations and puts them in a place there they can be accessed. (Original proposal; what we had laying around... Where you can call .Annotations to get any annotations added, including things like `Core.Description`) Then have another component that can parse a list of those annotation representations and updates the capabilities in a given model to properly distribute this information.

Even if explicitly dividing this into two steps imposes some perf cost, I'd rather have the annotation parsing and capability processing (the semantics you alluded to above) be entirely seperate. That is, the former piece won't know about `OdcmCapability` and the latter piece shouldn't need to know about the model / expressions. This also means that whatever capability semantics we pick will be easier to debug / test and reason about.

My concern here is that if we don't seperate these two concerns, what will happen is that we'll have some nasty tangled logic we need to reason through to process OdcmCapabilities and we may miss things.


Is there any reason for this?  Or is it a stub for / ?


it's 2015 ? or 2013


But it looks like it's enabling rand roll for chest.. it didn't exist @ vanilla.


82420068_GridViewMultiEdit (evanweaver) - x86_64-Linux-Ubuntu-14.04-clang-3.5: OK (2091 of 2182 tests passed)

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


some tests failed:
failure: http://build.servo.org/builders/linux1/builds/1078


In most code I've treated the key as an opaque string, that happens to be `{random}/{domain}`, but still just a client-generated string.


I don't think you need to do this check. The Comparer does that.


Again i think the comparer won't consider weak-named references equivalent.


saw approval from jdm
at https://github.com/Ms2ger/servo/commit/2cde68f13f997476ffd387fc19b347106b4d7ea4


merging Ms2ger/servo/global_init = 2cde68f1 into auto


Ms2ger/servo/global_init = 2cde68f1 merged ok, testing candidate = 4eb26065


Secondary heading example


TeamCity MonoGame :: Develop (Win) [Build 3.4.0.63](http://teamcity.monogame.net/viewLog.html?buildId=5831&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 461, ignored: 6 Build time: 00:14:04


Missing step: package names to install


82420068_GridViewMultiEdit (evanweaver) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


We shouldn't need this. Travis CI [sets the `CONTINUOUS_INTEGRATION` environment variable](http://docs.travis-ci.com/user/ci-environment/#Environment-variables), which [we use in karma.conf](https://github.com/rackt/react-router/blob/8c6b8a9cc9eb91565be19d6479fa123bde24bea6/karma.conf.js#L8).


yer tis:

```
http://magiccards.info/scans/en/hl/102.jpg [Abbey Matron.jpg]
http://magiccards.info/scans/en/hl/76.jpg [Aliban's Tower.jpg]
http://magiccards.info/scans/en/ai/97.jpg [Balduvian War-Makers.jpg]
http://magiccards.info/scans/en/hl/5.jpg [Cemetery Gate.jpg]
http://magiccards.info/scans/en/hl/92.jpg [Dwarven Trader.jpg]
http://magiccards.info/scans/en/fe/68.jpg [Elven Fortress.jpg]
http://magiccards.info/scans/en/fe/76.jpg [Elvish Scout.jpg]
http://magiccards.info/scans/en/ai/105.jpg [Enslaved Scout.jpg]
http://magiccards.info/scans/en/ps/107a.jpg [Ertai, the Corrupted.jpg]
http://magiccards.info/scans/en/ai/43.jpg [Foresight.jpg]
http://magiccards.info/scans/en/ai/74.jpg [Gift of the Woods.jpg]
http://magiccards.info/scans/en/fe/38.jpg [Homarid.jpg]
http://magiccards.info/scans/en/fe/152.jpg [Icatian Moneychanger.jpg]
http://magiccards.info/scans/en/cstd/27.jpg [Insidious Bookworms.jpg]
http://magiccards.info/scans/en/cstd/4.jpg [Kjeldoran Pride.jpg]
http://magiccards.info/scans/en/tsts/11.jpg [Moorish Cavalry.jpg]
http://magiccards.info/scans/en/ai/177.jpg [Soldevi Steam Beast.jpg]
http://magiccards.info/scans/en/an/14.jpg [Stone-Throwing Devils.jpg]
http://magiccards.info/scans/en/ps/74.jpg [Tahngarth, Talruum Hero.jpg]
http://magiccards.info/scans/en/gp/20.jpg [To Arms!.jpg]
http://magiccards.info/scans/en/hl/124.jpg [Trade Caravan.jpg]
http://magiccards.info/scans/en/ai/88.jpg [Undergrowth.jpg]
http://magiccards.info/scans/en/fe/61.jpg [Vodalian Mage.jpg]
http://magiccards.info/scans/en/po/201.jpg [Warrior's Charge.jpg]
http://magiccards.info/scans/en/hl/73.jpg [Willow Faerie.jpg]
http://magiccards.info/scans/en/mbp/7.jpg [Windseeker Centaur.jpg]
```


You could also do: `if (typeof window != "undefined") {...}` – wouldn't catch something like an undefined variable later on.


Defining extensions feels a little intense for me, vs using the strings inline.


Delete README.md.


This is a very general comment, only marginally related to this PR and is more to be seen as a generic advice for improvement:

When doing something that has absolutely nothing to do with the objective of a given branch / PR, then I'd be a good idea to take that single change, cherry-pick it on top of `development` and either push it directly (like for example with this commit: We've actually agreed doing this, so let's just push it over) or create a separate pull request for it.

I remember that I've recently said that "I never develop on the `development` branch". This is exactly what I mean: I have a very "private" branch and I try to isolate each commit so that it doesn't affect anything else. This allows me to incrementally develop in one branch and (later) distribute the changes into different branches.


This was just moved into the helpers section from above for consistency