Somehow, while mucking about trying to get GitHub to work on my Windows 7 desktop, I have created an online master repo named turnbulm/obspy-kelunji-classic. It has magically been populated with my new core.py and a test directory containing my test files. That must have happened when I was trying to configure my local copy of GitHub. That's all very fine; but that new master repo has no connection with the obspy/kelunji-classic branch that I created a few days ago. Is there a way to combine the obspy-kelunji-classic master with the obspy/kelunji-classic branch? Do I need to give you access to my master somehow?

Also, in my master, when I open the core.py file for editing, and click on the "edit file in my local desktop Git" link, I get messages on my desktop asking me to approve the opening of files and running of applications, so something is obviously happening under the hood - but nothing else happens!, apparently! My local GitHub does not fire up, and I don't get presented with any edit window with core.py in it. Is there something I needed to do but haven't done?

I'm following up on your suggestions for the carpentry tutes. They seem to be a lot more instructive than the others. Thanks for that. I'll also check out the Gitter im chat box. Cheers & thanks again.


I will think about merging this


`min_break` value needs to be rounded or else it might sometimes display as 3 w/o formatting. Numbers are rounded to nearest 0.5 for display but not in the `min_break` array.


I especially like this part


Oh wow


This is a bit hard to read, especially if you want to figure out which port corresponds to what. Temporary local variables would help:

    String binaryItf = IP_PREFIX + n + ":" + ports[2];
    // etc.


Please, avoid using old hash rocket syntax.


It's unused, do we still need it?


Fix the bug in render_error function.
Added unit tests for is_after_last_day_of_classes and is_before_first_day_of_term of 4 quarters.


isn't static always initialized to 0?


I have restored the old behavior. Its simpler to let users that want automatic focus configure their vimrc using `WinEnter`


> We solve (1) in our hosted infrastructure by simply reauthing an account if they try to connect the same account more than once.

So if developer A connects his email account using his IMAP credentials, could developer B screw up developer A's email sync by connecting user A's email address using a completely different IMAP server?


Ooo bby right there


@michaelsieben ,

I think this method should be called `findOneByName`. `findByName` indicates that it's returning all attributes with the name `$name`, while you use `getSingleResult` in the end...

Also, could you have a look at [PSR-2](http://www.php-fig.org/psr/psr-2), apply it on your changes and add some documentation to class and methods?

Please, don't forget to make a pull request next time...


Grade: 2/2
Answer that uses method chaining:
param.uniq!.map(&:to_i).map{|element| element + 2}.select{|element| element % 2 == 0 and element < 10}.inject{|sum, n| sum + n}


I suggest calling this `hostAddress` as this will be more obvious what it is in subclasses.


@michaelsieben,

Could you have a look at PSR-2, apply it on your changes and add some documentation to the class and methods?

Please, don't forget to make a pull request next time...


Throw an `AssertionFailure` to abort the test immediately.


These constants were protected. Made them internal.


Yes - that's what it's for.  Not sure what google were thinking.

On Fri, Mar 6, 2015 at 2:02 AM, Sven Bergström <notifications@github.com>
wrote:

> Does this resolve errors like the one below when using later NDK on stable
> hxcpp? :
>
> E/AndroidRuntime(17287): java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "tcgetattr" referenced by "libapplicationname.so".
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/HaxeFoundation/hxcpp/commit/1e9e4af613e9899d065ef43d64e8bc338b9d0353#commitcomment-10056827>
> .
>


2/2
Looks good! Look into method chaining to get your solution to question 2 much shorter.


This was protected. Made internal to remove from public surface.


Unnecessary space after :vcr.


I merged this to upstream FreeBSD in r279573


I have swapped the arguments to the error (the error message is the same) so that code shared among both compilers can create this diagnostic.


You are visiting register_path before each scenario maybe you could refactor it to background block :)


Would be nice to pick these dynamically using `TestUtils#findAvailablePort`, one day we might have other tests picking custom ports and this will make it easier to avoid collisions.


are these names generated by camera_calibration? Or did you have to manually rename them?


I don't think I understand how github works...yet.


Open catalogue record in a new window or tab


Grade: 2/2


Would it be simpler to put `checkInstanceAndUpdate` inside the goroutine or `delete` outside the goroutine rather than trying to orchestrate them across different goroutines?


persist.audio.handset.mic.type=analog \
persist.audio.dualmic.config=false \

This settings fixed call sound and mic in headphones without mic.


If user is invalid - does it matter whether the payment is invalid? It should always fail if user is invalid and then you should test payment validity if user details are correct.

Another thing is, if you are testing only the invalidity of card. Like card number "123123" - that should fail immediately in the browser as Stripe is checking the card format before sending you the token.


these have to be renamed manually for now. we could write something to automate it in future.
i had to use the convert 2 times because it always converts only the highest entry in the ost.txt files, so the second time you have to temporarily remove the entry and convert it.


@mmrtnz Do you remember why this height and width style is necessary?


No need to do `$rootScope.$broadcast` here. Simply use `handleVisibility` directly.


all tests pass:
success: http://build.servo.org/builders/linux1/builds/942
success: http://build.servo.org/builders/linux2/builds/940
success: http://build.servo.org/builders/android/builds/978
success: http://build.servo.org/builders/mac1/builds/1157
success: http://build.servo.org/builders/mac2/builds/1158
success: http://build.servo.org/builders/gonk/builds/128


I think I just fixed the problem in the wrong part.
I'll remove this and fix it @ line 204 in discovery.py similar to bdc4d8b.


I would have this only drop `myKeyspace`. One day we might start running the tests in parallel, so we don't want them dropping each other's keyspaces.
If some tests create other keyspaces, it should be their responsibility to delete them. To avoid collisions, we can rely on the convention that keyspaces generated by this class are prefixed by `ks_`, so subclasses should use different names.


@bors: retry


mate, read you tomorrow, its 2:50 a.m. on my side of the planet ^^


Thanks!


We should not create `ks` anymore, right?


Alright.  Just don't be surprised when the 2 tests fail in 2.6 on travis.


This seems unnecessary in `run` block.


Same as above, why do we keep creating the schema in the non-dynamic keyspace, it should go away.


Ok. My bootloader is acting up. Any command beginning with fastboot oem causes output '---' and fastboot hangs. I cant enter any fastboot oem command. Other commands like fastboot devices or reboot work fine. You have any idea.?


fast-forwarding master to auto = 0a7e495b


Since you will be calling `handleVisibility` directly (see the comment below), you can remove `isHidden` from the if statement.


Set default `idleDelay` to 10000 instead of 0.


Hi, I just released v1 with support for optional Play, Spray (or none at all) JSON support. Can you check it out? https://github.com/pathikrit/metarest


saw approval from SimonSapin
at https://github.com/luniv/servo/commit/1931a69ad2151b1bbf60655eee2502c198e836bd


merging luniv/servo/viewpoint-percent-lengths = 1931a69a into auto


luniv/servo/viewpoint-percent-lengths = 1931a69a merged ok, testing candidate = a557b51c


TeamCity Akka.NET :: Akka.NET PR Build [Build 106](http://petabridge-ci.cloudapp.net/viewLog.html?buildId=162&buildTypeId=AkkaNet_AkkaNetPrBuild&guest=1) is now running


Good to know about that technique. Done, thank you very much.


In the absence of a better place to put this feedback I'll do it here :-).

Since I'm thinking a lot about Effect as a platform, I've got some thoughts and feelings I would like to share by way of code review :).

If I understand it correctly, this function is trying to do more or less what `DeferredSemaphore.run` does.

This seems like desirable functionality, but:

1. The name `non_concurrently` suggests that it stops the operation of all `Effect`s.
2. Similarly `ConcurrentError` and its docstring are not straightforward; `LockAlreadyAcquired` would be clearer.
3. Something this general should definitely be factored out, possibly into effect itself, but at least into a utility module for the time being.
4. "ERef of PSet" is a crummy type to have to carry around with you.  By this I mean: constructing it requires importing names from two other modules, if you manipulate it in any way you will be violating the contract that this function proposes.  (Also, pyrsistent's docs are confusing. Is it `PSet` or `pset`?).  The bag of locks is internal state for this operation, and the choice to use this particular arrangement for locking is one that could be changed without changing the useful part of this function's contract, so it should be encapsulated as such.  By way of example, its one caller constructs a bag of locks which it then exclusively passes to this function.
5. I'm kinda curious reading about the guarantees that this attempts to provide, under what circumstances would it fail to execute `eff`?  (Personally I'd rather read about this as a description of behavior rather than in terms of guarantees; I feel like we oversell code by saying it provides "guarantees" when we are just saying what we think ought to happen, but I digress.)
6. I realize this is going well beyond the scope it's needed for in this case, but given that it seems you want a lock-set rather than an individual lock (presumably to track which groups are being converged upon for logging purposes), it would be nice to be able to pass more than one key at a time, so that the implementation could properly re-order them to avoid deadlocking issues.

To put this all together, from an API perspective, as a potential user, I'd want something more along the lines of:

```python
locks = Locks()
@do
def with_a_and_b(some_effect):
    yield locks.exclusively(["a", "b"], effect)
```

Hopefully this is useful feedback!


`null: false`ほしいかも


Add `stopOnVisibilityChange` config option in addition to `delayOnVisibilityChange`.


Should also be a `Maybe` thing, because nulls are terrible.


