Hello, I believe this change is incorrect. See [rfc7208#3.3](https://tools.ietf.org/html/rfc7208#section-3.3)

> If a published record contains multiple character-strings, then the record MUST be treated as if those strings are concatenated together without adding spaces.

I tried to look around for the motivation for this change (issues, git log), but I didn't find anything. Unless I overlooked something, I believe this should be reverted to more closely adhere to rfc7208.


bài sheep khá đầy đủ, bài làm của anh rất tốt


UpdateDocsSpecificVersionInRunMultiDirBat (JasonGlazer) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1077 of 1077 tests passed, 0 test warnings)

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


bài làm của chị rất chính xác :dancers:


bài sheep chị cho con rùa thêm làm gì :))))))))) cơ mà bài làm đủ rồi, chị làm tốt lắm


True enough. Node provides no alternative when `process.exit` is used. Uglify is generally used in command line apps. Mac `stdout` was blocking for years and no one noticed until the libuv upgrade.


okie man, cơ mà thiếu mất bài 3 rồi


ok. now try `manifestData['manifest']['uses-sdk']`


ok. now try manifestData['manifest']['uses-sdk']


Ah good catch. We were running into multi-string SPF records and thought this was an artifact of Ruby's `Resolv::DNS` library. Joining them without a space commonly resulted in an invalid SPF record. I will side with the RFC and revert this.

Also, would you happen to have an example domain with a multi-string SPF record I could use in the specs?


bài 4 còn thiếu nhé


Using a condition to check for true or false values results in the same
result as try-catching it which is considered more pythonic
On May 4, 2016 7:43 PM, "Surest Texas" <notifications@github.com> wrote:

> Here is something I would like your opinion on:
> Here is the code:
>
>     def removeGroup(self, group):
>         """ Removes the player to a specified group. If they are not part of the specified group, an IndexError is raised.
>         Args:
>             group: Group node (string)
>
>         Returns:
>             """
>         if "users" not in self.permissions:
>             self.permissions["users"] = {}
>         for uuid in self.permissions["users"]:
>             if uuid == self.mojangUuid.string:  # was self.uuid.string:
>                 if group in self.permissions["users"][uuid]["groups"]:
>                     self.permissions["users"][uuid]["groups"].remove(group)
>                 else:
>                     raise IndexError("%s is not part of the group '%s'" % (self.username, group))
>
> Let us say a pluginDev or plugin user ran a command which uses this method
> to remove player "froggy" from group "trusted". However, froggy is not in
> trusted because someone else already removed him (or maybe he never was a
> trusted player...)
>
> In the current setup, the person running this command gets a chat message
> back from the wrapper saying "something went wrong on the server side.
> Apologies!" (or something like that). A look at the console is the only way
> to know what the exception was.
>
> Would it not be more desireable to allow the plugin to know if the command
> failed with removeGroup() returning False versus just raising an exception?
> The plugin could then use something like:
>
>     if froggyplayer.removeGroup("trusted"):
>         adminplayer.message("%s removed from group trusted" % froggyplayer.username)
>     else:
>         adminplayer.message("Error: %s is not in group trusted" % froggyplayer.username)
>
> —
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub
> <https://github.com/suresttexas00/minecraft-wrapper/commit/210ef24e54e7e284d6eeac36ddb9ef725d9fc62c#commitcomment-17361121>
>


Hi @rogerlucas

The detail is in 2nd comment of this conversation.

In short, I removed the "content" field in the synchronization between server and client for the synchronization speed.

And you can access "http://localhost:8000/db_face/xxx.jpg" to show the trained face.
Therefore, if use the link instead of "content" field, the black images should be fixed.

But I still don't know how to get real domain name instead of "localhost".
If you figure it out, please let me know.


код чтения с файла можно в отдельный метод сунуть, по желанию


bài làm của chị rất ổn, thiếu bài 4.4 nữa nha


how?


Why not just move the patch to [bin/uglify.js](https://github.com/mishoo/UglifyJS2/blob/a0e03c9df47c411a40bceef02af2ce3dd1a329cc/bin/uglifyjs)?

Regardless of what this patch does, it just feels wrong to modify global unrelated behavior, it may surprise other apps that they suddenly break just because they stop relying on UglifyJS. Are there any downsides to just moving it to a binary?


**BOLD**


Yes, a token is valid for all searches for a given node. If it expires, it should be renewed for all requests.


Either `git rebase -i HEAD~1` or `git rebase -i HEAD~2`, not sure


thiếu bài số 3 và bài số 4


bài số 4 bị thiếu rồi ạ


где ошибка, покажи)


Thanks for taking the time to not let yellow patches go to waste!


thiếu bài số 4 nha em


randomize the field for a battleship game


thiếu bài số 3 và số 4 rồi khang ơi


bài làm của anh rất tốt và đầy đủ


Aquí debería haber una prueba que usa el clic sobre el icono de "Reply to thread" en vez de usar la URL directamente


nvm I'll do it


What did this do, exactly?


Yay you were able to use it.


sorry, yeah, that lacks context. I'm referring to my implementation, not the concept, and it's only been possible to code it this way since jb/functions made the closure version efficient (and made the macro unnecessary)


Change!


Mobile right now, but I bet the issue is due to `img[c,]` returning a vector/list in R, resulting in the subsequent `nrow(img)` in `im2col` returning NA. Pooling just reuses the `im2col` code, but does it over each channel separately, rather than over all channels collectively like in convolution, so this issue would only show up here. Can you try explicitly wrapping `img[c,]` here in a matrix with 1 row and Hin*Win columns?


【一脸茫然】


If you feel strongly about it you could submit a PR to put the functionality in `tools/stdio.js` and then have `bin/extract-props.js`, `bin/uglifyjs` and `test/run-tests.js` require and run it as the first statement.


not fully


Oke


TeamCity ReOpenLDAP :: devel [Build 254](https://binbug.bigbrother-matrix.ru/teamcity/viewLog.html?buildId=2083&buildTypeId=ReOpenLDAP_Devel&guest=1) is now running


Thanks for the input! looks like it works properly.


Wonder `fn` need to bind context?


Random location for this?


@aaustin ,
Here's the content:
```
[ { '$':
     { 'android:minSdkVersion': '14',
       'android:targetSdkVersion': '23' } } ]
```


@ansarimofid : Please verify the same.


なるべく
showのアクションにはshowのテンプレートを使ったほうが良いです。後に他の人がみるとわかりにくいので...

もしこういうことがしたいためにindex使わざるを得ない状況とかであれば教えて頂けるとそれにみあったルーティングの設定などをお伝えできると思います


@Naventus


多分これは可変だと思うので、controllerではなくてdatabaseとかで管理したほうが良いかと思います！
もし定数であれば別の方法で管理ができるので、言ってください！
@Naventus


Apparently, "mid-range" express "medium cost", that is, something that is not cheap, but neither expensive. So if we use "mid-range seller", we might be saying that it's a seller with "average" prices, and this wouldn't be related to the number of books they normally sell. I think that maybe "medium" was ok, or "average", "standard", "midpoint" maybe? I will look for a more accurate one.


zamiast informacji w stylu "Nieznana płeć" dostaniemy błąd mówiący, że jest tam pusto, a to nie będzie prawda :)


+OU - OU to create the Computer account in, this must be the DN eg "OU=TestOU1,OU=Servers,DC=sddc,DC=lab"
It also needs to be in quotes due to the commas.


verify this please


Gg


#

> [`_****_`](

-

- [ ] @1. url

)


potter


I've bumped into an issue w.r.t. the timeout here. What's happening is that a transfer can get aborted while a packet is being transferred. A `usb.core.USBError` will be raised and `packet` will end up being `None`.
Worse, the next time we read, we'll receive the remainder of the packet...

I traced the problem down to libusb:
https://github.com/libusb/libusb/blob/578942b5a90cd36b47b11e0992c2e92a05b70d91/libusb/os/darwin_usb.c#L1721

OS X's API has two timeouts, a "no data" timeout and a "completion" timeout, the latter will abort an on-going data transfer if it takes too long. In our case, we'd want a short "no data" timeout and a long "completion" timeout.

Getting this changed in libusb is probably not a quick fix.

I could just bump the timeout to something really long, but then we'd not be able to gracefully exit the threads.
Any ideas?

cc @chrisc11 @Hexxeh


is much more than -> còn hơn cả một hệ điều hành
no matter how -> bất kể như thế nào (idiom), cả câu ý là dù hệ điều hành có thế nào thì Debian vẫn hơn.
featureful -> nhiều tính năng
people should enjoy -> mọi người được hưởng thụ
not the other way around -> chứ không phải ngược lại
dismantle -> tháo rời
all the software that matters to them -> tất cả phần mềm quan trọng đối với họ
It doesn't matter if-> Chẳng có vấn đề gì /bất kể nếu
frivolous -> vớ vẩn :D (phù phiếm mình thấy thế nào ấy =)))
scenarios -> tình huống (tùy context thì dịch là kịch bản)
you should control it -> bạn nên kiểm soát nó (nó là Debian, chứ ko phải điều đó)
those freedoms -> những quyền tự do đó
able to delegate to people of their choice -> ủy quyền cho những người mà họ bầu chọn (ý nói việc bỏ phiếu)
devices -> những thiết bị (số nhiều)


Yes. Actually, what we mean here is the number of books sold which is a quantity not price.


合并最新的更新。


mid-range is literally in the middle of the range. If we are talking about
cost, it will be money, but if we are talking about sales, it refers to
sales.

2016-05-05 12:09 GMT+02:00 7ossam81 <notifications@github.com>:

> Yes. Actually, what we mean here is the number of books sold which is a
> quantity not price.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub
> <https://github.com/geneura-papers/2015_books/commit/7e30432019cd4fa778a0362e5a41d575305aee38#commitcomment-17364702>
>

--
JJ


