Yes, blaming is not helpful at all. So back to why I don't like the patch.

In the light of the last ML discussions about removing old compiler workarounds I don't like the idea of introducing a new workaround for code which can and should be fixed as shown above.

The Qt project finally managed to offer an option to work cleanly with Boost, so this should be the way the user should go. Hard as it might be. Been there, done that.

On the technical side, I think a config macro is absolutely necessary. If only to add support for other compilers, too. I think that Intel supports this, too, but is not covered by BOOST_MSVC.

The last thing I'm against is just throwing the code into the regression tests and see if anything breaks. But this a shortcoming of our regression testing system. Some method to inject patches out-of-line would be great.

Please consider updating the patch and maybe asking for a straw poll on the devel and/or maintenance mailing list.


Okay, well, I figured out that this error was simple typo, so now there's pull request #5 to fix that. Back to the original issue.

*/me rolls sleeves up*


This was fixed in a earlier PR. Please refer to https://github.com/wso2/carbon-event-processing/blob/master/components/adaptors/event-output-adaptor/org.wso2.carbon.event.output.adaptor.rdbms/pom.xml


Please replace the headline with an easier version. Maybe „Using multiple navigations“.


this works for now in small topologies

Later, use the payload to store these. I think its 64-bit for switches and 32-bits for ports or something like that.


The code has mixin some IDE config files~


? Did you mean: LastPositionHash **=** Printer::stepNumber; ?


This fix is now officially included in FA 2.4 Unstable:
http://sourceforge.net/p/frontaccounting/mercurial/ci/3debfe1c9b1ca6217cfe701332007faabe9b9ded/tree/reporting/includes/class.mail.inc?diff=5816f08cb1fec6d257236fbf9dd8047632c60163

https://github.com/apmuthu/frontac24/commit/433626960a27dce1e7228f22e2e1749765f835ca


Or I could write directly to *bspwm*'s socket...


Insert a blank line.


I will remove the 3 lines `pr_debug` below since there is no member `ctx` in `struct device` and it's no meaning to print the pointer of driver.


@chelseaarita, looks good. Only suggestion is to remove the logging, since they're no longer needed.


HVACSizingSim_CoincidentPlant (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: Tests Failed

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


test-only


Please add also a **short** definition for a second navigation. (e.g. `default`)


IDFXT (refaqtor) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: Build Failed

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


> In the light of the last ML discussions about removing old compiler
> workarounds I don't like the idea of introducing a new workaround for
> code which can and should be fixed as shown above.

well, there is a difference between removing support for outdated
compilers and introducing workarounds to ease the use of widely used c++
frameworks.

> On the technical side, I think a config macro is absolutely necessary.
> If only to add support for other compilers, too. I think that Intel
> supports this, too, but is not covered by BOOST_MSVC.

this does not sound too bad. i've provided the workaround for
msvc/gcc/clang, because those are the compilers that i'm able to test with.

> Please consider updating the patch and maybe asking for a straw poll on
> the devel and/or maintenance mailing list.

will post the patch/pr on the list


…and output the second navigation.


The numerical argument to RadioButton is the index of the default value, you know...


No, your recent changes don't fix this issue, sadly. There's still an empty string prepended to the `$urls` array. Turns out it's because the call to `get_post_meta()` will *always* return a string, since you're calling it with the `true` (`$single`) parameter, and as a result, when there's no data in the field, it will return an empty string. So the guard in the `foreach` loop is, indeed, necessary/more robust.

On another note, I've found another unexpected behavior (a bug?) in which deleting the contents of the Syndication Links `<textarea>` in the metabox doesn't actually delete or update the contents of the `syndication_urls` post meta field. This means the *only* way to delete the contents of that field is via the Custom Fields metaboxes, which seems unintended given the fact that the Custom Fields metabox is hidden by default?

I can open a new issue for this if you want and/or see if it's gonna be a lot of work to fix.


What has been changed?


Regarding the exception message, reading it through it seems very tailored to MSMQ (alot our our code base is that for obvious reasons). Being a Rabbit/Asb user I'm not sure eg "if running ServiceControl on a different machine" makes any sense.

Thoughts?

Can we come up with something that is more transport agnostic but still get the message across?


This breaks the compilation on Linux when debug flags are enabled. In line 480 the thread ID is read with SYS_gettid() which needs this header file.

I will comment out the include and the debug statement. Therefore, we can use it on other Posix systems but it will be easy to reactivate it, if it is needed for debugging on Linux.
However, if we ever integrate another Posix system I would also rename the files to show that they are not specific to Linux.


A lot of projects in GH will have the description epmpty; since we have a validation in labs for presence of project description, what is the expected resolution when the sync fails for those cases? Currently we get an error message without any means of correcting the errors, so effectively there is no way to import those projects from GH.


This setting controls the exponential backoff algorithm in the membership oracle, significantly reduces contention on the Azure Silo Instance table and improves start up time for large deployments.
@javier-alvarez reported that this improved the silo startup time significantly in his deployment.


there was never a release 1.0.0beta2.


IDFXT (refaqtor) - 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)


IDFXT (refaqtor) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: Build Failed

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


gfgg


Ok. Az email tárgynevéből arra következtettem, hogy a negatív-ellenőrzés
van rossz helyen .

2015-03-04 7:37 GMT+01:00 thomastrinn <notifications@github.com>:

> Az if(number.isEmpty()}{...} ahogy nézem nem a metódus elején van, hanem a
> List numberList = getNumbers(number);
> validateNumbers(numberList);
> után
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ViktorSarkozi/StringCalculator/commit/d56c26505ae264e37e6c54e83838128e2679fdcb#commitcomment-10023070>
> .
>


IDFXT (refaqtor) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: Build Failed

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


The driver only can be configured 'enable' on ARM or ARM64. So I think it's OK if we don't check architecture.


awesome :) Less code to maintain!


meh


del


89438532_RadianceBugFix (rpg777) - Win64-Windows-7-VisualStudio-12: OK (2198 of 2212 tests passed)

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


It will be great, I know (specially because I use some `NSMapTable` myself), but it will never work (at least in its current form) for arbitrary `NSMapTable`, because the keys and the objects might not even be Obj-C objects.

At the moment I though about looking into `keyPointerFunctions` and `valuePointerFunctions` and compare them against the same values in known configurations of `NSMapTable`, and bail out if we don’t recognize the configuration. A little bit more work than I first though this feature will be.


This was a bug. It should be Invoke() so the error propagates up. I'll fix that and clarify in a comment.


メールの確認が遅れて、アサインボタンを押していませんでした。
以後気をつけます、申し訳ありません。


IMO the methods can be in the ```System.Console``` class.

The tests are fine, it's hard to assert console output but of course it is nice to know that things are spelled correctly.

I don't think, however, that we should include a polyfill; the user can do that himself if s/he needs to support old browsers.


im totaly agree with you and your team that  you are another fucking leecher of wowsource team who stolen work rename and open for public hahha so go fuck your self  trash bad and  penis sucker that you are , if you ask how i know is my core and db well penis sucker  look at the  milions  damage from mobs who buff characters and  modify haste with valor - it makes houndreats of milions damage http://s9.postimg.org/ot9wfja1b/Wo_WScrn_Shot_030415_095005.jpg check the damage from my  characters , also the other thing that it showme is my old world and core is that the npc guids and objects and also  duel gable npc spawn around the world , any way people  we fix this  huge  issues in our core and a beter version then this crap leeched last year can be fiind here https://github.com/WoWSource/WoWSource434  so pee this fucking bastards  between the eyes and let them suck hairy balls LOOOOL. btw if you wish to  contact the real wowsource owner add skype geany_100 or  hes forum http://wowsource.info/