This broke build against GEOS trunk  (box2, box1) have to be bbox2, bbox1.
But sill after fix there's a failure in testsuite:
```
 clipbybox2d .. failed (diff expected obtained: /tmp/pgis_reg/test_103_diff)
-----------------------------------------------------------------------------
--- clipbybox2d_expected        2015-03-04 18:28:21.187446477 +0100
+++ /tmp/pgis_reg/test_103_out  2015-03-06 10:58:28.586676422 +0100
@@ -6,4 +6,4 @@
 POLYGON((2.5 2,5 4,5 5,5 4,7.5 2,2.5 2))
 POLYGON((2 2,2 5,5 5,5 2,2 2))
 SRID=3857;POLYGON EMPTY
-SRID=4326;POINT(0 0)
+ERROR:  gbox_overlaps: cannot compare geodetic and non-geodetic boxes
-----------------------------------------------------------------------------
```


Maybe something like this:

bin -> all the python scripts including db_ but also search scripts, the xmpp client and so on
etc -> configuration files?
lib -> the python libraries
web -> all the templates and the Flask aspp


I thought that the scope should be here so it didn't affect app/models/post.rb raw state. Doing some testes in rails c it makes sense that Wall.find(1).posts.all comes in default order and in the view (http://localhost:3000/walls/1) comes the most recent created first. My question is, does rails c shows the scope order descending? because if rails c receives Post.all it will return the posts in ascending order.


其实不需要了，Google fonts api解封了


saludos profe aqui le dejo mi tarea de polinomio


XXH64 is faster


@tmat one problem is that JSON.NET can no longer serialize CSharpCompilationOptions.


TOC uses js to jump to subheader. In general I'd add it with js, but because it appears 'above the fold' you'd get a flash of nothing before it appears

We could make a non-js list style TOC, and upgrade to dropdown with js - again, there'd be a flash of change, plus feels like it's an added extra rather than a core requirement


Going to throw out some more thoughts. There seem to be several separate information items here:

1. Does a store support transaction semantics:
 * yes: e.g. ISPN, Neo4
 * no: e.g. MongoDB
2. How does a store work with JTA:
 * "can_participate": e.g. ISPN fully, MongoDB, CouchDB tag-along
 * "exclusively": Neo4j; they (still?) use JTA as an API, but you cannot participate in an ongoing JTA TX; So the JTA `Transaction` impl works but it requires a dedicated `JtaPlatform`
3. Does a store offer a way of local TX execution (so RESOURCE_LOCAL works):
 * yes: possibly Neo4j through its own API; requires a custom `Transaction` implementation
 * emulated: e.g. MongoDB (using the new `Transaction` implementation)
 * no: ISPN?

If `GridDialect#getTransactionCapability()` returned a structure (class, no enum) answering all these questions I think we should be fine.

Our Tx Factory would query 2. and 3. to find the right `Transaction` implementation (in conjunction with the incoming "transaction-type" from the PU). Answering "Yes" for 3. would require a way for specifiying a custom `Transaction` class for stores which can do proper local TX.

Querying 1. would help to e.g. raise a warning upon rollback attempts (no matter whether it's a local or JTA TX).

The default impl for `TransactionCapability` probably would return:

* `isTransactional()`: false
* `getJtaParticipationType()`: can_participate
* `localTxType()`: no
* `getLocalTransactionImplementationType()`: null


I did!

Do you mean use Thumb2 conditional code in recursive call instead of "bl
fibonacci"??

On Fri, Mar 6, 2015 at 5:55 PM, Jim Huang <notifications@github.com> wrote:

> If you utlize Thumb2 condtional code, the whole sequence can be even
> shorten.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/hsuedw/arm-lecture/commit/432e03b7fd91326b9172a345bab105b02e7d51fb#commitcomment-10068102>
> .
>


```
Error: [ApplicationContext]: Error occured: System.InvalidOperationException: This operation cannot be performed on a default instance of ImmutableArray<T>.  Consider initializing the array, or checking the ImmutableArray<T>.IsDefault property.
   at System.Collections.Immutable.ImmutableArray`1.ThrowInvalidOperationIfNotInitialized()
   at System.Collections.Immutable.ImmutableArray`1.System.Collections.IEnumerable.GetEnumerator()
   at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeList(JsonWriter writer, IEnumerable values, JsonArrayContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeValue(JsonWriter writer, Object value, JsonContract valueContract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerProperty)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeValue(JsonWriter writer, Object value, JsonContract valueContract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerProperty)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeValue(JsonWriter writer, Object value, JsonContract valueContract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerProperty)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeValue(JsonWriter writer, Object value, JsonContract valueContract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerProperty)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.Serialize(JsonWriter jsonWriter, Object value, Type objectType)
   at Newtonsoft.Json.JsonSerializer.SerializeInternal(JsonWriter jsonWriter, Object value, Type objectType)
   at Newtonsoft.Json.Linq.JToken.FromObjectInternal(Object o, JsonSerializer jsonSerializer)
   at Newtonsoft.Json.Linq.JToken.FromObject(Object o)

```


Sorry about that. :( I thought it would be obvious from the commit message. I have to improve my commit messages.


If we do, you'd better introduce a "slow test suite" run on demand only. In order to test the last line, I need to bring the counter up to 99 (or 99999). I don't know how many hours 99999 would take to complete the test - most people would consider it hung, and I didn't have the patience to wait for the end of it.

It is possible though that 999 wouldn't have that much of a (test) performance yet, so I'd consider that a possible compromise.

Executive summary: reverting the change would cause all Travis builds to conk out (I think the limit is 1500 seconds). If they didn't conk out, the time for a build would probably increase to 12 hours or so :P


is it psr-2?


@mathiasbynens sure I was doing the same :smile: and got it into a git conflict :-1:


I believe this test is more than a matter of coverage or good form - it demonstrates what would happen, if the limit was reached.


These files are automatically generated and updated by the script at https://code.google.com/p/dart/source/browse/branches/bleeding_edge/dart/tools/apps/update_homebrew/bin/update_homebrew.dart , not updated by hand.

There is no 64-bit build of mac os x dartium, only a 32-bit build.  The proposed change incorrectly checks out the Dart SDK instead of dartium - look at the urls.

Closing this pull request.


Don't we want an `AST.Boolean`?


Typically contributors mention themselves in the copyright or give the copyright to the tcpdump project. Whichever looks best for you.


No worries, I thought it was a bugfix :)


So we are saying something like this:

`public TransactionType supportsTransactionType`

where `TransactionType` for now contains `NONE`, `JTA` and `RESOURCE_LOCAL`
MongoDB and EHCache would be `NONE`. Infinispan and Neo4J would be `JTA`. What's about CouchDB?


Altering the order of the template loaders in *95-outro.conf* breaks all of our customizations, please consider reverting.


master and 4.1 are ok, 4.0. is a dead branch already ;)

2015-03-06 11:00 GMT+01:00 Grzegorz Grzybek <notifications@github.com>:

> Last question: Should I update master, 4.1.x, 4.0.x and 3.1.x branches
> too? (the 3.1.x probably no)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ops4j/org.ops4j.pax.web/commit/eabc11dca75abbfd4cb7900945459967f8cc7c59#commitcomment-10068180>
> .
>

--

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>

Software Architect / Project Manager / Scrum Master


Hi @vpassapera, it's not really much but thanks!
TdnPilot looks like a great bundle, I'll keep it in mind.


I'd split this into a separate function and make the previous ones all one-liners.


`simpleExpression`, right?


I'd actually prefer to keep the original comment about Blue Skin to indicate where the styles originated.


`JPAJTATest`


@jferris Thanks for fixing my commit message!


Para qué añadir la dependencia a nan_account_extension?


`nonEmptyCallArgumentList`


trinity@emerald:~/server$ ./core.sh
TrinityCore rev. unknown 1970-01-01 00:00:00 +0000 (Archived branch) (Unix,
Release) (worldserver-daemon)
<Ctrl-C> to stop.

 ______                       __
/\__  _\       __          __/\ \__
\/_/\ \/ _ __ /\_\    ___ /\_\ \, _\  __  __
   \ \ \/\`'__\/\ \ /' _ `\/\ \ \ \/ /\ \/\ \
    \ \ \ \ \/ \ \ \/\ \/\ \ \ \ \ \_\ \ \_\ \
     \ \_\ \_\  \ \_\ \_\ \_\ \_\ \__\\/`____ \
      \/_/\/_/   \/_/\/_/\/_/\/_/\/__/ `/___/> \
                                 C O R E  /\___/
http://TrinityCore.org                    \/__/

Using configuration file /home/trinity/server/etc/worldserver.conf.dist.
Using SSL version: OpenSSL 1.0.1f 6 Jan 2014 (library: OpenSSL 1.0.1f 6 Jan
2014)
Using Boost version: 1.55.0
Realm running as realm ID 1 region 2 battlegroup 1
Using World DB: TDB 6.00
Using enUS DBC Locale
Will clear `logs` table of entries older than 1209600 seconds every 10
minutes.
Using DataDir /home/trinity/server/data/
WORLD: MMap data directory is: /home/trinity/server/data/mmaps
VMap support included. LineOfSight: 1, getHeight: 1, indoorCheck: 1
VMap data directory is: /home/trinity/server/data/vmaps
Loading Trinity strings...
>> Loaded 1036 trinity strings in 5 ms
Initialize data stores...
>> Initialized 143 DBC data stores in 385 ms
>> Initialized 33 DB2 data stores in 6799 ms
Loading SpellInfo store...
Segmentation fault (core dumped)
TrinityCore rev. unknown 1970-01-01 00:00:00 +0000 (Archived branch) (Unix,
Release) (worldserver-daemon)
<Ctrl-C> to stop.
 Error start worldserver