A typo in function name.


Yes it can be done. Tho that would require us to carry around state saying if it has been done or not. So we would have to weigh the cost of extra space and a check+call in all places where the hash is used vs. doing it in the constructor. It would be interesting to see profiling on performance loss/gain on always hashing. I think we can be smart about it in the constructor and do it along with the copy.


Or the even nicer ones from amsmath, which let you control your equations in even nicer ways.

https://www.sharelatex.com/learn/Aligning_equations_with_amsmath


@junjungoal
わざわざコメントまでありがとうございます。。
実装したいのは
showでチャット画面が呼び出されるんですが
indexのviewは変わらずviewの内部にチャット画面を呼び出したいのです。

もらったコメントの方法でいくと
やはりindexの使い回す部分をテンプレート化して
renderで呼び出す形にしたほうがベストってことですよね？


**SUCCESS** - TeamCity HotRod C++ Client :: Pull requests monitor - RHEL [Build 603](http://ci.infinispan.org/viewLog.html?buildId=39354&buildTypeId=HotRodCpp_PullRequestsMonitorRhel6&guest=1) for a6ac7bfd1d92d38291c5977d05bf03680913422a
Tests: 0, 0 failed (0 new), 0 ignored. Build time: 00:05:46


Tady by měl být string `link` místo `value`.


> mid-range is literally in the middle of the range.

Yes, you're right, when it is a noun. Here we're using it as an adjective to characterize the seller. And when it is an adjective, it refers to cost, size, or quality. And we don't mean that the seller sells "averaging cost" books, neither "books not too big not too small", nor "averaging quality" books.
That's only how I see it, of course :(


Is this before or after the bomb decrements for the round?

Meaning will this not pick the bomb with 1 timer and set it to 1 (which it already is)?


We used to have that behavior, and nobody could understand why their servers kept fetching history. That's why RIPD-1112 was opened in the first place.


@junjungoal
下のコメントに少しありますが、
actionを取ってViewの表示／非表示の制御フラグとして使ってます。
単純に indexアクション=>チャットview表示しない
showアクション=>チャット取得・view表示
とするつもりですがdatabaseに持っておいたほうが良さそうですか？


mid-sales range then?

mid-range sales?

Or simply middling seller?


extInt_issue5126 (Myoldmopar) - Win64-Windows-7-VisualStudio-12: OK (2164 of 2176 tests passed, 465 test warnings)

 * 477 tests had: AUD diffs.
 * 2 tests had: MDD diffs.
 * 2 tests had: MTD diffs.
 * 1 test had: RDD diffs.
 * 11 tests had: Table big diffs.
 * 7 tests had: EIO diffs.
 * 4 tests had: ESO big diffs.
 * 3 tests had: MTR big diffs.
 * 1 test had: SSZ big diffs.
 * 1 test had: ZSZ big diffs.
 * 3 tests had: ESO small diffs.
 * 2 tests had: Table small diffs.

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


ここはテンプレートを変更したら実装も変えたほうが良さそうではありますね。


Removed simple typo


là chị đây mà em ...


それがベストです！ viewはしっかりとshowとindexに分けた方が良いです！
共通な部分はテンプレート化して呼び出しましょう！
@Naventus


そうですね！


Shouldn't ````CellPassage```` return false? :)
And ````CellDoor```` should return true.
Just noticed you don't have CellDoor, update from master!


Hi James, I think your problem is that you haven't updated to the latest version from master :)


This doesn't benefit you in any way, so I'm curious as to why you would pick it.


Nikt nie chce znać prawdy przecież :D


Okay, something to do with the ScaledSpace...


Also don't need this in here


@peyerluk can we replace the br tag with a span?
```html
<span data-editable="remove"> </span>
```
instead of
```html
<br data-editable="remove"/>
```

The line break causes problems for elements with a `display: inline-block` css property.


Might want to make it pure virtual so that subclasses are forced to define it ( ```virtual bool isDoor() = 0```)


Hi Tjorriemorrie, that is intentional.  Trigger bomb will always trigger a bomb with the lowest timer, that includes a timer of 1.


TeamCity Mobile :: Android :: Android SDK (develop) [Build 467](http://teamcity.hq.judo/viewLog.html?buildId=27248&buildTypeId=JudoAndroid_AndroidGradle) is now running


Re-branded as Version Alpha 1.3.
Sound is considered a major feature.


The following doc(s) have been deployed to the [twootenpat](https://twootenpat-static-docs.pantheonsite.io/docs) Multidev environment:
- [docs/unsupported-modules-plugins](https://twootenpat-static-docs.pantheonsite.io/docs/unsupported-modules-plugins)


Or we can remove it completely and show the placeholder on focus when the contenteditable doesn't have any content.


@FlatOutPS2
it won't do miracle but it might be less broken.


Hello, I am having the following error:
"WindowsError: [Error 216] This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher"
I have been searching for solutions on google but could not find anything. Would you please write a step by step demonstration on how to compile the .exe


Uhm, mid-sales is normally understood as mid season sales, or even as someone who is the sales manager of a company. This applied as an adjective to "ranges"... I don't know :\

With mid-range sales we have the same problem as with mid-range seller, I think.

According to some articles like https://www.bkconnection.com/10-awful-truths-about-book-publishing or http://www.stevelaube.com/what-are-average-book-sales/, "average" seems a good word to describe it, what do you think? Maybe I can try asking in quora or something.


**SUCCESS** - TeamCity HotRod C++ Client :: Pull requests monitor - WIN_S2012 [Build 452](http://ci.infinispan.org/viewLog.html?buildId=39352&buildTypeId=HotRodCpp_PullRequestsMonitorWinS2012&guest=1) for a6ac7bfd1d92d38291c5977d05bf03680913422a
Tests: 0, 0 failed (0 new), 0 ignored. Build time: 00:13:35


See also #189


Fork please.


Please add unit tests for this code.


Works for me.


4r2k/7b/2b1P1P1/3P4/1rP1K3/5P2/4P1b1/4r3 w - - 1 23
in this position attacks1 is empty, which will make the analysis easier.
`attacks2` should not contain f3 and d5 but is missing c6 and h7

The following seems to work.
`Bitboard attacks2 = ei.pi->pawn_attacks(Us) & PseudoAttacks[BISHOP][pos.square<KING>(Us)] & ~ei.attackedBy[Us][KING];`


TODO @gn what is this?


TeamCity MemSub :: Subscriptions :: Promotions Tool [Build 18](https://teamcity-aws.gutools.co.uk/viewLog.html?buildId=3991&buildTypeId=memsub_promotions_tool) is now running


What's the reason to have these function also in the global namespace?


TeamCity MemSub :: Subscriptions :: Promotions Tool [Build 18](https://teamcity-aws.gutools.co.uk/viewLog.html?buildId=3991&buildTypeId=memsub_promotions_tool) outcome was **SUCCESS**
Summary: Tests passed: 4 Build time: 00:01:14


You should probably clear the error before, otherwise other uses of `json_encode` that resulted in an error will make a valid operation fail.


What about mid-scale seller ?


Diese Änderung versaut aber alle gesetzten Faboriten und Watch-Einträge. Wofür?!


So I'm trying this out, but `yc` does not align things right at the tick / grid line. `y` also does not.

![image](https://cloud.githubusercontent.com/assets/25916/15041681/76abc77c-12db-11e6-80ab-5632c72a1c23.png)

I can set a suitable offset and correct it, but then it breaks when I change the height of the plot. Know how to fix this? note that `y` scale is ordinal...


What does `getLock` do? Why do we need it if we have `withLock`?


@randyzwitch forgot to mention you in the comment. please see above..


Just want to note - crash is not potential, it is really happens. Thanks for fix!


directionX and directionY are the ball's internal properties, so they would be better inside the Ball class


Rather do a returns annotation


Did you see my previous comments? Please address them


Looks good to me too.

2016-05-05 12:37 GMT+02:00 7ossam81 <notifications@github.com>:

> What about mid-scale seller ?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub
> <https://github.com/geneura-papers/2015_books/commit/7e30432019cd4fa778a0362e5a41d575305aee38#commitcomment-17364899>
>

--
JJ


Looks great to me :+1:


It does seem less broken. Thanks :)


is there an alignment issue here ?


В третьем питоне, начиная с 3.5,  все абстрактные типы импортируют из `typing` (ещё полезно знать про `numbers`)


what's the correct way to revert the change when mouse moves out of a mark?


Yes, it shows that.


Yeah! I agree


I submit again problem zoom


Yes there is?


@cskksc Will you be the Jack Barker to my Richard Hendricks? :smile:


Oh, wait. Something has gone really wrong here...


Next version will make it completely full screen and I will add an exit button


Is there a way to parse the Flow type definition directly? Asking because:
- Writing the comments is a bit of extra work for people working on the APIs
- The names and types in comments could go out of sync. That's the case with any docs so smaller issue.


The master branch has been tagged as 2.5.25, and it shouldn;'t have been...


Все библиотечные модули засовываются в раздел с файлом `__init__.py`. Скрипты, которые пользуются библиотеками выносятся на уровень выше корня библиотеки.


Looking at the datasheet says:
mul: 0 <= d <= 31, 0 <= r <= 31
mov: 0 <= d <= 31, 0 <= r <= 31
eor: 0 <= d <= 31
swap: 0 <= d <= 31
andi: 16 <= d <= 31, 0 <= K <= 255
or: 0 <= d <= 31, 0 <= r <= 31

This means only mx and xr1 should be a "d", the other can be "r". This makes compilation still flexible but should fix the bug too.


Nice! Like the `@description`, `@example` etc.


**SUCCESS** - TeamCity HotRod C# Client :: Pull requests monitor - WIN_S2012 [Build 147](http://ci.infinispan.org/viewLog.html?buildId=39353&buildTypeId=HotRodCSharp_PullRequestsMonitorWinS2012&guest=1) for a6ac7bfd1d92d38291c5977d05bf03680913422a
Tests: 0, 0 failed (0 new), 0 ignored. Build time: 00:14:46


This is amazing! 👍  Finally we have a proper format for documenting these. Until now we'd use bullet lists, put types in brackets or whatever we came up with for each component :)


TeamCity Mobile :: Android :: Android SDK (develop) [Build 467](http://teamcity.hq.judo/viewLog.html?buildId=27248&buildTypeId=JudoAndroid_AndroidGradle) outcome was **FAILURE**
Summary: Execution timeout (new); tests passed: 58 Build time: 00:20:16


Hmm... maybe I can. It's not using the editor itself, but might be something to do with sending the tweet afterwards.


Hah. You introduced recursion in URL


TeamCity ReOpenLDAP :: devel [Build 255](https://binbug.bigbrother-matrix.ru/teamcity/viewLog.html?buildId=2088&buildTypeId=ReOpenLDAP_Devel&guest=1) is now running


Could you tell me the change help you?


there is an `unpacked_dir` keyword argument for `Binaries` providers which may make this cleaner


Thank you ;)


Why is there no english version saying organ theft?


Hmmm, interesting


@hadley: The reason for the RPostgreSQL regression is:

- A show() method is defined and tested in RPostgreSQL
- The default implementation is called because of S4 rules
- RPostgreSQL doesn't define isValid(), the default implementation throws an error

This was the easiest "solution" I could think of, another option is to remove show() altogether.


**SUCCESS** - TeamCity HotRod C# Client :: Pull requests monitor - WIN_S2012 [Build 148](http://ci.infinispan.org/viewLog.html?buildId=39355&buildTypeId=HotRodCSharp_PullRequestsMonitorWinS2012&guest=1) for a6ac7bfd1d92d38291c5977d05bf03680913422a
Tests: 0, 0 failed (0 new), 0 ignored. Build time: 00:14:19


You should set top on the ribbon-box.


Same here.


Report: MinetestForFun/server-minetestforfun-skyblock#109


@Felix2
> \<Original>Organ Theft\</Original>


initSelect2Open is not a proper name, it should be initS2Open I think.


This all looks really good. Nice job @aw3s0me !


I'm not sure this is the correct value to use based on the requirements. Did you test that this does what you need it to do?


Keep up the good work.


Ok cool. I guess some advance effects will be broken but at least it is still usable.


I'm moving today, so it will be a few days before I get back to working on this. Look at punchcard.jl, I just went through this. Points=true should do it on scales

> On May 5, 2016, at 6:38 AM, Shashi Gowda <notifications@github.com> wrote:
>
> So I'm trying this out, but yc does not align things right at the tick / grid line. y also does not.
>
>
>
> I can set a suitable offset and correct it, but then it breaks when I change the height of the plot. Know how to fix this? note that y scale is ordinal...
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly or view it on GitHub
>


Obrigado por abrir o Request amigo.


Angular is a peerDependency of PrimeNG not a dependency.


Latest English,Hindi,Animation Movie,Tv Show Download For PC Laptop. http://www.moviestimehd.com/ ultimate source From movies,trailers and everything you need to download


I can't find it in the string table


note that this only exists as a tag and has not been pushed to your master branch


Protože identifikátory mohou obsahovat mezery a ty mohou být escapovány backslashem :).


Causes the following error:

=============================================================================== FAILURES ================================================================================
________________________________________________________________ pyflakes-check(ignoring ImportStarUsed) ________________________________________________________________
/home/tomer/dev/flask-security/.eggs/pytest_flakes-1.0.1-py3.5.egg/pytest_flakes.py:78: in runtest
    found_errors, out = check_file(self.fspath, self.flakesignore)
/home/tomer/dev/flask-security/.eggs/pytest_flakes-1.0.1-py3.5.egg/pytest_flakes.py:156: in check_file
    w = Checker(tree, filename)
.eggs/pyflakes-1.2.0-py3.5.egg/pyflakes/checker.py:402: in __init__
    self.handleChildren(tree)
.eggs/pyflakes-1.2.0-py3.5.egg/pyflakes/checker.py:724: in handleChildren
    self.handleNode(node, tree)
.eggs/pyflakes-1.2.0-py3.5.egg/pyflakes/checker.py:771: in handleNode
    handler(node)
.eggs/pyflakes-1.2.0-py3.5.egg/pyflakes/checker.py:1150: in IMPORTFROM
    node.module, alias.name)
.eggs/pyflakes-1.2.0-py3.5.egg/pyflakes/checker.py:198: in __init__
    full_name = module + '.' + self.real_name
E   TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: stopping after 1 failures !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
================================================================== 1 failed, 12 passed in 0.89 seconds ==================================================================


Here's a 85x66 Stunky touched up on to not be as flawed ![stunky](https://cloud.githubusercontent.com/assets/10423892/15042241/a5d01c56-12c2-11e6-8b22-8c75d8a6c0fa.gif)

@Zarel upload and revert pls? :(


Ех, пойти шоль допилить полнофункциональные телефоны с набором номера?


@stuwph: Please clarify what is "exception error". We compile SF with C++ exceptions disabled, so I doubt it's an exception. Are you talking about an assert (debug compile) ? A segmentation fault ?


> auto p = "bin" ~ dirSeparator ~ name ~ ".o";
auto p = new string("bin", dirSeparator, name, ".o");

I think this is superior even for D strings. (Not sure if calling it `concat` vs. ctor is better). Perhaps we shouldn't have `~`. `~=` is more justifiable, but it's unusual to use tilde syntax (I know `+=` can conflict though). `thing.append(foo)` might be good enough.


It's not clear enough. I'd suggest to remove it, as this is so unlikely to happen.


Но командный никак не сливается с инжами, там светложелтый и ЯРКООРАНЖЕВЫЙ.


@mcostalba: No problem here. 5-men only though.


I found it now. I was searching on this page but it wasn't the whole file apparently. Sorry


Exactly, all the shebangs are going to be in requires. No need to install.


extInt_issue5126 (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2196 of 2208 tests passed, 465 test warnings)

 * 477 tests had: AUD diffs.
 * 7 tests had: EIO diffs.
 * 4 tests had: ESO big diffs.
 * 2 tests had: MDD diffs.
 * 2 tests had: MTD diffs.
 * 3 tests had: MTR big diffs.
 * 1 test had: SSZ big diffs.
 * 1 test had: ZSZ big diffs.
 * 11 tests had: Table big diffs.
 * 1 test had: RDD diffs.
 * 3 tests had: ESO small diffs.
 * 2 tests had: Table small diffs.

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


> One thing that my version does over yours is that String is only the size of size_t

I have an idea you might like about how to efficiently convert between your string and poppable strings, no time today but will post in the next few days.


It's playable now on basic BUA, where a it was completely black on some games before. There are still noticable issues, but so far nothing gamebreaking.


system environment


Aby program był sprytniejszy dodałbym jeszcze taki fragment:

```
                    # print('3', repr(a_fs))
                    # print('4', repr(a_s))
                    a_fsrt = ''.join(sorted(set(a_fs.lower()))).strip()
                    a_srt = ''.join(sorted(set(a_s.lower()))).strip()
                    # print('5', repr(a_fsrt))
                    # print('6', repr(a_srt))
                    if author == author_f:
                        return book_url
                        break
                    elif a_s == a_fs:
                        return book_url
                        break
                    elif a_srt == a_fsrt:
                        return book_url
                        break

```
Dlaczego?
Otóż jest opcja w programie calibre, która pozwala użyć pola author sort jako autora i wtedy w nagłówkach plików MOBI pojawia się zapis w formie "Nazwisko, Imię". Dzięki temu czytnik poprawnie sortuje według nazwisk autorów.

Proponowany sposób działa w niecodzienny sposób -- sortuje litery w imieniu i nazwisku i takie właśnie porównuje. Sprawdziłem to przed chwilą i dzięki temu potrafi rozpoznać więcej książek na LC.
Oczywiście można ten sposób dopracować w wolnej chwili.


create game veikia?


+1. Download pre-compiled binary of rpy2 package for proper Windows version + python version (http://www.lfd.uci.edu/~gohlke/pythonlibs/)


@davidfestal @bjansen WDYT of this change? David, do you think there is a better way to detect that the document has not changed since we last typechecked the file?


Вы же после этого сменили токен, да?


output will never be null

also mojangapi returns nothing when the name is not premium. (note the isEmpty method)

output will either be the data we need (substring 7 39 is uuid with fixed lenght 32) or it will be empty string (check readURL method )


Shouldn't need to specify the path to `json-sass` to run it, node will automatically search `node_modules` for you to find it.


Hum, I know AMD isn't fast but BUA on medium might yield better result.


Thanks, I haven't tried it, composer gave me errors as both packages require non-dev version and that causes conflict. But it does same thing as my version, so it has to do the job.
Thanks for the modification!


xx


Nejspíš jo. Upravíme, až budete mít hotovo i svoje :).


**SUCCESS** - TeamCity HotRod C# Client :: Pull requests monitor - WIN_S2012 [Build 149](http://ci.infinispan.org/viewLog.html?buildId=39356&buildTypeId=HotRodCSharp_PullRequestsMonitorWinS2012&guest=1) for a6ac7bfd1d92d38291c5977d05bf03680913422a
Tests: 0, 0 failed (0 new), 0 ignored. Build time: 00:14:15


May want to mention that this needs to be run whenever changes are made to the JSON file.


You don't add it there ...you need to keep ota_conf file in RR folder ....nowhere else ....root of RR folder


> To allow attack rule using classname.

What does it mean? Provide more info or example please.


Hello, I'm afraid with this change variadic_func() is missing its 2nd parameter, because you shifted positional parameters after initializing arg1. Therefore arg2 should receive "$1", not "$2".


Cierra la Issue #7


extInt_issue5126 (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


> catch (FileNotFoundException | IOException ex) {
>     ....
> }

The

>  dos.close();

 should be in a finally block...


> Hum, I know AMD isn't fast but BUA on medium might yield better result.

Not on the few games I tried. The broken graphics that remained were only gone at Ultra.


oh ok


I would drop '\\.'. AFAIK, smth like "abc@xyz" is a perfectly valid email.


lúc comment nên đề luôn bản dịch của tác giả vào để dễ so sánh chứ ko nhớ đc đâu =))


这是我的 git 团队测试项目


`Gem::Licenses` is actually part of dblock/gem-licenses and not intrinsic to the rubygems gem. I just found this out from some testing and googling because I was hoping to use it myself.


angularJS 完整的案例 包含路由器，无限滚动调用接口， 分页插件，上传文件插件，自定义指令，自定义过滤器......


[Done](https://github.com/freeorion/freeorion/commit/911b86ca24581fc3904590a9157432bf84203e04), works fine, thx.


I tried removing it but then it isn't copied to the Output file which is where I've been running FreePIE after building it with build_installer.bat. If it's okay I'll leave it in for now.


One thing: I would appreciate if you could split this in commits per module in the future. This makes merging branches way easier for git.


xem xét về  -> xem xét
which has not yet released -> chưa tung ra (chủ động)
Pragmatism -> chủ nghĩa thực dụng
led to choosing a Linux system -> dẫn tới việc lựa chọn một hệ thống Linux
have many positive consequences -> thiếu này
it is easier blabla -> người ta sẽ dễ dàng tìm được (viết như này đọc thuận hơn vì có chủ ngữ)


Fritz15 gui says "SF caused an exception.This is a problem in the engine", in Arena similar

did some test with mixed positions e.g. 7 white against black king, or 6 black against 2 white ones, on different squares ...
doesn't depend on what kind of pieces or position, but on 8 or more on the board


Nossa, passou despercebido isso, valeu ;)


Regarding

````
New elements had to have matched to get a nil.
````
this is right-retract, so it could logically be a retraction of everything that had been propagated before.

Regarding the nil propagation, perhaps just changing that now instead of preserving all existing behavior is the way to go here.  I'll put a comment on the issue about it.


These architectures -> Những kiến trúc này chứ
especially for a firewall -> đặc biệt là đối với tường lửa


That's actually a pedestrian detector, based on sliding window method. Function "train_detector" extracts pedestrian figures from a training set of images, then extracts backgroung patches (patches that don't intersect with pedestrians), trains SVM method on this set of examples, then retrains te algorithm using bootstrapping technique. Function "detect" detects pedestrians in a new image.


Brady,

Do we need to create a new code type for that? Those are concept codes which come under HL7 data set. If code type is mandatory then we can add.


>Beta builds need to be **postfixed** with `-SNAPSHOT`.


Completes #25


The `setCompass` & co. methods has been removed, [`Toggles`](https://ci.pgmann.cf/job/SpectatorPlus/javadoc/index.html?com/pgcraft/spectatorplus/Toggles.html) must be used instead.


chuyển đổi qua -> chuyển đổi sang nhé =)) (qua là thông qua 1 cái gì đấy)
small business -> doanh nghiệp nhỏ
For starters -> Để bắt đầu =)) (nó giống như Firstly ấy)


Err, I've added `#include <iostream>`at the top and `std::cout << Bitboards::pretty(attacks2);` to debug `attacks2`, and it seems to work with my version using the precomputed DiagonalPinningMask array. Here is a test session with your position:
````
position fen 4r2k/7b/2b1P1P1/3P4/1rP1K3/5P2/4P1b1/4r3 w - - 1 23
eval
+---+---+---+---+---+---+---+---+
|   |   |   |   |   |   |   |   |
+---+---+---+---+---+---+---+---+
|   |   |   |   |   |   |   | X |
+---+---+---+---+---+---+---+---+
|   |   | X |   |   |   |   |   |
+---+---+---+---+---+---+---+---+
|   |   |   |   |   |   |   |   |
+---+---+---+---+---+---+---+---+
|   |   |   |   |   |   |   |   |
+---+---+---+---+---+---+---+---+
|   |   |   |   |   |   |   |   |
+---+---+---+---+---+---+---+---+
|   |   |   |   |   |   |   |   |
+---+---+---+---+---+---+---+---+
|   |   |   |   |   |   |   |   |
+---+---+---+---+---+---+---+---+
````


`output` can be null under bad network.


valeu jovem !


👍 thanks @springmeyer!


1). Good point, I'll change the comments.

2) Those are the existing bindings. https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/engine.cljc#L772
This makes sense to me; the result binding should be bound to the initial value.  I'm not sure why you think the map should be empty.  It does raise an interesting question of how this currently works when there is no result binding.