It's asserting that you don't call Rethrow() twice. I have no idea if that's important, this isn't used yet.


y


Shouldn't this be an ||, not an &&?


Dear Hesham, it is great that you have provided this fix! I have copied your fix to my *fo-dicom* fork at [Cureos](https://github.com/cureos/fo-dicom), I hope you don't object to that.

Just a suggestion: wouldn't it be even safer to move the declaration of `frameArray` to the outer scope (before `try`) and place the `delete` in the `finally` block instead, like this:

    PinnedByteArray^ frameArray = nullptr;
    try {
      ...
      frameArray = gcnew PinnedByteArray(frameSize);
      ...
    }
    finally {
      if (frameArray != nullptr) {
        delete frameArray;
        frameArray = nullptr;
      }
      ...
    }

If I am not mistaken, this will ensure that `frameArray` gets properly cleaned up even if an exception occurs in the latter part of the `try` block.

What do you think?

Best regards,
Anders @ Cureos


I am fixing this pull request, so could you please not merge it yet?


yes.. stolen from httpp://google.com/404


教务处连不上不代表选课不能用对吧=￣ω￣=


Ok let me have a squiz.

Well you need to change the tools view to the tools/localfilter.html and localfilter needs to be edited as well to remove the ng-if mode = search. That's all i've noticed so far. I'll keep lookin'


HVACSizingSim_CoincidentPlant (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (630 of 630 tests passed)

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


QwtUpdate (macumber) - i386-Windows-7-VisualStudio-12: OK (2155 of 2202 tests passed)

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


was trying to do something that the original serializer did not allow but forgot what.


am scris ieri în asta și văd că nu s-a salvat.
da, nu putem să punem relcl ca o subdiviziune a acl pentru că relcl apar și ca ccomp sau altceva, deci subdiviziunea nu e corectă susțin propunerea să nu o aplicăm.


Thanks Thyrus!


en


Yes, but when you rebase and git push -f, you overwrite commits history and everyone's `composer.lock' file does not work.

I think libraries should keep its commits history if possible.


Good catch, thanks :)
I'm fixing this.


Inlining these isn't a good idea from a readability standpoint.

This definitely isn't a good way of doing this, but it's better than having a huge pile of magic numbers. A better approach might be to have a class "HorizontalLayout" which extends Group, with semantics vaguely similar of Android's HorizontalLayout.


qwe


to_representation is called when returning the JSON back to the client. this returns urls for all products in tradeIn/tradeFor.
instance.tradeIn is a ManyToManyRelatedManager, can not be serializers by default.


can be done.


Le petit pipou qui va bien !


Create a text file


It's only my design decision. According to the specification, there should be content of the element //xccdf:test-result/xccdf:instance. I don't know what to do if there is no element //xccdf:test-result/xccdf:instance. But I think that this is only a temporary problem. The next work for me would be to write some code to provide the //xccdf:test-result/xccdf:instance element every time. I'll see, maybe we will place there "return 1;" then.


Cette ligne change là par :
``'route' => '/table/[id]',``


why should I remove it ?


altceva: aceste pronume, adverbe și adjective relative au funcție în propoziție și ele trebuie subordonate de cuvântul regent în propoziția pe care o introduc și scris ce funcție au, nsubj, dobj sau, în cazu adverbelor, advmod.
de ce in UD am văzut că pronumele relative sunt nsubj, dobj iar when este mark?
propun să le analizăm pe toate, așa am și conceput tabelul meu de transpunere care nu e gata, va fi cam pe duminică seara.


will change the Rejected flow.
not sure what Closed actually is..


Yes, but sometimes there are good reasons for `push -f`.


fast-forwarding develop to borshop-integration-1076-feature/cs-debug-cuttlefish = 35bdf211


register 不应该有些返回.


Thanks for fast recovery!


Sure. As soon as we have the packages :-)


variable names


Noticed that you added ```--no-scripts``` option to the composer command. This, to me, presents a problem especially with symfony projects because the ```app/console``` script references a ```bootstrap.php.cache``` file which has yet to be created. All other tasks that rely on the ```app\console``` script fail e.g. the ```deploy:assetic``` task. Further, the applications front controller for generic symfony applications also references the bootstrap file.

What was the rationale behind disabling execution of composer scripts? What workaround is there to perform those actions that the composer scripts would do?

Thanks,
Njenga

P.S. Love this project.


88621024-ElectricLoadCenterStorageBattery-Crash (jasondegraw) - Win64-Windows-7-VisualStudio-12: Tests Failed

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


Ah.. Sweet Python.


I don’t think that we need to post them in the future. I was still trying to figure out how Unity and Github interact. I wonder if we can actual ignore Library/metadata in GitHub?


I have extended ```ros_mongodb-log``` and ```designator_integration``` to also handle these types for the SAPHARI demonstrator. Unfortunately, the data did not show up in the actual mongodb. Therefore, I have not issued a pull request, yet. I will look into this after all these crazy paper deadlines are up..


Hi Frederico,

No problem about it and *really* not your fault. It's something I have to bug report to Inkscape developpers ( why Linux version can't auto convert path like ```..\gfx``` into ```../gfx``` ? ... coding-wise it doesn't feel like a huge code patch to do... ).

Please do continue to work in the most confortable environment for you. I reopen each SVG here anyway to adjust speechbubbles size, and review if my Inkscape can read all properly before launching a bash rendering of everything. Converting the link slash/backslash is just a bunch of click with a search/replace in all documents, something trivial.

Thanks again for being the first to complete all the translations ! and for doing it via Github 'pull request'.


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

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


OK I understand. maybe you wanted to reduce repository size or something.


lol


Looks like we are using a wrong icon here in AvailableGPXFragment.java: Instead of ic_play_dark.png, which is a "Play" type button, it appears we should be using something like monitoring_rec_big.png or monitoring_rec_small.png, which is a recording type red dot.

A second issue is that once you stop the GPX recording (either in AvailableGPXFragment.java or using the GPX recording widget on the map screen), then in AvailableGPXFragment.java the "save" button is missing, which should probably always be displayed there once the current rack is not empty.


Кажется, я забыл Game1 отправить.


This I'm not sure about. Right now, my understanding is that it's better to decode('utf_8') when you get data into the script and encode('utf_8') when you write it to a file or return it to the browser, but not encoding anything while it is being processed and handled internally. This version with both encode() on URL and summary and a separate encode() when writing to file seems like it will double-encode data. Or?


Ok wait imma push something as well but still cant figure out how to filter it, the filter isn't getting passed to the favs list


Same question regarding these encode() calls..


Add a fork here.  If the delay is too long, throw out OS_LOG_ALERT instead


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

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


+1 for @urecio


[SideCI/RailsBestPractices] replace instance variable with local variable
reference: http://rails-bestpractices.com/posts/2010/07/24/replace-instance-variable-with-local-variable/


[SideCI/RailsBestPractices] restrict auto-generated routes workflow/routes (only: [])
reference: http://rails-bestpractices.com/posts/2011/08/19/restrict-auto-generated-routes/


Yeah, in general 32-bit links should only be installed for the 32-bit version, and 64-bit links only for the 64-bit version. Similar to the (broken) comparison in line 36 of this file. I'll come up with something.


