1: D400 First line should end with a period (not 'e')
23:1: I100 Imports statements are in the wrong order. from pprint should be before from string
24:1: I100 Imports statements are in the wrong order. import os should be before from pprint
29:1: I101 Imported names are in the wrong order. Should be task_low_level_submission, task_update_progress, write_message
30:30: E126 continuation line over-indented for hanging indent
34:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibdocfile.api should be before from invenio.legacy.bibsched.bibtask
35:1: I101 Imported names are in the wrong order. Should be assure_quality, encode_video
38:41: E126 continuation line over-indented for hanging indent
42:1: I100 Imports statements are in the wrong order. from invenio.modules.encoder.metadata should be before from invenio.modules.encoder.utils
43:41: E126 continuation line over-indented for hanging indent
45:1: I101 Imported names are in the wrong order. Should be chose2, generate_timestamp, getval
45:1: F999 redefinition of unused 'chose2' from line 41
46:1: I101 Imported names are in the wrong order. Should be CFG_BIBENCODE_ASPECT_RATIO_MARC_FIELD, CFG_BIBENCODE_DAEMON_DIR_NEWJOBS, CFG_BIBENCODE_PBCORE_MARC_XSLT
46:1: I100 Imports statements are in the wrong order. from invenio.modules.encoder.config should be before from invenio.modules.encoder.utils
47:39: E126 continuation line over-indented for hanging indent
51:1: I100 Imports statements are in the wrong order. from invenio.ext.email should be before from invenio.modules.encoder.config
52:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.ext.email
55:1: I100 Imports statements are in the wrong order. import invenio.config should be before from invenio.utils.json
65:1: E302 expected 2 blank lines, found 1
65: D401 First line should be in imperative mood ('Send', not 'Sends')
65: D400 First line should end with a period (not 'g')
65: D205 1 blank line required between summary line and description (found 0)
76:13: E128 continuation line under-indented for visual indent
77:13: E128 continuation line under-indented for visual indent
78:13: E128 continuation line under-indented for visual indent
79:13: E128 continuation line under-indented for visual indent
80:13: E128 continuation line under-indented for visual indent
82:14: E128 continuation line under-indented for visual indent
90:1: E302 expected 2 blank lines, found 1
90: D401 First line should be in imperative mood ('Send', not 'Sends')
90: D205 1 blank line required between summary line and description (found 0)
108:13: E128 continuation line under-indented for visual indent
109:13: E128 continuation line under-indented for visual indent
118:13: E128 continuation line under-indented for visual indent
119:13: E128 continuation line under-indented for visual indent
121:14: E128 continuation line under-indented for visual indent
122:14: E128 continuation line under-indented for visual indent
123:14: E128 continuation line under-indented for visual indent
126:14: E128 continuation line under-indented for visual indent
127:14: E128 continuation line under-indented for visual indent
128:14: E128 continuation line under-indented for visual indent
136:1: E302 expected 2 blank lines, found 1
136: D401 First line should be in imperative mood ('Send', not 'Sends')
136: D205 1 blank line required between summary line and description (found 0)
152:13: E128 continuation line under-indented for visual indent
153:13: E126 continuation line over-indented for hanging indent
159:13: E128 continuation line under-indented for visual indent
160:13: E128 continuation line under-indented for visual indent
162:14: E128 continuation line under-indented for visual indent
163:14: E128 continuation line under-indented for visual indent
164:14: E128 continuation line under-indented for visual indent
167:14: E128 continuation line under-indented for visual indent
168:14: E128 continuation line under-indented for visual indent
169:14: E128 continuation line under-indented for visual indent
177:1: E302 expected 2 blank lines, found 1
177: D210 No whitespaces allowed surrounding docstring text
177: D401 First line should be in imperative mood ('Generate', not 'Generates')
177: D205 1 blank line required between summary line and description (found 0)
177: D208 Docstring is over-indented
188:1: E302 expected 2 blank lines, found 1
188: D210 No whitespaces allowed surrounding docstring text
188: D401 First line should be in imperative mood ('Store', not 'Stores')
188: D400 First line should end with a period (not 's')
188: D205 1 blank line required between summary line and description (found 0)
188: D208 Docstring is over-indented
197:1: E302 expected 2 blank lines, found 1
197: D401 First line should be in imperative mood ('Remove', not 'Removes')
197: D400 First line should end with a period (not 'r')
197: D205 1 blank line required between summary line and description (found 0)
221:25: E128 continuation line under-indented for visual indent
222:25: E128 continuation line under-indented for visual indent
223:25: E128 continuation line under-indented for visual indent
224:25: E128 continuation line under-indented for visual indent
238:1: E302 expected 2 blank lines, found 1
238: D210 No whitespaces allowed surrounding docstring text
238: D401 First line should be in imperative mood ('Create', not 'Creates')
238: D400 First line should end with a period (not 'n')
238: D205 1 blank line required between summary line and description (found 0)
239:29: E126 continuation line over-indented for hanging indent
255:1: E302 expected 2 blank lines, found 1
255: D210 No whitespaces allowed surrounding docstring text
255: D401 First line should be in imperative mood ('Create', not 'Creates')
255: D400 First line should end with a period (not 'a')
255: D205 1 blank line required between summary line and description (found 0)
273:1: E302 expected 2 blank lines, found 1
273: D210 No whitespaces allowed surrounding docstring text
273: D401 First line should be in imperative mood ('Create', not 'Creates')
273: D400 First line should end with a period (not 's')
273: D205 1 blank line required between summary line and description (found 0)
296:1: E302 expected 2 blank lines, found 1
296: D210 No whitespaces allowed surrounding docstring text
296: D401 First line should be in imperative mood ('Create', not 'Creates')
296: D400 First line should end with a period (not 'y')
296: D205 1 blank line required between summary line and description (found 0)
297:21: E126 continuation line over-indented for hanging indent
319:1: E302 expected 2 blank lines, found 1
319: D210 No whitespaces allowed surrounding docstring text
319: D401 First line should be in imperative mood ('Check', not 'Checks')
319: D400 First line should end with a period (not 'y')
319: D205 1 blank line required between summary line and description (found 0)
325: D210 No whitespaces allowed surrounding docstring text
325: D401 First line should be in imperative mood ('Sanitize', not 'Sanitizes')
325: D400 First line should end with a period (not 's')
325: D200 One-line docstring should fit on one line with quotes (found 2)
354:5: E129 visually indented line with same indent as next logical line
356:21: E128 continuation line under-indented for visual indent
372:1: E302 expected 2 blank lines, found 1
372: D210 No whitespaces allowed surrounding docstring text
372: D401 First line should be in imperative mood ('Processe', not 'Processes')
372: D400 First line should end with a period (not 'y')
382: D210 No whitespaces allowed surrounding docstring text
382: D401 First line should be in imperative mood ('Create', not 'Creates')
382: D400 First line should end with a period (not 'd')
382: D200 One-line docstring should fit on one line with quotes (found 2)
385:36: E225 missing whitespace around operator
399:5: E266 too many leading '#' for block comment
402:5: E266 too many leading '#' for block comment
405:5: E266 too many leading '#' for block comment
415:5: E266 too many leading '#' for block comment
430:21: E129 visually indented line with same indent as next logical line
433:21: E266 too many leading '#' for block comment
435:25: E266 too many leading '#' for block comment
436:47: F821 undefined name 'get_fieldvalues'
444:27: E128 continuation line under-indented for visual indent
447:13: E266 too many leading '#' for block comment
450:5: E266 too many leading '#' for block comment
457:5: E266 too many leading '#' for block comment
465:5: E266 too many leading '#' for block comment
468:5: E266 too many leading '#' for block comment
472:5: E266 too many leading '#' for block comment
480:13: E266 too many leading '#' for block comment
481:13: E266 too many leading '#' for block comment
482:13: E266 too many leading '#' for block comment
483:13: E266 too many leading '#' for block comment
485:27: E128 continuation line under-indented for visual indent
487:37: E126 continuation line over-indented for hanging indent
490:13: E266 too many leading '#' for block comment
491:13: E266 too many leading '#' for block comment
495:21: E126 continuation line over-indented for hanging indent
512:28: E128 continuation line under-indented for visual indent
514:9: E266 too many leading '#' for block comment
524:13: E266 too many leading '#' for block comment
532:13: E266 too many leading '#' for block comment
537:13: E266 too many leading '#' for block comment
540:13: E266 too many leading '#' for block comment
541:13: E266 too many leading '#' for block comment
543:50: E126 continuation line over-indented for hanging indent
549:13: E266 too many leading '#' for block comment
551:18: E126 continuation line over-indented for hanging indent
565:53: E261 at least two spaces before inline comment
571:13: E266 too many leading '#' for block comment
572:15: E271 multiple spaces after keyword
573:17: E266 too many leading '#' for block comment
588:47: E127 continuation line over-indented for visual indent
614:25: W503 line break before binary operator
615:25: E128 continuation line under-indented for visual indent
617:28: E128 continuation line under-indented for visual indent
618:28: E128 continuation line under-indented for visual indent
619:28: E126 continuation line over-indented for hanging indent
629:13: E266 too many leading '#' for block comment
631:17: E266 too many leading '#' for block comment
632:17: E266 too many leading '#' for block comment
635:21: E266 too many leading '#' for block comment
636:21: E266 too many leading '#' for block comment
639:21: E266 too many leading '#' for block comment
642:21: E266 too many leading '#' for block comment
646:21: E266 too many leading '#' for block comment
650:21: E266 too many leading '#' for block comment
651:21: E266 too many leading '#' for block comment
655:35: E128 continuation line under-indented for visual indent
658:37: E126 continuation line over-indented for hanging indent
663:13: E266 too many leading '#' for block comment
675:5: E266 too many leading '#' for block comment
679:5: E266 too many leading '#' for block comment
684:9: E266 too many leading '#' for block comment
697:44: E251 unexpected spaces around keyword / parameter equals
697:46: E251 unexpected spaces around keyword / parameter equals
698:50: E251 unexpected spaces around keyword / parameter equals
698:52: E251 unexpected spaces around keyword / parameter equals
699:49: E251 unexpected spaces around keyword / parameter equals
699:51: E251 unexpected spaces around keyword / parameter equals
733:5: E266 too many leading '#' for block comment
743:55: E721 do not compare types, use 'isinstance()'
743:69: E202 whitespace before ')'
753:32: E128 continuation line under-indented for visual indent
754:32: E128 continuation line under-indented for visual indent
755:32: E128 continuation line under-indented for visual indent
757:1: W391 blank line at end of file


23:1: I201 Missing newline before sections or imports.
25:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from six


58:1: I201 Missing newline before sections or imports.
61:1: I100 Imports statements are in the wrong order. from invenio.utils.pagination should be before from invenio_formatter


26:1: I201 Missing newline before sections or imports.


