This change has been applied in #2068 - currently in 51f08defcba7380f67219f280f0ef484bf6f441b.


「,」後面請接一個半形空白


Добавил.
Почему-то при копировании методов, IDEA удаляет некоторые табуляторы. Надеюсь ничего не пропустил...


before_action 與下方 method 之間通常會留一空白行。


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4498](https://teamcity.mesosphere.io/viewLog.html?buildId=72424&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:58


Intended?


Shouldn't this be `cd `git rev-parse --show-toplevel`; $(RM) -f filesystem/apps/sodium/*bin build/$(ARCH)/sodium*; make qemu; cd -;`?


Rozwiązanie bardzo dobre. Moje byłoby "mniej obiektowe" ale coś podobnego miałem na uwadze.
Czy tą paginację będziesz robił również dla nodes oraz historii operacji?


請指定新增的欄位要插入的位置，否則預設會擺到最後面。

例如：
```ruby
add_column :users, :name, :string, after: :email
```


請縮排 2 spaces


@bobsummerwill It's understandable. I saw the issue regarding Jenkins. Will reply there.


Explain this please


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4503](https://teamcity.mesosphere.io/viewLog.html?buildId=72435&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:58


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4495](https://teamcity.mesosphere.io/viewLog.html?buildId=72421&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:17:56
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4501](https://teamcity.mesosphere.io/viewLog.html?buildId=72431&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:01:25


Tracę już cierpliwość :( Wrzucam ten projekt od 2 dni :(


왜 이런 알 수 없는 말을 적었나요?


즐


No indeed, for some reason my search results got mixed up, redoing them again..


Można by zrobić to już dla wszystkich list. Schemat wszędzie byłby taki
sam. I pozbyć się tej starej paginacji która była zbyt skomplikowana i
generalnie nie działała dobrze. Ale chwilowo brakuje mi czasu na to..

W dniu 11.11.2015 o 12:19, nicraMarcin pisze:
>
> Rozwiązanie bardzo dobre. Moje byłoby "mniej obiektowe" ale coś
> podobnego miałem na uwadze.
> Czy tą paginację będziesz robił również dla nodes oraz historii operacji?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/lmsgit/lms/commit/9930c55b67c9e534c3293ffca2c33a57c0013cd0#commitcomment-14326325>.
>

--
lion.net.pl - wdrożenia i rozwój Lan Management System


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4504](https://teamcity.mesosphere.io/viewLog.html?buildId=72436&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:01:37


@adrelanos could you check this commit (debian packaging of kernel module and initramfs module)?
Independently I should learn how to use `lintian`...


@moifort the application name needs to be `<%= baseName %>` instead of jhipster, i have corrected en and fr but needs correction in remaining languages as well


Ok, to ja w ramach "pracy domowej" i zapoznawania się z kodem to zrobię, ale jak mówiłem na liście, chwilę to potrwa.


VS didn't like it being a bool, you can't win :P


actually, both keys differ in both datasets, as they are a numeric sequence.


Ich glaube in dieser Tabelle waren Fehler: Habe es geändert gemäß Issue #14


*two additional keys :wink:


Всё хорошо, только вот это странный момент: зачем надо было захардкоживать здесь строчку? Если это осталось после отладки, то нужно убрать.


as well as keeping any number of conversations active. ;)


I don't owe you any explanation!


Damn, you’re up early (or going to bed late!).

I couldn’t get to the keyboard yesterday as I had a full day/night of other engagements.  But I’m sitting in front of the debugger right now.  I hope to have a solution by our meeting tonight.

-d

From:  Ryan Balfanz <notifications@github.com>
Reply-To:  dkannenberg/bloc-jams <reply@reply.github.com>
Date:  Wednesday, 11 November 2015 10:55
To:  dkannenberg/bloc-jams <bloc-jams@noreply.github.com>
Cc:  Derek Kannenberg <kannenberg@gmail.com>
Subject:  Re: [bloc-jams] assignment 27 (5aeebe7)

@dkannenberg Had a chance to fix this yet?

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


with /either/


I love this kind of Christmas gift ;)


Yeah that is because of an incomplete add. I'm still working on another thing that isn't finished, hence why I pushed incomplete additions. Sorry


looks good. gtk3 build runs well in gtk2 enviroment :smile:


ここは
```ruby
(1..100).each(&:printf)
```
でいいのかな


I'd like to see brackets here...


/optional/


It would be nice to avoid adding the **internal** Database property which breaks [encapsulation](http://blog.ploeh.dk/2015/09/22/unit-testing-internals/). I see the property is used only once in the `FakeStandardValuesProvider.DataStorage()` method. The the method receives a database as a *parameter* unlike the similar method from the `FakeDataProvider` class which uses *Database* property:
```csharp
// FakeDataProvider
public virtual DataStorage DataStorage()
{
  return DataStorageSwitcher.CurrentValue(this.Database.Name);
}

// FakeStandardValuesProvider
public virtual DataStorage DataStorage(string databaseName)
{
  return DataStorageSwitcher.CurrentValue(databaseName);
}
```

Is it possible to inject the *Database* into the `FakeStandardValuesProvider` somehow so that the methods became identical?


Hi Maurizio,

Landed here: https://github.com/vszakats/harbour-core/commit/d684b5806e21a13fd9580083356d7c39d07e70fa
(with a minor optimisation and keeping support for `ENDFOR` keyword logic, plus some style nits)

It'd be probably simpler if you asked Przemek directly about this, or you can also commit directly to the mainline Harbour tree, if you feel like doing so.

I haven't discovered new `hbformat` issues (admittedly haven't tried very hard either), so this few years old list inside the source code can still be used as a reference for outstanding ones: https://github.com/vszakats/harbour-core/blob/d684b5806e21a13fd9580083356d7c39d07e70fa/contrib/hbformat/hbfmtcls.prg#L57-L76

BTW, `hbformat` was lately integrated by @hernad into an [Atom editor](https://atom.io) [plugin](https://atom.io/packages/harbour-plus) ([broken](https://github.com/hernad/atom-harbour-plus/issues/1) at the moment unfortunately), meaning you can be using it from inside the editor, quite cool!


s/require/requires/


Here and in other tests's names: s/abbreviate/abbreviated/


Yeah, we know, but we decided to add it just in case, as we were writing the paper with a journal in mind.


Ok work my fault. thank you :)


could you change the DBAdapter and generate unit tests to a working instance of BioMart, so that the tests are running through again.


@nicraMarcin: super

Ja zaraz puszczę poprawki do nowej paginacji + przywrócenie identycznego jak dla scroller-a wyświetlania informacji.


This ticker is too close to be merged :)


Accidentally the whole comment.


Yeah, another attribute in the element.  It would need two parameters, at
least: how often to wait for a response, and how much to wait between tries.

This is only an issue, however, with really slow clouds (elastx), or really
heavy lab environments.  The only reason we don't wait forever is that
since this is an asynchronous task, if the student gives up waiting, we
would retry forever.  The point is that it's probably enough to just set
this to as high as would be tolerable for a student to wait.  Anything
longer can be considered an error, and must be fixed in other ways.

For instance, I think that the time elastx takes to fire up a 4-node stack
is an example of something that is not tolerable.  I think 2 minutes is the
ceiling, and we're waiting for something around 10.


logAboutAbsentPage() should pass abbreviated page when it's too long
так?


Poszło d91f5bcf69d3885437f050bd0e8e0c7f59b4ca8d


It's the way we tell the browser to actually install this app
https://developer.mozilla.org/en-US/docs/Web/API/DOMApplicationsRegistry/install

Although it seems that this is considered deprecated. We should probably remove it and have the app only on Marketplace.