2015-03-02 23:38 GMT+03:00 VolodymyrLavrenchuk <notifications@github.com>:

> And here there is the same error on Windows:
>
> http://www.trinitycore.org/f/topic/10582-6x-is-now-the-supported-branch-610-19702/page-16
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/TrinityCore/TrinityCore/commit/5c4fd7ac4fc5121f7ac620fc4ffdfae939420ba1#commitcomment-9993584>
> .
>


`Text` is the right type, `ST` is just a synonym.


cdn-bootcss-com.b0.upaiyun.com 非常快，所以替换了。
另外 ping.chinaz.com 测试 ajax.googleapis.com 依然超时。


I think we can agree on that. Please squash and I'll take a last look.


> So you are saying that you removed the dependency on JBoss Tx from the mongodb module

Correct

> But that also mean, we no longer test mongodb + JTA. At least not in the mongodb module.

Correct. However, in the MongoDB integration test JTA is used.


trinity@emerald:~/server$ ./core.sh
TrinityCore rev. unknown 1970-01-01 00:00:00 +0000 (Archived branch) (Unix, Release) (worldserver-daemon)
<Ctrl-C> to stop.

 ______                       __
/\__  _\       __          __/\ \__
\/_/\ \/ _ __ /\_\    ___ /\_\ \, _\  __  __
   \ \ \/\`'__\/\ \ /' _ `\/\ \ \ \/ /\ \/\ \
    \ \ \ \ \/ \ \ \/\ \/\ \ \ \ \ \_\ \ \_\ \
     \ \_\ \_\  \ \_\ \_\ \_\ \_\ \__\\/`____ \
      \/_/\/_/   \/_/\/_/\/_/\/_/\/__/ `/___/> \
                                 C O R E  /\___/
http://TrinityCore.org                    \/__/

Using configuration file /home/trinity/server/etc/worldserver.conf.dist.
Using SSL version: OpenSSL 1.0.1f 6 Jan 2014 (library: OpenSSL 1.0.1f 6 Jan 2014)
Using Boost version: 1.55.0
Realm running as realm ID 1 region 2 battlegroup 1
Using World DB: TDB 6.00
Using enUS DBC Locale
Will clear `logs` table of entries older than 1209600 seconds every 10 minutes.
Using DataDir /home/trinity/server/data/
WORLD: MMap data directory is: /home/trinity/server/data/mmaps
VMap support included. LineOfSight: 1, getHeight: 1, indoorCheck: 1
VMap data directory is: /home/trinity/server/data/vmaps
Loading Trinity strings...
>> Loaded 1036 trinity strings in 5 ms
Initialize data stores...
>> Initialized 143 DBC data stores in 385 ms
>> Initialized 33 DB2 data stores in 6799 ms
Loading SpellInfo store...
Segmentation fault (core dumped)

How to solved this problem?


I can't follow your point there, but then it is very early in the morning here.

the problem was that it needed to return false if it found no groups (count = 0) in order for this line:
```php
$is_member = ModUtil::apiFunc('ZikulaGroupsModule', 'user', 'isgroupmember', array('gid' => $args['gid'], 'uid' => $args['uid']));
```

to be false.

previously it was returning true. see #2301


No es necesario añadir el onchange, en la factura ya está con la nueva api por lo que en la vista sobra.


My theme! :P


simply checking for `is_array` doesn't work because if there are no groups, it returns and empty array.


Why you don't check the return value of ``git_submodule_path`` like you do with ``git_submodule_url`` ?


make this an assert, because it cannot happen.


Shouldn't ``py_submoudle->repo`` be set to NULL if ``repo`` is NULL?


1. Use tabs for indentation
1. Check your code in PyGMO:
```Python
from PyGMO import problem
print problem.cec2006(1).best_x  # Outputs the minima
print problem.himmelblau().best_x  # Outputs empty tuple because you never call initialize_best() anywhere (see https://github.com/esa/pagmo/blob/master/src/problem/cec2006.cpp#L75)
```


Yes, I disagree with it as well. @unho can you sort this out with julen please?


test Push


Yup ^w^


What troubles exactly? IIRC the dont-inline-if-not-possible is only enabled for JS, so genpy will always get complex exprs to generate, if any. However, here there's even no usage of a same var twice, so it should be safe. I see these Impl classes as some hack and I think if there are any problems that become a reason to use this approach, we should fix them in the compiler.

Unless I'm misunderstanding something, of course. @Simn?


Waaait. Plus and minus have different precedence? To be fair, it should actually work, but...


yes, but that's not my point.  there shouldn't be a FIXME for this, but it should be fixed.  (also note that we agreed that we use string-conversions type synonyms consistently.)


NB! Sain tööle ka localhost wampserveris.

Vaja lubada apache conf kaustas rewrite failis http.conf


tesst comment


I don't really know what you're talking about.


replace some lang keys values - Looks well.


Actually I think I was wrong on this - this commit is probably fine - see #269


I don't think users need to know about content_shell, in most cases.  It is being added so that the public automatic testing framework can test on the browser, but users shouldn't need to run it themselves in most cases.  If there is a failure in the browser tests, they probably want to debug it by running in dartium anyway, and if the test framework prints a command to reproduce the failure, the content_shell executable will be in that reproduction command line.  So I think this comment would make the README more complex, with no benefit.  There are many more important details left out of the SDK usage and dartium usage.


hmm, some comment might be appropriate here. Accessing the transaction manager makes really only sense for JTA (and is only in this case really needed). However, from the implementation side this method will return the transaction manager regardless, provided JBoss Transaction is on the classpath.


fixed
Now all kinds of values in cards with TYPE_MONSTER can be accessed.


It's certainly ok for now but perhaps there is a better way of doing it?..


@timowest I suppose you are rebasing this branch onto the surefire improvements?
If you want to keep the commit, you can combine this with yours.
If you don't you can drop it.


missing newline


master is still at pax-url-2.1.0...


I don't fully understand, why wall_with_posts instead of just wall and why build(:post), build(:post) twice ?


ssubnets → subnets


**[unitTests_js_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_js_branches/9498/testReport/) for this commit**


you could return an iterator instead and yield each result for better performance. Just a suggestion.


If I remember correctly you should be able to do `$menu.menuAim("destroy")`


And for #291


But way not check ```is_array``` and count? like this here:
https://github.com/zikula/core/blob/1.4/src/system/Zikula/Module/GroupsModule/Api/UserApi.php#L772
```
        if (!$group || !is_array($group) || count($group) == 0) {
            return false;
        }
```


"a WordPress product company, WooThemes, ..." reads rather clunkily to me. Maybe  "For the past three years, Maria has worked at WordPress company WooThemes, as the Internal Community Manager."


And we can do this regardless of precedenceLevel, because it binds stronger than all operators, and we never end up with e.g. `a + b[` -> `(a + b)[` because the recursive call for b will eat this bracket. Right, I can buy this. (This function is taking me forever to, ahem, parse, though.)


あざます！たすかります！


> Going to throw out some more thoughts. There seem to be several separate information items here: ...

I think you have a valuable point here. There are really orthogonal questions around "transactions". A simple enum or enumset cannot cover them all. I am not sure whether I would like to bake all of it into a some class or whether it would make more sense to have a couple of dedicated methods. For the current purpose what I am after is answering #1.

Is it worth going full out and adding more than is required for this particular case? Also it seems to me that we are not even 100% regarding the right "settings" for #2 and #3 for each data store.


I'd rather raise an exception here than to return something completely else here.


I would have expected you to use the value passed into the constructor (by the subclass) instead of false, as in:

   boolean previousUserTransactionAvailability = setUserTransactionAvailable(userTransactionAvailable);


Kill it!


I didn't realise you could leave inline comments like this.


So am I;)


When you're doing the initial render on the server, you don't have `document.width` available - however media queries are. That doesn't help of course when you're doing everything on the client with inline styles - so we need a way to support both scenario's. This should work for both inline styles, as styles compiled to CSS.

I think this is a good syntax to support both sides: https://github.com/js-next/react-style/blob/media-queries/examples/simple/index.js#L111. If you disagree, please tell what you would like to have otherwise.

Also, you can still use document.width if you want to :+1:


I wouldn't mention \\n here, rather talk a bit more about the unescaped thing since thats more important. Since you're getting a string one wouldn't expect \n as natural split pattern anyway IMHO.


Well, it is probably fine. I actually think that adding all different languages in one manifest file is the wrong approach (bigger download, slower parsing etc) and the .desktop format on Linux showed that.

Generating the manifest.json on the server and defining what language it is in should be fine... maybe some words on i18n and generating the manifest on the server?


This is guard so this code path is only taken when developer deliberately does not set any authentication value. If only username/password is set then I think it is an developer error. Passing only one of these values into authentication code will most likely trigger and authentication error so developer will know something is wrong.


The surrounding code doesn't use spaces before semicolons and this should probably stick to the surrounding coding style. Also, I have no other choice than to trust your (g)awk skills here, but I do, so it looks good to me okay otherwise.


I'd shorten these comment for all those functions, just say

> A regex pattern that defines where to split.

This makes everything clear per se.


done