4: L102 copyright year is outdated, expected 2015 but got 2013
25:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, nottest, run_test_suite
25:1: I100 Imports statements are in the wrong order. from invenio.testsuite should be before from invenio.utils.autodiscovery
25:1: F401 'nottest' imported but unused


1: D100 Missing docstring in public module
1: L101 copyright is missing
2:1: I201 Missing newline before sections or imports.
3:1: I100 Imports statements are in the wrong order. from invenio_formatter.engine should be before from lxml
3:1: I201 Missing newline before sections or imports.
10:1: E302 expected 2 blank lines, found 1
10: D103 Missing docstring in public function
11:5: E266 too many leading '#' for block comment
12:51: E225 missing whitespace around operator
16:5: E266 too many leading '#' for block comment
17:5: E266 too many leading '#' for block comment
18:108: E231 missing whitespace after ','
18:126: E231 missing whitespace after ':'
25:1: E302 expected 2 blank lines, found 1
25: D103 Missing docstring in public function
31:59: E231 missing whitespace after ','
34:59: E231 missing whitespace after ','
35:66: E231 missing whitespace after ','
42:65: E231 missing whitespace after ','
43:72: E231 missing whitespace after ','
46:1: W391 blank line at end of file


@Mayank009 dfsfds


fixed


@Kovah I'll be back at home on Thursday. Will create a PR on Thursday "late" night.


vs


TeamCity pull requests :: netty [Build 9](https://garage.netty.io/teamcity/viewLog.html?buildId=253&buildTypeId=pulls_netty&guest=1) is now running


@vilchik-elena could it be removed ?


:+1:  Good job!


Awesome, thanks for the tip.

https://github.com/ivorpad/bloccit/commit/f586d61991e319fae50fbfa887bd4383376dcd1e


@lindamartin I've done this in c444e071c113e4f95bf33f87ed3019d4d149f67e


I think you should append "ago"
-->
`ngettext("A minute ago", "{minutes} minutes ago`, ...)


This is incorrect!


Append here also "ago"


Hi, I have a question since I had to struggle with a bug lately: what should exactly this change prevent? It omits some of the "0" values (when more than one "0"s in a row I believe) in a simple grid graph (since PHP "empty" function returns true when "0"), so in PDF report all the points on the graph move to the left, but the X axis remains the same. I attach an example image. For now I solved the problem by replacing "empty" function with negated "isset" function.
![xaxis](https://cloud.githubusercontent.com/assets/3197917/9224013/79af32b4-40ff-11e5-97c2-506e1607ac30.png)


@asdqwdqd


@vilchik-elena  perfect! copy.


It's one of those compiler stupidities ... gcc 4.6 couldn't generate the move ctor, but you are right, for symmetric reasons, one should have a move assignment as well ...


It would be good to add tests that verify that non-contributors can't access these endpoints.


@bblimke asd


@Mayank009 dfsfds


have to be the one variable "zookeeper" or "zk"?
it's failing to deploy spark with message below:
```
$ dcos package install spark
Note that the Apache Spark DCOS Service is beta and there may be bugs, incomplete features, incorrect documentation or other discrepancies.
We recommend a minimum of two nodes with at least 2 CPU and 2GB of RAM available for the Spark Service and running a Spark job.
Note: The Spark CLI may take up to 5min to download depending on your connection.
Continue installing? [yes/no] yes
\Error: missing required property 'zk'.

Please create a JSON file with the appropriate options, and pass the /path/to/file as an --options argument.

```


@sadasd


I'm not sure, but maybe it should be `<= 6` because you can have the same weekday name as your current day.
Example:
Timestamp for Tuesday 4:00 PM
A week later at Tuesday 3:00 PM
d.days is 6, because the timespan is 6*24 hours + 23 hours


for future reference doing `tuple(["Nearest"])` can be more easily written as `("Nearest",)`


Compiled files may include dependencies of from other packages, which could lead to duplication.


So theres only one possibility: `1 week ago`
Then I would just return `A week ago` or raise the condition limit, maybe to 3 weeks: `d.days <= 21`


So git push -f very dangerous. do not using it as well.


Uh... you know that is hopefully how I hope to answer every question, right? :)


Hello,
You must take care of XMLNS when you search a node !
So I have added a xmlns declaration of the searched name in the function childNamed parameter !

In intensive functions, I test
debug.enabled
to avoid string concatenation for nothing ...


@jonathanendersby  The Show images don't work here.

