線段樹"初始"改進版

因為動態配置的版本雖然比較好理解 但是動態配置也是很花時間的冏
用陣列來做的話速度會快很多OAO
補充一下 這樣的線段樹空間複雜度為NlogN(上一個版本的也是NlogN) 至於為什麼就自己去驗證下XDD
你可以用N = 1, N = 4, N = 2147483647來算...(不推薦
你也可以用N = 1, N = k, N = k+1 數學歸納法證:D
你也可以用(Again)....不要等學長幫你想啦:DD 自己想
每次Build會花 NlogN 的時間(廢話
每次Modify會花 logN 的時間(廢話
每次Query會花 logN 的時間(廢話
當然現在這副模樣還是"初始"版..
意思是之後隨著問題的變種還會有更多優化方法...
那就下集待續(疑


It's ok for patches to contain more than 1 character diff.


This was done for compatibility with banks that use dialect 1, this would be your case?
You are using dialect 1


Feminine


comment on commit 756cf44


Wow, that was fast.

I spent days trying to find that bug, My program is rather large.

Thank you so much.


tm4c129 EK or DK ？http://www.ti.com/tool/ek-tm4c1294xl   or http://www.ti.com/tool/dk-tm4c129x？could you add a  readme?


first commit


Very nice find, thanks a bunch


what


nice comment ;)


d


Privacy note: this doesn't do much; the MITM still sees that you're connecting to Etherscan.io (and therefore, that you're interested in Ethereum).

However, now they don't know that you're checking the PRICE of Ethereum.


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


>  I'd consider it rude of a gem to lock a version like that

@rlister I understand that, but you would be locking, because it is broken.  If you don't lock (if you don't `add_dependency`), users will get:

```
RuntimeError: Expected a value or block when setting property DocileUndoFallback
```


@kasatelli the VISACARD issue has been fixed now you can check it out. Sorry for the late reply. Please open an issue next time


Hi! This is the friendly automated conda-forge-webservice.

I updated the Github team because of this commit.

- @looooo were added to this feedstock maintenance team.
  You should get push access to this feedstock and CI services.

Feel free to join the community [chat room](https://gitter.im/conda-forge/conda-forge.github.io).

NOTE: Please make sure to not push to the repository directly.
      Use branches in your fork for any changes and send a PR.
      More details [here](https://conda-forge.org/docs/conda-forge_gotchas.html#using-a-fork-vs-a-branch-when-updating-a-recipe)


You're welcome ;-)


@pbauer Jenkins CI reporting about code analysis
See the full report here: https://jenkins.plone.org/job/package-plone.app.discussion/61/violations
```
plone/app/discussion/comment.py:41:1: I004 isort found an unexpected blank line in imports
plone/app/discussion/comment.py:42:1: I004 isort found an unexpected blank line in imports
plone/app/discussion/comment.py:123:40: C812 missing trailing comma
plone/app/discussion/comment.py:167:80: C812 missing trailing comma
plone/app/discussion/comment.py:181:41: C812 missing trailing comma
plone/app/discussion/comment.py:182:19: C812 missing trailing comma
plone/app/discussion/comment.py:289:19: C812 missing trailing comma
plone/app/discussion/comment.py:293:38: C812 missing trailing comma
plone/app/discussion/comment.py:355:33: C812 missing trailing comma
plone/app/discussion/comment.py:356:14: C812 missing trailing comma
plone/app/discussion/comment.py:358:28: C812 missing trailing comma
plone/app/discussion/comment.py:425:14: C812 missing trailing comma
plone/app/discussion/comment.py:427:28: C812 missing trailing comma
plone/app/discussion/interfaces.py:62:80: C812 missing trailing comma
plone/app/discussion/interfaces.py:177:31: C812 missing trailing comma
plone/app/discussion/interfaces.py:178:10: C812 missing trailing comma
plone/app/discussion/interfaces.py:183:52: C812 missing trailing comma
plone/app/discussion/interfaces.py:185:23: C812 missing trailing comma
plone/app/discussion/interfaces.py:219:75: C812 missing trailing comma
plone/app/discussion/interfaces.py:233:56: C812 missing trailing comma
plone/app/discussion/interfaces.py:247:22: C812 missing trailing comma
plone/app/discussion/interfaces.py:253:48: C812 missing trailing comma
plone/app/discussion/interfaces.py:263:44: C812 missing trailing comma
plone/app/discussion/interfaces.py:350:47: C812 missing trailing comma
plone/app/discussion/interfaces.py:362:54: C812 missing trailing comma
plone/app/discussion/interfaces.py:369:22: C812 missing trailing comma
plone/app/discussion/testing.py:95:33: C812 missing trailing comma
plone/app/discussion/testing.py:122:36: C812 missing trailing comma
plone/app/discussion/conversation.py:41:1: I004 isort found an unexpected blank line in imports
plone/app/discussion/conversation.py:42:1: I004 isort found an unexpected blank line in imports
plone/app/discussion/conversation.py:43:1: I001 isort found an import in the wrong position
plone/app/discussion/conversation.py:423:24: C812 missing trailing comma
plone/app/discussion/catalog.py:17:1: I003 isort expected 1 blank line in imports, found 0
plone/app/discussion/catalog.py:85:80: E501 line too long (90 > 79 characters)
plone/app/discussion/tests/test_indexers.py:73:37: C812 missing trailing comma
plone/app/discussion/tests/test_indexers.py:85:37: C812 missing trailing comma
plone/app/discussion/tests/test_indexers.py:89:46: C812 missing trailing comma
plone/app/discussion/tests/test_indexers.py:94:46: C812 missing trailing comma
plone/app/discussion/tests/test_indexers.py:141:42: C812 missing trailing comma
plone/app/discussion/tests/test_indexers.py:156:45: C812 missing trailing comma
plone/app/discussion/tests/test_indexers.py:163:53: C812 missing trailing comma
plone/app/discussion/tests/test_indexers.py:167:53: C812 missing trailing comma
plone/app/discussion/tests/test_indexers.py:171:52: C812 missing trailing comma
plone/app/discussion/tests/test_indexers.py:178:44: C812 missing trailing comma
plone/app/discussion/tests/test_indexers.py:182:37: C812 missing trailing comma
plone/app/discussion/tests/test_functional.py:31:46: C812 missing trailing comma
plone/app/discussion/tests/test_contentrules.py:33:44: C812 missing trailing comma
plone/app/discussion/tests/test_contentrules.py:99:57: C812 missing trailing comma
plone/app/discussion/tests/test_contentrules.py:115:31: C812 missing trailing comma
plone/app/discussion/tests/test_contentrules.py:123:33: C812 missing trailing comma
plone/app/discussion/tests/test_contentrules.py:131:36: C812 missing trailing comma
plone/app/discussion/tests/test_contentrules.py:139:42: C812 missing trailing comma
plone/app/discussion/tests/test_contentrules.py:147:39: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:83:33: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:91:33: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:105:33: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:147:33: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:154:38: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:163:33: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:177:38: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:222:33: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:231:33: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:244:44: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:251:40: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:280:33: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:289:33: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:302:39: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:310:35: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:346:40: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:351:33: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:394:33: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:441:18: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:457:40: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:535:36: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:590:14: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:595:41: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:602:22: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:608:41: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:619:51: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:632:21: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:636:18: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:640:20: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:658:66: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:667:14: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:694:54: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:695:14: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:728:71: C812 missing trailing comma
plone/app/discussion/tests/test_comments_viewlet.py:742:67: C815 missing trailing comma in Python 3.5+
plone/app/discussion/tests/test_robot.py:26:57: C812 missing trailing comma
plone/app/discussion/tests/test_notifications.py:179:41: C812 missing trailing comma
plone/app/discussion/tests/test_notifications.py:222:16: C812 missing trailing comma
plone/app/discussion/tests/test_notifications.py:226:16: C812 missing trailing comma
plone/app/discussion/tests/test_notifications.py:232:16: C812 missing trailing comma
plone/app/discussion/tests/test_notifications.py:238:16: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:29:49: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:33:49: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:37:48: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:41:48: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:82:61: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:84:35: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:102:66: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:108:61: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:110:35: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:119:46: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:131:66: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:137:61: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:139:35: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:144:46: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:153:61: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:155:35: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:160:46: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:168:61: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:170:35: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:188:66: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:195:61: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:197:35: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:208:61: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:210:35: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:220:61: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:222:35: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:231:61: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:233:42: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:246:61: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:248:35: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:275:66: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:280:57: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:281:14: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:295:54: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:300:52: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:301:14: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:333:57: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:334:14: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:360:31: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:365:31: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:370:33: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:385:76: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:392:73: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:393:14: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:399:28: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:419:55: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:434:57: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:441:57: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:447:28: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:462:33: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:480:33: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:555:61: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:557:35: C812 missing trailing comma
plone/app/discussion/tests/test_catalog.py:570:43: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:32:43: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:43:14: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:54:18: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:65:18: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:76:18: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:102:25: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:113:23: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:124:17: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:130:68: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:137:18: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:170:34: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:171:14: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:182:34: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:183:14: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:190:34: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:191:14: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:205:41: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:214:44: C812 missing trailing comma
plone/app/discussion/tests/test_controlpanel.py:221:35: C812 missing trailing comma
plone/app/discussion/tests/test_events.py:155:57: C812 missing trailing comma
plone/app/discussion/tests/test_events.py:176:57: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:71:42: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:82:42: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:91:42: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:112:33: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:124:33: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:160:62: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:168:50: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:177:31: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:185:48: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:195:54: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:204:65: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:234:66: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:241:37: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:243:38: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:247:57: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:258:30: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:266:66: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:294:69: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:298:77: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:302:76: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:310:49: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:334:66: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:375:57: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:412:57: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:448:57: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:457:60: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:466:63: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:475:66: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:480:38: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:484:48: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:488:41: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:493:38: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:498:34: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:500:44: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:505:41: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:510:37: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:512:47: C812 missing trailing comma
plone/app/discussion/tests/test_comment.py:517:44: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:23:1: I004 isort found an unexpected blank line in imports
plone/app/discussion/tests/test_conversation.py:24:1: I004 isort found an unexpected blank line in imports
plone/app/discussion/tests/test_conversation.py:25:1: I001 isort found an import in the wrong position
plone/app/discussion/tests/test_conversation.py:77:34: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:85:33: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:283:34: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:331:34: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:401:11: T000 Todo note found.
plone/app/discussion/tests/test_conversation.py:517:56: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:521:61: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:531:64: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:535:41: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:545:64: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:549:41: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:623:11: T000 Todo note found.
plone/app/discussion/tests/test_conversation.py:631:38: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:637:43: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:641:40: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:649:54: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:673:43: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:686:40: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:692:34: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:852:59: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:857:59: C812 missing trailing comma
plone/app/discussion/tests/test_conversation.py:863:61: C812 missing trailing comma
plone/app/discussion/tests/test_moderation_view.py:82:59: C812 missing trailing comma
plone/app/discussion/tests/test_moderation_view.py:90:59: C812 missing trailing comma
plone/app/discussion/tests/test_moderation_view.py:98:59: C812 missing trailing comma
plone/app/discussion/tests/test_moderation_view.py:184:33: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:50:34: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:51:14: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:64:28: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:66:24: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:128:54: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:222:61: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:264:31: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:265:14: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:273:31: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:274:14: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:284:31: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:285:14: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:290:41: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:296:31: C812 missing trailing comma
plone/app/discussion/tests/test_workflow.py:297:14: C812 missing trailing comma
plone/app/discussion/browser/comment.py:5:1: I001 isort found an import in the wrong position
plone/app/discussion/browser/controlpanel.py:37:46: C812 missing trailing comma
plone/app/discussion/browser/controlpanel.py:71:44: C812 missing trailing comma
plone/app/discussion/browser/controlpanel.py:74:39: C812 missing trailing comma
plone/app/discussion/browser/controlpanel.py:95:40: C812 missing trailing comma
plone/app/discussion/browser/controlpanel.py:96:14: C812 missing trailing comma
plone/app/discussion/browser/comments.py:36:1: I004 isort found an unexpected blank line in imports
plone/app/discussion/browser/comments.py:37:1: F401 'six' imported but unused
plone/app/discussion/browser/comments.py:43:38: C812 missing trailing comma
plone/app/discussion/browser/comments.py:50:33: C812 missing trailing comma
plone/app/discussion/browser/comments.py:57:49: C812 missing trailing comma
plone/app/discussion/browser/comments.py:62:39: C812 missing trailing comma
plone/app/discussion/browser/comments.py:173:15: T000 Todo note found.
plone/app/discussion/browser/comments.py:177:16: T000 Todo note found.
plone/app/discussion/browser/comments.py:224:47: C812 missing trailing comma
plone/app/discussion/browser/comments.py:236:34: C812 missing trailing comma
plone/app/discussion/browser/comments.py:239:69: C812 missing trailing comma
plone/app/discussion/browser/comments.py:289:17: C812 missing trailing comma
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


Compare to only /grade/


## Joker
Este es mi villano favorito


@nicolasbock you may also add this trailer to make GitHub recognize several commit authors:
```yaml
Co-authored-by: Your Name <your@e.mail>
```


This also needed to be added in the Dockerfile.  Fix incoming


出现【高速受损。。。】怎么破


*comitted 4 days from now*

You seem to be living in the future! :open_mouth:


Entiendo porque agregaste a Deadshot, lo necesitaremos


@nitzantomer be careful when changing these codes as this is a breaking change


Wow a 🅱ug


thanks for the testing it; second fix incoming!


I'm not sure what change you are requesting here. Could you perhaps comment further.


Waiting...


Had problems importing firebase-jobdispatcher. Spent hours and hours syncing and rebuilding this.
ReminderUtilities.java and WaterReminderFirebaseJobService.java were particularly problematic.


An empty line is missing before this line.


Created multidev environment [masterfind-d8#ci-1](https://dashboard.pantheon.io/sites/6d468630-301d-41c1-8a4a-82768a4e2081#ci-1).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://ci-1-masterfind-d8.pantheonsite.io/)


Thanks @freddy33.
Done:
https://github.com/jfrog/jfrog-cli-go/commit/bb25c415f5b6ebad54c08fb02840d99ba7521f8f


There is a lot of funny indentation going on in this file. Please fix.


iuadsga


@gnodet , I have reworked the support, could you give it an eye? https://github.com/jfdenise/aesh-readline/commit/70fb1f656b07814681e4f1210c13e2b7ac15cb58
Mainly I am providing the codepoints to the terminal in case the terminal exposes an int[] consumer (something that Windows terminal does for Windows10+).


Why test this with `-p` first? This is the *least* interesting mode. Please use `--am` instead.


![](https://github.trello.services/images/mini-trello-icon.png) [L'accès aux logs sur la version 4.3.1 est cassé](https://trello.com/c/nv8v9HXQ/438-lacc%C3%A8s-aux-logs-sur-la-version-431-est-cass%C3%A9)


mi sa che hai messo uno spazio in più prima della parentesi


we shouldn't need the ABI


This should be `#e8e8e8` I believe


Microsoft MSDN resource centre and stack overflow used for additional guidance to develop application.


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


please.....


Created multidev environment [masterfind-d8#ci-3](https://dashboard.pantheon.io/sites/6d468630-301d-41c1-8a4a-82768a4e2081#ci-3).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://ci-3-masterfind-d8.pantheonsite.io/)


Collaborator: Review for this commit was created. [Link to review](https://demo.smartbeartrial.com/ui#review:id=628)


:( I need a different method for double-checking merge issues on the PR because what I did obviously didn't work.


We should update to 3.0.0


- degrad_res.pro: This file seems to be in an awkward place. It is common between FoMo-IDL and FoMo-C. Should we move it to another directory (e.g. postprocessing)? We had a similar discussion about elements.pro a while ago, and then we decided against it because of IDL path issues.

- fomo_synth.pro: ndens seems to be the total number density. However, in FoMo-C, I expect as input the electron density. Is it easy to keep this uniform in the documentation?

- goft_table.pro:
if logtm lt 5 then n_e_max = 1.e11 else n_e_max = 1.e12
Should it not be the other way around? If the temperature is low, then the density may be higher?

- which_line_fomo.pro:
0.002 is included as a possible range of wavelengths. Should this be a parameter in the routine? Also, later it is stated that this is 0.02%, but it is rather 0.2%.


You spelled censored wrong and the token is still visible


If contempt is implemented to beat weaker opponents, I think it should be tested against weaker opponent (like SF9 for example).
I imagine that if mg(contempt) >> eg(contempt), the engine will try to avoid going to endgame with advantage less than the contempt lost (and hoping that opponent will make a mistake in next moves). But against itself it should not bring something interessant.


compilation is failing

```
BOARD_HARDWARE_PATH="/home/fwernli/Arduino/hardware" /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/bin//kaleidoscope-builder build-all
Building output/Model01-Firmware/Model01-Firmware (0.0.0-gv1.22-15-gabd3) ...
In file included from /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:28:0,
                 from /home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:17:
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino: In function 'void setup()':
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:108:3: error: 'namespace' definition is not allowed here
   namespace kaleidoscope_internal {                                           __NL__ \
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:211:40: note: in expansion of macro '_KALEIDOSCOPE_INIT_PLUGINS'
 #define KALEIDOSCOPE_INIT_PLUGINS(...) _KALEIDOSCOPE_INIT_PLUGINS(__VA_ARGS__)
                                        ^
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:315:3: note: in expansion of macro 'KALEIDOSCOPE_INIT_PLUGINS'
   KALEIDOSCOPE_INIT_PLUGINS(European,
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:60:3: error: 'namespace' definition is not allowed here
   namespace kaleidoscope_internal {                                       __NL__ \
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/event_handlers.h:24:4: note: in expansion of macro '_REGISTER_EVENT_HANDLER'
    OPERATION(onSetup,                                                     __NL__ \
    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:133:3: note: in expansion of macro '_FOR_EACH_EVENT_HANDLER'
   _FOR_EACH_EVENT_HANDLER(_REGISTER_EVENT_HANDLER)
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:211:40: note: in expansion of macro '_KALEIDOSCOPE_INIT_PLUGINS'
 #define KALEIDOSCOPE_INIT_PLUGINS(...) _KALEIDOSCOPE_INIT_PLUGINS(__VA_ARGS__)
                                        ^
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:315:3: note: in expansion of macro 'KALEIDOSCOPE_INIT_PLUGINS'
   KALEIDOSCOPE_INIT_PLUGINS(European,
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:78:4: error: 'namespace' definition is not allowed here
    namespace kaleidoscope {                                               __NL__ \
    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/event_handlers.h:24:4: note: in expansion of macro '_REGISTER_EVENT_HANDLER'
    OPERATION(onSetup,                                                     __NL__ \
    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:133:3: note: in expansion of macro '_FOR_EACH_EVENT_HANDLER'
   _FOR_EACH_EVENT_HANDLER(_REGISTER_EVENT_HANDLER)
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:211:40: note: in expansion of macro '_KALEIDOSCOPE_INIT_PLUGINS'
 #define KALEIDOSCOPE_INIT_PLUGINS(...) _KALEIDOSCOPE_INIT_PLUGINS(__VA_ARGS__)
                                        ^
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:315:3: note: in expansion of macro 'KALEIDOSCOPE_INIT_PLUGINS'
   KALEIDOSCOPE_INIT_PLUGINS(European,
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:60:3: error: 'namespace' definition is not allowed here
   namespace kaleidoscope_internal {                                       __NL__ \
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/event_handlers.h:30:4: note: in expansion of macro '_REGISTER_EVENT_HANDLER'
    OPERATION(beforeEachCycle,                                             __NL__ \
    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:133:3: note: in expansion of macro '_FOR_EACH_EVENT_HANDLER'
   _FOR_EACH_EVENT_HANDLER(_REGISTER_EVENT_HANDLER)
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:211:40: note: in expansion of macro '_KALEIDOSCOPE_INIT_PLUGINS'
 #define KALEIDOSCOPE_INIT_PLUGINS(...) _KALEIDOSCOPE_INIT_PLUGINS(__VA_ARGS__)
                                        ^
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:315:3: note: in expansion of macro 'KALEIDOSCOPE_INIT_PLUGINS'
   KALEIDOSCOPE_INIT_PLUGINS(European,
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:78:4: error: 'namespace' definition is not allowed here
    namespace kaleidoscope {                                               __NL__ \
    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/event_handlers.h:30:4: note: in expansion of macro '_REGISTER_EVENT_HANDLER'
    OPERATION(beforeEachCycle,                                             __NL__ \
    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:133:3: note: in expansion of macro '_FOR_EACH_EVENT_HANDLER'
   _FOR_EACH_EVENT_HANDLER(_REGISTER_EVENT_HANDLER)
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:211:40: note: in expansion of macro '_KALEIDOSCOPE_INIT_PLUGINS'
 #define KALEIDOSCOPE_INIT_PLUGINS(...) _KALEIDOSCOPE_INIT_PLUGINS(__VA_ARGS__)
                                        ^
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:315:3: note: in expansion of macro 'KALEIDOSCOPE_INIT_PLUGINS'
   KALEIDOSCOPE_INIT_PLUGINS(European,
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:60:3: error: 'namespace' definition is not allowed here
   namespace kaleidoscope_internal {                                       __NL__ \
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/event_handlers.h:41:3: note: in expansion of macro '_REGISTER_EVENT_HANDLER'
   OPERATION(onKeyswitchEvent,                                             __NL__ \
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:133:3: note: in expansion of macro '_FOR_EACH_EVENT_HANDLER'
   _FOR_EACH_EVENT_HANDLER(_REGISTER_EVENT_HANDLER)
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:211:40: note: in expansion of macro '_KALEIDOSCOPE_INIT_PLUGINS'
 #define KALEIDOSCOPE_INIT_PLUGINS(...) _KALEIDOSCOPE_INIT_PLUGINS(__VA_ARGS__)
                                        ^
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:315:3: note: in expansion of macro 'KALEIDOSCOPE_INIT_PLUGINS'
   KALEIDOSCOPE_INIT_PLUGINS(European,
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:78:4: error: 'namespace' definition is not allowed here
    namespace kaleidoscope {                                               __NL__ \
    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/event_handlers.h:41:3: note: in expansion of macro '_REGISTER_EVENT_HANDLER'
   OPERATION(onKeyswitchEvent,                                             __NL__ \
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:133:3: note: in expansion of macro '_FOR_EACH_EVENT_HANDLER'
   _FOR_EACH_EVENT_HANDLER(_REGISTER_EVENT_HANDLER)
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:211:40: note: in expansion of macro '_KALEIDOSCOPE_INIT_PLUGINS'
 #define KALEIDOSCOPE_INIT_PLUGINS(...) _KALEIDOSCOPE_INIT_PLUGINS(__VA_ARGS__)
                                        ^
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:315:3: note: in expansion of macro 'KALEIDOSCOPE_INIT_PLUGINS'
   KALEIDOSCOPE_INIT_PLUGINS(European,
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:60:3: error: 'namespace' definition is not allowed here
   namespace kaleidoscope_internal {                                       __NL__ \
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/event_handlers.h:49:4: note: in expansion of macro '_REGISTER_EVENT_HANDLER'
    OPERATION(beforeReportingState,                                        __NL__ \
    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:133:3: note: in expansion of macro '_FOR_EACH_EVENT_HANDLER'
   _FOR_EACH_EVENT_HANDLER(_REGISTER_EVENT_HANDLER)
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:211:40: note: in expansion of macro '_KALEIDOSCOPE_INIT_PLUGINS'
 #define KALEIDOSCOPE_INIT_PLUGINS(...) _KALEIDOSCOPE_INIT_PLUGINS(__VA_ARGS__)
                                        ^
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:315:3: note: in expansion of macro 'KALEIDOSCOPE_INIT_PLUGINS'
   KALEIDOSCOPE_INIT_PLUGINS(European,
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:78:4: error: 'namespace' definition is not allowed here
    namespace kaleidoscope {                                               __NL__ \
    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/event_handlers.h:49:4: note: in expansion of macro '_REGISTER_EVENT_HANDLER'
    OPERATION(beforeReportingState,                                        __NL__ \
    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:133:3: note: in expansion of macro '_FOR_EACH_EVENT_HANDLER'
   _FOR_EACH_EVENT_HANDLER(_REGISTER_EVENT_HANDLER)
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:211:40: note: in expansion of macro '_KALEIDOSCOPE_INIT_PLUGINS'
 #define KALEIDOSCOPE_INIT_PLUGINS(...) _KALEIDOSCOPE_INIT_PLUGINS(__VA_ARGS__)
                                        ^
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:315:3: note: in expansion of macro 'KALEIDOSCOPE_INIT_PLUGINS'
   KALEIDOSCOPE_INIT_PLUGINS(European,
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:60:3: error: 'namespace' definition is not allowed here
   namespace kaleidoscope_internal {                                       __NL__ \
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/event_handlers.h:55:4: note: in expansion of macro '_REGISTER_EVENT_HANDLER'
    OPERATION(afterEachCycle,                                              __NL__ \
    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:133:3: note: in expansion of macro '_FOR_EACH_EVENT_HANDLER'
   _FOR_EACH_EVENT_HANDLER(_REGISTER_EVENT_HANDLER)
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:211:40: note: in expansion of macro '_KALEIDOSCOPE_INIT_PLUGINS'
 #define KALEIDOSCOPE_INIT_PLUGINS(...) _KALEIDOSCOPE_INIT_PLUGINS(__VA_ARGS__)
                                        ^
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:315:3: note: in expansion of macro 'KALEIDOSCOPE_INIT_PLUGINS'
   KALEIDOSCOPE_INIT_PLUGINS(European,
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:78:4: error: 'namespace' definition is not allowed here
    namespace kaleidoscope {                                               __NL__ \
    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/event_handlers.h:55:4: note: in expansion of macro '_REGISTER_EVENT_HANDLER'
    OPERATION(afterEachCycle,                                              __NL__ \
    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/kaleidoscope_internal/event_dispatch.h:133:3: note: in expansion of macro '_FOR_EACH_EVENT_HANDLER'
   _FOR_EACH_EVENT_HANDLER(_REGISTER_EVENT_HANDLER)
   ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:211:40: note: in expansion of macro '_KALEIDOSCOPE_INIT_PLUGINS'
 #define KALEIDOSCOPE_INIT_PLUGINS(...) _KALEIDOSCOPE_INIT_PLUGINS(__VA_ARGS__)
                                        ^
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:315:3: note: in expansion of macro 'KALEIDOSCOPE_INIT_PLUGINS'
   KALEIDOSCOPE_INIT_PLUGINS(European,
   ^
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:385:36: warning: 'void kaleidoscope::HostPowerManagement::enableWakeup()' is deprecated (declared at /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-HostPowerManagement/src/Kaleidoscope/HostPowerManagement.h:39):
------------------------------------------------------------------------
The HostPowerManagement.enableWakeup() call is not necessary anymore,
the firmware supports wakeup by default now. The line can be safely
removed.
------------------------------------------------------------------------
 [-Wdeprecated-declarations]
   HostPowerManagement.enableWakeup();
                                    ^
exit status 1
/home/fwernli/Arduino/hardware/keyboardio/avr/build-tools/makefiles//rules.mk:72: recipe for target 'build-all' failed
make: *** [build-all] Error 1
```


python 3.5: TypeError: Can't convert 'int' object to str implicitly
python 3.6: TypeError: must be str, not int


These changes work fine in my tests; suggest we merge


can relate


hi, it is git-hap


Alright. I will check on it tonight.. sorry I didn't open an issue. I was on my phone and in a hurry that day 👍


Don't forget the braces please ;)


__API Description file syntax error on line 1376__: base type 'HistoryAmount' is not defined in the document (Autogenerated message from apiary.io)


test


>@nicolasbock you may also add this trailer to make GitHub recognize several commit authors:
>```yaml
>Co-authored-by: Your Name <your@e.mail>
>```

Oh cool, I didn't know that GitHub understands this now. Thanks!


This line is no longer needed, and am surprised does not show up a warning.


Come to think of it the artificial limit is 16 GiB, so it should not matter.


bind the embedding information into the data.


Dear Poggit user,

This is an automatic message from Poggit-CI. Poggit-CI was triggered by this commit, but failed to create builds due to the following error:

```
Resend this delivery later. This commit is triggered by user jackthehack21,
who has created 60 Poggit-CI builds in the past 168 hours.

Contact @SOF3 [on Discord](https://discord.gg/NgHf9jt) to request for extra
quota. We will increase your quota for free if you are really contributing
to open-source plugins actively without abusing Git commits.
```

As a result, no builds could be created from this commit. More details might be available for repo admins at [the webhook delivery response log](https://github.com/jackthehack21/MCPEToDiscord/settings/hooks) — see the webhook starting with `https://poggit.pmmp.io/webhooks.gh.repo` and look for the delivery with ID `64dec9ba-6e3f-11e8-902d-c35ba6af3153`.

Shall you need any assistance, you may contact us on [on Discord](https://discord.gg/NgHf9jt), or more publicly, [on GitHub](https://github.com/poggit/support/issues). Commenting on this commit directly will **not** notify any Poggit staff.

Regards,
Poggit Bot (@poggit-bot)
The official Poggit automation account


[自動販売機のシステム.pdf](https://github.com/teijiejie/geek-job/files/2094062/default.pdf)


Cambio sugerido por el sistema


cout << siema


前面的版本只能單點修改
那如果pick一個區間要求你修改呢(區間修改)?
如果你跑一個迴圈修改每個點那一次要花NlogN的時間
M次就要花NM(logN)的時間
那有沒有比較快的方法可以一次改好呢?

有 這項技巧被稱為懶標記(Lazy tag)!!!

先想想: 一個節點一個節點更新下去的話..那是不是會有很多節點明明走訪過, 更新過同樣的父節點, 但卻每次都要花logN個時間的代價去更新, 這樣是不是很花時間呢?

這項技巧會被這麼稱呼的原因是因為他很懶(誤, 是因為每個節點多維護一個叫做懶標記的值
這個懶標記, 當你開Modify想要更改某區間的每個值時就會用到
當節點在往下更新值時, 會把懶標記傳到左子樹與右子樹, 同時利用左區間, 右區間有的數值總數(L, R值)去更新左子樹與右子樹的值
這個動作稱為Pull, 也就是把懶標記往下推, 利用這樣, 在Modify區間的時候就能節省很多時間

這裡做個小例子(改天補圖):
假設有一個節點他存的數值是Value = 50, 他的左子樹裡面所有的葉節點有3個, 右子樹裡面所有的葉節點有2個, 也就是說他維護的區間是[1, 5], 他的左子樹是[1, 3], 右子樹是[4, 5]
今天要求要為[2, 5]區間裡的每個數增加10
則先幫維護[1, 5]這個區間的節點的lazy tag寫為10
接下來因為目標區間[2, 5]在[1, 5]裡面, 表示還沒推懶標記到目的地, 因此先把懶標記往左子樹[1, 3]與右子樹[4, 5]推, 然後幫左子樹的Value值加(3-(1-1))*10, 右子樹的Value值加(5-(4-1))*10, 為左右子樹的懶標記加10, 遞迴左子樹與右子樹
因為目標區間[2, 5]在[1, 3]裡面, 表示還沒推懶標記到目的地, 因此先把懶標記往左子樹[1, 2]與右子樹[3, 3]推, 然後幫左子樹的Value值加(2-(1-1))*10, 右子樹的Value值加(3-(3-1))*10, 為左右子樹的懶標記加10, 遞迴左子樹與右子樹
因為目標區間[2, 5]在[1, 2]的右半區間內, 表示還沒推懶標記到目的地, 因此先把懶標記往左子樹[1, 1]與右子樹[2, 2]推, 然後幫左子樹的Value值加(1-(1-1))*10, 右子樹的Value值加(2-(2-1))*10, 為左右子樹的懶標記加10, 然後遞迴右子樹
因為目標區間[2, 5]完全包括[2, 2], 表示懶標記已經推到涵蓋整個[2, 2]區間, 直接回傳, 停止推懶標記
因為目標區間[2, 5]完全包括[3, 3], 表示懶標記已經推到涵蓋整個[3, 3]區間, 直接回傳, 停止推懶標記
因為回到[1, 3]了, 所以要記得利用[1, 3]的左子樹跟右子樹的值更新[1, 3]
因為目標區間[2, 5]完全包括[4, 5], 表示懶標記已經推到涵蓋整個[4, 5]區間, 直接回傳, 停止推懶標記
因為回到[1, 5]了, 所以要記得利用[1, 5]的左子樹跟右子樹的值更新[1, 5]

稍微算一下就知道利用了懶標記的Modify修改一次區間只要花logN
修改M次只要花MlogN的時間
Query的時候也只要花logN的時間而已

就這樣, 不知道有沒有覺得懶標記很實用呢?(看不懂要記得提醒我補圖阿:DD)


初始config client


Good question. I didn't check as I was merely polishing here. That said I see [there is one](https://github.com/spring-projects/spring-framework/blob/0b64bcd319abf39be435dd7b631c2045d60a8039/spring-jms/src/test/java/org/springframework/jms/config/MethodJmsListenerEndpointTests.java#L522).


那就先改了，以后有人要再放出来


<img width="1319" alt="screen shot 2018-06-12 at 8 55 10 am" src="https://user-images.githubusercontent.com/29581710/41291679-5d56ac06-6e1e-11e8-95c6-d9a81c38b942.png">


Why don't you set that via `occ`?


Hopefully that will work: https://github.com/odoo/odoo/pull/25207


__apiary.manifest contains reference to non-existent file in repository.__ (Autogenerated message from apiary.io)
+ apiary.apib


WHY? --- There is a test enviroment for this problem, and you break it again … WHY?

There was also a why to fix this permanently. - And you break it again.

I told you when and why it breaks …

I AM SAD :-(


## Joker
Villano


Just `occ` like it's done for the other commands?


I prefer not to use special values like -1, -2

I think it's fine to just have two separate interfaces : one using a bool that allows only short or long, and the other allowing a custom value. Sounds ok to you?


`occ ldap:create-empty-config`


## Notas

Nuevo comentario


`occ ldap:delete-config ''`


Created multidev environment [riveralive-cms#pr-11](https://dashboard.pantheon.io/sites/ced938b0-bbbf-4ed2-ba1c-98b66d8ba2be#pr-11).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://pr-11-riveralive-cms.pantheonsite.io/)


How often is this going to be updated?


This should be already enabled?


Congrats!


I think this is close but not exactly right - we need to avoid running the task at all if we've not waited long enough. I'm thinking the run method would be something like:
```
public void run() {
    if (canceled.get()) {
       return;
    }

   Date now = new Date();
    if (now.isBefore(nextSchedule)) {
      // If it's not quite time to run yet, find out how long we should wait and then schedule this task again
      flowEngine.schedule(this, nextSchedule.getTime() - now.getTime());
      return;
    } else {
      taskWrapper.run();
      now = new Date();
      this.nextSchedule = cronExpression.getTimeAfter(now);
      flowEngine.schedule(this, nextSchedule.getTime() - now.getTime());
    }
}
```

This is all just code off of the top of my head, that hasn't been tested, though, so take the code itself with a grain of salt. But the idea, is to simply check before invoking `taskWrapper.run()` "is it really time to run yet?" and if not, re-schedule for the correct time. Do that until the correct time (or slightly after the correct time). Only then should we call `taskWrapper.run()` and at that point we'd re-schedule based on the CRON expression. Does that make sense?


Where are these keywords used? probably by `helm` client?
we need to add `caching` too


became worse
![bfx-fix-bug](https://user-images.githubusercontent.com/10449591/41292044-091e740c-6e5a-11e8-8989-c44ae6c82e40.jpg)


import os
import sys
import time
import shutil
import tarfile
from os.path import isfile, isdir, join
from datetime import datetime
import logging

def check_date(file_name):
    """ Function to check that a file is old """

    # Get timestamp from file name
    datetime_str_arr = str(file_name).split("_")
    datetime_str = str(datetime_str_arr[1].split(".")[0])

    f_year = int(datetime_str[0:4])     # year
    f_month = int(datetime_str[4:6])    # month
    f_date = int(datetime_str[6:8])     # date

    # Get current date
    now_date = datetime.now().date()

    n_year = now_date.year
    n_month = now_date.month
    n_day = now_date.day

    if (f_year > n_year) or ((f_month >= n_month) and (f_year == n_year)):
        return False

    # Get Staging directory name
    if f_month < 12:
        if f_month < 9:
            f_month = '0' + str(f_month + 1)
        else:
            f_month = str(f_month + 1)

        staging_subdir = '%s%d%s%s' % ('data_prior_to_', f_year, f_month, '01')
    else:
        staging_subdir = '%s%d%s' % ('data_prior_to_', f_year + 1, '0101')

    source_dir = join(staging_path, staging_subdir)

    # Create a data directory in Staging directory
    try:
        os.stat(source_dir)
    except:
        os.mkdir(source_dir)

    return source_dir

def validate_file(file_name, flag):
    """ Function to validate file format """

    dir_array = str(file_name).split("_")

    # Check about files of data/Spr directory
    if flag == 1:
        if dir_array.__len__() == 2:
            if dir_array[1].split(".")[0].isdigit():
                if len(dir_array[1].split(".")[0]) == 8:
                    return True

    # Check about directories of Staging directory
    if flag == 2:
        if dir_array.__len__() == 4:
            if dir_array[3].isdigit():
                if len(dir_array[3]) == 8:
                    return True

    # Check about compress file type
    if flag == 3:
        if dir_array.__len__() == 4:
            date_ext = dir_array[3].split(".")
            if date_ext[0].isdigit():
                if len(date_ext[0]) == 8:
                    if (date_ext[1] == 'tar' and date_ext[2] == 'gz'):
                        return True

    return False

def move_staging(data_path, staging_path):
    """ Function to move old files to Staging directory """

    print "\nMoving old files from Spr directory to Staging directory..."

    # Get all files of the Spr directory
    dirs = os.listdir(data_path)

    # Check data each file and move
    for sub_dir in dirs:
        if isfile(join(data_path, sub_dir)):
            continue

        # Get files from sub directory
        sub_files = os.listdir(join(data_path, sub_dir))
        for f in sub_files:
            if validate_file(f, 1) == True:
                staging_dir = check_date(f)
                if staging_dir == False:
                    continue

                shutil.move(join(data_path, sub_dir, f), join(staging_dir, f))

def prepare_compression(staging_path, archiving_path):
    """ function to compress as Gzip file and  move into Archiving directory """

    print "Compressing gzip files and move into Archiving directory..."

    # Get all files of Staging directory
    files = os.listdir(staging_path)

    for f in files:
        if isfile(join(staging_path, f)):
            continue

        if not validate_file(f, 2):
            continue

        # Compress as Gzip file and move to Archiving directory
        gzpath = join(archiving_path, f) + '.tar.gz'
        f_out = tarfile.open(gzpath, 'w:gz')
        f_out.add(join(staging_path, f), arcname = f)
        f_out.close()

        # Remove directory from Staging
        # shutil.rmtree(join(staging_path, f))

def save_remote_server(archiving_path, server_url):
    """ Function to save in remote archiving server """

    print "Saving compress files in Remote Archiving Server..."

    # Get archiving data of Archiving directory
    files = os.listdir(archiving_path)
    is_new = True

    # Save compressed files in server
    try:
        for f in files:
            if not validate_file(f, 3):
                continue

            shutil.copy(join(archiving_path, f), server_url)

            # add log information
            logging_file(f, join(archiving_path, f), server_url, is_new)
            is_new = False
            # os.remove(join(archiving_path, f))

    except:
        print "Error: Remote Archiving Server Url"
        exit()

def logging_file(comp_file, comp_path, server_url, is_new):
    """ Function to save logging information """

    # Logging filename
    log_filename = "history.log"

    # Open log file
    try:
        f = open(log_filename, 'a')
    except IOError:
        os.stat(log_filename)

    # Write head info
    if is_new == True:
        print >> f, '\n-------------------- ' + str(datetime.now().date()) + ' --------------------\n'
        print >> f, 'Compressed files is saved in remote archiving server: ' + server_url

    print >> f, '\n' + str(comp_file) + ':'

    # Write archiving data filename
    gzfile = tarfile.open(comp_path)
    f_list = gzfile.getnames()

    for f_log in f_list:
        tmp_arr = f_log.split('/')
        if len(tmp_arr) == 1:
            continue
        print >> f, '\t' + str(tmp_arr[len(tmp_arr) - 1])

    logging.shutdown()

if __name__ == "__main__":

    # Source directory path
    data_path = "data"
    staging_path = "Staging"
    archiving_path = "Archiving"

    server_url = raw_input("Input remote archiving server url: \n")
    if not os.path.exists(server_url):
        print "Error: Remote Archiving Server Url. Try again!"
        exit()

    # Move files from data/spr to staging directory
    move_staging(data_path, staging_path)

    # Compress and move gzip files from staging to archiving
    prepare_compression(staging_path, archiving_path)

    # Save remote archiving server
    save_remote_server(archiving_path, server_url)

    print "\nComplete successfully!"


Lnvm_chunk_to_lba may be a better name.


Ok


Please officially announcement such pull requests to master branch in future, for sake of accountability. Thanks.


```
BOARD_HARDWARE_PATH="/home/fwernli/Arduino/hardware" /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/bin//kaleidoscope-builder build-all
Building output/Model01-Firmware/Model01-Firmware (0.0.0-gv1.22-16-g30f2) ...
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino: In function 'void setup()':
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:348:36: warning: 'void kaleidoscope::HostPowerManagement::enableWakeup()' is deprecated (declared at /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-HostPowerManagement/src/Kaleidoscope/HostPowerManagement.h:39):
------------------------------------------------------------------------
The HostPowerManagement.enableWakeup() call is not necessary anymore,
the firmware supports wakeup by default now. The line can be safely
removed.
------------------------------------------------------------------------
 [-Wdeprecated-declarations]
   HostPowerManagement.enableWakeup();
                                    ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-MouseKeys/src/Kaleidoscope-MouseKeys.cpp: In member function 'virtual void MouseKeys_::begin()':
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-MouseKeys/src/Kaleidoscope-MouseKeys.cpp:141:54: warning: 'static void kaleidoscope::Kaleidoscope_::useEventHandlerHook(kaleidoscope::Kaleidoscope_::eventHandlerHook)' is deprecated (declared at /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:171):
------------------------------------------------------------------------
The legacy plugin API based on hook registration is deprecated.

Consider upgrading your plugins, or implementing the new interface
described by `kaleidoscope::Plugin`. In particular, instead of using
`Kaleidoscope.useEventHandlerHook`, implement the
`.onKeyswitchEvent()` method instead.

If your plugins are up-to-date, and you are not a developer, it is
usually safe to ignore this message. Especally if the full error
points to a line containing `legacyLoopHook` or `legacyEventHandler`.
------------------------------------------------------------------------
 [-Wdeprecated-declarations]
   Kaleidoscope.useEventHandlerHook(legacyEventHandler);
                                                      ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-MouseKeys/src/Kaleidoscope-MouseKeys.cpp:142:42: warning: 'static void kaleidoscope::Kaleidoscope_::useLoopHook(kaleidoscope::Kaleidoscope_::loopHook)' is deprecated (declared at /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:178):
------------------------------------------------------------------------
The legacy plugin API based on hook registration is deprecated.

Consider upgrading your plugins, or implementing the new interface
described by `kaleidoscope::Plugin`. In particular, instead of using
`Kaleidoscope.useLoopHook`, implement `.beforeEachCycle`,
`.beforeReportingState()`, or `.afterEachCycle()` instead.

If your plugins are up-to-date, and you are not a developer, it is
usually safe to ignore this message. Especally if the full error
points to a line containing `legacyLoopHook` or `legacyEventHandler`.
------------------------------------------------------------------------
 [-Wdeprecated-declarations]
   Kaleidoscope.useLoopHook(legacyLoopHook);
                                          ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-Macros/src/Kaleidoscope-Macros.cpp: In member function 'virtual void Macros_::begin()':
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-Macros/src/Kaleidoscope-Macros.cpp:222:54: warning: 'static void kaleidoscope::Kaleidoscope_::useEventHandlerHook(kaleidoscope::Kaleidoscope_::eventHandlerHook)' is deprecated (declared at /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:171):
------------------------------------------------------------------------
The legacy plugin API based on hook registration is deprecated.

Consider upgrading your plugins, or implementing the new interface
described by `kaleidoscope::Plugin`. In particular, instead of using
`Kaleidoscope.useEventHandlerHook`, implement the
`.onKeyswitchEvent()` method instead.

If your plugins are up-to-date, and you are not a developer, it is
usually safe to ignore this message. Especally if the full error
points to a line containing `legacyLoopHook` or `legacyEventHandler`.
------------------------------------------------------------------------
 [-Wdeprecated-declarations]
   Kaleidoscope.useEventHandlerHook(legacyEventHandler);
                                                      ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-Macros/src/Kaleidoscope-Macros.cpp:223:42: warning: 'static void kaleidoscope::Kaleidoscope_::useLoopHook(kaleidoscope::Kaleidoscope_::loopHook)' is deprecated (declared at /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:178):
------------------------------------------------------------------------
The legacy plugin API based on hook registration is deprecated.

Consider upgrading your plugins, or implementing the new interface
described by `kaleidoscope::Plugin`. In particular, instead of using
`Kaleidoscope.useLoopHook`, implement `.beforeEachCycle`,
`.beforeReportingState()`, or `.afterEachCycle()` instead.

If your plugins are up-to-date, and you are not a developer, it is
usually safe to ignore this message. Especally if the full error
points to a line containing `legacyLoopHook` or `legacyEventHandler`.
------------------------------------------------------------------------
 [-Wdeprecated-declarations]
   Kaleidoscope.useLoopHook(legacyLoopHook);
                                          ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-LEDControl/src/Kaleidoscope-LEDControl.cpp: In member function 'virtual void kaleidoscope::LEDControl::begin()':
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-LEDControl/src/Kaleidoscope-LEDControl.cpp:261:54: warning: 'static void kaleidoscope::Kaleidoscope_::useEventHandlerHook(kaleidoscope::Kaleidoscope_::eventHandlerHook)' is deprecated (declared at /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:171):
------------------------------------------------------------------------
The legacy plugin API based on hook registration is deprecated.

Consider upgrading your plugins, or implementing the new interface
described by `kaleidoscope::Plugin`. In particular, instead of using
`Kaleidoscope.useEventHandlerHook`, implement the
`.onKeyswitchEvent()` method instead.

If your plugins are up-to-date, and you are not a developer, it is
usually safe to ignore this message. Especally if the full error
points to a line containing `legacyLoopHook` or `legacyEventHandler`.
------------------------------------------------------------------------
 [-Wdeprecated-declarations]
   Kaleidoscope.useEventHandlerHook(legacyEventHandler);
                                                      ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-LEDControl/src/Kaleidoscope-LEDControl.cpp:262:42: warning: 'static void kaleidoscope::Kaleidoscope_::useLoopHook(kaleidoscope::Kaleidoscope_::loopHook)' is deprecated (declared at /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:178):
------------------------------------------------------------------------
The legacy plugin API based on hook registration is deprecated.

Consider upgrading your plugins, or implementing the new interface
described by `kaleidoscope::Plugin`. In particular, instead of using
`Kaleidoscope.useLoopHook`, implement `.beforeEachCycle`,
`.beforeReportingState()`, or `.afterEachCycle()` instead.

If your plugins are up-to-date, and you are not a developer, it is
usually safe to ignore this message. Especally if the full error
points to a line containing `legacyLoopHook` or `legacyEventHandler`.
------------------------------------------------------------------------
 [-Wdeprecated-declarations]
   Kaleidoscope.useLoopHook(legacyLoopHook);
                                          ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-NumPad/src/Kaleidoscope-NumPad.cpp: In member function 'virtual void NumPad_::begin()':
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-NumPad/src/Kaleidoscope-NumPad.cpp:78:42: warning: 'static void kaleidoscope::Kaleidoscope_::useLoopHook(kaleidoscope::Kaleidoscope_::loopHook)' is deprecated (declared at /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:178):
------------------------------------------------------------------------
The legacy plugin API based on hook registration is deprecated.

Consider upgrading your plugins, or implementing the new interface
described by `kaleidoscope::Plugin`. In particular, instead of using
`Kaleidoscope.useLoopHook`, implement `.beforeEachCycle`,
`.beforeReportingState()`, or `.afterEachCycle()` instead.

If your plugins are up-to-date, and you are not a developer, it is
usually safe to ignore this message. Especally if the full error
points to a line containing `legacyLoopHook` or `legacyEventHandler`.
------------------------------------------------------------------------
 [-Wdeprecated-declarations]
   Kaleidoscope.useLoopHook(legacyLoopHook);
                                          ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-LEDEffect-BootGreeting/src/Kaleidoscope-LEDEffect-BootGreeting.cpp: In member function 'virtual void kaleidoscope::BootGreetingEffect::begin()':
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-LEDEffect-BootGreeting/src/Kaleidoscope-LEDEffect-BootGreeting.cpp:92:42: warning: 'static void kaleidoscope::Kaleidoscope_::useLoopHook(kaleidoscope::Kaleidoscope_::loopHook)' is deprecated (declared at /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:178):
------------------------------------------------------------------------
The legacy plugin API based on hook registration is deprecated.

Consider upgrading your plugins, or implementing the new interface
described by `kaleidoscope::Plugin`. In particular, instead of using
`Kaleidoscope.useLoopHook`, implement `.beforeEachCycle`,
`.beforeReportingState()`, or `.afterEachCycle()` instead.

If your plugins are up-to-date, and you are not a developer, it is
usually safe to ignore this message. Especally if the full error
points to a line containing `legacyLoopHook` or `legacyEventHandler`.
------------------------------------------------------------------------
 [-Wdeprecated-declarations]
   Kaleidoscope.useLoopHook(legacyLoopHook);
                                          ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-Model01-TestMode/src/Kaleidoscope-Model01-TestMode.cpp: In member function 'virtual void TestMode_::begin()':
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-Model01-TestMode/src/Kaleidoscope-Model01-TestMode.cpp:18:48: warning: 'static void kaleidoscope::Kaleidoscope_::useLoopHook(kaleidoscope::Kaleidoscope_::loopHook)' is deprecated (declared at /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:178):
------------------------------------------------------------------------
The legacy plugin API based on hook registration is deprecated.

Consider upgrading your plugins, or implementing the new interface
described by `kaleidoscope::Plugin`. In particular, instead of using
`Kaleidoscope.useLoopHook`, implement `.beforeEachCycle`,
`.beforeReportingState()`, or `.afterEachCycle()` instead.

If your plugins are up-to-date, and you are not a developer, it is
usually safe to ignore this message. Especally if the full error
points to a line containing `legacyLoopHook` or `legacyEventHandler`.
------------------------------------------------------------------------
 [-Wdeprecated-declarations]
   Kaleidoscope.useLoopHook(this->legacyLoopHook);
                                                ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-HostPowerManagement/src/Kaleidoscope/HostPowerManagement.cpp: In member function 'virtual void kaleidoscope::HostPowerManagement::begin()':
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-HostPowerManagement/src/Kaleidoscope/HostPowerManagement.cpp:57:42: warning: 'static void kaleidoscope::Kaleidoscope_::useLoopHook(kaleidoscope::Kaleidoscope_::loopHook)' is deprecated (declared at /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:178):
------------------------------------------------------------------------
The legacy plugin API based on hook registration is deprecated.

Consider upgrading your plugins, or implementing the new interface
described by `kaleidoscope::Plugin`. In particular, instead of using
`Kaleidoscope.useLoopHook`, implement `.beforeEachCycle`,
`.beforeReportingState()`, or `.afterEachCycle()` instead.

If your plugins are up-to-date, and you are not a developer, it is
usually safe to ignore this message. Especally if the full error
points to a line containing `legacyLoopHook` or `legacyEventHandler`.
------------------------------------------------------------------------
 [-Wdeprecated-declarations]
   Kaleidoscope.useLoopHook(legacyLoopHook);
                                          ^
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-Focus/src/Kaleidoscope/Focus.cpp: In member function 'virtual void kaleidoscope::Focus::begin()':
/home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-Focus/src/Kaleidoscope/Focus.cpp:146:42: warning: 'static void kaleidoscope::Kaleidoscope_::useLoopHook(kaleidoscope::Kaleidoscope_::loopHook)' is deprecated (declared at /home/fwernli/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/src/Kaleidoscope.h:178):
------------------------------------------------------------------------
The legacy plugin API based on hook registration is deprecated.

Consider upgrading your plugins, or implementing the new interface
described by `kaleidoscope::Plugin`. In particular, instead of using
`Kaleidoscope.useLoopHook`, implement `.beforeEachCycle`,
`.beforeReportingState()`, or `.afterEachCycle()` instead.

If your plugins are up-to-date, and you are not a developer, it is
usually safe to ignore this message. Especally if the full error
points to a line containing `legacyLoopHook` or `legacyEventHandler`.
------------------------------------------------------------------------
 [-Wdeprecated-declarations]
   Kaleidoscope.useLoopHook(legacyLoopHook);
                                          ^
/tmp/tmp.YvHuDSaj9E/sketch/Model01-Firmware.ino.cpp.o: In function `call<kaleidoscope::language::European, kaleidoscope::Key&, unsigned char&, unsigned char&, unsigned char&>':
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:307: undefined reference to `LangPack_EU'
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:307: undefined reference to `LangPack_EU'
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:307: undefined reference to `kaleidoscope::language::European::onKeyswitchEvent(kaleidoscope::Key&, unsigned char, unsigned char, unsigned char)'
/tmp/tmp.YvHuDSaj9E/sketch/Model01-Firmware.ino.cpp.o: In function `kaleidoscope::EventHandlerResult kaleidoscope_internal::EventDispatcher::apply<kaleidoscope_internal::EventHandler_onSetup>()':
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:307: undefined reference to `LangPack_EU'
/home/fwernli/git/Model01-Firmware/Model01-Firmware.ino:307: undefined reference to `LangPack_EU'
collect2: error: ld returned 1 exit status
exit status 1
/home/fwernli/Arduino/hardware/keyboardio/avr/build-tools/makefiles//rules.mk:72: recipe for target 'build-all' failed
make: *** [build-all] Error 1
```


😄 I also moved the new entry to the bottom. We've always listed items in each release top-to-bottom as you'd write a document, just the releases the other way so you don't have to scroll to the bottom.


I see you did [not ](http://tests.stockfishchess.org/tests/view/5b1fbeda0ebc5902ab9c8e96)consider my suggestion at this [commit](https://github.com/official-stockfish/Stockfish/commit/9646f23d3848b86ca072c3479bf45073608496d0), why?


Pos, is that chunk id?


@maslianok I so sorry for it, next time I will bring the issue to the discussion before doing it!
thank you for your comment!


Looks like this issue: https://github.com/flatpak/flatpak-builder/issues/155


图片显示不全


added


Using Ansible defaults better integrates with the Travis testing strategy used by https://github.com/ansibleplaybookbundle/hello-world-apb.

Basically, it supposes that your APB should be runnable without any params.


Another one of the things that I should have added a long time ago


про вагоны )
идея использовать модуль, чтобы не дублировать код хорошая
но есть одно "но"... или даже не одно ))
и появляются все эти "но" из-за того, что у тебя здесь речь идет наследниках класса Вагон
вот какие моменты нужно обдумать и поправить:
1. зачем выносить функционал в модуль, если вполне логично поместить его в родительский класс ?
2. не очень хорошо,  что в модуле используются переменные, которые в нем не определены и "наверное будут определены" в классах, куда модуль подключается... это как-то попахивает... вот если бы модуль сам добавлял эти переменные в класс и потом к ним обращался, но это уже заметно более сложный код ))
3. зачем в обоих наследниках есть `initialize`, если его можно также написать в родителе и из наследников толлько передавать в родителя "тип"
4. методы `take_seat` и `load`, если подумать очень похожи... можно определить общий метод в родителе, а в наследниках (наследнике) его переопредлить (чуть-чуть) и вызвать `super`
5. в КаргоКэрридж метод загрузки с кодом `@taken += number if number <= @capacity` позволит загрузить бесконечный груз в вагон, лишь бы каждая порция была меньше максимальной грузоподъемности
6. в ПэсснджерКэрридж в методе "тейк сит"  `@capacity - @taken` - это именно то, что ты определил в методе `available`, было бы правильно восопльзовать этим методом

резюме по вагонам:
- от модуля нужно откзаться в пользу наследования
- инишиалайз перенести в родителя, а в наследниках переопределить с вызовом "супер", чтобы передать в родителя тип
- метод загрузки также определить в родителе, а в наследниках (наследнике?) переопределить по необходимости

подсказка на подсказке ))))


Merging branches


I think it is more or less the same logic here. Let's use an example to compare the behaviors of this proposal and yours.

We have a trigger every t=5. So the first time it is scheduled for t=5. Actually, the code runs at t=4.9.
 - With your suggestion, we are scheduling the next run at 5 again. Then when we run we check and we say: hey, I already run at t=5, then let's schedule for the next time;
 - With my proposal we are doing the following. We check now it is t=4.9, but I was supposed to run at t=5. Then let's schedule the next time after t=5 (instead of after now, ie. after t=4.9, which is causing the issue).

Of course if the time of the run is >= of the time of scheduling there is no issue in both proposals (and in the current codebase).

S I think my current proposal is a bit more efficient, as it avoid to trigger a useless run in which we just check whether we should really run or not and then eventually return.

What do you think?


There's an icon for this, we're using it in the tags editor inside the note editor


IT and ERP Issues added again


Sorry Günther, I simply don't see your comment. However I receive it by email now :-)


` Hazelcast IMDG is the most widely used in-memory data grid with hundreds of thousands of installed clusters around the world. It offers caching solutions ensuring that data is in the right place when it’s needed for optimal performance.` We can put all execution related wording to hazelcast-jet helm chart when we have it.


Will be reverted in 5 minutes @dbe-odoo since it crashes `mass_mailing` if `website` is not installed


Indeed that's the same. It is @hughsie who noticed this inconsistency for us.

In your case, does it prevent the appdata to be properly parsed? That is our main problem, which neither flathub nor GNOME Software (and maybe others) use our appdata and we could not figure why yet. We hope this will fix it.


say what? both assumptions in that statement are simply wrong.


Why do we need to configure this? Isn't it fixed?


I suggest DS pulls directly to `/home/$UNAME/.docker` (not `/home/$UNAME/.docker/DockSTARTer`). so generally your folder structure would look something like this:
```
/home/$UNAME/.docker
/home/$UNAME/.docker/.git
/home/$UNAME/.docker/compose
/home/$UNAME/.docker/config
/home/$UNAME/.docker/docs
/home/$UNAME/.docker/scripts
/home/$UNAME/.docker/test
etc
```

I don't disagree we could (should) change it in `.env`. I would also think we should at least mention somewhere that it's a good idea to symlink your config folder to another location (like an external drive mounted somewhere else). that's the reason I have it set how it is in `.env` right now.


No problem ;-)


isn't those heap sizes are too low?


Fixes #1


@fyshi with `BreakWaterAbsorbCoef` being hard coded before and yielding 10.0 in sponges.F , do you feel we should default `BreakWaterAbsorbCoef` to 10.0 instead of 1.0 now in io.F? It might create the same confusion as `EqualEnergy` default option did between version 2.2/3.0 and 3.2 with all previous version being `EqualEnergy` by default, but 3.2 default to EqualEnergy=F. Speaking of which, might consider changing it too.

If the `BreakWaterAbsorbCoef` defaults to 1.0 now, people with previous widths they set of internal breakwater sponges would get completely different absorption/reflection.


negative numbers aren't working though


kkkkkkkkkkkkk


同意合并。


if we recommend that then liveness probe will not work right?


Worth setting `canUpdate` back to true in case this fails?


принципиально технология использована правильно )
но лучше конечно использовать здесь `each` - это рекомендуемый способ прохождения по элементам массива в руби
твой код в таком виде скорее похож на код на каком-то другом языке (JS, Java или еще что-то), но не на руби ))


Maybe use same wording here as suggested by @mesutcelik ?


аналогичный комментарий к классу Поезд


quicksort


@danuker I still find it a valuable improvement — with `https` enabled we can (to some reasonable extent) rely on _authenticity_ of the prices fetched from Etherscan.
And this authenticity closes, for example, the "price-manipulation" attach vectors, where the client is tricked into sending more money than they should, because some third party was able to alter the content of the Etherscan response mid-flight.

I also think that connecting to Etherscan is far from being the only indicator of the user's interest in Ethereum, given they run a Parity node — and I don't think that it's too hard to determine the fact of running Parity if one have a capability to eavesdrop on the client's traffic.


웹 서버 연결전 작업


is it normal to use beta version of the API?


So should I revert this and change the import statements to only import `Language.Drasil`? Because then it can't find its imports:

```
[15 of 19] Compiling Language.Drasil.Chunk.Code ( Language\Drasil\Chunk\Code.hs, .stack-work\dist\ca59d0ab\build\Language\Drasil\Chunk\Code.o )

C:\Users\samcr\Desktop\Summer Research\Drasil\code\Language\Drasil\Chunk\Code.hs:56:23: error:
    Not in scope: type constructor or class `Decoration'
    Perhaps you meant `Derivation' (imported from Language.Drasil)

C:\Users\samcr\Desktop\Summer Research\Drasil\code\Language\Drasil\Chunk\Code.hs:57:12: error:
    Not in scope: data constructor `Hat'
    Perhaps you meant variable `hat' (imported from Language.Drasil)

C:\Users\samcr\Desktop\Summer Research\Drasil\code\Language\Drasil\Chunk\Code.hs:58:12: error:
    Not in scope: data constructor `Vector'
    Perhaps you meant `Vect' (imported from Language.Drasil)

C:\Users\samcr\Desktop\Summer Research\Drasil\code\Language\Drasil\Chunk\Code.hs:59:12: error:
    Not in scope: data constructor `Prime'
    Perhaps you meant variable `prime' (imported from Language.Drasil)

--  While building custom Setup.hs for package drasil-code-0.0.9 using:
      C:\sr\setup-exe-cache\x86_64-windows\Cabal-simple_Z6RU0evB_1.24.2.0_ghc-8.0.2.exe --builddir=.stack-work\dist\ca59d0ab build lib:drasil-code --ghc-options " -ddump-hi -ddump-to-file"
    Process exited with code: ExitFailure 1
make: *** [build_code] Error 1
```


good point. I agree the default should be BreakWaterAborbCoef = 10.0 which keeps consistent with the previous version. Doing right now


LGTM with a minor comment 👍


Did not get the sense of this condition ... may you want to check for StringUtils.isEmpty(urIish.getHost()) ?


и еще... я посмотрел у тебя индекс присутствует и в методе и в вызывающем коде... какая-то явная путанница
но при переходе к `each` индекс тебе больше не понадобится )) по крайней мере такой... "ручной"
если нужен индекс - используй [`each_with_index`](https://ruby-doc.org/core-2.5.1/Enumerable.html#method-i-each_with_index)
а вот [тут](https://ruby-doc.org/core-2.5.1/Array.html) можно посмотреть документацию к методам массива


It works now.  Thanks for the update.


delete


Ha ok ... reading the comment can help ;-) ... in case no host is there urIish host should be emty as well?


Do you still need pgrep ?


and?


yes urlish is read from jenkins you have always the host part. Unfortinatly the ootb webhook implementation does not transfer any host information. hence GitStatus.loosleyMatches will never match. Therefore the host is set to be always equal.


@kasatelli Ok check it out lemme know if it works


box mobile


box tablet


box desktop


after my message...


too risky (but ok assuming it is in master)


Looking at the PR for WSAPI, it seems there are already quite a few changes. What was the motivation for having WSAPI deviate from the style guide?


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 139](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=1880&buildTypeId=XbimEssentials_XbimEssentials) is now running


Correct, it's backward compatible. Not sure about the version numbers yet, given the current release situation, and the PR hasn't been merged.


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 139](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=1880&buildTypeId=XbimEssentials_XbimEssentials) outcome was **SUCCESS**
Summary: Running Build time: 00:01:31


Why did you add a function to set the ID? This should not be allowed.


Wynik działania metody findFlight nie jest do niczego przypisany, operacja się wykona ale nie będziesz znał wyniku. Dodaj to i wyświetlenie otrzymanej wartości


Related #1893


<details>

<summary>Submitting the task to Taskcluster failed. Details</summary>

You do not have sufficient scopes. You are missing the following scopes:

{
  "AnyOf": \[
    {
      "AnyOf": \[
        "queue:create\-task:highest:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:very\-high:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:high:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:medium:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:low:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:very\-low:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:lowest:aws\-provisioner\-v1/servo\-docker\-worker"
      \]
    },
    {
      "AnyOf": \[
        "queue:create\-task:aws\-provisioner\-v1/servo\-docker\-worker",
        {
          "AllOf": \[
            "queue:define\-task:aws\-provisioner\-v1/servo\-docker\-worker",
            "queue:task\-group\-id:taskcluster\-github/R\_M6wlVeT52BrRJEuBxFsA",
            "queue:schedule\-task:taskcluster\-github/R\_M6wlVeT52BrRJEuBxFsA/R\_M6wlVeT52BrRJEuBxFsA"
          \]
        }
      \]
    }
  \]
}

You have the scopes:

```
\[
  "assume:project:taskcluster:mozilla\-github\-repository",
  "assume:repo:github.com/servo/servo:pull\-request",
  "notify:email:\*",
  "notify:irc\-channel:\*",
  "notify:irc\-user:\*",
  "queue:create\-task:aws\-provisioner\-v1/github\-worker",
  "queue:create\-task:aws\-provisioner\-v1/github\-worker\-windows",
  "queue:create\-task:aws\-provisioner\-v1/servo",
  "queue:create\-task:aws\-provisioner\-v1/win2012r2",
  "queue:route:garbage.\*",
  "queue:route:index.garbage.\*",
  "queue:route:notify.email.\*",
  "queue:route:notify.irc\-channel.\*",
  "queue:route:notify.irc\-user.\*",
  "queue:scheduler\-id:taskcluster\-github",
  "secrets:get:garbage/\*",
  "secrets:set:garbage/\*"
\]
```

This request requires you to satisfy this scope expression:

```
{
  "AllOf": \[
    {
      "AnyOf": \[
        {
          "AllOf": \[
            "queue:scheduler\-id:taskcluster\-github",
            {
              "AnyOf": \[
                "queue:create\-task:highest:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:very\-high:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:high:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:medium:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:low:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:very\-low:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:lowest:aws\-provisioner\-v1/servo\-docker\-worker"
              \]
            }
          \]
        },
        {
          "AnyOf": \[
            "queue:create\-task:aws\-provisioner\-v1/servo\-docker\-worker",
            {
              "AllOf": \[
                "queue:define\-task:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:task\-group\-id:taskcluster\-github/R\_M6wlVeT52BrRJEuBxFsA",
                "queue:schedule\-task:taskcluster\-github/R\_M6wlVeT52BrRJEuBxFsA/R\_M6wlVeT52BrRJEuBxFsA"
              \]
            }
          \]
        }
      \]
    }
  \]
}
```
----
method:     createTask
errorCode:  InsufficientScopes
statusCode: 403
time:       2018-06-12T13:38:37.160Z

</details>


Can you run `make VERBOSE=1`? That'll give me more info about what arguments the builder is trying to call gcc with.


add ex44e.py


<details>

<summary>Submitting the task to Taskcluster failed. Details</summary>

You do not have sufficient scopes. You are missing the following scopes:

{
  "AnyOf": \[
    {
      "AnyOf": \[
        "queue:create\-task:highest:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:very\-high:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:high:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:medium:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:low:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:very\-low:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:lowest:aws\-provisioner\-v1/servo\-docker\-worker"
      \]
    },
    {
      "AnyOf": \[
        "queue:create\-task:aws\-provisioner\-v1/servo\-docker\-worker",
        {
          "AllOf": \[
            "queue:define\-task:aws\-provisioner\-v1/servo\-docker\-worker",
            "queue:task\-group\-id:taskcluster\-github/ToSj8Z6MRa\-7W2xR0Lh7zQ",
            "queue:schedule\-task:taskcluster\-github/ToSj8Z6MRa\-7W2xR0Lh7zQ/ToSj8Z6MRa\-7W2xR0Lh7zQ"
          \]
        }
      \]
    }
  \]
}

You have the scopes:

```
\[
  "assume:project:taskcluster:mozilla\-github\-repository",
  "assume:repo:github.com/servo/servo:pull\-request",
  "notify:email:\*",
  "notify:irc\-channel:\*",
  "notify:irc\-user:\*",
  "queue:create\-task:aws\-provisioner\-v1/github\-worker",
  "queue:create\-task:aws\-provisioner\-v1/github\-worker\-windows",
  "queue:create\-task:aws\-provisioner\-v1/servo",
  "queue:create\-task:aws\-provisioner\-v1/win2012r2",
  "queue:route:garbage.\*",
  "queue:route:index.garbage.\*",
  "queue:route:notify.email.\*",
  "queue:route:notify.irc\-channel.\*",
  "queue:route:notify.irc\-user.\*",
  "queue:scheduler\-id:taskcluster\-github",
  "secrets:get:garbage/\*",
  "secrets:set:garbage/\*"
\]
```

This request requires you to satisfy this scope expression:

```
{
  "AllOf": \[
    {
      "AnyOf": \[
        {
          "AllOf": \[
            "queue:scheduler\-id:taskcluster\-github",
            {
              "AnyOf": \[
                "queue:create\-task:highest:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:very\-high:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:high:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:medium:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:low:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:very\-low:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:lowest:aws\-provisioner\-v1/servo\-docker\-worker"
              \]
            }
          \]
        },
        {
          "AnyOf": \[
            "queue:create\-task:aws\-provisioner\-v1/servo\-docker\-worker",
            {
              "AllOf": \[
                "queue:define\-task:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:task\-group\-id:taskcluster\-github/ToSj8Z6MRa\-7W2xR0Lh7zQ",
                "queue:schedule\-task:taskcluster\-github/ToSj8Z6MRa\-7W2xR0Lh7zQ/ToSj8Z6MRa\-7W2xR0Lh7zQ"
              \]
            }
          \]
        }
      \]
    }
  \]
}
```
----
method:     createTask
errorCode:  InsufficientScopes
statusCode: 403
time:       2018-06-12T13:39:49.176Z

</details>


`<<a b c>>` is actually `qqww/a b c/` not `qqw/a b c/`


My plan is to work with `-p` first. Currently, I am working in `apply_autostash()`. Maybe working in `--am` after this would be better. What do you think?


.catch(callback) may be good here