I reworked and committed color choice for Kami of the Painted Road. I started some month ago to move  choices that are wrongly handled while the spell goes to stack to resolution. But there are still a lot not changed.

I also added a newer way to check the sourceObject here that gurantees that the effect only works for the correct origin object (and not also for a e.g. cloudshifted object). It's possible because we save the origin object in the ability now.
If needed you should check object reference that way in the future.
Example:
```
        Permanent permanent = game.getPermanent(source.getSourceId());
        if (permanent != null && new MageObjectReference(permanent).refersTo(source.getSourceObject(game))) {
```


Rather something like "Use alternative equal-area projection; 3410 causes some countries to receive a null value for area"


Isn't this one lacking a `.references(:concept_relations)`?


I'm not registered at forge.prestashop.com, I just wrote products import
script from XML file where product category is specified by category path
(Home/Category1/Category2) and while debugging I noticed that if there is
another category named "Category1" under other parent category then while
creating "Category2" it gets wrong parent id, from that other category.
After I updated Category.php with same "if id_parent_category else" clause
the problem was solved.

 P.S. Sorry for my english :)

On Fri, Mar 6, 2015 at 11:49 AM, Gregory Roussac <notifications@github.com>
wrote:

> Hi,
>
> Would mind you mind explaining that again on forge.prestashop.com and
> joining your csv ?
>
> Regards
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/PrestaShop/PrestaShop/commit/96fd3f3d32afb1f8c6db1e6fb954fa1b99967033#commitcomment-10068010>
> .
>

--
Pagarbiai,
Denas Pavlavičius
Inžinierius-programuotojas


> As for me, I made Entware package manager as static binary. No matter how f\w toolchain will be changed, ipkg will remains stable and working.

Makes perfect sense. Advice followed: 4164b911e62d691c98f231dc5f949858e99c26fe
Thanks again!


The ER just turns on the maintenance mode and not the "core only" mode.


Can also be shortened. You're remembering me of my german classes... babble babble babble... sorry but you know what I mean, do you? If the doc comment is longer than the function it won't be of so much help because people don't read it.

One sees clearly at the signature that its optional. I'm not sure but I think in our sphinx generated documentation this will apear automatically.

So proposal for shorter description:

```
    :param max_split:            Defines the maximum number of splits. If 0 is provided, unlimited splits are made.
```

You did specify how the return value behaves in different cases, that should go into the spec of the return value which in turn is a bit short. ;)


@rakuco thx


Yeah... The problem is that on a pubsub service, you don't want just anyone able to create nodes by publishing.

But yes, it needs putting into the disco#info response for the account, too.


(Don't take that personally I just tried to illustrate it a bit... you're not as bad as my german teacher :))


Hello,
i get a crash when closing my app. the session doesn't seem to be closed, so i need to shutdown my camera and turn it on before i can launch the app again...
i'm running this code on windows 8.
any idea ?
cheers,
guillaume


this comment doesnt add information to the code. Overdocumentation, I know you meant it well though.


But way not check ```is_array``` and count? like this here:
https://github.com/zikula/core/blob/1.4/src/system/Zikula/Module/GroupsModule/Api/UserApi.php#L772
```
        if (!$group || !is_array($group) || count($group) == 0) {
            return false;
        }
```


88737258-EPW-Ruby-Access (jasondegraw) - Win64-Windows-7-VisualStudio-12: OK (2174 of 2196 tests passed)

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


didn't you mean unescaped?


Ok. Sorry I didn't have time to make it well-formed or wrap it up as xspec tests yet. Let me know if you need something more from me with regards to these tests.


Cool~
Still, try use 'enumerate' to simplify the code.
Use 'for i in range(len(num))' is a C++/Java style.
Use 'for i, n in enumerate(num)' will look better.


Because I stored it in an array, I had to give them different precedence levels.


Fair enough


Go to your vendor and ask him. Or ask someone who has the device... Start a thread on xda.


hey denis,  thank you very much for that fast commit!


1: M110 missing component name


1: M100 needs more reviewers
1: M101 signature is missing
3: M102 unrecognized bullet/signature
1: M110 missing component name


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


1: M100 needs more reviewers
1: M101 signature is missing
3: M102 unrecognized bullet/signature
1: M110 missing component name
1: M190 line is too long (51 > 50)


1: D100 Docstring missing


1: D100 Docstring missing
3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
20:1: E302 expected 2 blank lines, found 1
20: D401 First line should be imperative: 'Retrieve', not 'Retrieves'
20: D400 First line should end with '.', not 'd'
20: L101 copyright is missing


1: D100 Docstring missing
3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
21: L101 copyright is missing


1: D100 Docstring missing
3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
21: D401 First line should be imperative: 'Return', not 'Returns'
21: L101 copyright is missing


1:1: E266 too many leading '#' for block comment
1: D100 Docstring missing
2:1: E266 too many leading '#' for block comment
3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
16: D103 Docstring missing
16: L101 copyright is missing


1: D100 Docstring missing
3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
21: D401 First line should be imperative: 'Searche', not 'Searches'
21: D400 First line should end with '.', not 'd'
21: L101 copyright is missing
33:9: B901 blind except: statement


(or generator)


> For the current purpose what I am after is answering #1.

Is it really? Would this help to decide which `Transaction` implementation to return (emulated local vs. JTA)? I would have said that you'd actually need 2. and 3. here, 1. not being strictly needed atm.

Maybe even only 3. to find out whether "emulated local" should be used when "RESOURCE_LOCAL" is requested or whether we should fall back to JTA (as we do as of today).

+1 for adding only the stuff needed right now. I only put everything down to get a clearer picture for myself :)

I'd prefer a separate object instead of several fine-grained dedicated methods in order to keep the `GridDialect` interface lean.


Any reason for the spaces after/before the parentheses? Also please drop the spaces before semicolons.


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
20: L101 copyright is missing
24:1: E402 module level import not at top of file
25:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
29:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, merge_error_messages, run_test_suite, test_web_page_content
29:1: E402 module level import not at top of file
30:6: E126 continuation line over-indented for hanging indent
64:49: E127 continuation line over-indented for visual indent
66:49: E127 continuation line over-indented for visual indent
259:111: E203 whitespace before ','
283:114: E203 whitespace before ','
289:1: E302 expected 2 blank lines, found 1
313:47: E202 whitespace before ')'
351:9: B901 blind except: statement
379:1: E302 expected 2 blank lines, found 1
384:130: E203 whitespace before ','
393:102: E203 whitespace before ','
402:113: E203 whitespace before ','


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
22: L101 copyright is missing
27:1: E402 module level import not at top of file
28:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, merge_error_messages, run_test_suite, test_web_page_content
28:1: I100 Imports statements are in the wrong order. from invenio.testsuite should be before from mechanize
28:1: I201 Missing newline before sections or imports.
28:1: E402 module level import not at top of file
29:31: E126 continuation line over-indented for hanging indent
31:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from invenio.testsuite
31:1: E402 module level import not at top of file
32:1: E402 module level import not at top of file
36:1: E302 expected 2 blank lines, found 1
71:1: E302 expected 2 blank lines, found 1
89:17: E128 continuation line under-indented for visual indent
91:17: E128 continuation line under-indented for visual indent
95:9: E303 too many blank lines (3)
104:17: E128 continuation line under-indented for visual indent
105:55: E502 the backslash is redundant between brackets
111:13: E128 continuation line under-indented for visual indent


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
20: L101 copyright is missing
83:73: E502 the backslash is redundant between brackets
84:17: E128 continuation line under-indented for visual indent
99:84: E712 comparison to False should be 'if cond is False:' or 'if not cond:'


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


