TeamCity Ignite :: Ignite Cache 2 [Build 257](http://204.14.53.152/viewLog.html?buildId=59855&buildTypeId=Ignite_IgniteCache2&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 469, muted: 25 Build time: 00:23:20


TeamCity Ignite :: Ignite Cache Tx Recovery [Build 253](http://204.14.53.152/viewLog.html?buildId=59860&buildTypeId=Ignite_IgniteCacheTxRecover&guest=1) is now running


@btovar please backport this to the 5.X releases.


Can we define 1 nautical mile to be 5280.0 / (1852.0 / 0.3048) statute miles, 1.0 / 1852.0 meters, and 1.0 / (1852.0 / 0.3048) feet?


ups thank you for fixinf this!


TeamCity Ignite :: Ignite Cache 2 [Build 258](http://204.14.53.152/viewLog.html?buildId=59856&buildTypeId=Ignite_IgniteCache2&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 469, muted: 25 Build time: 00:23:30


TeamCity Ignite :: Ignite Cache Tx Recovery [Build 254](http://204.14.53.152/viewLog.html?buildId=59861&buildTypeId=Ignite_IgniteCacheTxRecover&guest=1) is now running


Sync with Master.


TeamCity Ignite :: Ignite Logging [Build 1712](http://204.14.53.152/viewLog.html?buildId=59859&buildTypeId=Ignite_IgniteLogging&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1 Build time: 00:03:38


TeamCity Ignite :: Ignite Cloud [Build 281](http://204.14.53.152/viewLog.html?buildId=59862&buildTypeId=Ignite_Cloud&guest=1) is now running


Better make it 8MU, Endless Hunger is coming.


develop (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1269 of 1269 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)


拿到这个题目后，首选决定了使用Node做后端服务，因为最近在学习express。
功能不是太复杂，但是第一次处理这样的业务逻辑，还是值得好好思考。


TeamCity Ignite :: Ignite WebSessions [Build 1621](http://204.14.53.152/viewLog.html?buildId=59858&buildTypeId=Ignite_IgniteWebSessions&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 8, muted: 1 Build time: 00:05:41


```$this->getListFromRedis($params);``` get a fatal error

``` ModLoggedHelper::getListFromRedis ``` used now


TeamCity Ignite :: Ignite Cloud [Build 282](http://204.14.53.152/viewLog.html?buildId=59863&buildTypeId=Ignite_Cloud&guest=1) is now running


:+1: thanks


Got it, that's what I thought, but I'm glad to know for sure. Thanks!


Tried building TWRP with that flag, but it didn't boot not so long ago. But maybe something else was broken.


One argument constructor => almost always *explicit*!
The *explicit* keyword in this case prevents calling your constructor with object of some strange type that can be casted to integer.


TeamCity Ignite :: Ignite Cloud [Build 281](http://204.14.53.152/viewLog.html?buildId=59862&buildTypeId=Ignite_Cloud&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 2, muted: 2 Build time: 00:03:41


@Nadahar doesn't quite qualify as a 'mess' imo. The joke is I was scratching my head even though I wrote those original ```return```s :P.


TeamCity Ignite :: Ignite GCE [Build 241](http://204.14.53.152/viewLog.html?buildId=59864&buildTypeId=Ignite_Gce&guest=1) is now running


*Retirando código JavaScript da página principal


Yes, MinGW can produce a library using the native Win32 threads.

As it currently stands, if I compile a `libblosc.dll` using mingw, this `!defined(__GNUC__)` forces me to use pthreads, which are not standard on Win32, and hence require the libblosc user to link MinGW's pthreads implementation.

(This arises in building `libblosc.dll` for use with the Julia Blosc package.)


It could me multiple plugins configured for this hook. For example mem3 could be converted into plugin and in this case it would be responsible for `_nodes` database. Plugins not suppose to return errors for this particular hook. They return `true` when the name is valid. Having that said we have following options:
- do call to `is_systemdb` before we call `couch_epi` (this wouldn't solve the problem with were to place check of a regex)
- have default validation in couch app (as we currently do in validate_dbname_int)
- move the responsibility to call default validation fun into `couch_db_plugin.erl` as we do [here](https://github.com/cloudant/couchdb-chttpd/blob/epi_hooks/src/chttpd_auth.erl#L71)

I would tend to choose option 3

Let me know if it would work for you.


you misspelled "canola"


搭建express开发环境，使用VS Code开发。
这里的包依赖中，handlebars之后被弃用了，改为ejs。因为会和前端的mvvvm框架冲突，不好解决。


~~Меня подставили~~. Сейчас еще раз проверил, оказывается bundler по дефолту его добавляет.


This method should be marked as **const** because logic says that it doesn't mutate the underlying object.


That description "Fixed int test" was meant for some other commit...


https://github.com/plone/plone.app.content/blob/linkintegrity/plone/app/content/browser/contents/delete.py#L58 checks if there are breaches on object and https://github.com/plone/plone.app.content/blob/linkintegrity/plone/app/content/browser/contents/delete.py#L61 returns the formatted breach html output.

Looks like your changes broke plone.app.content integration. I imagine there are errors in the log if you check.

Notice you renamed checkObject and also removed the skip_context options on __call__ in plone/app/linkintegrity/browser/info.py


@technobly, I was thinking of using the Serial2 for production programing purposes and testing. Is this OK to use Serial2 for this purpose? I also have USB broken out too.


TeamCity Ignite :: Ignite Cloud [Build 282](http://204.14.53.152/viewLog.html?buildId=59863&buildTypeId=Ignite_Cloud&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 2, muted: 2 Build time: 00:04:56


TeamCity Ignite :: Ignite GCE [Build 242](http://204.14.53.152/viewLog.html?buildId=59865&buildTypeId=Ignite_Gce&guest=1) is now running


This change on line 69 is causing this error **cfndsl-0.2.1/lib/cfndsl/JSONable.rb:69: Undefined symbol: to_ary** .  The .rb file has not been modified since this error started.


Подобные конструкции вносят некую таинственность... А хочется полной ясности :) В данном случае я не стал бы юзать require_all а подключил бы все ручками. Но это опять же мое мнение и про красоту


Maybe this is not the best interface here. Should be split in multiple interfaces probably.


TeamCity Ignite :: Ignite GCE [Build 241](http://204.14.53.152/viewLog.html?buildId=59864&buildTypeId=Ignite_Gce&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1 Build time: 00:03:29


Why'd you remove the media queries?


TeamCity Ignite :: Ignite Cache Full API [Build 1185](http://204.14.53.152/viewLog.html?buildId=59866&buildTypeId=Ignite_IgniteCacheFullApi&guest=1) is now running


设计了功能相关的几个接口。这应该属于软件工程的设计阶段，但总是因为考虑不周到而带来麻烦。不过这次的需求很明确了，所以后面接口的改动不是很大。


Was there a reason you applied your multipliers to timeout, rather than to adjHealth?


Actually the current implementation is pretty bad as well. It only adds an adjustmentcommand if a matching command is found. There's probably no reason to not just add all adjustmentcommands to the end regardless of existing commands.


Record is renamed in https://github.com/cloudant/couchdb-chttpd/commit/c1a0bd9772b861f0102690d8bc977b0af38e4d98


TeamCity Ignite :: Ignite GCE [Build 242](http://204.14.53.152/viewLog.html?buildId=59865&buildTypeId=Ignite_Gce&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1 Build time: 00:03:32


TeamCity Ignite :: Ignite Cache Expiry Policy [Build 1161](http://204.14.53.152/viewLog.html?buildId=59867&buildTypeId=Ignite_IgniteCacheExpiryPolicy&guest=1) is now running


TeamCity Glyssen :: Glyssen-master Continuous [Build *.*.898.d6c6ce3114fcb9769b35d4df95f0df6d3984e918](http://build.palaso.org/viewLog.html?buildId=60881&buildTypeId=bt431) outcome was **SUCCESS**
Summary: Tests passed: 410, ignored: 4 Build time: 00:02:43


TeamCity Ignite :: Ignite Cache Tx Recovery [Build 253](http://204.14.53.152/viewLog.html?buildId=59860&buildTypeId=Ignite_IgniteCacheTxRecover&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 74 Build time: 00:12:47


TeamCity Ignite :: Ignite Geospacial Indexing [Build 1575](http://204.14.53.152/viewLog.html?buildId=59868&buildTypeId=Ignite_IgniteGeospacialIndexing&guest=1) is now running


这里实现了根据路径获取文件信息的接口。去查Node的API，成功得拿到了数据。并使用Q promise解决了一个异步获取数据的return问题。


ActuallyUpdateCopyrightYears (Myoldmopar) - i386-Windows-7-VisualStudio-12: OK (1795 of 1795 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)


TeamCity Ignite :: Ignite Cache Tx Recovery [Build 254](http://204.14.53.152/viewLog.html?buildId=59861&buildTypeId=Ignite_IgniteCacheTxRecover&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 74 Build time: 00:12:44


TeamCity Ignite :: Ignite Geospacial Indexing [Build 1576](http://204.14.53.152/viewLog.html?buildId=59869&buildTypeId=Ignite_IgniteGeospacialIndexing&guest=1) is now running


This comment needs fix anyway, because git grep ADDRMAN_UNKNOWN_BUCKET_COUNT is empty.


nice :) :heart:


Ah yes, did not mean to write int there, thanks for catching that. I've clarified it now hopefully, any ISO 8601 date string works. No combined date+time strings, as we don't store that information at this point.


Exception was the right use here. Please revert.


ActuallyUpdateCopyrightYears (Myoldmopar) - Win64-Windows-7-VisualStudio-12: OK (1795 of 1795 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)


The user isn't getting any feedback now ..


Please report this in secp256k1's repo.


Feedback? What type of feedback I want to get when I press `Cancel`?


Congratulations! This is your first memory leak! :)
When you create something with **new** you should clean it afterwards with **delete**.
Welcome to C++ world!

Cleaner solution will be to:
1. Have class SinglyLinkedList that will hold a pointer to first element of the list and manage lifetime of list nodes (allocate memory for them, delete them in destructor).
2. Implement iterator class and use it to iterator over list or to insert new nodes.

But that's tricky. So let's just write a function that will iterate over list end delete all it's elements. And then call it for myList.


完成了其余接口的实现。
实现上传文件接口时，采用硬链接方式将上传来的文件添加到目标路径。看起来似乎没什么问题，而且实现比较简单。如果有正规方法的话，这只能叫猥琐通关了。


TeamCity Ignite :: Ignite Geospacial Indexing [Build 1575](http://204.14.53.152/viewLog.html?buildId=59868&buildTypeId=Ignite_IgniteGeospacialIndexing&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 3 Build time: 00:04:19


TeamCity Ignite :: Ignite AOP [Build 1787](http://204.14.53.152/viewLog.html?buildId=59870&buildTypeId=Ignite_IgniteAop&guest=1) is now running


you didn't had to fork to change this...
if you want to open an issue I can guide you


TeamCity LabkeyModules15.2 :: CDS postgres 9.4 [Build 6](https://teamcity.labkey.org/viewLog.html?buildId=265506&buildTypeId=LabkeyModules152_CdsPostgres93) outcome was **FAILURE**
Summary: Tests failed: 3, passed: 22 Build time: 00:34:53
### Failed tests
```
org.labkey.test.tests.CDSVisualizationTest.verifyBoxPlots: <no details avaliable>

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

org.labkey.test.tests.CDSTest.verifyHomePage: <no details avaliable>

```


TeamCity Ignite :: Ignite Geospacial Indexing [Build 1576](http://204.14.53.152/viewLog.html?buildId=59869&buildTypeId=Ignite_IgniteGeospacialIndexing&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 3 Build time: 00:04:21


TeamCity Ignite :: Ignite AOP [Build 1788](http://204.14.53.152/viewLog.html?buildId=59871&buildTypeId=Ignite_IgniteAop&guest=1) is now running


Oh, btw, the `store` -> `[]=` change is completely unnecessary in this case. But whatever.


this welcome right


This is a try/catch, it's used to implicitly catch exceptions. If you want to explicitly catch a use-case you do not use try/catch. In this case you need to validate the result and if the result was empty you dismiss the function call. The try/catch is not in-place to handle this use case, it's in place to handle edge-cases.


因为git的操作失误，少传了一个文件夹。
顺便说一下，后台接口的测试使用了Fiddler，这个工具也是最近才学会用，非常方便。
之前因为研究前后端分离架构，觉得这个工具以后会在设计思路上帮上忙。


Sure, thanks. I did try using the template argument in my model, but looking at the default getGroupTemplate function it seemed to rely on a lot of internal data.


I found it here: https://www.threadingbuildingblocks.org/docs/help/reference/containers_overview/concurrent_hash_map_cls.htm


91958608DOASEffectOnZoneSizing (wfbuhl) - Win64-Windows-7-VisualStudio-12: Tests Failed

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


Keep a slightly larger buffer around rather than realloc a slightly smaller one.


It seems to indicate that thread-safe access is possible through the accessor class.


Hocam bu çok daha iyi. Ama koşmadan önce emeklemek lazım. :)


Some inefficiencies in global memory read/write pattern caused cache evictions (arising from not full utilization of 64-byte cachelines). Since ECC mechanism relies on tagging and error correction at the cahceline level, it affected performance. This has been largely fixed now.


This vector is not changed inside the function.
So it would more efficient to pass it as **const reference**
```cpp
  const std::vector<int>& values
```
This will avoid copying the vector on function call and will just use the vector from calling place.
It will be equally efficient to pass it simply by reference but we want to give a guarantee to function caller that we won't change his vector inside the function.


You could DRY things slightly by calling model.set({...}) here and in a few other spots.


TeamCity LabkeyTrunk :: CDS postgres 9.4 [Build 295](https://teamcity.labkey.org/viewLog.html?buildId=265508&buildTypeId=LabkeyTrunk_CdsPostgres93) outcome was **FAILURE**
Summary: Tests failed: 28, passed: 2 Build time: 00:08:53
### Failed tests
```
org.labkey.test.Runner: org.labkey.test.tests.CDSSecurityTest: <no details avaliable>

org.labkey.test.tests.CDSSecurityTest.verifyUserPermissions: <no details avaliable>

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

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

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

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

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

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

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

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

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

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


!values.empty()


This is not the check you would want, since `overwrite_ttl = false` would still test `true` against `present?`


Why you removed it? This means you definitely need to pass it in. hm :|
might be fine :)


Assignment 5 update.


I think that notify would be good to use here.


Don't forget to delete list!


TeamCity Ignite :: Ignite AOP [Build 1787](http://204.14.53.152/viewLog.html?buildId=59870&buildTypeId=Ignite_IgniteAop&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 117 Build time: 00:08:22


TeamCity Ignite :: JCache TCK [Build 1044](http://204.14.53.152/viewLog.html?buildId=59872&buildTypeId=Ignite_JCacheTck&guest=1) is now running


This commit resolves #76


Not a bad start but I did notice some mistakes in the body of the code. Your logic was actually very good, however you made some silly tiny mistakes that will show you just how temperamental code can be:
- line 68 you wrote your return statement outside of the brackets for the getWinner function.
- line 48 and line 50 you capitalized both "Player" and "Computer" and down in your playToFive function you are checking for lowercase "player", so every time you check the value of winner you'll never find "player" and it will think the computer is winning every time.
- lines 46, 53, and 60 should all be `else if`'s. Look these statements up to find out why these are better(it'll be a good exercise to practice your google-fu!).


If it were up to me, I'd have both `moveToEnd` and `pull` defined inline where they're used. IMO this is creeping toward TKism...


My bad, I was looking at ```tbb::concurrent_unordered_map```


This commit replaces `auth_name` function with the explicit value passed in `#user_ctx.handler`.
It fixes an existent problem with `authenticated` field missing in the response.
Implementation of `auth_name` used to be a guess based on none documented module naming convention.


TeamCity Ignite :: Ignite AOP [Build 1788](http://204.14.53.152/viewLog.html?buildId=59871&buildTypeId=Ignite_IgniteAop&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 117 Build time: 00:08:01


TeamCity Ignite :: JCache TCK [Build 1045](http://204.14.53.152/viewLog.html?buildId=59873&buildTypeId=Ignite_JCacheTck&guest=1) is now running


We want to bubble the interrupted result to managed here.


No problem, tbb::concurrent_unordered_map looked like a giant pile of 'nope', so I decided to use something a little different.


TeamCity Ignite :: JCache TCK [Build 1044](http://204.14.53.152/viewLog.html?buildId=59872&buildTypeId=Ignite_JCacheTck&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 464 Build time: 00:01:58


If we got interrupted before the calling kqueue itself, we probably can get away from closing it.


TeamCity Ignite :: Ignite WebSessions [Build 1622](http://204.14.53.152/viewLog.html?buildId=59874&buildTypeId=Ignite_IgniteWebSessions&guest=1) is now running


We do, when interrupted is TRUE, the callback was called, and res is -1.


:dog: such win, right there


Awesome, thanks @lpantano!


TeamCity Ignite :: JCache TCK [Build 1045](http://204.14.53.152/viewLog.html?buildId=59873&buildTypeId=Ignite_JCacheTck&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 464 Build time: 00:02:00


TeamCity Ignite :: Ignite Visor Console [Build 1624](http://204.14.53.152/viewLog.html?buildId=59875&buildTypeId=Ignite_IgniteVisorConsole&guest=1) is now running


It's dangerous to access a pointer that was given to you by a stranger. You should check that it's not null first!


前端使用的是avalon+手写css+seajs模块化处理。
avalon是司徒正美的mvvm框架，seajs是玉伯的模块化库，整个前端居然用的都是国货。
画这个页面用了好大的功夫，虽然没什么卵用。
当然如果可以的话，我会选择使用fis，但不清楚目标计算机上是否安装了fis（以防万一），而没有用这个工具。


Sorry, just renamed repos to remove the inconsistent dashes, but unfortunately the "fdroid" user namespace is taken :/


Sorry about this one. I had some problems with my internet connection and I thought that the last one was not uploaded.


Anyway, is this still not thread safe (considering the new class)?


Notify only works on the main window.


@ChrisPetr0 are you able to show me what you're passing into `FnNot`, In the mean time I'll revert this as I don't want it causing others issues too


Haha dogru :)


updated.

On Mon, Aug 10, 2015 at 2:16 PM, W. Trevor King <notifications@github.com>
wrote:

> The mailing list gets a separate section (since we use it outside of the
> weekly-call context), so I think the IRC channel should also get a separate
> section (e.g. see #102 <https://github.com/opencontainers/specs/pull/102>'s
> 6ef382b
> <https://github.com/vbatts/specs/commit/6ef382b69c23b2f45f1d46ea5de6e9f2537c86f6>
> ).
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/vbatts/specs/commit/d7bf181ffe3e22e2707d905575ad4a0e4348c577#commitcomment-12621751>
> .
>


Some sort of alert?


TeamCity Ignite :: Ignite WebSessions [Build 1622](http://204.14.53.152/viewLog.html?buildId=59874&buildTypeId=Ignite_IgniteWebSessions&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 8, muted: 1 Build time: 00:03:40


TeamCity Ignite :: Ignite URI Deploy SPI [Build 1609](http://204.14.53.152/viewLog.html?buildId=59876&buildTypeId=Ignite_IgniteUriDeploySpi&guest=1) is now running


 since this is an abstract class and not an interface it shouldn't be IMatrix.
 It could be AbstractMatrix or Matrix depending on the teams convention
 Also this class implements all its functions so it doesn't need to be abstract


typo vlaues


It is still not thread safe becuase you modify ```access``` after it is inserted into the map. You must fully initialize ```access``` before putting it into the map.


I believe you've meant [std::set<int>](http://en.cppreference.com/w/cpp/container/set) here.
Basic syntax:
```cpp
   std::set<int> table;
   table.insert(42);
   if (table.find(42) != table.end()) {
     std::cout << "42 is in set, neat!" << std::endl;
   }
```


duplication here


first


Unutmadan http://underscorejs.org/docs/underscore.html ve https://github.com/tryghost/Ghost kaynak kodlarini inceleyerek ogrenmek icin fena degiller. https://github.com/airbnb/javascript da kod standartlari acisindan iyi bir kaynak.


Yes, this is possible. Today I thought about possible "scenario":
1) when rebooting to lpm, store in param.lfs bootmode=3(if rebooting from system) or bootmode=4(if rebooting from recovery)
2) usr/u8500_initramfs_files/init should be edited accordingly
3) you should load j4fs.ko and param.ko as early as possible
4) once detected bootmode==3 or bootmode==4, you should append lpm_boot=1 to command line

Do you still think that worth it? ;)


By Clean code convention no need for too many comments


TeamCity Ignite :: Ignite Visor Console [Build 1624](http://204.14.53.152/viewLog.html?buildId=59875&buildTypeId=Ignite_IgniteVisorConsole&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 125, muted: 1 Build time: 00:04:55


TeamCity Ignite :: Ignite Start Nodes [Build 1646](http://204.14.53.152/viewLog.html?buildId=59877&buildTypeId=Ignite_IgniteStartNodes&guest=1) is now running


@kitsuta was this cherry-picked into master? (I had a note that we should do this from a while ago)


TeamCity Ignite :: Ignite Cache Expiry Policy [Build 1161](http://204.14.53.152/viewLog.html?buildId=59867&buildTypeId=Ignite_IgniteCacheExpiryPolicy&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 91, muted: 22 Build time: 00:21:54


TeamCity Ignite :: Ignite Spring [Build 1683](http://204.14.53.152/viewLog.html?buildId=59878&buildTypeId=Ignite_IgniteSpring&guest=1) is now running


clarified.

On Mon, Aug 10, 2015 at 2:21 PM, W. Trevor King <notifications@github.com>
wrote:

> Maybe “Before undertaking a non-trivial change…”? In the discussion on
> 2015-08-05 <https://plus.google.com/events/cqfpicicbnra9mv6kvpj0mb24u4>
> (after 26:02), a few folks felt the need to say typos and such should go
> straight to a PR. While that may be too obvious to deserve a full sentence
> here, I think it deserves a one-word addition ;).
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/vbatts/specs/commit/d7bf181ffe3e22e2707d905575ad4a0e4348c577#commitcomment-12621897>
> .
>


This seems to indicate otherwise (when read in conjunction with the other link about the accessor class): https://www.threadingbuildingblocks.org/docs/help/reference/containers_overview/concurrent_hash_map_cls/concurrent_operations_hash.htm

The accessor is set *during* the insert within the tbb class.


Well.. that's what I was using .. :p


make this static since it's a constant.
Also naming convention is constants are all caps


Thanks to @AndreiLux


testing


First Commit


Is there a reason to control flow by exception, rather than say by breaking out into a small method:

```ruby
      if Puppet::FileSystem.symlink?(puppet_modules_vendor_folder)
        unlink(puppet_modules_vendor_folder)
      elsif Puppet::FileSystem.exist?(puppet_modules_vendor_folder)
        append_location_with_current_date_time puppet_modules_vendor_folder
      end
```

And just using normal `if` type control flow?

```ruby
def unlink(path)
    if Puppet::FileSystem.exist?(Puppet::FileSystem.readlink(path))
      Puppet::FileSystem.unlink(path)
    else
      # If the target path doesn't exist, unlinking will fail.
      # Instead prefer to move the path so the link creation
      # can occur successfully.
      Puppet.warning "Error occurred attempting to remove old symlink. It's likely the target path no longer exists. Renaming the link instead."
      append_location_with_current_date_time path
    end
end
```

Then we PUP-5018 gets fixed, we can theoretically replace the call to `unlink` with `Puppet::FileSystem.unlink` and just delete this method.

Thoughts?


Compiler doesn't complain when compiling this file:
index.ts:
```typescript
///<reference path="typings/angular2/angular2.d.ts"/>
///<reference path="typings/router/router.d.ts"/>
console.log('hi');
```


:pizza:


TeamCity Ignite :: Ignite URI Deploy SPI [Build 1609](http://204.14.53.152/viewLog.html?buildId=59876&buildTypeId=Ignite_IgniteUriDeploySpi&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 32 Build time: 00:06:24


@lfu This is only taking into account a single appliance configuration instead of looking at all the configurations in the environment.  Additional event filters could be setup on a different server that is designated as the event monitor and they would not be included.  You need a method that loops over all the 'event_handling` configurations and returns a complete list of event names to process against.


It seems that ```concurrent_hash_map``` has a serious problem. The documentation on
 https://www.threadingbuildingblocks.org/docs/help/index.htm#reference/containers_overview/concurrent_hash_map_cls.htm

says 'The concurrent operations (count, find, insert, and erase) invalidate any iterators pointing into the affected instance even with a const qualifier. It is unsafe to use these operations concurrently with any other operation.'
So if you use iterators to the map anywhere, they are not guaranteed to be correct. I haven't looked close enough at the code to see if that is true.


TeamCity Ignite :: Ignite SPI [Build 1704](http://204.14.53.152/viewLog.html?buildId=59879&buildTypeId=Ignite_IgniteSpi&guest=1) is now running


And it wasn't very good IMO because the content of this alert was very specific. I think you just need to write a good text for this alert. But also I suggest to add a simple box with red border saying that no colors will be imported or something like that under "Import" button if the user pressed Cancel.


Good idea


Effective testing of this UI and the orch layer behind it I think means using some of the information/ideas/action as described here  https://broadinstitute.atlassian.net/wiki/display/DSDE/Mock+Configuration+Data


RoomAirflowNetwork (lgu1234) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1796 of 1796 tests passed)

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


Like it.


Whisker menu now looks beautiful. :'D Thanks @ochosi!


TeamCity Ignite :: Ignite Spring [Build 1683](http://204.14.53.152/viewLog.html?buildId=59878&buildTypeId=Ignite_IgniteSpring&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 73, muted: 1 Build time: 00:05:36


TeamCity Ignite :: Ignite Scalar Examples [Build 1621](http://204.14.53.152/viewLog.html?buildId=59880&buildTypeId=Ignite_IgniteScalarExamples&guest=1) is now running


Cool!


Testcases missing!

- Add Unit tests. No manual testing! Write a function to compare two lists once and be happy.
- Check some corner cases (empty list, one element, all equal, all different)
- Try calling DeleteDuplicates twice on same random list and check that nothing changes (e.x. look at size).

![magnifying-glass-detective-9875_0dc4603c0e0b7dfe4515c58822eb8cca](https://cloud.githubusercontent.com/assets/1192958/9182338/c2aacd82-3fb2-11e5-9090-bd95ece803b3.jpg)


Hi Chris, as far as I can tell iterators in this instance are never used, I
will check more closely (but it is good to note that for the future).

On Mon, Aug 10, 2015 at 9:55 PM, Chris Jones <notifications@github.com>
wrote:

> It seems that concurrent_hash_map has a serious problem. The
> documentation on
>
> https://www.threadingbuildingblocks.org/docs/help/index.htm#reference/containers_overview/concurrent_hash_map_cls.htm
>
> says 'The concurrent operations (count, find, insert, and erase)
> invalidate any iterators pointing into the affected instance even with a
> const qualifier. It is unsafe to use these operations concurrently with any
> other operation.'
> So if you use iterators to the map anywhere, they are not guaranteed to be
> correct. I haven't looked close enough at the code to see if that is true.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/lgray/cmssw/commit/794bf67b39b5bd7c72ff35eebfd3f4e81eb43c56#commitcomment-12623797>
> .
>


You're confusing the message with the method. The MESSAGE wasnt very good, the method of delivery was fine, not ideal, but not a problem either. Happy to review any improvements you can make but lets not get confused over what is the issue.


This fixes #10


@lfu This delete logic could also be moved into the method that collects the event names.  It happens in a transaction and would only be committed if the entire process completes successfully.


sorry, not trying to be difficult, but i still don't see how this works.

let's take this example:
```
1.2.3.4:foo.port:5677
```
even through i and the build know the bind ip should be `1.2.3.4`, i have external code that does not and i want it to get the ip address and port from a single file using property names that i define. how do i accomplish that with a 3 part variant?

on some level, i think this discussion is similar to #198, it's just a different ip address being exposed. as an alternative, i think that same mechanism could be used to support this instead of changing the 3 part variant, we'd just need to decide how the xml should look.


TeamCity Ignite :: Ignite Start Nodes [Build 1646](http://204.14.53.152/viewLog.html?buildId=59877&buildTypeId=Ignite_IgniteStartNodes&guest=1) outcome was **FAILURE**
Summary: Tests failed: 18, passed: 1 Build time: 00:07:30
### Failed tests
```
org.apache.ignite.internal.IgniteStartStopRestartTestSuite: org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testStopNodes: org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
 at com.jcraft.jsch.Util.createSocket(Util.java:344)
 at com.jcraft.jsch.Session.connect(Session.java:215)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:101)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:38)
 at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6200)
 at org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:899)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:579)
 at java.net.Socket.connect(Socket.java:528)
 at java.net.Socket.<init>(Socket.java:425)
 at java.net.Socket.<init>(Socket.java:208)
 at com.jcraft.jsch.Util.createSocket(Util.java:338)
 ... 9 more

org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
	at com.jcraft.jsch.Util.createSocket(Util.java:344)
	at com.jcraft.jsch.Session.connect(Session.java:215)

org.apache.ignite.internal.IgniteStartStopRestartTestSuite: org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls: org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
 at com.jcraft.jsch.Util.createSocket(Util.java:344)
 at com.jcraft.jsch.Session.connect(Session.java:215)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:101)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:38)
 at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6200)
 at org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:899)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:579)
 at java.net.Socket.connect(Socket.java:528)
 at java.net.Socket.<init>(Socket.java:425)
 at java.net.Socket.<init>(Socket.java:208)
 at com.jcraft.jsch.Util.createSocket(Util.java:338)
 ... 9 more

org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
	at com.jcraft.jsch.Util.createSocket(Util.java:344)
	at com.jcraft.jsch.Session.connect(Session.java:215)

org.apache.ignite.internal.IgniteStartStopRestartTestSuite: org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testRestartNodesFiltered: org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
 at com.jcraft.jsch.Util.createSocket(Util.java:344)
 at com.jcraft.jsch.Session.connect(Session.java:215)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:101)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:38)
 at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6200)
 at org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:899)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:579)
 at java.net.Socket.connect(Socket.java:528)
 at java.net.Socket.<init>(Socket.java:425)
 at java.net.Socket.<init>(Socket.java:208)
 at com.jcraft.jsch.Util.createSocket(Util.java:338)
 ... 9 more

org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
	at com.jcraft.jsch.Util.createSocket(Util.java:344)
	at com.jcraft.jsch.Session.connect(Session.java:215)

org.apache.ignite.internal.IgniteStartStopRestartTestSuite: org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds: org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
 at com.jcraft.jsch.Util.createSocket(Util.java:344)
 at com.jcraft.jsch.Session.connect(Session.java:215)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:101)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:38)
 at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6200)
 at org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:899)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:579)
 at java.net.Socket.connect(Socket.java:528)
 at java.net.Socket.<init>(Socket.java:425)
 at java.net.Socket.<init>(Socket.java:208)
 at com.jcraft.jsch.Util.createSocket(Util.java:338)
 ... 9 more

org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
	at com.jcraft.jsch.Util.createSocket(Util.java:344)
	at com.jcraft.jsch.Session.connect(Session.java:215)

org.apache.ignite.internal.IgniteStartStopRestartTestSuite: org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testStopNodesFiltered: org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
 at com.jcraft.jsch.Util.createSocket(Util.java:344)
 at com.jcraft.jsch.Session.connect(Session.java:215)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:101)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:38)
 at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6200)
 at org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:899)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:579)
 at java.net.Socket.connect(Socket.java:528)
 at java.net.Socket.<init>(Socket.java:425)
 at java.net.Socket.<init>(Socket.java:208)
 at com.jcraft.jsch.Util.createSocket(Util.java:338)
 ... 9 more

org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
	at com.jcraft.jsch.Util.createSocket(Util.java:344)
	at com.jcraft.jsch.Session.connect(Session.java:215)

org.apache.ignite.internal.IgniteStartStopRestartTestSuite: org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testRestartNodesByIdsC: org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
 at com.jcraft.jsch.Util.createSocket(Util.java:344)
 at com.jcraft.jsch.Session.connect(Session.java:215)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:101)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:38)
 at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6200)
 at org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:899)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:579)
 at java.net.Socket.connect(Socket.java:528)
 at java.net.Socket.<init>(Socket.java:425)
 at java.net.Socket.<init>(Socket.java:208)
 at com.jcraft.jsch.Util.createSocket(Util.java:338)
 ... 9 more

org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
	at com.jcraft.jsch.Util.createSocket(Util.java:344)
	at com.jcraft.jsch.Session.connect(Session.java:215)

org.apache.ignite.internal.IgniteStartStopRestartTestSuite: org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testStartThreeNodesAndDoEmptyCall: org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
 at com.jcraft.jsch.Util.createSocket(Util.java:344)
 at com.jcraft.jsch.Session.connect(Session.java:215)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:101)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:38)
 at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6200)
 at org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:899)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:579)
 at java.net.Socket.connect(Socket.java:528)
 at java.net.Socket.<init>(Socket.java:425)
 at java.net.Socket.<init>(Socket.java:208)
 at com.jcraft.jsch.Util.createSocket(Util.java:338)
 ... 9 more

org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
	at com.jcraft.jsch.Util.createSocket(Util.java:344)
	at com.jcraft.jsch.Session.connect(Session.java:215)

org.apache.ignite.internal.IgniteStartStopRestartTestSuite: org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testStopNodesByIdsC: org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
 at com.jcraft.jsch.Util.createSocket(Util.java:344)
 at com.jcraft.jsch.Session.connect(Session.java:215)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:101)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:38)
 at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6200)
 at org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:899)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:579)
 at java.net.Socket.connect(Socket.java:528)
 at java.net.Socket.<init>(Socket.java:425)
 at java.net.Socket.<init>(Socket.java:208)
 at com.jcraft.jsch.Util.createSocket(Util.java:338)
 ... 9 more

org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
	at com.jcraft.jsch.Util.createSocket(Util.java:344)
	at com.jcraft.jsch.Session.connect(Session.java:215)

org.apache.ignite.internal.IgniteStartStopRestartTestSuite: org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testStartOneNode: org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
 at com.jcraft.jsch.Util.createSocket(Util.java:344)
 at com.jcraft.jsch.Session.connect(Session.java:215)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:101)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:38)
 at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6200)
 at org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:899)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:579)
 at java.net.Socket.connect(Socket.java:528)
 at java.net.Socket.<init>(Socket.java:425)
 at java.net.Socket.<init>(Socket.java:208)
 at com.jcraft.jsch.Util.createSocket(Util.java:338)
 ... 9 more

org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
	at com.jcraft.jsch.Util.createSocket(Util.java:344)
	at com.jcraft.jsch.Session.connect(Session.java:215)

org.apache.ignite.internal.IgniteStartStopRestartTestSuite: org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testRestartNodes: org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
 at com.jcraft.jsch.Util.createSocket(Util.java:344)
 at com.jcraft.jsch.Session.connect(Session.java:215)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:101)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:38)
 at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6200)
 at org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:899)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:579)
 at java.net.Socket.connect(Socket.java:528)
 at java.net.Socket.<init>(Socket.java:425)
 at java.net.Socket.<init>(Socket.java:208)
 at com.jcraft.jsch.Util.createSocket(Util.java:338)
 ... 9 more

org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
	at com.jcraft.jsch.Util.createSocket(Util.java:344)
	at com.jcraft.jsch.Session.connect(Session.java:215)

org.apache.ignite.internal.IgniteStartStopRestartTestSuite: org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testStartThreeNodes: org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
 at com.jcraft.jsch.Util.createSocket(Util.java:389)
 at com.jcraft.jsch.Session.connect(Session.java:215)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:101)
 at org.apache.ignite.internal.util.nodestart.StartNodeCallableImpl.call(StartNodeCallableImpl.java:38)
 at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6200)
 at org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:899)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)

org.apache.ignite.IgniteException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
	at com.jcraft.jsch.Util.createSocket(Util.java:389)
	at com.jcraft.jsch.Session.connect(Session.java:215)

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


I am going to implement a "dump all" feature soon-ish. It's still TODO right now though. It's all still WIP at the moment since I'm trying to improve on the old method :)


TeamCity Ignite :: Ignite Queries [Build 1665](http://204.14.53.152/viewLog.html?buildId=59881&buildTypeId=Ignite_IgniteQueries&guest=1) is now running


@churkin Looking at this now I think what we can avoid testing whole pipeline, but anyway in this case we shouldn't test from the `Session` perspective. We should directly test `UploadStorage` methods instead.


Useless commit.

```bash
git reset --hard HEAD~1
git push -f
```


woot


yeah besides `Object#present?` is a Rails activesupport feature, which I forgot about


asdf


Right again! Thanks once more.


Due to the way Java handles class inheritance, it's possible to return a CAScene as a Scene, since `CAScene extends Scene`, it's not really ambiguous as any subclass has implementations of the superclasses methods and variables. It would be an entirely different story if CAScene did not extend Scene, however.


RoomAirflowNetwork (lgu1234) - 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)


that would leave the documentation in the tagged version telling you that the old version was the newest. (the reference I'm referring to is in https://github.com/JuliaLang/julia/blob/5505cf83e2f00c9ebc9bfdb642dbce58495f4f76/README.md#source-download-and-compilation)


Whoops, I failed hard here. I'll fix.


The commit that bumps `VERSION` is the commit that gets tagged. So either this should be before, or long after - not between things that are supposed to be simultaneous.


其实我是在别的代码中发现的这个问题，那边是一个多线程程序。
GetStub内部是有一个锁的，如果不搞成成员变量的话，每次rpc都要去拿那个锁。
智能指针也不是线程安全的……我再想想有啥好办法不


The beginning time was not right. Need to change to 0:00 of the same day.


having the system ignore errors like this (during `cb`) is not good, it should only be ignoring the ones that come from `wait`


Was this file deprecated by another methodology for reading SQL databases, or was support just removed?


@davidmoten Do you see something like this being useful in rxjava-file?  It seems like the generics around ```WatchEvent```s are kinda funky, and the ```OVERFLOW``` event kind of throws a wrench in things (as it's generic type is an ```Object``` vs a ```Path```.  I would like to prevent having to cast, e.g.  ```(Path) event.context()```, is possible.


this is also likely simultaneous


Yes, I understand now. Thanks for the plugin, it solves a need for me!


I don't see in settings page. lol


Every feature should be valuable enough to offset the load it adds to the API (bug surface area, test coverage, LOC, cognitive overhead). I didn't think this one made the cut. If you feel strongly about it I can add it back. Alternatively the same separation could be achieved using a higher order function:

```js
function filter(filt, icpt) {
  return function() {
    return filt.apply(this, arguments)
      && icpt.apply(this, arguments)
  }
}

proxy.intercept('response', filter(function(req, resp, cycle) {
  // filtering logic
}, function(req, resp, cycle) {
  // intercept logic
}));
```


the only change in the commit that bumps `VERSION` should be to bump `VERSION`


Is there any way to check right at the start for the issue of the build directory's parent directories having spaces or other shell metacharacters, instead of "failing badly"?


可以使用js动态控制，不用一定要在元素上设置


0.6.1 isn't available in bower


one是投放区，投放区的各个事件都要加入e.preventDefault();


Besides, we don't install `README.md`, online documentation is generated live from the branch (AIUI) so edits that only matter for the live docs can be made post-tagging.


When I pulled these changes down, I get this error.

```
Conversion error: Jekyll::Converters::Scss encountered an error while converting 'assets/stylesheets/application.scss':
                    File to import not found or unreadable: bootstrap. on line 1
```

application.scss looks like this:

```
---
---

@import 'bootstrap';

```

If I delete the first three lines, I can get the project to run, but I'm not sure it's correct.


这里代码写错了。是ondragover


Thanks. Fixed in 20cf2dd0892d3d1b374d63d39d936ad60a0fb36e


What does this do? Meaning what is strict mode?


LG! merge


Yes, if it works. Can you test? I don't have an Edge browser set up yet.


this is test code


虽然在投放区投放成功了。不过后续的操作要自己取处理。这里直接appendChild(two)是如果document中有这个two节点，移动过去了。不会增加新的节点


what is nestTables?


Looks like a typo 'canals' instead of canola.


After fixing that, `add_page` (`malloc`) is called 100 times, exactly as many times as `pushStackFrame` is called. So there is little/no advantage of using stacks. Instead of freeing memory on `popStackFrame`, should we keep it in a queue that `add_page` can reuse instead of calling `malloc`?


I thought the other was better?


These casts are redundant. And the right shift should be replaced by a division, as it's not guaranteed that the sign bit gets extended.


Why so important to go from "->'?


这里设置数据可以使用事件参数ee.dataTransfer.setData(xxKey,"xxVal");注意这里只能传递string，或者file的值参数。参考如下网址 http://www.cnblogs.com/fsjohnhuang/p/3961066.html#t8


Thank you for reply.
But the problem is that ISO-2022-JP is wrongly mapped to CP932 (Shift_JIS) and I DON'T want this.
since Encoding.HeaderName property is iso-2022-jp in encoding object for shift_jis (see output in examples in the document), the lines deleted in this commit overwrites codepage of iso-2022-jp in aliases to 932.
the original problem was something like following.
1. at first, aliases["iso-2022-jp"] is 50221, which is correct.
2. GetCodePage("shift_jis") is called to parse email encoded with Shift_JIS.
3. aliases["iso-2022-jp"] is set to 932 as stated above.
4. after that, parsing email encoded with ISO-2022-JP returns garbage because it tries to parse data using wrong codepage 932.


I think something went wrong with the index changes- when I run any of the calorimeters now that use set_index_j, set_index_k, and set_index_l, Fun4All crashes with the message "unknown index 124". If I comment the set_index_l, it seems to run fine. It's not clear to me yet where exactly the bug is.


the SQL queries all use tendoo_ , which assumes that the prefix for the table names were left tendoo_ during the install. My table prefixes in my database are tenecp_  and not tendoo_ ... meaning that when you leave the code the way it was before, e.g., tendoo_query, and not appending the correct prefix to the table (whichever was used in the install, and in my case tenecp_ ) then the queries break when you run them or try to add a page in my case.

Best Regards,
Frank Pennock

Date: Sun, 9 Aug 2015 01:25:47 -0700
From: notifications@github.com
To: tendoo-cms@noreply.github.com
CC: frank.pennock@outlook.com
Subject: Re: [tendoo-cms] Began adding the prefix into the tables instead of hardcoding (2c6d302)

Hi,

all the changes you have applied to seems only to affect code structure. I have been looking for prefix hardcoded in this file, but i'didn't see it. Can you explain well what you're saying by "HardCoding Prefix" ?

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


GNU General Public License, version 2


Deleting Apple, we want to go with Gala Apple


relaxed.


This is final


sadsa


unnecessary trailing `\`


This is no longer a bower dep, hasn't been since it was ported to an ember-addon


let's get rid of the target with this too


You can solve this problem by pushing a frame at the start, prior to
running your code. This will ensure that the page is still around, and not
freed, during the run of your program. Then we can test this against the
cost of calling malloc/free repeatedly.

If it makes a difference, we can easily change the policy to not free up to
N pages right away.

-Mike

On Sun, Aug 9, 2015 at 7:28 PM, Abhishek Anand <notifications@github.com>
wrote:

> After fixing that, add_page (malloc) is called 100 times, exactly as many
> times as pushStackFrame is called. So there is little/no advantage of
> using stacks. Instead of freeing memory on popStackFrame, should we keep
> it in a queue that add_page can reuse instead of calling malloc?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/FStarLang/FStar/commit/e2806149af9194cbe96efc4ba4cd769b126f838a#commitcomment-12606850>
> .
>


changelog? :) http://webpack.github.io/docs/changelog.html still only shows 1.10


the index_l wasn't changed. That does sound like a mix in include files
or shared libraries. The changes were tested with the
Fun4All_G4_sPHENIX.C macro which went through. If you have private code
you need to wipe the install area and rebuild it from scratch otherwise
indices might be affected. If it's a macro which runs out of the box
with the current build - let me know and I'll have a look at this.
Chris

On 8/9/2015 10:37 PM, Nils Feege wrote:
> I think something went wrong with the index changes- when I run any of the calorimeters now that use set_index_j, set_index_k, and set_index_l, Fun4All crashes with the message "unknown index 124". If I comment the set_index_l, it seems to run fine. It's not clear to me yet where exactly the bug is.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/sPHENIX-Collaboration/coresoftware/commit/dde8eccbc09ecb780ce692100a09a2cd84b46174#commitcomment-12606872

--
*************************************************************

Christopher H. Pinkenburg	;    pinkenburg@bnl.gov
				;    http://www.phenix.bnl.gov/~pinkenbu

Brookhaven National Laboratory	;    phone: (631) 344-5692
Physics Department Bldg 510 C	;    fax:   (631) 344-3253
Upton, NY 11973-5000

*************************************************************


rebase ate previous comment, this should either be switched with 2 or after 10 or 11 - and really this can be done as soon as there's a release-n branch, it doesn't need to be done at tag time


Zend framework 2 skeleton


What happens if the METAR has SKC?  Is the `aw::sky_cover_type` still clear?  Should we differentiate between the two (since they have different meanings)?


Actually this change set resolves also the re-drawing issue of adjacent views


Yeah, I'm aware....just haven't gotten to it yet....all in time, thanks though


asdf


You should get warning from compiler here.
The reason is: comparing **int** and **size_t** types.
Usually it's not a big deal, but if your list has enormous size you will get infinite loop here because of the overflow in int variable. So it's safer to use **size_t** for counter variable.


mvvm框架的一个好处就是，你可以更加专注于业务逻辑的思考，而不用花过多的精力在页面逻辑上。经过一阵噼里啪啦的敲打，这个东西终于成型了。
这其中上传文件，为了实现无刷新上传，使用了iframe代替请求。这个方法以前听说过，当把它实现的时候，觉得前人的智慧是无限的。有时有些办法看起来是很猥琐，但确实能解决问题。
由于时间问题，没能添加更过的功能，本来想加一个终端模式的，但考虑到功能的复杂性balabala..
整过过程用了4天时间，还是学到了很多东西，还有很多不足。


Also, I had the same idea about a checkbox. I just need to around to it sometime.


testing


:) still need some work, but probably working for the end of the weeks. Mainly try to get all dependencies into the installation process.


Fair enough :)


TeamCity Ignite :: Ignite Scalar Examples [Build 1621](http://204.14.53.152/viewLog.html?buildId=59880&buildTypeId=Ignite_IgniteScalarExamples&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 37 Build time: 00:03:50


TeamCity Ignite :: Ignite JTA [Build 1697](http://204.14.53.152/viewLog.html?buildId=59882&buildTypeId=Ignite_IgniteJta&guest=1) is now running


Use checkpoint file as new


Let's just use alert with a good message :)


TeamCity Ignite :: Ignite Cache Full API [Build 1185](http://204.14.53.152/viewLog.html?buildId=59866&buildTypeId=Ignite_IgniteCacheFullApi&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 8384, muted: 27 Build time: 00:35:47


TeamCity Ignite :: Ignite Cache [Build 1690](http://204.14.53.152/viewLog.html?buildId=59883&buildTypeId=Ignite_IgniteDataGrid&guest=1) is now running


By the way, there is another nice way to initialize member fields:
```cpp
  Node(int d): data(d), next(nullptr)
  { }
```
The benefit of this approach is that it avoids calling both default + assignment constructors for member fields and does only copy construction. This happens because inside the constructor function the object should be already initialized. And that leads to call of default constructor for each member field. Afterwards assignment happens and assignment operator is called.


I think it is very flexible having the possibility to run every command in the target rootfs. Other then the static qemu executable (copied in the target rootfs) it only requires the binfmt_misc kernel feature, which is present by default on recent major Linux distributions.
But yes, maybe this flexibility is useful only in the current development phase. I will test your suggestion.


Good call. Fixed in next commit.


Revertiste este cambio


This adds your json list as a mod repository, so it can be used to look for
mods.

For example:

    $ mtpm install armor
      # 1. Look up armor in the repos
      # 2. Check minetest-bower first, it's likely to be more accurate than
other sources
      # 3. Download archice
      # 4. Extract
      # 5. Validate, install
      # 6. Go to 1, for any dependencies.

I really need to go through and validate the URLs (ie: test that they lead
to a valid link)


`-DUNICODE` was just in the list of flags that were suggested for compatibility with visual studio. I think they are pretty widely used/defined macros, and swapping `min` for `std::min` should be pretty easy to do.


TeamCity Ignite :: Ignite JTA [Build 1697](http://204.14.53.152/viewLog.html?buildId=59882&buildTypeId=Ignite_IgniteJta&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 7, muted: 2 Build time: 00:03:23


TeamCity Ignite :: Ignite JDBC Driver [Build 1589](http://204.14.53.152/viewLog.html?buildId=59884&buildTypeId=Ignite_IgniteJdbcDriver&guest=1) is now running


Spelling mistake: Should be "prop**a**gation"


I believe this is unnecessary as line 14 gives super_admins access to everything


This can change with ring changes.

A partition where half the k relays know list n and the other half know list n-1 can cause a lot of off by ones.

How does the simulation behave in this edge case


Derp, you're right. This didn't get transposed when the rest of the code did, should be `self.A.append(len(exps)-1, 0, 0)`


@mikeal could you get a regular svg of this?


What do you think about that? https://github.com/Defman21/TabulaRasa/commit/def3389da422be26f806f6efd8522b69951e069d


Okay, that makes sense. I think my confusion is about how to alter `getScene()` to return a `CAScene` only if the entity is in a `CAScene`. However, now that I'm looking in more detail, I see that `BaseComponent.getScene()` is probably what I should be using anyway, and I can probably override that in the `GridSeedComponent`.

I'll give it a shot, thanks for the help.


@hemantkr please review


Great! :-)


TeamCity Ignite :: Ignite JDBC Driver [Build 1589](http://204.14.53.152/viewLog.html?buildId=59884&buildTypeId=Ignite_IgniteJdbcDriver&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 54 Build time: 00:03:54


TeamCity Ignite :: Ignite Java Client [Build 1637](http://204.14.53.152/viewLog.html?buildId=59885&buildTypeId=Ignite_IgniteJavaClient&guest=1) is now running


Better, though you should still handle the user-case of the user not selecting a file (which would exit the function without giving any user feedback).


Works fine for me, I don't know what you screwed up.


timeout seems a little low. We usually do 5 sec.


`dotfiles` FTW!


Yep, fixing.


Note about clamping by worker count. If minPeersBYRelsy is 5 and worked count is 2.


i see. yes. then I'll just need to remove it from admin permission set.


98812452-EMSSensorError-4941 (rglazer2) - x86_64-MacOS-10.9-clang: OK (1789 of 1790 tests passed)

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


in markdown or html5 format?


I believe this broke my app; getting this since today:

```
2015-08-10T20:09:17.663059+00:00 heroku[api]: Release v59 created by uwe@dauernheim.net
2015-08-10T20:09:17.751024+00:00 heroku[web.1]: State changed from crashed to starting
2015-08-10T20:09:21.988394+00:00 heroku[web.1]: Starting process with command `lein with-profile production trampoline run`
2015-08-10T20:09:23.828958+00:00 app[web.1]: Error occurred during initialization of VM
2015-08-10T20:09:23.828963+00:00 app[web.1]: java/lang/ClassNotFoundException: error in opening JAR file .lein/leiningen-2.5.2-standalone.jar
2015-08-10T20:09:23.694530+00:00 app[web.1]: Downloading Leiningen to .lein/leiningen-2.5.2-standalone.jar now...
2015-08-10T20:09:24.563719+00:00 heroku[web.1]: State changed from starting to crashed
2015-08-10T20:09:24.543143+00:00 heroku[web.1]: Process exited with status 1
```


Shouldn't the host be `host: 'localhost'` to match the one defined in `elao_mysql_login_host` ?


Unless by invalidating iterators they mean we can set references to contained data?


In this case I don't think it matters, as we don't do anything with body and all we do with an error is write it to console. So I think it might be better to timeout quicker so we send the next error.


Assuming iterators to ```invokers_``` are never used, I believe the safe and efficient operation is
```c++
   InvokerHashMap::key_type the_key = edm::TypeID(type.typeInfo());
   //avoid holding a write lock on the container by using a const_accessor
   InvokerHashMap::const_accessor c_access;
   if( not invokers_.find(c_access, the_key) ) {
      InvokerHashMap::accessor access;
      access.second = std::make_shared<SingleInvoker>(type, name_, argsBeforeFixups_);

      c_access =access;
      invokers_.insert(c_access, the_key);
      //If insert fails than the just created SingleInvoker will be automatically deleted
   }
   return *(c_access->second);
```


Please update the download method. I would like to use this, but cannot find a barcode


Super-nit: // instead of ///


The latest report claims compatibility with Jasmine 2.0
https://github.com/larrymyers/jasmine-reporters
Would you be able to swap in the new reporter (https://github.com/larrymyers/jasmine-reporters/blob/master/src/junit_reporter.js)?  The arguments to dump the report are still in the code but not functional at the moment.


Hmm... https://github.com/Defman21/TabulaRasa/commit/e7c3d76aa3f64b84f19ccc135104a5991b95e475


Comments!

You don't really need a class or struct here.

And this isn't really a struct - it has non-trivial behavior - and it really has no state at all!


Looks good.
Thank you!


Nit: Any reason we couldn't make this a static var like appVersion instead of a func?


> but the preferred way is the former..

and exactly that way, where you don't format/% yourself (particularly if it's a debug log), it's left to the logging module.


RoomAirflowNetwork (lgu1234) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (748 of 748 tests passed)

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


The thread safety issue isn't the ```accessor``` it is the fact that you modify ```access``` after the insertion which means another thread may hit that exact spot, get a copy of ```access``` before the ```shared_ptr<>``` is set and then return a reference to a null object.


The only option for that would be to return the superclass, as you can't change the return type after compilation. It's just a pitfall of java. What I have done above isn't as clean as what you're suggesting, but it's just as performant I think


I object a bit to the datatypes used here.  `stopPropogation` seems always to be either `None` or `Some(1)`, which is to say that it uses a datatype that holds more than 4 billion possible values in order to represent **two** possible values.  It seems to me that a boolean or a simple ADT (`TopLevel` U `ButtonLevel`) would suffice.  Is there an intended use for this to allow propagation from arbitrarily-deep levels?

On similar grounds, I have a bit of an objection to initializing `blockLevel` below to `-1`.  `-1` is not actually a valid value for that variable.  I feel like the code **using** `blockLevel` should subtract `1`, or, if we want to accept the idea that `blockLevel` **can** have an invalid value at times—a notion that I strongly question, but can be convinced of—that invalid value should be `None`.


+1 I think that's a good idea too.


TeamCity Ignite :: Ignite Java Client [Build 1637](http://204.14.53.152/viewLog.html?buildId=59885&buildTypeId=Ignite_IgniteJavaClient&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 262, muted: 8 Build time: 00:09:37


TeamCity Ignite :: Ignite Hibernate [Build 1586](http://204.14.53.152/viewLog.html?buildId=59886&buildTypeId=Ignite_IgniteHibernate&guest=1) is now running


How do u get on to play


a comment


Same nit comment as above


Nit: Can combine the two if lets into:
```
if let packageType = ..., baseBundleIdentifier = ... {

}
```


`x` should be in double-backticks, right?


When/why did it come to be that these models aren't checked anymore?


@sccolbert! Great to know!

@jdfreder You'll be able to use [`Symbol`](http://blog.keithcirkel.co.uk/metaprogramming-in-es6-symbols/) for the encapsulation in about a month (works in Chrome, Firefox, Edge; coming to Safari next month).


I would double check to make sure count(components) > 0 just in case


You have typo there:
```however, this probject```
should be `project`


Should we add that to the `NSURLRequest` extension?


No need for throws Exception since IAE isn't checked


None of this code has changed, only moved.


The URL and headers need to be binary IIRC.


Also `filing` should be `filling`


val.doubleValue() isn't used


Vírus


Can we use AppInfo.appVersion here?


why not use the official image?


TeamCity Ignite :: Ignite Hibernate [Build 1586](http://204.14.53.152/viewLog.html?buildId=59886&buildTypeId=Ignite_IgniteHibernate&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 35, muted: 2 Build time: 00:04:21


I thought about that but didn't do it for two reasons

1) not sure where else we'll use it
2) Couldn't think of a good method name for it as part of the extension :confused:

If you think I should move it there, I'm happy to :smile:


TeamCity Ignite :: Ignite Hadoop [Build 1627](http://204.14.53.152/viewLog.html?buildId=59887&buildTypeId=Ignite_IgniteHadoop&guest=1) is now running


hello


TeamCity Ignite :: Ignite SPI [Build 1704](http://204.14.53.152/viewLog.html?buildId=59879&buildTypeId=Ignite_IgniteSpi&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1 (1 new), passed: 360, muted: 2 Build time: 00:27:50
### Failed tests
```
org.apache.ignite.testsuites.IgniteSpiTestSuite: org.apache.ignite.spi.discovery.tcp.TcpDiscoverySslSelfTest.testMulticastIpFinder: junit.framework.AssertionFailedError: expected:<2> but was:<1>
	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.Assert.failNotEquals(Assert.java:329)

```


TeamCity Ignite :: Ignite AOP [Build 1789](http://204.14.53.152/viewLog.html?buildId=59888&buildTypeId=Ignite_IgniteAop&guest=1) is now running


That's straight from the old website. You could just take that base64 and convert it to a regular string and send it to a file to get the "regular" SVG :)


So I had some plans of doing almost exactly this, I hate this being a ERB template right now. Also eventually want to close https://github.com/acidprime/r10k/issues/46. The only thing I am not so sure about here is the use of the r10k.yaml to store data that's not "ours", any thoughts on that?


you should not need to set goroot


C++のコードに合わせてnewLine()を削除した。
これに伴って、各メンバ関数の最初にbegin()を実行するようにした。
また、これのためnextToken()で例外を投げるようにした。


The whole line can go, actually!


Changes look good and thorough Qifan. Thank you.


sum elements isn't a function of the entity double matrix. There should be a utility class that handles math on the matrix.


Hmm, for the code you gave you'd need to use a ::accessor (not const) the
whole time or insert access itself.

const_accessors don't appear to allow any write access at all and are
overwritten then you use insert (at least according to the manual).

Otherwise OK, I get what the issue is! Thanks!

On Mon, Aug 10, 2015 at 10:16 PM, Chris Jones <notifications@github.com>
wrote:

> The thread safety issue isn't the accessor it is the fact that you modify
> access after the insertion which means another thread may hit that exact
> spot, get a copy of access before the shared_ptr<> is set and then return
> a reference to a null object.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/lgray/cmssw/commit/794bf67b39b5bd7c72ff35eebfd3f4e81eb43c56#commitcomment-12624231>
> .
>


i would install go from source rather than through alpine that way you can control the go version via ENV variable like we do in the docker/docker Dockerfile and like the offical golang image does

https://github.com/docker-library/golang/blob/master/1.4/Dockerfile


if they use this dockerfile for testing they may not want to remove these thinngs, but i understand for a minimal image why you would


This is a nested comment, the compiler warns about missing declaration of fopen/fprintf due the commented #include <stdio.h>


Nit: This code looks like it's the same as the above FxAClient code. Could we create a helper function that takes in UA and returns a manager to DRY this up a bit?


How about switching to stable branch?
http://github.com/MatthewBooth/OTAUpdates/commits/stable


@djui can you open a support ticket so we can take a look: http://help.heroku.com

In the meantime, you can rollback to 2.5.1 by running:

```
$ heroku buildpacks:set https://github.com/heroku/heroku-buildpack-clojure#previous-version
```


Ugh, really sorry—didn't mean to commit this.


Sleep-based backoff isn't going to work with UDP writes. Should we split the write path here or make this into a queue?


why the i in the parameters ?  If this represents input parameters then it should be consistent for all functions. iVal, iRows, iCols . I don't think that's java convention though


@fabricioflores WAT


I have that in our Travis config file, but it never seems to run the OS X versions. Maybe it is paid only?


Why iRow and not just row


Hey @coreytegeler look this over and test it? We were forcing an install of an outdated version of ABP, so I unbundled. Now ABP isn't included. It's also a recommendation from https://github.com/slambert/Add-Art/issues/47 . Add-Art still doesn't check for ABP (but that's a feature).

Anyway, would you test the compile script and load it up and see if it works for you? If so I will submit to Mozilla.

Thanks!


Moved in 7ffd66c2d0450bf4a8b132c1ae53456108ae5403


Good job mark


Are you committed to transferring this update to the others?


autoboxing handles the equality. doubleValue just clutters the code.


test again


you need to actually do something in them! and you cannot set the attributes because they are final => they can only be set in the constructor.
Still, that is no reason to have 2 extra methods which do nothing. The solution is simple. leave out the 'final' modifier so you can set the attributes in those setters.


TeamCity Ignite :: Ignite AOP [Build 1789](http://204.14.53.152/viewLog.html?buildId=59888&buildTypeId=Ignite_IgniteAop&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 117 Build time: 00:09:25


TeamCity Ignite :: Ignite Basic [Build 1895](http://204.14.53.152/viewLog.html?buildId=59889&buildTypeId=Ignite_IgniteBasic&guest=1) is now running


no two empty lines


@imaus10 Can you provide a post-commit review of this? I could have buried "Frame" and "PersonID" in the template metadata string, but my feeling was that these fields were general enough, and accessed frequently enough to, to warrant breaking `br_universal_template` binary compatibility. My hope is that this is the last time I'll break binary compatibility :)


TeamCity Ignite :: Ignite Hadoop [Build 1627](http://204.14.53.152/viewLog.html?buildId=59887&buildTypeId=Ignite_IgniteHadoop&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 998, muted: 10 Build time: 00:11:29


TeamCity Ignite :: Ignite Cache [Build 1691](http://204.14.53.152/viewLog.html?buildId=59890&buildTypeId=Ignite_IgniteDataGrid&guest=1) is now running


Errrm, aren't you comparing the raw pointer values for < here, instead of the resources?


looks to me like all these properties could use the shorter syntax pubic foo {get; set}


Hi @jzoldak ,
about the data dir etc, I think (at least) I did as the original implementation was meant to be, meaning you can overwrite the url/urls but the rest will be taken from the original config, the reason was that I thought of it as a nice way to just keep a standard configuration. But I see your point, in coming version it would be cool to override whatever you want, I'll add an issue for that tomorrow.

About the headerFile: If you run from the cli you can use the file, if you use the objects you pass the headers as an object, the same way as for example with the urls. If I remember correctly, haven't checked the code :)

Best
Peter


Make that ```result == 0``` a ```!result``` (below too)


It seems like all, right?


`${provider_root}` instead of path?


Agree


Capitalize the first letter of the first word after the "AURORA: " in the commit message


i used the format of the other files, but i could change them too ?


I mean javascript file :P


good catch


The Eclipse block should be further up, below the CMake block. And add a newline between the blocks


Correct. Updated now.


@173210 Just a proposal: maybe you better squash commits before making PR? I'm losing tracks what happened whithin the day :) I'm also sometimes pushing frequently but that's only because doing that with only GitWeb available


Avoid printing exceptions like that. Use logger in the case that you wanna print it.


Use DISTS instead of GIT for the .gitignore. And capitalize the "Ignore".


I'm a newbie ^^


By the way, I don't understand this line:

```javascript
return (/\.scss$/.test(m.name) && m.name.slice(-2) === 'ss' && m.reasons[0].moduleName.slice(-2) === 'ss');
```

It has to end with .scss AND it has to end with 'ss' AND its reason moduleName has to end with 'ss'.
Am I the only one who thinks this is nonsense and that these ANDs should have been ORs?

for example, for `./src/views/Widgets.scss` the reasons will be
```
[ { moduleId: 460,
    moduleIdentifier: 'G:\\work\\react-redux-universal-hot-example\\node_modules\\react-hot-loader\\index.js!G:\\wor
eact-redux-universal-hot-example\\node_modules\\babel-loader\\index.js?stage=0&optional=runtime&plugins=typecheck!G:
rk\\react-redux-universal-hot-example\\src\\views\\Widgets.js',
    module: './src/views/Widgets.js',
    moduleName: './src/views/Widgets.js',
    type: 'cjs require',
    userRequest: './Widgets.scss',
    loc: '33:13-38' } ]
```


To do: Rewrite this test and model it after `pyi_stderr_encoding.py`: Compare interpreter value with frozen value, and "normalize" codec name using `codecs.lookup`


Thanks @stevenjack.  I just started using your tool and this .rb file was created by another engineer, however, here is the `FnNot` call:

`Condition :UseLoadbalancer, FnNot([FnEquals(Ref('loadBalancer'), '')])`

Please let me know if you need anymore information


That's the inverse of "not giving feedback", change line 165 to `return;`.


It is not clear to me what happens here... when you press reply we send to andriod the json, but it will only contain "sent from nuntius", no?

I know we are not able to show a inline entry for now... but I do not think we should allow to send broken sms. We should pop up the main UI, allow to reply there and then send the sms.
This can be a follow up patch, but right now I would separate a "reply" method that sends the json and not add the reply buttton to the notification


Done


no empty lines


ahh okay, sorry I didn't read your message properly :P


This will need https://github.com/ocaml/ocaml-travisci-skeleton/pull/61 I guess.


Is there a way to start containers that have been previously stopped?


new ivan build or what source?


space after if


:godmode:


TeamCity Xbim :: Xbim Geometry :: XbimGeometry [Build 13](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=36&buildTypeId=Xbim_XbimGeometry_XbimGeometry) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 03:07:00


develop (Myoldmopar) - i386-Windows-7-VisualStudio-12: OK (1272 of 1272 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)


One thing to note is that variables can point to objects, which are mutable. Only primitive types can't be mutated.


develop (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1269 of 1269 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)


We discussed this before... I do not want another separate window. Since we have to bring up a window, lets bring up the main window


PlantOperationSchemes (kbenne) - Win64-Windows-7-VisualStudio-12: Build Failed

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


debug leftover


This should apply the boundary checking filter first, then the `filter` parameter so the filter has no knowledge of tile entities outside the range.


it allow me to test for now. i think we cna work on the UI next ?


This is not a mixin do this won't work


ok, i will merge your commit, if you leave changes only in Odnoklassniki.m


the name is confusing, it should be "connections" or "connection_table"


Good point. I just left it here for the current time as it is used by this only instance of the IMatrix<Double>.


what about %r{} syntax? It's much more readable on my eyes.
`%r{^POST /gateways/([^/]+)/orders$}`
but it's related more with the personal taste :)


Yes that looks better, although the indexOf looks crafty and error prone. It would be better to just check if path is null and then just return. This doesn't need to be part of the try/catch.


I thought on sharing the settings with GTK statusicon plugin.
But i'm not sure it is ok to have two different sets of defaults for the same section (statusicon). Just thought it would be better to avoid possible collisions or saving/deleting issues.

I see no segfault here, on KDE.

And I get two quit actions in the context menu if I add it manually.
I tried getting back the context menu, removing a couple of last actions from the list, clearing the menu, and adding the cut list of actions back to menu. No result, auto Quit was still there.


double instead of Double to allow users to pass the primitive type without incurring a performance cost. This would work for both Double and double due to autboxing.


This is just for clarifying that this is an iterator kind of variable used in the for loop. Just for clarity.


when scrollView.contentSize.height > scrollView.frame.size.height+Cell Height, the layout crashes
I added a line to check it.

Hope this can help!


fix some minor md formatting issues before we'll merge this in.


you could make this a hyperlink


better make it a parameter...


oi @ivobarcelos , tem algum motivo para você concatenar a query desse jeito? Fica um pouco complicado para outros programadores lerem.


thanks to https://gist.github.com/simonz05/1160477


Actually it is questionable if the compression of the png changes the filesize of the compiled exe...
I have actually no idea how img resources are included into the build but I would guess its either transfered to bmp just because it's easy to read/show or compressed into its own container. In both cases the input compression wouldn't matter.


no space after (


leave this empty line


no empty line


Pupil Cam!?!!!


A mensagem está aparecendo quando você faz o redirect?


@mlyle I left the expo3 in as it looked as though it was used for a couple of other things.


why? var is ok


Unfortunately it doesn't. This is a reference to an object, so you'll need to use Double.Equals which is highly recommended to be used in equals(Object) overriding.


Return double to avoid the explicit boxing


wtf? D:

On Mon, Aug 10, 2015 at 11:22 PM, Allan Victor <notifications@github.com>
wrote:

> Vírus
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/taypi/taypi.github.io/commit/f3c68a0ff3f7fc658873a35d046d692b481f870e#commitcomment-12624333>
> .
>


Ideally this should be split in two commits: one that adds the actions and a second one for SMS


Yes, I know that but I don't know why I didn't change it.. Anyways, thanks!


O FacesContext é um objeto que você possivelmente vai usar no sistema inteiro. Pode ser interessante que você isole ele numa outra classe e crie um produtor do CDI. A mesma coisa vale para a criação de novas mensagens, ter um método que já cria a mensagem com alguma severidade é muito útil


It DRYs up your code, which is a good thing. Without switching to a JS framework, I'm not sure there's a much better way to do this.


voce acha nego véi?

acho que assim fica ate legivel não?

bro mas tem como voce ver o problema que relatei lá no trello?

eu injeto um EntityManagerFactory mas ele vem nulo, eu fiz igual esta na
apostila e o Gama, tambem
falou desta forma no curso de JSF

att.

Ivo

Em 10 de agosto de 2015 17:43, Alberto Luiz Souza <notifications@github.com>
escreveu:

> oi @ivobarcelos <https://github.com/ivobarcelos> , tem algum motivo para
> você concatenar a query desse jeito? Fica um pouco complicado para outros
> programadores lerem.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ivobarcelos/Jornada-Submissao-Palestras/commit/f0ddf92384ca32e191250d61affb339af2e752c3#commitcomment-12624817>
> .
>


This is removed now as Exception is removed. But using a logger is the way to go indeed. Specially we can't assume that the caller has the Console privilege.


JC, how did you manage to do this? The only reason I added this line separator is because I was not able to commit a line longer than 80 characters due to the git commit hooks.


I can confirm that the fix works on Mac OS 10.10.4, Chrome version 44.0.2403.130. Now I sometimes see/hear a split second of autoplay but nothing more.

Many thanks!


TeamCity Ignite :: Ignite Cache [Build 1690](http://204.14.53.152/viewLog.html?buildId=59883&buildTypeId=Ignite_IgniteDataGrid&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1 (1 new), passed: 513, muted: 77 Build time: 00:45:52
### Failed tests
```
org.apache.ignite.testsuites.IgniteCacheTestSuite: org.apache.ignite.cache.affinity.fair.IgniteFairAffinityDynamicCacheSelfTest.testStartStopCache: java.util.concurrent.TimeoutException: Test has been timed out [test=testStartStopCache, timeout=300000]
	at org.apache.ignite.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1596)
	at junit.framework.TestCase.runBare(TestCase.java:141)

```


TeamCity Ignite :: Ignite Cache 2 [Build 259](http://204.14.53.152/viewLog.html?buildId=59891&buildTypeId=Ignite_IgniteCache2&guest=1) is now running


$headers = array()


That is great! I was getting tired of giving my money to Logitech and Microsoft... :p


Hi,

doch, es geht noch. Es erscheinen nur keine gepeerten Kanäle mehr in der Drop-Down-Box. Man kann aber in der Kommandozeile sehr wohl noch doppelt peeren.

Man kann sogar in der Kommandozeile das eingeben:

            "set HMW_LC_Bl1_DR_MEQ0078948_01 peer muell"

Das geht ohne Fehlermeldung durch. Im Device steht dann

            " peer_act_0   channel_01 → unknown"

Irgendwas wird auch ans Device geschickt. Das Peering kann man dann nicht mehr löschen.

Also drei Probleme:

1. Man kann schon gepeerte Kanäle nochmal peeren.

2. Man kann totalen Müll peeren.

3. Man kann Müll-Peerings nicht mehr löschen.

Gruß,

   Thorsten

From: hresalg [mailto:notifications@github.com]
Sent: Montag, 10. August 2015 18:29
To: kc-GitHub/FHEM-HM485
Subject: Re: [FHEM-HM485] mehrmaliges peeren nicht mehr möglich (9216374)

Nun sollte das peeren mehrer gleicher Kanäle nicht mehr möglich sein.

—
Reply to this email directly or view it on GitHub <https://github.com/kc-GitHub/FHEM-HM485/commit/9216374fa88056a31b87b0848eac096d2fbeee8d#commitcomment-12619351> .  <https://github.com/notifications/beacon/AHN0jaQQxHs1OGycQ8rBlH1kSexrWUjqks5omMi3gaJpZM4Fo08D.gif>


if (!empty($headers)) {


Wilco! I do love a good comment

On Mon, Aug 10, 2015 at 2:13 PM, gittheking <notifications@github.com>
wrote:

> Good stuff Ed, very well done. Only thing I would add is to get into the
> habit of adding comments to your code especially in the getInput() and
> playToFive method where you invoke the getInput(). This will help others to
> decipher your code when you work on a team of a bunch of engineers all
> manipulating the same codebase. Great work and keep crushing it!
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/edpetner/wdi-fundamentals-rps/commit/f7cc324bb6b79245f5daa717ae5d021dc87c3854#commitcomment-12621698>
> .
>


@KevinZinsmeister @andyeck1 ,

I moved your file from here

Structural/Struct_Xcel_Sports Complex_8_6_2015.rvt

 to here:

Models/Proposal 2/Struct_Xcel_Sports Complex.rvt

In the future, please keep this file here.  Please do not change file name with date.  With revision control, we do not need to add any versioning information anymore.

Thanks, Ryan


develop (axelstudios) - x86_64-MacOS-10.9-clang: Tests Failed

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


This should be protected.


I think, the creation of /dev/rfkill should be done by udev (or systemd-udev), so IMO we should raise exception if /dev/rfkill does not exist. So, on my system (Slackware64-14.1) I have:
```
$ grep rfkill /{etc,lib}/udev/rules.d/*.rules
/lib/udev/rules.d/40-slackware.rules:# Set rfkill device writable by netdev group
/lib/udev/rules.d/40-slackware.rules:KERNEL=="rfkill", GROUP:="netdev", MODE:="0664"
/lib/udev/rules.d/50-udev-default.rules:KERNEL=="rfkill", MODE="0644"
/lib/udev/rules.d/95-keymap.rules:ENV{DMI_VENDOR}=="Hewlett-Packard", ATTR{[dmi/id]product_name}=="HP ProBook*", RUN+="keymap $name 0xF8 rfkill"
```


is this a mistake?


Em relação a concatenação, em geral, ela sempre torna o código mais complicado para os outros programadores. Lembre que você escreve código para os outros entenderem :). Pode me adicionar no trello? o usuário é alotsssa.


Almost there, you don't need to be so explicit with your path check. Just use `if (!path)`.

Try to read and comprehend the code that you are writing and think of possible edge cases.


FYI, this should change to fuchsia.googlesource.com soon (like this week)


Thanks for talk and slides (and taking the effort to put this on the pages yourself ;-))!


my script was working fine until it stopped last week and keept saying this..Error: Forwarded declaration doesn't match at line 488
Compiling failed.

i understand i have to put in what u typed in here in my script but i dont know where. could you please help me out?


It's important to note that Elfzenon on RR gaming does not care.


Hey @narangrishab. Where are you trying to locate this and why?


Done.


note that this and the parent commit 88d55cb were apparently never pushed to the master branch?


Useless commit :D I had a rebase conflict :'D


it says: override


The keys will always be converted to strings, you can technically pass 'anything' as the key, and internally it will have toString() called onto it. One example of this was the underscore test we looked at for pluck:

https://github.com/jashkenas/underscore/blob/master/test/collections.js#L504


I've made the changes.


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


why didn't you add a newline


Hooks can be disabled by renaming the file `.git/hooks/pre-commit`

Two options moving forward:
* document the "trick"
or
* improve the hook so that (length) checks could be disabled if the message include a given instruction.


Lembre de não produzir o EntityManagerFactory o tempo inteiro? O processamento dele é um pouco mais pesado. Produza ele em outra classe, ApplicationScoped, e o receba injetado na sua EntityManagerProducer.


this carriage return isn't good enough


User can pick not a json file...


That's what the try/catch is for. Not a JSON file would still not equal false/null/undefined.


True. Done.


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


A better option would be to do the following:

```
set(_tmp "DCMDICTHOME=<APPLAUNCHER_DIR>/${Slicer_SHARE_DIR}/dicom.dic")
set(_tmp "${_tmp}<PATHSEP><APPLAUNCHER_DIR>/${Slicer_SHARE_DIR}/private.dic")
set(${proj}_ENVVARS_LAUNCHER_INSTALLED ${_tmp})
```


hmm, you probably need different `#define` for i686


This looks weird? `wibox.wibox` really?


Actually, this might be related to the S3 outage today. So a redeploy might fix it. Regardless, please file a ticket so we can help. Thanks!


TeamCity Ignite :: Ignite Basic [Build 1895](http://204.14.53.152/viewLog.html?buildId=59889&buildTypeId=Ignite_IgniteBasic&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 831, muted: 6 Build time: 00:24:48


TeamCity Ignite :: Ignite Cache 3 [Build 258](http://204.14.53.152/viewLog.html?buildId=59892&buildTypeId=Ignite_IgniteCache3&guest=1) is now running


The returned function will be called with a $scope's context, thus the $on method will be defined, tested and fully working


Not as much as the others :-)


*Edit*: makes sense after seeing https://github.com/psychon/awesome/commit/8c34a88e6a59f4689dbbbedf19bf3019cb3fe7a4.


not sure why nacho used the longer version... maybe because of "construct"?
anyway, you can leave this for now

On Mon, Aug 10, 2015 at 10:35 PM, Ronan Nello <notifications@github.com>
wrote:

> i used the format of the other files, but i could change them too ?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/flyingrub/nuntius-linux/commit/57e3f7089d9e65b8d442d41c4aede45cc1e888bc#commitcomment-12624642>
> .
>


также можно юзать `PRAGMA table_info()`


Try to get this test to run without it being in an ucla environment.


I'm not sure, but judging by the format, it was seems it was a *long* time ago - there isn't a `procedures` object or even `tortoise_requires`. The last update to Termites was made on May 6, 2014, so it seems likely they have been unchecked for at least a year.


```js
$scope.$meteorObject = $meteorStopper($meteorObject);
var meteorObject = $scope.$meteorObject();
```

Notice the way we called the generated function


Должен рейзить RecordNotFound exception


TeamCity Ignite :: Ignite Queries [Build 1665](http://204.14.53.152/viewLog.html?buildId=59881&buildTypeId=Ignite_IgniteQueries&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 709, muted: 11 Build time: 01:00:48


`path does not exist: /my_super_path` error?


TeamCity Ignite :: Ignite Cache 4 [Build 257](http://204.14.53.152/viewLog.html?buildId=59893&buildTypeId=Ignite_IgniteCache3_2&guest=1) is now running


Markdown

> On Aug 10, 2015, at 3:10 PM, Ming Tang <notifications@github.com> wrote:
>
> in markdown or html5 format?
>
> —
> Reply to this email directly or view it on GitHub.
>


Is the "hack" here that no context is available to pass in?


Please add the boilerplate


Nope. Typo.


please add the boilerplate


I'd forgotten about this `Parameterized.Parameters` capability since I'd last seen it. It does come in quite handy for this sort of repeat testing with different data sets.


Opened a ticket, thanks for the advice. https://help.heroku.com/tickets/261251