I do think there should a minor change here though; we should be retracting the converted initial value. https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/engine.cljc#L673


Richard, do you think `2.1` is ready to be uploaded on Hackage?


This could be really awesome combined with the calendar sensor I just submitted. Pull the origin from device_tracker and the destination from the calendar sensor and figure out if we need to trigger an automation based on the start_time of the calendar sensor.

Would love to work something out with you to get that ability.


**Stockfish 040516 64 BMI2 by T. Romstad, M. Costalba, J. Kiiski, G. Linscott
setoption name SyzygyPath value F:/SY6
info string Found 510 tablebases
position fen 4k3/3ppp2/8/8/8/8/3PPP2/4K3 w - -
go infinite**
info depth 1 seldepth 1 multipv 1 score cp -4 nodes 9 nps 4500 tbhits 0 time 2 pv d2d3
info depth 2 seldepth 2 multipv 1 score cp 7 nodes 30 nps 15000 tbhits 0 time 2 pv d2d3 d7d6
info depth 3 seldepth 3 multipv 1 score cp -6 nodes 118 nps 59000 tbhits 0 time 2 pv d2d4 d7d6 e2e3
info depth 4 seldepth 4 multipv 1 score cp 12 nodes 160 nps 53333 tbhits 0 time 3 pv d2d4 d7d6 e2e3 e7e6
info depth 5 seldepth 5 multipv 1 score cp -1 nodes 632 nps 210666 tbhits 0 time 3 pv f2f3 f7f6 e1f2 e8f7 d2d3
info depth 6 seldepth 6 multipv 1 score cp 7 nodes 867 nps 289000 tbhits 0 time 3 pv f2f3 f7f6 e1f2 e8f7 d2d3 d7d6
info depth 7 seldepth 7 multipv 1 score cp -3 nodes 1507 nps 376750 tbhits 0 time 4 pv f2f3 f7f6 e1f2 e8f7 f2e3 d7d6 d2d3
info depth 8 seldepth 8 multipv 1 score cp 6 nodes 3513 nps 501857 tbhits 4 time 7 pv f2f3 d7d5 d2d3 d5d4 e1d2 e8d7 d2c2 d7e6
info depth 9 seldepth 10 multipv 1 score cp -4 nodes 18465 nps 1231000 tbhits 90 time 15 pv d2d4 e7e6 e1d2 e8e7 e2e4 d7d6 d2e2 e7f6 e2e3
info depth 10 seldepth 11 multipv 1 score cp 0 nodes 32616 nps 1553142 tbhits 257 time 21 pv d2d4 f7f6 e2e3 e7e5 d4e5 f6e5
info depth 11 seldepth 12 multipv 1 score cp -1 nodes 66521 nps 1956500 tbhits 700 time 34 pv e2e4 f7f6 e1e2 e7e6 e2e3 e8e7 d2d3 e7d6 f2f4 d6c6 f4f5
info depth 12 seldepth 13 multipv 1 score cp 0 nodes 71994 nps 1945783 tbhits 844 time 37 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 13 seldepth 14 multipv 1 score cp 0 nodes 84248 nps 2005904 tbhits 1120 time 42 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 14 seldepth 14 multipv 1 score cp 0 nodes 113316 nps 2098444 tbhits 1556 time 54 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 15 seldepth 14 multipv 1 score cp 0 nodes 156041 nps 2197760 tbhits 2520 time 71 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 16 seldepth 14 multipv 1 score cp 0 nodes 195468 nps 2272883 tbhits 3578 time 86 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 17 seldepth 14 multipv 1 score cp 0 nodes 241881 nps 2348359 tbhits 4830 time 103 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 18 seldepth 14 multipv 1 score cp 0 nodes 308084 nps 2425858 tbhits 6823 time 127 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 19 seldepth 14 multipv 1 score cp 0 nodes 407031 nps 2481896 tbhits 9521 time 164 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 20 seldepth 14 multipv 1 score cp 0 nodes 502987 nps 2527572 tbhits 13087 time 199 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 21 seldepth 14 multipv 1 score cp 0 nodes 665224 nps 2598531 tbhits 17812 time 256 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 22 seldepth 14 multipv 1 score cp 0 nodes 904707 nps 2862996 tbhits 25994 time 316 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 23 seldepth 14 multipv 1 score cp 0 nodes 1176760 nps 3104907 tbhits 34877 time 379 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 24 seldepth 14 multipv 1 score cp 0 nodes 1504877 nps 3314707 tbhits 46743 time 454 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 25 seldepth 14 multipv 1 score cp 0 nodes 2048138 nps 3555795 tbhits 63739 time 576 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 26 seldepth 14 multipv 1 score cp 0 nodes 2536836 nps 3703410 tbhits 80487 time 685 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 27 seldepth 14 multipv 1 score cp 0 nodes 3267502 nps 3848647 tbhits 104683 time 849 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4
info depth 28 seldepth 14 multipv 1 score cp 0 nodes 4217074 nps 3989663 hashfull 651 tbhits 134635 time 1057 pv e2e4 f7f6 e1e2 e7e5 e2e3 e8e7 d2d4 e5d4 e3d4