![naamloos](https://cloud.githubusercontent.com/assets/7928052/9224126/5b505ce8-4100-11e5-82c6-49f717c8622b.png)
![naamlooss](https://cloud.githubusercontent.com/assets/7928052/9224125/5b4f254e-4100-11e5-9413-35da747c3746.png)


Nvm to accept only a `datetime.timedelta`, just have seen that you use the absolute time value^^


TeamCity Subsonic :: Debug [Build 42](http://109.103.226.38:8512/viewLog.html?buildId=34994&buildTypeId=Subsonic_Debug) is now running


lgtm


I fixed the documentation in https://github.com/rust-lang/rust/pull/27693. Thanks for noti(ci)ng!


TeamCity Subsonic :: Debug [Build 42](http://109.103.226.38:8512/viewLog.html?buildId=34994&buildTypeId=Subsonic_Debug) outcome was **SUCCESS**
Summary: Running Build time: 00:04:25


delete


So far there wasn't really a need for us to touch pip at all (aside from installing pygame for me)... so I don't really know. This way has worked fine for us so far... knock on wood that that agar.io stop changing their protocol on a daily basis. (plus Windfisch isn't really a fan of pip)


Is this needed? I see a bunch of `is self.err is None: self.setup_err()`


Please change state names & delete the fields which are commented.


Does the markdown function accept a dict (which I believe you mentioned is what this check is guarding against)?


@Mayank009 dfsfds


not return `strftime` from the reference_timestamp?


Also here using the reference_timestamp?


True but I am wanting to set max freq using MSM_Limiter. This fixes that not sticking properly.


Does this comment make any sense?


They are supported https://github.com/Microsoft/TypeScript/pull/3397

Now it's possible that the editor your using doesn't support them yet, so it may be something we'll have to work around.


unused module glib


No explanation for that ;)


Hello,
For event:  the specification says that you MUST send events very <2000 ms, even the list is empty !
Intel Upnp validation tools, wait for an event, even the list is empty.

For XMLNS;  upnp clients can use prefixes of their choice, you can not wait explicitly dc:title upnp:date, there are no standard for xml prefix.  We must pass the xmlns URI for each searched tag.

OK for soap error code ... good idea.

Thanks for the help !
Regards ...


> Hmm... looking at some older code, maybe `htab_t` (from `hashtab.h`) is the only viable alternative.

Yet another hashtable ;-) Seems to be working with this, but would be great if you could do a quick review: https://github.com/jpf91/GDC/commit/83983bb7b980339bc9b9d3eaf419f2d57797b060
I think there's no way to easily review merge commits on github. `git show 83983bb` produces more useful output.

BTW: Which code conventions are we using right now? Whitespace after function name before parenthesis? Whitespace after parenthesis for casts?


okay it's a bit more complicated, maybe using hours is better instead.


@Mayank009 gandduu


TeamCity pull requests :: netty [Build 9](https://garage.netty.io/teamcity/viewLog.html?buildId=253&buildTypeId=pulls_netty&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1 (1 new), passed: 4249, ignored: 20 Build time: 00:20:28
### Failed tests
```
io.netty.osgitests.OsgiBundleTest.testResolvedBundles: <no details avaliable>

```


22 second load time here for LLCC, we'll have to find another way, or leave it as it is.


@sahilsarpal15 http://demo.apps.horntell.com/github/response/hooks


Updated to cache all movie info on app start up and only reload if the app data is destroyed


91977808_LBNL_NewVRFModel (rongpengzhang) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (753 of 754 tests passed)

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


Yes... Actually, the value of `pool.ha_cluster_stack` does not really matter when HA is not enabled. Instead of this upgrade rule, I'll say that to the API doc string (and will leave the default as `""`).


this will speedup boot process


**test comment**


Seem Intel don’t see the same spec as i do from upnpforum.
Moderated events for systemUpdateId should be moderated at a 2 second rate, meaning it should not occur more than once every 2 seconds.
Maybe i’m wrong, but it’s what i understand from the spec.

> Le 12 août 2015 à 14:51, Olivier Oeuillot <notifications@github.com> a écrit :
>
> Hello,
> For event: the specification says that you MUST send events very <2000 ms, even the list is empty !
> Intel Upnp validation tools, wait for an event, even the list is empty.
>
> For XMLNS; upnp clients can use prefixes of their choice, you can not wait explicitly dc:title upnp:date, there are no standard for xml prefix. We must pass the xmlns URI for each searched tag.
>
> OK for soap error code ... good idea.
>
> Thanks for the help !
> Regards ...
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663314>.
>


...
hello world this is a test comment.
...


You need to add this function:

        /**
        Return the column value as an Int64
        :returns:  An Optional Int64 corresponding to the apprioriate column value. Will be nil if: the column name does not exist, the value cannot be cast as a Int64, or the value is NULL
        */
        public func asInt64() -> Int64?
        {
            return value as? Int64
        }


Use noun from class and verb for methods


Since this change, ndiff can be called when it is not needed. And because of a problem in ndiff in CMFDiffTool, this can lead to a UnicodeDecodeError. See the discussion in https://github.com/plone/Products.CMFPlone/issues/820

I have restructured this some more in 3fcb68efe5c23850e9828952dd5751c7325d203d. Seems fine now.


:smile: I hope so too. Keep up the good work.


Is `('GET',)` default value?


add


yes


No.  This is an internal function. To get the locks you would call the Locks function on the client:

pkg/client/client.go
...
func (c *Client) Locks(namespace string) LockInterface {
        return newLocks(c, namespace)
}


Why :open_mouth: ? Because now, if you specified another file extension in your `dest` front-matter, at the end, it write only html... Maybe we can put that line before the `if (pageMatter.data.dest)` condition ?


DB 컬럼 추가는 같이 의논해 볼 여지가 있어 보임.


See
http://upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf <http://upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf>

2.5.20. SystemUpdateID
This required variable changes whenever anything in the Content Directory changes. A change could be a new or removed object, or a change in the metadata of an object. This variable is evented and the event is moderated at a maximum rate of 0.5 Hz (once every 2 seconds). The actual value of SystemUpdateID is unspecified. Clients should only check for equality with previous values of SystemUpdateID. Note that the (optional) ContainerUpdateIDs variable provides more information about the scope of the change, since it takes advantage of the ContainerUpdateID values maintained for each container.

> Le 12 août 2015 à 14:51, Olivier Oeuillot <notifications@github.com> a écrit :
>
> Hello,
> For event: the specification says that you MUST send events very <2000 ms, even the list is empty !
> Intel Upnp validation tools, wait for an event, even the list is empty.
>
> For XMLNS; upnp clients can use prefixes of their choice, you can not wait explicitly dc:title upnp:date, there are no standard for xml prefix. We must pass the xmlns URI for each searched tag.
>
> OK for soap error code ... good idea.
>
> Thanks for the help !
> Regards ...
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663314>.
>


                                                                                Sent from my BlackBerry 10 smartphone on the Bell network.                                                                                From: NetkinsSent: Wednesday, August 12, 2015 08:16To: netty/nettyReply To: netty/nettySubject: Re: [netty] Allow to create SslContext from existing PrivateKey / X509Certificate (ad1909e)TeamCity pull requests :: netty Build 8 outcome was FAILURE
Summary: Tests passed: 3291, ignored: 6; compilation error: Compiler (new) Build time: 00:02:57

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


Our names don't follow qemu style at the moment [iirc?]. But I think we should keep everything as-is now and just make sure that new functions hint what they are doing and where they belong (especially GL functions).
We can still refactor at a later point.
The function names do make sense at least. The file names on the other hand are really confusing. [Partially named after xbox components (nv2a, mcpx, ...), partly after host counterparts (nv2a_shaders, nv2a_vsh, ...)].


True, I use it only in the `_process` method


間違いです。逆でした！


Ah, thanks! It sneaked in on my replacement laptop, which didn't have an identical global git ignore.


逆でした！


well, pake inspect devpanel sih kalo mau ngetes ini itu,
(cara: undock devpanel -> ctrl+shift+j di dev panel -> muncul inspection window -> boleh dock lagi devpanelnya)
'w')b


すいません。関係なかったです。


I meant that these two lines (133,4) should be removed. The border width should be included even if it uses a blank color.


ありがとうございます、追加します！


                                                                                In a split tunnel, the client can act as a relay for an external attacker to access a secured network. In a split tunnel, the private network must rely on the security of the client firewall which, if compromised, is nil.  In many cases the network that the vpn attaches to also provides dns filtering, proxy, and firewalling which is more secure than what is on the client. Marc                                                                                Sent from my BlackBerry Passport                                                                                From: Nikos MavrogiannopoulosSent: Wednesday, August 12, 2015 1:05 AMTo: openwrt/packagesReply To: openwrt/packagesCc: waitfor1tSubject: Re: [packages] openconnect: corrected port descriptions in README (0313444)I don't understand what you mean that split tunnels are a security risk. They are not. However, I'd be glad to additionally add text for the setup that you propose. Please submit a pull request for that.

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


The one I'm pushing for in my changes are:
```
MACRO_ACCESSOR (obj);  // space between macro and parenthesis.
function_call(obj);    // no space between macro and parenthesis.
((Cast *) obj)->foo;   // space between closing cast parenthesis and object
```
The only change has been to function calls, where there was a mix between:
```
some_call (foo)->bar()->baz (42);
```
Which was just bad...
```


@vilchik-elena could this method be removed and fully replaced with the one line 87 ?


Is this really readable formatting? It is not for me but maybe I'm the only one.


Hello
I have read this spec, but nothing about an empty list !?
We can disable it  ... (I send empty list for intel upnp validation kit :-)

Have you some clients which really use systemUpdateID ?   (I don't have any
client !)

For black-boxes in  the code: no problem I can comment the sections you
want ...

IDEA: For the project, we can make a (new ?) organisation and I can
transfer upnpserver to it ?

Regards,
Olivier

2015-08-12 15:00 GMT+02:00 s-leger <notifications@github.com>:

> See
> http://upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf <
> http://upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf>
>
> 2.5.20. SystemUpdateID
> This required variable changes whenever anything in the Content Directory
> changes. A change could be a new or removed object, or a change in the
> metadata of an object. This variable is evented and the event is moderated
> at a maximum rate of 0.5 Hz (once every 2 seconds). The actual value of
> SystemUpdateID is unspecified. Clients should only check for equality with
> previous values of SystemUpdateID. Note that the (optional)
> ContainerUpdateIDs variable provides more information about the scope of
> the change, since it takes advantage of the ContainerUpdateID values
> maintained for each container.
>
>
>
>
> > Le 12 août 2015 à 14:51, Olivier Oeuillot <notifications@github.com> a
> écrit :
> >
> > Hello,
> > For event: the specification says that you MUST send events very <2000
> ms, even the list is empty !
> > Intel Upnp validation tools, wait for an event, even the list is empty.
> >
> > For XMLNS; upnp clients can use prefixes of their choice, you can not
> wait explicitly dc:title upnp:date, there are no standard for xml prefix.
> We must pass the xmlns URI for each searched tag.
> >
> > OK for soap error code ... good idea.
> >
> > Thanks for the help !
> > Regards ...
> >
> > —
> > Reply to this email directly or view it on GitHub <
> https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663314
> >.
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663506>
> .
>


I doubt that it is good to install to the /skel folder. It will not install for an already installed user!
Any advice from the more experienced on how to do this properly, please!?


Ok for debug.enabled, won’t remove them again :)

> Le 12 août 2015 à 14:43, Olivier Oeuillot <notifications@github.com> a écrit :
>
> Hello,
> You must take care of XMLNS when you search a node !
> So I have added a xmlns declaration of the searched name in the function childNamed parameter !
>
> In intensive functions, I test
> debug.enabled
> to avoid string concatenation for nothing ...
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/s-leger/upnpserver/commit/ba81a0022bd03a8c74f0c041230af826d2f14665#commitcomment-12663142>.
>


Check spelling


Great advice.

Looks so much better now.


ne ma kefi


Hi 在项目设置里面把我拉到Collaborators列表里面～


There's an extra set of parens here, right?


ありがとうございます、気をつけます　m  _ _ m


``*slot != NULL`` should be impossible here I think.  Did you get ICE's during testing?


Avoid qualifying class selectors with an element.


Docstring please


In the other ContourNext documentation I did see 20/600 thresholds as examples, but the documentation states "They are not intended as references for true defaults ".


It does display IN the console.

On Wednesday, August 12, 2015, RandomAltThing <notifications@github.com>
wrote:

> Instead or using
>
> for(Player p : getOnlinePlayers){
> p.sendMessage(message);
> }
>
> , isint there a way to broadcast a chat packet or something so it would
> display to console aswell? It would also make it visible to RCON
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/RedstoneLamp/RedstoneLamp/commit/8f36f3978fcd536e468fd4c6d19940eade4558ec#commitcomment-12660757>
> .
>

--


I think the config files should go to /etc/bspwm and /etc/sxhkd, no?


@vilchik-elena why JavaScriptTree and not Tree ?


> Le 12 août 2015 à 15:07, Olivier Oeuillot <notifications@github.com> a écrit :
>
> Hello
> I have read this spec, but nothing about an empty list !?
> We can disable it ... (I send empty list for intel upnp validation kit :-)
>
> Have you some clients which really use systemUpdateID ? (I don't have any
> client !)

Maybe one day someone will provide a good client implementation ;)
I think changes in directories are not expected too often.

> For black-boxes in the code: no problem I can comment the sections you
> want …

In a perfect world, i expect all of them with comments.
But until this world becomes reality, the node part seem to be the mutch darker area to me.

> IDEA: For the project, we can make a (new ?) organisation and I can
> transfer upnpserver to it ?

Keep this in your repo, so folks forks still valid.

P.S as you can reed from my english, i do spoke frensh.

> Regards,
> Olivier
>
> 2015-08-12 15:00 GMT+02:00 s-leger <notifications@github.com>:
>
> > See
> > http://upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf <
> > http://upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf>
> >
> > 2.5.20. SystemUpdateID
> > This required variable changes whenever anything in the Content Directory
> > changes. A change could be a new or removed object, or a change in the
> > metadata of an object. This variable is evented and the event is moderated
> > at a maximum rate of 0.5 Hz (once every 2 seconds). The actual value of
> > SystemUpdateID is unspecified. Clients should only check for equality with
> > previous values of SystemUpdateID. Note that the (optional)
> > ContainerUpdateIDs variable provides more information about the scope of
> > the change, since it takes advantage of the ContainerUpdateID values
> > maintained for each container.
> >
> >
> >
> >
> > > Le 12 août 2015 à 14:51, Olivier Oeuillot <notifications@github.com> a
> > écrit :
> > >
> > > Hello,
> > > For event: the specification says that you MUST send events very <2000
> > ms, even the list is empty !
> > > Intel Upnp validation tools, wait for an event, even the list is empty.
> > >
> > > For XMLNS; upnp clients can use prefixes of their choice, you can not
> > wait explicitly dc:title upnp:date, there are no standard for xml prefix.
> > We must pass the xmlns URI for each searched tag.
> > >
> > > OK for soap error code ... good idea.
> > >
> > > Thanks for the help !
> > > Regards ...
> > >
> > > —
> > > Reply to this email directly or view it on GitHub <
> > https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663314
> > >.
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663506>
> > .
> >
> —
> Reply to this email directly or view it on GitHub <https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663636>.
>


@emilywistia I think thi is really the only place. Plus, the docs is the concerning place. Everything else can be brushed off as "marketing speak" -- the docs _should_ be factual.


Hm, I definitely proofread all of this and totally missed that, twice. Made sense when I read it in my head. Fixing.


@lindada i don't think so, these are 2 different tokens (*Token* is used for comments, which cannot be presented as InternalSyntaxToken). I've saved offsets https://github.com/SonarCommunity/sonar-javascript/blob/a41ae1b466b86766971f673ea6025c924e92fb44/javascript-squid/src/main/java/org/sonar/javascript/model/internal/lexical/InternalSyntaxToken.java#L53, to not compute SourceFileOffsets, but now i see that still for trivias i don't have *startIndex*


@vangheem I'll have a proof-of-concept working, but need some time to clean it up before being able to push a working branch out of it.

In short, those ++layout++something in display menu will be used to generate merged site layout in fly with ++layout++something content layout merged into main template. Then editor will show all data-panels defined within data-panel="content" as editable areas (and there should also be data-panel="content" in there) and as long as all available layouts in display menu define slots with same name, one can change layout in fly by just selecting from the menu.

Some overhead added from that additional merge.


Yes. It's not properly documented, but with `NO_INSERT`:

```c++
entry = htab->entries[index];
if (entry == HTAB_EMPTY_ENTRY)
  goto empty_entry;

[...]

empty_entry:
  if (insert == NO_INSERT)
    return NULL;
```


An example comment.


@lindamartin i don't know:) how to choose?


Great, much better.


Indirection overflow. How about many small tests, for each case? To be honest, I can't grok that code, and if there's a failure, it'll take ages to understand 1/ why it's failing 2/ is it supposed to be failing 3/ how to fix it (the failure, or the test)


این پراکسی گریدل هست
این لازم نیست
حذفش کن که سریعتر سینک کنه
@pouyabs5


good catch


Thanks @neoatomic - Not sure what's going on. How do the generated image urls compare to the ones you get when you visit http://www.imdb.com/search/title?at=0&sort=moviemeter&title_type=tv_series&year=2014,2016 ?


@Myoldmopar @jasondegraw I checked results and found a single test file did not pass with some machine configurations: _5ZoneEvapCooled. The previous commit showed tests passed 100%. The changes were not related to this file. Could let me know how to proceed?


Other areas of the code checks packet->code to make sure it's in the known range of packet codes.  Are you certain the packet code will be in the range enumerated by fr_packet_codes once it gets here?


Actually, I'd iterate over the survey's question and then use one of these:

    getattr(form, 'question_{}'.format(q.id)).data

or

    data = form.data
    # ...
    data['question_{}'.format(q.id)]


@rohitpaulk ruby is wow!


Wow! This script is amazing!
Would be nice if you filtered extended_price though.


Let's be consistent and use either `lists:keyfind` or `proplists:get_value` here and not both.


@rohitpaulk man ruby is wow!


:+1: for commit description


Looks good, I will give it a try


You can actually just have `emoji.image_filename == "#{emoji.name}.png"` as the body; no `is_image` at all.


@lgu1234 To get a clean test report, you will need to merge develop into your branch.


[Sorry, for the french section]
Bon ça va simplifier le travail de parler un peu francais :-)
Je suis en vacances, donc je merge lentement, j’espère mettre le master à
niveau rapidement pour que l'on commite tous les 2 plus facilement !
J'ai presque tout mergé, il me reste server.js
Donc exceptionnellement (si si) je vais commiter le master sans le tester
... c'est juste pour cette phase de transition !  (je n'ai pas non plus mes
clients upnp habituels sous la main) et après je travaille sur une branche !

Sinon , il faut que l'on s'organise un moment pour discuter des axes des
envis de chacun et donc des travaux à venir (et il en reste :-)

Bonne journée...
Olivier

2015-08-12 15:15 GMT+02:00 s-leger <notifications@github.com>:

>
> > Le 12 août 2015 à 15:07, Olivier Oeuillot <notifications@github.com> a
> écrit :
> >
> > Hello
> > I have read this spec, but nothing about an empty list !?
> > We can disable it ... (I send empty list for intel upnp validation kit
> :-)
> >
> > Have you some clients which really use systemUpdateID ? (I don't have any
> > client !)
>
> Maybe one day someone will provide a good client implementation ;)
> I think changes in directories are not expected too often.
>
> > For black-boxes in the code: no problem I can comment the sections you
> > want …
>
> In a perfect world, i expect all of them with comments.
> But until this world becomes reality, the node part seem to be the mutch
> darker area to me.
>
> > IDEA: For the project, we can make a (new ?) organisation and I can
> > transfer upnpserver to it ?
>
> Keep this in your repo, so folks forks still valid.
>
> P.S as you can reed from my english, i do spoke frensh.
>
>
>
> > Regards,
> > Olivier
> >
> > 2015-08-12 15:00 GMT+02:00 s-leger <notifications@github.com>:
> >
> > > See
> > > http://upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf <
> > > http://upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf>
> > >
> > > 2.5.20. SystemUpdateID
> > > This required variable changes whenever anything in the Content
> Directory
> > > changes. A change could be a new or removed object, or a change in the
> > > metadata of an object. This variable is evented and the event is
> moderated
> > > at a maximum rate of 0.5 Hz (once every 2 seconds). The actual value of
> > > SystemUpdateID is unspecified. Clients should only check for equality
> with
> > > previous values of SystemUpdateID. Note that the (optional)
> > > ContainerUpdateIDs variable provides more information about the scope
> of
> > > the change, since it takes advantage of the ContainerUpdateID values
> > > maintained for each container.
> > >
> > >
> > >
> > >
> > > > Le 12 août 2015 à 14:51, Olivier Oeuillot <notifications@github.com>
> a
> > > écrit :
> > > >
> > > > Hello,
> > > > For event: the specification says that you MUST send events very
> <2000
> > > ms, even the list is empty !
> > > > Intel Upnp validation tools, wait for an event, even the list is
> empty.
> > > >
> > > > For XMLNS; upnp clients can use prefixes of their choice, you can not
> > > wait explicitly dc:title upnp:date, there are no standard for xml
> prefix.
> > > We must pass the xmlns URI for each searched tag.
> > > >
> > > > OK for soap error code ... good idea.
> > > >
> > > > Thanks for the help !
> > > > Regards ...
> > > >
> > > > —
> > > > Reply to this email directly or view it on GitHub <
> > >
> https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663314
> > > >.
> > > >
> > >
> > > —
> > > Reply to this email directly or view it on GitHub
> > > <
> https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663506
> >
> > > .
> > >
> > —
> > Reply to this email directly or view it on GitHub <
> https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663636
> >.
>
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663813>
> .
>


Don’t know anything about XMLNS before learning upnp. So it’s still pretty unclear to me.

> Le 12 août 2015 à 14:43, Olivier Oeuillot <notifications@github.com> a écrit :
>
> Hello,
> You must take care of XMLNS when you search a node !
> So I have added a xmlns declaration of the searched name in the function childNamed parameter !
>
> In intensive functions, I test
> debug.enabled
> to avoid string concatenation for nothing ...
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/s-leger/upnpserver/commit/ba81a0022bd03a8c74f0c041230af826d2f14665#commitcomment-12663142>.
>


Same test as earlier (Xtrend 8k with internal HDD and 2-part USB stick): automaounts were as before (so int HDD = HDD, FAT32part1 =  USB, EXT4part2 = SDA6).
Only one test, but seems OK.


To be more precise about my "Indirection overflow" sentence: the test itself seems to mix several use cases/data, and it's using the `check_filters` helper which is itself looping on filters, accepting a `**kw` that we don't know much about (it seems it's only `filename` in the code written here), and returns a tuple... which is compared to the provided filters.


I like this idea but we need to be clear about this in the doc and probably provide a simple configuration for HAProxy.


Ok so i can switch back the ids from Extra utilities i see.


@rohitpaulk not important but idk why this email test fails. Take a look when you can. It's strange.


Or /usr/share You just have to ckeck where bspwm and sxhkd are looking for the config - or maybe you can call the config path as an option with the apps...?


It feels like this change doesn't belong on that commit. Any reason why this has been removed ?


I don't like this filter any more...


Almost there ...

On Tue, Aug 11, 2015 at 3:32 PM Josiah Wolf Oberholtzer <
notifications@github.com> wrote:

> Hmm!
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Abjad/ide/commit/39bee7e7a4cd774ecfdd9e535e182e0ee3952336#commitcomment-12648901>
> .
>


This breaks real wiimotes on linux :(


With disabled MSM Simple Thermal I can't stick max freq.. How do You do that? :confused:


For the first Show True Detective :

On IMDB :
http://ia.media-imdb.com/images/M/MV5BMTUzNTMwODI1OV5BMl5BanBnXkFtZTgwMDIzMTQ0NTE@._V1._SX54_CR0,0,54,74_.jpg

Inside Sickrage. :
http://ia.media-imdb.com/images/M/MV5BMTUzNTMwODI1OV5BMl5BanBnXkFtZTgwMDIzMTQ0NTE@._V1._SX108_CR0,0,108,148_.jpg


should this be "A read-write property is defined like using a single getter"


@rohitpaulk have a look.


Nice. Just some tweaks.

Do this check as part of `get_expected()` so you don't have to reopen the file.

Like we did for regular skip, it's good to provide a reason why the file is being skipped when running with valgrind. You probably can reuse the skip return value there, just adding to the message this was caused by valgrind.

You'll see that you'll have less work if you put the `TEST-SKIP-VALGRIND` earlier in the tests files (before the expected output), so prefer that.


Triple quotes and ending `.` please


파일명 잘못됨
dhcpd.conf 임


if this was added a preinstall step, and it's only used by cache.sh, do we need it as a package dependency here?


wha? was this a bug before?


Akka.NET IO is currently a straight port from Akka JVM, which uses selectors. It will require design changes to switch to async IO. I have done some initial work on this and we might include in some time in the future.


But for example in `d-codegen.cc` we have this:
```
int
pop_binding_label(void **slot, void *arg)
{
}

tree
build_local_temp (tree type)
{
}
```
I guess the new style is 'no space'?


Roger that. I'll update.


Yes, that doesn't really fit in with this commit. However it was removed as it is an unused private method. So it didn't make much sense to be included. I can revert this if you would prefer?


Good catch!


I want to postpone this change since the old Yesod version that does not have withUrlRenderer is still the one in Debian Stable and I want to be able to package a backport of gitit2 for the current Debian stable.


@vilchik-elena I would say based from what the Interface provide and what is used in this case. If methods from JavaScriptTree is needed by consumer of this method "CLASS_ELEMENT" so I would say JavaScriptTree should be used but if it is not so the view from Tree interface is enough and should be used IMHO.


I thought the error handler was the last point where errors were supposed to be intercepted. Why do we need to call `next(err)` again?


+2 for this patch.


Nah a bit of noise in the history is fine, I just wanted to make sure it wasn't an unintended mistake. Thanks for the PR !


Creo que estos aporte debería ir por PR, es lo mas recomendable


Minor: I'd prefer to see supertypes w/o braces


[Again sorry for the french section]

A priori, je teste sur plusieurs clients : un client « bullet proof » qui prendrait n’importe quoi dans les dents sans broncher.
VLC qui a l’air de fonctionner.
Lecteur windows media qui pour le moment ne voit même pas le serveur (qui tourne sur mon mac)…
Je bricole sur un mac (..), mais j’ai une ubuntu virtuelle sous la main.

J’ai ouvert une branche pour créer un niveau d’abstraction « device » et séparer l’API du serveur upnp, dans l’optique d’implémenter un point de contrôle et un client qui va streamer sur des airplay.

Bonnes vacances !

> Le 12 août 2015 à 15:21, Olivier Oeuillot <notifications@github.com> a écrit :
>
> [Sorry, for the french section]
> Bon ça va simplifier le travail de parler un peu francais :-)
> Je suis en vacances, donc je merge lentement, j’espère mettre le master à
> niveau rapidement pour que l'on commite tous les 2 plus facilement !
> J'ai presque tout mergé, il me reste server.js
> Donc exceptionnellement (si si) je vais commiter le master sans le tester
> ... c'est juste pour cette phase de transition ! (je n'ai pas non plus mes
> clients upnp habituels sous la main) et après je travaille sur une branche !
>
> Sinon , il faut que l'on s'organise un moment pour discuter des axes des
> envis de chacun et donc des travaux à venir (et il en reste :-)
>
> Bonne journée...
> Olivier
>
>
>
>
>
>
> 2015-08-12 15:15 GMT+02:00 s-leger <notifications@github.com>:
>
> >
> > > Le 12 août 2015 à 15:07, Olivier Oeuillot <notifications@github.com> a
> > écrit :
> > >
> > > Hello
> > > I have read this spec, but nothing about an empty list !?
> > > We can disable it ... (I send empty list for intel upnp validation kit
> > :-)
> > >
> > > Have you some clients which really use systemUpdateID ? (I don't have any
> > > client !)
> >
> > Maybe one day someone will provide a good client implementation ;)
> > I think changes in directories are not expected too often.
> >
> > > For black-boxes in the code: no problem I can comment the sections you
> > > want …
> >
> > In a perfect world, i expect all of them with comments.
> > But until this world becomes reality, the node part seem to be the mutch
> > darker area to me.
> >
> > > IDEA: For the project, we can make a (new ?) organisation and I can
> > > transfer upnpserver to it ?
> >
> > Keep this in your repo, so folks forks still valid.
> >
> > P.S as you can reed from my english, i do spoke frensh.
> >
> >
> >
> > > Regards,
> > > Olivier
> > >
> > > 2015-08-12 15:00 GMT+02:00 s-leger <notifications@github.com>:
> > >
> > > > See
> > > > http://upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf <
> > > > http://upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf>
> > > >
> > > > 2.5.20. SystemUpdateID
> > > > This required variable changes whenever anything in the Content
> > Directory
> > > > changes. A change could be a new or removed object, or a change in the
> > > > metadata of an object. This variable is evented and the event is
> > moderated
> > > > at a maximum rate of 0.5 Hz (once every 2 seconds). The actual value of
> > > > SystemUpdateID is unspecified. Clients should only check for equality
> > with
> > > > previous values of SystemUpdateID. Note that the (optional)
> > > > ContainerUpdateIDs variable provides more information about the scope
> > of
> > > > the change, since it takes advantage of the ContainerUpdateID values
> > > > maintained for each container.
> > > >
> > > >
> > > >
> > > >
> > > > > Le 12 août 2015 à 14:51, Olivier Oeuillot <notifications@github.com>
> > a
> > > > écrit :
> > > > >
> > > > > Hello,
> > > > > For event: the specification says that you MUST send events very
> > <2000
> > > > ms, even the list is empty !
> > > > > Intel Upnp validation tools, wait for an event, even the list is
> > empty.
> > > > >
> > > > > For XMLNS; upnp clients can use prefixes of their choice, you can not
> > > > wait explicitly dc:title upnp:date, there are no standard for xml
> > prefix.
> > > > We must pass the xmlns URI for each searched tag.
> > > > >
> > > > > OK for soap error code ... good idea.
> > > > >
> > > > > Thanks for the help !
> > > > > Regards ...
> > > > >
> > > > > —
> > > > > Reply to this email directly or view it on GitHub <
> > > >
> > https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663314
> > > > >.
> > > > >
> > > >
> > > > —
> > > > Reply to this email directly or view it on GitHub
> > > > <
> > https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663506
> > >
> > > > .
> > > >
> > > —
> > > Reply to this email directly or view it on GitHub <
> > https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663636
> > >.
> >
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663813>
> > .
> >
> —
> Reply to this email directly or view it on GitHub <https://github.com/s-leger/upnpserver/commit/903f6ceda359b24996f6addf82260891585cb515#commitcomment-12663938>.
>


ok


Weird.... both links work for me. @miigotu @WebSpider - Can you check if those links work for you? @neoatomic your IP isn't on some list is it?

@neoatomic I'm guessing you can load both those images in a regular web browser? Or does the latter URL just never work? They appear to be rejecting your referrer. What's hostname are you serving SR off?

BTW, the difference between the two urls is simply me requesting a bigger version of the same image.  See line 25 of imdbPopular.py.


thanks :)


:+1: no problem!


Yes.  Because of manpower, I'm only updating them as and when I write new code. :-)


+1 for this commit.

Consider adding a FBP test that triggers this error. Shift "too much" and verify there was an error packet sent.


On 08/11/2015 03:28 PM, kpj wrote:
> Should |ltx:XMath:| and |ltx:XMArg:| also be colored, or only the
> corresponding numbers (|0/1|, |6/6|)?

Last checkin looks reasonable to me.
Are we all happy?
Should we go to PR?


Tested it out yesterday. Worked as expected even through the proxy. Thanks! How did you do it?


MUCH better


This actually does not fix but break the namespace. You have to pass a single namespace here. The model is not found anymore!


здесь нужно использовать
```ruby
image_tag
```
смотри rails api guide


Hi @htch, I merged it to thank you at https://github.com/what-studio/profiling/commit/d4e71442208e1c87dcd499f8ba5c574d5a04f668.


I've added a comment to explain this


This commit breaks tests


@vilchik-elena Wow huge work! LGTM, nice to see all this cleared out!


Do we need a fallback when the position isn't in the file? In the previous code, it was returning the last line.


sublime text 不是一个ide  不建议写 本书的代码都是在sublime上编辑运行的。

书上的代码都是openresty 实践，不是纯粹的lua，不可能在sublime上运行。


I am using https://github.com/smrq/tsify in a gulp pipeline which I believe is using Typescript 1.5.4 and that's what is throwing the error.  Perhaps I have some kind of configuration error and its not really using 1.5.4, or do I need to use Typescript master?


gcc should have done this for us.


See https://trello.com/c/ltEhCsjV/37-filter-non-membership-zoura-subscriptions-to-avoid-clash-with-subscribe-theguardian-com


Please give the promise a somewhat more descriptive name - it could be a promise for anything!


This one was probably always unnecessary since `case '*-cvsserver' '*-receive-pack'` etc should work, too.


the naming derives from https://github.com/elastic/elasticsearch/blob/master/docs/reference/cluster/nodes-info.asciidoc#operating-system-information


why there is no
obj-$(CONFIG_CPU_FREQ_GOV_INTERACTIVE)	+= cpufreq_intelliactive.o
?


@vilchik-elena what's the status of this commented-out code ?


Thanks. I've never seen that before. You can keep those method names if you like but I think it's confusing and deceiving because it makes you think it's part of the visitor pattern when indeed it is not.


BTW, may I suggest that you do not use daemon mode?

As I already mentioned, I also work on multithreaded code and I first used also daemon mode. Somehow I noticed later that there were a lot of threads (more than expected) and the fact that it didn't work as expected was somehow hidden by using daemon mode.
I switched then to non-daemon mode (which means you have to cleanly tear down the threads you create) and had to clean up the code until it was really clean and well-behaved. So non-daemon was good for code cleanliness and even correctness. :)


Don't you need that method for #10?


@jonathanendersby At first i coudnt. Always got the "Referral Denied"  error as i posted in the above screen-shot. But been testing and now got the image for that show working, but not the rest.
Try'd another browser, just to make sure it isn't the add-blocker, but also there no images.

![1](https://cloud.githubusercontent.com/assets/7928052/9225136/c36ec6a0-4107-11e5-8874-55d242ab7a92.png)


Exceptions in Java are types. In particular, they are classes (which is is a kind of type, the others being enum and interface). So, you could have a set of types that represent exceptions, which would be easier to work with than statements, I would think, because there can be more than one statement that throws the same kind of exception.


why do you need that? if you don't want the title field, `del` it in the `config_form` method


Ops, demonisering skjer med `-D` eller `--demonize`


Why was the ITypeBinding visit method removed? I think it's important.


lua的数字类型是double类型 应该是64位 不是32位


@mccalluc is `current_user` a method required by CanCan?


instaed of skipping you could simply do

```
if not form.anonymous.data:
    survey.require_user = True
```

the current code is also fine though


:clap:


whoops.. disregard. Reading through next commits.


I see, can you merge getting rid of the latest commit?


Why do you think using a global variable is a simplification?


i'd still go for a set instead of a tuple here ;)


I'm happy, happy Wednesday to everyone!


By the way, I don't have instructions for you. As far as I know, noone has tried to do what you are doing here before. I am just here for guidance but even then, I am not familiar with this class in Eclipse. I can try to answer some specific questions but it's not like I know the answer and am just hiding it from you (like teachers normally do). I don't know the answer :).


This uses Travis to deploy to an upstream target on every passing commit. In this case, we're having Travis deploy to the Pantheon site at https://dashboard.getpantheon.com/sites/f0072597-f475-4513-af94-13a33b630923 .


why the `()`?


Not anymore ;)


And also since I am not familiar with this Eclipse class, please take my guidance with a grain of salt. You probably know more than I do :).


Unrelated: maybe `DeclarationContainerImpl` should be renamed and should not be public?


this is the way to generate random-day commits for example in a 400 range days (not consecutive) ??


ah ! gotcha


:tada:


ok


So far we don't know yet, there is no Statement that final variable, more likely, we might need a approach like iterate over collection


@mssavai I think we need to handle this null return value. Because this would mean we're adding null to the list of observation, isn't it?


*the user*


Maybe change that to boolean value for enable or disable gravity, directly in Physics class


`display_survey_list` would be better english

also, there shouldn't be `/display` in the URL..


Mmm, I see


i would omit the trailing slash here since we don't have anything inside. i'd also be fine with keeping it though.


 #[zstack Test Bot Report] P A S S
 Integration Test Result:
Test Summary:

 TestSuite|TestCase | Pass | Fail | Timeout | Skip
 ---------|---------| ---- | ---- | ------- | ----
 basic_test|__suite_setup__|0|1|0|0
basic_test|_basic/test_create_vm_|0|0|0|1
basic_test|_basic/test_stop_vm_|0|0|0|1
basic_test|_basic/test_start_vm_|0|0|0|1
basic_test|_basic/test_reboot_vm_|0|0|0|1
basic_test|_basic/test_add_volume_|0|0|0|1
basic_test|_basic/test_add_vol_to_stopvm_|0|0|0|1
basic_test|_basic/test_add_volume_reboot_vm_|0|0|0|1
basic_test|_basic/test_add_multi_volumes_|0|0|0|1
basic_test|_basic/test_add_volume_negative_|0|0|0|1
basic_test|_basic/test_crt_temp_from_volume_|0|0|0|1
basic_test|_basic/test_crt_vm_with_volume_|0|0|0|1
basic_test|_basic/test_vm_securitygroup_|0|0|0|1
basic_test|_basic/test_create_iso_vm_|0|0|0|1
basic_test|_account/test_crt_vm_by_normal_account_|0|0|0|1
basic_test|_account/test_crt_vm_by_normal_account2_|0|0|0|1
basic_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
basic_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
basic_test|_suite_teardown_|0|0|0|1
virtual_router_test|__suite_setup__|0|1|0|0
virtual_router_test|_host/test_reconnect_host_|0|0|0|1
virtual_router_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
virtual_router_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
virtual_router_test|_novlan/test_create_vm_|0|0|0|1
virtual_router_test|_novlan/test_reboot_vm_|0|0|0|1
virtual_router_test|_novlan/test_ping_vms_|0|0|0|1
virtual_router_test|_host/test_reconnect_host_|0|0|0|1
virtual_router_test|_vlan/test_create_vm_|0|0|0|1
virtual_router_test|_vlan/test_reboot_vm_|0|0|0|1
virtual_router_test|_vlan/test_snat_create_|0|0|0|1
virtual_router_test|_vlan/test_dnat_reboot_|0|0|0|1
virtual_router_test|_vlan/test_ping_vms_|0|0|0|1
virtual_router_test|_vlan/test_create_3vms_|0|0|0|1
virtual_router_test|_vlan/test_start_vm_|0|0|0|1
virtual_router_test|_vlan/test_3l3s_vm_|0|0|0|1
virtual_router_test|_vlan/test_remove_dhcp_|0|0|0|1
virtual_router_test|_vlan/test_2l3_vm_|0|0|0|1
virtual_router_test|_vlan/test_crt_vms_with_limited_ips_|0|0|0|1
virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.0_|0|0|0|1
virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.1_|0|0|0|1
virtual_router_test|_vlan/test_start_vms_simultaneously_|0|0|0|1
virtual_router_test|_vlan/test_crt_static_ip_vm_|0|0|0|1
virtual_router_test|_vlan/test_crt_vm_with_hostname_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_stopped_vm_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_reboot_vm_|0|0|0|1
virtual_router_test|_volume/test_add_volume_|0|0|0|1
virtual_router_test|_volume/test_add_m_vols_|0|0|0|1
virtual_router_test|_volume/test_add_volume_vr_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_volume_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_2_volumes_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_24_volumes_|0|0|0|1
virtual_router_test|_volume/test_volume_ops_on_stopped_vm_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_from_dvt_|0|0|0|1
virtual_router_test|_template_image/test_crt_temp_image_|0|0|0|1
virtual_router_test|_template_image/test_del_temp_image_|0|0|0|1
virtual_router_test|_sg/test_ingress_|0|0|0|1
virtual_router_test|_sg/test_egress_|0|0|0|1
virtual_router_test|_sg/test_icmp_|0|0|0|1
virtual_router_test|_sg/test_udp_|0|0|0|1
virtual_router_test|_sg/test_stopped_vm_|0|0|0|1
virtual_router_test|_sg/test_vm_ops_|0|0|0|1
virtual_router_test|_sg/test_2vm_egress_|0|0|0|1
virtual_router_test|_sg/test_2vm_ingress_|0|0|0|1
virtual_router_test|_sg/test_4vm_complx_|0|0|0|1
virtual_router_test|_sg/test_detach_l3_|0|0|0|1
virtual_router_test|_pf/test_2l3s_pfs_|0|0|0|1
virtual_router_test|_pf/test_attach_pf_|0|0|0|1
virtual_router_test|_pf/test_delete_pf_after_destroy_vm_|0|0|0|1
virtual_router_test|_pf/test_del_vip_before_add_pf_to_vm_|0|0|0|1
virtual_router_test|_pf/test_multi_pfs_sg_tcp_|0|0|0|1
virtual_router_test|_pf/test_multi_rules_|0|0|0|1
virtual_router_test|_pf/test_pf_after_destroy_vm_|0|0|0|1
virtual_router_test|_pf/test_pf_sg_tcp_|0|0|0|1
virtual_router_test|_pf/test_pfs_tcp_udp_same_vip_ports_|0|0|0|1
virtual_router_test|_pf/test_pfs_tcp_with_same_vip_|0|0|0|1
virtual_router_test|_pf/test_tcp_|0|0|0|1
virtual_router_test|_pf/test_udp_|0|0|0|1
virtual_router_test|_pf/test_vm_ops_|0|0|0|1
virtual_router_test|_eip/test_2_eips_|0|0|0|1
virtual_router_test|_eip/test_2l3s_eip_pf_|0|0|0|1
virtual_router_test|_eip/test_2l3s_eips_|0|0|0|1
virtual_router_test|_eip/test_attach_eip_|0|0|0|1
virtual_router_test|_eip/test_create_eip_vm_|0|0|0|1
virtual_router_test|_eip/test_del_vip_before_add_eip_to_vm_|0|0|0|1
virtual_router_test|_eip/test_eip_sg_tcp_|0|0|0|1
virtual_router_test|_eip/test_pf_eip_attach_|0|0|0|1
virtual_router_test|_eip/test_vm_ops_|0|0|0|1
virtual_router_test|_eip/test_vm_ops2_|0|0|0|1
virtual_router_test|_snapshot/test_backup_snapshot_|0|0|0|1
virtual_router_test|_snapshot/test_create_snapshot_|0|0|0|1
virtual_router_test|_snapshot/test_create_sp_after_delete_|0|0|0|1
virtual_router_test|_snapshot/test_create_image_by_snapshot_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_for_both_root_..._|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm2_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm3_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm_|0|0|0|1
virtual_router_test|_snapshot/test_delete_snapshot_on_ru..._|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_live_vm_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_from_vol_crt_f..._|0|0|0|1
virtual_router_test|_snapshot/test_change_max_sp_depth_|0|0|0|1
virtual_router_test|_snapshot/test_change_max_sp_depth_l..._|0|0|0|1
virtual_router_test|_regression/delete_sg_with_2_attache..._|0|0|0|1
virtual_router_test|_regression/rm_nic_sg_on_stopped_vm_|0|0|0|1
virtual_router_test|_regression/test_data_volume_with_vm..._|0|0|0|1
virtual_router_test|_vr/test_ping_vms_reboot_vr_|0|0|0|1
virtual_router_test|_vr/test_reconnect_vr_|0|0|0|1
virtual_router_test|_vr/test_start_vrs_simultaneously_|0|0|0|1
virtual_router_test|_host/test_reconnect_host_|0|0|0|1
virtual_router_test|_suite_teardown_|0|0|0|1
local_ps_virtual_router_test|__suite_setup__|0|1|0|0
local_ps_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_ps_virtual_router_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
local_ps_virtual_router_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_novlan/test_create_vm_|0|0|0|1
local_ps_virtual_router_test|_novlan/test_reboot_vm_|0|0|0|1
local_ps_virtual_router_test|_novlan/test_ping_vms_|0|0|0|1
local_ps_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_create_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_reboot_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_snat_create_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_dnat_reboot_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_ping_vms_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_create_3vms_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_start_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_3l3s_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_remove_dhcp_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_2l3_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vms_with_limited_ips_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.0_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.1_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_start_vms_simultaneously_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_static_ip_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vm_with_hostname_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_reboot_vm_|0|0|0|1
local_ps_virtual_router_test|_volume/test_add_volume_|0|0|0|1
local_ps_virtual_router_test|_volume/test_add_m_vols_|0|0|0|1
local_ps_virtual_router_test|_volume/test_add_volume_vr_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_volume_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_2_volumes_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_24_volumes_|0|0|0|1
local_ps_virtual_router_test|_volume/test_volume_ops_on_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_from_dvt_|0|0|0|1
local_ps_virtual_router_test|_template_image/test_crt_temp_image_|0|0|0|1
local_ps_virtual_router_test|_template_image/test_del_temp_image_|0|0|0|1
local_ps_virtual_router_test|_sg/test_ingress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_egress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_icmp_|0|0|0|1
local_ps_virtual_router_test|_sg/test_udp_|0|0|0|1
local_ps_virtual_router_test|_sg/test_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_sg/test_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_sg/test_2vm_egress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_2vm_ingress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_4vm_complx_|0|0|0|1
local_ps_virtual_router_test|_sg/test_detach_l3_|0|0|0|1
local_ps_virtual_router_test|_pf/test_2l3s_pfs_|0|0|0|1
local_ps_virtual_router_test|_pf/test_attach_pf_|0|0|0|1
local_ps_virtual_router_test|_pf/test_delete_pf_after_destroy_vm_|0|0|0|1
local_ps_virtual_router_test|_pf/test_del_vip_before_add_pf_to_vm_|0|0|0|1
local_ps_virtual_router_test|_pf/test_multi_pfs_sg_tcp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_multi_rules_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pf_after_destroy_vm_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pf_sg_tcp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pfs_tcp_udp_same_vip_ports_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pfs_tcp_with_same_vip_|0|0|0|1
local_ps_virtual_router_test|_pf/test_tcp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_udp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_eip/test_2_eips_|0|0|0|1
local_ps_virtual_router_test|_eip/test_2l3s_eip_pf_|0|0|0|1
local_ps_virtual_router_test|_eip/test_2l3s_eips_|0|0|0|1
local_ps_virtual_router_test|_eip/test_attach_eip_|0|0|0|1
local_ps_virtual_router_test|_eip/test_create_eip_vm_|0|0|0|1
local_ps_virtual_router_test|_eip/test_del_vip_before_add_eip_to_vm_|0|0|0|1
local_ps_virtual_router_test|_eip/test_eip_sg_tcp_|0|0|0|1
local_ps_virtual_router_test|_eip/test_pf_eip_attach_|0|0|0|1
local_ps_virtual_router_test|_eip/test_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_eip/test_vm_ops2_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_backup_snapshot_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_create_snapshot_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_create_sp_after_delete_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_create_image_by_snapshot_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_for_both_root_..._|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm2_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm3_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_delete_snapshot_on_ru..._|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_live_vm_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_from_vol_crt_f..._|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_change_max_sp_depth_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_change_max_sp_depth_l..._|0|0|0|1
local_ps_virtual_router_test|_regression/delete_sg_with_2_attache..._|0|0|0|1
local_ps_virtual_router_test|_regression/rm_nic_sg_on_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_regression/test_data_volume_with_vm..._|0|0|0|1
local_ps_virtual_router_test|_vr/test_ping_vms_reboot_vr_|0|0|0|1
local_ps_virtual_router_test|_vr/test_reconnect_vr_|0|0|0|1
local_ps_virtual_router_test|_vr/test_start_vrs_simultaneously_|0|0|0|1
local_ps_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_ps_virtual_router_test|_suite_teardown_|0|0|0|1
local_nfs_virtual_router_test|__suite_setup__|0|1|0|0
local_nfs_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_nfs_virtual_router_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
local_nfs_virtual_router_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_novlan/test_create_vm_|0|0|0|1
local_nfs_virtual_router_test|_novlan/test_reboot_vm_|0|0|0|1
local_nfs_virtual_router_test|_novlan/test_ping_vms_|0|0|0|1
local_nfs_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_create_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_reboot_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_snat_create_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_dnat_reboot_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_ping_vms_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_create_3vms_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_start_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_3l3s_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_remove_dhcp_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_2l3_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vms_with_limited_ips_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.0_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.1_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_start_vms_simultaneously_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_static_ip_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vm_with_hostname_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_reboot_vm_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_add_volume_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_add_m_vols_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_add_volume_vr_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_volume_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_2_volumes_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_24_volumes_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_volume_ops_on_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_from_dvt_|0|0|0|1
local_nfs_virtual_router_test|_template_image/test_crt_temp_image_|0|0|0|1
local_nfs_virtual_router_test|_template_image/test_del_temp_image_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_ingress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_egress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_icmp_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_udp_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_2vm_egress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_2vm_ingress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_4vm_complx_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_detach_l3_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_2l3s_pfs_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_attach_pf_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_delete_pf_after_destroy_vm_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_del_vip_before_add_pf_to_vm_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_multi_pfs_sg_tcp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_multi_rules_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pf_after_destroy_vm_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pf_sg_tcp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pfs_tcp_udp_same_vip_ports_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pfs_tcp_with_same_vip_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_tcp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_udp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_2_eips_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_2l3s_eip_pf_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_2l3s_eips_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_attach_eip_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_create_eip_vm_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_del_vip_before_add_eip_to_vm_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_eip_sg_tcp_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_pf_eip_attach_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_vm_ops2_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_backup_snapshot_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_create_snapshot_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_create_sp_after_delete_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_create_image_by_snapshot_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_for_both_root_..._|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm2_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm3_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_delete_snapshot_on_ru..._|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_live_vm_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_from_vol_crt_f..._|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_change_max_sp_depth_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_change_max_sp_depth_l..._|0|0|0|1
local_nfs_virtual_router_test|_regression/delete_sg_with_2_attache..._|0|0|0|1
local_nfs_virtual_router_test|_regression/rm_nic_sg_on_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_regression/test_data_volume_with_vm..._|0|0|0|1
local_nfs_virtual_router_test|_vr/test_ping_vms_reboot_vr_|0|0|0|1
local_nfs_virtual_router_test|_vr/test_reconnect_vr_|0|0|0|1
local_nfs_virtual_router_test|_vr/test_start_vrs_simultaneously_|0|0|0|1
local_nfs_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_nfs_virtual_router_test|_suite_teardown_|0|0|0|1
Total|292|0|4|0|288


no need to store the surveys on `self`


Hi!

There is some confusion in the submitted patch. On the very line you edited, your CWD is marked as `DBIx-Class/examples/Schema$`. Also a bit higher up on line 27 you have an explicit `cd ...` command.

Could you please harmonize these pieces?
Thanks!


tam tam


I do not follow this change.  Why is `typ` the same as `session[:userid]`?


![image](https://cloud.githubusercontent.com/assets/6815038/9225227/c6cf7d62-4125-11e5-911d-b449be4489b8.png)

hi., i follow your  tutorials from javavids.com, i have some problem while adding slf4j log4j   jar in pom.xml  i having   error message, i don't know how to solve this issue  b'cuz i am new to  spring mvc. can u please  give some  tips to  initialize log4j system


Here, we assume strict client authentication is enabled by default, in such cases, it is better to add a debug log saying above element is not present, hence credential validation is enabled. This help us to find bugs by enabling debug logs not by debugging the code.


Yeah, I agree. Some lines are over 100 lines in this project, and I just reflexively broke them. I'll follow up with something better.


I've taken a look at the API and there is only one copy of this method.


    raise Forbidden(response=redirect_to_login(reason=_('You are trying to answer a survey that requires you to be logged in')))

this will show a nice message if the login page is enabled


Изменил элемент картинки на image_tag


Do we have test case when callable is `KProperty2` and `KMutableProperty2`?


This wonderful refactoring can come out into its own PR.


if the survey was already submitted i'd simply flash a message and redirect to the survey list (you need to move the check into _process or `_checkParams` for that)


能用的啊，接口一样的


`survey=self.survey`


Well, I would really like to know what is wrong here and why I'm still seeing patterns between different local domains and thus GPUs.

The simulation grid is `-g 128 256 64` with `-d 2 2 1`.

Here a picture of the electron density:
![new_seed_still_patterns](https://cloud.githubusercontent.com/assets/5416860/9225371/3c3b5c28-4109-11e5-98fc-f8be072b6dc2.png)

Here the same picture magnified and with lines between the local domains
![new_seed_still_patterns_with_gpu_separation](https://cloud.githubusercontent.com/assets/5416860/9225355/2438dbc8-4109-11e5-8fa6-6117d5b1a368.png)


Поменял.


why not merge `save_submission` and `save_answers` into a single method?


@miigotu page name also has a `FixME` in the tittle.


`submission=submission`


Sascha

Do NOT push directly to ANY of the repositories. There's a mandatory PR policy for flatfish.

Thanks.


I think the JavaBeans specification allows this (having both `get` and `is`)


why not use colspan?


maybe a `survey.can_submit(session.user)` method would be cleaner?


There is a `test.throws` assertion you can use instead of the try catch.


23:1: E402 module level import not at top of file
25:1: I100 Imports statements are in the wrong order. import re should be before from datetime
25:1: E402 module level import not at top of file
26:1: E402 module level import not at top of file
27:1: I100 Imports statements are in the wrong order. import copy should be before import zlib
27:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
29:1: E402 module level import not at top of file
30:1: I100 Imports statements are in the wrong order. import cookielib should be before import urllib2
30:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
32:1: E402 module level import not at top of file
34:1: E402 module level import not at top of file
35:1: I201 Missing newline before sections or imports.
35:1: E402 module level import not at top of file
37:1: I100 Imports statements are in the wrong order. from invenio.ext.logging should be before import invenio_formatter
37:1: E402 module level import not at top of file
38:1: E402 module level import not at top of file
39:1: F401 'auto_version_url' imported but unused
39:1: E402 module level import not at top of file
40:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord.xmlmarc2textmarc should be before from invenio.utils.url
40:1: E402 module level import not at top of file
42:1: I101 Imported names are in the wrong order. Should be CFG_BIBCATALOG_SYSTEM, CFG_BIBCATALOG_SYSTEM_RT_URL, CFG_BIBEDIT_AJAX_RESULT_CODES_REV, CFG_BIBEDIT_AUTOCOMPLETE, CFG_BIBEDIT_SHOW_HOLDING_PEN_REMOVED_FIELDS, CFG_SITE_LANG
42:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.bibrecord.xmlmarc2textmarc
42:1: E402 module level import not at top of file
48:1: I101 Imported names are in the wrong order. Should be deactivate_cache, delete_hp_change, delete_related_holdingpen_changes, get_hp_update_xml, get_info_of_record_revision, get_marcxml_of_record_revision, get_name_tags_all, get_record_last_modification_date, get_record_revision_author, get_record_revisions, get_related_hp_changesets, reserve_record_id
48:1: E402 module level import not at top of file
55:1: I101 Imported names are in the wrong order. Should be InvalidCache, add_record_cnum, cache_exists, cache_expired, can_record_have_physical_copies, create_cache, crossref_process_template, delete_cache, extend_record_with_template, get_affiliation_for_paper, get_bibrecord, get_cache_contents, get_cache_mtime, get_field_templates, get_marcxml_of_revision, get_new_ticket_RT_info, get_record_revision_authors, get_record_revision_timestamps, get_record_template, get_record_templates, get_xml_from_textmarc, latest_record_revision, merge_record_with_template, modify_record_timestamp, record_is_conference, record_locked_by_other_user, record_locked_by_queue, record_locked_by_user_details, record_revision_exists, record_xml_output, replace_references, revision_to_timestamp, save_xml_record, timestamp_to_revision, touch_cache, update_cache_contents
55:1: E402 module level import not at top of file
70:1: I101 Imported names are in the wrong order. Should be create_field, create_record, field_add_subfield, field_get_subfield_values, print_rec, record_add_field, record_add_fields, record_add_subfield_into, record_delete_field, record_delete_subfield_from, record_extract_dois, record_get_field_instances, record_get_field_values, record_get_subfields, record_modify_controlfield, record_modify_subfield, record_move_fields, record_move_subfield, record_order_subfields, record_replace_field, record_strip_controlfields, record_strip_empty_fields, record_strip_empty_volatile_subfields
70:1: E402 module level import not at top of file
81:1: I101 Imported names are in the wrong order. Should be CFG_BIBEDIT_INTERNAL_DOI_PROTECTION_LEVEL, CFG_BIBEDIT_KB_SUBJECTS, CFG_BIBEDIT_PROTECTED_FIELDS, CFG_BIBUPLOAD_INTERNAL_DOI_PATTERN, CFG_CERN_SITE, CFG_INSPIRE_SITE, CFG_SITE_RECORD, CFG_SITE_URL
81:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.bibrecord
81:1: F401 'CFG_BIBEDIT_PROTECTED_FIELDS' imported but unused
81:1: E402 module level import not at top of file
85:1: I101 Imported names are in the wrong order. Should be guess_primary_collection_of_a_record, perform_request_search, record_exists
85:1: E402 module level import not at top of file
87:1: E402 module level import not at top of file
88:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibcatalog.api should be before from invenio.legacy.webuser
88:1: E402 module level import not at top of file
89:1: E402 module level import not at top of file
90:1: E402 module level import not at top of file
91:1: E402 module level import not at top of file
92:1: I101 Imported names are in the wrong order. Should be show_diff, wash_for_xml
92:1: E402 module level import not at top of file
93:1: I100 Imports statements are in the wrong order. from invenio.modules.knowledge.api should be before from invenio.utils.text
93:1: E402 module level import not at top of file
94:6: E126 continuation line over-indented for hanging indent
96:1: I100 Imports statements are in the wrong order. from invenio.legacy.refextract.api should be before from invenio.modules.knowledge.api
96:1: E402 module level import not at top of file
97:36: E126 continuation line over-indented for hanging indent
100:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.legacy.refextract.api
100:1: E402 module level import not at top of file
101:1: I101 Imported names are in the wrong order. Should be CrossrefError, get_marcxml_for_doi
101:1: E402 module level import not at top of file
103:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from invenio.utils.crossref
103:1: E402 module level import not at top of file
114: D103 Missing docstring in public function
119: D400 First line should end with a period (not ':')
119: D205 1 blank line required between summary line and description (found 0)
126:17: E126 continuation line over-indented for hanging indent
129:22: E203 whitespace before ':'
130:23: E203 whitespace before ':'
131:23: E203 whitespace before ':'
132:28: E203 whitespace before ':'
133:33: E203 whitespace before ':'
134:13: E126 continuation line over-indented for hanging indent
135:23: E203 whitespace before ':'
136:30: E203 whitespace before ':'
138:33: E203 whitespace before ':'
139:22: E203 whitespace before ':'
140:24: E203 whitespace before ':'
141:13: E126 continuation line over-indented for hanging indent
143:1: E302 expected 2 blank lines, found 1
143: D400 First line should end with a period (not 's')
143: D205 1 blank line required between summary line and description (found 0)
157:9: E115 expected an indented block (comment)
159:21: E126 continuation line over-indented for hanging indent
159:27: E203 whitespace before ':'
160:34: E203 whitespace before ':'
161:37: E203 whitespace before ':'
162:26: E203 whitespace before ':'
163:28: E203 whitespace before ':'
164:17: E121 continuation line under-indented for hanging indent
167:21: E126 continuation line over-indented for hanging indent
169:26: E203 whitespace before ':'
170:27: E203 whitespace before ':'
171:27: E203 whitespace before ':'
172:32: E203 whitespace before ':'
173:37: E203 whitespace before ':'
177:1: E302 expected 2 blank lines, found 1
179:11: E221 multiple spaces before operator
196:26: E251 unexpected spaces around keyword / parameter equals
196:34: E251 unexpected spaces around keyword / parameter equals
196:26: E221 multiple spaces before operator
197:25: E251 unexpected spaces around keyword / parameter equals
197:34: E251 unexpected spaces around keyword / parameter equals
197:25: E221 multiple spaces before operator
198:27: E251 unexpected spaces around keyword / parameter equals
198:34: E251 unexpected spaces around keyword / parameter equals
198:27: E221 multiple spaces before operator
199:29: E251 unexpected spaces around keyword / parameter equals
199:34: E251 unexpected spaces around keyword / parameter equals
199:29: E221 multiple spaces before operator
200:24: E251 unexpected spaces around keyword / parameter equals
200:34: E251 unexpected spaces around keyword / parameter equals
200:24: E221 multiple spaces before operator
201:29: E251 unexpected spaces around keyword / parameter equals
201:34: E251 unexpected spaces around keyword / parameter equals
201:29: E221 multiple spaces before operator
202:29: E251 unexpected spaces around keyword / parameter equals
202:34: E251 unexpected spaces around keyword / parameter equals
202:29: E221 multiple spaces before operator
203:32: E251 unexpected spaces around keyword / parameter equals
203:34: E251 unexpected spaces around keyword / parameter equals
204:24: E251 unexpected spaces around keyword / parameter equals
204:34: E251 unexpected spaces around keyword / parameter equals
204:24: E221 multiple spaces before operator
207:5: E303 too many blank lines (2)
241:32: E203 whitespace before ':'
242:33: E203 whitespace before ':'
243:27: E203 whitespace before ':'
243:66: E221 multiple spaces before operator
244:35: E203 whitespace before ':'
255: D210 No whitespaces allowed surrounding docstring text
305:13: F821 undefined name 'bibedit_templates'
306:13: F821 undefined name 'bibedit_templates'
317: D400 First line should end with a period (not 'h')
317: D205 1 blank line required between summary line and description (found 0)
327: D400 First line should end with a period (not 'D')
327: D205 1 blank line required between summary line and description (found 0)
347: D202 No blank lines allowed after function docstring (found 1)
347: D400 First line should end with a period (not 's')
381:17: F821 undefined name 'bibedit_templates'
382:49: E128 continuation line under-indented for visual indent
385:1: E302 expected 2 blank lines, found 1
385: D400 First line should end with a period (not 'r')
385: D205 1 blank line required between summary line and description (found 0)
406: D103 Missing docstring in public function
409:5: B901 blind except: statement
431:9: E128 continuation line under-indented for visual indent
432:9: E128 continuation line under-indented for visual indent
432:9: E129 visually indented line with same indent as next logical line
457:84: E231 missing whitespace after ','
499:1: E302 expected 2 blank lines, found 1
499: D210 No whitespaces allowed surrounding docstring text
499: D400 First line should end with a period (not 's')
549: D400 First line should end with a period (not 'f')
549: D205 1 blank line required between summary line and description (found 0)
582:13: E303 too many blank lines (2)
594: D400 First line should end with a period (not 'r')
594: D205 1 blank line required between summary line and description (found 0)
774:75: E502 the backslash is redundant between brackets
878:25: E127 continuation line over-indented for visual indent
894:53: E261 at least two spaces before inline comment
895:52: E114 indentation is not a multiple of four (comment)
895:52: E116 unexpected indentation (comment)
903:61: E126 continuation line over-indented for hanging indent
910:25: E126 continuation line over-indented for hanging indent
965:17: E128 continuation line under-indented for visual indent
1016: D210 No whitespaces allowed surrounding docstring text
1016: D401 First line should be in imperative mood ('Perform', not 'Performs')
1016: D400 First line should end with a period (not 'h')
1016: D205 1 blank line required between summary line and description (found 0)
1035: D202 No blank lines allowed after function docstring (found 1)
1035: D400 First line should end with a period (not 'g')
1035: D205 1 blank line required between summary line and description (found 0)
1083:13: B901 blind except: statement
1091:13: B901 blind except: statement
1140:21: E128 continuation line under-indented for visual indent
1173:67: E114 indentation is not a multiple of four (comment)
1175:44: E126 continuation line over-indented for hanging indent
1186:44: E261 at least two spaces before inline comment
1188:42: E261 at least two spaces before inline comment
1189:43: E114 indentation is not a multiple of four (comment)
1189:43: E116 unexpected indentation (comment)
1193:17: E128 continuation line under-indented for visual indent
1199:21: E128 continuation line under-indented for visual indent
1204:19: E128 continuation line under-indented for visual indent
1209:13: E128 continuation line under-indented for visual indent
1209:46: E251 unexpected spaces around keyword / parameter equals
1210:13: E122 continuation line missing indentation or outdented
1213:13: E128 continuation line under-indented for visual indent
1219:13: E128 continuation line under-indented for visual indent
1222:42: E203 whitespace before ','
1230:17: E128 continuation line under-indented for visual indent
1237:18: E261 at least two spaces before inline comment
1240:17: E128 continuation line under-indented for visual indent
1255:29: E128 continuation line under-indented for visual indent
1263:33: E128 continuation line under-indented for visual indent
1289: D400 First line should end with a period (not 'e')
1289: D205 1 blank line required between summary line and description (found 0)
1303:9: E116 unexpected indentation (comment)
1376: D200 One-line docstring should fit on one line with quotes (found 3)
1390:21: E128 continuation line under-indented for visual indent
1405:25: E122 continuation line missing indentation or outdented
1406:25: E122 continuation line missing indentation or outdented
1407:25: E122 continuation line missing indentation or outdented
1480:38: E128 continuation line under-indented for visual indent
1500: D401 First line should be in imperative mood ('Add', not 'Adds')
1500: D400 First line should end with a period (not ')')
1500: D205 1 blank line required between summary line and description (found 0)
1516:36: E127 continuation line over-indented for visual indent
1517:36: E127 continuation line over-indented for visual indent
1522: D400 First line should end with a period (not 's')
1539:9: E128 continuation line under-indented for visual indent
1540:13: E128 continuation line under-indented for visual indent
1541:9: E128 continuation line under-indented for visual indent
1546: D400 First line should end with a period (not 'l')
1546: D205 1 blank line required between summary line and description (found 0)
1564:5: B901 blind except: statement
1587: D210 No whitespaces allowed surrounding docstring text
1587: D202 No blank lines allowed after function docstring (found 1)
1587: D400 First line should end with a period (not 'd')
1629:5: B901 blind except: statement
1649: D210 No whitespaces allowed surrounding docstring text
1649: D400 First line should end with a period (not 'g')
1649: D200 One-line docstring should fit on one line with quotes (found 3)
1681: D210 No whitespaces allowed surrounding docstring text
1681: D400 First line should end with a period (not 'F')
1681: D200 One-line docstring should fit on one line with quotes (found 2)
1693: D210 No whitespaces allowed surrounding docstring text
1693: D400 First line should end with a period (not 't')
1693: D200 One-line docstring should fit on one line with quotes (found 2)
1705:13: E126 continuation line over-indented for hanging indent
1710: D210 No whitespaces allowed surrounding docstring text
1710: D400 First line should end with a period (not 'o')
1710: D205 1 blank line required between summary line and description (found 0)
1725:13: E128 continuation line under-indented for visual indent
1726:29: E127 continuation line over-indented for visual indent
1732: D401 First line should be in imperative mood ('Return', not 'Returns')
1732: D400 First line should end with a period (not 't')
1749:26: E128 continuation line under-indented for visual indent
1750:26: E124 closing bracket does not match visual indentation
1765:38: E128 continuation line under-indented for visual indent
1777:5: E303 too many blank lines (2)
1779:1: E266 too many leading '#' for block comment
1781:1: E302 expected 2 blank lines, found 1
1781: D400 First line should end with a period (not 's')
1833: D210 No whitespaces allowed surrounding docstring text
1833: D400 First line should end with a period (not 'e')
1846: D209 Multi-line docstring closing quotes should be on a separate line
1846: D400 First line should end with a period (not 'e')
1846: D205 1 blank line required between summary line and description (found 0)
1859:5: B901 blind except: statement
1866: D210 No whitespaces allowed surrounding docstring text
1866: D400 First line should end with a period (not 'e')
1871: D103 Missing docstring in public function
1908: D103 Missing docstring in public function
1921:45: E131 continuation line unaligned for hanging indent


1: D400 First line should end with a period (not 'I')
4: L102 copyright year is outdated, expected 2015 but got 2014
26:1: I100 Imports statements are in the wrong order. from tempfile should be before import pkg_resources
26:1: I201 Missing newline before sections or imports.
30:1: I100 Imports statements are in the wrong order. from invenio.legacy.webpage should be before from invenio.legacy.webuser
31:1: I101 Imported names are in the wrong order. Should be CFG_ETCDIR, CFG_TMPSHAREDDIR
31:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.webpage
31:1: F401 'CFG_ETCDIR' imported but unused
32:1: I101 Imported names are in the wrong order. Should be extract_references_from_file_xml, extract_references_from_string_xml, extract_references_from_url_xml
33:36: E126 continuation line over-indented for hanging indent
37:1: I100 Imports statements are in the wrong order. import invenio.legacy.template should be before from invenio_formatter.engine
41: D400 First line should end with a period (not 'n')
50: D400 First line should end with a period (not 'h')
53:12: E127 continuation line over-indented for visual indent
54:12: E127 continuation line over-indented for visual indent
57: D209 Multi-line docstring closing quotes should be on a separate line
57: D400 First line should end with a period (not 'g')
77: D400 First line should end with a period (not 'v')
86: D203 1 blank line required before class docstring (found 0)
86: D204 1 blank line required after class docstring (found 0)
86: D400 First line should end with a period (not 'I')
94: D400 First line should end with a period (not 'f')
103: D400 First line should end with a period (not 'l')
117: D400 First line should end with a period (not 't')
129: D203 1 blank line required before class docstring (found 0)
129: D204 1 blank line required after class docstring (found 0)
129: D400 First line should end with a period (not 'I')
132:9: E128 continuation line under-indented for visual indent
138: D400 First line should end with a period (not 's')
148: D401 First line should be in imperative mood ('Refrence', not 'Refrences')
148: D209 Multi-line docstring closing quotes should be on a separate line
148: D400 First line should end with a period (not 'e')
177:44: E128 continuation line under-indented for visual indent