I considered this, but I would consider it less safe to return the list of functions.

Here are my thoughts
- Enforcing an initialisation function is easy because if it doesn't exist then nothing's been created (except possibly statics, which can be disposed of on destruction)
- There is no point in enforcing a termination because there's nothing to do if it doesn't exist - At this point there is no exception handling in tlli.
- Even though the functional nature of the language might not like it, an extension might require state setup and destruction, therefore I prefer to have matched init/terminate so the extension has the ability to clean up after itself, however that may be (close file handles, send server disconnect messages, whatever)
- tlli currently doesn't support removal of functions. It certainly should do, as, like you said, it would be bad for an extension to add a bunch of functions, then for the extension to be unloaded and the functions to be gone.

Unfortunately, I'm not sure there's really a sensible way to bullet proof this at this stage. I cannot just 'watch' what functions are added, because not all of them may be added by the extension, some may well be valid after unloading the extension, the extension might add other values such as lists - should these be removed? Keeping a 'rollback list' for each extension seems quite heavy handed. Maybe I might be able to add it into debug builds that it somehow generates a list, which it checks against when unloading the extension, but I would prefer to keep something like that from release builds as it seems cumbersome. I'd much rather rely on extensions to clean up after themselves properly.

General usage would not really unload extensions in the middle of execution anyway.


Sure


Can you change to ^3.0?


Actually that should be in BufferLevelRule no BufferContorller.  This will limit the forward buffer to just one segement.


J'ai oublié de l'enlever, elle ne sert plus à rien en fait


@ednawig Why not simply remove the function?


Ne vous prenez pas trop la tête avec AJAX, si ça fonctionne sans, c'est suffisant à mon goût.


Than I must be calling cmake bootstrap wrong.

> -DBUILD_DIR=/home/hudo/dev/kodiws/kodi/project/cmake/addons/build/bootstrap

should be
> -DBUILD_DIR=/home/hudo/dev/kodiws/kodi/project/cmake/addons/build

For reference, this is what I normally use:

> cmake /home/hudo/dev/kodiws/kodi/project/cmake/addons/bootstrap -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/home/hudo/dev/kodiws/kodi/project/cmake/addons/addons -DBUILD_DIR=/home/hudo/dev/kodiws/kodi/project/cmake/addons/build/bootstrap


It kinda works but it bypasses gradle and uses IDEA build system, which does not launch code gen tasks and (at least for me) produces some mystical errors at run time oftentimes.


to Improve


@rschmukler this might have re-introduced #6023 and #6030.


Thanks Michael for this update! I came home to a nice surprise waiting for me


complete


109626134-VariousDocumentationIssues (mjwitte) - x86_64-MacOS-10.9-clang: OK (1971 of 1972 tests passed)

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


THX, my shaky cold fingers in the outside testingfields all thank you :) A nice Christmas surprise fix :+1:


I've opened a Cargo project in WebStorm just fine but it is indeed a source of potential strange failures.


Thank you! The reason I removed brew instructions from the docs is that I was unsure if the brew formula would be kept up to date.

Is it possible for me to update the formula if you're busy? What are the steps I would need to do? Is this the file that someone has to update? https://github.com/Homebrew/homebrew/blob/f211aba712bf43e7772514001f422f51ce2958f0/Library/Formula/postgrest.rb


@vihu