-> engine freeze  and windows throwing exception error


- Get the form data (meats, drinks, others and quantity of people).
- Calculate the total quantity of meats, drinks and others
 - Man 450g meat, 1,5L drink, 1 garlic bread
 - Woman 400g meat, 1L drink, 1 garlic bread
 - Children 200g meat, 500mL drink, 1 garlic bread
- Create the calcBarbecue, the main function to calculate the barbecue quantity


This field in demographics was already existing as a single textbox entry. So we retained it. We have only moved the field from Contact to Guardian Name group


Drop the response from this function in a gist and I can take look if you want to.


Hey @juandazapata I'm not sure if we should keep in the source code the rvm role code. I know the possibilities. Please see this discussion: https://github.com/spireworks/spire-ansible/pull/10/files/2e3d6c1475223e1d9466183622e87778f122fd48#r58075728 . I agree that versioning is the best to control and also to see the diff of the vendor role.


```java
SpectateAPI spAPI = SpectateAPI.getAPI();
// or
SpectateAPI.getAPI().setSpectating(player, true);
```


@gavinking :  seems good to me.


@andela-gkuti - create more sections for the content of your README file.


@batusai513

Move `store` into `index.js` and pass it as a prop so it doesn’t get created on every HMR update.


Because, this role is only for testing purpose. When we include this ansible-nginx-passenger role inside another repo, it will  include all the code for the rvm again.