TeamCity TripleA :: UnitTest [Build 20](http://188.177.191.210/viewLog.html?buildId=79&buildTypeId=TripleA_UnitTest&guest=1) is now running


I thinks， here have a issue, if process start failed and throw exception, we can not open any process's start button.


@emcho Unfortunately it won't compile with Smack3 that currently in use with sip communicator. This issue might be resolved with excluding the Smackv4 layer file from Ant build, but I suggest that it won't give you the most possibly targeted behavior to access Smackv4 interop layer within sc-bundles JARs.


TeamCity TripleA :: UnitTest [Build 20](http://188.177.191.210/viewLog.html?buildId=79&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 37 Build time: 00:01:02


Va a romper aca, es ssin _


User common notification for successful start process.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4502](https://teamcity.mesosphere.io/viewLog.html?buildId=72432&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:17:52
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


I'd rather write it this way:
```js
if (task.screenshots.hasCapturedFor(testRun.test))
    reportItem.screenshotPath = task.screenshots.getPathFor(testRun.test);
```


ega


`opts` should be the last argument


Here we can create `capturer` and pass it to the `testRun` instead of `screenshots`


TeamCity TripleA :: UnitTest [Build 21](http://188.177.191.210/viewLog.html?buildId=80&buildTypeId=TripleA_UnitTest&guest=1) is now running


Há quase um ano (#332) eu dei uma sugestão para o README. Para considerações futuras, irei anexá-la aqui:

```md
### Setup do projeto em ambientes Unix com o GVM

O GVM (http://gvmtool.net/) -- Grails Version Manager -- é uma ferramenta para gerenciamento de versões de Groovy e de Grails (parecida com o mais famoso [RVM](http://rvm.io)). Com ele, pra rodar o RGMS a partir do 0, você só precisa:

* Estar em um ambiente (S.O.) Linux;
* Abrir um terminal de linha de comando;
* Instalar o GVM `curl -s get.gvmtool.net | bash`
* Fechar o terminal e abrir novamente (pra que a instalação do GVM faça efeito);
* Instalar o groovy (o comando abaixo irá instalar a versão estável mais recente)
`gvm install groovy`
* Instalar a versão do Grails que o projeto especifica
`gvm install grails 2.1.0`
* Fazer o clone do repositório
`git clone git@github.com:spgroup/rgms.git`
* Mudar para o diretório do projeto e executar a aplicação:
`cd rgms && grails run-app`

Obs.:

* A aplicação estará disponível através do endereço http://localhost:8080/rgms
* Escolha sim (Y) depois da instalação do Groovy e do Grails para que eles sejam setados como versões padrão em uso no sistema
Qualquer dúvida, manda aí.
```


That works too.


TeamCity TripleA :: UnitTest [Build 21](http://188.177.191.210/viewLog.html?buildId=80&buildTypeId=TripleA_UnitTest&guest=1) outcome was **FAILURE**
Summary: Tests failed: 12, passed: 37 Build time: 00:00:16
### Failed tests
```
CashRegister.Test.Unit.dll: CashRegister.Test.Unit.Sales.SalesControllerUnitTest.CTorSalesController_SettingLocalPaymentProviderList_ListIsSet: <no details avaliable>

CashRegister.Test.Unit.dll: CashRegister.Test.Unit.Sales.SalesControllerUnitTest.SalesController_AddTransaction_OrderControllerAddTransactionIsCalled: <no details avaliable>

CashRegister.Test.Unit.dll: CashRegister.Test.Unit.Sales.SalesControllerUnitTest.SalesController_CallingAddProductOrderController_OrderControllerAddingProductIsCalled: <no details avaliable>

CashRegister.Test.Unit.dll: CashRegister.Test.Unit.Sales.SalesControllerUnitTest.SalesController_CancelOrder_OrderControllerClearOrderIsCalled: <no details avaliable>

CashRegister.Test.Unit.dll: CashRegister.Test.Unit.Sales.SalesControllerUnitTest.SalesController_CancelOrder_OrderControllerMissingAmountIsCalled: <no details avaliable>

CashRegister.Test.Unit.dll: CashRegister.Test.Unit.Sales.SalesControllerUnitTest.SalesController_CancelOrder_OrderControllerSaveOrderIsCalled: <no details avaliable>

CashRegister.Test.Unit.dll: CashRegister.Test.Unit.Sales.SalesControllerUnitTest.SalesController_CancelOrder_StartNewOrderIsCalled: <no details avaliable>

CashRegister.Test.Unit.dll: CashRegister.Test.Unit.Sales.SalesControllerUnitTest.SalesController_ClearOrder_OrderControllerClearOrderIsCalled: <no details avaliable>

CashRegister.Test.Unit.dll: CashRegister.Test.Unit.Sales.SalesControllerUnitTest.SalesController_MissingPayment_OrderControllerMissingAmountIsCalled: <no details avaliable>

CashRegister.Test.Unit.dll: CashRegister.Test.Unit.Sales.SalesControllerUnitTest.SalesController_RemoveProductFromOrderList_OrderControllerAddingProductIsCalled: <no details avaliable>

CashRegister.Test.Unit.dll: CashRegister.Test.Unit.Sales.SalesControllerUnitTest.SalesController_RetrieveIncompleteOrder_OrdercontrollerGetStashedOrderIsCalled: <no details avaliable>

##### there are 2 more failed tests, see build details
```


Yes - I think I will go down that road - I mean rip it off and let it blow (if it blows) - NB: it used to fallback to Oblivion.esm no matter what which rings a bell like "Bug bug":

c33859b67e68384d9ae474dc5965cacc4b86b91b


extra bool?


This function now returns a string, not a list.


We have `array-find` for this: https://github.com/inikulin/testcafe/blob/master/package.json#L6


Updated with a new commit containing the necessary fixes that are related to this commit - https://github.com/mksh/jitsi/commit/f71e227f0ff38cd3a528b8b1b85b148a1c3aa18f . I'm not rebasing that into the single commit to not affect this conversation, but looking forward to perform rebase before merging my PR


I think it's `testEntry` or smthg


It's `this.testEntries`


これはループの中に入れなくてもいいんちゃう？
一回だけ実行すればOKなので。


これもかな。


good code btw


> `d="M4 12.5h10"/>`

Исправь на `d="M4 12.5h11"/>`, а то виднеется линия между частями стрелки:
![screenshot_20151111144606](https://cloud.githubusercontent.com/assets/1163958/11090465/312fa868-8883-11e5-9bb2-47b2587de01e.png)


We shouldn't store capturers, instead we should pass `screenshots` to the capturer and on screenshot capturer should set `hasScreenshots` for the appropriate test entry.


Воо, это дело!


With symtab creation code


TeamCity TripleA :: UnitTest [Build 22](http://188.177.191.210/viewLog.html?buildId=81&buildTypeId=TripleA_UnitTest&guest=1) is now running


TeamCity TripleA :: UnitTest [Build 22](http://188.177.191.210/viewLog.html?buildId=81&buildTypeId=TripleA_UnitTest&guest=1) outcome was **FAILURE**
Summary: Compilation error: Software\TripleA\CashRegister\CashRegister.csproj (new); compilation error: Software\TripleA\TripleA.sln (new); number of tests is too small: 0 (new) Build time: 00:00:04


TeamCity TripleA :: UnitTest [Build 23](http://188.177.191.210/viewLog.html?buildId=82&buildTypeId=TripleA_UnitTest&guest=1) is now running


TeamCity TripleA :: UnitTest [Build 23](http://188.177.191.210/viewLog.html?buildId=82&buildTypeId=TripleA_UnitTest&guest=1) outcome was **FAILURE**
Summary: Compilation error: Software\TripleA\TripleA.sln; number of tests is too small: 0 Build time: 00:00:07


TeamCity TripleA :: UnitTest [Build 24](http://188.177.191.210/viewLog.html?buildId=83&buildTypeId=TripleA_UnitTest&guest=1) is now running


TeamCity TripleA :: UnitTest [Build 24](http://188.177.191.210/viewLog.html?buildId=83&buildTypeId=TripleA_UnitTest&guest=1) outcome was **FAILURE**
Summary: Tests passed: 37; number of inspection errors is too large: 40 (new) Build time: 00:00:12


AFAIK this should never happen, since we always create capturer for the test.


Во-первых — тут, на самом деле, если сначала сделать `map{|x| x['producer']}` — то дальше sort и uniq упростятся.
А во-вторых — хорошо бы режиссёров по фамилии всё же отсортировать.


Varför inte jQuery här? Vore också nice om den bytte citat lite med lite mellanrum


We should always have `testInfo`, see above


Ну да!


Yes. I'll check all REST javadoc.


According to wapidoc [1] for 'extensibleattrobutedef', object may look like:

class EADef(InfobloxObject):
    _infoblox_type = 'extensibleattributedef'
    _fields = ['comment', 'default_value', 'name',
                    'namespace', 'type']
    _search_fields = ['name']
    _return_fields = ['comment', 'default_value', 'name',
                               'namespace', 'type']

[1] https://172.23.25.175/wapidoc/objects/extensibleattributedef.html?highlight=extensibleattributedef


You could add your favorit color


In which cases `takeScreenshot` may throw?


The proper way to do it is
rc = ibv_dereg_mr(..)
ACCERT_TRUE(rc == 0)

There is no need to add user messages.

For example, from my test:
[ RUN      ] tc_verbs_create_cq.ti_1
tests/cross-channel/cc_verbs_test.h:149: Failure
Value of: ctx->mqp != NULL
  Actual: false
Expected: true
[  FAILED  ] tc_verbs_create_cq.ti_1 (14 ms)


Good catch. Thanks


`opts` should be last arg


"Nordic.js Mini-Sumo Robo Clash Attendee" tycker jag blir bättre


We don't need `screenshots` here


favorit color?


Please don't use defines inside the class.


New Card


`s/Varadic/Variadic`!


`capturer` should have `enabled` as well, so we will not need `screenshots` here


favorit color


Bry er inte om vilken kod där står. Det är när man skapar ett Javadoc


Si, lo cambié en un commit dps


It's a question for my knowledge. When you apply the plugin "nuget-base", is it applying the plugin "nuget" which itself is applying "base" ?


I'm wondering, maybe we should just pass `err` object here? We can perform `err.screenshotRequired` check inside  `captureForError` as well then.


most of this includes are part of common.h
Please use the following structure:
#include "common.h"
#include <infiniband/verb_exp.h>

And don't forget to check the HAVE_INFINIBAND_VERBS_EXP_H define.
In my setup this code will fail to build.


please be less self-critical in a public repo. To make sure you don't make such a mistake in the future, consider making smaller commits.


Minor: Did you intentionally use a `when 'flat'` clause here rather than an `else`? It seems a bit inconsistent with what you've done elsewhere, but I might be missing something. I guess the advantage of what you've done is that if a new option is added, then a developer would have to explicitly change the logic to avoid an error.


Насчёт zip — отличная догадка, апплодирую (хотя `line_format` лучше сделать константой, так код лучше читается: сразу видно, что никто не собирается по ходу пьесы формат данных менять).

А вот разобраться, как заменить each_line+push на map — всё же надо. Логика тут простая, на самом деле:
1. Прочитать файл как массив строк (например, с помощью readlines)
2. Превратить этот массив строк в массив хешей (с помощью map)


That variable is a bit of a waste of time, no? :smiley:

(don't have to fix it, your call)


Maybe we should pass `msg` directly here? And rename method to `captureForAction` or smthg
\cc @VasilyStrelyaev


!3 => ".ST_CUSTDELIVERY."


Looks good but I'm not sure I understand your comments on lines 144-146 in `utils.py`. You say not to use it but then you use it in the templates? It almost looks like it shouldn't be here.

Also can you change the comment on lines 133-136 to:

```
# Add a unique dict filter, by key.
# DEPRECATION WARNING: This is only used for backwards compatibility,
#                      please use the unique filter instead
```


TeamCity TripleA :: UnitTest [Build 25](http://188.177.191.210/viewLog.html?buildId=84&buildTypeId=TripleA_UnitTest&guest=1) is now running


Ok


TeamCity TripleA :: UnitTest [Build 25](http://188.177.191.210/viewLog.html?buildId=84&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 37 Build time: 00:00:12


TeamCity TripleA :: UnitTest [Build 26](http://188.177.191.210/viewLog.html?buildId=85&buildTypeId=TripleA_UnitTest&guest=1) is now running


TeamCity TripleA :: UnitTest [Build 27](http://188.177.191.210/viewLog.html?buildId=86&buildTypeId=TripleA_UnitTest&guest=1) is now running


TeamCity TripleA :: UnitTest [Build 26](http://188.177.191.210/viewLog.html?buildId=85&buildTypeId=TripleA_UnitTest&guest=1) outcome was **FAILURE**
Summary: Compilation error: Software\TripleA\TripleA.sln (new); number of tests is too small: 0 (new) Build time: 00:00:06


TeamCity TripleA :: UnitTest [Build 27](http://188.177.191.210/viewLog.html?buildId=86&buildTypeId=TripleA_UnitTest&guest=1) outcome was **FAILURE**
Summary: Tests passed: 37; number of inspection errors is too large: 40 (new) Build time: 00:00:12


If you put it here, the translation string would be `dialogue.do-not-track`. I think the tracking stuff should either have its own `tracking` namespace and use e.g. `tracking.do-not-track` or we can just put it on the `de` level.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4506](https://teamcity.mesosphere.io/viewLog.html?buildId=72442&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:02
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


Canola instead o cannola


I don't think this is correct, it's a fixed commit id that doesn't match the current commit id.


LGTM.


@tdeheurles would be great if you could get this working with CCI, or any other CI-as-a-Service, and write a post about it :+1:


Magento 2.0.0-rc Publication, means that it is a Magento 2.0 (no beta) version? please explain rc
In fact, I'm waiting for new Magento 2.0 version to update a website asap, I saw information about launch in Q4,  someone knows if the launch fro 2.0 is for end november? december? Thank you all !


@remoe I am to believe it is retro-compatible. Thing is I'm mobile and can't spend my data plan on provisioning test clusters for the time being.


Joya, lo dejamos asi o decis que lo agreguemos?
Si queres yo llego a casa y lo hago


What about instances created through the static factory methods, `*Ref.{create,zero}`?


Yes, but then how do AA should handle parameters for `@Path` variables?

```java
	@Get(value = "{hello}{bye}{parameterName}")
	void get(@Path("hello") String bye, @Path("bye") String hello, String parameterName);
```

In this case, `parameterName` is not annotated but it still valid for `@Path` annotations. Maybe, this method name is not good for this...`doesAllParametersAnnotatedOrPathParameter`? What do you think?


I am wondering if the package name should end with `-dkms`.

Search result of Debian packages "dkms":
https://packages.debian.org/search?keywords=dkms&searchon=names&suite=stable&section=all

Will try to find packages that build depend on dkms, yet not ending with name `-dkms`.

-----

Running lintian is rather simple. `sudo apt-get install lintian`

Build the package as usual. On Debian...
```
cd source-folder
```
```
BACKEND_VMM=xen dpkg-buildpackage -b
```
```
lintian
```

Or have it show more warnings.

```
lintian --pedantic
```

Other interesting switches.

```
lintian --pedantic --info --display-info --fail-on-warnings
```


INTEGRATION TESTING_2015-11-11 14:01:55


INTEGRATION TESTING_2015-11-11 14:01:58


mooi hoor


TeamCity TripleA :: UnitTest [Build 28](http://188.177.191.210/viewLog.html?buildId=87&buildTypeId=TripleA_UnitTest&guest=1) is now running


+ <Standard-Revision = "refs / tags / android-5.1. 1_r26"

not + <Standard-Revision = "refs / tags / android-5.1. 1_r28"


Is the problem solved dublicate user?


TeamCity TripleA :: UnitTest [Build 29](http://188.177.191.210/viewLog.html?buildId=88&buildTypeId=TripleA_UnitTest&guest=1) is now running


TeamCity TripleA :: UnitTest [Build 28](http://188.177.191.210/viewLog.html?buildId=87&buildTypeId=TripleA_UnitTest&guest=1) outcome was **FAILURE**
Summary: Compilation error: Software\TripleA\TripleA.sln (new); number of tests is too small: 0 (new) Build time: 00:00:06


Of course! I should've notice these.


TeamCity TripleA :: UnitTest [Build 29](http://188.177.191.210/viewLog.html?buildId=88&buildTypeId=TripleA_UnitTest&guest=1) outcome was **FAILURE**
Summary: Tests passed: 37; number of inspection errors is too large: 40 (new) Build time: 00:00:12


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4508](https://teamcity.mesosphere.io/viewLog.html?buildId=72444&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1 (1 new), passed: 0, ignored: 199 Build time: 00:12:59
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


This, I believe, breaks this library on pre-1.5 Go. Any chance you'd consider reverting it?


I thought these are `@Path`. I will revert this and the test case.


Sorry, I mean the assignment to the appRecord variable. I think it would be better to remove the <li> in this case. (and maybe also check if the app is already installed (https://developer.mozilla.org/en-US/docs/Web/API/DOMApplicationsRegistry/getInstalled) and disable it on load as well.


These constructors perform a volatile write. But I guess you're only considering removing the call if there are no other references to the field (everything has collapsed back to local variables being accessed in a single thread) so there is nothing that needs the "happens before" memory barrier.


In a common, case we can have console and external descriptors.


As of qubes-linux-utils 3.1.3, for the qubes-kernel-vm-support package there is only a small, easily fixed lintian warning.

```
W: qubes-kernel-vm-support: extended-description-line-too-long
N:
N:    One or more lines in the extended part of the "Description:" field have
N:    been found to contain more than 80 characters. For the benefit of users
N:    of 80x25 terminals, it is recommended that the lines do not exceed 80
N:    characters.
N:
N:    Refer to Debian Policy Manual section 3.4.1 (The single line synopsis)
N:    for details.
N:
N:    Severity: normal, Certainty: certain
N:
N:    Check: description, Type: binary, udeb
N:
```


This is a bit fragile, I'd prefer to call something in `Definitions` to give us a list of symbols.


I'm not sure I see the point of the release tag added like this. It seems to me it pollutes the version string with unneeded information so that you now have 1.0.7.0.a10289a vs 1.0.6.0 and that short-hash doesn't add an extra information that the 1.0.7.0 already contain if it's a release version.


Yes, I am still working in both papers right now.


I mean the handler should call 'urlVariableNamesExistInParameters()' directly.


ok. I will see it


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4507](https://teamcity.mesosphere.io/viewLog.html?buildId=72443&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:17:10
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


This is not needed as well.


No dice nada, para mi dejemoslo así.


I think wxGetUserId() is ok for all platforms.


Сделал


discard was removed, so we need to put spaces here and fix column vertical alignment for "wait" mount option.


TeamCity TripleA :: UnitTest [Build 30](http://188.177.191.210/viewLog.html?buildId=89&buildTypeId=TripleA_UnitTest&guest=1) is now running


Thank you for this change!


TeamCity TripleA :: UnitTest [Build 30](http://188.177.191.210/viewLog.html?buildId=89&buildTypeId=TripleA_UnitTest&guest=1) outcome was **FAILURE**
Summary: Tests passed: 37; number of inspection errors is too large: 40 Build time: 00:00:14


The wait option moved 2 spaces because /data and /cache changes.
So the column vertical alignment was updated here too by adding 2 spaces.


@aspiers: In perl, anything that stringifies to the empty string `''` or the string `'0'` is false in boolean context:
```
$ a=0 perl -e 'print 1 if $ENV{a}'
```
yield nothing. This patch cause some valid directory like `0`, `('')` or `()` can not be used.

I suggest to apply my patch instead.


Scalable-Units-Pumps (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


あえて & に変えてみた理由はどんなものでしょう？ (変えたのがダメと言ってるわけではなくて意図の確認です)


Hier ist ein trailing space! Haettest du das clang formatted, waere das nicht da!


Und hier hast du random tabs eingesetzt oder so.


Originally, I didn't want to expose the table object outside of the helper, but now I understand the architecture that you created. Would it be better for the helper to have a private Connection that will open it upon creation (aka in the private constructor)? The main reason to encapsulate the Connection interface in the helper is that the configuration is private in the class currently, and that is needed for the Connection.

With the above change in mind, the method signatures creating the table can be changed back to a Table interface instead of a String, while using the connection interface to create the table. The insert method signature can be changed back to a Table interface as well, including the logic for opening the Conection and the Table taken out of this method. Finally, you will want to check and make sure that the Connection and Table are closed, hence a finally block should be added to the main() method try/catch block.

I have the above changes ready, but I wanted to check with you first. I have another developer using and testing the code, so it has been tested.


nitpick I'd prefer: `val storesRemoved = compilerSettings.YoptCopyPropagation.value && eliminateStaleStores(...)`, etc.


Hier sind auch Tabs und Spaces gemixt.


Here's a screen recording of what these changes introduce:
http://gfycat.com/IcyCheeryBluewhale
We can revert this and fallback to just overflow-x on all tables, but I really like how this works on mobile


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4511](https://teamcity.mesosphere.io/viewLog.html?buildId=72452&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 197 Build time: 00:04:44


af


Good point about `0`, I will fix that.  However it is not possible for `$ENV{STOW_DIR}` to return a list - it will always be a scalar.


Line 115: can't use `T` as parameter and instance.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4509](https://teamcity.mesosphere.io/viewLog.html?buildId=72446&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:14:28
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


Clarification on my comment above: elastx is taking something between
2 and 4 minutes to deliver a stack that is pingable, which is still
too high, but we can probably improve the time it takes for
provisioning to finish.


I think this is a good idea but I can't help but feel that we should something more general in the hof (or another module) that handles this. I also think that we should probably be integrating with a frontend framework. (Backbone.js? Something more modern and hence cooler?)


ja coel achterground man


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4499](https://teamcity.mesosphere.io/viewLog.html?buildId=72429&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout Build time: 01:00:01


I thought Skydust already had a min range because the aiming ray source was in the middle of the turret, causing some rays emitted from skydust to be blocked by the platform.


Would be interesting to keep track of a histogram of the number of rounds required. I'd love to see the bytecode progression for the method that takes the most rounds. Might even be worth adding a diagnostic mode to log that out for a nominated method during compilation, might really help people report bugs or understand the progression of the optimizer.


@jonjamcam , @Ezeer , I release the 2.0.5.
I think the release is good enough. The problem we are trying to solve ti pljones is very specific to the pljones machine, so no make sense wait for a new release.


Documentação do projeto


Let me reiterate:
Neither `captureForError` nor `captureForAction` **means anything**.
Because we won't say *capture a screenshot for the error/action* in our case (cause it means to capture a screenshot required for the error/action). At least, we'll say *capture a screenshot of the error/action*.
But, you guess, `captureOfError` is not the way to go.
We need to come up with something different.


Great overview, much appreciated.


Hi John, I will try to follow all the best practices you mentioned in the future . However these changes are not complete. It seems there are resizing issues sometimes on which I'm investigating.


I found the use of `next` a bit confusing, especially because it has to be used in the first two case statements, but not the third. Did you consider using the `if` / `elsif` / `else` construction for the outer conditionals as you have done elsewhere? I think that your `case` solution might've reduce the levels of indentation by one, but I still think the `if` / `elsif` / `else` construction would be less confusing.


What do you that breaks the flow? they are just html entities.


Surely threads are expected to be supported without needing to be embedded in a JS implementation supporting workers?


Same comment as before regarding the use of `next`.


As FP modes > 30Hz don't exist then this means we'll fall back to 3D SBS/TAB in this case (rather than displaying no image at all).


I think that `screenshotCapturer.captureError` and `screenshotCapturer.captureAction` are pretty clear and won't be confused with catching errors.


Лишний пробел перед знаком вопроса?


No worries. I just gave you some small tips as I saw them. Let me know if you want me to keep making these small comments ;-)


Looks like `exports.readSeq` is assigned twice - should one of these assignments be removed?


Does it sound ok for you?
@AlexanderMoskovkin


retrieveWorkItemsById seems to take the old id as input, and the only usage of this method is the getWorkItems endpoint in EntityResource. What is the reason that this endpoint takes the ID and not the URI?


Fixed.


' seen that  .
I have updated the wiki already with the download page at github .
Don't forget to update your web site too .
good job !
;)


Do we still need this?


yeni değişiklik


The proper way will not work here - it is callback. This is the best way I found so far.


kinda


@jdsolucoes meu editor oficial para o Git. :+1: :stuck_out_tongue_winking_eye:


pure-button-primary?


\cc @MargaritaLoseva


(1) I am not big fan of x.y.z.Final-SNAPSHOT, imho, more natural is to have x.y.z-SNAPSHOT and release the AlphaN, BetaN, Final from it and after each such release going back to x.y.z-SNAPSHOT. It gives you the freedom, because you don't have to know that after Alpha8 there will be Final. But I can add this rule, if necessary, I can send an email to hawkular dev list to find out what we want.

(2) the src-dep plugin should be fine, because this checks only the `project.version` property, i.e. the project version of the module itself, not of its dependencies.


есть строка routing_planning. Надо либо использовать её, либо удалить старую.


хз, похоже на то


Shouldn't the List string be in between the <i> tag? What is this actually doing?


やってみたんですが、Fixnumにprintfメソッドはないと怒られてしまいました。


Ah, right ! Thanks, I'll remove it.


@damienpontifex

I am mostly glad with this article and happy that you have made the work of formatting it. Also I am happy to see your engagement of making this knowledge more accessible and exposed in the right place.

There are few things to discuss here:

I have a question about stripping out content about non MS databases. On the one hand I have a feeling that it's ok but on the other hand asp.net5  is about open source so mysql and postgresql fits here perfectly. Moreover the configuration of last two is more complex than MS databases. We should think how to or if we should cover this topic.

My impression in that the article title is a little misleading now. There is nothing about building application here but it's more about config. Maybe we should change article name?

Another option would be to add some content that would correspond title - creating dbcontext, creating migrations, using entity framework in the application. We should be careful though that the content should adhere strictly to ASP.NET 5 to avoid repeating good content at EF site and to bring a real value.

Another thing is that article does not state explicitly that it uses code first approach only. I haven't tired other approaches and I am not sure if they work all right. This should be checked and noted respectively.

What do you think about changing the note about migrations into separate section. I feel that in my original article I didn't made a good job of informing readers that they should work, they can be scaffolded, even automatic migrations (that notably uses the same mechanism for creating migrations) works perfectly.

I feel that the note should be rephrased further (I like the fact that you added info about auto migrations) to add something like "ASP.NET 5 is still in beta version.. [blah blah] migrations in final version should work". I am almost sure that I have seen commit that fixes this issue. We should try it on rc1 or rc2 unstable packages.

My changes I have made so far and will commit shortly:

As this article is mostly based on my work and the text is taken from my blog I feel that sequence of authorship should be changed.

I also made a commit that adds additional resources section and placeholder for summary.

Additional resources contains link to my original article as it provides somewhat different value than this simple doc.

What do you think?


Good catch. EASYRPG_SHARED_PTR should be removed in a different PR btw. Is not needed anymore since C++11.


Unrelated: Is there any reason this condition couldn't all be on the same line as the `if` statement?


やってみたんですがFixnumクラスにprintfはないと怒られてしましました


remove "want"


var model2 olmalı


Аналогично с my_position, правда там текст "My Position".


see (fr-FR) line 456 (blue-ok)
everything's ok until **"**- then turn grey + KEYS for lines 457 to 460 turns red as the **"**


[11.11.15, 15:29:08] Nataliya Yakavenka: нет
[11.11.15, 15:29:16] Nataliya Yakavenka: это нюансы французкого


(1) ok, wildfly uses the x.y.z.CR5-SNAPSHOT approach


Left some comments. It would be even great if you could attach a print on UI changes! I am super curious about this change :smile:


Subjective: I would probably have gone for two spaces rather than one here and I might also have moved the other condition on this line onto the next line at the same level of indentation.


I think now we have this code more that twice.
Maybe we can introduce little class for range?


Никогда не любил французский)


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4510](https://teamcity.mesosphere.io/viewLog.html?buildId=72451&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:17:48
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


COOL! Long waited release......Fear me little Bugs, I'm coming for you!


fixed leds and keyboard backlight


It would be easy to shim. I chose not to (and it was approved by other core devs) because there might be other implementations than `pytz`. Some projects might have their own implementations. We didn't give a lot of thought to the possibility that this would mask useful exceptions.

Masking exceptions is consistent (for better or worse, probably worse...) with the Django template engine's historical behavior. I believe this is the correct thing to do in the current context, even though it has some drawbacks.


'The range appears to be quite big and this action can take a while. Do you want to continue?'


So the user must throw an exception in deny()?

If not, the `with-body` codes will be executed even if check() failed.


My comment was about debugging the album switch (a tougher prospect).  I fixed this one and updated the repo.


also combine ifs and get rid of second call


Noch ein paar Anmerkungen:
* Der Autoloader ist wieder drin
* Farbe muss noch in AbstractSocialNetwork
* Und bei $newJSON kannst du dann auf die Attribute zugreifen statt sie hart zu kodieren.


LGTM. Not going to bother with a ton of little nitpicks - everything seems on point.


Because it is sufficient to define it once :grinning:

There is another "def full_name" in the same file, further above, slightly different to this. Ruby allows this, the last def wins, and this can be very confusing.


Your code won't try to build this code - see configure


is this name from API?


Try to use `rct_map_element* mapElement = map_get_first_element_at(x / 32, y / 32);` instead of doing it this way. We have extra checks to make sure its a real value.


test


what's BB?


A minor thing, but indentation


@jmcphers We've got a number of postMessage handlers all of which have a slightly different contract (e.g. some take the e.data value as a string and some as an object). Further, I'm in the process of adding another postMessage handler that takes an object. This requires us to both screen on the type of e.data but also introduce another "type" field in handlers that take an object (to distinguish the type of object that's begin passed).

In this commit I add this screening to the ShinyFrameHelper. Could you quickly review and test (I wasn't sure how to instrument the product to test the ShinyFrameHelper) to make sure I haven't borked anything up?


I think this should just be a normal monomorphic function, not a Show instance. If `FileFlags` is to have a Show instance then it should be `show R = "R"; show R_PLUS = "R_PLUS"; ...` and so on, so that the Show instance produces code that can be evaluated to give back the original value.


`qrad_base[i] = qrad_input[i];` perhaps is more readable.


Hi,

This commit solves infinite recursion caused by UIAlertView

Although it seems this one hasn't included inside pod (1.0.5)

Can you take a look?
Thanks for your hard work.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4512](https://teamcity.mesosphere.io/viewLog.html?buildId=72453&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:17
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


Whenever it tries to access the type variable & `0x3C` you should convert this to `map_element_get_type(mapElement)`


The matrix input to the block is column-major or row-major?


I think you've removed the question mark suffix in previous commits where you've converted `define_predicate` blocks into `next_node_calculation` blocks, because of a problem when state variables are converted into a hash for outcome templates. Is that not a problem here?


again see below use `map_element_get_type(mapElement);`


Sir,can this branch be used for cm13?


predicate メソッドの否定の〜となると、コードを読んでる人は、つまり？って頭の中で？が3つくらいついちゃうので、not excpeiton? に適切な名前をつけてあげるといいと思います。


I would vote for either removing it or ignoring it! Whatever you fancy

On Wed, Nov 11, 2015, 11:57 Sam Smith <notifications@github.com> wrote:

> @joakin <https://github.com/joakin> Should the /raw/[title] endpoint be
> converted to JSON too?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/joakin/loot/commit/4bdc229b7eb19fd6e9f37fa99c1e25238052c165#commitcomment-14325911>
> .
>


@kumajaya my sim-patch
https://github.com/Aromer-room/0/blob/master/sim-patch


This is a known value `MAP_ELEMENT_TYPE_TRACK `


あと、インスタンス変数はインスタンスメソッドから参照できるので引数に渡してあげなくてもいいと思います。


It feels a bit weird to have both the `:is_ips_application` and `:ips_application?` state variables. Is it not possible to only have one of them?


This is a known value MAP_ELEMENT_TYPE_TRACK


Слишком длинный текст, на андроиде переносится на вторую строку. Остальные переводы звучат как "Из".


И тут слишком длинно ИМХО


I don't think this is a good idea.
Boot sectors starts at 0x7c00 and its stack goes
down to, say, 7b00. This leaves us only with
~25K to read, but I have PC-DOS with ibmbio.com
being 40K. I think we need a fixed values.


Prefered use of this is `rct_ride* ride = GET_RIDE(mapElement->properties.track.ride_index;`


What if the constant load we're eliminating isn't a string, but is rather a `Class`?
> ldc
>
> Otherwise, if the runtime constant pool entry is a symbolic reference to a class (§5.1), then the named class is resolved (§5.4.3.1) and a reference to the Class object representing that class, value, is pushed onto the operand stack.

> 5.4.3.1 Class and Interface Resolution
> Any exception that can be thrown as a result of failure of class or interface creation can thus be thrown as a result of failure of class and interface resolution.

Same for method type / method handle literals.


to_string として to_s という名前が使われるのが Ruby 的なスタンダードです。使う側のプログラマも MyYear の文字列化されたものをほしいときは、とりあえず to_s を呼ぶと思います。使う人の前提にしている背景にあわせるというのはよい API 設計の一つのパターンなので踏襲しておきましょう。

ちなみに、to_str は to_s とはまた違った特別な意味合いがあります。

see http://d.hatena.ne.jp/kitak/20120724/1343084846


Я у себя обозвал "Маршрут отсюда" и "Маршрут сюда".


Doesn't it work without this one?
14 root sectors for FAT12 doesn't boot?


Prefered version is `rct_ride_type* rideEntry = GET_ENTRY(ride->subtype);`


Should mention that globbing rules apply, e.g Use "github.com/MYNAME/*" to use a single account for all repos under that github namespace.


On Wed, Nov 11, 2015 at 04:01:56AM -0800, Patrick Schleizer wrote:
> I am wondering if the package name should end with `-dkms`.
>
> Search result of Debian packages "dkms":
> https://packages.debian.org/search?keywords=dkms&searchon=names&suite=stable&section=all
>
> Will try to find packages that build depend on dkms, yet not ending with name `-dkms`.

I was thinking about that, but the package also contains initramfs
module. Or should it be split to separate package?

--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?


Sure, but what value to pick, track size is what the real boot.blk appears to do?


This can also be a regular NSString


Oh. Sorry. Only just seen this. Ignore my previous related comments.


typo - VERSION


Уже есть строка routing_start


Have you tried changing the track size to
see if that's the case?


However, do you not need to update the regression test checksums *after* this commit?


Nope, but will try now


А чем отличается от p2p_planning_route_title?


https://github.com/lrytz/scala/commit/29d772d0655a3a5af79c3d8eca91bb33a82c7194#diff-70147974eed4d5f7faa546e42504ce64R683 - maybe I have to add method handles?


If you don't want ASSERT_* you can use EXPECT_* check. It will print the error and continue further without crashing the test.


will add a tests!


I think this is the case, but just checking: does optimizer's handling of tuples account for the fact that `TupleN` is not (yet) final?


comment


another approach might be to change the codec of `request_redirect_t`: add a member variable `do_direct` in it, ignore its payload in `request_redirect_t::encode()` and `request_redirect_t::decode()`? this approach does not require the `CEPH_FEATURE_NEW_OSDOP_ENCODING` feature bit, i guess.


For sure I would like to have informed about my coding mistakes. It's not a problem for me, these things makes the difference between a programmer and a Programmer, and I would like to learn all.

I will inform you once the changes will be done. ;-)


「4年に1回というのを通常のルールとしたときに例外として〜」というニュアンスでの exception だとは思うんですが、コード中に exception だけ登場すると、本道はどっち？と考えながら読むことになるので、そのあたりがわかりやすいとよさそうですね。その辺のヒントとしてコードパスの話を置いていきます。

see http://www.clear-code.com/blog/2012/3/28.html


yes, it only eliminates `new TupleN`


cc @DanielePucci take into account this before using this block.


TeamCity LabkeyRelease15.3 :: Git sqlserver 2014 [Build 36](https://teamcity.labkey.org/viewLog.html?buildId=284344&buildTypeId=LabkeyRelease153_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:01:24


Don't leave commented code, it is not useful to leave it the it only pollutes the code with unnecessary lines, we will take a look on some clean code principles that will elaborate on this.


The code looks good, but I guess I am wondering why you are only adding this to the Infinispan 7 service?


Awesome!


Wrong indentation


ここはもはや TDD の練習での指摘を超えてる気もしますが、便宜上の例外をわける必要あるかなーという点はメソッド分割の設計としては考え直してもいいかもしれないですね。


Hi


Code in comments


> つまり？って頭の中で？が3つくらいついちゃう

predicate の否定を見たときの私の頭の中は、 記号論理的には ` ￢(∀XP(X))⇔∃X(￢P(X))。全てのXについてP(X)が成り立つ、が偽ならば、P(X)ではない或るXが存在する。かつ、その逆。` なので、P(X)ではない或る X という概念がいっぱいでてきてしまうので、混乱する、という感じです。


We decided to do such checks in the code itself and print "SKIPPED" sign near all tests which were not run.
In such way, we won't miss any tests.


We use english spelling throughout the code base not american.


I don't really like this new way of doing `Params`, having to write:

``` csharp
[BenchmarkTask(..., intParams: new[] { 1, 2, 3, 8, 9, 10 })]
public static void Benchmark()
{
...
}
```

and then wire it up in a constructor
``` csharp
public ParamsTestProperty()
{
        ParamProperty = BenchmarkState.Instance.IntParam;
}
```

Instead of just:
``` csharp
[Params(1, 2, 3, 8, 9, 10)]
public int ParamProperty { get; set; }
```
seems more clunky and less intuitive.

Plus with the old-way, if we wanted to support `Params` on 2 variables, we could allow:
``` csharp
[Params(1, 2, 3, 8, 9, 10)]
public int ParamPropertyA { get; set; }

[Params(4, 5, 6, 7)]
public int ParamPropertyB { get; set; }
```

But I'm not sure how you would do that with the new way, you need to support something like this:
``` csharp
[BenchmarkTask(..., intParamsA: new[] { 1, 2, 3, 8, 9, 10 },  intParamsB: new[] { 4, 5, 6, 7 } )]
```

I guess I just don't see the benefit of overloading the `BenchmarkTask[...]` attribute with things that could go elsewhere? Having the `Params[..]` attribute applied to the `property/field` that is to be used by seems more intuitive to me


Good question. Let me find out what the motivation behind it was.


I hadn't seen this plugin until you pointed it out; thanks for the suggestion.  Based on Sayonara's documentation, it seems aimed at a different mindset than the bufkill plugin.  Vim has built-in support for unloading, deleting, or wiping out buffers via ```bunload```, ```:bdelete```, and ```:bwipeout```.  These commands close the associated window.  Bufkill provides equivalents to these three that leave the window intact.  Sayonara, on the other hand, seems to come from the mindset that the user just wants this buffer out of his way while leaving the windows unchanged (except perhaps for the current window).  If the current buffer is showing in only the current window, the buffer is deleted; otherwise, it is left alone.  In my use cases, I'm interested in explicitly deleting (or, more often, wiping out) a given buffer, with the express goal of making sure Vim is not holding it open.  If it's open in multiple windows, I want it removed from all of them.  I also generally prefer the ```:BW``` (```:bwipeout```) variants to avoid accumulating lots of unlisted buffer numbers during my long-running Vim sessions.  So I think the two plugins are trying to accomplish different things.  Mostly, I view Sayonara's goal to be "stop showing me this current buffer", with the user not really caring if the buffer gets deleted or not.  I don't find this to be a typical need for my use cases; instead, I normally either want the buffer to be wiped out, or I want to keep this buffer alive and switch to a different buffer (for which a buffer switcher is the appropriate tool).

Sayonara does seem to work harder at keeping the window layouts unchanged, even
in other tabs; this is something that bufkill doesn't currently handle well
(e.g., if a given file were open in three tabs, ```:BW``` would close the
windows in the inactive tabs, possibly closing the tabs as well).  That feels
like a limitation that bufkill should probably address, and probably the main
advantage I see to Sayonara's implementation.  But I think the interface to
bufkill is generally the right idea for my needs.  I find it a bit surprising
that Sayonara chooses to close the window by default, and requires the extra
```!``` to preserve the current window (despite going to great lengths to
preserve the window layout everywhere else).

Thanks again for the suggestion.  The two plugins do seem to have different
strengths, and I could imagine combining them to some advantage.  Adding a
```:BC``` ("buf close") command to bufkill which would essentially perform
```:Sayonara``` and fixing bufkill to preserve windows in the inactive tabs
would make for a nice superset of functionality for my use cases.  An
alternative approach would be for Sayonara to add ```:BW```, ```:BD```, and
especially ```:BC``` (because typing ```:Sayonara``` has already grown old just
from this comment :-)), where ```:BC``` would be the same as ```:Sayonara!```,
and ```:BC!``` would force closing even if the buffer is changed.


Today I tested this patch for all 3 regions. I played offline 3 races in-order and 3 random at each region. And it worked like DimitriPilot3 told. In the next days I'll test, if it have online side effects.


@aspiers: Ah, right.

Also note that starting from perl 5.18.0, all keys, values in `ENV` are stringified.


Scalable-Units-Pumps (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (907 of 907 tests passed)

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


Unnecessary spaces


should be integer instead of mixed


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4516](https://teamcity.mesosphere.io/viewLog.html?buildId=72466&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:29


Hey Andrew! What are you using in Etsy instead of dashboard now?


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4517](https://teamcity.mesosphere.io/viewLog.html?buildId=72467&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:03


Ah I see. What is the "upstream" that was changed? I don't understand? Can you link the change you are talking about?


coment 1


Line Note 1


>//this class is implemented in different files for multiplatform purposes.
+//The implementation files are WindowsPerformanceMonitor.cpp, MacPerformanceMonitor.cpp
+//and in the future LinuxPerformanceMonitor
+//The correct implementation file is selected in Jamtaba-common.pri

good design !

Your implementation is clear , good job !


Quite minor thing:
Usually we write tags in totally one line like:
```
<p>my paragraph</p>
```
or totally new lines like:
```
<p>
  my paragraph
</p>
```
Use one on one tag, don't mix it


Ok, it is a reasonable point. But what if I want to use different parameter sets for different tasks?


It's component for including backbone views to react


Nit: extra imports.


@SweetViper I had'nt had the time to test it so I merged his commit, sorry about that. I just reverted the changed you pointed out. It seems to be working properly.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4513](https://teamcity.mesosphere.io/viewLog.html?buildId=72463&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:19
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4519](https://teamcity.mesosphere.io/viewLog.html?buildId=72469&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:07


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4520](https://teamcity.mesosphere.io/viewLog.html?buildId=72470&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:03


No. When you apply 'nuget' it will apply 'nuget-base'


"throught" is "through" ?


Math.round периодически возвращает "undefined".
Заменил его на Math.floor - нормально стало (раз 50 пересдал для проверки).
Они округляют по разному:
floor - в меньшую сторону, а round - классически (от 0,5 - в большую).
Видимо, периодически при таком округлении (Math.round), число выскакивает из диапазона индексов.
На руках игрока может получиться ['K', 'undefined'] и сумма очков "NaN".


it's an additional key for define not provisioned ip addresses


Bug fix for #24864 - Fix method return type.


s/usptream/upstream/ :-)


Done


@anusha-ragunathan @tiborvass I am working on couple of patches to do what you are trying to do. Will soon generate a PR.


That sounds like a great idea. Thanks Noah! And yes, any help is greatly appreciated! :)


Hello!
Please help me.
I use XLabs.Forms.Controls BindableRadioGroup , create BindableRadioGroup by c# code:
 answers = new BindableRadioGroup
            {
                Padding = new Thickness(0, 10, 0, 0),
                TextColor = Color.Black,
                BackgroundColor = Color.Blue,
                FontSize = 12.0,
                FontName = "Arial",
                VerticalOptions = LayoutOptions.FillAndExpand
            };
            answers.ItemsSource = myList.Values;

but my application watch BackgroundColor' rectangle, but didn't watch text(items).


circuitry？


I guess I forgot to remove the old timestamp from dev/head.js.  Sorry about that and thanks!


Bug reported as https://github.com/headius/options/issues/2.
If a fix is needed in the meanwhile, one could
`Options.DEBUG_FULLTRACE.unforce();`
just before
`config.processArguments(new String[]{"--debug"});`.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4514](https://teamcity.mesosphere.io/viewLog.html?buildId=72464&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1 (1 new), passed: 1, ignored: 199 Build time: 00:13:01
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


Sounds good. I like this change more. The idea is that the Helper knows how to create, modify and delete tables, using internally any object that is needed. I don't know if that object is now a Connection or is still the HBaseAdmin object.

There's one thing I don't understand yet (maybe is because the Hadoop interfaces have changed) and it's why the Connection object is needed. In your previous patch I saw it was used only for retrieving a table but after that it was not used anymore. If the helper, through the HBaseAdmin object can create a table, why it's necessary to instantiate a Connection?

OTOH, I saw that the HBaseAdmin object is no longer part of the external API and Admin should be used instead https://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/client/HBaseAdmin.html To get an Admin object a connection is needed. So maybe the change that is needed is something like:

```java
Connection connection = ConnectionFactory.createConnection(conf);
Admin admin = connection.getAdmin();
```

This can go in Helper.create. As for closing the connection, as you said in the finally, I think is best to add a close() method in the Helper which has to be closed explicitly. What do you think about these changes? Does it make sense?


Hi Mark

qcow2 images can only grow. If you want to shrink, in addition, to zeroing out the disk you have to run something like
```
qemu-img convert -O qcow2 ...
```

This should be run after the packer build.

In addition, I don't have room on my computer to use, e.g., 100GB of space while zeroing out. So I'll skip out on zeroing out for now.

kind regards,
Jakob


Топ хештэгов


Nice looks good :+1:


`wbi::frameFromSerialization` serialize/deserialize row major ordering. Matlab should be column.


I tried out the patch by hand (editing the local file) and it's working fine; thanks!


RootNamespace and AssemblyName are incorrect


Promijenjen kod prema sugestijama.


`ENV` values have always been stringified AFAIK.  Maybe you are talking about them [being forced to byte strings](https://metacpan.org/pod/release/RJBS/perl-5.18.0/pod/perldelta.pod#Defined-values-stored-in-environment-are-forced-to-byte-strings)?


有没有发现在musl库里编译sans会启动失败？


Ah!, got it.
What about the method name? is `hasAnnotatedAllParameters` good?


@smithfarm trailing space.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4515](https://teamcity.mesosphere.io/viewLog.html?buildId=72465&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:01
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


@adnanghaffar07 'from selenium.webdriver.common.keys import Keys' this is added twice. Quality check.


Scalable-Units-Pumps (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: Tests Failed

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


Seria legal especificar que só é necessário rodar esse script, caso você não tenha o postgres instalado na sua máquina e se o seu sistema for linux! :P


This method name is fine. I am just talking about extracting the url variable check.


Actually, it's definitely  an ideal approach


Apparently not, but `valid?` is being called before `save` when `save!` is called so adding an extra callback for `before_validation` with a guard in the first line of `update_url_title` to return immediately if `title` hasn't been set. (Calling `save` instead in the controller would be simpler but then any future calls to `save!` could throw unexpected errors)


I'm Casce, and I'm new and learning. Apologies in advance for my crude caveman ways.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4523](https://teamcity.mesosphere.io/viewLog.html?buildId=72473&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:00:47


{ }で囲むのはhtml記法の部分だけなのでclassとroleだけでいいです！
あとremote: :true => remote: trueですね


@AlfredoChavez es mejor que saques el seed como una variable de entrada del componente que te permita modificarlo, para poder sacar diseños diferentes con el mismo script.

@Fablab-Sevilla/students


It uses all three. This is part of the Sufia install, in which Blacklight creates the User class and adds its own functionality, then Hydra and Sufia build off of it. Here's another example:
https://github.com/psu-stewardship/scholarsphere/blob/develop/app/models/user.rb


(ﾉ´ヮ´)ﾉ*:･ﾟ✧ YESSSSSS`~


Wow :+1:


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4525](https://teamcity.mesosphere.io/viewLog.html?buildId=72476&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:00:24


Sleepily copied that from another form that isn't translating things. Will track it down and make sure there's a ticket to repair it.


This is part of the role management gem where admins can change the role of current users, such as making them admins.


I did add a close() method, in line with how the Helper works currently, so we are on the same page there.

The newest apache.org/hbase Javadoc for the Table interface and all implementations (HTable) specify that you should do the same thing that you suggested for Admin as for Tables, therefore that's how I implemented my changes. I will update the classes specified and push up to this pull request, including the update to the Admin creation that you referenced above.


I don't understand what you're asking.


The action 'facebook' could not be found for Devise::OmniauthCallbacksController


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4518](https://teamcity.mesosphere.io/viewLog.html?buildId=72468&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:16
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


Ok great, will update that.


provideOkHttpClient() ?


I'm surprised this wasn't already done :grin:


Default exports are broken in Babel 6 (as is almost everything else they did in this release).
You should not try to adapt to broken behaviour in your toolchain (but instead downgrade to babel 5 until version 6 is usable).
Also: This change is a **breaking** change and must come with a new major version, because it changes the public API of your module
```javascript
import lory from 'lory.js';
```
vs new:
```javascript
import {lory} from 'lory.js';
```


Yes. There needs to be a default, hard-coded set of admins who can make other users admins as well. As far as I know, this will carry forward into production, unless shib. has a notion of groups.


Why is there a special snowflake check here?  Why not put this in salglu_solution/on_mob_life ?

Also, it's WORSE at treating bloodloss than just shoving iron in someone's mouth, is that intentional?


没有啊，我一直都是musl，除了有时候过滤效果不是特别好之外，没发现什么问题


Muy clara esta forma de separar el código entre la generción del número aleatorio y su uso en la componente del punto después, aunque podrías haber hecho:

*Pt1X = Ptnew.X+rd.randint(-1,1)*

A su vez la forma de guardar las componentes modificadas del punto es un tanto enrevesada pero funciona parece. Aquí sólo te diría que prestes atención a las estructuras de los ejercicios de los compañeros, a ver si puedes ver otras estructuras que permitan lo mismo sin tanta variable auxiliar de paso.

cc/ @Fablab-Sevilla/students


Is there a particular reason prob is rolled twice?


How else would we do it? I'm open to suggestions.


Вооот. (К слову, если у тебя ruby версии старше 2.0 — а это крайне желательно — то есть прекрасный метод to_h, который ещё немного упрощает эту конструкцию)


I reduced the cylinder size to 16 and the boot.blk generated reads did this
~~~
DISK 128 read [h:0,s:1,t:1](15)->0000:0700
DISK 128 read [h:1,s:0,t:1](16)->0000:2500
DISK 128 read [h:2,s:0,t:1](13)->0000:4500
~~~

with 17 it was this
~~~
DISK 128 read [h:3,s:15,t:0](2)->0000:0700
DISK 128 read [h:0,s:0,t:1](17)->0000:0b00
DISK 128 read [h:1,s:0,t:1](17)->0000:2d00
DISK 128 read [h:2,s:0,t:1](8)->0000:4f00
~~~

So it looks like it reads the whole file, but seems to adjust the first read to align with the cylinder length


OKです！


Note for others: this does **not** box with Roslyn, the question came up in an unrelated PR.


Okay, I'll look into how to fix this without introducing the sleep. I'll see if I can figure out how to have github pull your hexdump change separately.


As far as I can tell from their apidocs, the main difference between the Connection interface and the Admin and Table interfaces is that Connections are thread-safe, and are for "heavy-weight operation" whereas the others are not thread-safe, and are for "light-weight operation."

Reference: https://hbase.apache.org/apidocs/


Scrub that, it's part of a help page so it's probably ok as-is


Oh, forgot to mention: The 'fedora-rawhide.repo' is added by the 'fedpra-repos-rawhide' RPM install, on line-74 above (which is just `yum install fedora-repos-rawhide`)


In this case we need a separate 'case' handling.


OK let's discuss how we can make it more general offline when we meet up.

Meanwhile...
my preference would be to *not* use a frontend framework like BB. The bundled js already contains underscore and jquery :-(


https://github.com/NextBook-organisation/nextbook/blob/production/pom.xml#L623
і там же треба всі зміні середовища підтягнути з environment


Ну уж нет! У нас в списке режиссёров 13 человек с именами вроде "Alejandro González Iñárritu", "Brian De Palma", "Florian Henckel von Donnersmarck" и т.д. Не позволю так обходиться с гениальными творцами!!!


Yes I believe he's well aware. I will write it in the in-block documentation


This is less efficient due to string.Concat(), but it needs more love than that - I'll fix in a separate commit with a StringBuilder. Note: need to check status of the new Net standard string utilities and see what's exposed in vCurrent.


Pre perl 5.18.0, if you setting something in `${ENV}`, then that value wasn't stringified. You can see `perldoc -v '%ENV'` for more details.


We are using 4 spaces instead one tab


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4521](https://teamcity.mesosphere.io/viewLog.html?buildId=72471&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:12
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


@XinzeChi  To be honest, it looks complicated to me and also it makes assumption about number of chunks (which may go out of control). I understand the idea, but I think the client code shouldn't dictate number of chunks because then, it should also know how many of them there will be, and to know this, it must know when they are being split (in other words, you force some of the logic internal to chain_*xattr() functions outside of them).


+1 - This commit looks good.


why no field injection here?


Use spaces instead of tabs


Esto es una chorrada estilística, pero normalmente el nombre de las variables (que se pueden establecer de millones de formas diferentes) suele construirse con un prefijo en miníscula y un nombre base que comienza en mayúsculas (para separarlo visualmente del prefijo y un sufijo (si fuera necesario). Cómo lo hubiera hecho yo:

ptNew, ptList, ptNew2, pt1Y (aquí puede ser interesante poner en mayúsculas el sufijo que denota la componente).

Por cierto, esto es sólo una recomendación sin mucho fundamento y porque a mi me resulta más visual y clara esa forma de nombrar variables (y porque de los diferentes métodos que aprendí en su día es el que más me gusta)...Y lo más importante, es intentar mantener el mismo sistema a lo largo de todo el código que escribas y no cambiar de unos archivos a otros.


This should be

```
n = normalise_tuning(n)
```


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4522](https://teamcity.mesosphere.io/viewLog.html?buildId=72472&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:03
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


lgtm - is it tested on a local instance?


Youi should jsut put void gsm_properties on top


TeamCity TripleA :: UnitTest [Build 31](http://188.177.191.210/viewLog.html?buildId=90&buildTypeId=TripleA_UnitTest&guest=1) is now running


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4524](https://teamcity.mesosphere.io/viewLog.html?buildId=72475&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:06
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


@ethanresnick Oh yeah that's much better. It also follows convention, which is good! Thanks for spotting that :100:


could use "do_redirect" for the variable name.


TeamCity TripleA :: UnitTest [Build 31](http://188.177.191.210/viewLog.html?buildId=90&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 37 Build time: 00:00:38


Let's not use `var` on this and on line 88 - these are places it's better to be explicit on types.


Only one dependency here - so more code without benefit - e=mc² ;-)


@kshefchek does this mean the `maxMaxIC` will always appear when there's data returned from compare api?


Use one empty line after public:
see: http://www.ascemu.org/wiki/index.php?title=Coding_standards#keywords


Reasoning for this? I don't think it matters.


These are less readable now - can you please restore the left-hand align? That seems like a non-default VS setting kicking in.


```while (!map_element_is_last(...))```


Please tabs to spaces.
See: http://www.ascemu.org/wiki/index.php?title=Coding_standards#Tabs.2FSpaces


Ну вот и славно.
Остались две важные вещи:
1. когда тебе надо положить в хеш по одному ключу одно значение, есть более простая конструкция, чем `@sort_algorithms.merge!({algo => block})` :)
2. надо, чтобы если выбран алгоритм сортировки/фильтр, которого наш класс не знает — прилетал-таки exception с информативным сообщением (типа «Unknown sort algo: blah»)


Good point. Should I keep it in here or revert?


`object`


Oh OK, but that's talking about how the values are passed to child
processes, which is not relevant to Stow since it reads STOW_DIR itself.

On 11 November 2015 at 13:19, Cuong Manh Le <notifications@github.com>
wrote:

> Pre perl 5.18.0, if you setting something in ${ENV}, then that value
> wasn't stringified. You can see perldoc -v '%ENV' for more details.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/aspiers/stow/commit/d0f3e5458fd9f93bff68cb2047ad531c7e0e9375#commitcomment-14328571>
> .
>


You need a single space here.
See: http://www.ascemu.org/wiki/index.php?title=Coding_standards#control_statements


in the vagrant.yaml file can you revise the borrower_frontend::branch_or_revision to 'develop' please


obviously changes to this function are critical and should probably be reviewed as I am just starting work on this project, I have no idea what the implications may be


Hi Jorge,

you are right, of course. We would change the code then to do the simple copy only if the MediaWiki format is allowed and that is the default one and do the conversion to Creole format in any other cases.

Would that be fine?

Thank you,
Zsigmond


![critical](https://cloud.githubusercontent.com/assets/8997458/11091991/09c297f2-8880-11e5-8478-8e676d914391.png)

Ser veldig bra ut!


> What "bothers" me here is that the resulting code gives more "importance" to one variable over the other when they are equivalent, just because it is assigned last.

Good point. It would be good to be "modest" about what we attempt to flag/correct, seeing that RuboCop can't possibly detect and understand every nuance of why code was written a certain way.


*TEST* Wed Nov 11 14:25:53 CET 2015


got this idea from [here](https://github.com/maidsafe/crust/blob/96c534aec6ab24d32d9f0dc50942e5b7cafdc147/examples/crust_peer.rs#L451)


if you are reusing this feature bit, might need to define your own, and let its value equal to the one to be reused.

imho, i don't really like the way to use a feature bit to tell if a client is supporting a certain version or not...


how do we handle these cases?


Use "Object* pObject" and "Player* Plr"
See: http://www.ascemu.org/wiki/index.php?title=Coding_standards#pointer_and_reference


1000 requirements per which time unit? It is not a grand total of 1000 requirements.


What do these challenges mean?


Which version of PC-DOS has ibmbio.com at 40k?


Wrong intend


<string>7265231C-39B4-402C-89E1-16167C4CC990<string>
<string>CC0D0F4F-05B3-431A-8F33-F84AFCB2C651<string>


Aquí puedes forzar el *"Type Hint"* desde la entrada del componente de GH, no te haría falta *int(sSeed)*. Esto no sólo limpia la apariencia del código sino que mejora la eficiencia del componente al no tener que averiguar que tipado darle a la variable de entrada. [Post interesante en la comunidad de gh3d sobre el tema](http://www.grasshopper3d.com/forum/topics/ghpython-some-bottlenecks-bugs)


*TEST* Wed Nov 11 14:28:07 CET 2015


why?


Use one single empty line at the end of the file.


Right. But Connection and Admin are used for different purposes, right? It's not possible to create or delete a table with connection, as I can read in the API. The API also says that Admin object should not be cached https://hbase.apache.org/apidocs/ So I think that instead of having and admin property in the Helper, it should obtained in every operation from the connection. If you have time to implement that in your patch would be great, if not it can be done later.


Missing space after "from(src,"


this should be reviewed as well, got the idea [from the same file](https://github.com/maidsafe/crust/blob/96c534aec6ab24d32d9f0dc50942e5b7cafdc147/examples/crust_peer.rs#L451)


isra-fel - Both mouse and touch generate pointer events.  In what situation would a user be "not able to use pointer events"?


why??


*TEST* Wed Nov 11 14:29:28 CET 2015


关于reverse()

可以试试

```python
for line in reversed(file_org.readlines()):
	file_ter.write(line.rstrip()+'\n')
```


test


cool :+1:


难忘中山忍


When did isUtc become true?  I don't see any difference between this case and the last.


Could you also start with a UTC time one, and leave it unchanged?


Hi @CosimaNomaD Thank you for the kind words and for taking the time to get in touch. I'm happy to know that the addon was useful for you :) .

Health & Happiness to you and yours.

Regards

Dill


not required.


@Fablab-Sevilla/students por cierto, no lo comentamos en clase, pero sería interesante que junto al archivo de GH y el *.py subiéramos una captura de la vista de Rhino en la que se vea la geometría generada. Podemos usar la misma estructura de nombre: *INICIALES_NOMBREEJERCICIO.jpg*


> ` Init page 83ms `

Мда. Вернул как было (2 мс).


You can't simply get rid of this, otherwise it may break for certain kinds of packets. This is what I do with alffplay:
```
static int packet_queue_put(PacketQueue *q, AVPacket *pkt)
{
    AVPacketList *pkt1;
    if(pkt != &flush_pkt && !pkt->buf && av_dup_packet(pkt) < 0)
        return -1;

    pkt1 = av_malloc(sizeof(AVPacketList));
    if(!pkt1) return -1;
    pkt1->pkt = *pkt;
    pkt1->next = NULL;

    almtx_lock(&q->mutex);
    if(!q->last_pkt)
        q->first_pkt = pkt1;
    else
        q->last_pkt->next = pkt1;
    q->last_pkt = pkt1;
    q->nb_packets++;
    q->size += pkt1->pkt.size;
    almtx_unlock(&q->mutex);

    alcnd_signal(&q->cond);
    return 0;
}
```


这是peter的评论


No I just missed it when I was removing them


Any way of getting this merged and release?


这是lissa 的评论


Not sure this is the case. SKIPPED aproach is inevittable when it is determined in run-time. When in build time ibverbs doesn't support some feature - whe add empty tests?


I propose to not have two overloads with a lot of parameters, since it makes both reading and refactoring a lot harder. Adding a few `emptyList`s at call sites is easier and clearer IMO


> If false, a HttpBadRequestException will be thrown

I think you mean **true** for a HttpBadRequestException


Can you please push this to npm ? :pray:


```ruby
$ thread = MessageThread.includes(:messages).find(1)
> "QUERY DB"
$ message = thread.mesages.first
> "NO QUERY"
$ message.thread
> "Before this would QUERY, now it won't"
```

There might be some places where this does something strange (unlikely) but I wanted the other changes to go live first.


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

 TestSuite|TestCase | Pass | Fail | Timeout | Skip
 ---------|---------| ---- | ---- | ------- | ----
 Total|||||


Actually "is installing" is present participle, so your commit message is slightly wrong!

</nitpick>


@craigcook What is the "intel"?


@craigcook see https://bugzilla.mozilla.org/show_bug.cgi?id=1223521


Looking at https://issues.jboss.org/browse/JGRP-1747, it's not possible to enable diagnostics at runtime before JGroups v 3.5, therefore we would have to resort to specifying custom jgroups config files with configurable TP.enable_diagnostics property. I probably saw the API changes when implementing the wrapper, so I judged it's not supported in previous versions - indeed it is, but only with TP.enable_diagnostics property=true on startup.


I think this isn't needed as we have this in ``ci-helpers``, right at the top:
```
# EGG_INFO
if [[ $SETUP_CMD == egg_info ]]; then
    return  # no more dependencies needed
fi
```


[This](http://www.os2museum.com/wp/hang-with-early-dos-boot-sector/) seems to suggest that DOS reads it one sector at a time, though modern disks cause problems because of their high sector count per track. I'm not sure though how we should treat IBMBIO.COM over 29k. Will the rest be loaded later into non contiguous memory?


You did so nice with using the imperative for commit messages, why did you stop? :wink:


@FelsyWaschbaer  Please take a look at the change of code in src/main/java/de/mpg/imeji/logic/validation/impl/ItemValidator.java  . I commented this new code, because it was not functioning properly. For example, if you have

Parent1
   Child 1.1
   Child 1.2

where child1,1 and child 1.2  are different (not multiple) types, validation of the item was failing.


gdf


Thanks a lot @nafg!


Agreed, I'll do it.


From what I had tried, finding loads of non-deterministic packages is rather easy, but fixing most of what you find is very time-consuming.


Три точки лучше заменить на символ многоточия (ASCII код 133).


Is it save to use this patch also on non-x250 hardware?


yes - personally I'd go for consistency here, but don't have a strong opinion on that. ;)


Checkmarx scan results 11 Nov 2015 15:40 UTC +02:00

High
Medium
Low
Info

New
2
2
21
0

Recurrent
0
0
0
0

Fixed
0
0
0
0

 Open Viewer
Included commits

Commit ID	Owner

84652d046be449561880fdd008307d81cc08a6d7	@BearSpace


@TheConen soll hier auch noch die aktuallisieren Beispielbilder rein?


难忘中山忍


yes


這一段有沒有作用 ？ 好像沒有對不對？若沒有就拿掉


Так в чём разница с routing_panning?


Hi, just found the typo by luck:  `imu` should be `ft_sensor`


Another point - in such case jenkins will run test four times - for each interface. We need some special treatment for two-carded test in test_jenkins.sh. (Build separate binary?)


Haha, will be more diligent in the future.


Hi Jorge,

ok, we will change the place of replacing to have that in each cases.

However, we have some more problems with this part. In the xml file which we have to import, there are links in the following format:

[[File:somenemforthefile.doc]]

According to the official documentation of MediaWiki (https://www.mediawiki.org/wiki/Help:Images) it is an accepted format, however, we support the image links with "Image:" prefix only. I think that is because the "File:" prefix was not supported at the time of the implementation. Is it right? If so, I think we should handle this a feature request.

It is an other question that the doc format is not supported even by the Wikipedia according to the description.

An other problem is that it seems, on Wikipedia, there are pages with file info through the "Image:" and "File:" link prefixes with the information of the file. I am pretty sure that it is rather a feature request also.

A final question is that, do you remember why we needed to implement the new SharedImages wiki page logic for storing those file?

Thank you,
Zsigmond


but as said - x201 still does funny thinks


check for empty value first, before other conditions
137 line no need, if empty cell


什么芯片的？
Assertion failed: sock > 0 (dnsmsg.c: query_recv: 74)报这样的错误

2015-11-11 21:13 GMT+08:00 Syrone Wong <notifications@github.com>:

> 没有啊，我一直都是musl，除了有时候过滤效果不是特别好之外，没发现什么问题
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/wongsyrone/openwrt-1/commit/cbfae54ddc3f05824b5f8d37eafb4ac51493dbc9#commitcomment-14328466>
> .
>


This is still in the newest version!
v 0.9.4.1 from wordpress.org


Today I tested this patch for all 3 regions. I played offline 3 races in-order and 3 random at each region. And it worked like DimitriPilot3 told. In the next days I'll test, if it have online side effects.


TeamCity LabkeyRelease15.3 :: Git postgres 9.4 [Build 39](https://teamcity.labkey.org/viewLog.html?buildId=284342&buildTypeId=LabkeyRelease153_GitPostgres) outcome was **FAILURE**
Summary: Tests failed: 32 (3 new), passed: 233 Build time: 01:08:08
### Failed tests
```
org.labkey.test.Runner: org.labkey.test.tests.CDSLoginTest: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyAntigenVariableSelector: <no details avaliable>

org.labkey.test.tests.ScrumtimeTest: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testDatasetExport: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testImmuneSpaceStudySubset: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testStudySummaryWindow: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testStudyCards: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testSelection: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testNavigationDoesNotRemoveFinderFilter: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testBackDoesNotRemoveFinderFilter: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testStudyCardStudyLinks: <no details avaliable>

##### there are 22 more failed tests, see build details
```


> Which version of PC-DOS has ibmbio.com at 40k?

7.0
There is already the code:
    case REALPCD_D:             /* old MS-DOS, PC-DOS */
    case OLDPCD_D:              /* old MS-DOS, PC-DOS */

You just need to separate those.

> I'm not sure though how we should treat IBMBIO.COM over 29k.

By not loading it fully.
It has a second-stage bootsector at the beginning of it
(also mentioned in the link you pointed)


Ah yes, good catch, I'd forgotten this.


fix for issue #137


Linksys WRT1900ac v1 (ARM/mvebu/mamba)


@yfdyh000 I suggest to use our mailing lists (or IRC in #l10n) to ask these questions, not development pull requests.
"Intel" means "information" ("intelligence").


dead code?


Так что насчёт старой строки routing_start?


Good job :)


? La fin de la phrase apparait dans une autre clé normalement.


Scalable-Units-Pumps (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1445 of 1445 tests passed)

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


Oh that's interesting :wink: So how the government controls this?


When I created the hdimage file with the same geometry 306/4/17 and have MS-DOS 3.3 formatted it, it was made with 32 root sectors, just the same as FAT16 HD. I figured the 14 root sectors was set in Dosemu for floppies, so shuffled the code to maintain that value for them.


Use spawn instead of exec&nohup. Don't use a log file. Attach a listener to stdout of the child process instead.


Attention `osm_id` is still present in the `fields`. And I added the `osm_id` on purpose to be more consistent - even if Mapbox does not do it - but your decision.

https://github.com/osm2vectortiles/osm2vectortiles/blob/b81e11cfb88b53d62fd0700ba0b9ef59aaf78fe7/open-streets.tm2source/data.yml#L562


@Propanu you'll likely want to do the same thing in UPM


LGTM


Updated this as well in the latest patch.


Thanks!


Thanks.


The switch from studio.h from cstdio should be uneccessary in C++ cstdio is preferred because it imports the functions into the std namespace


We shouldn't use `Object.assign` un-polyfilled for the server side JS though as it won't work in versions without ES2015 support.


Shouldn't it be deleted then? This is the only thing that I would correct from this PR. Besides this it is OK for me


Why is there still lein-cljsbuild "1.1.0" included in the :dev profile? Why was it moved out of the dev profile with this commit? The current template seems to be broken for me, but guess the changes are not yet released.


J'ai bien compris, ce n'est pas le caractère incomplet de la chaîne qui me dérange mais le "sur comment" et "vous rendre" (vous êtes cernés ?), que je propose d'améliorer


I am one of the developers for ImageMagick and I am happy to see that you are making some changes to our OpenCL code. I hope you are planning to send us a pull request later. Could you please remove the block below you send us these requests?

```C
const char *force_ocl = getenv("MAGICK_OPENCL_FORCE_ENABLE");
if (force_ocl && strcmp(force_ocl, "1") == 0)
```
We already have an option to disable OpenCL here: https://github.com/ImageMagick/ImageMagick/blob/master/MagickCore/accelerate.c#L111


oops I missed that one


Ok, then I need to know how much of IBMBIO.COM you want to load for that, or since it was loading 4 sectors before and presumably worked, should I just maintain that value?


fftw is also required. I suggest adding instructions on how to install them with homebrew.


exercices!!!! ERRADO CARAIO


Yes, I refactored this but it still has some padding specifications, etc.


可能是musl对mt720支持不行吧

2015-11-11 21:46 GMT+08:00 Syrone Wong <notifications@github.com>:

> Linksys WRT1900ac v1 (ARM/mvebu/mamba)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/wongsyrone/openwrt-1/commit/cbfae54ddc3f05824b5f8d37eafb4ac51493dbc9#commitcomment-14329052>
> .
>


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4533](https://teamcity.mesosphere.io/viewLog.html?buildId=72532&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 199 Build time: 00:04:10


Sure.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4535](https://teamcity.mesosphere.io/viewLog.html?buildId=72535&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 199 Build time: 00:04:58


能从日志里找错问题原因吗？

2015-11-11 21:53 GMT+08:00 ql li <gxfclql@gmail.com>:

> 可能是musl对mt720支持不行吧
>
> 2015-11-11 21:46 GMT+08:00 Syrone Wong <notifications@github.com>:
>
>> Linksys WRT1900ac v1 (ARM/mvebu/mamba)
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/wongsyrone/openwrt-1/commit/cbfae54ddc3f05824b5f8d37eafb4ac51493dbc9#commitcomment-14329052>
>> .
>>
>
>


"pure-button-primary" will make it blue, essentially. I thought of keeping just the "Add" for Balance entries that way, since that will be the primary operation, but if you think it's worth spreading to other forms, I can do that here as well :) Should I add to "List", too?


I tried to use the new target and modified MANIFEST.MF files but still was not able to get the IDE to run. A WebEx/tcon would be helpful.


You can actually use the `@param {...@var...}` notation here to define this.


See above. I can add it here if you want.


no problem, just made me confused :)


Also, then my test cases would no longer run so I reverted the MANIFEST.MF file so that I could continue test case development.


> dnsmsg.c: query_recv: 74
找这个文件的那个函数那个行看看？因为过滤效果一般而且作者貌似已经不开发了，所以我用过一两次之后就不再使用了


just pushed out a fix to Clojars


Not really, sorry about that. Font Awesome recommends using either <i> or <span> to create the icons. <span> would be more correct, but all examples are with <i> and they state it's just because it is shorter and easier to type.

So yeah, it's there JUST for the icon. The text should really be outside.


We don't have disabled it. There were discussions around it a few times already, but noone has done it (and few have permissions to do it). In any case, it's very unlikely we would lose (any significant) commits with so many forks floating around.


@alxndrsn any thoughts on these comments?  should we make these changes?  did you want me to make them?


Aaaaaaah :joy: I even rebased the entire branch to update the commit messages before pushing, but fell back to my usual habits on this commit.


I see. Nice to learn!


My bad. Here's how it looks:

![screen shot 2015-11-11 at 11 56 20 am](https://cloud.githubusercontent.com/assets/69997/11092534/5498a3f8-886b-11e5-9492-fbc742a90d92.png)


It is just a nit, but I would say yes. Anyways, up to you. Please go ahead and merge when you think it is fine.


No, this is not right.

All download recipes need a url_downloader, so we should only make it once. I'll fix this up so that it does this correctly.


Awesome!!!!!


It would be good if these were the other way round within the device, to confirm we don't have personality ID and slot count reversed.


like I said in the ticket comments this was preventing the patientDashboard from loading.
description is no longer a property of ConceptName, the only property in the class I thought I could replace it with was name. sn is shortName


Thanks, fixed.


"publishers were only"?


A parte comentada? Acho que sim. Eu gosto de deixar comentado por um tempo, porque as vezes você percebe no dia seguinte que o código novo não funciona. Mas aparentemente está funciondando sim.


"subscribers always subscribed automatically"?


I'll do it on a follow-up. I'll merge just the icons now.


Any reason why you didn't upgrade to the latest ruby 2.2.3?


So is the main reason for unmounting `/Users` the clash with `targetPath`? If so, wouldn't it be better to only unmount when there is a clash? Or does the mount have a negative impact on performance, even if it's not being used by the container?

The main reason for not using b2d-sync for the second container is that the sync needs to be bidirectional. The container contains our testing framework, which needs to read configuration files from the current host directory and write test reports back into that directory.


これで()外してもまだエラー出ますか？


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 4534](https://teamcity.mesosphere.io/viewLog.html?buildId=72534&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:07
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


The next few lines should be outside of file creation contextmanager.


$ git pull
remote: Counting objects: 51, done.
remote: Compressing objects: 100% (51/51), done.
remote: Total 51 (delta 26), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (51/51), done.
From https://github.com/elieserdejesus/JamTaba
   dce99cf..f5e1206  master     -> origin/master
Updating dce99cf..f5e1206
Fast-forward
 Client/Jamtaba-common.pri                          |  11 +++-
 Client/Standalone/Jamtaba2 - Stringer.ico          | Bin 922170 -> 0 bytes
 Client/Standalone/Jamtaba2.ico                     | Bin 16958 -> 922170 bytes
 Client/Standalone/Standalone.pro                   |   3 +-
 Client/src/MainController.cpp                      |  13 +++-
 Client/src/gui/MainWindow.cpp                      |   5 ++
 Client/src/gui/MainWindow.h                        |   5 +-
 Client/src/gui/MainWindow.ui                       |  10 ++-
 Client/src/gui/widgets/CustomTabWidget.cpp         |  44 +++++++++++++
 Client/src/gui/widgets/CustomTabWidget.h           |  23 +++++++
 Client/src/performance/MacPerformanceMonitor.cpp   |  19 ++++++
 Client/src/performance/PerformanceMonitor.h        |  19 ++++++
 .../src/performance/WindowsPerformanceMonitor.cpp  |  70 +++++++++++++++++++++
 13 files changed, 216 insertions(+), 6 deletions(-)
 delete mode 100644 Client/Standalone/Jamtaba2 - Stringer.ico
 create mode 100644 Client/src/gui/widgets/CustomTabWidget.cpp
 create mode 100644 Client/src/gui/widgets/CustomTabWidget.h
 create mode 100644 Client/src/performance/MacPerformanceMonitor.cpp
 create mode 100644 Client/src/performance/PerformanceMonitor.h
 create mode 100644 Client/src/performance/WindowsPerformanceMonitor.cpp

i got it !
Tested , but cpu can't be read by human on gui because of refresh = 0


Also check if bz2 file exists or not on the disk. Use os.path.exist


之前我用的还可以的 不知道你网络环境问题 感觉他的思路蛮不错的 ，现在还有那些好的工具推荐下

在 2015年11月11日 下午9:55，Syrone Wong <notifications@github.com>写道：

> dnsmsg.c: query_recv: 74
> 找这个文件的那个函数那个行看看？因为过滤效果一般而且作者貌似已经不开发了，所以我用过一两次之后就不再使用了
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/wongsyrone/openwrt-1/commit/cbfae54ddc3f05824b5f8d37eafb4ac51493dbc9#commitcomment-14329296>
> .
>


**Code Quality: Nitpick*

Variables like these are better declared within a configuration file to make it accessible application wide. It's much cleaner.


Claro! "Seems legit!" =P
Não tenho certeza, mas acho que sim.De qualquer forma, deve ser difícil alterarem um anexo já enviado.


There is no guaranty that the file exists, as I said in the above comment, please create the bz2 file in the setup part, so that we know for sure all tests should have that file.


After everything is done, remember to remove the .bz2 and the text file in the teardown.