![battleship_pos](https://cloud.githubusercontent.com/assets/10503083/11640170/f4cd3614-9d0f-11e5-91a1-c467850726c3.png)


Well I don't know how it should be on Linux so @wsnipex might be able to help you out but on win32 all the scripts are setup to not pollute the existing directories and to write all the generated files into `project/cmake/addons/build/`. You can choose whatever you want for `BUILD_DIR` but I would recommend choosing a directory that is already gitignored ;-)


This commit can be reverted. The AJAX request issue has been fixed.

```bash
git reset 48a7529 --hard
git push -f
```


This page of the documentation needs to be updated to reflect this change:

http://ag-grid.com/javascript-grid-properties/index.php


Mike Champion started this document and this version is all his.  I simply copied Mike's document into a W3C repo so work can continue here.  Mike's last update in his repo was 2015-11-25.


This indeed lacks the proposed forward pointers to other subsections. My feeling is that for these to be effective, we first need to remove even more unrelated content from the subsecs, and also break them up into smaller, more directly referencable parts (if that makes sense).


Thanks! I didn't notice until after you pointed this out that I had unnecessary renders on the index and show views.


@robske110
Thats not true. I left a note that its a third party build and that
> PocketMine is free software
It would be illegal if i remove that line also and write something like:
> This Serversoftware is made by ImagicalCorp and not PocketMine


TeamCity LabKey :: Trunk :: Premium :: Git sqlserver 2014 [Build 90](https://teamcity.labkey.org/viewLog.html?buildId=290048&buildTypeId=LabkeyTrunk_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:06:09


We could. You put it there, so I assumed you needed it there...

Edna

-------- Original message --------
From: Chris McCafferty <notifications@github.com>
Date: 12/07/2015  23:21  (GMT+02:00)
To: theias/ldap <ldap@noreply.github.com>
Cc: ednawig <edna@ias.edu>
Subject: Re: [ldap] Renamed delete() method as it caused an infinite recursion
  by calling itself... (575158e)

@ednawig Why not simply remove the function?

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


Yes, I figured that out by trying.  You're right; I'll make a note of asking the resource manager team for that to be documented.


oops


Documentation is absent. Also there are no simple examples of use of library. It is not clearly what is it and how to use it.


cool. openblas is available from conda.


This update from Stephen Hilt adds:
- A Guardian ATG (automatic tank gauge) information gathering plugin: atg-info.nse
- A CSPv4 scanner for certain Allen-Bradley PLCs which do not support Ethernet/IP protocol: cspv4-info.nse
- A DNP3 scanner which identifies live controllers and displays readable information: dnp3-info.nse


this line is not necessary any more?


@DougGregor, do you mind reviewing this commit?  I approved this pull request to fix the build but it also needs a proper review.


Is there a way we could combine this with the un-parameterized getChannels above? Maybe call getChannels[Any] or something?


lol


complete


unless `path.to_s.downcase.include?`


sorry if i didn't mention it, but this already exists in `NSArray+WMFMapWithoutNil`. can you pick one?


:-/ I guess I would have waited to commit them all together.


`%w(.xib .storyboard)`


Oh I see how it works now. I would just send a PR like you did. How did you calculate the sha256? At first I thought it was a commit in the postgrest git history but I can't find it in the commit log.


`[error] AI : StringTable.cpp @ 120: Duplicate string ID found: 'SD_TROOP_DROP_DESC'`


AppDomain.CurrentDomain.BaseDirectory, which is Program.Location, is returned with a separator included, how come it's missing? I use "AppDomain.CurrentDomain.BaseDirectory" in a few other projects, this was never an issue.


Yeah, that's the file that needs updated. Anybody can do it.

This was the first package I ever created, so I wasn't sure how keeping it up to date worked either. I just followed the instructions for submitting a version upgrade here: https://github.com/Homebrew/homebrew/blob/master/CONTRIBUTING.md


It is since the package name is still the same when running tests.


Fixes #41


Fix for issue #20


fixed #9


Fair enough.


No JavaDoc?


I think it should be plural: 'electronics designs'


TeamCity MonoGame :: Develop (Win) [Build 3.5.0.907](http://teamcity.monogame.net/viewLog.html?buildId=12013&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 552, ignored: 6 Build time: 00:21:00


After updating the url, I just ran `brew fetch postgrest --build-from-source`, which gave me the new sha256


I don't think I used it in my tests, but I figured I would add it just for completeness for any external users.  Since the project number is randomly generated in `create`, I figured it'd be nice to expose this method.  Without this method, a user would have to call `getProject`, change the project number, call `removeProject` (because `addProject` won't overwrite an existing project at the moment), and then call `addProject`.


Good catch!


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


It's because `get_exercise_cache` was replaced with `get_topic_nodes` in develop...


Leaving it in was a mistake - it was an override of the library method that added logging. If we still need logging, and I think we do, we can leave it in with call to the parent method then write the log.


Why import it inside the function?


@edolstra In addition to my previous comment, this also breaks when `-K` is used:

```
error: while setting up the build environment: can't map '/private/tmp/nix-build-file-embed-0.0.9.drv-0' to '/private/tmp/nix-build-file-embed-0.0.9.drv-2': mismatched impure paths not supported on darwin: Bad file descriptor
```


Does anyone know why this file needs to be included for **some** classes serverside (CLuaAccountDefs e.g.) for "CLuaDefs" (in line 15) to resolve?


Agree, fixed it in cd767bce8066b526c34d978f429352e3ec71cceb


Agreed, specificity about the particular UI is helpful.


try to avoid tabs


@Kotshi Hi, you probably shouldn't have a binary on git/gihub :laughing:
I guess you already know ;)


@traxxas

Hi Brandon,

I am an employee at Traxxas.  Traxxas is in the process of becoming more active in the open source community.  We would like to create a GitHub organization using the name "traxxas". Would you be willing to change your GitHub.com user name and allow Traxxas to take ownership of github.com/traxxas?

Feel free to contact me @ tkawamura@traxxas.com

Thank you,


Thanks, by the way. I believe this also breaks with soft wrapping too which is a pain.


Nice


Also #76 — They describe the same problem.


Is `it` defined?  (Same for other changes in this commit)


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


use `find` here instead of `filter...[0]`


109626134-VariousDocumentationIssues (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1442 of 1442 tests passed)

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


The postfix `_` is mainly for the common case where I want a parameter or local variable of the same name, e.g. for a setter method like `void set_foo(const Bar& foo) { foo_ = foo; }`. (It also has to be a postfix instead of prefix as that is reserved for the compiler and system libraries.) Personally I prefer using `m_` and `s_` for (static) members, but I saw postfix `_` at some place in RT and hoped to be as consistent as possible.


``LUA_DECLARE`` f.e. is defined in *CLuaDefs.h*


This caused a script of ours to start failing while importing novaclient:

```
Traceback (most recent call last):
  File "[our script]", line 10, in <module>
    import novaclient.client
  File "/data/app/kochiku-worker/.local/lib/python2.7/site-packages/novaclient/client.py", line 38, in <module>
    from oslo_utils import netutils
  File "/data/app/kochiku-worker/.local/lib/python2.7/site-packages/oslo_utils/netutils.py", line 25, in <module>
    import netifaces
ImportError: No module named netifaces
```

It was easy to work around with `pip install netifaces`, but I expect that a lot of users will run into this.

This could be "fixed" with lazy imports, so that netifaces is really only needed in exceptional paths, but IMHO it still seems really bad to fail if netifaces isn't present, even if it's in exceptional paths only (because the error will be misleading). I think making everyone install netifaces is the lesser evil.


![screen shot 2015-12-07 at 1 38 22 pm](https://cloud.githubusercontent.com/assets/360927/11640584/236be2cc-9ce8-11e5-8ae8-fb96d3b490c1.png)


`torndo` should be `tornado`, of course :)


David,
I think this is an unrelated problem, perhaps it has something to do with the selected architecture or missing (automatic) restore og packages.


> Setting the article title afterwards is unsupported.

Then it should be passed in an initializer or a class factory method (if this is builds its UI w/ a storyboard)


rename with .js


I guess it has something to do with ScriptHookVDotNet. Just checked it, and it doesn't include a separator in any shvdn script.


Magnificent!


There is more like this throughout the server but it's good to take it one step at a time.


Is there some reserved words registry defined?


Yep, it looks like a typo. I've understood very soon that testing controllers this way is pointless. The more concise way is to assert that response is matched against certain schema. Currently I write:

* specs for serializers itself. These specs tests the decorator behavior and matching agains json schema - serialization
* controller specs. These specs makes assertion about response code and body is matching json schema.

I encourage you not to waste your time


it says "Merge pull request #3 from billyodonnell/google_maps_fix"
but I (foxtrv) am the one who implemented this whole update/branch


I need a way to fix the Icon. My `install.py` allows users to install the package to an arbitrary location, so I want to fill the Icon property using that [information](https://github.com/hashhar/vscode/blob/hashhar-desktop/resources/linux/install.py#L21) but I don't how to do that.


This seems like it would be equivalent to setting `sidekiq_options unique: true` in every worker class. Is there a way to turn on uniqueness for a single ActiveJob class?


Tenhle if stačí jednou v každém while


if you add semicolon after this (and the `@weakify` below) uncrustify will work normally


Changed shop link to https://shop.350ppm.co/


Missing the leading C in Copyright?


Indeed, but it is also declared in *CLuaFunctionDefs.h*. The `LUA_DECLARE` in this file refers to that one, allowing *CLuaDefs.h* to be "excluded". Certain classes server side run into trouble when you don't include CLuaDefs.h, but it works fine here..


yes.. Didn't see that one (Well it's also in the comments so.. No compiler warnings for that one)


tady před to dáš ten if


Ok, great ,lets do that where necessary, although as discussed, we should really try and fix any issues we find as opposed to simply adding pending tests.


Use only with ECMonv1.java


I still feel like there should be a better way of doing this in the containers... I digress though... this is fine


Could we spell out "options" instead? But probably if the method is ```restoreSettings```, the parameter wants to be ```settings```.


`tlliMalloc`/`tlliFree` are internal functions to the tlli library. Technically speaking the repl, even though it currently resides in the same source directory, is not part of the library but rather an example of possible use for the library, which is why it didn't use the internal `tlliMalloc`/`tlliFree` functions. I can, however, see that it might sense to give the repl access to at least some of the functionality.


Nice, been hoping for this.

Something I'd like to do when I get back to a clean tree is move the generated control code to it's own file, and just include it in `rsedu_control.c`


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


Cool I'll put the brew docs back into the project. I appreciate you learning how brew works in order to help the project.


What is all about those input and output names with underscores? I've seen similar replacement but the other way round in one of the previous commits.


It broke our builds too. I agree with dlubarov here. I'd like to see netifaces back in requirements.txt.


`facepalm`


Good catch, I missed that. Awesome fact about `%q` - I was weirdly thinking they'd be outside of quotes. I'm just having a slow day.

Either way probably useful to double check we have tests to make sure we're escaping properly.


We have pretty new automated process of building Galaxy's Python wheels on OSX using https://github.com/galaxyproject/starforge that might possibly be used to improve the conda build situation. Ping @natefoo who knows the most.


This has already been slightly discussed in the general comments of this PR.

My first attempt was to pull in `javax.inject:inject:1` and `java.inject:inject:1:sources` as dependencies and create a `javax/inject/Inject.gwt.xml` file which would then be inherited by `Dagger.gwt.xml`. So thats similar to your b) or c(2) approach but just within dagger itself.

However this caused a Java compiler warning about implicit compilation while trying the dagger-gwt artifact in one of my sample projects. The reasons for that warning are:
- `javax.inject:inject:1` artifact has class files that have older timestamps than the source files in `javax.inject:inject:1:sources`
- build tools have a tendency to create incorrect class / source paths

When the build tool does not create correct class/source paths (in my example case it was a nowadays old Gradle 2.1 or so) then the Java compiler will see a newer source file for an existing class file (in this case it was Provider.java) and the compiler will then compile the source file implicitly (along with a warning) and places the class file in the compile output.

To avoid that warning I unpacked the `javax.inject:inject:1:sources` artifact and embedded the source files as `super-source` as part of dagger, just like GIN does.

According to @tbroyer this behavior of build tools have been fixed in some cases, but to be on the safe side I would stay with the current approach.

I would prefer having a `javax.inject:inject-gwt` artifact (official or unofficial) that contains the source + GWT module but again if we then want to be on the safe side this artifact should make sure that source file timestamps are older than the class timestamps of the official class files. Otherwise some build tools might emit warnings as mentioned above.


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


Nice work, but you really ought to merge with master to please Travis.

Also, remember that I won't be at the meeting tomorrow.  It's all you and Cosmin!


Zhuowei, rideAnimal(); is crashing, could you fix it please.
Thanks! ;)


The GUI currently lists 3.0 as beta access. Is that changing?


FYI this became apple/swift@e437a0e14ccbc47e50223469f828f9ea583f5936


you'll find the => will


le build


Why that?


Ich habe die Labels hinzugefügt


TeamCity LabKey :: LabkeyRelease15.3 :: CDS postgres 9.4 [Build 99](https://teamcity.labkey.org/viewLog.html?buildId=290019&buildTypeId=LabkeyRelease153_CdsPostgres94) outcome was **FAILURE**
Summary: Tests failed: 13 (1 new), passed: 35 Build time: 01:12:42
### Failed tests
```
org.labkey.test.tests.CDSVisualizationTest.verifyAntigenScatterPlot: <no details avaliable>

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

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

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

org.labkey.test.tests.CDSVisualizationTest.verifyGutterPlotBrushing: <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.CDSTest.verifyCounts: <no details avaliable>

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

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

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

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


i usually do the "initial" KVO observation option instead of calling it myself after observing. this allows you to keep all the update logic in 1 place while also ensuring the object has the latest state after observing.


tas cebao


@bry4n and @glynnis This commit is an updated commit and the most recent CSS. It allows the calendar to include a bit of padding at the bottom. Variables have also been updated. Side paddings weren't working out too well, so I say we just go with how this is.

<img width="321" alt="screen shot 2015-12-07 at 3 38 17 pm" src="https://cloud.githubusercontent.com/assets/14296817/11640792/1b564674-9cfa-11e5-8a79-67bbf657b13a.png">


I didn't realise that this code was public and I don't really care. It's here because I had to work on it with friends during 2 days...


Why not putting binary on git/github? Or Why did I have to come and bother you with this? :smile:

Because git (and more specifically github) is about code, and binaries aren't useful here, as you won't be able to run them on all systems, and you'll have to compile them anyway.

Just add them to a `.gitignore` files to ignore them on git.
:D


saw approval from macintux
at https://github.com/basho/riak_kv/commit/1b0b3eda43b7c19b28bebb7f50927d0d44fe7018


merging basho/riak_kv/at/primaries_only_in_coverage = 1b0b3eda into borshop-integration-1294-at/primaries_only_in_coverage


Just saw the function comment: "Wrapper for ::delete that handles logging.". Indeed.


basho/riak_kv/at/primaries_only_in_coverage = 1b0b3eda merged ok, testing candidate = d6d61f41


I think for now its probably better to leave the images in for now and come back to it later if we decide we need better, more descriptive ones.  I get the sense if customers use the getting started page they are a bit of a lost sheep that needs some encouragement that they're on the right track.


I've noticed that when using `transitionEnterTimeout/transitionLeaveTimeout` in other projects I get flickering also - not isolated to this impelementation


I know, I'm just being probably a dick to point that out. Just wanting to let you know I looked your code, not bad
:D


I agree that these things should be enums, but I will change this in a later change as it is irrelevant to the extension work


I like deleteUser, let's go with it.


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


I will rename to tlliExtRAIIFn. It was initially called tlliExtInitFn but I then chose the more general name as the same type was also used for the terminate function.


All peoples concerned by this code add the same system at this time.
Thanks for the compliment ;)


The idea is to make the user's white balance choice affecting DNG.
An appropriate "neutral" matrix is required for each white balance choice.
Currently I just tested a pair of neutral matrixes to be sure the corresponding DNGs were affected by the choice...


this should be declared in the method to reduce accessibility. it shouldn't be possible to access (or mutate!) the global variable used to store the singleton.


You have a backup file `driver.go~`.  Can you remove that?  Otherwise it LGTM.


create database on the server before use
get the package before build
go get github.com/go-sql-driver/mysql
go get github.com/go-xorm/xorm
go get github.com/labstack/echo


They recommend that version always be on maximum, because upgrading CMake doesn't cost anything. If you need package which requires version 3.4 then just install it, and all will be fine.


Thanks. There is still a bit of rough transition at the low end, but maybe nothing we can do about it (too much difference in brightness at each step)


Why I didn't do this before is anyone's guess


Whoops, can't restore my old reply.

I guess there's a file that includes *CLuaDefs.h* __and__ _CLua*Defs.h_ so that LUA_DECLARE is defined there.
The reason why CLuaDefs.h is included in some files is also that it is a better style to add all dependencies to each file (imagine you want to use the class in another project, but you have to find the exact dependencies first to be able to it).


I will do it.


So how are you supposed to include a link in a menu item now and not have the styling be thrown off?


Okay, I will do this in the next days.


does it work? I've face issue with outdated requirements' builds for Py3.4.


This is an error. Should have been `PARSER.parse_args(argv)`.


Happy to help. I'm super excited about the project, and glad I could contribute.


Splat arguments are actually arrays.


Format is always set to json in the post method.


This was correct! "groups" is plural! I use "capturing groups" to mean "groups that capture stuff". Maybe we should change the term "capturing group" with something else.


Wauw I couldn't do this faster >< Well done.


Please revert this.


I'd have to ask someone closer to OR Redis to be 100% certain, however, I don't think it's a bad idea to leave it off to help future-proof the documentation. @heydonovan have you heard any rumors when Redis 3.0 will be out of beta?


I HATE empty string/array returns and would rather return false if *thing* was not found.


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


LGTM.


Heh, the function names should be swapped in the commit message, otherwise the sentence doesn't any make sense.


Please add this file to https://github.com/mono/mono/blob/4497e9265b3ff2a7d935db80f91ec297f8708efc/data/Makefile.am#L17 to avoid problems with the tarball.

I guess we should remove the script from http://www.mono-project.com/docs/debug+profile/debug/#debugging-with-lldb and just link here?


I changed deleteUser to take the username as the parameter instead, so we must update usages. We should actually use $uid, not $username in this class.


Can't figure it out. No matter what path I try, files end up on the same place.
Thanks anyway.


Quick question - have you already implemented this for Android? I'd like to keep the two sides of the plugin in-sync. If not, it's something I can do.

Thanks again for your work!


@gabrielPeart Why is this change correct?  You are ignoring the parameter "serializeAll".


Sorry, I meant to say: Touch detection and also collision detection between touch location and elf position now works.


TeamCity LabKey :: LabkeyRelease15.3 :: Git postgres 9.4 [Build 103](https://teamcity.labkey.org/viewLog.html?buildId=290027&buildTypeId=LabkeyRelease153_GitPostgres) outcome was **FAILURE**
Summary: Tests failed: 40 (15 new), passed: 247 Build time: 01:18:07
### Failed tests
```
org.labkey.test.tests.CDSTest.testLearnAboutStudyProductsSearch: <no details avaliable>

org.labkey.test.Runner: org.labkey.test.tests.CDSMeasureStoreTest: <no details avaliable>

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

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

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

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

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

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

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

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

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

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


we want to keep this, right?


Hahaha @Chriz007 great! thanks for all the help on helping us making this better.


I did notice that I included fileNames that I was no longer patching here. I've update the pull to only patch the one file.


[See](https://github.com/atom/atom/commits/master). I think it's weird, but santa thinks it's cool.


Yep, was moved into [a setter on the model](https://github.com/DFurnes/northstar/commit/bd93696b54a4435ad369e52c9e02751f36a6d1c6#diff-73e993efb6ae7f1d579f4e967f6224f7R65).


Well, I copied it from another method :P


i use it in 2 places


The main MTK limitation is that white balance is completely ignored/lost.
But the preview clearly shows if the user is using an inappropriate manual white balance.
So my idea is to use the WB user choice to store a better DNG. Obviously there is the need for a matrix for each manual white balance choice.
This solution obviously is not useful with AWB...


Uh


btw I've opened https://github.com/JetBrains/gradle-intellij-plugin/issues/41 and hopefully the plugin will soon also support WebStorm, PyCharm, etc.


wtf is `lektor`


unfortunately no, there's no consistency :(

I for one use this->xxx to reference the parameters when I can't do differently.  If you don't mind, let's keep the class' parameters without "_" trailing char and eventually use it for function parameters. I know it's not defined anywhere, we're still lacking coding guideline (except for styling, we're using astyle to make the code standard).

I can refactor the names for you if you don't want to spend time on this (but not for all your numerous and appreciated branch).


Either needs a result type or `DataTransactionResult.replaceSuccess(oldValue);`


Yeah, at the time I started writing this gem I didn't quite understand how they work. I still don't, but I know I pretty much never need to use them.


Yes.


ah okay that's true. it works fine though as long as you don't have to regenerate the sources. you could also run the tests with gradle inside of IntelliJ though which should in theory also work out of the box.


Windows and Linux can not work with this format of icons. Windows can work only with `.ico`.


Is it possible to only use ES6 modules?


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


> 80 cols


@jefperito por que você alterou aqui pra required = true? após essa modificação o ConsultaCadastro parou de funcionar. Os métodos dos webservices não têm o parâmetro IE pra ser passado adiante. Coloquei em todos os que eram necessários e testei, dá erro de XML mal formado. Ao trocar o required pra false, tudo volta a funcionar.


Let's [avoid globals](http://www.w3.org/wiki/JavaScript_best_practices#Avoid_globals) when possible.


ah, i see... carry on then!


No need to set this value, going to deprecate this in upcoming changes with minio-go - it will be set automatically. By doing getBucketLocation() - works more transparently than defaulting to 'us-east-1'.


What if usernames arn't case sensitive?


The styling looks right on my computer?
~~~java
	ItemStack stackInInput = this.getStackInSlot(1);
		if (FluidHelper.itemStackIsWaterContainer(stackInInput)) {
		ItemStack drainedItemStack = FluidHelper.fillTankFromItem(stackInInput, myTank);
		setInventorySlotContents(1, drainedItemStack);
	}
~~~
to...
~~~java
	ItemStack stackInInput = this.getStackInSlot(1);
	if (FluidHelper.itemStackIsWaterContainer(stackInInput)) {
		ItemStack drainedItemStack = FluidHelper.fillTankFromItem(stackInInput, myTank);
		setInventorySlotContents(1, drainedItemStack);
	}
~~~


Why did this file go away? A readme here in the project root is worthwhile.


What's with only static-method signatures?


Also, if you think that you're working on a key class, don't forget to add Dyxygen comments. We try to add them when we can (Gabor didn't take too much care of this initially, except for rtengine.h).

The resulting doc is hosted here by michael : http://michaelezra.com/projects/rt/documentation/
I know, it's way outdated, but I guess that you know how to build it if you need it.


Was a little surprised to see that `code` was unused, you might want to take a closer look.


updated tests from kyle


Someone here is using tab characters instead of spaces.


This undoes the previous change, it sounds like depending on the flow of starting the game, the room id is initialized differently.  Can you keep it in both places and protect it with a null check?  e.g.
`if (mRoomId == null) {
    mRoomId = room.getRoomId();
}
`


Sério cara?


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


This will make it so that a possible language from the recents is selected *if and only if* it is also the first one in `pairs[curSrcLang]`. However, this is not desired behavior since the first possible language in `recentDstLangs` being chosen is the optimal behavior. Then, if none of these are available, we choose `pairs[curSrcLang][0]`.


I'm doing something very similar. I do have specs for the serializer itself. However, I'd like to add assertions for my controller that A) it attempted to serialize the right object and that it B) serialized the object with the correct serializer.

For my use case, I solved the problem my monkey patching the method mentioned here and then just proceeded to write my own matcher inspired by the `SerializationAssertions` module.

If you're interested, I'd be happy to share the RSpec matcher.


can you combine the if statement into one? e.g.
```
 if( mIncomingInvitationId != null &&  mIncomingInvitationId.equals(invitationId)) {
             mIncomingInvitationId = null;
             switchToScreen(mCurScreen); // This will hide the invitation popup
         }
```


Sorry about that and thanks for fixing my mess :)


just found this ... I'll check it tomorrow on my platform and provide feedback!


all tests pass:
success: http://buildbot.bos1/builders/test-riak_kv/builds/2864


I believe it's since scripts are loaded into new appdomains (for the ability to unload/reload them), when creating an appdomain you can specify it's "location", I guess they did that, without a leading separator, I could submit a fix for that there.


Источник света слишком ярко освещает, если за эмиттером ничего нет

![2](https://cloud.githubusercontent.com/assets/13021826/11641371/6b108628-9d51-11e5-88de-52de5c963bb6.jpg)


Se essa imagem não existir lá na pasta[1], dá erro no processo automático de atualização do servidor (eu percebe que falta a imagem e aborta o processo) e o post não vai aparecer no site

[1] https://github.com/okfn-brasil/gastos_abertos_website/tree/master/static/img/blog


Declared type can be Set and instance can be immutable:
`private static final Set<String> AUTHORIZED_PERMISSIONS = ImmutableSet.of(GlobalPermissions.SCAN_EXECUTION, GlobalPermissions.SYSTEM_ADMIN);`


Ah crap, of course not. Thanks again.


IV вырабатывать случайно. Во всех режимах использовать предсказуемые IV крайне плохо, а в CTR - смерти подобно.


Очень магическая строчка. Мб вынести в отдельный класс с переменными с адекватными названиями?


See https://code.google.com/p/google-web-toolkit/wiki/ResourceOracle (which we need to backup!)
Indeed the exclude is not needed, by design (this unsurprisingly looks a bit similar to how BUILD files compartmentalize packages in Bazel)


ESI review


Thanks for catching the error
You might also want to change the path inside
public void testArchivesTgz() throws Exception {
    testArchives("test/jvm/backtype/storm/localizer/localtestwithsymlink.tgz", true,
        21344);
  } and all such methods in the current JIRA


Another ESI review


If you are up for performance and AddDefinition/RemoveDefinition do not use any IO, you could move them inside of the upper loops and use std::set instead of std::map, but the code will be less readable...

I assume cmake_parse_arguments is used often in macros in which case more probably ARGN could have wrong content.


Wrap in a `finally` here to close the cursor.


ESI line review


#4702-AirloopHVACUnitarySystem-autosizing-incorrect-for-heating-only-systems-when-using-FlowPerHeatingCapacity (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1966 of 1973 tests passed)

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


С rb/wb проблем будет меньше.


Oh alright. I don't think they would want to merge it since it can break compatibility


Теперь это ведь можно убрать из класса `EmbeddedSimulation`?


I'm only slightly unhappy about adding extra testenvs.


Future proofing is a fair point! I left it out of #77.


Откуда `data` браться будет :grinning:


Sorry, I filed the internal bug before looking at the thread here, and obviously I neither updated it with the discussion here nor reread it when coming back.


Do we really drop Debian 7 support while it is still supported by Debian?


Is fullscreen video playback ok for you ?


Надо как-то обработать.


TeamCity LabKey :: Trunk :: Community :: CDS postgres 9.4 [Build 26](https://teamcity.labkey.org/viewLog.html?buildId=290029&buildTypeId=LabkeyTrunk_CdsPostgres94) outcome was **FAILURE**
Summary: Tests failed: 13 (1 new), passed: 34 Build time: 01:19:11
### Failed tests
```
org.labkey.test.tests.CDSTest.verifyFilterDisplays: <no details avaliable>

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

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

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

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

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

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

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

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

org.labkey.test.Runner: org.labkey.test.tests.CDSLoginTest: <no details avaliable>

org.labkey.test.tests.CDSLoginTest.testSessionTimeoutIntercept: <no details avaliable>

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


This method already exited above. Please edit the above method rather than making a new one. There is some extra functionality here that you're missing (auto group creation). You can use the same SQL statement if there isn't a parent, just pass "None" in as the value. Psycopg2 should convert that to a NULL.


Ах, стоп. Он же замыкается. Я скобок недосчитал.


TeamCity LabKey :: Sprint :: Premium :: Git sqlserver 2014 [Build 4](https://teamcity.labkey.org/viewLog.html?buildId=290054&buildTypeId=LabKey_Sprint_2_LabkeyPremiumTrunk_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:06:17


Double separators do not cause issues AFAIK, anyway I found the source to the issue in their code, https://github.com/crosire/scripthookvdotnet/blob/dev/source/Main.cpp line 31, adding a separator after "scripts" would do the trick, the only reason they can combine that string without prefixing a separator is because there's already one there, I'm on a limited workspace at the moment so I wouldn't be able to clone and submit the patch for the next few hours, you could take the honor if you wish.


Из родительской функции `(num, data) => `. Там вполне прозрачная видимость.


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


Can you check this typo 'Funcionalidade'


It looks like this PR has been merged -- can this workaround be removed now?


right, modified too quickly. thanks


@Gruck Indeed ; a permission issue, it seems. I just fixed it. Thanks for reporting it!


Somehow I missed this. Next week I'll get right on this!


Очень магическая строчка. Мб вынести в отдельный класс с переменными с адекватными названиями?


ну тут от класса-то осталось всего ничего. по идее, можно выпилить его уже.


review_class is not used no more


comment above also needs to be changed


Можешь глянуть на es5-версию, там эти правки вообще никак не отражаются.


Previous version of CritiqueBrainz used review classes for various features within the website. The problem is that these classes are not very useful and confusing. So they are removed now.


не, не надо. это как раз тот случай, когда модель не содержит инита. все остальные классы исключений полетят дальше и будут пойманы глобальным кетчем


Hey Amber, since you want this to toggle back and forth you may need to use an if statement and check what the html is and then figure out what you want to change it to after that.

```
var dashboardTitle = $("#checklist-banner-a").html();
if (dashboardtitle === "My List ⇣") {
    $("#checklist-banner-a").html("Back to Content ⇡");
}
else {
    $("#checklist-banner-a").html("My List ⇣");
}
```

Since I'm reusing the #checklist-banner-a selector it would probably be smart to save that as a variable, so you don't have to use extra resources.


If we want to explicitly support using GIN and Dagger at the same time, then ideally we'd want a separate artifact shared between them (that would mean releasing a new version of GIN).
But given both use javax.inject v1 (there's no other version), it doesn't really matter if there are 2 copies in the ResourceOracle.
Maybe we could start that way to unblock the situation, then possibly have an inject-gwt (that uses super-source) and then re-release GIN and Dagger to use it.
WDYT?


No prob :dancers:


Я уже понял. Все нормально.


LAME. :-1:


Rebased the branch without the postfix underscores. I will change any other places when they are reviewed, but I think the listeners-to-signals-RFC branch is to only other one introducing member variables.


Ок, удалил его вообще.


@chapmanb @scatreux as part of the new RTG Tools 3.6 release, I put a rocplot screencapture on https://github.com/RealTimeGenomics/rtg-tools and you can see from that a rough indication of how much ROC performance you can miss out on by using a lowest-common-denominator score.


Why was this file here? `actions` folder doesn't seems to be supported by DirectAdmin, or am I wrong here? (I also wasn't able to get it working tho, and it didn't out-of-the-box)


@zimbatm: This hash [doesn't seem to be correct](https://headcounter.org/hydra/build/813217/nixlog/1/raw). Was it incorrect in the first place or did the upstream project alter the tag?


Кстати, этот `var` вроде можно поместить внутрь `if`а ниже.


Might want to use https://www.gitignore.io/api/osx%2Clinux%2Cwindows%2Cvisualstudio as your .gitignore


да, забыл просто про нее. тут нам надо просто избавиться от расширения и имя модели вычленить. надо подумать, может взять URI и воспользоваться готовым хелпером из RaoNaming


Т.е. `getDeclaredMethod()` выкидывает исключение, а не возвращает ошибку? Тогда ок.


то же самое, что и выше. на нет и суда нет, как говорится.


sp - current


extra space


Да. Я сначала думал, что он вернет `null`, но нет.


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


Please move this to 0xf0000000. This will allow larger ROM sizes


oh that's rich coming from you :)


netifaces is being used though https://github.com/openstack/oslo.utils/blob/master/oslo_utils/netutils.py#L25


Yeah you're right. But I'm not on my computer either so I can't do it right
now

El lun., 7 de diciembre de 2015 23:22, Dor <notifications@github.com>
escribió:

> Double separators do not cause issues AFAIK, anyway I found the source to
> the issue in their code,
> https://github.com/crosire/scripthookvdotnet/blob/dev/source/Main.cpp
> line 31, adding a separator after "scripts" would do the trick, the only
> reason they can combine that string without prefixing a separator is
> because there's already one there, I'm on a limited workspace at the moment
> so I wouldn't be able to clone and submit the patch for the next few hours,
> you could take the honor if you wish.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Guad/GTACoop/commit/953bcf12b5cab14b53ada2ecd78b345512378608#commitcomment-14833557>
> .
>


109626134-VariousDocumentationIssues (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1976 of 1978 tests passed)

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


Точно)


The power was out! Go on again.


Я так понимаю, `-4` убирает `.rao`?


Maybe this function should have a different name? Or different documentation? Without knowing the code, it is unclear that filter is the currently value of the input


Move to 0xf0000000


Remove this


@ptnalexa The power was out! Go on again.


The `actions ` is a custom folder and not created for DirectAdmin. It was to store all actions and trigger them via includes/POST's.

The code was indeed not ready to use because of a missing parameter in letsencrypt. Issue for feature request is open.


This looks good. I will also install this update and try it in one of our orgs. Good job @ceiroa


Ah, thanks! I'll remember that next time :grin:


elf-loader, jtag_vpi, mt48lc16m16a2, vlog_tb_utils and wiredelay should be in the depend sections of modelsim and icarus instead


именно. надо поковырять класс File, может у него можно без расширения имя получить


Why set a weak default here in the first place?


Ah, I wasn't able to trigger it using a POST, so that must be through include?

Yeah, I removed that part because of the move to a PHP library.


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


On 07/12/15 21:35, foyzur wrote:
> Given that we solve the correctness issue by checking the versioning
> every time we grab a lock, I believe the separate mechanism to track
> MD version (without using invalidation messages) is easier to debug,
> understand and maintain.

The syscache invalidation mechanism is there, and needs to be maintained
anyway, even if you decide to not use it. By re-inventing the wheel -
even if that new wheel is simpler - is just extra code that we need to
maintain in addition to what's there already. I strongly advise you to
use the existing mechanism, so that you can benefit from any possible
bug fixes and improvements to the syscache in the future, without having
to apply the same fixes/improvements separately to this parallel mechanism.

> Besides, for such a simple mechanism/requirement we shouldn't require
> to couple the syscache existence of an object and make the object
> part of the syscache just to ensure proper tracking.

You could patch just that part of, instead of re-inventing the whole
wheel. For example, you could hack PrepareToInvalidateTuple to send
invalidation events also for catalog tables without a syscache, perhaps
using a magic syscache ID value for those invalidation events. From
there on, you could assume that there will be an invalidation event for
everything you need.

That said, I have to wonder what catalog you need invalidations on, that
don't have a syscache on them. Because the Postgres planner would
probably also have issues with that catalog. Perhaps it would be even
better if you could list all the catalogs that you *do* need
invalidation events from, and put in some kind of a compile-time check
or assertion that there is indeed a syscache on all of them.

> The solution is also lighter weight as at a high level, it processes
> the invalidation message (it doesn't, but this is for conceptual
> discussion) at the originator, rather than receiving the message on
> every backend and parsing and determining that md version has
> changed. Therefore, IMHO, this separate mechanism is better than
> retrofitting into existing syscache mechanism.

The syscache invalidations are happening anyway, so the performance
argument is moot.

BTW, how expensive is it to populate the metadata cache in ORCA, anyway?
Presumably the calls to populate it use the syscache, so those should be
fairly cheap. Have you considered simply resetting the cache for every
query that's planned? Or is that how it works today?

- Heikki


cc @matthewjohnston4  - is this is the best way to do this?


Definitely will revert when we have an appropriate alternative. Currently, spectator is handled by copying over the player who is being spectated's playerState_t. perhaps something analogous can be done with the entity?


109626134-VariousDocumentationIssues (mjwitte) - 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)


While you're at it can you remove this no-longer-necessary "idiom" from the SAMRAI build?
```
    mpi = next(m for m in ('openmpi', 'mpich', 'mvapich')
                       if m in spec)
```
That was from when Specs couldn't match on vdeps in `__getitem__`.   Now, plain-old `spec['mpi']` will work.


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


Do we need to set this option here? I think we are already setting in BeforeClass.


Thanks for this. It looks much better now. Just a few small things I would like to change before committing this


Is this extra level of indirection worth it, given that the only validateIdentityFunc is for domain?


Is this too specific?  Should it be `3.8.0:`?


It does for 32bit and fails for 64bit. Further investigation required.


Good to know. I'll update the PR and remove the exclude then once the other discussion has come to a decision.

(there is already a wiki backup: [gwtproject/old_google_code_wiki](https://github.com/gwtproject/old_google_code_wiki))


I see what you did there :laughing:

Nice work on this project


> the explicit return is misleading


@mckenzielong indeed, thanks for keeping up with it! I actually didn't intend for this to get merged as it was. I'll be reverting some of the changes in an upcoming commit. Thanks!


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


Just realized: the default function is incorrectly saving the local time as a Zulu-time timestamp.  If I force refresh my tokens right now (1730EST), the box expires_at gets saved as 2330Z, but the googledrive expires_at is saved as 1830Z, which has already expired.  This means gdrive will get refreshed every single time.


Perhaps, although sometimes there changes between versions of SAMRAI that would break the build.


I'll update the PR.


hence the EDIT :P


complete


TeamCity LabKey :: Trunk :: Premium :: Git postgres 9.4 [Build 828](https://teamcity.labkey.org/viewLog.html?buildId=290025&buildTypeId=LabkeyTrunk_GitPostgres) outcome was **FAILURE**
Summary: Tests failed: 23 (1 new), passed: 257 Build time: 01:40:05
### Failed tests
```
org.labkey.test.Runner: org.labkey.test.tests.ScrumtimeTest: <no details avaliable>

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

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

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

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

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

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

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

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

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

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

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


I don't think `match` would ever equal `out` anyway.


@vtimofee the URLs printed on the album sleeves should be up and running again soon.  the data is stored in S3 so it will never go anywhere

i'm going to hook up all the other downloads soon but i did this as a test/example


@aklaver No idea I'm afraid, tried to inform the owner even filled in a bug report but it was ignored and the bug was set to fixed with no explanation. So I give up and stopped using the autocomplete component.


> In this case **it** is better ...


Either add some docs re: the semantics of this field, or name it something even more explicit, eg. AllowableEmailDomain (yuck, but you get the point)


Looks good to me.

Since you showed me it works I think its good to just push in.


Is it possible that we could still end up with batches of size >= OUTPUT_BATCH_SIZE (32K)? Sorry I didn't look at the new mergejoin patch in detail.


un-indent


I've got a WIP branch [1] adding RFC 2119 capitalization that's just blocking on #3 landing (still another day before its new window closes [2]).  I don't mind if we want to land some of that capitalization here, but I think you should either stick with lowercase for now or explicitly green-light discussion on the capitalization you're suggesting ;).

[1]: https://github.com/wking/oci-command-line-api/tree/rfc-2119
[2]: https://github.com/wking/oci-command-line-api/pull/3#issuecomment-162086895


Thanks!


BoringSSL doesn't have this function. So that could be handled in the same obfuscated way as `CONF_modules_load_file()`:
```
--- a/lib/vtls/openssl.c 2015-12-02 16:34:00
+++ b/vtls/openssl.c   2015-12-07 23:38:22
@@ -123,8 +123,9 @@
 #define NO_RAND_SEED 1
 /* In BoringSSL OpenSSL_add_all_algorithms does nothing */
 #define OpenSSL_add_all_algorithms()
-/* BoringSSL does not have CONF_modules_load_file */
+/* BoringSSL does not have CONF_modules_load_file nor CONF_modules_free */
 #define CONF_modules_load_file(a,b,c)
+#define CONF_modules_free()
 #endif

 #if (OPENSSL_VERSION_NUMBER < 0x0090808fL) || defined(OPENSSL_IS_BORINGSSL)
```


Why? What’s the issue with this? We use a non-standard SSH key filename, so we need to tell Travis to use that key.


No particular reason, it just felt weird to refine `string` (used in error messages) but not `equals` and `hash`.


Might as well add the the if null check here too.    Thanks!


Yeah, I am not understanding what it was supposed to fix and why something that works no longer works. Seems like a regression to me.


POST 적는 문법이 잘못 되어서 DB에 데이터가 들어가지 않았음.


Unfortunately so, I will now be moving everything over ronspogot as I am no longer allowed to post plugins on bukkit


No problem at all!


complete


* to spigot


Yeah I was definitely not arguing for removing initialization or um, destruction.

You're right that it gets kinda weird when they can also add variables. And you can't exactly just keep lisp values either, since for example a lisp function would maybe call one of the added C functions. You'd quickly get in to a big mess of keeping track of things.

I guess I'm a little bit torn on the whole thing. You also don't want it to be too cumbersome to write extensions, as this seems like something that is easy to slip up on whilst making an extension. But yeah, unloading isn't really the most common use-case ever.


move storing of tokens into `save`/`restore` position


OUTPUT_BATCH_SIZE is 32k. I tested with outputPosition == OUTPUT_BATCH_SIZE and changed it to outputPosition >= OUTPUT_BATCH_SIZE just to be on safe side.


Just noticed this boo-boo. Please feel free to update it to `queriesWithPairs`.


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


Why don't we set the default as the DefaultRules anymore?


Remove this


But also if unloading is quite uncommon, most extensions would probably not be designed for being unloaded anyway. So it almost seems like the cleanup function may as well be called by the user from lisp before unloading.


This should stay `funC <COMMAND>`, because its an example of the full invocation.


All the changes above are unrelated and seem to be coming from a rebase conflict. I think this shouldn't be changed.


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


where?


i think not needed


So this is not the change required for fixing the bug right?


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


yup


complete


Commenting on commits is not a good option for reporting issues. In this case, the issue is likely already addressed: https://github.com/jquery/jquery-ui/commit/de2ef2a585447cf75fc8d4a734c12aa2bbd028c2


Only catch `ControlFlowError`, e.g.
```
if (e instanceof ControlFlowError) {
          ...
        } else {
          throw e;
        }
```


fast-forwarding end-to-end/timeseries to borshop-integration-1294-at/primaries_only_in_coverage = d6d61f41


This method name is too generic and does not really describe what the method does.


saw approval from javajolt
at https://github.com/basho/riak_pb/commit/8601c304569c0a24b674c6890265e9d2d433cee4


merging basho/riak_pb/feature/jrd/toggle-pb-t2b = 8601c304 into borshop-integration-171-feature/jrd/toggle-pb-t2b


basho/riak_pb/feature/jrd/toggle-pb-t2b = 8601c304 merged ok, testing candidate = 5561f2f2


Add a test for `...<b && c >...` to expect error `unexpected closing tag`...


And we probably want to stick with “invocation of `<COMMAND>`” (instead of “invocation of the `<COMMAND>`), although I don't feel particularly strongly about that.


Just modifying package.json would suffice. Npm adds ^ by default.


This is to address #114


Yeah, can do.


The rest of this spec uses “exit code”, so we probably want to stick with that and say “… exit with a nonzero code and…”.


Reviewed.  Looks good to me.


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


@philbogle FYI that the scope of this conditional has been expanded to include other companies.


Thanks for letting me know!


This is a known issue with CMake not finding the appropriate Python library -- see http://www.itk.org/Bug/view.php?id=14809 and my suggested fix (scroll to the bottom).


hallo


Посмотри образцы тестов, что уже сделаны. Эти тесты не годятся.


TODO remove this check, since support for `require.ensure` has been factored out of the core `install.js` implementation: https://github.com/benjamn/install/commit/73896dd55e1bfd2796b6fe5ca6e43d341c8e1585


I wasn't going to touch older logs, but sure, why not...


Name does not really indicate what the test is doing.


Kyle and I were both involved in this code.


Wanna wrap this in a `t()` ?


Is it useful to filter on `trc_election_type_id` and `trc_election_status_id`? I'm not sure what either column means. If we do want to keep these filters (and their corresponding fields in the output), how about getting clearer names from FEC?


That's what i thought until this was posted on my wall

> LogicallyRogue  - 20 hours ago
> On the topic of Plex-Plugin 1.0.13 (with PlexPy) - it appears that the plugin does not consider python a prereq. So on a base install, PlexPy doesn't work. However, once python is installed and the service is rebooted - it works fine. So I would assume you just need to add Python as a prereq to the plug in. THanks!

So to be on the safe side i added it.


Great! Will create icons for Windows & Linux (added to the PR descriptions) :+1:


Now that we're adding min and max election dates, is the `upcoming` filter still useful? It seems like it's redundant with `min_election_date`, but less flexible.


It's possible that the problem is in the test.


I dont think I want to make this localized yet mostly because we probably will change it.


cool


On Mon, Dec 07, 2015 at 02:53:18PM -0800, Mike Brown wrote:
> Reviewed.  Looks good to me.

Heh, I haven't even PRed this yet ;).  One thing I'm not clear on is
whether MAY [1] is intended for these sort of generic extension
mechanisms (e.g. “you MAY add other options”), or whether it's just
for explicit behavior (e.g. “you MAY add a --log-level option with
these semantics: …”).

[1]: http://tools.ietf.org/html/rfc2119#section-5


Can you think of other tests?


Yes, I agree with the RFC 2119 capitalization branch changes.  Noted added to said branch in progress [1] https://github.com/wking/oci-command-line-api/commit/527f3c629a7224144c1e5e41a8a197fe0eb5bc00.


I made the edits separately in the web browser.

Cut me some slack I only actually started using github yesterday.


TeamCity LabKey :: Trunk :: Premium :: Git sqlserver 2014 [Build 91](https://teamcity.labkey.org/viewLog.html?buildId=290078&buildTypeId=LabkeyTrunk_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:02:34


:v LOL is not darkness it is based on Darkness :+1:


Nit: capitalize the commit message like "Set query ID as name prefix of HDFS files"


This commit looks fine to me although I do not think that (at least if OGDF_SEPARATE_TESTS is off) the time to compile the tests is not that large.

I'm not sure if WITH_TEST should be named OGDF_WITH_TEST (or OGDF_WITH_TESTS). What do you think, @TiloW?


@gustavocms Both when we have the url ready


Hah, I didn't know you had commit access here :)
Thanks!


Shouldn't we write a warning into the console if `chown` is not found ?


At last.


No, in fact I need it…


@gustavocms This is like a carousel basically. The posting may have more than one image. That is the impression I get from the design I was provided.


There is an API for ADS: https://github.com/adsabs/adsabs-dev-api  But we need a token in order to access it, and I'm not sure that using it within this package would be acceptable.


TeamCity LabKey :: Trunk :: Premium :: Git postgres 9.4 [Build 829](https://teamcity.labkey.org/viewLog.html?buildId=290050&buildTypeId=LabkeyTrunk_GitPostgres) outcome was **FAILURE**
Summary: Tests failed: 25 (2 new), passed: 255 Build time: 01:33:47
### Failed tests
```
org.labkey.test.Runner: org.labkey.test.tests.CDSMeasureStoreTest: <no details avaliable>

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

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

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

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

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

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

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

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

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

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

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


I have a bit too fast computer to see the difference even with all the gtk_ symbols. But I guess I'd be able to see it in the profiler if I try.

What I was thinking about when writing this patch was to make the search cheap and basically independent of the length of the prefix so the "characters to type for autocompletion" settings could be eliminated. We could pop up the symbol list intelligently based on the number of results - now we pop up the list with 30 first results even if there are 10000 matching symbols - there's almost no chance that the symbol the user wants is in the list. We could delay the pop up until we get only 30 symbols or less so it's guaranteed that what the user wants is in the list. What do you think?


No, no, in fact no.


OK.


Извлечь проперти можно гораздо проще. У нас уже кто-то извлекал с помощью аннотации


That's fair!


[image: Inline image 4][image: Inline image 3][image: Inline image 2][image:
Inline image 1]

On Mon, Dec 7, 2015 at 4:53 PM, diaod01 <notifications@github.com> wrote:

> create database on the server before use
> get the package before build
> go get github.com/go-sql-driver/mysql
> go get github.com/go-xorm/xorm
> go get github.com/labstack/echo
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/trandt01/acs560_course_project/commit/b873f69a7413d754c2e98b6edad1ad32f73ca45d#commitcomment-14832898>
> .
>


A bug is submitted at launchpad for oslo.utils. https://bugs.launchpad.net/oslo.utils/+bug/1523706.


:metal:


Какой смысл в громоздкости этой конструкции?


shim everything... :) https://github.com/RR-msm7x30/android_device_samsung_ancora/commit/79533a1c1114cb1744d82896c5f914b0aa349fe7

ok..done...it is ready to test..(but we need to figure out vendor part/hex editing stuff first)
ı hope our shim lib will work good...


np


Nicely done :+1:


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


:eyes:


I don't get it... Why exactly is this function necessary?

Why parse wgetrc config files manually and set the proxy variable when wget will do exactly this automatically?

And actually, why `$PROXY`? Every other program is using the well known `http_proxy` variable. Why invent a new one? And then use this one to just override the default variable? What?


probably didn't want to commit this file


Why is npm 3 required? It is terribly slow.


@ekonstantinidis you can use [iConvert](https://iconverticons.com/online/).


:+1: :boom:


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


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


не понятно из названия что делает этот тест


I don't think this is lame at all. https://www.elastic.co/guide/en/logstash/current/pipeline.html#_fault_tolerance suggests that a bounded queue between stages is the only measure to limit data loss if Logstash crashes. In my opinion, the same approach needs to be applied for KPL when used as part of Logstash output pipeline: until you limit number of records KPL accepts without making sure it gets through to Kinesis, there is unbound amount of data potentially lost if crash happens.


This (and for the copies below) has to be `https://github.com/ogdf/ogdf.git` for the final version.


Add :func:`map_concat` function


This is kind of reasonable, might have been okay to implementing voding using integers as well, +1 for "up" and -1 for "down". That way we could skip all the "is_up" checks in the code and would be easier to run some queries to get the "best" quotes.

Also, might have been achievable to add features like "strongly up" and "strongly down" in the future while not sacrificing any readability or functionality to just get it made.


Isn't /system/etc already linked to /etc?


@ruiaraujo that was a temporary change for diagnosing some other issues i had, it was reverted in the following commit https://github.com/erikras/react-redux-universal-hot-example/commit/4ea989dd3d88d2cd9bbd6905633bc50eec9052b1


See how `map_keys` and `map_values` are written: `map_concat(x<K,V>, y<K,V>) -> map<V>`. Please also adapt the description accordingly.


remove extra space


Give a different name in neko it's better


109626134-VariousDocumentationIssues (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (904 of 904 tests passed)

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


For easier debugging, can you add the function name and line ?
You added the file descriptor address, in what that can be helpful ? Excuse my stupid question.


@bit101 probably want to remove console.log :)


I think that using such method assign will perform very bad, the whole idea of Math.imul I think is that JIT can optimize for it


Basically just do a while loop to check if a file exist, if it does increment the id number. NOTE deleting the files generated after the program has run is recommended


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


@bit101 seems like this code duplication could be removed if the original styles object was duplicated(cloned) instead of being modified


Fair call :) My #techwriting skills are pretty bad - I wrote this in 35 seconds and didn't even proofread it. I'll revise it soon!


I have no experience in writing package configurations for CMake but these `if(WIN32) ... elseif(APPLE) ... else() ... endif()` parts look like CMake should (be able to) handle this OS-specific stuff and not leave that to the one writing configuration. But I am not sure about that. @TiloW, do you know something here?


You may want to keep the styling on `.txp-option-link` to prevent line breaking mid word in languages such as CJK – and maybe others, I’m a bit rusty on line breaking rules for e.g. arabic and south-asian languages.


MAY means OPTIONAL.  So in the first example you are saying additional options are in fact optional.  In the second example you are saying those semantics are optional for the log level option are optional semantics.  Lower case may holds less weight.


Agreed with the above, but also ActiveRecord automatically gives you the predicate method (i.e. the one with the question mark) for boolean columns so isn't actually doing anything.


add tears


Needs more keywords


The css override is for themes that use bootstrap...


Disagree in removing muparser.

The integration of the muparser library is part of the entity system and the particle system.


@glinscott @mcostalba @zamar: Expected cost, for the double `(0,5)` test:
```
Elo	BayesElo(STC)	BayesElo(LTC)	%Pass	CPU days
-2.00	-3.23	-3.75	0.00%	4.65
-1.50	-2.42	-2.81	0.00%	5.46
-1.00	-1.61	-1.87	0.00%	6.68
-0.50	-0.81	-0.94	0.03%	8.76
0.00	0.00	0.00	0.25%	13.08
0.50	0.81	0.94	1.65%	22.76
1.00	1.61	1.87	8.52%	43.09
1.50	2.42	2.81	28.17%	69.68
2.00	3.23	3.75	56.95%	83.09
2.50	4.03	4.69	79.73%	78.07
3.00	4.84	5.62	91.69%	65.75
3.50	5.65	6.56	96.78%	54.09
4.00	6.45	7.50	98.80%	44.91
4.50	7.26	8.43	99.55%	38.10
5.00	8.07	9.37	99.83%	32.99
5.50	8.87	10.31	99.95%	29.11
6.00	9.68	11.24	99.99%	26.01
```
I used the drawelo I had estimated before, with 15+0.05 and 60+0.05. When we have more data on 100+0.1, I will recalc drawelo properly, run the numbers, and update the wiki:
https://github.com/glinscott/fishtest/wiki/Creating-my-first-test#standard-tests-2


Hmm.. I think this needs to be `background-repeat` right?


Victor, Thank you for your love, <3 <3 <3 You are the best, my dearest baby @pwnall @spark008


> For easier debugging, can you add the function name and line ?

This should be handled better with the logging rework.

> You added the file descriptor address, in what that can be helpful ? Excuse my stupid question.

Previously you just got generic `close()` error without any other fd/n (index loop) number, which helps with debugging. And it's not fd address, it's fd number.


Same comment applies here - I think the property needs to be `background-repeat`


Do we want to store the results here? If we call the getTableNames() multiple times, we don't have to make the same metastore call again? With caching this should be fast I guess, but it also avoids the cache lookup.


this fixes #104 (not #102 which was fixed earlier)


`content-available` needs to be quoted inside a literal javascript object or JSON, with different errors being thrown at each case:
- `Uncaught SyntaxError: Unexpected token -`
- http://www.json.org/

It even requires double quotes if we're talking about strict JSON.


We already have an API in DrillHiveMetaStoreClient, do we just want to pass the client ref to HiveDatabaseSchema?


Missing module docstring. (C0111, missing-docstring, )

*Detected by PyLintBear with severity 0 while running section `python`.*

*The issue occurred in the file `test.py`, lines 1 to 1.*

```
```


Missing function docstring. (C0111, missing-docstring, main)

*Detected by PyLintBear with severity 0 while running section `python`.*

*The issue occurred in the file `test.py`, lines 1 to 1.*

```
```


Couple places here where `background-image: no-repeat;` , I think may need to change to `background-repeat`.


Trailing whitespace. (C0303, trailing-whitespace, )

*Detected by PyLintBear with severity 0 while running section `python`.*

*The issue occurred in the lines 10 to 10.*


Missing function docstring. (C0111, missing-docstring, a_lot_of_args)

*Detected by PyLintBear with severity 0 while running section `python`.*

*The issue occurred in the lines 5 to 5.*


Too many arguments (8/5). (R0913, too-many-arguments, a_lot_of_args)

*Detected by PyLintBear with severity 0 while running section `python`.*

*The issue occurred in the lines 5 to 5.*


Unused argument 'cccc'. (W0613, unused-argument, a_lot_of_args)

*Detected by PyLintBear with severity 1 while running section `python`.*

*The issue occurred in the lines 5 to 5.*


Unused argument 'gggg'. (W0613, unused-argument, a_lot_of_args)

*Detected by PyLintBear with severity 1 while running section `python`.*

*The issue occurred in the lines 5 to 5.*


Unused argument 'eeee'. (W0613, unused-argument, a_lot_of_args)

*Detected by PyLintBear with severity 1 while running section `python`.*

*The issue occurred in the lines 5 to 5.*


Line contains following spacing inconsistencies:
- Trailing whitespaces.

*Detected by SpaceConsistencyBear with severity 1 while running section `python`.*

*The issue occurred in the lines 10 to 10.*

The issue can be fixed by applying the following patch:

```diff
--- a/test.py
+++ b/test.py
@@ -7,5 +7,5 @@
     cccc += dddd
     eeee += ffff
     gggg += hhhh
-
+
     return aaaa
```


109626134-VariousDocumentationIssues (mjwitte) - Win64-Windows-7-VisualStudio-12: OK (1977 of 1978 tests passed)

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


Should be 1.8.8... And I forgot about tag...


Thanks Len, can you please expand a bit more on what the screencapture is showing and the point
you are trying to make?
The angle I'm coming from is that I'm looking to use RTG to compare different pipeline's performance,
in terms of ROC at the variant calling level. So selecting the same score across pipelines makes
more sense to me, to keep the comparison across pipelines apples-to-apples.

S.


I upload the script in its very preliminary version


This is clearly a non functional change in fishtest conditions. What's the point of testing it ?


Isn't it in `Sources/` now?


The issue has been addressed in ogrisel/python-appveyor-demo. I've just pulled in the latest scripts from `master` and now everything works like a charm :)


Thanks, I will pull this, and then add a bit more context explanation at the start!


it will readded as soon as we need it :) if you want to rebase your work on top of the new master youll only need to revert that specific commit and youre good to go (well apart from the other changes like renaming your .h to .hpp files and moving your source files accordingly, i think that will need some time)


@aschaeffer Yes. You can read that as soon as the entity and particle system are integrated :)


endcode text --> decode and encode text (respectively)


No, I moved everything back to original folders, cause as you said there is no need in separate plists. I run `pod spec lint`, there were no errors.


But what's the problem here? If I understand correctly, on e.g. V8, `Math.imul` is a "built-in" function whose internal structure has some specific id that is [checked by the optimizer](https://github.com/v8/v8/blob/7765a5fd8871f6955820b88aed9edd1995705bab/src/compiler/js-builtin-reducer.cc#L100-L102) and reduced to native call and it doesn't matter whether we use it directly as `Math.imul` or assign it to some variable/field and use like that. Am I wrong?


respectively


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


Well I said `CODE_SIGNING_IDENTITY` from memory (not at home with an an Xcode right now) but you might check that and check if you don't need others as well.


indent


line 26 is no longer accurate


On Mon, Dec 07, 2015 at 03:17:38PM -0800, Mike Brown wrote:
> MAY means OPTIONAL.  So in the first example you are saying
> additional options are in fact optional.

That's what I want to say here, but the RFC wording has a bunch of
singular references: “an item”, “the item”, “a particular option” [1],
which makes it sound like the RFC authors weren't intending it to be
used for marking generic extension mechanisms.  And unfortuately RFC
822 predated RFC 2119, so we can't check the X- prefix for a precedent
[2].  The RFC 2119 wording I'm particuarly concerned about is [1]:

  An implementation which does not include a particular option MUST be
  prepared to interoperate with another implementation which does
  include the option, though perhaps with reduced functionality.

Which might be saying that “runtime MAY support [global] options”
would mean that runtimes couldn't fail fast if they saw an option they
didn't recognize.

> Lower case may holds less weight.

It might be more helpful to say “upper-case entries translate to
compliance test cases” ;), and by that criterion we'd want lowecase
may for the generic extension mechanisms.

[1]: http://tools.ietf.org/html/rfc2119#section-5
[2]: http://tools.ietf.org/html/rfc822#section-4.7.5


Same issue with line 12.


My pleasure.


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


Looks like ``Math.floor(Date.now()/1000/60/60/24)`` should be a constant evaluated on file creation?


I had a feeling it was something like this. Didn't really try it out. Looks good!


As long as deployment does not fail, fine. I can't change my hosting environment in this case

Am 08.12.2015 00:01 schrieb Jérémy Huet <notifications@github.com>:

Shouldn't we write a warning into the console if chown is not found ?

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


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


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


You shouldn't be creating users with names that are similar to those in other files. In fact I would re-theme the names of explorations here entirely to minimise the risk of conflicts.


I think you need to be in "source" for the {ES-version} to be replaced. Does this work for you when you compile the docs?


I just uploaded a Django version of the server part here:
https://github.com/vplin/Cloud_Forecast_Server
This one is based on Python 2.7 which I think might be more suitable for Django project. I used POST to accept the data from the gateway.


I agree but it was requested by @zamar
See https://github.com/official-stockfish/Stockfish/pull/519


Here as well. you might need: +["source","sh",subs="attributes,callouts"] in front.


Please use the GALLERY_URL_SUFFIX as is done in publicationAndGallery.js.


Is this essential?


this seems like a pretty indirect test of setting up the vcap password, might want to check that /etc/passwd has the expected value but that is kinda sketchy as well. Maybe the thing to do would be to try and `su vcap` with the new password.


likewise


Thanks, should be fixed in https://github.com/coova/coova-chilli/pull/168


Is this Kibana-version or kibana-version? It needs to be Kibana-version.


Well obviously this is new and can be a reason of failure compared to the iOS target of Travis doesn't have that Mac Developer cert?!


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


`bosh ssh` supports password-less sudo for new stemcells + new CLI so you should be able to run `bosh ssh 'sudo <some-command>` rather than needing a helper if we only use sudo a handful of times


I had seen the definition of GetWindowText as GetWindowTextW or GetWindowTextA depending on the character set. But I overestimated its scope. I've modified that line in events.cpp, and changed the character mode. It compiles just fine.

I've overloaded the function DisplayError in scripting.cpp, and defined a function ConvertNarrowToWide that converts a narrow string to a wide one (needs to be done twice, for the error message and for the title of the box). For the moment I left it in dialog.cpp. But it seems to me that it should be put in another place of the code. Any suggestion on the matter?

Everything is working alright on my computer (I've also started to take a look at the saving problem, hopefully in a few days I'll have a clearer view of everything).


Here as well, ["source", subs="attributes,callouts"] in front?


In the interests of speed I would combine these into a single test.


fixes issue #20


Here's another change to inspect to check if it can be the reason


And here I was starting to wonder if it's an issue on my end, at least I had the chance to learn more about the patcher and the instruction set's :/


It would be good to also check that the rating is displayed correctly.


Create Numbers repo


Same


Ya estaban hechas, faltaba hacer el control de errores del ID, que todavía no sabíamos.


If it's convenient I would add a check of the rating displayed within the player, which you can access by clicking the (i) in the navbar.


bug report by mattjbenson.


Can we add a `dns` tag? The idea is that these tests will eventually move out of BATs because while DNS testing is a high level integration test between the Director, CPI, and Agent these tests don't really fit with the rest of the tests in the BATs suite


109626134-VariousDocumentationIssues (mjwitte) - i386-Windows-7-VisualStudio-12: OK (1977 of 1978 tests passed)

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


Which file is the data handling performed in?


Ok, thanks for answering my question


acá faltó una identación


Mucho espacio sin ocupar


Este archivo no es necesario, recuerdas el .gitignore ?


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


You should add a protractor-test-rating-star class to the DOM and use it here.


I looked again.  It looks to me like lockdep does validate the try_ variants, based on kernel-2.6.32-504.16.2.1chaos.

For mutexes, I see mutex_trylock -> __mutex_trylock_slowpath -> mutex_acquire.  For rwlocks, I see read_lock -> _read_lock -> __read_lock -> rwlock_acquire_read -> lock_acquire.

So I will add handle mutex_tryenter().


@thewtex Matt:  I think this is what you were suggesting for a change to VXL.

Initial compilations work.


You may want to add an additional tag besides the manual networking like `multiple_manual_networks` because some CPI's may only support having a single NIC. Maybe a more generic `multiple_networks` tag would work


@akalicki we can combine them. It was just easier to code keeping them separate. When we add all types to the language, including `Dist`, I will go back in and make this a single function with a boolean flag.


Again, use a protractor-test specific class here.


Cuando se carga esto?


I would call the input ratingValue rather than stars.


I thought about that. Do any of these strike your fancy?

- limitDomain
- filterDomain
- allowableDomain


They were not saying that MAY is a generic extension mechanism. They are saying it means truly optional.  For extensions and whether or not the global options MUST NOT fail fast and MUST instead allow for plugins/hooks/extensions etc. to process said unknown global options... Well you just need to make that statement if that's what you want :-)


This can also have a `multiple_manual_networks` tag as well


Looks very nice! I have made some suggestions.


@akalicki Fixed in later commit.


I wanted to keep the actual business logic out of the gigantic callback HTTP handler.


https://github.com/vplin/Cloud_Forecast_Server/blob/master/System_Data_Socket/views.py
I'm learning how to put the codeblock in wiki...
The gateway example is here, later I will delete this one when I know how to put simple codeblock in wiki page
https://github.com/vplin/Cloud_Forecast_Gateway/blob/master/forwarder.py


Very elegant to fix this here already, rather than in every language binding generator that can't handle it.


This was travis specific, now it is too ugly. I prefer receiving this as parameter, like `ci/release <version>`.

Also, because it was travis-specific it was OK to support all OS travis support. Now, I prefer having one release script per OS.


TeamCity LabKey :: Sprint :: Premium :: Git postgres 9.4 [Build 4](https://teamcity.labkey.org/viewLog.html?buildId=290052&buildTypeId=LabKey_Sprint_2_LabkeyPremiumTrunk_GitPostgres94) outcome was **FAILURE**
Summary: Tests failed: 27 (5 new), passed: 253 Build time: 01:41:12
### Failed tests
```
org.labkey.test.tests.CDSVisualizationTest.verifyAntigenScatterPlot: <no details avaliable>

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

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

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

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

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

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

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

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

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

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

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


Ah ok, after a further look I understand. You are saying the ROC is significantly impacted by the score selected.
That's understood.

However, to do cross pipelines comparison, where let's say Freebayes, GATK Haplotype Caller and LoFreq are compared, in my view, all ROC should use the same score metric, otherwise it's not an apple-to-apple comparison.


que hace esta linea?


http://search.cpan.org/~leont/Test-Harness-3.35/lib/Test/Harness.pm#DESCRIPTION

Test::Harness is at present, because the modules that are available for backwards compatibility, it is that there is correct to use the TAP::Harness.

Therefore, it is thought that there is no need to put the link.


Yes, thank you!!


This should probably have a `raw_ephemeral_storage` tag on it. Basically I'm thinking that places we call `@requirements.stemcell.supports*` call we should have a group of tags


llevar esto a una hoja externa


Oh, OK. No problem. Take your time.
I was looking for data parsing and database insertions.

To start and end code block, simply use three `s. See https://guides.github.com/features/mastering-markdown/.


Los placeholder son explicativos no el mismo nombre del label


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


Hey @zee-moz! I like the matrix, however asking for an estimate on "Hour needed to complete" while also asking them to make sure their project continues indefinitely (sustainability plan) is a bit confusing. What is complete?

Could we either:
- specify hours needed to get to a specific goal (e.g. first working prototype)
- specify ongoing hours per month needed


clases semanticas "pestana-facebook-pegada" no sirve, que pasa si no va pegada despues?


IOW the language in rfc2119 around MAY include an item means the item is optional.  Item is one of those legal terms.  It's used for substitution.  You replace the word item with your thing that is made optional by the use of the word MAY.


Can we not use `bosh_ssh` here?


Este archivo no es necesario agregalo al .gitignore


Hooray! Long Live GCC 5.3! (wut


Falta una identación


On Mon, Dec 07, 2015 at 03:44:42PM -0800, Mike Brown wrote:
> They were not saying that MAY is a generic extension mechanism. They
> are saying it means truly optional.  For extensions and whether or
> not the global options MUST NOT fail fast and MUST instead allow for
> plugins/hooks/extensions etc. to process said unknown global
> options... Well you just need to make that statement if that's what
> you want :-)

No I think we want to leave the fail-fast/fail-slow for unknown
options up to the runtime (and I'd fail-fast in a runtime I was
responsible for).  I just wanted to make sure we weren't implying that
we wanted fail-slow by using MAY here.  It sounds like you're saying
fail-fast counts as “prepared to interoperate”, and if so, MAY is here
fine with me.


@gvanem Thanks, landed in df40b20.


No esta bien identado


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


Not sure why you chose to combine stylistic changes with data structure in this commit again... It looks like you followed the changes on my branch https://github.com/star-bnl/star-ist/commits/ds-bingchu-fork-1 but decided to rework them. I had a similar commit but without the semicolon fixes: https://github.com/star-bnl/star-ist/commit/542deadc59aec76d3b2b629ed584776fca2cfad3

Why double the work? Just cherry-pick them from my branch and modify the log message if you don't like them. I'd be absolutely fine with that.

All of those changes where you just do minor fixes in the style like removing semicolons I'd move into a single clean-up commit. "git rebase -i master" is quite powerful and can let you squash or split changes


Didn't know that. It builds OK for me locally, but I'm not building all the doc. I'll try your approach and update the PR. Thanks!


Please use spaces for margins


This issue is to implement the method. You can remove the comment since this change is doing exactly that :)


why the +1 here?


This is a good start, but you should probably talk to me, Camden, and Kiwi before you do any more work on a modpack system. We've actually been planning something for a while now and we have some very specific ideas in mind.


Looks nice, but... I can't figure out how to call `setuptools_scm.get_version()` directly from `setup.py`. It's a little embarrassing, but I'm currently doing this—which doesn't _quite_ work:

```
# Temp hack to work around the lack of an SCM working copy in our current
# setup: just return a hard-coded, dummy value if the lookup via SCM tags
# would fail.
dummy_version = '0.1.0'
class GetUseScmVersionArg:

    def dummy_version_from_scm(self, scm_root):
        import pdb;pdb.set_trace()
        return dummy_version

    def __call__(self, *args, **kwds):
        import setuptools_scm

        scm_version_okay = False
        for scm_path in ('.', '..'):
            try:
                setuptools_scm.get_version(scm_path)
                scm_version_okay = True
                break
            except LookupError:
                pass

        if not scm_version_okay:
            # Monkey patch the internal setuptools_scm function version_from_scm()
            setattr(setuptools_scm, 'version_from_scm', self.dummy_version_from_scm)

        return { 'root': scm_path, 'version_scheme': 'post-release' }

    def pop(self, value, retval=None):
        return retval
...

setup(
    author='...',
    ...
    packages=find_packages(),
    setup_requires=[
        'setuptools_scm',
    ] + pytest_runner,
    test_suite='tests',
    tests_require=[
        'coverage',
        'pytest',
    ],
    use_scm_version=GetUseScmVersionArg(),
    version=dummy_version,
    zip_safe=False,
)

```

(Passing a callable instance was suggested in the README for `setuptools_scm`, but monkey-patching `version_from_scm()` in it was my hack-tastic idea.)

I'm in the middle of changing our packaging process, bringing individual modules over one-at-a-time. Until I've finished that work, I can't guarantee that `setuptools.get_version()` won't throw an exception due to the most recent tag not matching the expected pattern. I'd hoped monkey-patching `version_from_scm()` to return a hard-code value, but the exception is getting thrown before then, here in `version.py`:

```
def meta(tag, distance=None, dirty=False, node=None, **kw):
    if parse_version is not None and not isinstance(tag, SetuptoolsVersion):
        tag = tag_to_version(tag)
    trace('version', tag)

    assert tag is not None, 'cant parse version %s' % tag      # <-- This assertion is failing for me
    return ScmVersion(tag, distance, node, dirty, **kw)
```

Does the `parse` argument to `get_version()` help me in this case?


* Pequeno erro.


Thank you! I have put it on wiki. For data storage, there is a ORM library in Django. It is very easy to manipulate data by using it. If the data from gateway is very regular, I suggest maybe we can use forms to accept/filter/verify the data in Django.


Unnecessary change


[![Pictorial Hanging Illustrating the Feast of Peaches](http://api.artsmia.org/images/16871/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=16871)


[![Chair cover](http://api.artsmia.org/images/14497/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=14497)


[![Woman's Quasi-Official Vest with Insignia Square](http://api.artsmia.org/images/16589/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=16589)


[![Chair cover](http://api.artsmia.org/images/16695/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=16695)


[![Pair of chair covers](http://api.artsmia.org/images/16697/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=16697)


[![Chair cover](http://api.artsmia.org/images/16702/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=16702)


[![Chair cover](http://api.artsmia.org/images/16733/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=16733)