Use `°C` to get the degree in front of the C


Since it’s only useful in development, I don’t think so.


distributions or systems -> những bản phân phối hoặc hệ thống
important contributions -> những đóng góp quan trọng (số nhiều)
recognize -> công nhận (ko phải nhận biết đâu =)) )
principles of freedom upon which they are founded -> những nguyên tắc về tự do mà dựa trên đó chúng (GNU/Linux) được xây dựng


This is fixed as of commit 29cacd1
<https://github.com/DSLsofMath/BScProj/commit/29cacd1c3de59a248b5bb8d1c12ad53f936c2d62>
.

On Thu, May 5, 2016 at 12:13 PM Rembane <notifications@github.com> wrote:

> Or the even nicer ones from amsmath, which let you control your equations
> in even nicer ways.
>
> https://www.sharelatex.com/learn/Aligning_equations_with_amsmath
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub
> <https://github.com/DSLsofMath/BScProj/commit/f68f297a4763b9ef462694cd8cc5b60155d965ba#commitcomment-17364732>
>


According to the mockup, the status should be in capitals


I can't handle this


It seem not work. Because of dnsmasq config(https://github.com/Pillar1989/wifidog-server/blob/BBGW/conf/SoftAp0) ,whatever any website you visit, you will be redirect to 127.0.0.1.SoftAp0 is only used to configure WiFi. If you want to make router, connman tether is a better chose.


has chosen to follow -> quyết định làm theo


Sweet!


@timler I find this name a bit confusing. Should the "COMPONENT_BATCH" part not be "COMPONENTS"? And donation batches should be plural.


text


proprietary -> bản quyền chứ nhỉ (phần mềm bản quyền)


should it not be:
`(Session.Character.Level >= 20 ? Language.Instance.GetMessageFromKey("ASK_REVIVE")` ?


OK, my mistake, I missed the `~` when I read
`DiagonalPinningMask[s1] = PseudoAttacks[BISHOP][s1] & ~StepAttacksBB[KING][s1];`

(Note to self: please stop reviewing tests before your morning coffee)

One caveat of those pinned pawns attempt:
Even if c4 is pinned, Rb4 should not move to b5.
And a Rd7 should not move to e7 or c7.

So for mobility area for example, possibly it will help if we keep the original pawn attacks.
`Bitboard mobilityArea[]...`


ghhhh


the possession or acquisition of an item -> sở hữu hoặc thu hồi/mua lại một mặt hàng
initial choice -> lựa chọn ban đầu


The heading should be "Receive Components" and it is missing the tabs from the mockups.


extInt_issue5126 (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1062 of 1062 tests passed, 0 test warnings)

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


Why 31? Boolean.hashCode() returns 1231 or 1237, so some smaller prime should work fine.


Acredito que daqui há um ano será a solução ideal 👍


I do not like the name DEFAULT. I guess OTHER or UNDEFINED will do better here (as it is not a default value for something, it is a token that doesn't fit to the classification below).


it is easy to manipulate it -> dễ dàng để vận dụng nó


hm, seems like there's a larger issue with node-sqlite and node6: https://travis-ci.org/mapbox/tile-reduce/jobs/128036165


Thanks


Even when you work with internal functions, it is basically a bad idea to use mutable arguments, as they make the code harder to follow.


qeqe


Nice!


Possible improvements:
add ability to provide Properties values via arguments.
add method which will return attribute, so can be overridden for cases like "tags"


Line 1


Hello


but you didn't have it in any of your files .. neither `DrawSpriteSystem.hx` not `DrawColourSystem.hx` had it !!


Is this a replacement change or an addition? i.e. can we still use `/` or is it only `.` now?


We have CVX codes as 03, 09 etc. When we save this to integer field, it as saved as 3 and 9. That is the reason we converted it to varchar.


sure .. as I told you before I was planning on finishing the functionality first then adding the tests. instead of having to modify the tests multiple times.


growing small business -> doanh nghiệp nhỏ đang phát triển (sao lại tiến triển =)) )
what's in store -> những điều sẽ xảy đến (idiom)


it's write on the PR, this is breaking change free. So you can still use the old method.

On 5 May 2016 at 14:18:57, Dan Gamble (notifications@github.com(mailto:notifications@github.com)) wrote:

>
>
> Is this a replacement change or an addition? i.e. can we still use / or is it only . now?
>
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub(https://github.com/adonisjs/adonis-framework/commit/58532ed52e8f77461b8be1f604278e11ef11ad70#commitcomment-17365602)
>
>
>
>
>


can you elaborate ?


I couldn't know what `Binaries` provider does. Are you aware of any documentation for it, or any packages that can be an example for me?


envisioned -> hình dung (mường tượng nghe cổ quá =)) )
case study -> tình huống/ví dụ thực tiễn
medium sized company -> công ty cỡ vừa


These values different from page to page. For example in `Middleware Deployments Summary` page, we have `Name` and `Nativeid`


Aktuell wurde die Nightly bereits mit dem neuen Stand der Master abgeglichen und demnächst sollte es auch die erste Beta für 2.2.1 geben ;)

So gesehen ist es auch aus dieser Sicht nicht mehr nötig!


**UNKNOWN** - TeamCity HotRod C# Client :: Pull requests monitor - WIN_S2012 [Build 150](http://ci.infinispan.org/viewLog.html?buildId=39359&buildTypeId=HotRodCSharp_PullRequestsMonitorWinS2012&guest=1) for a6ac7bfd1d92d38291c5977d05bf03680913422a
Tests: 0, 0 failed (0 new), 0 ignored. Build time: 00:00:07

Process exited with code 1


administrative office -> văn phòng hành chính

Đoạn sau sao m không dịch?


this is the oposite so it's not a fix XD


Expected README.md to change with this commit


Awesome, nice change then. I remember trying to do this somewhere before in the template and it didn't work :)


yes it should be... so i don't know why it was changed XD


omg... what is this colon syntax?! is it even documented anywhere?


Hab es geändert weil es bei der Suche über GlobalSearch anhand der Site-ID sortiert wird.
Somit wird die falsche Domain auch angezeigt, wenn das nicht wäre würde es mich auch nicht interessieren!


**FAILURE** - TeamCity HotRod C# Client :: Pull requests monitor - WIN_S2012 [Build 151](http://ci.infinispan.org/viewLog.html?buildId=39360&buildTypeId=HotRodCSharp_PullRequestsMonitorWinS2012&guest=1) for a6ac7bfd1d92d38291c5977d05bf03680913422a
Tests: 0, 0 failed (0 new), 0 ignored. Build time: 00:01:09

Process exited with code 255


@tkelman Do you think it is a good idea to use URL such as: https://github.com/chkwon/PathJulia/raw/0.0.7/lib/osx/libpath47julia.dylib? Instead of https://github.com/chkwon/PathJulia/archive/0.0.7.tar.gz, then unpack?


yes, as I mentioned in my comment https://github.com/jkandasa/cfme_tests/commit/0c3099a5c2d489985dff6f089db63da9b99e2bd2#commitcomment-17364303
we need to extend all classes from this provider, and these properties will have their own values for each subclass


modifie！写错字了！TAT


Hi, very interesting. maybe it would be nicer to have it in a separate attribute handler, one designed for a specific attribute.
It can be done declaring the following method in a Magmi_Item_Processor plugin:

  public function initialize($params)
    {
....
 $this->register_attribute_handler($this,'attribute_code:vendor');
....
}

then declare the following method in your processor