1: M111 unrecognized component name: BibIndex


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
19: L101 copyright is missing
23:1: E402 module level import not at top of file
24:1: I100 Imports statements are in the wrong order. import os should be before from invenio.testsuite
24:1: I201 Missing newline before sections or imports.
24:1: E402 module level import not at top of file
25:1: E402 module level import not at top of file
26:1: I201 Missing newline before sections or imports.
26:1: E402 module level import not at top of file
28:1: I101 Imported names are in the wrong order. Should be make_test_suite, nottest, run_test_suite
28:1: E402 module level import not at top of file
29:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from invenio.testsuite
29:1: E402 module level import not at top of file
30:1: E402 module level import not at top of file
32:1: E402 module level import not at top of file
115:59: E251 unexpected spaces around keyword / parameter equals
115:61: E251 unexpected spaces around keyword / parameter equals
115:74: E251 unexpected spaces around keyword / parameter equals
115:76: E251 unexpected spaces around keyword / parameter equals
163:46: E251 unexpected spaces around keyword / parameter equals
164:41: E251 unexpected spaces around keyword / parameter equals
164:43: E251 unexpected spaces around keyword / parameter equals
173:50: E128 continuation line under-indented for visual indent
174:68: E126 continuation line over-indented for hanging indent
185:56: E251 unexpected spaces around keyword / parameter equals
185:58: E251 unexpected spaces around keyword / parameter equals
214:49: E231 missing whitespace after ':'
214:27: E251 unexpected spaces around keyword / parameter equals
214:29: E251 unexpected spaces around keyword / parameter equals
215:45: E231 missing whitespace after ':'
226:49: E231 missing whitespace after ':'
226:27: E251 unexpected spaces around keyword / parameter equals
226:29: E251 unexpected spaces around keyword / parameter equals
227:45: E231 missing whitespace after ':'
247:24: E261 at least two spaces before inline comment
247:25: E262 inline comment should start with '# '
292:52: E231 missing whitespace after ':'
292:27: E251 unexpected spaces around keyword / parameter equals
292:29: E251 unexpected spaces around keyword / parameter equals
293:45: E231 missing whitespace after ':'
304:52: E231 missing whitespace after ':'
304:27: E251 unexpected spaces around keyword / parameter equals
304:29: E251 unexpected spaces around keyword / parameter equals
305:45: E231 missing whitespace after ':'
309:5: E303 too many blank lines (2)
379:51: E231 missing whitespace after ':'
379:27: E251 unexpected spaces around keyword / parameter equals
379:29: E251 unexpected spaces around keyword / parameter equals
380:45: E231 missing whitespace after ':'
391:51: E231 missing whitespace after ':'
391:27: E251 unexpected spaces around keyword / parameter equals
391:29: E251 unexpected spaces around keyword / parameter equals
392:45: E231 missing whitespace after ':'
396:5: E303 too many blank lines (2)
409:5: E303 too many blank lines (2)
443:45: E231 missing whitespace after ':'
443:27: E251 unexpected spaces around keyword / parameter equals
443:29: E251 unexpected spaces around keyword / parameter equals
447:5: E303 too many blank lines (2)
455:45: E231 missing whitespace after ':'
455:27: E251 unexpected spaces around keyword / parameter equals
455:29: E251 unexpected spaces around keyword / parameter equals
459:5: E303 too many blank lines (2)
471:5: E303 too many blank lines (2)
483:5: E303 too many blank lines (2)
499:1: E303 too many blank lines (3)
514:45: E231 missing whitespace after ':'
514:27: E251 unexpected spaces around keyword / parameter equals
514:29: E251 unexpected spaces around keyword / parameter equals
525:45: E231 missing whitespace after ':'
525:27: E251 unexpected spaces around keyword / parameter equals
525:29: E251 unexpected spaces around keyword / parameter equals
529:5: E303 too many blank lines (2)
541:5: E303 too many blank lines (2)
577:42: E251 unexpected spaces around keyword / parameter equals
577:44: E251 unexpected spaces around keyword / parameter equals
595:18: E127 continuation line over-indented for visual indent
597:60: E231 missing whitespace after ','
602:18: E127 continuation line over-indented for visual indent
604:60: E231 missing whitespace after ','
609:18: E127 continuation line over-indented for visual indent
611:60: E231 missing whitespace after ','
659:45: E231 missing whitespace after ':'
659:27: E251 unexpected spaces around keyword / parameter equals
659:29: E251 unexpected spaces around keyword / parameter equals
670:45: E231 missing whitespace after ':'
670:27: E251 unexpected spaces around keyword / parameter equals
670:29: E251 unexpected spaces around keyword / parameter equals
674:5: E303 too many blank lines (2)
686:5: E303 too many blank lines (2)
714:42: E231 missing whitespace after ':'
714:27: E251 unexpected spaces around keyword / parameter equals
714:29: E251 unexpected spaces around keyword / parameter equals
715:45: E231 missing whitespace after ':'
726:42: E231 missing whitespace after ':'
726:27: E251 unexpected spaces around keyword / parameter equals
726:29: E251 unexpected spaces around keyword / parameter equals
727:45: E231 missing whitespace after ':'
731:5: E303 too many blank lines (2)
763:9: F841 local variable 'bibRecID' is assigned to but never used
773:28: E261 at least two spaces before inline comment
795:20: E261 at least two spaces before inline comment
828:81: E231 missing whitespace after ','
829:94: E231 missing whitespace after ','
848:45: E251 unexpected spaces around keyword / parameter equals
848:47: E251 unexpected spaces around keyword / parameter equals
876:81: E231 missing whitespace after ','
877:94: E231 missing whitespace after ','
895:45: E251 unexpected spaces around keyword / parameter equals
895:47: E251 unexpected spaces around keyword / parameter equals
984:66: E231 missing whitespace after ','
991:66: E231 missing whitespace after ','
992:67: E231 missing whitespace after ','
997:66: E231 missing whitespace after ','
998:58: E231 missing whitespace after ','
1003:66: E231 missing whitespace after ','
1004:61: E231 missing whitespace after ','
1009:66: E231 missing whitespace after ','
1026:43: E203 whitespace before ':'
1026:44: E231 missing whitespace after ':'
1031:1: E303 too many blank lines (4)
1051:53: E251 unexpected spaces around keyword / parameter equals
1051:55: E251 unexpected spaces around keyword / parameter equals
1069:53: E251 unexpected spaces around keyword / parameter equals
1069:55: E251 unexpected spaces around keyword / parameter equals
1075:5: E303 too many blank lines (2)
1087:5: E303 too many blank lines (2)
1099:5: E303 too many blank lines (2)
1158:91: E231 missing whitespace after ','
1165:5: E303 too many blank lines (2)
1171:65: E231 missing whitespace after ','
1297:34: E712 comparison to True should be 'if cond is True:' or 'if cond:'
1367:5: E303 too many blank lines (2)
1373:5: E303 too many blank lines (2)
1429:39: E231 missing whitespace after ','
1432:1: E302 expected 2 blank lines, found 1
1441:25: E261 at least two spaces before inline comment
1451:25: E261 at least two spaces before inline comment
1457:1: E303 too many blank lines (3)


ah now I'm switching names around a bit, not sure if it's the best naming scheme because this would indicate that we'd only split by the delimiter pattern if it is actually escaped. But instead we ignore escapes which is a bit misleading IMO.


True


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
19: L101 copyright is missing
23:1: E402 module level import not at top of file
24:1: I100 Imports statements are in the wrong order. import os should be before from invenio.testsuite
24:1: I201 Missing newline before sections or imports.
24:1: E402 module level import not at top of file
25:1: E402 module level import not at top of file
26:1: I201 Missing newline before sections or imports.
26:1: E402 module level import not at top of file
28:1: I101 Imported names are in the wrong order. Should be make_test_suite, nottest, run_test_suite
28:1: E402 module level import not at top of file
29:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from invenio.testsuite
29:1: E402 module level import not at top of file
30:1: E402 module level import not at top of file
32:1: E402 module level import not at top of file
115:59: E251 unexpected spaces around keyword / parameter equals
115:61: E251 unexpected spaces around keyword / parameter equals
115:74: E251 unexpected spaces around keyword / parameter equals
115:76: E251 unexpected spaces around keyword / parameter equals
163:46: E251 unexpected spaces around keyword / parameter equals
164:41: E251 unexpected spaces around keyword / parameter equals
164:43: E251 unexpected spaces around keyword / parameter equals
173:50: E128 continuation line under-indented for visual indent
174:68: E126 continuation line over-indented for hanging indent
185:56: E251 unexpected spaces around keyword / parameter equals
185:58: E251 unexpected spaces around keyword / parameter equals
214:49: E231 missing whitespace after ':'
214:27: E251 unexpected spaces around keyword / parameter equals
214:29: E251 unexpected spaces around keyword / parameter equals
215:45: E231 missing whitespace after ':'
226:49: E231 missing whitespace after ':'
226:27: E251 unexpected spaces around keyword / parameter equals
226:29: E251 unexpected spaces around keyword / parameter equals
227:45: E231 missing whitespace after ':'
247:24: E261 at least two spaces before inline comment
247:25: E262 inline comment should start with '# '
292:52: E231 missing whitespace after ':'
292:27: E251 unexpected spaces around keyword / parameter equals
292:29: E251 unexpected spaces around keyword / parameter equals
293:45: E231 missing whitespace after ':'
304:52: E231 missing whitespace after ':'
304:27: E251 unexpected spaces around keyword / parameter equals
304:29: E251 unexpected spaces around keyword / parameter equals
305:45: E231 missing whitespace after ':'
309:5: E303 too many blank lines (2)
379:51: E231 missing whitespace after ':'
379:27: E251 unexpected spaces around keyword / parameter equals
379:29: E251 unexpected spaces around keyword / parameter equals
380:45: E231 missing whitespace after ':'
391:51: E231 missing whitespace after ':'
391:27: E251 unexpected spaces around keyword / parameter equals
391:29: E251 unexpected spaces around keyword / parameter equals
392:45: E231 missing whitespace after ':'
396:5: E303 too many blank lines (2)
409:5: E303 too many blank lines (2)
443:45: E231 missing whitespace after ':'
443:27: E251 unexpected spaces around keyword / parameter equals
443:29: E251 unexpected spaces around keyword / parameter equals
447:5: E303 too many blank lines (2)
455:45: E231 missing whitespace after ':'
455:27: E251 unexpected spaces around keyword / parameter equals
455:29: E251 unexpected spaces around keyword / parameter equals
459:5: E303 too many blank lines (2)
471:5: E303 too many blank lines (2)
483:5: E303 too many blank lines (2)
499:1: E303 too many blank lines (3)
514:45: E231 missing whitespace after ':'
514:27: E251 unexpected spaces around keyword / parameter equals
514:29: E251 unexpected spaces around keyword / parameter equals
525:45: E231 missing whitespace after ':'
525:27: E251 unexpected spaces around keyword / parameter equals
525:29: E251 unexpected spaces around keyword / parameter equals
529:5: E303 too many blank lines (2)
541:5: E303 too many blank lines (2)
577:42: E251 unexpected spaces around keyword / parameter equals
577:44: E251 unexpected spaces around keyword / parameter equals
595:18: E127 continuation line over-indented for visual indent
597:60: E231 missing whitespace after ','
602:18: E127 continuation line over-indented for visual indent
604:60: E231 missing whitespace after ','
609:18: E127 continuation line over-indented for visual indent
611:60: E231 missing whitespace after ','
659:45: E231 missing whitespace after ':'
659:27: E251 unexpected spaces around keyword / parameter equals
659:29: E251 unexpected spaces around keyword / parameter equals
670:45: E231 missing whitespace after ':'
670:27: E251 unexpected spaces around keyword / parameter equals
670:29: E251 unexpected spaces around keyword / parameter equals
674:5: E303 too many blank lines (2)
686:5: E303 too many blank lines (2)
714:42: E231 missing whitespace after ':'
714:27: E251 unexpected spaces around keyword / parameter equals
714:29: E251 unexpected spaces around keyword / parameter equals
715:45: E231 missing whitespace after ':'
726:42: E231 missing whitespace after ':'
726:27: E251 unexpected spaces around keyword / parameter equals
726:29: E251 unexpected spaces around keyword / parameter equals
727:45: E231 missing whitespace after ':'
731:5: E303 too many blank lines (2)
763:9: F841 local variable 'bibRecID' is assigned to but never used
772:28: E261 at least two spaces before inline comment
794:20: E261 at least two spaces before inline comment
827:81: E231 missing whitespace after ','
828:94: E231 missing whitespace after ','
847:45: E251 unexpected spaces around keyword / parameter equals
847:47: E251 unexpected spaces around keyword / parameter equals
875:81: E231 missing whitespace after ','
876:94: E231 missing whitespace after ','
894:45: E251 unexpected spaces around keyword / parameter equals
894:47: E251 unexpected spaces around keyword / parameter equals
983:66: E231 missing whitespace after ','
990:66: E231 missing whitespace after ','
997:66: E231 missing whitespace after ','
1004:66: E231 missing whitespace after ','
1011:66: E231 missing whitespace after ','
1030:43: E203 whitespace before ':'
1030:44: E231 missing whitespace after ':'
1035:1: E303 too many blank lines (4)
1055:53: E251 unexpected spaces around keyword / parameter equals
1055:55: E251 unexpected spaces around keyword / parameter equals
1073:53: E251 unexpected spaces around keyword / parameter equals
1073:55: E251 unexpected spaces around keyword / parameter equals
1079:5: E303 too many blank lines (2)
1091:5: E303 too many blank lines (2)
1103:5: E303 too many blank lines (2)
1162:91: E231 missing whitespace after ','
1169:5: E303 too many blank lines (2)
1175:65: E231 missing whitespace after ','
1301:34: E712 comparison to True should be 'if cond is True:' or 'if cond:'
1371:5: E303 too many blank lines (2)
1377:5: E303 too many blank lines (2)
1433:39: E231 missing whitespace after ','
1436:1: E302 expected 2 blank lines, found 1
1445:25: E261 at least two spaces before inline comment
1455:25: E261 at least two spaces before inline comment
1461:1: E303 too many blank lines (3)