The commit comment suggests JSONP support was removed entirely. However, the `:set_jsonp_format` filter is still present and active. Shouldn't that be removed as well?


I wanted to drop the test case for unresolved element <instance>, which is resolved now :-) You can put only <sub> or <instance> in Benchmark/Rule/fix. If you put any other element there, OpenSCAP will raise an error:

[jcerny@t440s unittests]$ oscap xccdf validate test_remediation_subs_unresolved.xccdf.xml
File 'test_remediation_subs_unresolved.xccdf.xml' line 9: Element '{http://checklists.nist.gov/xccdf/1.2}foo': This element is not expected. Expected is one of ( {http://checklists.nist.gov/xccdf/1.2}sub, {http://checklists.nist.gov/xccdf/1.2}instance ).
OpenSCAP Error: Invalid XCCDF Checklist (1.2) content in test_remediation_subs_unresolved.xccdf.xml. [oscap_source.c:205]

Maybe we can write some new test which tests this error message.


Hi,

Tried your latest commit but I still have the issue.

2015-03-04 1:32 GMT+01:00 Gregory Roussac <notifications@github.com>:

> In deed i addedd two test products I forgot. All right ! Cheers !
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/PrestaShop/PrestaShop/commit/27e4841246ad0df00b65d6d3fcbadc50576db18d#commitcomment-10019935>
> .
>


Good grief. I probably need to clean up a bit. Here and there. But for this I need to create tests, to be sure to not break things in the wake of strange strings. I have a tendency to be extract careful in python 2.7 which is working internally in unicode aka `u'something'`.


This spec is still missing the %changelog section:

%changelog
* Sun Oct 06 2013  Elan Ruusamäe <glensc@gith.ub>
- Initial checkin

I'm reusing this spec and I want to show that I am reusing what you did.


I'll try to find some time soon (whatever that means) to prepare a small update for CRAN.
Sorry for the delays -- time is a scarce resource.


I wouldn't go so far as to say perfect :) It took me a while to learn what the `Msg` class was up to and how these enums affected it.


So if I understand well, with the latest commit you have Undefined offset PHP Notice ?


Whoops. Did not see that!

And I believe you're adding topic_id to @post instance. I was wondering how to associate ```current_user``` in that line but couldn't figure it out so I used. You're code is much more readable. Thank you!


I don't know about the overhead, but instead of creating and running a new goroutine, you could also `ReplaceAndClose` the old client after you release the `Unlock` in line 165.


commentaire dans "write" n c'est un commentaire pour un commit


Yeah the series not displaying was @SchizoDuckies fault for making the H3 text position:absolute for the posters in adding.


Listen, this file .gitignore what does it do ?


So it turns out it wasn't that hard to fix. I opened a new pull request, #6. Now I'm going to bed. Later.


when there is no default_coafile.


I didnt have any notice.

2015-03-04 9:27 GMT+01:00 Jocelyn Fournier <notifications@github.com>:

> So if I understand well, with the latest commit you have Undefined offset
> PHP Notice ?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/PrestaShop/PrestaShop/commit/27e4841246ad0df00b65d6d3fcbadc50576db18d#commitcomment-10024240>
> .
>


strcpy copied including the null terminator,, you don't need to terminate by hand


Looks like this commit actually made $memoryCheckFactor obsolete. Unless this variable is still in use somewhere else, it should be removed. (Just got bitten by this when debugging memory issues.)

/cc @horst-n


Awesome! Thank you!


HVACSizingSim_CoincidentPlant (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1124 of 1130 tests passed)

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


This would work, but is a bit hackish. Normally, no-one should dereference the 'end' iterator.
In this case you know the implementation of the iterator, and you know for sure that there is one extra element, so it's OK.


Issues #142 is not causes by this. In fact, this is the first step to be able to fix #141.


Hello,

I've done this module about 3 years ago. It's not maintened anymore but it's open sourced and free :)


Finally got around to doing it properly as a tag and handling the path the same way as other song assets.  https://github.com/stepmania/stepmania/commit/0318f07d2ddcc330e424e56e4e357cfaf27630bc


Hmmm. I think you right. Instead of `--no-scripts` it must be `--no-interaction`.


当コミットで以下も行いました(コミットコメントに書き忘れておりました)

Command.isExecuted()の削除
Command.margeCommand()の削除
DrawingLogicとArtboardCommandLogicの　undo/redo は戻り値を返すようにしました


Yes. This header file should be removed.


this should be assert, right?


Nice!


ok, but 0 for every manufacturers.
Could you try to echo the query line 190, execute it, and paste the result here ?


Thanks man. I really do enjoy having you in our team :+1:


# MacDown

![1](wenzy/下载/IMG_0877.JPG)

Hello there! I’m **MacDown**, the open source Markdown editor for OS X.

Let me introduce myself.

## Markdown and I

**Markdown** is a plain text formatting syntax created by John Gruber, aiming to provide a easy-to-read and feasible markup. The original Markdown syntax specification can be found [here](http://daringfireball.net/projects/markdown/syntax).

**MacDown** is created as a simple-to-use editor for Markdown documents. I render your Markdown contents real-time into HTML, and display them in a preview panel.

![MacDown Screenshot](http://d.pr/i/10UGP+)

I support all the original Markdown syntaxes. But I can do so much more! Various popular but non-standard syntaxes can be turned on/off from the [**Markdown** preference pane](#markdown-pane).

You can specify extra HTML rendering options through the [**Rendering** preference pane](#rendering-pane).

You can customize the editor window to you liking in the [**Editor** preferences pane](#editor-pane):

You can configure various application (that's me!) behaviors in the [**General** preference pane](#general-pane).

## The Basics
Before I tell you about all the extra syntaxes and capabilities I have, I'll introduce you to the basics of standard markdown. If you already know markdown, and want to jump straight to learning about the fancier things I can do, I suggest you skip to the [**Markdown** preference pane](#markdown-pane). Lets jump right in.

### Line Breaks
To force a line break, put two spaces and a newline (return) at the end of the line.

	These lines
	won't break

	These lines
	will break

### Strong and Emphasize

**Strong**: `**Strong**` or `__Strong__` (Command-B)
*Emphasize*: `*Emphasize*` or `_Emphasize_`[^emphasize] (Command-I)

### Headers (like this one!)

	Header 1
	========

	Header 2
	--------

or

	# Header 1
	## Header 2
	### Header 3
	#### Header 4
	##### Header 5
	###### Header 6

### Links and Email
#### Inline
Just put angle brackets around an email and it becomes clickable: <uranusjr@gmail.com>
`<uranusjr@gmail.com>`

Same thing with urls: <http://macdown.uranusjr.com>
` <http://macdown.uranusjr.com>`

Perhaps you want to some link text like this: [Macdown Website](http://macdown.uranusjr.com "Title")
`[Macdown Website](http://macdown.uranusjr.com "Title")` (The title is optional)

#### Reference style
Sometimes it looks too messy to include big long urls inline, or you want to keep all your urls together.

Make [a link][arbitrary_id] `[a link][arbitrary_id]` then on it's own line anywhere else in the file:
`[arbitrary_id]: http://macdown.uranusjr.com "Title"`

If the link text itself would make a good id, you can link [like this][] `[like this][]`, then on it's own line anywhere else in the file:
`[like this]: http://macdown.uranusjr.com`

[arbitrary_id]: http://macdown.uranusjr.com "Title"
[like this]: http://macdown.uranusjr.com

### Images
#### Inline
`![Alt Image Text](path/or/url/to.jpg "Optional Title")`
#### Reference style
`![Alt Image Text][image id]`
on it's own line elsewhere:
`[image id]: path/or/url/to.jpg "Optional Title"`

### Lists

* Unordered lists start each item with a `*`
- `-` works too
	* Indent a level to make a nested list
		1. Ordered lists are supported.
		2. Start each item (number-period-space) like `1. `
		42. It doesn't matter what number you use, I will render them sequentially
		1. So you might want to start each line with `1.` and let me sort it out

Here is the code:

```
* Unordered lists start each item with a `*`
- `-` works too
	* Indent a level to make a nested list
		1. Ordered lists are supported.
		2. Start each item (number-period-space) like `1. `
		42. It doesn't matter what number you use, I will render them sequentially
		1. So you might want to start each line with `1.` and let me sort it out
```

### Block Quote

> Angle brackets `>` are used for block quotes.
Technically not every line needs to start with a `>` as long as
there are no empty lines between paragraphs.
> Looks kinda ugly though.
> > Block quotes can be nested.
> > > Multiple Levels

> Most markdown syntaxes work inside block quotes.
> * Lists
> * [Links][arbitrary_id]
> * Etc.

Here is the code:

```
> Angle brackets `>` are used for block quotes.
Technically not every line needs to start with a `>` as long as
there are no empty lines between paragraphs.
>Looks kinda ugly though.
> > Block quotes can be nested.
> > > Multiple Levels

> Most markdown syntax keeps working even inside block quotes.
> * Lists
> * [Links][id]
> * Etc.
```

### Inline Code
`Inline code` is indicated by surrounding it with backticks:
`` `Inline code` ``

If your ``code has `backticks` `` that need to be displayed, you can use double backticks:
```` ``Code with `backticks` `` ````  (mind the spaces preceding the final set of backticks)

### Block Code
If you indent at least four spaces or one tab, I'll display a code block.

	print('This is a code block')
	print('The block must be preceded by a blank line')
	print('Then indent at least 4 spaces or 1 tab')
		print('Nesting does nothing. Your code is displayed Literally')

I also know how to do something called [Fenced Code Blocks](#fenced-code-block) which I will tell you about later.

### Horizontal Rules
If you type three asterisks `***` or three dashes `---` on a line, I'll display a horizontal rule:

***

## The Markdown Preference Pane
This is where I keep all preferences related to how I parse markdown into html.
![Markdown preferences pane](http://d.pr/i/RQEi+)

### Document Formatting
The ***Smartypants*** extension automatically transforms straight quotes (`"` and `'`) in your text into typographer’s quotes (`“`, `”`, `‘`, and `’`) according to the context. Very useful if you’re a typography freak like I am. Quote and Smartypants are syntactically incompatible. If both are enabled, Quote takes precedence.

### Block Formatting

#### Table

This is a table:

First Header  | Second Header
------------- | -------------
Content Cell  | Content Cell
Content Cell  | Content Cell

You can align cell contents with syntax like this:

| Left Aligned  | Center Aligned  | Right Aligned |
|:------------- |:---------------:| -------------:|
| col 3 is      | some wordy text |         $1600 |
| col 2 is      | centered        |           $12 |
| zebra stripes | are neat        |            $1 |

The left- and right-most pipes (`|`) are only aesthetic, and can be omitted. The spaces don’t matter, either. Alignment depends solely on `:` marks.

#### Fenced Code Block

This is a fenced code block:

```
print ('Hello world!)'
```

You can also use waves (`~`) instead of back ticks (`` ` ``):

~~~
print('Hello world!')
~~~

You can add an optional language ID at the end of the first line. The language ID will only be used to highlight the code inside if you tick the ***Enable highlighting in code blocks*** option. This is what happens if you enable it:

![Syntax highlighting example](http://d.pr/i/9HM6+)

I support many popular languages as well as some generic syntax descriptions that can be used if your language of choice is not supported. See [relevant sections on the official site](http://macdown.uranusjr.com/features/) for a full list of supported syntaxes.

### Inline Formatting

The following is a list of optional inline markups supported:

Option name         | Markup           | Result if enabled     |
--------------------|------------------|-----------------------|
Intra-word emphasis | So A\*maz\*ing   | So Amazing   |
Strikethrough       | \~~Much wow\~~   | Much wow   |
Underline [^under]  | \_So doge\_      | So doge        |
Quote [^quote]      | \"Such editor\"  | <q>Such editor</q>    |
Highlight           | \==So good\==    | So good  |
Superscript         | hoge\^(fuga)     | hogefuga   |
Autolink            | http://t.co      | <http://t.co>         |
Footnotes           | [\^4] and [\^4]: | [^4] and footnote 4   |

[^4]: You don't have to use a number. Arbitrary things like `[^footy note4]` and `[^footy note4]:` will also work. But they will *render* as numbered footnotes. Also, no need to keep your footnotes in order, I will sort out the order for you so they appear in the same order they were referenced in the text body. You can even keep some footnotes near where you referenced them, and collect others at the bottom of the file in the traditional place for footnotes.

## The Rendering Preference Pane
This is where I keep preferences relating to how I render and style the parsed markdown in the preview window.
![Rendering preferences pane](http://d.pr/i/rT4d+)

### CSS
You can choose different css files for me to use to render your html. You can even customize or add your own custom css files.

### Syntax Highlighting
You have already seen how I can syntax highlight your fenced code blocks. See the [Fenced Code Block](#fenced-code-block) section if you haven’t! You can also choose different themes for syntax highlighting.

### TeX-like Math Syntax
I can also render TeX-like math syntaxes, if you allow me to.[^math] I can do inline math like this: \\( 1 + 1 \\) or this (in MathML): <math><mn>1</mn><mo>+</mo><mn>1</mn></math>, and block math:

\\[
    A^T_S = B
\\]

or (in MathML)

<math display="block">
    <msubsup><mi>A</mi> <mi>S</mi> <mi>T</mi></msubsup>
    <mo>=</mo>
    <mi>B</mi>
</math>

### Task List Syntax
1. [x] I can render checkbox list syntax
	* [x] I support nesting
	* [x] I support ordered *and* unordered lists
2. [ ] I don't support clicking checkboxes directly in the html window

### Jekyll front-matter
If you like, I can display Jekyll front-matter in a nice table. Just make sure you put the front-matter at the very beginning of the file, and fence it with `---`. For example:

```
---
title: "Macdown is my friend"
date: 2014-06-06 20:00:00
---
```

### Render newline literally
Normally I require you to put two spaces and a newline (aka return) at the end of a line in order to create a line break. If you like, I can render a newline any time you end a line with a newline. However, if you enable this, markdown that looks lovely when I render it might look pretty funky when you let some *other* program render it.

## The General Preferences Pane

This is where I keep preferences related to application behavior.
![General preferences pane](http://d.pr/i/rvwu+)

The General Preferences Pane allows you to tell me how you want me to behave. For example, do you want me to make sure there is a document open when I launch? You can also tell me if I should constantly update the preview window as you type, or wait for you to hit `command-R` instead. Maybe you prefer your editor window on the right? Or to see the word-count as you type. This is also the place to tell me if you are interested in pre-releases of me, or just want to stick to better-tested official releases.

## The Editor Preference Pane
This is where I keep preferences related to the behavior and styling of the editing window.
![Editor preferences pane](http://d.pr/i/6OL5+)

### Styling

My editor provides syntax highlighting. You can edit the base font and the coloring/sizing theme. I provided some default themes (courtesy of [Mou](http://mouapp.com)’s creator, Chen Luo) if you don’t know where to start.

You can also edit, or even add new themes if you want to! Just click the ***Reveal*** button, and start moving things around. Remember to use the correct file extension (`.styles`), though. I’m picky about that.

I offer auto-completion and other functions to ease your editing experience. If you don’t like it, however, you can turn them off.

## Hack On

That’s about it. Thanks for listening. I’ll be quiet from now on (unless there’s an update about the app—I’ll remind you for that!).

Happy writing!

[^emphasize]: If **Underlines** is turned on, `_this notation_` will render as underlined instead of emphasized

[^under]: If **Underline** is disabled `_this_` will be rendered as *emphasized* instead of being underlined.

[^quote]: **Quote** replaces literal `"` characters with html `<q>` tags. **Quote** and **Smartypants** are syntactically incompatible. If both are enabled, **Quote** takes precedence. Note that **Quote** is different from *blockquote*, which is part of standard Markdown.

[^math]: Internet connection required.


%(header)s


aaaa


Ok, I will integrate it.


This is fixed


No problem. This is fun :).


Please refer PR #43. Changes are applied.


This assignment is redundant.


Are you running Android? You might enjoy [AIMSICD](https://secupwn.github.io/Android-IMSI-Catcher-Detector/) as well.


В исходном модуле есть данный метод http://retailcrm.github.io/api-client-php/class-RetailCrm.ApiClient.html#_sitesList


这句话语句不太通顺吧？o(╯□╰)o


I removed python and set it up again => no problem anymore.


上面这句的”逍遥“两个字应该改成”想要“。


非常感谢您的提交，有几个小的地方需要再次修改下，麻烦了。您是第一个贡献者！


I will replace printf with DEBUG_LEVEL_ERROR_TRACE


Ok, I will combine this change with 4636b2b.


Maybe it is easier to assume that in case of warehouses operator is always child_of.  (view locations don't contain a thing anyways on themselves)


Ok, I will combine this with 9450da3


Do you want to test this?
```set GIT_AUTHOR_NAME="Dummy Name"```
```set GIT_AUTHOR_EMAIL="dummy@example.com"```


hello world


We don't really use the force_company when len(warehouses) <= 100


a bit of a hack for now but we'll let it slide. Happy hacking. happy birthday!


[SP](http://adroiti-west-vm.cloudapp.net/) found an issue: 'Complex Method'

It's currently on:
**Commit**: 22e0a495344f44d834b68bd6bdef81862a6a646b
**File**: [SparkleSetup.cs](https://github.com/jccdromwell/andariel-crown/blob/22e0a495344f44d834b68bd6bdef81862a6a646b/SparkleSetup.cs)
**Lines**: [72-301](https://github.com/jccdromwell/andariel-crown/blob/22e0a495344f44d834b68bd6bdef81862a6a646b/SparkleSetup.cs#L72-301)


@dionlarson I think it's a good call switching to fixed update for this exercise. However, for physics platformers built by the students we will probably still have to rely on the velocity integration function (could maybe abstract it away), because update in fixed update seems to cause more glitches (e.g. player gets forced into wall).


What is happening with this pull request ? FY: @favreau


--> `translated_state`  or in a similar way


On SL with HAVE_ERRNO_H is not defined:
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)
cmake version 3.1.3
Even though the file is located under /usr/include/errno.h .
Here is the according part from CMakeCache.txt:
//Have include errno.h
HAVE_ERRNO_H:INTERNAL=


Not sure this is the right place for this check? I haven't had time to look through properly but shouldn't only the MethodArgumentStrategy care?


goood


Thanks!


y not use the variable "nick"?


here I am.


1: M111 unrecognized component name: I18N


1: M100 needs more reviewers
1: M101 signature is missing
1: M110 missing component name


1: M110 missing component name


10: M102 unrecognized bullet/signature
11: M102 unrecognized bullet/signature
12: M102 unrecognized bullet/signature
13: M102 unrecognized bullet/signature
14: M102 unrecognized bullet/signature
15: M102 unrecognized bullet/signature
1: M110 missing component name


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


6: M102 unrecognized bullet/signature
7: M102 unrecognized bullet/signature
1: M110 missing component name


1: M111 unrecognized component name: BibIndex


1: M111 unrecognized component name: WebSession


1: D100 Docstring missing


1: D205 Blank line missing between one-line summary and description
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: I100 Imports statements are in the wrong order. import fnmatch should be before import time
31:1: E402 module level import not at top of file
32:1: E402 module level import not at top of file
33:1: E402 module level import not at top of file
35:1: E402 module level import not at top of file
36:1: I101 Imported names are in the wrong order. Should be CFG_BIBINDEX_ADDING_RECORDS_STARTED_STR, CFG_BIBINDEX_INDEX_TABLE_TYPE, CFG_BIBINDEX_SPECIAL_TAGS, CFG_BIBINDEX_TOKENIZER_TYPE, CFG_BIBINDEX_UPDATE_MESSAGE, CFG_BIBINDEX_UPDATE_MODE, CFG_BIBINDEX_WASH_INDEX_TERMS, CFG_CHECK_MYSQL_THREADS, CFG_MAX_MYSQL_THREADS, CFG_MYSQL_THREAD_TIMEOUT
36:1: I100 Imports statements are in the wrong order. from invenio.bibindex_engine_config should be before from invenio.config
36:1: E402 module level import not at top of file
37:6: E126 continuation line over-indented for hanging indent
46:1: I100 Imports statements are in the wrong order. from invenio.bibauthority_config should be before from invenio.bibindex_engine_config
46:1: E402 module level import not at top of file
48:1: E402 module level import not at top of file
49:6: E126 continuation line over-indented for hanging indent
50:1: I100 Imports statements are in the wrong order. from invenio.bibauthorid_dbinterface should be before from invenio.bibauthority_engine
50:1: E402 module level import not at top of file
51:1: I101 Imported names are in the wrong order. Should be get_index_stemming_language, get_synonym_terms, perform_request_search, search_pattern, search_unit_in_bibrec
51:1: E402 module level import not at top of file
52:6: E126 continuation line over-indented for hanging indent
57:1: I101 Imported names are in the wrong order. Should be DatabaseError, deserialize_via_marshal, run_sql, serialize_via_marshal, wash_table_column_name
57:1: I100 Imports statements are in the wrong order. from invenio.dbquery should be before from invenio.search_engine
57:1: E402 module level import not at top of file
58:6: E126 continuation line over-indented for hanging indent
59:1: I100 Imports statements are in the wrong order. from invenio.bibindex_engine_washer should be before from invenio.dbquery
59:1: E402 module level import not at top of file
60:1: I101 Imported names are in the wrong order. Should be get_datetime, task_get_option, task_get_task_param, task_init, task_set_option, task_sleep_now_if_required, task_update_progress, write_message
60:1: E402 module level import not at top of file
63:1: E402 module level import not at top of file
64:1: I100 Imports statements are in the wrong order. from invenio.errorlib should be before from invenio.intbitset
64:1: E402 module level import not at top of file
65:1: E402 module level import not at top of file
66:1: I101 Imported names are in the wrong order. Should be CFG_JOURNAL_PUBINFO_STANDARD_FORM, CFG_JOURNAL_PUBINFO_STANDARD_FORM_REGEXP_CHECK, CFG_JOURNAL_TAG
66:1: I100 Imports statements are in the wrong order. from invenio.bibindex_tokenizers.BibIndexJournalTokenizer should be before from invenio.solrutils_bibindex_indexer
66:1: F401 'CFG_JOURNAL_PUBINFO_STANDARD_FORM_REGEXP_CHECK' imported but unused
66:1: F401 'CFG_JOURNAL_PUBINFO_STANDARD_FORM' imported but unused
66:1: F401 'CFG_JOURNAL_TAG' imported but unused
66:1: E402 module level import not at top of file
70:1: I100 Imports statements are in the wrong order. from invenio.bibindex_termcollectors should be before from invenio.bibindex_tokenizers.BibIndexJournalTokenizer
70:1: E402 module level import not at top of file
71:1: I101 Imported names are in the wrong order. Should be filter_for_virtual_indexes, get_all_index_names_and_column_values, get_all_indexes, get_all_synonym_knowledge_bases, get_field_tags, get_index_id_from_index_name, get_index_remove_html_markup, get_index_remove_latex_markup, get_index_remove_stopwords, get_index_tags, get_index_virtual_indexes, get_marc_tag_indexes, get_min_last_updated, get_nonmarc_tag_indexes, get_records_range_for_index, get_virtual_index_building_blocks, list_union, load_tokenizers, make_prefix, recognize_marc_tag, remove_inexistent_indexes, run_sql_drop_silently
71:1: I100 Imports statements are in the wrong order. from invenio.bibindex_engine_utils should be before from invenio.bibindex_termcollectors
71:1: F401 'get_field_tags' imported but unused
71:1: F401 'get_all_index_names_and_column_values' imported but unused
71:1: E402 module level import not at top of file
93:1: I101 Imported names are in the wrong order. Should be NonmarcTermCollector, TermCollector
93:1: F999 redefinition of unused 'TermCollector' from line 70
93:1: E402 module level import not at top of file
96:1: E402 module level import not at top of file
111:17: E261 at least two spaces before inline comment
112:25: E261 at least two spaces before inline comment
119: D401 First line should be imperative: 'Return', not 'Returns'
128: D400 First line should end with '.', not 'n'
128: D205 Blank line missing between one-line summary and description
128: D208 Docstring is over-indented
143:66: E502 the backslash is redundant between brackets
148: D400 First line should end with '.', not 'd'
148: D205 Blank line missing between one-line summary and description
177: D209 Put multi-line docstring closing quotes on separate line
177: D205 Blank line missing between one-line summary and description
180:53: E502 the backslash is redundant between brackets
203:67: E225 missing whitespace around operator
204:30: E124 closing bracket does not match visual indentation
204:31: E261 at least two spaces before inline comment
213:33: E261 at least two spaces before inline comment
225:33: E261 at least two spaces before inline comment
236:33: E261 at least two spaces before inline comment
248:33: E261 at least two spaces before inline comment
259:33: E261 at least two spaces before inline comment
271:33: E261 at least two spaces before inline comment
281: D401 First line should be imperative: 'Remove', not 'Removes'
281: D300 Expected """-quotes, got '-quotes
286: D401 First line should be imperative: 'Return', not 'Returns'
286: D400 First line should end with '.', not 'd'
298: D401 First line should be imperative: 'Return', not 'Returns'
298: D400 First line should end with '.', not 'e'
298: D205 Blank line missing between one-line summary and description
298: D208 Docstring is over-indented
309:68: E502 the backslash is redundant between brackets
317: D401 First line should be imperative: 'Check', not 'Checks'
317: D205 Blank line missing between one-line summary and description
317: D208 Docstring is over-indented
338: D401 First line should be imperative: 'Return', not 'Returns'
338: D400 First line should end with '.', not 's'
340:10: E225 missing whitespace around operator
355:56: E261 at least two spaces before inline comment
363: D290 White spaces around docstring should be trimmed.
363: D400 First line should end with '.', not 's'
363: D205 Blank line missing between one-line summary and description
374:70: E502 the backslash is redundant between brackets
375:32: E127 continuation line over-indented for visual indent
379: D401 First line should be imperative: 'Return', not 'Returns'
379: D400 First line should end with '.', not 'e'
379: D300 Expected """-quotes, got '-quotes
392: D401 First line should be imperative: 'Create', not 'Creates'
392: D209 Put multi-line docstring closing quotes on separate line
392: D400 First line should end with '.', not 'd'
392: D205 Blank line missing between one-line summary and description
411: D401 First line should be imperative: 'Return', not 'Returns'
411: D400 First line should end with '.', not 't'
433:74: E502 the backslash is redundant between brackets
437:52: E261 at least two spaces before inline comment
438:52: E261 at least two spaces before inline comment
439:54: E261 at least two spaces before inline comment
440:54: E261 at least two spaces before inline comment
443: D205 Blank line missing between one-line summary and description
443: D208 Docstring is over-indented
453:70: E502 the backslash is redundant between brackets
459: D290 White spaces around docstring should be trimmed.
459: D400 First line should end with '.', not 'd'
469: D401 First line should be imperative: 'find_affected_record', not 'find_affected_records'
469: D205 Blank line missing between one-line summary and description
469: D208 Docstring is over-indented
480: D202 No blank lines allowed *after* function docstring, found 1
480: D400 First line should end with '.', not 'd'
480: D205 Blank line missing between one-line summary and description
480: D208 Docstring is over-indented
501:37: E127 continuation line over-indented for visual indent
527:24: E127 continuation line over-indented for visual indent
536:20: E126 continuation line over-indented for hanging indent
574: D401 First line should be imperative: 'Split', not 'Splits'
574: D400 First line should end with '.', not 's'
574: D205 Blank line missing between one-line summary and description
574: D208 Docstring is over-indented
595: D203 Expected 1 blank line *before* class docstring, found 0
595: D205 Blank line missing between one-line summary and description
595: D208 Docstring is over-indented
614: D102 Docstring missing
619:65: E502 the backslash is redundant between brackets
620:49: E128 continuation line under-indented for visual indent
620:57: E502 the backslash is redundant between brackets
621:49: E128 continuation line under-indented for visual indent
621:62: E502 the backslash is redundant between brackets
622:49: E128 continuation line under-indented for visual indent
625:24: E261 at least two spaces before inline comment
628: D401 First line should be imperative: 'Update', not 'Updates'
628: D400 First line should end with '.', not 'B'
628: D205 Blank line missing between one-line summary and description
628: D208 Docstring is over-indented
633:57: E502 the backslash is redundant between brackets
635:64: E502 the backslash is redundant between brackets
637:62: E502 the backslash is redundant between brackets
638:23: E128 continuation line under-indented for visual indent
657:63: E502 the backslash is redundant between brackets
660:73: E502 the backslash is redundant between brackets
665:62: E502 the backslash is redundant between brackets
679:65: E502 the backslash is redundant between brackets
691:75: E502 the backslash is redundant between brackets
697:55: E502 the backslash is redundant between brackets
699:54: E502 the backslash is redundant between brackets
700:23: E128 continuation line under-indented for visual indent
702: D400 First line should end with '.', not 'y'
705:28: E261 at least two spaces before inline comment
709:74: E502 the backslash is redundant between brackets
713:74: E502 the backslash is redundant between brackets
715:134: E261 at least two spaces before inline comment
717:14: E261 at least two spaces before inline comment
718:70: E502 the backslash is redundant between brackets
722:142: E261 at least two spaces before inline comment
724:17: E266 too many leading '#' for block comment
725:17: E266 too many leading '#' for block comment
728:20: E261 at least two spaces before inline comment
729:104: E261 at least two spaces before inline comment
731: D401 First line should be imperative: 'Keep', not 'Keeps'
731: D400 First line should end with '.', not 'g'
731: D205 Blank line missing between one-line summary and description
731: D208 Docstring is over-indented
746:21: W601 .has_key() is deprecated, use 'in'
751:29: F841 local variable 'e' is assigned to but never used
752:84: E502 the backslash is redundant between brackets
764: D400 First line should end with '.', not 'y'
764: D205 Blank line missing between one-line summary and description
778: D401 First line should be imperative: 'Clean', not 'Cleans'
778: D300 Expected """-quotes, got '-quotes
783: D203 Expected 1 blank line *before* class docstring, found 0
783: D205 Blank line missing between one-line summary and description
783: D208 Docstring is over-indented
799: D401 First line should be imperative: 'Create', not 'Creates'
799: D205 Blank line missing between one-line summary and description
799: D208 Docstring is over-indented
808:43: E127 continuation line over-indented for visual indent
809:43: E127 continuation line over-indented for visual indent
810:43: E127 continuation line over-indented for visual indent
814: D401 First line should be imperative: 'Set', not 'Sets'
814: D400 First line should end with '.', not 'l'
814: D205 Blank line missing between one-line summary and description
814: D208 Docstring is over-indented
822: D205 Blank line missing between one-line summary and description
822: D208 Docstring is over-indented
841:85: E502 the backslash is redundant between brackets
863:28: E126 continuation line over-indented for hanging indent
866:87: E502 the backslash is redundant between brackets
896: D401 First line should be imperative: 'Retrieve', not 'Retrieves'
896: D202 No blank lines allowed *after* method docstring, found 1
896: D400 First line should end with '.', not 'x'
896: D205 Blank line missing between one-line summary and description
896: D208 Docstring is over-indented
916: D401 First line should be imperative: 'Retrieve', not 'Retrieves'
916: D202 No blank lines allowed *after* method docstring, found 1
916: D400 First line should end with '.', not 'x'
916: D205 Blank line missing between one-line summary and description
916: D208 Docstring is over-indented
936: D401 First line should be imperative: 'Update', not 'Updates'
936: D400 First line should end with '.', not ':'
936: D205 Blank line missing between one-line summary and description
936: D208 Docstring is over-indented
966:55: E502 the backslash is redundant between brackets
967:24: E127 continuation line over-indented for visual indent
968:24: E127 continuation line over-indented for visual indent
968:69: E261 at least two spaces before inline comment
970:174: E261 at least two spaces before inline comment
974: D401 First line should be imperative: 'Insert', not 'Inserts'
974: D400 First line should end with '.', not 'e'
974: D205 Blank line missing between one-line summary and description
974: D208 Docstring is over-indented
1002:179: E261 at least two spaces before inline comment
1004:174: E261 at least two spaces before inline comment
1008: D401 First line should be imperative: 'Remove', not 'Removes'
1008: D400 First line should end with '.', not 'd'
1008: D205 Blank line missing between one-line summary and description
1008: D208 Docstring is over-indented
1033:179: E261 at least two spaces before inline comment
1035:174: E261 at least two spaces before inline comment
1039: D401 First line should be imperative: 'Update', not 'Updates'
1039: D400 First line should end with '.', not 'o'
1039: D205 Blank line missing between one-line summary and description
1039: D208 Docstring is over-indented
1078: D401 First line should be imperative: 'Update', not 'Updates'
1078: D205 Blank line missing between one-line summary and description
1078: D208 Docstring is over-indented
1093: D401 First line should be imperative: 'Update', not 'Updates'
1093: D400 First line should end with '.', not 'd'
1093: D205 Blank line missing between one-line summary and description
1093: D208 Docstring is over-indented
1121: D401 First line should be imperative: 'Remove', not 'Removes'
1121: D400 First line should end with '.', not 'e'
1128: D401 First line should be imperative: 'Clean', not 'Cleans'
1128: D400 First line should end with '.', not ')'
1128: D205 Blank line missing between one-line summary and description
1128: D208 Docstring is over-indented
1135:18: E127 continuation line over-indented for visual indent
1139: D401 First line should be imperative: 'Remove', not 'Removes'
1139: D400 First line should end with '.', not ')'
1139: D205 Blank line missing between one-line summary and description
1139: D208 Docstring is over-indented
1156:5: E303 too many blank lines (2)
1156: D401 First line should be imperative: 'Remove', not 'Removes'
1156: D205 Blank line missing between one-line summary and description
1156: D208 Docstring is over-indented
1194: D203 Expected 1 blank line *before* class docstring, found 0
1194: D400 First line should end with '.', not 'x'
1194: D205 Blank line missing between one-line summary and description
1194: D208 Docstring is over-indented
1205: D401 First line should be imperative: 'Create', not 'Creates'
1205: D205 Blank line missing between one-line summary and description
1246: D401 First line should be imperative: 'Fill', not 'Fills'
1246: D400 First line should end with '.', not 'h'
1246: D205 Blank line missing between one-line summary and description
1246: D208 Docstring is over-indented
1269: D401 First line should be imperative: 'Prevent', not 'Prevents'
1269: D208 Docstring is over-indented
1269: D200 One-line docstring should not occupy 3 lines
1275: D401 First line should be imperative: 'Turn', not 'Turns'
1275: D208 Docstring is over-indented
1275: D200 One-line docstring should not occupy 3 lines
1281: D401 First line should be imperative: 'Return', not 'Returns'
1281: D209 Put multi-line docstring closing quotes on separate line
1281: D202 No blank lines allowed *after* method docstring, found 1
1281: D400 First line should end with '.', not 'e'
1281: D205 Blank line missing between one-line summary and description
1281: D208 Docstring is over-indented
1296: D401 First line should be imperative: 'Inform', not 'Informs'
1296: D205 Blank line missing between one-line summary and description
1296: D208 Docstring is over-indented
1316: D401 First line should be imperative: 'Display', not 'Displays'
1316: D300 Expected """-quotes, got '-quotes
1323: D401 First line should be imperative: 'Return', not 'Returns'
1323: D300 Expected """-quotes, got '-quotes
1327: D401 First line should be imperative: 'Print', not 'Prints'
1327: D300 Expected """-quotes, got '-quotes
1331: D202 No blank lines allowed *after* method docstring, found 1
1331: D300 Expected """-quotes, got '-quotes
1343:22: W601 .has_key() is deprecated, use 'in'
1344:62: E502 the backslash is redundant between brackets
1345:17: E128 continuation line under-indented for visual indent
1347:75: E502 the backslash is redundant between brackets
1348:31: E127 continuation line over-indented for visual indent
1350: D401 First line should be imperative: 'Fetche', not 'Fetches'
1350: D400 First line should end with '.', not 's'
1350: D205 Blank line missing between one-line summary and description
1363:35: E261 at least two spaces before inline comment
1380:73: E502 the backslash is redundant between brackets
1381:25: E128 continuation line under-indented for visual indent
1391:73: E502 the backslash is redundant between brackets
1392:25: E128 continuation line under-indented for visual indent
1421:29: W601 .has_key() is deprecated, use 'in'
1446:24: W601 .has_key() is deprecated, use 'in'
1447:31: E701 multiple statements on one line (colon)
1468:27: E701 multiple statements on one line (colon)
1471:184: E261 at least two spaces before inline comment
1474:179: E261 at least two spaces before inline comment
1486: D401 First line should be imperative: 'Divide', not 'Divides'
1486: D209 Put multi-line docstring closing quotes on separate line
1486: D400 First line should end with '.', not ','
1486: D205 Blank line missing between one-line summary and description
1486: D208 Docstring is over-indented
1508: D209 Put multi-line docstring closing quotes on separate line
1508: D205 Blank line missing between one-line summary and description
1519:81: E502 the backslash is redundant between brackets
1520:17: E128 continuation line under-indented for visual indent
1523:63: E502 the backslash is redundant between brackets
1524:21: E128 continuation line under-indented for visual indent
1526: D401 First line should be imperative: 'Keep', not 'Keeps'
1526: D400 First line should end with '.', not 'g'
1526: D205 Blank line missing between one-line summary and description
1526: D208 Docstring is over-indented
1541:21: W601 .has_key() is deprecated, use 'in'
1546:9: B901 blind except: statement
1550:5: E303 too many blank lines (2)
1550: D401 First line should be imperative: 'Fetche', not 'Fetches'
1550: D400 First line should end with '.', not 's'
1550: D205 Blank line missing between one-line summary and description
1566: D401 First line should be imperative: 'Delete', not 'Deletes'
1566: D209 Put multi-line docstring closing quotes on separate line
1566: D400 First line should end with '.', not 'w'
1566: D205 Blank line missing between one-line summary and description
1566: D208 Docstring is over-indented
1569:82: E502 the backslash is redundant between brackets
1570:17: E128 continuation line under-indented for visual indent
1580:80: E502 the backslash is redundant between brackets
1581:17: E128 continuation line under-indented for visual indent
1583: D401 First line should be imperative: 'Find', not 'Finds'
1583: D200 One-line docstring should not occupy 3 lines
1592: D400 First line should end with '.', not 'r'
1592: D205 Blank line missing between one-line summary and description
1616: D400 First line should end with '.', not 'e'
1634:35: E261 at least two spaces before inline comment
1665: D400 First line should end with '.', not 'e'
1667:9: E266 too many leading '#' for block comment
1673:19: E261 at least two spaces before inline comment
1675:9: E266 too many leading '#' for block comment
1678:17: E127 continuation line over-indented for visual indent
1683: D202 No blank lines allowed *after* method docstring, found 1
1683: D400 First line should end with '.', not 'y'
1683: D205 Blank line missing between one-line summary and description
1703:25: W601 .has_key() is deprecated, use 'in'
1707:15: E261 at least two spaces before inline comment
1709:16: E713 test for membership should be 'not in'
1722:49: E713 test for membership should be 'not in'
1742:29: E128 continuation line under-indented for visual indent
1743:33: E128 continuation line under-indented for visual indent
1748:21: E126 continuation line over-indented for hanging indent
1759:13: E128 continuation line under-indented for visual indent
1760:13: E128 continuation line under-indented for visual indent
1783:13: E128 continuation line under-indented for visual indent
1784:13: E128 continuation line under-indented for visual indent
1800:13: E126 continuation line over-indented for hanging indent
1805:1: E302 expected 2 blank lines, found 1
1813:1: E302 expected 2 blank lines, found 1
1813: D290 White spaces around docstring should be trimmed.
1813: D400 First line should end with '.', not 'e'
1813: D205 Blank line missing between one-line summary and description
1847:78: E502 the backslash is redundant between brackets
1848:17: E128 continuation line under-indented for visual indent
1861:1: E302 expected 2 blank lines, found 1
1861: D290 White spaces around docstring should be trimmed.
1868: D401 First line should be imperative: 'Find', not 'Finds'
1868: D290 White spaces around docstring should be trimmed.
1868: D400 First line should end with '.', not ']'
1868: D205 Blank line missing between one-line summary and description
1868: D208 Docstring is over-indented
1887:36: E127 continuation line over-indented for visual indent
1893:41: E127 continuation line over-indented for visual indent
1896:36: E127 continuation line over-indented for visual indent
1902:41: E127 continuation line over-indented for visual indent
1907:36: E127 continuation line over-indented for visual indent
1914:41: E127 continuation line over-indented for visual indent
1925: D401 First line should be imperative: 'Find', not 'Finds'
1925: D290 White spaces around docstring should be trimmed.
1925: D400 First line should end with '.', not ']'
1925: D205 Blank line missing between one-line summary and description
1925: D208 Docstring is over-indented
1965:48: E261 at least two spaces before inline comment
1971: D401 First line should be imperative: 'Find', not 'Finds'
1971: D205 Blank line missing between one-line summary and description
1971: D208 Docstring is over-indented
1987: D401 First line should be imperative: 'Get', not 'Gets'
1987: D400 First line should end with '.', not 'n'
1987: D205 Blank line missing between one-line summary and description
1987: D208 Docstring is over-indented
2022: D401 First line should be imperative: 'Get', not 'Gets'
2022: D400 First line should end with '.', not 'e'
2022: D205 Blank line missing between one-line summary and description
2022: D208 Docstring is over-indented
2040: D401 First line should be imperative: 'Remove', not 'Removes'
2040: D205 Blank line missing between one-line summary and description
2040: D208 Docstring is over-indented
2064: D401 First line should be imperative: 'Decide', not 'Decides'
2064: D205 Blank line missing between one-line summary and description
2064: D208 Docstring is over-indented
2073: D205 Blank line missing between one-line summary and description
2073: D208 Docstring is over-indented
2106: D401 First line should be imperative: 'Run', not 'Runs'
2106: D205 Blank line missing between one-line summary and description
2106: D208 Docstring is over-indented
2162:85: E502 the backslash is redundant between brackets
2163:56: E128 continuation line under-indented for visual indent
2163:86: E502 the backslash is redundant between brackets
2164:56: E128 continuation line under-indented for visual indent
2170:5: E303 too many blank lines (2)
2191:29: E126 continuation line over-indented for hanging indent
2230:29: E126 continuation line over-indented for hanging indent
2242:25: E126 continuation line over-indented for hanging indent
2269:29: E126 continuation line over-indented for hanging indent
2283:25: E126 continuation line over-indented for hanging indent
2308:5: E303 too many blank lines (2)
2312:1: E266 too many leading '#' for block comment


I tried to add the last 2 lines but it still doesnt work for me. What do I have to change to get this working again? (restarted Eagle of course)


37: D290 White spaces around docstring should be trimmed.


what about `options = options || {}`?


1: D100 Docstring missing
21:1: I100 Imports statements are in the wrong order. from operator should be before from invenio.dbquery
21:1: I201 Missing newline before sections or imports.
22:1: I100 Imports statements are in the wrong order. from itertools should be before from operator
23:1: I201 Missing newline before sections or imports.
27:1: E302 expected 2 blank lines, found 1
27: D103 Docstring missing
30:1: E302 expected 2 blank lines, found 1
30: D103 Docstring missing
41:40: E127 continuation line over-indented for visual indent
41:49: E202 whitespace before ')'
49:38: E127 continuation line over-indented for visual indent
49:44: E202 whitespace before ')'
77:20: E127 continuation line over-indented for visual indent
77:90: E202 whitespace before ')'
81:16: E127 continuation line over-indented for visual indent
83:1: E302 expected 2 blank lines, found 1
83: D103 Docstring missing