public function handleVendorAttribute(e($pid, &$item, $storeid, $attrcode, $attrdesc, $ivalue)
{
// do your vendor attribute specific code here.

}

and it should override the default behaviour for attribute you want.


That was in your test right? I saw that when I added tests for clearing the AltField.

I thought that your approach was rather interesting, you ran all operations against that hidden field including test assertions and the hidden field was never actually inserted into the DOM.

I also noticed something interesting about your style of jQuery programming...

You do this,

$(ElementId)

instead of...

$("#ElementId")

Which I had no idea even worked. It's interesting that it does and I see why now, but I have never seen either of these approaches before so I enjoyed reading your code, working in it, and learning from it!


I suspect the Binaries provider will work better with tarballs than directly downloading library files, but I could be wrong. Probably not a huge difference in size? Check GLPK.jl as an example that uses the Binaries provider.


cool, I understand now. You can add `('type', 'Type')` in HawkularProvider.property_tuples


It should be "folders" in the commitmessage of course.


Issue is there is no check for null. Check for null & get context from activity.


@jensens Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.autoform/15/violations
```
plone/autoform/base.py:32:1: C901 'AutoFields.updateFieldsFromSchemata' is too complex (11)
plone/autoform/base.py:161:1: C901 'AutoFields._calculate_field_moves' is too complex (11)
plone/autoform/directives.py:123:31: S001 found %s formatter
plone/autoform/supermodel.py:53:26: S001 found %s formatter
plone/autoform/supermodel.py:64:17: S001 found % formatter
plone/autoform/supermodel.py:71:1: C901 'FormSchema.read' is too complex (11)
plone/autoform/supermodel.py:106:67: S001 found %s formatter
plone/autoform/supermodel.py:111:1: C901 'FormSchema.write' is too complex (14)
plone/autoform/supermodel.py:145:26: S001 found %s formatter
plone/autoform/supermodel.py:153:26: S001 found %s formatter
plone/autoform/utils.py:192:1: C901 'processFields' is too complex (13)
plone/autoform/widgets.py:70:17: S001 found %s formatter
plone/autoform/tests/test_supermodel_handler.py:41:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:42:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:44:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:44:52: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:45:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:45:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:46:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:46:54: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:48:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:49:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:84:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:85:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:87:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:87:53: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:88:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:88:56: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:89:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:89:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:92:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:92:53: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:93:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:93:56: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:138:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:139:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:142:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:143:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:148:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:149:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:150:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:153:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:154:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:155:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:246:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:247:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:247:52: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:248:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:248:54: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:250:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:251:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:272:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:273:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:274:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:274:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:275:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:286:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:287:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:288:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:289:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:317:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:318:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:321:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:322:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:326:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:327:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:328:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:331:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:332:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:333:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:418:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:418:63: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:419:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:419:64: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:461:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:462:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:465:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:466:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:482:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:486:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:500:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:504:31: Q000 Remove bad quotes.
plone/autoform/tests/test_utils.py:23:23: Q000 Remove bad quotes.
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


This is the only change between v1.7.1 and 1.7.2b1


Consider replacing the cp 50 percent's and cp 75 percent with different bit tests of the same random byte (just grab hRandomAdd the second and third time), and calling RandomSub at line 150, for better random results.


Yes, but now AppContainer is "rendered" in the production environment. It needs react-hot-loader to know to fall through, no?


Questo file non doveva stare su github era uno dei miei esperimenti su un modo per non rendere visibili le credenziali ma non funzionava ora ho pensato un nuovo medoto ho pensato di metterle in un file json cosa ne pensi?
Ah nel frattempo ho creato un nuovo branch dove ho messo la nuova versione del bot https://github.com/emanuelecesari/mrBot/tree/developement


@hhovsepy +1 for tags


@ShadowCoder69

Thanks, Ravi :grin:

Sorry I haven't been in lately, it's been really busy :( Hopefully tomorrow night I'll be able to keep going


generally the URL here should point to PyPI, because it may be used to scan for downloads.


1. Download zipped project;
2. Under CreditCardNumberValidator/Kottans_CreditCardOperator/Kottans_CreditCardOperator/bin/Debug/ find .exe file;
3. Start Kottans_CreditCardOperator.exe => you'll have a cmd opened;
4. Just follow the commands in the console and good luck :)


TeamCity Tests Backend :: Build [Build 0.0.0.15](http://pc-kuld.edu.isd.dp.ua:8010/viewLog.html?buildId=213&buildTypeId=TestsBackend_Build) is now running


TeamCity Tests Backend :: Build [Build 0.0.0.15](http://pc-kuld.edu.isd.dp.ua:8010/viewLog.html?buildId=213&buildTypeId=TestsBackend_Build) outcome was **FAILURE**
Summary: Cannot start build runner Build time: 00:00:08


@tkelman So then, using `unpacked_dir`, it will tell `julia` that the location of library files is  `C:\Users\chkwon\.julia\v0.4\GLPK\deps\glpk-4.52\w64`, for example? I found that it does not copy library files to `\desp\usr\lib`, etc. Just unpacked.


TeamCity Tests Backend :: Build [Build 0.0.0.16](http://pc-kuld.edu.isd.dp.ua:8010/viewLog.html?buildId=214&buildTypeId=TestsBackend_Build) is now running


TeamCity Tests Backend :: Build [Build 0.0.0.16](http://pc-kuld.edu.isd.dp.ua:8010/viewLog.html?buildId=214&buildTypeId=TestsBackend_Build) outcome was **FAILURE**
Summary: Cannot start build runner Build time: 00:00:02


My apologies... I've uploaded the new version to pypi.python.org.


@marcel1981 podrias pasarme el ejemplo.


It's holiday here now :smile:  (well it is already for a week but I wasn't able to clone IE cause of I only had access to my laptop and cloning and setting up forge mods isn't really setup there)


Also, I think the line 267 should be replaced with:
loss = log_loss(np.expand_dims(self.y_true_holdout, 0), np.expand_dims(y_pred_holdout_proba, 0))
Otherwise, I get the following error:

2016-05-05 14:17:13,555 INFO     [hyperopt.fmin/fmin:189]: job exception: 'axis' entry is out of bounds
Traceback (most recent call last):
  File "/home/leonid/Programs/vowpal_wabbit/utl/vw-hyperopt.py", line 380, in <module>
    main()
  File "/home/leonid/Programs/vowpal_wabbit/utl/vw-hyperopt.py", line 374, in main
    h.hyperopt_search()
  File "/home/leonid/Programs/vowpal_wabbit/utl/vw-hyperopt.py", line 322, in hyperopt_search
    best_params = fmin(objective, space=self.space, trials=self.trials, algo=algo, max_evals=self.max_evals)
  File "/usr/local/lib/python2.7/dist-packages/hyperopt/fmin.py", line 334, in fmin
    rval.exhaust()
  File "/usr/local/lib/python2.7/dist-packages/hyperopt/fmin.py", line 294, in exhaust
    self.run(self.max_evals - n_done, block_until_done=self.async)
  File "/usr/local/lib/python2.7/dist-packages/hyperopt/fmin.py", line 268, in run
    self.serial_evaluate()
  File "/usr/local/lib/python2.7/dist-packages/hyperopt/fmin.py", line 187, in serial_evaluate
    result = self.domain.evaluate(spec, ctrl)
  File "/usr/local/lib/python2.7/dist-packages/hyperopt/fmin.py", line 114, in evaluate
    rval = self.fn(pyll_rval)
  File "/home/leonid/Programs/vowpal_wabbit/utl/vw-hyperopt.py", line 298, in objective
    loss = self.validation_metric_vw()
  File "/home/leonid/Programs/vowpal_wabbit/utl/vw-hyperopt.py", line 271, in validation_metric_vw
    loss = log_loss(self.y_true_holdout, y_pred_holdout_proba)
  File "/usr/lib/python2.7/dist-packages/sklearn/metrics/metrics.py", line 2256, in log_loss
    Y /= Y.sum(axis=1)[:, np.newaxis]
  File "/usr/lib/python2.7/dist-packages/numpy/core/_methods.py", line 25, in _sum
    out=out, keepdims=keepdims)
ValueError: 'axis' entry is out of bounds


viết thêm bản dịch vào thì dài quá, thôi để như này sau nhìn bản gốc mà so cũng được =))


You don't necessarily need to copy the library files anywhere as long as you refer to the library location by the absolute path that gets saved in the `deps.jl` file. It's also customary on windows to put dll's in `bin` rather than `lib`.


Why using string concat where there is already usage of `spritf()`?


@tkelman Great! Thanks. I'll make changes and release with the next version update.


アイテムがなくなったら自動攻撃 #793


Commit message is incorrect, it's start not install.


**SUCCESS** - TeamCity HotRod C# Client :: Pull requests monitor - WIN_S2012 [Build 152](http://ci.infinispan.org/viewLog.html?buildId=39363&buildTypeId=HotRodCSharp_PullRequestsMonitorWinS2012&guest=1) for a6ac7bfd1d92d38291c5977d05bf03680913422a
Tests: 0, 0 failed (0 new), 0 ignored. Build time: 00:14:25


TeamCity Mobile :: Android :: Android SDK (develop) [Build 468](http://teamcity.hq.judo/viewLog.html?buildId=27314&buildTypeId=JudoAndroid_AndroidGradle) is now running


TeamCity ReOpenLDAP :: devel [Build 255](https://binbug.bigbrother-matrix.ru/teamcity/viewLog.html?buildId=2088&buildTypeId=ReOpenLDAP_Devel&guest=1) outcome was **SUCCESS**
Summary: Tests passed Build time: 01:53:21


'cause I never use sprintf and didn't even notice it was there :)


>>> version="12.345"
>>> '.'.join([c for c in version if c.isdigit()])
'1.2.3.4.5'

Is this what you intended to do?


I'm a bit confused, you moved the `defer db.Close()` to before any work is being done on the db. Did I misunderstand the meaning of this command? Is it not closing the db connection?


#LinuxFTW


Why was the Delay decreased?


mmmmmmmb ，不小心点错了提交，还没写完呢，也可以本地生成随机数


i pushed it now


Looks good Carter!


@eltang uh, I'm not your tester. :)

If you want to put this into a proper keymap, submit it into a pull request with the compiled hex file, I can try it out quickly (will take me some time to get to it). But "are you too busy to test this or something" is pretty hilarious.


Never mind, I just realized what `defer` means :)


IMO such logical operators (`or` + `and`) should be replaced throughout whole codebase to avoid moar of such bugz.


Какое-то замечание


It wasn't the source for the bug. But you are right. We are going to replace them step by step.


I clicked "revert" but didn't complete it because it seems to break CentOS tests, ironically.


Can you tag this commit with 2.2.1? That makes package it easier.


@thet Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.autoform/16/violations
```
plone/autoform/base.py:32:1: C901 'AutoFields.updateFieldsFromSchemata' is too complex (11)
plone/autoform/base.py:161:1: C901 'AutoFields._calculate_field_moves' is too complex (11)
plone/autoform/directives.py:123:31: S001 found %s formatter
plone/autoform/supermodel.py:53:26: S001 found %s formatter
plone/autoform/supermodel.py:64:17: S001 found % formatter
plone/autoform/supermodel.py:71:1: C901 'FormSchema.read' is too complex (11)
plone/autoform/supermodel.py:106:67: S001 found %s formatter
plone/autoform/supermodel.py:111:1: C901 'FormSchema.write' is too complex (14)
plone/autoform/supermodel.py:145:26: S001 found %s formatter
plone/autoform/supermodel.py:153:26: S001 found %s formatter
plone/autoform/utils.py:120:1: C901 'processFields' is too complex (19)
plone/autoform/widgets.py:70:17: S001 found %s formatter
plone/autoform/tests/test_supermodel_handler.py:41:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:42:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:44:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:44:52: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:45:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:45:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:46:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:46:54: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:48:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:49:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:84:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:85:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:87:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:87:53: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:88:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:88:56: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:89:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:89:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:92:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:92:53: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:93:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:93:56: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:138:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:139:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:142:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:143:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:148:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:149:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:150:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:153:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:154:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:155:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:246:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:247:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:247:52: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:248:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:248:54: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:250:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:251:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:272:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:273:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:274:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:274:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:275:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:286:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:287:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:288:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:289:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:317:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:318:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:321:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:322:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:326:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:327:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:328:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:331:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:332:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:333:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:418:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:418:63: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:419:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:419:64: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:461:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:462:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:465:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:466:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:482:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:486:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:500:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:504:31: Q000 Remove bad quotes.
plone/autoform/tests/test_utils.py:23:23: Q000 Remove bad quotes.
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


Ignore this commit...


@timler Did you consider adding another query for this use case which does a fetch join? That way we would reduce the number of queries that hibernate needs to do.


I've tested locally... The CentOS box I use in vagrant (bento/centos-7.1) does not have /etc/ansible...

Yet the travis docker image seems to have it already...


Is there a lib/plugin you would recommend instead?


Hi,
I'm trying to achieve the same goal and migrate spring-data-cassandra to 3.x based.
have you notice a major performance downgrade during junit execution?


This makes sense if we have to use these empty textures.  I still do not completely understand why this is needed, but if it is needed this is the fix for CubeMaps.

According to the WebGL 2 specification there are two new valid option for bindTexture in addition to gl.TEXTURE_2D and gl.TEXTURE_CUBE_MAP, so if we have to follow this pattern we'll have to extend it further for WebGL 2 with support for:

gl.TEXTURE_2D_ARRAY
gl.TEXTURE_3D

Source: https://www.khronos.org/registry/webgl/specs/latest/2.0/


Be careful! You have that falling through to printing the "no cycling allowed here" text. Replace call PrintText at L2346 with jp PrintText or add a ret after it.


yuanxing


arggggg found it

```

# Install Ansible inventory file
RUN mkdir /etc/ansible
RUN echo -e '[local]\nlocalhost ansible_connection=local' > /etc/ansible/hosts

```


@timler Would checking for a null parent component work for determining if this is an initial component? That would be clearer in my mind.


Sorry, forgot to push the tag. 0545a09 is tagged as 2.2.1.


TeamCity Tests Backend :: Build [Build 0.0.0.17](http://pc-kuld.edu.isd.dp.ua:8010/viewLog.html?buildId=215&buildTypeId=TestsBackend_Build) is now running


I experienced the same issue, currently chasing for the reason.


just curious why it is there release:prepare-with-pom and later release:prepare, they are alternatives to each other. See https://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html#Generating_release_POMs

I am also confused by multiple clean install with release:prepare* and then on standalone line.


do we have GWT compiled sources in Windup?


TeamCity Tests Backend :: Build [Build 0.0.0.17](http://pc-kuld.edu.isd.dp.ua:8010/viewLog.html?buildId=215&buildTypeId=TestsBackend_Build) outcome was **SUCCESS**
Summary: Running Build time: 00:01:28


hehe, no.


Thanks! I updated with `\text` at bf273a1e2bfdb56062fe308300edcc56a4986991 :-)


**SUCCESS** - TeamCity HotRod C# Client :: Pull requests monitor - WIN_S2012 [Build 153](http://ci.infinispan.org/viewLog.html?buildId=39364&buildTypeId=HotRodCSharp_PullRequestsMonitorWinS2012&guest=1) for a6ac7bfd1d92d38291c5977d05bf03680913422a
Tests: 0, 0 failed (0 new), 0 ignored. Build time: 00:14:23


Because of issues with building the tests. It generally has to be done twice. Really it only has to be done this way for core windup, but it doesn't seem harmful with the others either.


ok


++ thanks for fixing


@jensens Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.autoform/17/violations
```
plone/autoform/base.py:32:1: C901 'AutoFields.updateFieldsFromSchemata' is too complex (11)
plone/autoform/base.py:161:1: C901 'AutoFields._calculate_field_moves' is too complex (11)
plone/autoform/directives.py:123:31: S001 found %s formatter
plone/autoform/supermodel.py:53:26: S001 found %s formatter
plone/autoform/supermodel.py:64:17: S001 found % formatter
plone/autoform/supermodel.py:71:1: C901 'FormSchema.read' is too complex (11)
plone/autoform/supermodel.py:106:67: S001 found %s formatter
plone/autoform/supermodel.py:111:1: C901 'FormSchema.write' is too complex (14)
plone/autoform/supermodel.py:145:26: S001 found %s formatter
plone/autoform/supermodel.py:153:26: S001 found %s formatter
plone/autoform/utils.py:192:1: C901 'processFields' is too complex (13)
plone/autoform/widgets.py:70:17: S001 found %s formatter
plone/autoform/tests/test_supermodel_handler.py:41:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:42:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:44:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:44:52: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:45:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:45:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:46:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:46:54: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:48:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:49:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:84:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:85:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:87:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:87:53: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:88:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:88:56: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:89:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:89:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:92:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:92:53: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:93:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:93:56: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:138:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:139:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:142:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:143:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:148:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:149:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:150:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:153:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:154:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:155:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:246:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:247:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:247:52: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:248:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:248:54: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:250:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:251:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:272:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:273:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:274:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:274:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:275:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:286:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:287:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:288:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:289:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:317:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:318:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:321:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:322:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:326:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:327:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:328:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:331:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:332:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:333:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:418:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:418:63: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:419:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:419:64: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:461:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:462:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:465:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:466:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:482:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:486:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:500:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:504:31: Q000 Remove bad quotes.
plone/autoform/tests/test_utils.py:23:23: Q000 Remove bad quotes.
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


use case& activity diagram


I think easier to use versions plugin to adjust property version like
`mvn versions:update-property -Dproperty=version.windup -DnewVersion=$DEV`


@Olegf13
You can use e.g. `app\classes\MyRule` into textfield


The one I'm building. :grin: I'm intending on releasing an initial beta version quite soon.

Right now it's only using SAT, but eventually I will add a solver based very loosely on the code in this commit.


TeamCity Mobile :: Android :: Android SDK (develop) [Build 468](http://teamcity.hq.judo/viewLog.html?buildId=27314&buildTypeId=JudoAndroid_AndroidGradle) outcome was **FAILURE**
Summary: Execution timeout (new); tests passed: 58 Build time: 00:20:32


TeamCity Mobile :: Android :: Android SDK (develop) [Build 469](http://teamcity.hq.judo/viewLog.html?buildId=27316&buildTypeId=JudoAndroid_AndroidGradle) is now running


fixed typos in automatic email message sent to registrant awaiting confirmation on registrant change by the current registrant.


This change broke my disabled columns on stores such as host, dms, feed etc. Is there a reason in particular why it was changed?


Good idea. Feel free to send a PR. :)


I would say that url should point to github and download_url at pypi.


+1 for tags


i suppose if a download_url is given it will be used. but if not, the only url will be used as download url as well.


You broke tito auto-magical version bumping by this commit. Take a look on the man page for tito templates feature and  rel-eng/templates/version file.


Use case and activity diagrams


I'm not sure writing out 320x200 PNGs is ever the right thing to do (well, perhaps if the user has set their window size to 320x200...) but, most of this is relevant to if we move to writing out texture_upscaled (just adding some stuff in the else branch for that case) if that's what we agree we should be doing...


Though it won't change the original value of `el` when `el` is string, this function looks a little strange.

How about replacing it with:
```javascript
export function query (el) {
  let result = el
  if (typeof el === 'string') {
    result = document.querySelector(el)
    if (!result) {
      process.env.NODE_ENV !== 'production' && warn(
        'Cannot find element: ' + el
      )
    }
  }
  return result
}
```


I do not agree that Ardulink-1 is a simpler solution (line 8). Why do you think it's "simpler"? Of course the internal structure is more complex due it's more flexible but that should not affect Ardulink users. So what's the point of "simpler"?


this effectively blocks using java 7. Are we aware of that?


@T1mL3arn I wrote it is potential because by just having the window open and closing Tiled, you won't get it to crash. You have to actually make a change as well. Maybe it was a poor wording choice.


As much as I would like to fix these issues, I have spent 4 hours working
on related things last night, and I would like to concentrate on the CDR
first. The plots have been an uphill battle.

On Wed, May 4, 2016 at 10:57 PM, Warren Hoburg <notifications@github.com>
wrote:

> what happened to the time on station vs wind speed plot? it's suddenly
> constant
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub
> <https://github.com/hoburg/gpkit-models/commit/2a1576c956a10d7070aff90464a3aa193396ed06#commitcomment-17362292>
>

--
Berk Öztürk
Massachusetts Institute of Technology | Class of 2016
Department of Aeronautics and Astronautics


Je pensais que je m'occupais du back, mais bon, je viens d'écrire du code totalement doublon avec le tien du coup...


lock


A visualização é mais agradável, mas a indentação do arquivo não! 😂 😂 😂


TeamCity Mobile :: Android :: Android SDK (develop) [Build 469](http://teamcity.hq.judo/viewLog.html?buildId=27316&buildTypeId=JudoAndroid_AndroidGradle) outcome was **FAILURE**
Summary: Tests failed: 3, passed: 152, ignored: 1 Build time: 00:09:25
### Failed tests
```
com.judopay.ActivityResultTest: com.judopay.receipts.ListReceiptsTest.listCollectionReceipts: <no details avaliable>

com.judopay.ActivityResultTest: com.judopay.receipts.ListReceiptsTest.listPaymentReceipts: <no details avaliable>

com.judopay.ActivityResultTest: com.judopay.receipts.ListReceiptsTest.listPreAuthReceipts: <no details avaliable>

```


Services ;)


We could also add a default `dbIsValid()` method that returns `TRUE`?


Please remove this comment


@jensens Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.autoform/18/violations
```
plone/autoform/base.py:32:1: C901 'AutoFields.updateFieldsFromSchemata' is too complex (11)
plone/autoform/base.py:161:1: C901 'AutoFields._calculate_field_moves' is too complex (11)
plone/autoform/directives.py:123:31: S001 found %s formatter
plone/autoform/supermodel.py:53:26: S001 found %s formatter
plone/autoform/supermodel.py:64:17: S001 found % formatter
plone/autoform/supermodel.py:71:1: C901 'FormSchema.read' is too complex (11)
plone/autoform/supermodel.py:106:67: S001 found %s formatter
plone/autoform/supermodel.py:111:1: C901 'FormSchema.write' is too complex (14)
plone/autoform/supermodel.py:145:26: S001 found %s formatter
plone/autoform/supermodel.py:153:26: S001 found %s formatter
plone/autoform/utils.py:192:1: C901 'processFields' is too complex (13)
plone/autoform/widgets.py:70:17: S001 found %s formatter
plone/autoform/tests/test_supermodel_handler.py:41:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:42:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:44:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:44:52: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:45:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:45:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:46:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:46:54: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:48:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:49:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:84:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:85:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:87:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:87:53: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:88:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:88:56: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:89:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:89:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:92:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:92:53: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:93:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:93:56: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:138:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:139:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:142:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:143:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:148:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:149:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:150:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:153:16: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:154:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:155:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:246:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:247:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:247:52: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:248:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:248:54: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:250:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:251:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:272:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:273:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:274:26: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:274:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:275:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:286:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:287:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:288:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:289:50: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:317:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:318:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:321:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:322:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:326:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:327:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:328:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:331:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:332:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:333:32: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:418:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:418:63: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:419:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:419:64: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:461:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:462:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:465:13: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:466:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:482:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:486:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:500:31: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:504:31: Q000 Remove bad quotes.
plone/autoform/tests/test_utils.py:23:23: Q000 Remove bad quotes.
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


How so?


Thanks for the fix. I'm not really sure why the length of the object is checked here, and I also can't think of any scenarios in BAMMtools where the object needs to be only of class bammdata.


this is my project code


ok


@adamgins I'll do


It's good but it appears a bit elongated


Les migrations SQL ne doivent pas ête éditée. Il faut juste en récréer une autre pour modifier la table.


Please let us us the scalable version of the logo (svg) if possible.


Il faut pas éditer les migrations SQL mais en ajouter de nouvelles. Le but est de ne pas avoir à redétruire la BDD pour la mettre à jour...


removed student number


#gusongshishi


dfdfdfd


I don't think this should be in the repo...


@jensens Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.autoform/19/violations
```
plone/autoform/base.py:32:1: C901 'AutoFields.updateFieldsFromSchemata' is too complex (11)
plone/autoform/base.py:161:1: C901 'AutoFields._calculate_field_moves' is too complex (11)
plone/autoform/directives.py:123:31: S001 found %s formatter
plone/autoform/supermodel.py:53:26: S001 found %s formatter
plone/autoform/supermodel.py:64:17: S001 found % formatter
plone/autoform/supermodel.py:71:1: C901 'FormSchema.read' is too complex (11)
plone/autoform/supermodel.py:106:67: S001 found %s formatter
plone/autoform/supermodel.py:111:1: C901 'FormSchema.write' is too complex (14)
plone/autoform/supermodel.py:145:26: S001 found %s formatter
plone/autoform/supermodel.py:153:26: S001 found %s formatter
plone/autoform/utils.py:120:1: C901 'processFields' is too complex (19)
plone/autoform/widgets.py:70:17: S001 found %s formatter
plone/autoform/tests/test_supermodel_handler.py:351:30: E231 missing whitespace after ':'
plone/autoform/tests/test_supermodel_handler.py:351:30: E901 SyntaxError: invalid syntax
plone/autoform/tests/test_supermodel_handler.py:387:30: E231 missing whitespace after ':'
plone/autoform/tests/test_supermodel_handler.py:389:26: E225 missing whitespace around operator
plone/autoform/tests/test_supermodel_handler.py:408:30: E231 missing whitespace after ':'
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


It's easier to automate jumping to an exact number than it is to a loose version. But maybe I can make it loose-versioning for now


Did you find a solution to clear properly a page ?

And potentially we could do something more clever with the hack. Limit is to the top & bottom row pages. It is potentially enough for the hack to be efficient.


@adamgins at `3.0.3-rc.3`


I will name it `getInsightPages`


@jensens Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.autoform/20/violations
```
plone/autoform/base.py:32:1: C901 'AutoFields.updateFieldsFromSchemata' is too complex (11)
plone/autoform/base.py:161:1: C901 'AutoFields._calculate_field_moves' is too complex (11)
plone/autoform/directives.py:123:31: S001 found %s formatter
plone/autoform/supermodel.py:53:26: S001 found %s formatter
plone/autoform/supermodel.py:64:17: S001 found % formatter
plone/autoform/supermodel.py:71:1: C901 'FormSchema.read' is too complex (11)
plone/autoform/supermodel.py:106:67: S001 found %s formatter
plone/autoform/supermodel.py:111:1: C901 'FormSchema.write' is too complex (14)
plone/autoform/supermodel.py:145:26: S001 found %s formatter
plone/autoform/supermodel.py:153:26: S001 found %s formatter
plone/autoform/utils.py:120:1: C901 'processFields' is too complex (19)
plone/autoform/widgets.py:70:17: S001 found %s formatter
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


We should also pass parameter with sort type


Sorry, I usually write tests and code together. I forgot that you like to add them later.


Actually it's not insights context but insights pages so I will consider changing variable name


@ErmiyaEskandary Yep, the collision detection was broken, but this fixes it.


Sorry, I missed this. (In general, you do a good job of asking questions, not just following what other code does.)

I see why. `AbstractSystem.update` is "virtual." In the future, if we add functionality there, we'll need to call super for all systems. I'll make a note and I'll do this later.


Le agregaré un `id` a los enlaces para evitar poner las url


i wanna *** mario


because jboss-parent:20 contains requirement for java 8
I noticed it on failed nightly job
```
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ windup-bom ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireJavaVersion failed with message:
To build this project JDK 1.8 (or greater) is required. Please install it.
```


What do you think about storing sorted data instead of class instance (which is not used anymore)?


@jensens Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.autoform/21/violations
```
plone/autoform/base.py:32:1: C901 'AutoFields.updateFieldsFromSchemata' is too complex (11)
plone/autoform/base.py:161:1: C901 'AutoFields._calculate_field_moves' is too complex (11)
plone/autoform/directives.py:123:31: S001 found %s formatter
plone/autoform/supermodel.py:53:26: S001 found %s formatter
plone/autoform/supermodel.py:64:17: S001 found % formatter
plone/autoform/supermodel.py:71:1: C901 'FormSchema.read' is too complex (11)
plone/autoform/supermodel.py:106:67: S001 found %s formatter
plone/autoform/supermodel.py:111:1: C901 'FormSchema.write' is too complex (14)
plone/autoform/supermodel.py:145:26: S001 found %s formatter
plone/autoform/supermodel.py:153:26: S001 found %s formatter
plone/autoform/utils.py:120:1: C901 'processFields' is too complex (19)
plone/autoform/widgets.py:70:17: S001 found %s formatter
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


Good job.

@RoughTomato It's able to be merged.


Looks like it updates the default minimum to 8, but you can override it.

See https://github.com/jboss/jboss-parent-pom under "How to use it?"


Please initialize `$content` variable


Yes and no. What little I understand can be covered in this case; imagine if you:
- Draw first
- Move next (apply velocity)
- Apply collision detection

It looks like there is no collision, but it's just because we drew first. We should always draw last for consistency.


you should also test choosing a color, not just that it renders


I like this a lot. Could you three-d map these as well so the shadows move along with the stars?


@jensens Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.autoform/22/violations
```
plone/autoform/base.py:32:1: C901 'AutoFields.updateFieldsFromSchemata' is too complex (11)
plone/autoform/base.py:161:1: C901 'AutoFields._calculate_field_moves' is too complex (11)
plone/autoform/directives.py:123:31: S001 found %s formatter
plone/autoform/supermodel.py:53:26: S001 found %s formatter
plone/autoform/supermodel.py:64:17: S001 found % formatter
plone/autoform/supermodel.py:71:1: C901 'FormSchema.read' is too complex (11)
plone/autoform/supermodel.py:106:67: S001 found %s formatter
plone/autoform/supermodel.py:111:1: C901 'FormSchema.write' is too complex (14)
plone/autoform/supermodel.py:145:26: S001 found %s formatter
plone/autoform/supermodel.py:153:26: S001 found %s formatter
plone/autoform/utils.py:192:1: C901 'processFields' is too complex (13)
plone/autoform/widgets.py:70:17: S001 found %s formatter
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


add tests for this component