1: M111 unrecognized component name: WebAlert


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
20: L101 copyright is missing
24:1: E402 module level import not at top of file
25:1: I100 Imports statements are in the wrong order. import sys should be before from cStringIO
25:1: E402 module level import not at top of file
26:1: I100 Imports statements are in the wrong order. import datetime should be before import sys
26:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
29:1: F401 'cfg' imported but unused
29:1: E402 module level import not at top of file
30:1: E402 module level import not at top of file
32:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, merge_error_messages, run_test_suite, test_web_page_content
32:1: E402 module level import not at top of file
33:31: E126 continuation line over-indented for hanging indent
127:37: E261 at least two spaces before inline comment
166:37: W601 .has_key() is deprecated, use 'in'


1: M111 unrecognized component name: WebSearch


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
22: L101 copyright is missing
24:1: F401 'InvenioTestCase' imported but unused
25:1: I100 Imports statements are in the wrong order. import os should be before from invenio.testsuite
25:1: I201 Missing newline before sections or imports.
29:1: I100 Imports statements are in the wrong order. import socket should be before import urlparse
34:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from invenio.utils.json
46:1: E266 too many leading '#' for block comment
47:1: E266 too many leading '#' for block comment
48:1: E266 too many leading '#' for block comment
49:1: E266 too many leading '#' for block comment
63:21: E126 continuation line over-indented for hanging indent
65:21: E126 continuation line over-indented for hanging indent
86:17: E126 continuation line over-indented for hanging indent
91:17: E126 continuation line over-indented for hanging indent
98:17: E126 continuation line over-indented for hanging indent
142:9: E266 too many leading '#' for block comment
143:9: E266 too many leading '#' for block comment
212:21: E266 too many leading '#' for block comment


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
19: L101 copyright is missing
23:1: I101 Imported names are in the wrong order. Should be CFG_BIBAUTHORITY_PREFIX_SEP, CFG_BIBAUTHORITY_RECORD_CONTROL_NUMBER_FIELD, CFG_BIBAUTHORITY_TYPE_NAMES
23:1: E402 module level import not at top of file
28:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, run_test_suite
28:1: E402 module level import not at top of file
30:1: I100 Imports statements are in the wrong order. from invenio.base.wrappers should be before from invenio.testsuite
30:1: E402 module level import not at top of file
41:1: E302 expected 2 blank lines, found 1


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
20: L101 copyright is missing
24:1: E402 module level import not at top of file
25:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, merge_error_messages, run_test_suite, test_web_page_content
25:1: E402 module level import not at top of file
26:31: E126 continuation line over-indented for hanging indent
57:41: E128 continuation line under-indented for visual indent
65:31: E127 continuation line over-indented for visual indent
68:41: E128 continuation line under-indented for visual indent
76:31: E127 continuation line over-indented for visual indent
79:41: E128 continuation line under-indented for visual indent


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
21: L101 copyright is missing
24:1: I100 Imports statements are in the wrong order. import os should be before import sys
46:13: E128 continuation line under-indented for visual indent
47:13: E128 continuation line under-indented for visual indent
53:13: E128 continuation line under-indented for visual indent
54:13: E128 continuation line under-indented for visual indent
56:13: E128 continuation line under-indented for visual indent
57:13: E128 continuation line under-indented for visual indent
59:13: E128 continuation line under-indented for visual indent
60:13: E128 continuation line under-indented for visual indent
74:13: E128 continuation line under-indented for visual indent
86:9: E303 too many blank lines (2)
93:5: E303 too many blank lines (2)
116:5: E303 too many blank lines (3)
120:9: E303 too many blank lines (2)
132:13: E128 continuation line under-indented for visual indent
144:9: E303 too many blank lines (2)
147:9: E303 too many blank lines (2)
153:5: E303 too many blank lines (3)
157:9: E303 too many blank lines (2)
166:9: E303 too many blank lines (2)
172:13: E128 continuation line under-indented for visual indent
186:9: E303 too many blank lines (2)
192:5: E303 too many blank lines (3)
209:17: E128 continuation line under-indented for visual indent
225:9: E303 too many blank lines (3)
288:1: E302 expected 2 blank lines, found 1
351:1: E302 expected 2 blank lines, found 1
416:1: E302 expected 2 blank lines, found 1
666:1: E303 too many blank lines (3)


1: D100 Docstring missing
3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
20: L101 copyright is missing
21:1: I100 Imports statements are in the wrong order. from fixture should be before from invenio.config
21:1: I201 Missing newline before sections or imports.
22:1: I101 Imported names are in the wrong order. Should be FieldData, FormatData
22:1: I201 Missing newline before sections or imports.
25: D101 Docstring missing
108: D101 Docstring missing
858:18: E231 missing whitespace after ','
859:18: E231 missing whitespace after ','
860:18: E231 missing whitespace after ','
868:18: E231 missing whitespace after ','
869:18: E231 missing whitespace after ','
870:18: E231 missing whitespace after ','
878:18: E231 missing whitespace after ','
879:18: E231 missing whitespace after ','
880:18: E231 missing whitespace after ','
888:18: E231 missing whitespace after ','
889:18: E231 missing whitespace after ','
890:18: E231 missing whitespace after ','
898:18: E231 missing whitespace after ','
899:18: E231 missing whitespace after ','
900:18: E231 missing whitespace after ','
905: D101 Docstring missing
1034: D101 Docstring missing
1057: D101 Docstring missing
1535: D101 Docstring missing
1613: D101 Docstring missing
1961: D101 Docstring missing
2124: D101 Docstring missing
2799: D101 Docstring missing
3017: D101 Docstring missing


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
20: L101 copyright is missing
24:1: E402 module level import not at top of file
25:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, run_test_suite, test_web_page_content, test_web_page_existence
25:1: E402 module level import not at top of file
26:31: E126 continuation line over-indented for hanging indent


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
23: L101 copyright is missing
27:1: E402 module level import not at top of file
28:1: I101 Imported names are in the wrong order. Should be cgi, urlparse
28:16: E401 multiple imports on one line
28:1: E402 module level import not at top of file
29:1: I100 Imports statements are in the wrong order. import sys should be before import urlparse, cgi
29:1: E402 module level import not at top of file
30:1: I100 Imports statements are in the wrong order. import cStringIO should be before import sys
30:1: E402 module level import not at top of file
37:1: E402 module level import not at top of file
38:1: I101 Imported names are in the wrong order. Should be Browser, HTTPError, LinkNotFoundError
38:1: I201 Missing newline before sections or imports.
38:1: E402 module level import not at top of file
40:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from mechanize
40:1: E402 module level import not at top of file
41:1: E402 module level import not at top of file
42:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, get_authenticated_mechanize_browser, make_surl, make_test_suite, make_url, merge_error_messages, nottest, run_test_suite, test_web_page_content
42:1: E402 module level import not at top of file
43:31: E126 continuation line over-indented for hanging indent
48:1: E402 module level import not at top of file
55:10: E261 at least two spaces before inline comment
55:11: E262 inline comment should start with '# '
67:1: E302 expected 2 blank lines, found 1
89:1: E302 expected 2 blank lines, found 1
110:1: E302 expected 2 blank lines, found 1
144:44: E225 missing whitespace around operator
144:70: E225 missing whitespace around operator
208:1: E302 expected 2 blank lines, found 1
232:9: E266 too many leading '#' for block comment
249:5: E303 too many blank lines (2)
300:1: E302 expected 2 blank lines, found 1
352:105: E502 the backslash is redundant between brackets
361:26: E128 continuation line under-indented for visual indent
367:26: E128 continuation line under-indented for visual indent
377:5: E301 expected 1 blank line, found 0
468:21: B901 blind except: statement
473:17: E303 too many blank lines (2)
474:54: E713 test for membership should be 'not in'
526:44: E128 continuation line under-indented for visual indent
527:44: E128 continuation line under-indented for visual indent
530:1: E302 expected 2 blank lines, found 1
565:56: E251 unexpected spaces around keyword / parameter equals
565:58: E251 unexpected spaces around keyword / parameter equals
566:61: E251 unexpected spaces around keyword / parameter equals
566:63: E251 unexpected spaces around keyword / parameter equals
567:63: E251 unexpected spaces around keyword / parameter equals
567:65: E251 unexpected spaces around keyword / parameter equals
575:62: E251 unexpected spaces around keyword / parameter equals
576:64: E251 unexpected spaces around keyword / parameter equals
585:62: E251 unexpected spaces around keyword / parameter equals
586:63: E251 unexpected spaces around keyword / parameter equals
586:65: E251 unexpected spaces around keyword / parameter equals
595:62: E251 unexpected spaces around keyword / parameter equals
601:56: E251 unexpected spaces around keyword / parameter equals
601:58: E251 unexpected spaces around keyword / parameter equals
602:61: E251 unexpected spaces around keyword / parameter equals
602:63: E251 unexpected spaces around keyword / parameter equals
606:56: E251 unexpected spaces around keyword / parameter equals
606:58: E251 unexpected spaces around keyword / parameter equals
607:61: E251 unexpected spaces around keyword / parameter equals
607:63: E251 unexpected spaces around keyword / parameter equals
611:56: E251 unexpected spaces around keyword / parameter equals
611:58: E251 unexpected spaces around keyword / parameter equals
612:61: E251 unexpected spaces around keyword / parameter equals
612:63: E251 unexpected spaces around keyword / parameter equals
630:17: E203 whitespace before ':'
631:16: E203 whitespace before ':'
632:17: E203 whitespace before ':'
646:17: E203 whitespace before ':'
647:16: E203 whitespace before ':'
648:17: E203 whitespace before ':'
662:17: E203 whitespace before ':'
663:16: E203 whitespace before ':'
664:17: E203 whitespace before ':'
778:38: E203 whitespace before ':'
854:44: E128 continuation line under-indented for visual indent
855:44: E128 continuation line under-indented for visual indent
873:65: E128 continuation line under-indented for visual indent
873:70: E231 missing whitespace after ','
874:71: E126 continuation line over-indented for hanging indent
875:41: E131 continuation line unaligned for hanging indent
875:53: E231 missing whitespace after ':'
876:42: E122 continuation line missing indentation or outdented
876:56: E231 missing whitespace after ':'
885:22: E231 missing whitespace after ','
887:29: E231 missing whitespace after ':'
888:32: E231 missing whitespace after ':'
891:5: E303 too many blank lines (2)
915:13: E128 continuation line under-indented for visual indent
931:62: E261 at least two spaces before inline comment
965:1: E302 expected 2 blank lines, found 1
1005:5: E303 too many blank lines (2)
1161:1: E302 expected 2 blank lines, found 1
1247:17: E128 continuation line under-indented for visual indent
1373:8: E122 continuation line missing indentation or outdented
1374:8: E122 continuation line missing indentation or outdented
1375:8: E122 continuation line missing indentation or outdented
1397:81: E231 missing whitespace after ','
1406:81: E231 missing whitespace after ','
1934:5: E303 too many blank lines (2)
1936:9: E122 continuation line missing indentation or outdented
1940:1: E302 expected 2 blank lines, found 1
2163:8: E122 continuation line missing indentation or outdented
2164:8: E122 continuation line missing indentation or outdented
2165:8: E122 continuation line missing indentation or outdented
2650:21: E122 continuation line missing indentation or outdented
2651:21: E122 continuation line missing indentation or outdented
2652:21: E122 continuation line missing indentation or outdented
2771:1: E303 too many blank lines (3)
2835:8: E122 continuation line missing indentation or outdented
3083:21: E122 continuation line missing indentation or outdented
3276:13: E128 continuation line under-indented for visual indent
3367:5: E303 too many blank lines (2)
3406:5: E303 too many blank lines (2)
3541:84: E231 missing whitespace after ','
3669:1: E302 expected 2 blank lines, found 1
3711:49: E127 continuation line over-indented for visual indent
3732:51: E127 continuation line over-indented for visual indent
3736:1: E302 expected 2 blank lines, found 1
3745:1: E302 expected 2 blank lines, found 1
3785:1: E302 expected 2 blank lines, found 1
3833:1: E302 expected 2 blank lines, found 1
3860:1: E302 expected 2 blank lines, found 1
3888:5: E303 too many blank lines (2)
3936:5: E303 too many blank lines (2)
3959:1: E302 expected 2 blank lines, found 1
3995:1: E302 expected 2 blank lines, found 1
4022:1: E302 expected 2 blank lines, found 1
4049:1: E302 expected 2 blank lines, found 1
4067:1: E302 expected 2 blank lines, found 1
4121:1: E302 expected 2 blank lines, found 1
4141:1: E302 expected 2 blank lines, found 1
4150:63: E231 missing whitespace after ','
4157:63: E231 missing whitespace after ','
4221:1: E302 expected 2 blank lines, found 1
4241:70: E231 missing whitespace after ','
4262:1: E302 expected 2 blank lines, found 1
4301:1: E302 expected 2 blank lines, found 1
4445:14: E261 at least two spaces before inline comment
4445:15: E262 inline comment should start with '# '
4449:73: E225 missing whitespace around operator
4458:73: E225 missing whitespace around operator
4459:51: E128 continuation line under-indented for visual indent
4631:19: E128 continuation line under-indented for visual indent
4662:9: E303 too many blank lines (2)
4666:5: E303 too many blank lines (3)
4758:66: E251 unexpected spaces around keyword / parameter equals
4758:68: E251 unexpected spaces around keyword / parameter equals
4766:66: E251 unexpected spaces around keyword / parameter equals
4766:68: E251 unexpected spaces around keyword / parameter equals
4774:66: E251 unexpected spaces around keyword / parameter equals
4774:68: E251 unexpected spaces around keyword / parameter equals
4782:66: E251 unexpected spaces around keyword / parameter equals
4782:68: E251 unexpected spaces around keyword / parameter equals


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
20: L101 copyright is missing
24:1: E402 module level import not at top of file
25:1: E402 module level import not at top of file
26:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
28:1: I201 Missing newline before sections or imports.
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
32:1: E402 module level import not at top of file
65:1: E302 expected 2 blank lines, found 1
75:13: E266 too many leading '#' for block comment
78:13: E266 too many leading '#' for block comment
169:99: E502 the backslash is redundant between brackets
170:9: E128 continuation line under-indented for visual indent
170:21: E251 unexpected spaces around keyword / parameter equals
195:25: E225 missing whitespace around operator
195:51: E225 missing whitespace around operator
207:1: E302 expected 2 blank lines, found 1
243:109: E251 unexpected spaces around keyword / parameter equals
247:22: E261 at least two spaces before inline comment
312:32: E201 whitespace after '('
315:16: E222 multiple spaces after operator
346:1: E303 too many blank lines (3)
355:45: E251 unexpected spaces around keyword / parameter equals
355:47: E251 unexpected spaces around keyword / parameter equals
356:46: E251 unexpected spaces around keyword / parameter equals
356:48: E251 unexpected spaces around keyword / parameter equals
356:63: E251 unexpected spaces around keyword / parameter equals
356:65: E251 unexpected spaces around keyword / parameter equals
357:43: E251 unexpected spaces around keyword / parameter equals
357:45: E251 unexpected spaces around keyword / parameter equals
359:45: E251 unexpected spaces around keyword / parameter equals
359:47: E251 unexpected spaces around keyword / parameter equals
360:46: E251 unexpected spaces around keyword / parameter equals
360:48: E251 unexpected spaces around keyword / parameter equals
360:63: E251 unexpected spaces around keyword / parameter equals
360:65: E251 unexpected spaces around keyword / parameter equals
361:43: E251 unexpected spaces around keyword / parameter equals
361:45: E251 unexpected spaces around keyword / parameter equals
368:42: E251 unexpected spaces around keyword / parameter equals
368:44: E251 unexpected spaces around keyword / parameter equals
368:59: E251 unexpected spaces around keyword / parameter equals
368:61: E251 unexpected spaces around keyword / parameter equals
369:40: E251 unexpected spaces around keyword / parameter equals
369:42: E251 unexpected spaces around keyword / parameter equals
369:66: E251 unexpected spaces around keyword / parameter equals
369:68: E251 unexpected spaces around keyword / parameter equals
370:43: E251 unexpected spaces around keyword / parameter equals
370:45: E251 unexpected spaces around keyword / parameter equals
372:42: E251 unexpected spaces around keyword / parameter equals
372:44: E251 unexpected spaces around keyword / parameter equals
372:59: E251 unexpected spaces around keyword / parameter equals
372:61: E251 unexpected spaces around keyword / parameter equals
373:40: E251 unexpected spaces around keyword / parameter equals
373:42: E251 unexpected spaces around keyword / parameter equals
373:66: E251 unexpected spaces around keyword / parameter equals
373:68: E251 unexpected spaces around keyword / parameter equals
374:43: E251 unexpected spaces around keyword / parameter equals
374:45: E251 unexpected spaces around keyword / parameter equals
384:51: E251 unexpected spaces around keyword / parameter equals
384:53: E251 unexpected spaces around keyword / parameter equals
385:35: E128 continuation line under-indented for visual indent
385:46: E251 unexpected spaces around keyword / parameter equals
385:48: E251 unexpected spaces around keyword / parameter equals
385:63: E251 unexpected spaces around keyword / parameter equals
385:65: E251 unexpected spaces around keyword / parameter equals
386:35: E128 continuation line under-indented for visual indent
386:43: E251 unexpected spaces around keyword / parameter equals
386:45: E251 unexpected spaces around keyword / parameter equals
388:51: E251 unexpected spaces around keyword / parameter equals
388:53: E251 unexpected spaces around keyword / parameter equals
389:35: E128 continuation line under-indented for visual indent
389:46: E251 unexpected spaces around keyword / parameter equals
389:48: E251 unexpected spaces around keyword / parameter equals
389:63: E251 unexpected spaces around keyword / parameter equals
389:65: E251 unexpected spaces around keyword / parameter equals
390:35: E128 continuation line under-indented for visual indent
390:43: E251 unexpected spaces around keyword / parameter equals
390:45: E251 unexpected spaces around keyword / parameter equals
398:1: E302 expected 2 blank lines, found 1
424:54: E203 whitespace before ','
426:59: E203 whitespace before ','
461:1: E302 expected 2 blank lines, found 1
481:1: E302 expected 2 blank lines, found 1
489:1: E302 expected 2 blank lines, found 1
494:35: E251 unexpected spaces around keyword / parameter equals
494:37: E251 unexpected spaces around keyword / parameter equals
497:65: E203 whitespace before ':'
497:69: E201 whitespace after '{'
497:74: E203 whitespace before ':'
497:36: E251 unexpected spaces around keyword / parameter equals
497:38: E251 unexpected spaces around keyword / parameter equals
497:56: E251 unexpected spaces around keyword / parameter equals
497:58: E251 unexpected spaces around keyword / parameter equals
502:36: E251 unexpected spaces around keyword / parameter equals
502:38: E251 unexpected spaces around keyword / parameter equals
512:35: E251 unexpected spaces around keyword / parameter equals
512:37: E251 unexpected spaces around keyword / parameter equals
515:36: E251 unexpected spaces around keyword / parameter equals
515:38: E251 unexpected spaces around keyword / parameter equals
533:28: E251 unexpected spaces around keyword / parameter equals
533:30: E251 unexpected spaces around keyword / parameter equals
533:43: E251 unexpected spaces around keyword / parameter equals
533:45: E251 unexpected spaces around keyword / parameter equals
533:60: E251 unexpected spaces around keyword / parameter equals
533:62: E251 unexpected spaces around keyword / parameter equals
534:28: E251 unexpected spaces around keyword / parameter equals
534:30: E251 unexpected spaces around keyword / parameter equals
534:43: E251 unexpected spaces around keyword / parameter equals
534:45: E251 unexpected spaces around keyword / parameter equals
534:61: E251 unexpected spaces around keyword / parameter equals
534:63: E251 unexpected spaces around keyword / parameter equals
534:70: E261 at least two spaces before inline comment
536:42: E231 missing whitespace after ','
537:42: E231 missing whitespace after ','
541:28: E251 unexpected spaces around keyword / parameter equals
541:30: E251 unexpected spaces around keyword / parameter equals
541:43: E251 unexpected spaces around keyword / parameter equals
541:45: E251 unexpected spaces around keyword / parameter equals
542:28: E251 unexpected spaces around keyword / parameter equals
542:30: E251 unexpected spaces around keyword / parameter equals
542:43: E251 unexpected spaces around keyword / parameter equals
542:45: E251 unexpected spaces around keyword / parameter equals
542:49: E261 at least two spaces before inline comment
543:43: E231 missing whitespace after ','
544:43: E231 missing whitespace after ','
547:43: E231 missing whitespace after ','
548:43: E231 missing whitespace after ','
548:65: E261 at least two spaces before inline comment
569:5: E303 too many blank lines (2)
594:14: E261 at least two spaces before inline comment
594:15: E262 inline comment should start with '# '


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
20: L101 copyright is missing
24:1: E402 module level import not at top of file
26:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from invenio.testsuite
26:1: E402 module level import not at top of file
27:1: I101 Imported names are in the wrong order. Should be make_test_suite, merge_error_messages, run_test_suite, test_web_page_content
27:1: E402 module level import not at top of file
28:31: E126 continuation line over-indented for hanging indent
46:71: E251 unexpected spaces around keyword / parameter equals


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
20: L101 copyright is missing
24:1: E402 module level import not at top of file
26:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
28:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, get_authenticated_mechanize_browser, make_test_suite, make_url, run_test_suite, test_web_page_content
28:1: E402 module level import not at top of file
129:355: E225 missing whitespace around operator
130:38: E127 continuation line over-indented for visual indent
130:48: E203 whitespace before ':'
139:192: E225 missing whitespace around operator
140:49: E203 whitespace before ':'
161:72: E222 multiple spaces after operator
213:1: E302 expected 2 blank lines, found 1
274:1: E302 expected 2 blank lines, found 1
289:5: E303 too many blank lines (2)
298:1: E302 expected 2 blank lines, found 1
382:1: E302 expected 2 blank lines, found 1
414:1: E302 expected 2 blank lines, found 1
420:11: E128 continuation line under-indented for visual indent
421:13: E128 continuation line under-indented for visual indent
426:11: E128 continuation line under-indented for visual indent
427:13: E128 continuation line under-indented for visual indent
432:11: E128 continuation line under-indented for visual indent
433:13: E128 continuation line under-indented for visual indent
438:11: E128 continuation line under-indented for visual indent
439:13: E128 continuation line under-indented for visual indent
444:11: E128 continuation line under-indented for visual indent
445:13: E128 continuation line under-indented for visual indent
450:11: E128 continuation line under-indented for visual indent
451:13: E128 continuation line under-indented for visual indent
453:1: E302 expected 2 blank lines, found 1
459:11: E128 continuation line under-indented for visual indent
460:13: E128 continuation line under-indented for visual indent
462:1: E302 expected 2 blank lines, found 1
468:11: E128 continuation line under-indented for visual indent
469:13: E128 continuation line under-indented for visual indent
474:11: E128 continuation line under-indented for visual indent
475:13: E128 continuation line under-indented for visual indent
484:11: E128 continuation line under-indented for visual indent
485:13: E128 continuation line under-indented for visual indent
490:11: E128 continuation line under-indented for visual indent
491:13: E128 continuation line under-indented for visual indent
497:13: E301 expected 1 blank line, found 0
498:35: E701 multiple statements on one line (colon)
498:49: E231 missing whitespace after ':'
498:54: E231 missing whitespace after ','
498:57: E231 missing whitespace after ','
498:62: E231 missing whitespace after ':'
499:21: E701 multiple statements on one line (colon)
499:29: E702 multiple statements on one line (semicolon)
540:5: E303 too many blank lines (2)
561:5: E303 too many blank lines (2)


3:1: E266 too many leading '#' for block comment
4:1: E266 too many leading '#' for block comment
6:1: E266 too many leading '#' for block comment
7:1: E266 too many leading '#' for block comment
8:1: E266 too many leading '#' for block comment
9:1: E266 too many leading '#' for block comment
11:1: E266 too many leading '#' for block comment
12:1: E266 too many leading '#' for block comment
13:1: E266 too many leading '#' for block comment
14:1: E266 too many leading '#' for block comment
16:1: E266 too many leading '#' for block comment
17:1: E266 too many leading '#' for block comment
18:1: E266 too many leading '#' for block comment
20: L101 copyright is missing
24:1: E402 module level import not at top of file
26:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from invenio.testsuite
26:1: E402 module level import not at top of file
27:1: I101 Imported names are in the wrong order. Should be make_test_suite, merge_error_messages, run_test_suite, test_web_page_content
27:1: E402 module level import not at top of file
28:31: E126 continuation line over-indented for hanging indent
48:71: E251 unexpected spaces around keyword / parameter equals